Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

revert of #167 seem is not sufficient #196

Open
leakingtapan opened this issue May 23, 2024 · 0 comments
Open

revert of #167 seem is not sufficient #196

leakingtapan opened this issue May 23, 2024 · 0 comments

Comments

@leakingtapan
Copy link

in #177, it reverted #167, however, the revert seems not sufficient. we uses buildkite agent which depends on this pty package's v1.1.21. However, we are still seeing

fork/exec... operation not permitted

when PTY is enabled.

Note that v1.1.21 does help in that the occurrence of this bug is lower than v1.1.20. However, it just still happens at a lower rate.

See buildkite/agent#2790 for more details of the bug.

jsoriano added a commit to elastic/elastic-package that referenced this issue Jun 26, 2024
Use the helper `pty.Start()` instead of handling ourselves the tty and associated ptty. Wait for the finalization of the command just with the copy, to avoid a separate goroutine in an attempt to avoid the hangs we are seeing in CI.

Downgrade to pty 1.1.19, that seems to solve some kind of race condition creack/pty#196 that could be producing
the hangs.

Co-authored-by: Mario Rodriguez Molins <mario.rodriguez@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant