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

feat: return status in L2ToL1Message.waitUntilReadyToExecute #381

Merged
merged 1 commit into from
Dec 13, 2023

Conversation

DZGoldman
Copy link
Contributor

No description provided.

Copy link
Contributor

@yahgwai yahgwai left a comment

Choose a reason for hiding this comment

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

Looks good to me, but prob best to get an approve from the full stack team for sdk changes

@@ -349,18 +349,20 @@ export class L2ToL1MessageReaderClassic extends L2ToL1MessageClassic {
* WARNING: Outbox entries are only created when the corresponding node is confirmed. Which
* can take 1 week+, so waiting here could be a very long operation.
* @param retryDelay
* @returns
* @returns outbox entry status (either executed or confirmed but not executed)
Copy link
Contributor

Choose a reason for hiding this comment

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

"either executed or confirmed but not executed" - should be not pending?

@spsjvc spsjvc changed the title return status in L2ToL1Message.waitUntilReadyToExecute feat: return status in L2ToL1Message.waitUntilReadyToExecute Dec 13, 2023
@spsjvc spsjvc changed the title feat: return status in L2ToL1Message.waitUntilReadyToExecute feat: return status in L2ToL1Message.waitUntilReadyToExecute Dec 13, 2023
@spsjvc spsjvc changed the title feat: return status in L2ToL1Message.waitUntilReadyToExecute feat: return status in L2ToL1Message.waitUntilReadyToExecute Dec 13, 2023
@spsjvc spsjvc merged commit 376c83f into main Dec 13, 2023
7 checks passed
@spsjvc spsjvc deleted the return-in-waituntilreadytoexecute branch December 13, 2023 20:40
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants