-
Notifications
You must be signed in to change notification settings - Fork 9
feat(runner): Add onCommit callback support for Cell and Stream operations #1879
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
Merged
bfollington
merged 2 commits into
main
from
feat/add-on-success-callback-for-cell-and-stream-send
Oct 8, 2025
Merged
Changes from all commits
Commits
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -42,6 +42,10 @@ const logResult = ( | |
| }; | ||
|
|
||
| export class ExtendedStorageTransaction implements IExtendedStorageTransaction { | ||
| private commitCallbacks = new Set< | ||
| (tx: IExtendedStorageTransaction) => void | ||
| >(); | ||
|
|
||
| constructor(public tx: IStorageTransaction) {} | ||
|
|
||
| get journal(): ITransactionJournal { | ||
|
|
@@ -175,6 +179,38 @@ export class ExtendedStorageTransaction implements IExtendedStorageTransaction { | |
| } | ||
|
|
||
| commit(): Promise<Result<Unit, CommitError>> { | ||
| return this.tx.commit(); | ||
| const promise = this.tx.commit(); | ||
|
|
||
| // Call commit callbacks after commit completes (success or failure) Note | ||
| // that promise always resolves, even if the commit fails, in which case it | ||
| // passes an error message as result. An exception here would be an internal | ||
| // error that should propagate. | ||
| promise.then((_result) => { | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should we capture commitCallbacks first? |
||
| // Call all callbacks, wrapping each in try/catch to prevent one | ||
| // failing callback from breaking others | ||
| for (const callback of this.commitCallbacks) { | ||
| try { | ||
| callback(this); | ||
| } catch (error) { | ||
| logger.error("Error in commit callback:", error); | ||
| } | ||
| } | ||
| }); | ||
|
|
||
| return promise; | ||
| } | ||
|
|
||
| /** | ||
| * Add a callback to be called when the transaction commit completes. | ||
| * The callback receives the transaction as a parameter and is called | ||
| * regardless of whether the commit succeeded or failed. | ||
| * | ||
| * Note: Callbacks are called synchronously after commit completes. | ||
| * If a callback throws, the error is logged but doesn't affect other callbacks. | ||
| * | ||
| * @param callback - Function to call after commit | ||
| */ | ||
| addCommitCallback(callback: (tx: IExtendedStorageTransaction) => void): void { | ||
| this.commitCallbacks.add(callback); | ||
| } | ||
| } | ||
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.
Think it makes sense to pass error to the onCommit function?
onCommit could have an optional additional parameter for it.
However, that may be exposing more runtime information to patterns than we want.
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 don't think patterns will be allowed to 'see' this signature anyway? We could have ANOTHER optional callback for errors but that's starting to feel bloated to me.