You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Commands that fire interactive programs do not work properly. It seems this is because we spawn commands with new process group id (using SysProcAttr.Setpgid) and for some reason we loose stdout/stdin connection somehow.
Steps To Reproduce
Create the following actfile:
# actfile.ymlversion: 1acts:
vim:
cmds: vim
Run act run vim
We going to see a warning telling that input is not from a terminal and vim does not work properly.
Expected Behaviour
The interactive program should be indeed interactive and does not show any errors.
Screenshots
Environment
OS: MacOS
OS Version: 10.15.7
Act Version: 1.1.7
The text was updated successfully, but these errors were encountered:
## [1.1.9](v1.1.8...v1.1.9) (2021-07-05)
### Bug Fixes
* **log:** fix double logging for detached acts ([c71a80a](c71a80a))
* **run:** convert flags to upper snake case so they can be correctly used in commands as env vars ([fd90f06](fd90f06))
* **run:** use SysProcAttr.Setsid instead of SysProcAttr.Setpgid to allow interactive acts ([b836e0a](b836e0a)), closes [#1](#1)
Bug Description
Commands that fire interactive programs do not work properly. It seems this is because we spawn commands with new process group id (using
SysProcAttr.Setpgid
) and for some reason we loose stdout/stdin connection somehow.Steps To Reproduce
act run vim
Expected Behaviour
The interactive program should be indeed interactive and does not show any errors.
Screenshots
Environment
The text was updated successfully, but these errors were encountered: