You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We have received 2 instances of reports with logs such as:
FATAL <C Chain> handler/handler.go:335 shutting down chain {"reason": "received an unexpected error", "error": "failed to notify VM that bootstrapping has started: synced root (0x35ae5c47aeab8d06a088b70034833af6414dfdb228f1f6e2a3cf65e94f4f04e5) does not match expected (0x48d9b80aa254dad0cbd11c36414eb36af46a595bbad975fefe5462a70eea9bd6) for atomic trie while processing async message:
To Reproduce
Unknown.
Expected behavior
No error during state sync.
The text was updated successfully, but these errors were encountered:
Describe the bug
We have received 2 instances of reports with logs such as:
FATAL <C Chain> handler/handler.go:335 shutting down chain {"reason": "received an unexpected error", "error": "failed to notify VM that bootstrapping has started: synced root (0x35ae5c47aeab8d06a088b70034833af6414dfdb228f1f6e2a3cf65e94f4f04e5) does not match expected (0x48d9b80aa254dad0cbd11c36414eb36af46a595bbad975fefe5462a70eea9bd6) for atomic trie while processing async message:
To Reproduce
Unknown.
Expected behavior
No error during state sync.
The text was updated successfully, but these errors were encountered: