74 lines
8.9 KiB
Plaintext
74 lines
8.9 KiB
Plaintext
INFO: Will watch for changes in these directories: ['F:\\SOFT\\MNOTE\\wolai-backend']
|
|
INFO: Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit)
|
|
INFO: Started reloader process [26764] using WatchFiles
|
|
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
|
|
⚠ Warning: Next.js inferred your workspace root, but it may not be correct.
|
|
We detected multiple lockfiles and selected the directory of F:\SOFT\MNOTE\pnpm-lock.yaml as the root directory.
|
|
To silence this warning, set `turbopack.root` in your Next.js config, or consider removing one of the lockfiles if it's not needed.
|
|
See https://nextjs.org/docs/app/api-reference/config/next-config-js/turbopack#root-directory for more information.
|
|
Detected additional lockfiles:
|
|
* F:\SOFT\MNOTE\wolai-frontend\pnpm-lock.yaml
|
|
|
|
[2025-12-27 22:47:28,531: WARNING/MainProcess] C:\Users\liaib\AppData\Roaming\Python\Python38\site-packages\celery\worker\consumer\consumer.py:508: CPendingDeprecationWarning: The broker_connection_retry configuration setting will no longer determine
|
|
whether broker connection retries are made during startup in Celery 6.0 and above.
|
|
If you wish to retain the existing behavior for retrying connections on startup,
|
|
you should set broker_connection_retry_on_startup to True.
|
|
warnings.warn(
|
|
|
|
[2025-12-27 22:47:28,567: INFO/MainProcess] Connected to redis://localhost:6379/0
|
|
[2025-12-27 22:47:28,570: WARNING/MainProcess] C:\Users\liaib\AppData\Roaming\Python\Python38\site-packages\celery\worker\consumer\consumer.py:508: CPendingDeprecationWarning: The broker_connection_retry configuration setting will no longer determine
|
|
whether broker connection retries are made during startup in Celery 6.0 and above.
|
|
If you wish to retain the existing behavior for retrying connections on startup,
|
|
you should set broker_connection_retry_on_startup to True.
|
|
warnings.warn(
|
|
|
|
[2025-12-27 22:47:28,578: INFO/MainProcess] mingle: searching for neighbors
|
|
[2025-12-27 22:47:29,652: INFO/MainProcess] mingle: all alone
|
|
[2025-12-27 22:47:29,721: INFO/MainProcess] celery@LIX ready.
|
|
INFO: Started server process [25896]
|
|
INFO: Waiting for application startup.
|
|
INFO: Application startup complete.
|
|
[2025-12-27 22:47:31,536: INFO/SpawnPoolWorker-1] child process 27416 calling self.run()
|
|
[2025-12-27 22:47:31,680: INFO/SpawnPoolWorker-2] child process 10168 calling self.run()
|
|
[2025-12-27 22:47:31,778: INFO/SpawnPoolWorker-4] child process 16672 calling self.run()
|
|
[2025-12-27 22:47:31,802: INFO/SpawnPoolWorker-3] child process 18588 calling self.run()
|
|
[2025-12-27 22:47:31,897: INFO/SpawnPoolWorker-6] child process 27992 calling self.run()
|
|
[2025-12-27 22:47:31,985: INFO/SpawnPoolWorker-5] child process 14316 calling self.run()
|
|
[2025-12-27 22:47:31,986: INFO/SpawnPoolWorker-7] child process 28396 calling self.run()
|
|
[2025-12-27 22:47:31,999: INFO/SpawnPoolWorker-8] child process 1396 calling self.run()
|
|
[2025-12-27 22:47:32,014: INFO/SpawnPoolWorker-10] child process 21240 calling self.run()
|
|
[2025-12-27 22:47:32,117: INFO/SpawnPoolWorker-11] child process 27396 calling self.run()
|
|
[2025-12-27 22:47:32,135: INFO/SpawnPoolWorker-12] child process 12748 calling self.run()
|
|
[2025-12-27 22:47:32,160: INFO/SpawnPoolWorker-14] child process 24500 calling self.run()
|
|
[2025-12-27 22:47:32,167: INFO/SpawnPoolWorker-16] child process 26204 calling self.run()
|
|
[2025-12-27 22:47:32,171: INFO/SpawnPoolWorker-9] child process 20484 calling self.run()
|
|
[2025-12-27 22:47:32,177: INFO/SpawnPoolWorker-13] child process 15704 calling self.run()
|
|
[2025-12-27 22:47:32,230: INFO/SpawnPoolWorker-18] child process 23508 calling self.run()
|
|
[2025-12-27 22:47:32,230: INFO/SpawnPoolWorker-15] child process 8340 calling self.run()
|
|
[2025-12-27 22:47:32,234: INFO/SpawnPoolWorker-17] child process 26884 calling self.run()
|
|
[2025-12-27 22:47:32,266: INFO/SpawnPoolWorker-20] child process 10120 calling self.run()
|
|
[2025-12-27 22:47:32,308: INFO/SpawnPoolWorker-22] child process 16744 calling self.run()
|
|
[2025-12-27 22:47:32,333: INFO/SpawnPoolWorker-19] child process 27164 calling self.run()
|
|
[2025-12-27 22:47:32,350: INFO/SpawnPoolWorker-24] child process 16536 calling self.run()
|
|
[2025-12-27 22:47:32,359: INFO/SpawnPoolWorker-21] child process 22232 calling self.run()
|
|
[2025-12-27 22:47:32,374: INFO/SpawnPoolWorker-23] child process 21236 calling self.run()
|
|
Using the user object as returned from supabase.auth.getSession() or from some supabase.auth.onAuthStateChange() events could be insecure! This value comes directly from the storage medium (usually cookies on the server) and may not be authentic. Use supabase.auth.getUser() instead which authenticates the data by contacting the Supabase Auth server.
|
|
Using the user object as returned from supabase.auth.getSession() or from some supabase.auth.onAuthStateChange() events could be insecure! This value comes directly from the storage medium (usually cookies on the server) and may not be authentic. Use supabase.auth.getUser() instead which authenticates the data by contacting the Supabase Auth server.
|
|
Yjs was already imported. This breaks constructor checks and will lead to issues! - https://github.com/yjs/yjs/issues/438
|
|
Using the user object as returned from supabase.auth.getSession() or from some supabase.auth.onAuthStateChange() events could be insecure! This value comes directly from the storage medium (usually cookies on the server) and may not be authentic. Use supabase.auth.getUser() instead which authenticates the data by contacting the Supabase Auth server.
|
|
Yjs was already imported. This breaks constructor checks and will lead to issues! - https://github.com/yjs/yjs/issues/438
|
|
Using the user object as returned from supabase.auth.getSession() or from some supabase.auth.onAuthStateChange() events could be insecure! This value comes directly from the storage medium (usually cookies on the server) and may not be authentic. Use supabase.auth.getUser() instead which authenticates the data by contacting the Supabase Auth server.
|
|
Yjs was already imported. This breaks constructor checks and will lead to issues! - https://github.com/yjs/yjs/issues/438
|
|
Using the user object as returned from supabase.auth.getSession() or from some supabase.auth.onAuthStateChange() events could be insecure! This value comes directly from the storage medium (usually cookies on the server) and may not be authentic. Use supabase.auth.getUser() instead which authenticates the data by contacting the Supabase Auth server.
|
|
Yjs was already imported. This breaks constructor checks and will lead to issues! - https://github.com/yjs/yjs/issues/438
|
|
Using the user object as returned from supabase.auth.getSession() or from some supabase.auth.onAuthStateChange() events could be insecure! This value comes directly from the storage medium (usually cookies on the server) and may not be authentic. Use supabase.auth.getUser() instead which authenticates the data by contacting the Supabase Auth server.
|
|
Yjs was already imported. This breaks constructor checks and will lead to issues! - https://github.com/yjs/yjs/issues/438
|
|
Using the user object as returned from supabase.auth.getSession() or from some supabase.auth.onAuthStateChange() events could be insecure! This value comes directly from the storage medium (usually cookies on the server) and may not be authentic. Use supabase.auth.getUser() instead which authenticates the data by contacting the Supabase Auth server.
|
|
Yjs was already imported. This breaks constructor checks and will lead to issues! - https://github.com/yjs/yjs/issues/438
|
|
Using the user object as returned from supabase.auth.getSession() or from some supabase.auth.onAuthStateChange() events could be insecure! This value comes directly from the storage medium (usually cookies on the server) and may not be authentic. Use supabase.auth.getUser() instead which authenticates the data by contacting the Supabase Auth server.
|
|
Yjs was already imported. This breaks constructor checks and will lead to issues! - https://github.com/yjs/yjs/issues/438
|
|
Using the user object as returned from supabase.auth.getSession() or from some supabase.auth.onAuthStateChange() events could be insecure! This value comes directly from the storage medium (usually cookies on the server) and may not be authentic. Use supabase.auth.getUser() instead which authenticates the data by contacting the Supabase Auth server.
|
|
Yjs was already imported. This breaks constructor checks and will lead to issues! - https://github.com/yjs/yjs/issues/438
|
|
Using the user object as returned from supabase.auth.getSession() or from some supabase.auth.onAuthStateChange() events could be insecure! This value comes directly from the storage medium (usually cookies on the server) and may not be authentic. Use supabase.auth.getUser() instead which authenticates the data by contacting the Supabase Auth server.
|
|
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
|