Repository navigation
eoc dataize command provides insufficient progress updates during prolonged compilation #1257
Description
I cannot tell whether eoc dataize is actually doing anything or has silently hung, because the only progress output is a step counter and file count that barely changes over several minutes:
➜ eprog eoc dataize hello
[9 steps] 3min; 3 files generated so far...
Two minutes later, the exact same command still shows almost nothing new:
➜ eprog eoc dataize hello
[9 steps] 5min; 3 files generated so far...
For an extremely small EO program, waiting 5+ minutes with no sign of what step is running or why it's taking so long gives no confidence that work is happening. This makes me want to hit Ctrl-C, even if something important is going on behind the scenes.
🤖 Generated with Claude Code
Activity
[-]eoc dataize gives no indication of progress during long compilation steps, making it look hung[/-][+]`eoc dataize` command provides insufficient progress updates during prolonged compilation[/+]objectionary#1257: show the running Maven goal in the progress line
objectionary#1257: show the running Maven goal in the progress line
objectionary#1257: show the running Maven goal in the progress line
yegor256 commentedon Nov 6, 2026
The current ticker shows a phase summary and file count, so the requested per-goal detail remains pending in #1456. That PR has changes requested: extend the concurrent-run readline/stream fixtures, verify goal delivery and forwarded output, and gate piped progress on stdout.isTTY before re-review. Current code: src/mvnw.js:138.
objectionary#1257: show the running Maven goal in the progress line
objectionary#1257: give the test wrapper a readline interface and a c…