-
Notifications
You must be signed in to change notification settings - Fork 0
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
Wait for last operation if not completed #59
Conversation
Pull Request Test Coverage Report for Build 12039568963Details
💛 - Coveralls |
Not ready for review yet |
Okay - PTAL? |
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.
This reminded me that I had hit this very same issue earlier this year:
https://github.com/m-lab/visualizations/pull/10/files
I had tried to use the operations wait
functionality, but there was a bug in it and I just fell back on using sleep
with a safe amount of time. Your implementation is very similar to what I had originally in the PR above, but I found that sometimes the command substitution didn't return anything due to likely very tight timings, and when that happens the entire command fails, and the build fails too. I'm wondering if your solution might run into the same issue?
Reviewable status: 0 of 1 approvals obtained
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.
Oh, it definitely could - the || :
was meant to catch the case where the wait operation fails, either for the reason you describe or any other.
What do you think?
Reviewable status: 0 of 1 approvals obtained
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.
Got it. Sorry I missed that bit. LGTM.
Reviewed 1 of 1 files at r2, all commit messages.
Reviewable status: complete! 1 of 1 approvals obtained
The Autojoin API deployment includes three distinct steps in production:
While step 2 will return successfully, the operation it creates is not yet "COMPLETE" by the time step 3 begins, which generates a build error like the one below.
This change adds an explicit
operation wait
on that operation before continuing to step 3.Build error:
This change is