-
Notifications
You must be signed in to change notification settings - Fork 153
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
Regard DSP as done only when preparation is successful considering of reuse the provider #5216
Regard DSP as done only when preparation is successful considering of reuse the provider #5216
Conversation
… reuse the provider Signed-off-by: Yoshiki Fujikane <[email protected]>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #5216 +/- ##
=======================================
Coverage 22.82% 22.83%
=======================================
Files 420 420
Lines 45302 45302
=======================================
+ Hits 10340 10344 +4
+ Misses 34166 34163 -3
+ Partials 796 795 -1 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch, thank you 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[ASK] How about the following point?
p.done = true |
Signed-off-by: Yoshiki Fujikane <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you
What this PR does / why we need it:
This modification is necessary to avoid an error when executing a cancellation while executing deploySourceProvider.Get in another stage.
I encountered such a situation when canceling the deployment via WebUI during the SCRIPT_RUN stage execution.
I reproduced the behavior when checking the behavior for the PR #5215 like this↓
Which issue(s) this PR fixes:
Part of #5214
Does this PR introduce a user-facing change?: