-
Notifications
You must be signed in to change notification settings - Fork 72
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
[5.0] mapped_private causes fork database issue #1878
Comments
The Maybe an issue with WSL2 |
We are using mapped_private on debian 11 or 12. No issues so far. |
I'll give the |
As pointed out by @spoonincode WSL does not have
|
[5.0] Add additional tests for mapped_private
…main [5.0 -> main] Add additional tests for mapped_private
Testing with 5.0 commit 42034e3
Syncing with eos mainnet.
start/stop, start
./nodeos --data-dir dd --config-dir mainconfig2 --plugin eosio::prometheus_plugin --plugin eosio::chain_api_plugin --database-map-mode mapped_private
Note forkdb is ahead of state, so maybe state didn't write out.
The stop looks clean and there is no core.
The text was updated successfully, but these errors were encountered: