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: Restrict try-catch in upload command so build can be finalized #387

Merged
merged 2 commits into from
Oct 3, 2019

Conversation

wwilsman
Copy link
Contributor

@wwilsman wwilsman commented Oct 3, 2019

Purpose

During image upload, If an error occurs after starting a build, but before finalizing, the build will get stuck waiting for snapshots.

Approach

Rather than try-catching the entire method, the try-catch can be wrapped around only the section between creating and finalizing a build. The try-catch is used instead of chaining a .catch onto the promise in case the reduce callback throws during argument evaluation.

Rather than try-catching the entire method, the try-catch can be wrapped around
only the section between creating and finalizing a build. The try-catch is used
instead of chaining a `.catch` onto the promise in case the `reduce` callback
throws during argument evaluation.
@wwilsman wwilsman requested a review from Robdel12 October 3, 2019 21:30
Copy link
Contributor

@Robdel12 Robdel12 left a comment

Choose a reason for hiding this comment

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

🏁 LGTM :shipit:

@wwilsman wwilsman merged commit eed8798 into master Oct 3, 2019
@wwilsman wwilsman deleted the ww/finalize-upload-error branch October 3, 2019 21:42
djones pushed a commit that referenced this pull request Oct 3, 2019
## [0.18.1](v0.18.0...v0.18.1) (2019-10-03)

### Bug Fixes

* Restrict try-catch in upload command so build can be finalized ([#387](#387)) ([eed8798](eed8798))
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.

None yet

2 participants