[GH-ISSUE #5484] [Feature] Add optional command timing summaries to CLI runs #3338

New issue

Closed

opened 2026-10-31 00:39:19 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 00:39:19 +00:00

Owner

Originally created by @jayykernel on GitHub (Oct 20, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/5484

Problem

Long-running analyses can involve input preparation, provider startup, analysis, projection, and output publication. Users currently have to infer where time is spent when diagnosing slow commands.

Proposed change

Add an opt-in --timings mode that prints a concise timing summary to stderr, leaving stdout unchanged for commands that emit JSON or other machine-readable results. Where feasible, expose the same measurements in an explicitly versioned metadata object.

Acceptance criteria

Timing output is disabled by default.
Stdout remains valid and parseable when a command is used in a pipeline.
Durations are labeled by measured stage and are not presented as provider-only time unless that is what was measured.
Unsupported stage measurements are omitted rather than guessed.
Tests verify both successful and failed command summaries.

The request is for observability; no current performance regression is asserted.

Originally created by @jayykernel on GitHub (Oct 20, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/5484 ### Problem Long-running analyses can involve input preparation, provider startup, analysis, projection, and output publication. Users currently have to infer where time is spent when diagnosing slow commands. ### Proposed change Add an opt-in `--timings` mode that prints a concise timing summary to stderr, leaving stdout unchanged for commands that emit JSON or other machine-readable results. Where feasible, expose the same measurements in an explicitly versioned metadata object. ### Acceptance criteria - Timing output is disabled by default. - Stdout remains valid and parseable when a command is used in a pipeline. - Durations are labeled by measured stage and are not presented as provider-only time unless that is what was measured. - Unsupported stage measurements are omitted rather than guessed. - Tests verify both successful and failed command summaries. The request is for observability; no current performance regression is asserted.

bsakaguchi closed this issue

2026-10-31 00:39:19 +00:00

bsakaguchi referenced this issue

2026-10-31 01:10:31 +00:00

[PR #3827] [CLOSED] fix(process): preserve __proto__ environment overrides #5929

bsakaguchi referenced this issue

2026-10-31 01:10:33 +00:00

[PR #3834] [CLOSED] fix(process): reject the __proto__ environment name the PTY backend drops #5935