Improve extraction error reporting #122

Open
opened 2023-11-06 15:23:15 +01:00 by lucas · 0 comments
Owner

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.

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.
lucas added the
kind
enhancement
stage
actionable
crate/dtmt
labels 2023-11-06 15:23:15 +01:00
lucas added the
status/good first issue
label 2023-11-12 19:01:55 +01:00
lucas added this to the Mod Manager project 2023-11-15 01:02:49 +01:00
lucas added this to the DTMM v1.0 + DTMT milestone 2023-11-15 01:02:51 +01:00
lucas removed this from the DTMM v1.0 + DTMT milestone 2023-12-05 17:04:51 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: bitsquid_dt/dtmt#122
No description provided.