-
Notifications
You must be signed in to change notification settings - Fork 804
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
[DependencyManager] Possible deadlock reading stdout and stderr #10665
Comments
KevinRansom
added a commit
to KevinRansom/fsharp
that referenced
this issue
Dec 13, 2020
KevinRansom
added a commit
that referenced
this issue
Dec 14, 2020
* fix 10665 - Possible deadlock reading stdout and stderr #10665 * Add timeout to resolve api * validation * surface area * FSharpqa test
KevinRansom
added a commit
to KevinRansom/fsharp
that referenced
this issue
Dec 15, 2020
KevinRansom
added a commit
that referenced
this issue
Dec 15, 2020
nosami
pushed a commit
to xamarin/visualfsharp
that referenced
this issue
Feb 23, 2021
* fix 10665 - Possible deadlock reading stdout and stderr dotnet#10665 * Add timeout to resolve api * validation * surface area * FSharpqa test
nosami
pushed a commit
to xamarin/visualfsharp
that referenced
this issue
Feb 23, 2021
* Fix dotnet#10665 --- for test framework * Update test framework
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please provide a succinct description of the issue.
The pattern for consuming stdout and stderr from a child process could lead to a deadlock here:
fsharp/src/fsharp/FSharp.DependencyManager.Nuget/FSharp.DependencyManager.Utilities.fs
Lines 184 to 185 in 02fbde6
Provide the steps required to reproduce the problem:
Conditions that can lead to a deadlock are documented here: https://docs.microsoft.com/en-us/dotnet/api/system.diagnostics.process.standardoutput?view=net-5.0#remarks
It's possible that this is implicated in frequent deadlocks we've been seeing in the .NET Interactive CI pipeline but they're not reproducible elsewhere, so I'm speculating.
The text was updated successfully, but these errors were encountered: