-
-
Notifications
You must be signed in to change notification settings - Fork 95
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
Error when trying to read dotnet --info #228
Labels
Comments
daveaglick
added a commit
that referenced
this issue
Dec 20, 2023
#236 was merged recently, which includes your environment variable to extend the |
daveaglick
added
⚠ Bug
Something isn't working as expected
Feedback Needed
Further information is requested
labels
Dec 20, 2023
I'll test it and let you know, thanks. |
Worked perfectly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
I'm getting an error when reading the dotnet --info command, at certain times my cluster takes more than 4000ms to return the dotnet --info which causes Buildalyzer to fail.
Does it make sense to implement an environment variable for custom timeout values or wait for the console to respond to some value?
I can open this PR, but I would like to know if it makes sense and if there is any preference for waiting for the console or reading the timeout of some environment variable.
Just for context, I'm using dotnet stryker which has a dependency on Buildalyzer.
Code
Stryker Issue
The text was updated successfully, but these errors were encountered: