Skip to content
This repository has been archived by the owner on Feb 3, 2021. It is now read-only.

"Accept header absent and forced to application/json" spam #608

Closed
jaley opened this issue Jun 18, 2018 · 3 comments · Fixed by #611
Closed

"Accept header absent and forced to application/json" spam #608

jaley opened this issue Jun 18, 2018 · 3 comments · Fixed by #611

Comments

@jaley
Copy link

jaley commented Jun 18, 2018

Since updating to 0.8.0, I'm getting a lot of warnings printed to stderr about a missing Accept header in the REST requests. Seems to be coming from the Azure REST API, here.

This fills up our logs on VSTS for long-running jobs.

@timotheeguerin
Copy link
Member

timotheeguerin commented Jun 18, 2018

This sounds like msrest was updated recently to this, we don't have a direct dependency on it, I guess the issue is with some of the sdk that is not specifiing the header correctly.

In the meantime you can force msrest to be at a previous version or suppress the warning

@jafreck
Copy link
Member

jafreck commented Jun 18, 2018

We already suppress warning from msrestazure, should we do the same thing for msrest?

Since the issue is arising because of a transitive dependency, we really shouldn't surface any logging I feel.

@timotheeguerin
Copy link
Member

I looked at their code and it seems like the logger name is the filename not msrest azure so I think it might be pretty hard to suppress

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants