You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Nomad version
v1.0.4 (and much before)
Issue
When headers are present on the Nomad client config, the header map from the config is assigned to the request header map in
newRequest
:https://github.com/hashicorp/nomad/blob/v1.0.4/api/api.go#L680-L682
This means that downstream usage of this header map (esp. mutation) can result in concurrent access to the map from the client config. We ran into this problem in the Nomad terraform provider:
https://travis-ci.org/github/hashicorp/terraform-provider-nomad/builds/765624353
The assignment linked above needs to be a copy, in the spirit of the initialization in
doRequest
:https://github.com/hashicorp/nomad/blob/v1.0.4/api/api.go#L657
Reproduction steps
Documenting test in #10302
The text was updated successfully, but these errors were encountered: