Weird cache regression after PR #4358
# support
p
I'm running into a bunch of 404s on GraphQL after PATCHing resources. The cause of this "404" is that frequently in the redis cache, we're putting in resources with missing projectIds, so when we query overy GQL, the API 404s the object, since it can't verify which project it came from. I dropped a debugger in the code, and it seems to be stemming from the
postCommit
callbacks. On my specific transaction, I see that there are 3 stacked
postCommit
callBacks, and on the final
callBack
,
project
becomes undefined and then we store the broken object in Redis, which ends up causing the 404. I'm not exactly sure what's causing this final callback to be missing the project, but I believe it's related to the changes in PR #4358.
Note that this isn't a problem pre-4358 (I believe!)
Just confirmed that reverting to version 3.2.10 in does solve the issue for us! (3.2.10 does not include PR 4358, but there's potentially other PRs also causing the bug here)
r
@Pavan thank you for surfacing this to us! Would you mind filing a Github issue, then our engineers can take a look
p
Will do!
148 Views