Improve error message for verdi import when archive version is incompatible#1960
Merged
sphuber merged 1 commit intoSep 12, 2018
Conversation
…mpatible Since there is a known solution to this problem, i.e. running `verdi export migrate` it is best to inform the user of this instead of dumping a stack trace.
sphuber
force-pushed
the
fix_1947_verdi_import_better_error_message
branch
from
2d8d267 to
3a04770
Compare
szoupanos
approved these changes
Sep 12, 2018
Codecov Report
@@ Coverage Diff @@
## develop #1960 +/- ##
===========================================
- Coverage 67.59% 67.56% -0.03%
===========================================
Files 324 324
Lines 33330 33342 +12
===========================================
- Hits 22530 22529 -1
- Misses 10800 10813 +13
Continue to review full report at Codecov.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fixes #1947
Since there is a known solution to this problem, i.e. running
verdi export migrateit is best to inform the user of this instead of dumping a stack trace.