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
When setting FullState as false in StateService.json of StateService, that will not store every MPT data, but just calculate the latest State Root hash. However, I find it can be interrupted and throw exception which can force node stopping sync. But it works well when set FullState as true.
To Reproduce
Steps to reproduce the behavior:
Prepare a testnet node, install MPTTrie and StateService
Set FullState as false in StateService.json of StateService
Run the node, wait for sometime.
Error will be showed as:
Expected behavior
Every State Root hash should be calculated correctly and be the same as FullState mode. It shouldn't be interrupted. It shouldn't stop node sync as well.
Describe the bug
When setting
FullState
as false in StateService.json of StateService, that will not store every MPT data, but just calculate the latest State Root hash. However, I find it can be interrupted and throw exception which can force node stopping sync. But it works well when setFullState
as true.To Reproduce
Steps to reproduce the behavior:
MPTTrie
andStateService
FullState
as false in StateService.json of StateServiceExpected behavior
Every State Root hash should be calculated correctly and be the same as FullState mode. It shouldn't be interrupted. It shouldn't stop node sync as well.
Screenshots
Platform:
winx64, neo master branch
@cschuchardt88 @shargon
The text was updated successfully, but these errors were encountered: