blitz icon indicating copy to clipboard operation
blitz copied to clipboard

Call many requests when build in production env using Docker

Open linhltn opened this issue 1 year ago • 3 comments

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_HERE (leave the ``` marks)

Paste all relevant code snippets here:

PASTE_HERE (leave the ``` marks)

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

linhltn avatar Jul 25 '22 09:07 linhltn

@beerose https://github.com/blitz-js/blitz/issues/3595 Seems to be the same problem?

StringKe avatar Jul 27 '22 07:07 StringKe

@beerose #3595 Seems to be 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?

beerose avatar Jul 28 '22 15:07 beerose

I need help @beerose 🆘

linhltn avatar Aug 02 '22 01:08 linhltn

same issue in production when you run it in port 3000 (not 80)

cesarve77 avatar Oct 17 '23 08:10 cesarve77