hailin 416867b1d5 fix(deploy): delete Debezium connector offsets during full-reset ... This fixes an issue where Debezium would skip initial snapshot after full-reset because the connector offset persisted in Kafka Connect's internal connect-offsets topic. The fix adds two strategies to delete connector offsets: 1. REST API method (Kafka Connect 3.6+): DELETE /connectors/<name>/offsets 2. Tombstone method (Kafka Connect 3.5-): Send NULL messages via kafkacat Reference: https://debezium.io/documentation/faq/#how_to_remove_committed_offsets_for_a_connector Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>		2026-01-12 23:17:45 -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): delete Debezium connector offsets during full-reset	2026-01-12 23:17:45 -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