-
Notifications
You must be signed in to change notification settings - Fork 20
chore(deps): bump libdatadog to 48da0d8 for client-computed header fix
#1244
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
Open
lucaspimentel
wants to merge
3
commits into
main
Choose a base branch
from
lpimentel/bump-libdatadog-client-computed-headers
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+171
−54
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
dce5658
chore(deps): bump libdatadog to 48da0d8 for client-computed header fix
lucaspimentel 149ba09
test(traces): add Tier 0 client-computed header-parsing coverage for …
lucaspimentel 7c77ad6
docs(traces): clarify isHeaderTrue parsing rule in test module comment
lucaspimentel 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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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.
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.
Shouldn't this live then either in test or with the test feature so its not included in prod code?
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.
The libdatadog version bump made
SendData::sendrequireHttpClientCapability+SleepCapability, and bottlecap callssend, so the binary won't compile without it.The
// never invoked on bottlecap's code pathscomment only applies to thenew()constructor. It's trait-required factory we never call, same asnew_client()onHttpClientCapabilityabove. Thesleep()method itself is used in production: libdatadog's sender calls it for retry/backoff between send attempts.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.
mmm, and so we're getting that new capability which might not be something we want for lambda lifecycle no?
Uh oh!
There was an error while loading. Please reload this page.
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.
The retry/backoff isn't new with this bump.
send_with_retryalready existed at the previous revision and bottlecap already goes through it. Bottlecap configures its own strategy intrace_flusher.rs(trace_retry_strategy(): 3 retries, 0ms delay, constant backoff), so we're already opted in explicitly.SleepCapabilityonly changed how libdatadog reaches the sleep primitive: the request timeout went fromtokio::time::timeout(...)to aselect!race againstcapabilities.sleep(timeout), which is the sametokio::time::sleepunderneath on our target. Same runtime behavior, no new waiting in the Lambda lifecycle.🤖