-
Notifications
You must be signed in to change notification settings - Fork 672
fix(billing): resolve terminal promise even if success side effects throw #14964
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
Open
christian-byrne
wants to merge
4
commits into
main
Choose a base branch
from
test/billing-op-store-coverage
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
e3442d9
fix(billing): resolve terminal promise even if success side effects t…
christian-byrne 46b357d
fix(billing): extend try/finally to cover all post-success side effects
christian-byrne 027e785
fix(billing): move try/finally to cover cleanup, telemetry, and recon…
christian-byrne 5518a47
[automated] Apply ESLint and Oxfmt fixes
actions-user File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win
Consider logging the swallowed side-effect error.
The
finallyblock guaranteesresolveTerminal, but the original error still propagates out ofhandleSuccess.pollawaitshandleSuccessinside its owntry, so the rejection reaches thecatchat line 258. There,currentOperation !== operationis true becauseupdateOperationStatusreplaced the map entry, sopollreturns and discards the error.Result: a reconciliation or telemetry failure leaves no diagnostic signal. Add a
catchthat logs the error before rethrowing or before returning, so failures in the success path stay observable.♻️ Proposed observability improvement
} finally { resolveTerminal(opId) }📝 Committable suggestion
🤖 Prompt for AI Agents