-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
Fail to sync past epoch 22 on sui mainnet when data ingestion is enabled #20487
Comments
Seems to have been introduced by #18144 |
@robmcl4 Thanks for the very detailed report and for bisecting to figure out where the bug was introduced. Its unfortunate that some of those commits didn't build (that's embarrassing on my part) but the information you provided was able to help me know where to look. I haven't had time to do a repro of the case you provided but I believe #20490 (or some form of this fix) should address the change in functionality, and bug, that was introduced in 874da38 (CheckpointData: fix bug when loading input objects with deleted shared objects, 2024-06-10). If you get a chance, before I do, let me know if the patch was able to successfully fix the bug and let you proceed past epoch 22 with the ingestion turned on. |
No worries, I will pull |
That seems to have fixed it! |
Steps to Reproduce Issue
I am running within docker-compose. I ran a
git bisect
and identified that the issue is introduced somewhere within commits 76d4852 (known bad), 874da38 (does not compile) and 855aa35 (does not compile). The issue is ONLY present when thecheckpoint-executor-config
section is present in the config; otherwise it does not present. The crash occurs every time I delete and try again (not flaky).I have the
sui
repository cloned in./sui/
System Information
Exception
Below is a snippet of the exception with RUST_BACKTRACE=full (as set in
docker-compose.yml
above). I also attached the full log. Note that this log is from commit 76d4852. Later commits are also bad, and I have logs demonstrating a crash for them as well, if needed.76d48528e6c11bdea99fbb26472884cf5ed97c14.crash.log.gz
The text was updated successfully, but these errors were encountered: