hailin 2a4cb829fe fix(deploy-mining): truncate processed_cdc_events after CDC offset reset ... Problem: full-reset script resets Kafka consumer offsets but doesn't clear the processed_cdc_events table. When migrations run, containers may start and consume CDC events, inserting records into this table. After offset reset, the service restarts and detects all events as "duplicates" because the idempotency records still exist. Solution: Add TRUNCATE processed_cdc_events step after CDC offset reset in Step 8, before starting services. This ensures the idempotency table is in sync with the Kafka offset position. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>		2026-01-12 21:00:34 -08:00
..
.claude	refactor: simplify mpc-service to gateway mode	2025-12-06 17:16:14 -08:00
api-gateway	fix(kong): 修复auth-service路由配置	2026-01-11 17:52:53 -08:00
infrastructure	chore(docker): 为 mpc-system、api-gateway、infrastructure 添加时区配置	2025-12-23 18:35:09 -08:00
mpc-system	feat(blockchain): 切换到dUSDT(绿积分)合约 - KAVA主网	2026-01-02 04:31:11 -08:00
scripts	fix(scripts): 修正容器名为 rwa-blockchain-service	2025-12-15 10:34:25 -08:00
services	fix(deploy-mining): truncate processed_cdc_events after CDC offset reset	2026-01-12 21:00:34 -08:00
.env.windows	fix(referral): 修复 getMyReferralInfo 使用 userId 而不是 accountSequence 的问题	2025-12-14 05:05:03 -08:00
docker-compose.windows.yml	feat(service-party-app): implement co-sign multi-party signing	2025-12-30 18:36:11 -08:00