mirror of
https://github.com/asciinema/asciinema.git
synced 2026-04-25 07:55:51 +03:00
[GH-ISSUE #548] asciinema cat fails with OSError: [Errno 6] No such device or address: '/dev/tty' when running from GitHub Action #300
Labels
No labels
bug
compatibility
feature request
fit for beginners
help wanted
hosting
idea
improvement
packaging
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/asciinema#300
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @vorburger on GitHub (May 6, 2023).
Original GitHub issue: https://github.com/asciinema/asciinema/issues/548
Describe the bug
In https://github.com/enola-dev/enola/pull/142, I would like to run
asciinemafrom a GitHub Action.To Reproduce
Create a GitHub
.github/workflows/asciinema.yamlwith arun:of something which launchesasciinematriggers:Versions:
2.2.0Additional context
I gathered this is related to https://github.com/actions/runner/issues/241, and understand that this isn't so much a "bug" of
asciinemabut a limitation of the Linux environment of a GitHub Action not having a/dev/tty.But perhaps someone can provide some input or suggestions how to work around this? I've found https://github.com/tarides/meio/pull/48/files where @TheLortex patches a
get_terminal_size()- but that doesn't seem to be where it fails above...@vorburger commented on GitHub (May 6, 2023):
After enabling
set -xin my script, I figured that this actually seems to be specific only toasciinema catand notasciinema rec; I will update the log above with details, and the issue title, accordingly.I can work around this by not using
asciinema catin the GitHub Action and just change my script to to run that locally. (BTW https://github.com/zechris/asciinema-rec_script/issues/63 is something about doing that alltogether differently, otherwise unrelated to this.)Keeping this issue open for others who may run into this and possible future better workaround.
@ku1ik commented on GitHub (May 7, 2023):
Thanks. I think we can find a simple way to fix this for
cat.