Replies: 3 comments 1 reply
-
So, this code happens on this try catch, await this.cacheHandler?.set(pathname, data, ctx) So, I could speculate, that a fetch all, or data request in general, resolved to |
Beta Was this translation helpful? Give feedback.
0 replies
-
Same here, did you find something? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Unfortunately no way to reproduce the issue, however the root cause was due to a vulnerability in the next version we were using. This is the vulnerability: GHSA-gp8f-8m3g-qvj9. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
We've had an issue in production where page requests were returning stale data. Upon inspecting the logs, we noticed this error getting logged when loading the page:
We believe this error was causing our problem, however I would like to be able to reproduce this scenario locally. Does anyone know how I can trigger this error? The page in question has no server side or static props.
Many thanks in advance!
Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions