Feature #1325
closed
obsync: summary error on exit
Added by Sage Weil almost 13 years ago.
Updated almost 13 years ago.
Description
Print a final error message that classifies errors with source vs destination and transient vs permanent. This should be easily parseable by obsync users..
The transient/permanent is the tricky part. Permanent would include authentication, transient would include any connectivity issues.
Which should we err toward?
- Target version changed from v0.32 to v0.33
- Translation missing: en.field_position set to 2
- Translation missing: en.field_story_points set to 5
- Translation missing: en.field_position deleted (
14)
- Translation missing: en.field_position set to 14
- Assignee set to Colin McCabe
- Status changed from New to Resolved
3e9a982a88ed16e5b47136f617193d6056b32ab4 should give us enough to get started with.
Right now, I just made all the I/O-related errors temporary, and everything else permanent. I'm sure we'll discover errors we want to reclassify as temporary or permanent once we start using obsync a little more in production, and we can file bugs for just those issues.
ALL errors output a last line in the form:
ERROR TYPE: <type>, ORIGIN: <origin>
where type={temporary, permanent, unknown}
origin={source, destination, unknown}
Also available in: Atom
PDF