Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix http pipelining test on Netty 4.1 #8412

Merged
merged 1 commit into from
May 5, 2023

Conversation

laurit
Copy link
Contributor

@laurit laurit commented May 4, 2023

No description provided.

@laurit laurit requested a review from a team May 4, 2023 10:46
Copy link
Member

@trask trask left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤯 does this resolve #2496?!??

@trask
Copy link
Member

trask commented May 5, 2023

🤯 does this resolve #2496?!??

oh right #2496 is about netty client instrumentation 🤦‍♂️

this PR is still 💯

@laurit
Copy link
Contributor Author

laurit commented May 5, 2023

#2496 could probably be resolved by changing the channel attributes into queues. Request handler would push new context/request to the end of the queue and response handler would remove the first element of the queue. This should avoid new requests coming in overwriting context for the in progress request. Server instrumentation will also probably need similar queueing to work when response isn't written immediately after reading the request. You could read the requests, place them in a queue and write responses after all requests are read which would fail with current instrumentation.

@laurit laurit merged commit 0ecd146 into open-telemetry:main May 5, 2023
@laurit laurit deleted the netty41-http-pipelining branch May 5, 2023 10:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants