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
When using error extensions, I should be able to implement the ErrorExtensions trait for my errors and then call error.extend() inside resolvers. When querying a field that returns an error, I should be able to see the error along with the code and other custom fields I may add
Actual Behavior
The program crashes when calling the graphql endpoint. Here is the stacktrace
thread 'actix-rt|system:0|arbiter:0' has overflowed its stack
fatal runtime error: stack overflow
Steps to Reproduce the Problem
Run the error-extensions example contained in the examples folder
Call the extend query on the schema
The server crashes
Basically the code goes in a loop on this line, and then ultimately crashes
Specifications
Version: Reproduced with the branches actix-web-v4-beta and master
Platform:
Subsystem:
The text was updated successfully, but these errors were encountered:
Expected Behavior
When using error extensions, I should be able to implement the
ErrorExtensions
trait for my errors and then callerror.extend()
inside resolvers. When querying a field that returns an error, I should be able to see the error along with thecode
and other custom fields I may addActual Behavior
The program crashes when calling the graphql endpoint. Here is the stacktrace
Steps to Reproduce the Problem
error-extensions
example contained in the examples folderextend
query on the schemaBasically the code goes in a loop on this line, and then ultimately crashes
Specifications
actix-web-v4-beta
andmaster
The text was updated successfully, but these errors were encountered: