You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Null assertion error when a null Locale is set into Validation code #2907
Yeah the problem here is the locale is indeed nul..
ExecutionInput was indeed changed to default it during its builder private Locale locale = Locale.getDefault(); but its possible for a caller to have set it to null (perhaps through calling some other method like customCode.getLocale() returning null.
We need to default this at the call site.
As a work around until this gets fixed, people seeing this should ensure that a non null Locale is set into their ExecutionInput
changed the title [-]unclear breaking change in 19.0 update[/-][+]Null assertion error when a null Locale is set into Validation code[/+]on Aug 1, 2022
Activity
softprops commentedon Aug 1, 2022
I think the problem lie here with
executionInput.getLocale()which may be nullgraphql-java/src/main/java/graphql/GraphQL.java
Line 628 in 35ff68d
passing that along up the chain off calls will eventually nullable to the the runtime error
assertNotNull(locale);emitsbbakerman commentedon Aug 1, 2022
Yeah the problem here is the locale is indeed nul..
ExecutionInputwas indeed changed to default it during its builderprivate Locale locale = Locale.getDefault();but its possible for a caller to have set it to null (perhaps through calling some other method likecustomCode.getLocale()returning null.We need to default this at the call site.
As a work around until this gets fixed, people seeing this should ensure that a non null
Localeis set into theirExecutionInput[-]unclear breaking change in 19.0 update[/-][+]Null assertion error when a null Locale is set into Validation code[/+]