-
Notifications
You must be signed in to change notification settings - Fork 17
fix: oversize payload causing universal instrumentation failures #1067
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
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
a64bb1c
add test to show the issue
joeyzhao2018 11cef1d
Fix handle_end_invocation dropping processing on oversized payloads
joeyzhao2018 0764c83
solving merge conflict
joeyzhao2018 7d6b284
cargo fmt
joeyzhao2018 87f7e17
refactor
joeyzhao2018 e9abece
cargo fmt
joeyzhao2018 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So if you're using extract_request_body_or_empty, what's going on with
extract_request_body? Is that ever used again? Do we need to update this new behavior in previous usages or?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there are a few other usages for
extract_request_bodydatadog-lambda-extension/bottlecap/src/extension/telemetry/listener.rs
Line 97 in dda9b26
datadog-lambda-extension/bottlecap/src/otlp/agent.rs
Line 144 in dda9b26
datadog-lambda-extension/bottlecap/src/traces/stats_processor.rs
Line 45 in dda9b26
datadog-lambda-extension/bottlecap/src/traces/trace_agent.rs
Line 479 in dda9b26
datadog-lambda-extension/bottlecap/src/traces/trace_agent.rs
Line 659 in dda9b26
I actually don't have enough background knowledge to say if those cases can follow the same pattern...Do you think we should make all of them just log the error and accept empty body?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, fair enough, let's keep it as is for this one and let the other ones handle it as they expect it