Disable apply button to workaround data loss issue #2204
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Temporary workaround for #2191. The actual fix requires a refactor to how entries/groups are created and saved (ie, move that function away from DatabaseWidget class).
Also fixes divide by zero error that can occur in the database icon download (found during testing of this issue).
Motivation and context
If a user creates a new entry and only hits apply and then locks the database, the new entry is lost.
How has this been tested?
Corrected automatic tests and manually
Types of changes
Checklist:
-DWITH_ASAN=ON
. [REQUIRED]