Skip to content
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

Catch CORRUPTION error code and attempt automatic repair and reopen, or at least provide users the ability to directly repair #35

Open
CMCDragonkai opened this issue Jun 26, 2022 · 0 comments
Labels
development Standard development r&d:polykey:supporting activity Supporting core activity

Comments

@CMCDragonkai
Copy link
Member

CMCDragonkai commented Jun 26, 2022

Specification

Our C++ code can throw an exception with the code indicating CORRUPTION. This means the user needs to attempt to repair the database before they try to open it. This is because dbOpen itself can fail.

We need to catch this and attempt the repairDb native function. However we need to come up with tests for this, what is an example of a broken database? Maybe mess with the files in it.

Additional context

Tasks

  1. ...
  2. ...
  3. ...
@CMCDragonkai CMCDragonkai added the development Standard development label Jun 26, 2022
@teebirdy teebirdy added r&d:polykey:core activity 1 Secret Vault Sharing and Secret History Management and removed r&d:polykey:core activity 1 Secret Vault Sharing and Secret History Management labels Jul 24, 2022
@CMCDragonkai CMCDragonkai self-assigned this Jul 10, 2023
@CMCDragonkai CMCDragonkai added the r&d:polykey:supporting activity Supporting core activity label Jul 10, 2023
@CMCDragonkai CMCDragonkai removed their assignment Sep 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
development Standard development r&d:polykey:supporting activity Supporting core activity
Development

No branches or pull requests

2 participants