-
Notifications
You must be signed in to change notification settings - Fork 289
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
Some bugs when TiCDC setting the timezone #8798
Labels
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-7.1
This bug affects the 7.1.x(LTS) versions.
area/ticdc
Issues or PRs related to TiCDC.
severity/moderate
type/bug
The issue is confirmed as a bug.
Comments
Rustin170506
added
type/bug
The issue is confirmed as a bug.
area/ticdc
Issues or PRs related to TiCDC.
labels
Apr 17, 2023
Rustin170506
added
severity/moderate
needs-cherry-pick-release-6.5
Should cherry pick this PR to release-6.5 branch.
labels
Apr 17, 2023
Rustin170506
added
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-7.1
This bug affects the 7.1.x(LTS) versions.
and removed
needs-cherry-pick-release-6.5
Should cherry pick this PR to release-6.5 branch.
labels
Apr 21, 2023
ti-chi-bot
pushed a commit
that referenced
this issue
Apr 21, 2023
This was referenced Apr 21, 2023
/close |
@nongfushanquan: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
16 tasks
17 tasks
17 tasks
This was referenced Jun 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-7.1
This bug affects the 7.1.x(LTS) versions.
area/ticdc
Issues or PRs related to TiCDC.
severity/moderate
type/bug
The issue is confirmed as a bug.
What did you do?
Set the timezone to TiCDC server and sink-uri. How does TiCDC set the time zone internally?
What did you expect to see?
TiCDC uses timezone correctly.
What did you see instead?
Versions of the cluster
TiCDC version (execute
cdc version
):v6.5.1
The text was updated successfully, but these errors were encountered: