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
In case the node is shut down without writing the snapshot fully, offline pruning becomes incompatible with the delayed snapshot initialization. This theory should be confirmed and the initialization sequence should be fixed.
Expected behavior
Offline pruning should function without any workarounds or unrelated configuration changes.
Screenshots
If applicable, add screenshots to help explain your problem.
Logs
If applicable, please include the relevant logs that indicate a problem and/or the log directory of your node. By default, this can be found at ~/.avalanchego/logs/.
Metrics
N/A
Operating System
N/A
Additional context
Add any other context about the problem here.
Describe the bug
In case the node is shut down without writing the snapshot fully, offline pruning becomes incompatible with the delayed snapshot initialization. This theory should be confirmed and the initialization sequence should be fixed.
To Reproduce
Several users have reported this on discord with a workaround: https://discord.com/channels/578992315641626624/1113120800975888444/1113120800975888444
https://discord.com/channels/578992315641626624/757576823570825316/1115070900413419521
Expected behavior
Offline pruning should function without any workarounds or unrelated configuration changes.
Screenshots
If applicable, add screenshots to help explain your problem.
Logs
If applicable, please include the relevant logs that indicate a problem and/or the log directory of your node. By default, this can be found at
~/.avalanchego/logs/
.Metrics
N/A
Operating System
N/A
Additional context
Add any other context about the problem here.
Avalanche Bug Bounty program can be found here.
The text was updated successfully, but these errors were encountered: