Open e-lobo opened 2 years ago
Thanks for the bug report @e-lobo . I thought that we might be able to avoid having to capture exceptions in futures (like promises do) but it I don't think it's avoidable. Will update here when it's working.
@jkimbo basically any error getting raised inside our dataloader throws this error instead of the actual error..
For instance say you are resolving a field as
None
and it is defined in schema asNon Null ( ! )
. Now because of the below screenshot.=> GraphQL deferred execution failed to complete Error
Upon investigating the flow of execution of SyncFuture i noticed the below
callback() here throws the error seen below
Now im not sure why SyncFuture below is in Pending State though