Conversation
…me-type conversion bug The SQL Server connector IT tests used 10:23:45 as test data for val_time_p2 (time(2)) and val_time (time(4)). When CI runs with a random JVM timezone (e.g. GMT+11 or GMT+12), Debezium 1.9.8.Final's CDC change-log reader interprets the time value with the timezone offset, producing a negative epoch. This causes a DateTimeException (Invalid value for NanoOfSecond) and silent data loss (time values become null). Shift the test time values from 10:23:45 to 15:23:45 so that even with the maximum possible positive timezone offset (GMT+12), the resulting epoch remains positive and Debezium's conversion succeeds.
yuxiqian
force-pushed
the
hotfix/flaky-ut
branch
from
September 17, 2026 08:19
4688c40 to
c2ee9ec
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the purpose of this pull request?
The SQL Server connector IT tests used 2018-07-13 10:23:45 as test data. When CI runs with a random JVM timezone (e.g. GMT+11 or GMT+12), Debezium 1.9.8.Final's CDC change-log reader interprets the time value with the timezone offset, producing a negative epoch. This causes a DateTimeException (Invalid value for NanoOfSecond) and silent data loss (time values become null).
Brief change log
Shift the test date to 2000-01-01 and the time to 15:23:45 so that even with the maximum possible positive timezone offset (GMT+12), the resulting epoch remains positive and Debezium's conversion succeeds.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Documentation
Was generative AI tooling used to co-author this PR?
Generated-by: ChatGPT (GPT-5 Codex)