You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2026/06/27 01:02:45 UTC
[GH] (shardingsphere/fix/snowflake-utc-epoch): Workflow run "E2E - Agent" failed!
The GitHub Actions job "E2E - Agent" on shardingsphere.git/fix/snowflake-utc-epoch has failed.
Run started by GitHub user vasiliy-mikhailov (triggered by linghengqian).
Head commit for run:
0d4185fdb5f09963c454d6ab692b650c4b1ac2cb / Vasiliy Mikhailov <va...@gmail.com>
Compute the Snowflake epoch in UTC instead of the system timezone
The static EPOCH (2016-11-01 00:00:00) was converted to epoch millis using the JVM default timezone offset, so the generated key timestamps shifted with the server timezone, risking duplicate or mis-ordered keys across deployments in different zones. Use ZoneOffset.UTC so the epoch is timezone-independent.
Report URL: https://github.com/apache/shardingsphere/actions/runs/28262198883
With regards,
GitHub Actions via GitBox