search

phmonte / Buildalyzer

A utility to perform design-time builds of .NET projects without having to think too hard about it.
MIT License
589 stars 92 forks source link

Error when trying to read dotnet --info #228

Closed phmonte closed 4 months ago

phmonte commented 1 year ago

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

daveaglick commented 6 months ago

236 was merged recently, which includes your environment variable to extend the dotnet --info timeout. I also extended the default wait time in version 6.0.2 to 10 seconds (rolling out now). Can you try the latest 6.0.2 version and let me know if this issue is now resolved? Thanks!

phmonte commented 5 months ago

I'll test it and let you know, thanks.

phmonte commented 4 months ago

Worked perfectly.