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
Currently the server is calling many requests when build in production environment using Docker, it only happens in GET Method
I tried running Dev mode on the server, everything is fine, and I only get this issue when I build with Docker
Even the built-in function of blitzjs when creating a new project, getCurrentUser() has the same problem.
Yes, it looks like it. I think this issue is not related to refetchInterval, but the result (infinite requests) is the same. Also, for you it's not related to Docker, right?
What is the problem?
Currently the server is calling many requests when build in production environment using Docker, it only happens in GET Method
I tried running Dev mode on the server, everything is fine, and I only get this issue when I build with Docker
Even the built-in function of blitzjs when creating a new project, getCurrentUser() has the same problem.
https://www.youtube.com/watch?v=T9SWNtQm_v0
Paste all your error logs here:
Paste all relevant code snippets here:
What are detailed steps to reproduce this?
Run
blitz -v
and paste the output here:inux 5.4 | linux-x64 | Node: v14.18.2
blitz: 0.45.4 (global)
blitz: 0.45.4 (local)
Package manager: yarn
System:
OS: Linux 5.4 Ubuntu 20.04.4 LTS (Focal Fossa)
CPU: (4) x64 Intel Xeon E312xx (Sandy Bridge, IBRS update)
Memory: 1.49 GB / 7.23 GB
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 14.18.2 - /usr/local/bin/node
Yarn: 1.22.19 - /usr/bin/yarn
npm: 8.11.0 - /usr/local/bin/npm
Watchman: Not Found
npmPackages:
@prisma/client: 3.15.1 => 3.15.1
blitz: 0.45.4 => 0.45.4
prisma: 3.15.1 => 3.15.1
react: 18.0.0 => 18.0.0
react-dom: 18.0.0 => 18.0.0
typescript: ~4.5 => 4.5.5
PASTE_HERE (leave the ``` marks)
Please include below any other applicable logs and screenshots that show your problem:
No response
The text was updated successfully, but these errors were encountered: