-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
Potential timezone related bugs caused by gotime.Local
location
#13626
Labels
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
severity/major
sig/sql-infra
SIG: SQL Infra
type/bug
The issue is confirmed as a bug.
Comments
bb7133
added
type/bug
The issue is confirmed as a bug.
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
labels
Nov 20, 2019
I am working on it. |
Thanks! @Rustin-Liu |
This was referenced Nov 26, 2019
This was referenced Nov 28, 2019
@bb7133 can we close this issue? |
Please edit this comment or add a new comment to complete the following informationNot a bug
Duplicate bug
BugNote: Make Sure that 'component', and 'severity' labels are added 1. Root Cause Analysis (RCA) (optional)2. Symptom (optional)3. All Trigger Conditions (optional)4. Workaround (optional)5. Affected versions6. Fixed versions |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
severity/major
sig/sql-infra
SIG: SQL Infra
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
When dealing with timestamps, currently there are several pieces of codes that used
gotime.Local
as the timezone location rather than system/global/session variables, which may lead to unexpected errors:tidb/types/mytime.go
Line 79 in 61f24d2
tidb/types/time.go
Line 433 in 61f24d2
...
For example, "Invalid time format" caused by time zone issue #13605 is a bug caused by such codes, we should try to avoid using
gotime.Local
to prevent such errors.tidb-server -V
or runselect tidb_version();
on TiDB)?Such codes exist in all TiDB versions.
The text was updated successfully, but these errors were encountered: