Replies: 3 comments 3 replies
|
I keep going back and forth on Task honestly. Lately I've been leaning a bit more against - to solve the logging thing what we could do is add an e.g. |
3 replies
|
(EDIT: comment posted before the above) Or maybe could we just add a log to: (but perhaps logging is not the only benefit of having everything go through Task so maybe it's not an excuse to give up on this discussion) |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I use
RUST_LOG=debugand forcrate::task::Taskit works great, e.g.:but for
std::process::Command(e.g.):https://github.com/containers/bootc/blob/d7c3f9f4aaf89eefe7c1ff7e5f2512b3fd010131/lib/src/mount.rs#L32-L41
there's no log, which is unfortunate.
Would it be reasonable to get rid of
Commandaltogether?Some obvious concerns is that Task doesn't necessarily provide all the flexibility
Commanddoes, but I'm sure in most cases that flexibility is unnecessaryAll reactions