- Notifications
You must be signed in to change notification settings - Fork690
[DRAFT DO NOT REVIEW] Make ObserverHolder thread safe by having a thread local observer member#6882
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:develop
Are you sure you want to change the base?
Conversation
This pull requestintroduces 1 alert when merging64fe5c2 intoc68a770 -view on LGTM.com new alerts:
|
64fe5c2
to2a98a10
Compare2a98a10
to141e30f
Comparethis PR appears to be abandoned, can it be closed? |
onichols-pivotal left a comment• edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
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.
comment deleted
I would prefer not to close it yet as it is an alternative approach to#6874 as it is mentioned in the comments. |
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
Has your PR been rebased against the latest commit within the target branch (typically
develop
)?Is your initial contribution a single, squashed commit?
Does
gradlew build
run cleanly?Have you written or updated unit tests to verify your changes?
If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion underASF 2.0?