-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uvicorn-0 #9089
Comments
Have you checked all the details in the development environment guidelines? It looks like there might be an issue with |
Please, fill the issue template, providing all required details as steps to reproduce, environment and version. |
I think there is issue with uvicorn |
@Mansi08git Could you describe what the issue with the uvicorn is? |
@azhavoro after carefully review the bug, I found that uvicorn is running successfully, 304 not modifies happens when a client or user makes a request with a caching mechanism |
No issues are actually reported, let's close for now. |
Actions before raising this issue
Steps to Reproduce
i have a problem with run the command docker logs cvat_server -f
and result this:
2025-02-11 02:50:18,537 DEBG 'uvicorn-1' stderr output:
INFO: ASGI 'lifespan' protocol appears unsupported.
INFO: Application startup complete.
2025-02-11 02:50:18,538 DEBG 'uvicorn-1' stderr output:
INFO: Uvicorn running on socket /tmp/uvicorn.sock (Press CTRL+C to quit)
2025-02-11 02:50:18,551 DEBG 'uvicorn-0' stderr output:
INFO: Started server process [239]
INFO: Waiting for application startup.
2025-02-11 02:50:18,552 DEBG 'uvicorn-0' stderr output:
INFO: ASGI 'lifespan' protocol appears unsupported.
INFO: Application startup complete.
2025-02-11 02:50:18,552 DEBG 'uvicorn-0' stderr output:
INFO: Uvicorn running on socket /tmp/uvicorn.sock (Press CTRL+C to quit)
2025-02-11 02:50:24,223 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 200 OK
2025-02-11 02:50:39,109 DEBG 'uvicorn-1' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 200 OK
2025-02-11 02:50:44,747 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 200 OK
2025-02-11 02:50:55,475 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:51:01,982 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:51:16,271 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:51:31,081 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:51:40,585 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:51:50,247 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:52:02,389 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:52:14,372 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:52:26,539 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:52:33,909 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:52:40,162 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:52:52,114 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:53:00,157 DEBG 'uvicorn-1' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 200 OK
2025-02-11 02:53:05,508 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 200 OK
2025-02-11 02:53:11,413 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:53:19,740 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:53:32,238 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:53:46,399 DEBG 'uvicorn-1' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 200 OK
2025-02-11 02:53:55,208 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 200 OK
2025-02-11 02:54:07,833 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:54:17,180 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:54:29,113 DEBG 'uvicorn-1' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 200 OK
2025-02-11 02:54:38,314 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 200 OK
2025-02-11 02:54:50,221 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:55:00,745 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:55:15,147 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:55:27,412 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:55:32,492 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:55:40,971 DEBG 'uvicorn-1' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 200 OK
2025-02-11 02:55:54,344 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 200 OK
2025-02-11 02:56:07,673 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
2025-02-11 02:56:17,856 DEBG 'uvicorn-0' stdout output:
INFO: 172.18.0.6:0 - "GET /api/auth/rules HTTP/1.0" 304 Not Modified
Expected Behavior
No response
Possible Solution
No response
Context
No response
Environment
The text was updated successfully, but these errors were encountered: