Closed radekmie closed 2 years ago
I noticed the same behavior with mutations with v0.9.4. On v0.9.3 they are working. I couldn't test with v0.9.5 because it's not starting for some reason.
Did you try to run it with the variables_deduplication
option disabled ?
@bnjjj We will, thanks!
@bnjjj Nope, it doesn't change anything - it's still failing.
@bnjjj We've tried a few different configurations, and it looks like only query_deduplication
is causing problems - it works with variables_deduplication
enabled and disabled.
@radekmie do you see anything suspicious when running the router with --log debug
or --log trace
?
@Geal It's hard for me to know which log is first when a request is made, as there's so many of them, so here are two most often recurring patterns:
I could send you all of the logs (~76k lines), but I'd need an automated way to anonymize them - our Apollo key as well some IPs are there.
@radekmie we're not sure yet it would fix your issue but https://github.com/apollographql/router/pull/1350 is very probably related to it
@radekmie we just released the router v0.10, can you check if it solves your issue?
@Geal I can confirm that v0.10.0 solved the problem. Thank you for your fast response!
awesome!
Describe the bug We've switched from Apollo Gateway to Apollo Router (v0.9.5) last Friday, and everything went smoothly. We've tested it on a few most used queries (no mutations) - it looked fine.
Today we've got a few alerts, that one of the mutations is not working properly, and it returns an error. The mutation is fairly simple:
And the error was quite cryptic:
We've quickly reverted the deployment, and checked the logs. The weren't many of them:
timestamp
is different):As I've checked, making a request directly at the subgraph works, and so does the gateway - it's only the router.
To Reproduce I can reproduce it in multiple environments of ours, but haven't prepared a reproduction yet. Also, restarting the router doesn't help either.
Expected behavior No errors at all. (And a better error messasge...)
Additional context The router configuration: