-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Running tool in Azure Pipelines will throw exception #6
Comments
I did some further investigation and when I output straight to the IConsole it does work. |
Hi @wterpstra ! I'm sorry I haven't been able to spend some time on this one.
I'm not really sure what's going on TBH but maybe changing the Region we provide here might have something to do with it? If we can determine it's an issue with CommandLine.Rendering then we should file an issue there. |
Hi @leonardochaia, no worries. I have both tried |
Hey @wterpstra! Just wanted you to know that I'm be building an Azure Pipelines where I'm using the current deployed version ( I wanted to ask you if you can give me more info of the stuff you have tried, so that we don't duplicate effort. |
All right, managed to reproduce it in this GitHub build. The fix came from here |
Run tool in CI pipeline. Fix NRE when piping output Fixes #6
Hey @wterpstra, I've released I've tested in Azure DevOps and it seems to be working fine. So perhaps with the Thanks for the help bud! |
When running the tool in Azure Pipelines to inspect my repository it throws the following exception:
Command I run:
It looks like the System.CommandLine.Rendering package cannot handle the way that Azure DevOps handles the stdout.
The text was updated successfully, but these errors were encountered: