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

Copying of stdout/stderr causes frequent deadlocks under WSL2 #673

Open
istyf opened this issue Nov 2, 2024 · 0 comments · May be fixed by #674
Open

Copying of stdout/stderr causes frequent deadlocks under WSL2 #673

istyf opened this issue Nov 2, 2024 · 0 comments · May be fixed by #674

Comments

@istyf
Copy link
Contributor

istyf commented Nov 2, 2024

Running the unit tests have a near (if not) 100% reproducible deadlock between all of the different output writers, caused by contention of a semaphore deep in the posix file system to be able to output text.

I have not had the time to root out the exact reason, but the use of io.Copy(os.Stdout, stdout) seems to be the culprit, because if that is changed the deadlock is no longer reproducible.

It seems reasonable that this deadlock could also happen within air itself and not only in the unit tests.

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

Successfully merging a pull request may close this issue.

1 participant