[Issue] Nym client fails to setup persistent storage backend and creates fresh database every time.

[a-moreira]

Describe the issue
Getting en ERROR every time that I start a new client. Using nym-sdk to spin up a client and listen to messages.

Expected behaviour
I expect it to be able to restore the last DB and start from there.

Stack Traces

2023-10-26T17:07:39.481Z INFO  nym_client_core::client::base_client::non_wasm_helpers > loading existing surb database
2023-10-26T17:07:39.483Z INFO  nym_client_core::client::replies::reply_storage::backend::fs_backend::manager > Database migration finished!
2023-10-26T17:07:39.483Z ERROR nym_client_core::client::base_client::non_wasm_helpers                        > failed to setup persistent storage backend for our reply needs: The loaded data is inconsistent - it seems that on the last shutdown the client hasn't finished the data flush. You may have to remove the entire storage manually. We're going to create a fresh database instead. This behaviour might change in the future
2023-10-26T17:07:39.484Z INFO  nym_client_core::client::base_client::non_wasm_helpers                        > creating fresh surb database
2023-10-26T17:07:39.486Z INFO  nym_client_core::client::replies::reply_storage::backend::fs_backend::manager > Database migration finished!
2023-10-26T17:07:39.490Z INFO  nym_client_core::client::base_client                                          > Starting nym client

Steps to Reproduce
Steps to reproduce the behaviour, if you're familiar with BDD syntax, please write it in this style:

• I'm running nym-sdk in Rust to listen to messages
• I'm basically running the parallel_sending_and_receiving.rs example inside my own application.
• Every time I start the application it throws the error above and crates a fresh DB.
• I expect it to be able to restore the last DB and start from there.

Which area of Nym were you using?

• Application: nym-sdk in Rust, specifically the nym-client.
• OS: Ubuntu 23, MacOS Sonoma
• Version: commit 6e3bb2ec181fa8bf59548a0cb45ca5f6033f5c3b

[github-actions]

Thank you for raising this issue

[a-moreira]

Nevermind, my mistake. I was not calling disconnect() after a SIGINT. Just added a ctrlc handler and it works properly now.