-
Notifications
You must be signed in to change notification settings - Fork 18
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: temporary polling fix #114
Conversation
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.
approved with comments that aren't that important given the short-term nature of this code.
while (!complete) { | ||
const status = await mdapiRetrieve.checkStatus(); | ||
if (totalTimeMs >= this.getFlag<Duration>('wait').milliseconds) { | ||
throw SfdxError.create('@salesforce/plugin-source', 'retrieve', 'retrieveTimeout', [ |
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.
I haven't really looked in what SDR is doing, but I'm remembering we wanted to set a particular exit code (69? 70?) for timeouts and give the user something they could do [retry the deploy? check the status?]. If SDR isn't handling that, you might want to catch your error.
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.
The message Your retrieve request did not complete within the specified wait time [1 minutes]. Try again with a longer wait time.
already suggests increasing the timeout with --wait
I'll set the exit code to 69 - coming from https://salesforce.quip.com/JoC2A2IlF9a3
What does this PR do?
temp workaround for polling bug in core/SDR
What issues does this PR fix or reference?
@W-9472869@