Graphql-dotnet: Deadlocks starting with alpha-802

Created on 15 Dec 2017  路  4Comments  路  Source: graphql-dotnet/graphql-dotnet

I tried upgrading my app from alpha 797 to 802, and I discovered that my queries were starting to hang indefinitely. The affected fields use FuncFieldResolver returning Task.

I did some digging and I believe I've tracked down the offending commit. It appears that the resolver created in FieldMiddlewareBuilder no longer returns a task, and is calling result.Result to force synchronous execution. I tried reverting that one change against master, but apparently other code is relying on this resolver being synchronous now, and I couldn't get the tests to pass.

bug

All 4 comments

Thanks for the report, yes that seems like an issue.

Setting SetFieldMiddleware = false on your ExecutionOptions would probably be a workaround, assuming you aren't using field middleware.

Pull request #536 should also fix this issue.

I can confirm that this is fixed as of alpha 870.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

VladimirAkopyan picture VladimirAkopyan  路  4Comments

dharmeshtailor picture dharmeshtailor  路  4Comments

mahald picture mahald  路  4Comments

damithashyamantha picture damithashyamantha  路  4Comments

wendelnascimento picture wendelnascimento  路  3Comments