-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release v3.4.10 cherry-pick candidates #11552
Comments
We would like to get a fix for #11330 because it breaks our production pipelines. |
Let's get this one in the patch release as well: #11493 |
Would it be possible to get this fix in? #10927 |
@advithVashist That's a feature so no. We want to avoid new bugs. |
Got it, thanks :) |
Any chance of getting #11456 in? Would be nice to not have to manually patch this and I'm not sure if the check box being unchecked mean it's not getting in. |
Sure |
Working branch: https://github.com/argoproj/argo-workflows/tree/release-3.4.10 Will need more time for the following: Failed to cherry-pick due to conflicts:
|
Yes unchecked ones are not getting included in this release. They are either not cherry-pickable or are bug fixes for new features that did not exist in v3.4 yet. |
These cannot be cherry-picked since the v3.4.10 release branch diverges from master branch too much and have non-trivial conflicts to resolve. If you'd like to get them into this release, please submit a PR to the release branch by the end of next Tuesday. https://github.com/argoproj/argo-workflows/tree/release-3.4.10
|
#11426 might be good to get into a patch as well. I believe it's still failing on a test flake (unfortunately being a Member does not give CI retry permissions 😕 ) |
@shmruin would you be willing to make a PR for this? The conflict seems rather simple to solve as far as I can tell (add Sorry for asking, but I don't have a good way to test this right now. |
@jaen yes, I am willing to. I think I can try this on tuesday. |
Done |
@terrytangyuan @jaen I made a PR to 143d0f5 fix: Fixed memoization is unchecked after mutex synchronization. |
Thanks. Since no one else has responded regarding other commits, I'll trigger the release process soon. |
Please check the ones we want to cherry-pick.
From discussions:
Bug fixes:
httpbin
with something up to date #10427 (fix: Switch to use kong/httpbin to support arm64. Fixes #10427 #11533)OOMKilled
with container-set. Fixes Pod hangs when container in ContainerSet is OOM Killed #10063 (fix: SupportOOMKilled
with container-set. Fixes #10063 #11484)Persisted
label ([Pre-release] Workflows are shown as not archived after workflow GC #11367) (fix: persist archived workflows withPersisted
label (#11367) #11413)msg="Checking daemoned children of "
#10960) (fix(controller): Drop log "Checking daemoned children" without nodeID (Fixes #10960) #10974)Build:
Makefile
(build: pin versions of NPM global deps inMakefile
#11425)CI:
snyk.yaml
andrelease.yaml
for Node v20 (ci: fixsnyk.yaml
andrelease.yaml
for Node v20 #11461)The text was updated successfully, but these errors were encountered: