Skip to content

Conversation

@tinnou
Copy link
Contributor

@tinnou tinnou commented Sep 19, 2018

Naïve attempt to fix #1233. The idea is to release the lock on callstack (in FieldLevelTrackingApproach) before executing the actual dispatch so children threads don’t get blocked.

@andimarek andimarek added the Not to be merged spikes or other stuff that should never or not yet to be merged label Oct 1, 2018
bbakerman added a commit to bbakerman/graphql-java that referenced this pull request Oct 2, 2018
@andimarek
Copy link
Member

closing this in favour of #1255.

@andimarek andimarek closed this Oct 3, 2018
bbakerman added a commit that referenced this pull request Oct 3, 2018
* Added @OverRide as part of errorprone code health check

* Revert "Added @OverRide as part of errorprone code health check"

This reverts commit 38dfab1

* Brads attempt at #1234

* Missed the test
bbakerman added a commit to bbakerman/graphql-java that referenced this pull request Oct 3, 2018
* Added @OverRide as part of errorprone code health check

* Revert "Added @OverRide as part of errorprone code health check"

This reverts commit 38dfab1

* Brads attempt at graphql-java#1234

* Missed the test
bbakerman added a commit that referenced this pull request Oct 3, 2018
* Added @OverRide as part of errorprone code health check

* Revert "Added @OverRide as part of errorprone code health check"

This reverts commit 38dfab1

* Brads attempt at #1234

* Missed the test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Not to be merged spikes or other stuff that should never or not yet to be merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Deadlock in FieldLevelTrackingApproach

2 participants