-
Notifications
You must be signed in to change notification settings - Fork 31
Closed
Labels
bugSomething isn't workingSomething isn't workingfixedBug got fixed or found a solutionBug got fixed or found a solution
Description
The function runtime compiled using the most recent pull requests and function app version change commit no longer returns a success code of 200 to the service hook in Azure DevOps. It appears that line 83 of AzureFunctionHandler.cs is the issue:
return req.CreateResponse(HttpStatusCode.OK, execResult);
The tooltip states that if no formatter is found then CreateResponse will return 406: Not Acceptable, which is what ends up being returned to the service hook which interprets it as having failed. Changing the line as seen here fixes the issue:
return req.CreateResponse(HttpStatusCode.OK);
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingfixedBug got fixed or found a solutionBug got fixed or found a solution