-
Notifications
You must be signed in to change notification settings - Fork 256
az pipelines agent list returns invalid JSON #755
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
Comments
@WillTheProgrammer This is the json response I am getting.. the oSDescription is Null yes but I do not get the error. The output should be compliant with the API output as described here. Can you share more on what you are getting? Depending on the details I can work with the team owning that API to help fix it. |
@WillTheProgrammer Awaiting details on this issue. It is not reproducible at my end. Please share more details like json output you are getting or debug logs of output in case of failure. |
I am still seeing the error on my end. It appears to be present any time that there is an oSDescription available for the agent. I noticed that in your example you get back a single null description for 'oSDescription'. Could you try running this command on a pool-id with a pool that has an agent with an oSDescription that is not null? I believe that you will see the duplicate key (making it an invalid json) then. Thanks! |
@WillTheProgrammer Thank you for sharing the details. I will give it a try. |
@atbagga -> Any success? |
@WillTheProgrammer Was working on some other tickets. Will get back to this one next. |
Fix will be available in release 0.13.0 in next couple of weeks. |
Describe the bug
The command az pipelines agent list --pool-id [any valid pool id] return a JSON object that has two entries for oSDescription, the first key oSDescription always has a value of 'null'. This invalid format prevents it from being parsed.
To Reproduce
Azure Cli Version: 2.0.69
Azure-Devops extension version: 0.12.0
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: