Improve extraction error reporting #122
Labels
No labels
ci
crate/dtmm
crate/dtmt
crate/sdk
crate/serde_sjson
kind
bug
kind
documentation
kind
enhancement
kind
feature
kind
question
kind
upstream
part/bundle
part/filetype
stage
actionable
stage
design
stage
proposal
status/duplicate
status/good first issue
status/help wanted
status/invalid
status
need-replicate
status/wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: bitsquid_dt/dtmt#122
Loading…
Add table
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?
When extraction produces a lot of files and some of them error, their result is printed immediately, only to be buried by the subsequent output. This is especially apparent in debug mode, where logging produces at lot more data.
https://github.com/eyre-rs/color-eyre/issues/122 has a nice idea of accumulating everything until the end, then printing it. And with https://github.com/eyre-rs/color-eyre/pull/125, it could be put into a single
Report
structure.Though I probably don't need that specifically. I probably want the flexibility of printing each error myself.
I should, however, not stop printing failure notifications right where they happen.
Seeing both the success messages and at least a one-line failure message in real time is very nice to verify that everything is running fine.