microsoft / microsoft/go

AzDO pipeline polling error: "invalid character '<' looking for beginning of value"

Open
#1,035 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

release-automation
Dominant language
Go
Stars
431
Forks
44
Avg merge
21h 18m
Merged PRs (30d)
30

Description

While polling a build for completion, a call got this error, making the pipeline fail:

invalid character '<' looking for beginning of value

https://dev.azure.com/dnceng/internal/_build/results?buildId=2261106&view=logs&j=8d802004-fbbb-5f17-b73e-f23de0c1dec8&t=995a157e-87d5-56c6-b42a-d8b689a8a0cd&l=409

In my experience this happens when the API returns HTML instead of the expected JSON. Authentication is an easy way to hit it, but maybe it's rate limiting or some internal error?

At the very least, we should try to change the code to show the whole response when this happens so we can investigate. I'm not sure how deep in the AzDO library this would need to be done. We should also see if there are newer versions of the module available that might address this.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files or tests; start by locating the Azure DevOps build-polling entry point and reproducing the linked build failure. Inspect the response behind the JSON parse error and check whether newer Azure DevOps module versions exist. Done means exposing the complete non-JSON response and adding coverage for the failure if the relevant test location can be found.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, go
Domain
ci-cd, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.