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

fix: reverse syncwave order (#12376) #13101

Closed
wants to merge 1 commit into from

Conversation

drpaneas
Copy link
Contributor

@drpaneas drpaneas commented Apr 4, 2023

This PR is trying to address the situation where when you try to delete a syncwaves-created deployment, it does so in reverse order. I tried to come up with a unit-test but it always passes (before and after this PR) so it was useless. I have not much experience with syncwaves nor their code, but from what I understand this feature never worked properly (I am talking about the deletion -- not the creation).

Checklist:

  • Either this is a bug fix for Sync-waves not working as expected #12376
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Toolchain Guide
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • I have added a brief description of why this PR is necessary and/or what this PR solves.

Fixes #12376

@drpaneas drpaneas changed the title Fix reverse syncwave order Fix reverse syncwave order (fix for issue #12376) Apr 4, 2023
@crenshaw-dev crenshaw-dev changed the title Fix reverse syncwave order (fix for issue #12376) fix: reverse syncwave order (#12376) Apr 4, 2023
Signed-off-by: Panagiotis Georgiadis <[email protected]>
@codecov
Copy link

codecov bot commented Apr 4, 2023

Codecov Report

Patch coverage has no change and project coverage change: -0.05 ⚠️

Comparison is base (696631e) 49.06% compared to head (98d93ea) 49.01%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #13101      +/-   ##
==========================================
- Coverage   49.06%   49.01%   -0.05%     
==========================================
  Files         246      246              
  Lines       42561    42586      +25     
==========================================
- Hits        20881    20873       -8     
- Misses      19565    19599      +34     
+ Partials     2115     2114       -1     
Impacted Files Coverage Δ
controller/appcontroller.go 51.86% <0.00%> (-1.18%) ⬇️

... and 1 file with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@drpaneas
Copy link
Contributor Author

drpaneas commented Apr 5, 2023

This PR doesn't seem to address the issue properly.

@drpaneas drpaneas closed this Apr 5, 2023
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.

Sync-waves not working as expected
1 participant