Matt DaSilva
05/21/2025, 8:01 AMdata
should be populated and errors
null), but also in unhappy path tests (when errors
should be populated by a different error)
[KotlinxGraphQLError(message=Cannot invoke "java.lang.Comparable.compareTo(Object)" because "pivot" is null, locations=null, path=null, extensions=null)].
[KotlinxGraphQLError(message=Cannot invoke "java.lang.Comparable.compareTo(Object)" because "a[runHi]" is null, locations=null, path=null, extensions=null)]
We are using the default SimpleDataFetcherExceptionHandler
1. graphql error messages should have the format "Exception while fetching data (%s) : %s", path, exception.getMessage()"
- these ones do not
2. I've added logging the exception handler. However on the occurrence of these graphql errors, nothing is logged
3. 1. and 2. suggest these errors are occurring after the error handling part of the execution strategy
Note:
• seems to occur on queries with a high number of data loaders
• occurs more on jenkins than local builds
graphqlKotlinExpediaVersion = '8.5.0'