Numerous logs coming from opentelemetry:http: superfluous response.WriteHeader call from go.opentelemetry.io

[ytimocin]

Steps to reproduce

I have been seeing these warnings in the UCP logs:

Observed behavior

One of the logs:

2024/11/03 14:06:52 http: superfluous response.WriteHeader call from go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp/internal/request.(*RespWriterWrapper).writeHeader (resp_writer_wrapper.go:78)

Desired behavior

Not seeing these warning messages

Workaround

No response

rad Version

RELEASE VERSION BICEP COMMIT
0.38.0 v0.38.0 0.30.3 cf376db

Operating system

macOS Apple M1 Pro Sequoia 15.1

Additional context

Probably related: open-telemetry/opentelemetry-go-contrib#6053

Would you like to support us?

• Yes, I would like to support you

AB#13573

[radius-triage-bot]

👋 @ytimocin Thanks for filing this bug report.

A project maintainer will review this report and get back to you soon. If you'd like immediate help troubleshooting, please visit our Discord server.

For more information on our triage process please visit our triage overview

[radius-triage-bot]

👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

[radius-triage-bot]

👋 @ytimocin Thanks for filing this issue.

A project maintainer will review this issue and get back to you soon.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

[ytimocin]

Dear future contributor,
This may have been fixed by a dependabot PR.
Thanks.

[rynowak]

I hope so. I investigated this too, and found that it's already been fixed upstream. The fix is in a dependency-of-a-dependency so we haven't picked it up yet.