-
Notifications
You must be signed in to change notification settings - Fork 18
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 with mainnet is failing on merging GPOS+Graphene updates #276
Comments
|
Following PR #283 addressed this issue |
Instructions
Merge PR #270 (contains GPOS+Graphene fixes tested on Beatrice public TESTNET) with master branch.
Build the software and run the witness node with resync option.
Bug Description
Sync is failing at 20183906 complaining that "Unable to find object 1.26.4648" during the bet_cancel operation. Attached witness log have handful of information on failing operation with complete details.
Even though fork has happened on the same date, this issue has nothing to do with any fork related code changes. As a part of graphene updates, lot changes were done to upgrade peerplays chain.
Expecting that dealing with account(history) might went wrong or the object was removed from the db.
Corresponding PR:
Impacts
Describe which portion(s) of Peerplays may be impacted by this bug. Please tick at least one box.
Expected Behavior
resync should be successful without any issues.
The text was updated successfully, but these errors were encountered: