Subtle incompatibilities between graphql-java version 20.x and 21.x

[svametcalf]

Greetings! First off, thanks for the great library!

We ran into a strange bug when upgrading to version 3.2.x of Spring Boot this week. Upgrading from 3.1.8 to 3.2.0 broke our exception resolution for Subscription types. With the upgrade, our previously working SubscriptionExceptionResolver was not being called and subscription exceptions were just being adapted to the generic error message "Subscription error".

I was unable to create a minimal reproducible case with a simple schema / service setup, because the error did not present itself. You can see my attempt to repro the error here: https://github.com/svametcalf/gql-subscription-exceptions-debug.

After some more debugging of our production code, it became apparent that a ContextDataFetcherDecorator was not being registered as the DataLoader for each Subscription type using Spring 3.2.x (and version 21.x of graphql-java). Downgrading the version of graphql-java to 20.x solved the issue for us.

Therefore, it seems that there might be some incompatibilities between the schema traversal mechanism in v20.x and v21.x of graphql-java which may be causing issues for other users.

Unfortunately our schema is quite large and would be hard to debug against but if you have any suggestions for what I can try to make a more minimal repro case, I am happy to help get to the bottom of this issue.

[bclozel]

Hello @svametcalf !

This is a duplicate of #861. For now (and until the next maintenance release), downgrading graphql-java is the easiest workaround.

I'd like to check that your sample works with the latest snapshot before really closing this issue as a duplicate.

[spring-projects-issues]

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

[spring-projects-issues]

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.