con / con/duct

idea: --timestamp-outputs or --json-outputs

Open
#213 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
12
Forks
6
Avg merge
11d 11h
Merged PRs (30d)
1

Description

For debugging it might be useful to know when output was produced. ATM I could pipe output to `ts` to get stdout annotated. But that would not anyhow help with stderr. Hence I thought it might have been nice to be able to store outputs with

It is useful e.g. to see when command actually output something after "thinking hard". We could then also improve plotting graph with annotation on when tool was producing any stdout and/or stderr output on the timeline of resources consumption.

Sure thing, with buffering all those timings might be "approximate".

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.