Summary
moat run sometimes prints the container's stdout inline after Press Ctrl+C to stop, and sometimes prints nothing — the output is then only retrievable via moat logs <run-id>. Same command, same example, different runs.
Repro
moat run examples/grant-github-nossh repeatedly. Some invocations show the script output inline; others show only the Started … / View output: lines and require moat logs <id> to see anything.
Environment
- macOS, ghostty terminal (cmux).
Notes
Summary
moat runsometimes prints the container's stdout inline afterPress Ctrl+C to stop, and sometimes prints nothing — the output is then only retrievable viamoat logs <run-id>. Same command, same example, different runs.Repro
moat run examples/grant-github-nosshrepeatedly. Some invocations show the script output inline; others show only theStarted …/View output:lines and requiremoat logs <id>to see anything.Environment
Notes
-i), short-lived container runs while validating github grant injects Bearer for github.com, but git smart-HTTP requires Basic — HTTPS git fetch/push still broken (follow-up to #180) #370. Possibly a race between container exit / log flush and the host attach/stream path (inline stream vsstorage.LogWritercapture).