-
Notifications
You must be signed in to change notification settings - Fork 310
Defer remote components to avoid OkHttp class-loading side-effects #8131
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 1 commit
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
92ca151
Additional logging to help triage custom log-manager / jmx-builder te…
mcculls 40c7583
Move SharedCommunicationObjects creation to InstallDatadogTracerCallb…
mcculls 84d2b6d
Add ability to pause remote components until SharedCommunicationObjec…
mcculls 9b97d7a
Delay starting trace-writer and data-stream-monitoring until remote I…
mcculls 2cdc507
Delay starting logs-intake backend until remote I/O is allowed
mcculls 9a09d98
Install tracer and logs-intake as soon as necessary, but defer any re…
mcculls 9ee929b
Remove exemption where we didn't defer if the custom logging manager
mcculls c9cf18f
Adjust minimumBranchCoverage to account for new double-checked lock i…
mcculls File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
<
10000
/div>
Diff view
Diff view
Prev
Previous commit
Adjust minimumBranchCoverage to account for new double-checked lock i…
…n SharedCommunicationObjects
- Loading branch information
commit c9cf18f1498cbb46fd0f75961ef70d9d85fdfdb0
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
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.
Is the whole module not testable or it the cost too high?
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.
It's the double-checked lock that tips things over - attempting to cover all the cases for this piece of code would be very intensive (you'd end up testing the narrow volatile visibility edge.) There are other branches in
SharedCommunicationObjects
which are not currently tested which is why we're at this boundary to begin with, but adding tests for those unrelated pieces of code in this PR is IMHO confusing for future reviewers.I could just exclude
SharedCommunicationObjects
from branch coverage completely, but that feels worse - it's already excluded from instrumentation coverage - so reducing the coverage requirement here by a small amount is the least worst option.The proper solution is to add tests to increase coverage in a separate PR, as a separate work item.