-
Notifications
You must be signed in to change notification settings - Fork 70
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
Problems with ship initial block in Leap 4.0.3 #1340
Milestone
Comments
snapshot source: http://seed01.eosusa.news/snaps/proton/proton-2023-06-25_10-00.tar.gz node configuration:
|
Testing with 3.1 I do not see deltas in the first block after a snapshot. What version of SHiP do you see expected behavior? |
heifner
added a commit
that referenced
this issue
Jul 6, 2023
heifner
added a commit
that referenced
this issue
Jul 6, 2023
… blocks applied. Also do not repeatable send empty get_blocks_response messages but rather start sending first available block data.
heifner
added a commit
that referenced
this issue
Jul 7, 2023
[4.0] SHiP: Support snapshot start with full deltas
heifner
added a commit
that referenced
this issue
Jul 7, 2023
heifner
added a commit
that referenced
this issue
Jul 7, 2023
[4.0 -> main] SHiP: Support snapshot start with full deltas
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I started a ship server from a recent portable snapshot (Proton Mainnet, which is fully EOS-compatible), then after restart it prints
Trying to start Chronicle from this ship endpoint, and getting a number of various errors:
If I remove all p2p peers (to save the CPU and storage I/O), Chronicle does not receive anything from ship.
With at least one living p2p peer, starting chronicle with
--start-block=200079886
and it starts receiving table deltas immediately. It's supposed to receive the whole state first, so that it populates its ABI database. This is a breaking change.The text was updated successfully, but these errors were encountered: