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

sync upstream #5

Closed
wants to merge 21 commits into from
Closed

sync upstream #5

wants to merge 21 commits into from

Conversation

steebchen
Copy link
Collaborator

No description provided.

kkovaacs and others added 21 commits September 3, 2024 10:58
…ersioned constants

Starknet 0.13.2.1 introduces a new set of versioned constants which we'll
have to handle.
This defaulted to the L2 poll interval, which is 2s right now. This is
completely unjustified and just results in us polling L1 with a much
higher rate than expected.

This change adds the `--sync.l1-poll-interval` CLI option that defaults
to 30s.
We do check the continuation token before appending pending events to
the result set. However, the check was too strict: in case of an extract
block number match we used the offset from the token and we returned an
error in all other cases.

Unfortunately this breaks in the completely valid case where a
continuation token was in the request pointing to the non-pending block
but the page was not full with results from the database yet so we go on
appending events from the pending block.

This change fixes the check: if the block number in the token is
_before_ the pending block we simply start from offset 0 instead of
returning an error.

Closes: eqlabs#2191
…de-for-0.13.2.1

feat(crates/executor): upgrade blockifier to 0.8.0-rc.3 and add new versioned constants
…bugfixes

chore: backport some fixes to 0.14.2
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.

4 participants