-
Notifications
You must be signed in to change notification settings - Fork 568
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
Odb undo #5491
Odb undo #5491
Conversation
Signed-off-by: Matt Liberty <[email protected]>
Signed-off-by: Matt Liberty <[email protected]>
Signed-off-by: Matt Liberty <[email protected]>
Intended usage:
|
clang-tidy review says "All clean, LGTM! 👍" |
Signed-off-by: Matt Liberty <[email protected]>
Signed-off-by: Matt Liberty <[email protected]>
Nice! Does the critical error crash the program? If we added C++ unit tests around this it would be easier if they were just throws. |
Critical calls exit(1) as there is no hope to continue with the db in an inconsistent state. We could have a test mode where it throws instead for unit testing if required. |
Head branch was pushed to by a user without write access
clang-tidy review says "All clean, LGTM! 👍" |
No description provided.