-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
The timestamp was forcibly changed. Procedure #4494
Comments
2024-05-11 20:30:40,636 - uvicorn.error - INFO - Uvicorn running on http://10.132.62.2:8000 (Press CTRL+C to quit) |
hello @Dapeng960208, can you please clarify what's the expected behaviour vs. the behaviour you observe? it's not very clear what you are trying to achieve. |
To reproduce
quest_db_url = f'questdb://{user}:{password}@{host}:{port}/qdb?timezone=UTC%2B8'
create_engine(quest_db_url, pool_pre_ping=True)As soon as I link to quest db through this code, my local time locale is implemented, forced to utc, and in fastapi, all subsequent times become utc
2024-05-11 **15:30:39,592** - uvicorn.access - INFO - 10.132.49.248:56978 - "OPTIONS /lsf/api/clusters/1/resource?start_time=2024-05-10+15:32:00&end_time=2024-05-11+15:32:00 HTTP/1.0" 200 2024-05-11 **07:30:40,088** - uvicorn.access - INFO - 10.132.49.248:56980 - "GET /lsf/api/clusters/1/resource?start_time=2024-05-10+15:32:00&end_time=2024-05-11+15:32:00 HTTP/1.0" 200 2024-05-11 **07:30:46,709** - uvicorn.access - INFO - 10.132.49.248:56982 - "GET /lsf/api/clusters/1/summary HTTP/1.0" 200
This problem affects the time zone Settings of my entire system, how can I solve this problem, I use the recommended sqlachemy for connection
QuestDB version:
7.3.5
OS, in case of Docker specify Docker and the Host OS:
rehat 7
File System, in case of Docker specify Host File System:
无
Full Name:
dapeng
Affiliation:
1332606303@qq.com
Have you followed Linux, MacOs kernel configuration steps to increase Maximum open files and Maximum virtual memory areas limit?
Additional context
No response
The text was updated successfully, but these errors were encountered: