refactor: configurable inbox lag #19034
Merged
Conversation
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
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
LHerskind
force-pushed
the
lh/tmnt-462-lag-inbox-tree-consumption-by-one-checkpoint
branch
from
f95ea90 to
80399a5
Compare
Merged
LHerskind
force-pushed
the
lh/tmnt-462-lag-inbox-tree-consumption-by-one-checkpoint
branch
from
80399a5 to
c9cada9
Compare
Surprisingly little pain on the typescript side since we already had all that pain long ago, so the ts was already waiting until ready which seemed handled without hardcoded ideas around a lag
AztecBot
force-pushed
the
lh/tmnt-462-lag-inbox-tree-consumption-by-one-checkpoint
branch
from
c9cada9 to
ee146c8
Compare
AztecBot
deleted the
lh/tmnt-462-lag-inbox-tree-consumption-by-one-checkpoint
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Surprisingly little pain on the typescript side since we already had all that pain long ago, so the ts was already waiting until ready which seemed handled without hardcoded ideas around a lag