Poor error reporting for bad YAML includes #196
Labels
No labels
blocked
breaking
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
borgmatic-collective/borgmatic#196
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Given these config files that wrongly try a (dictionary) YAML merge include on a item that is a list...
bad.yaml:repositories.yaml:Both
borgmaticandvalidate-borgmatic-configgive this error message:Unlike for other errors, theer's no indication what or where in the file the error is.
Thanks for reporting. This error is coming from deep within
ruamel.yaml, but we may be able to do something about it.Well, I've got a potential fix (needs more testing) that results in the following better error message:
Fixed in master. The fix will go out as part of the next release. I do really appreciate tickets on these sorts of things, as it helps me find and fix things that are unclear or just plain wrong that I may not know about.
Just released as part of borgmatic 1.3.7.