[GH-ISSUE #246] Recording command that exits quickly produces asciicast without event lines #789

New issue

Closed

opened 2026-03-15 10:26:46 +03:00 by kerem · 3 comments

kerem commented

2026-03-15 10:26:46 +03:00

Owner

Originally created by @ku1ik on GitHub (Dec 2, 2017).
Original GitHub issue: https://github.com/asciinema/asciinema/issues/246

Recording who:

asciinema rec -c who out.cast

Produces asciicast with only header line.

It seems the process (who) exits before asciinema manages to write stdout to a file, even though who prints text.

Originally created by @ku1ik on GitHub (Dec 2, 2017). Original GitHub issue: https://github.com/asciinema/asciinema/issues/246 Recording `who`: asciinema rec -c who out.cast Produces asciicast with only header line. It seems the process (`who`) exits before asciinema manages to write stdout to a file, even though `who` prints text.

kerem

2026-03-15 10:26:46 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-15 10:27:12 +03:00

Author

Owner

@luckydenis commented on GitHub (May 6, 2019):

Good evening. I am interested in this problem. Can I add more information?

@luckydenis commented on GitHub (May 6, 2019): Good evening. I am interested in this problem. Can I add more information?

kerem commented

2026-03-15 10:27:17 +03:00

Author

Owner

@bsene commented on GitHub (Jul 15, 2019):

@sickill I tried the same recording:
asciinema rec -c who out.cast

Cast file contains all data and can be read within asciinema, so the issue seems to have been resolved maybe in recent versions.

PS: I tested it on MacOS(Mojave) environement

@bsene commented on GitHub (Jul 15, 2019): @sickill I tried the same recording: `asciinema rec -c who out.cast` Cast file contains all data and can be read within `asciinema`, so the issue seems to have been resolved maybe in recent versions. PS: I tested it on MacOS(Mojave) environement

kerem commented

2026-03-15 10:27:22 +03:00

Author

Owner

@ku1ik commented on GitHub (Feb 20, 2022):

This has been fixed around 2.0.

@ku1ik commented on GitHub (Feb 20, 2022): This has been fixed around 2.0.