Skip to content
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

cherry-pick: Add container set fixes to v3.4.8 (#22) #23

Merged
merged 3 commits into from
Jul 5, 2023

Conversation

JPZ13
Copy link
Collaborator

@JPZ13 JPZ13 commented Jun 5, 2023

Cherry picks @isubasinghe's commits related to container sets against a v3.4.8 install. After validating with our affected customer, we should look to contribute these into the upstream

Fixes #TODO

Please do not open a pull request until you have checked ALL of these:

* [ ] Create the PR as draft .
* [ ] Run `make pre-commit -B` to fix codegen and lint problems.
* [ ] Sign-off your commits (otherwise the DCO check will fail).
* [ ] Use [a conventional commit
message](https://www.conventionalcommits.org/en/v1.0.0/) (otherwise the
commit message check will fail).
* [ ] "Fixes #" is in both the PR title (for release notes) and this
description (to automatically link and close the issue).
* [ ] Add unit or e2e tests. Say how you tested your changes. If you
changed the UI, attach screenshots.
* [ ] Github checks are green.
* [ ] Once required tests have passed, mark your PR "Ready for review".

If changes were requested, and you've made them, dismiss the review to
get it reviewed again.

---------

Signed-off-by: isubasinghe <isitha@pipekit.io>
@JPZ13 JPZ13 requested review from tico24 and isubasinghe June 5, 2023 11:07
@JPZ13
Copy link
Collaborator Author

JPZ13 commented Jun 5, 2023

@isubasinghe - I had to make some slight changes to deal with a conflict. Could you take a look?

@JPZ13 JPZ13 changed the title fix: add guard against NodeStatus (#22) cherry-pick: add guard against NodeStatus (#22) Jun 5, 2023
isubasinghe and others added 2 commits July 4, 2023 15:30
Ensures that a DAG is marked as failed always when shutdown strategy is
enabled.

---------

Signed-off-by: isubasinghe <isitha@pipekit.io>
Co-authored-by: Alan Clucas <alan@clucas.org>
…for LadyBug. (#10)

Need to properly fix this later, looks to be some kinda race condition
where sometimes Name is defined and sometimes it is not.

Signed-off-by: Isitha Subasinghe <isitha@pipekit.io>
@JPZ13 JPZ13 changed the title cherry-pick: add guard against NodeStatus (#22) cherry-pick: Add container set fixes to v3.4.8 (#22) Jul 4, 2023
@JPZ13 JPZ13 requested a review from Joibel July 4, 2023 14:35
Copy link
Collaborator

@Joibel Joibel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@JPZ13 JPZ13 merged commit 75449b0 into v3.4.8-pipekit Jul 5, 2023
@JPZ13 JPZ13 deleted the v3.4.8-pipekit-cherry-pick branch July 5, 2023 10:31
@JPZ13
Copy link
Collaborator Author

JPZ13 commented Jul 5, 2023

@tico24 - when you're feeling better, can you cut a release of v3.4.8-pipekit and ping @mostaphaRoudsari when it's ready?

@mostaphaRoudsari
Copy link

Thank you, @JPZ13!

@tico24, let me know if there is anything that I can do to help with testing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants