The GitHub Actions job "CI" on rocketmq-dashboard.git/codex/reservation-stamps-creation-time has succeeded. Run started by GitHub user iloveeyjafjalla (triggered by iloveeyjafjalla).
Head commit for run: dc87d8c2af54b781c21a5775abf28289f41ada48 / iloveeyjafjalla <[email protected]> fix(instance): stamp the ownership reservation's bookkeeping columns The reservation INSERT of ResourceOwnershipGuard named neither gmt_create nor gmt_modified, so those columns fell back to the schema's DEFAULT CURRENT_TIMESTAMP - the database's clock - while the create path stamps gmt_modified from the JVM clock. Because the guard always reserves the row before the provider writes it, isNew in RocketMQAdminClientImpl is false for a studio-created topic or group, so the creation time stays on the database clock for the whole life of the row and a single row reports two clocks: with the database in UTC and the studio in Asia/Shanghai, gmt_create was eight hours behind its own gmt_modified, and the console (which renders both in the viewer's zone) showed a creation time hours before the resource existed. Stamp both columns from the studio clock the update path already uses, so one row can never mix clocks regardless of the database's zone. Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/38736011697 With regards, GitHub Actions via GitBox
