The dev could probably say more, but Boolean values describes some of the general idea.
A boolean option passed will translate to the value
trueif it is supplied with no assigned value.
implicitly means (and it’s been more directly said elsewhere) that not giving option is false.
This forces code to choose the default behavior without the option, and here it’s to replace.
If you don’t like that, then add don't-replace ... option with a syntax that means true.
was probably a response to
Ensure booleans are false by default #6333
This PR changes
--replace-faulty-index-filesto--dont-replace-faulty-index-files, and swaps the default value.
The behavior with no option should be the same, but the way to change behavior changed.
To me, the GUI views look the same, but the help text didn’t change when option did.
I’ll repeat my previous gripe about the new UI not actually showing the option’s name.
I do know what name I chose from the selector menu, but how to reverse the display?
The help made more sense for replace-faulty-index-files idea. It should be changed, however writing to match the boolean false-by-default has a risk of using double-negatives.
One attempt: “Use this option to stop replacement of index files that are missing content during the testing phase. Replacement takes slightly longer, but will prevent very slow database recreates.”
As a side note, the replacement dindex is faulty enough to be replaced again and again, however is probably an improvement for recreate. This has been mentioned a few times.
I have a question for dev or other expert about Stop during backup. The old ngax UI gives two options (one renamed since earlier release). The new ngclient UI doesn’t give options.
Behaviors seem to vary. Can expectations be easily summarized? In particular, I’m seeing ngclient upload a short dlist file when I stop backup when status starts Counting, and this worries me because new Restore doesn’t note that it’s a partial file. This seems like a risk.
What used to be “Stop now” in ngax I think once just stopped without a dlist upload.
Given that these are somewhat controlled stops, is dlist supposed to upload, or is a synthetic file list supposed to happen on the next backup, probably allowing fast stop?
I haven’t tested ngax “Stop after current file”, but it would be nice if docs could explain various ways to Stop. There appear to be three between two UIs. Are some the same?