diff options
| author | furszy <matiasfurszyfer@protonmail.com> | 2024-01-09 09:54:49 -0300 |
|---|---|---|
| committer | furszy <matiasfurszyfer@protonmail.com> | 2024-01-22 10:50:03 -0300 |
| commit | 966f5de99a9f5da05c91378ad1e8ea8ed37ac3b3 (patch) | |
| tree | 8d1d6abefc908ec6dd83391553477f6349b02cc1 /src/test | |
| parent | 03752444cd54df05a731557968d5a9f33a55c55c (diff) | |
| download | bitcoin-966f5de99a9f5da05c91378ad1e8ea8ed37ac3b3.tar.xz | |
init: improve corrupted/empty settings file error msg
The preceding "Unable to parse settings file" message lacked
the necessary detail and guidance for users on what steps to
take next in order to resolve the startup error.
Co-authored-by: Ryan Ofsky <ryan@ofsky.org>
Diffstat (limited to 'src/test')
| -rw-r--r-- | src/test/settings_tests.cpp | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/src/test/settings_tests.cpp b/src/test/settings_tests.cpp index fa8ceb8dd6..41190b3579 100644 --- a/src/test/settings_tests.cpp +++ b/src/test/settings_tests.cpp @@ -99,7 +99,9 @@ BOOST_AUTO_TEST_CASE(ReadWrite) // Check invalid json not allowed WriteText(path, R"(invalid json)"); BOOST_CHECK(!common::ReadSettings(path, values, errors)); - std::vector<std::string> fail_parse = {strprintf("Unable to parse settings file %s", fs::PathToString(path))}; + std::vector<std::string> fail_parse = {strprintf("Settings file %s does not contain valid JSON. This is probably caused by disk corruption or a crash, " + "and can be fixed by removing the file, which will reset settings to default values.", + fs::PathToString(path))}; BOOST_CHECK_EQUAL_COLLECTIONS(errors.begin(), errors.end(), fail_parse.begin(), fail_parse.end()); } |