Skip to content

Use Beijing time and Snowflake IDs - #2

Draft
369pro wants to merge 9 commits into
mainfrom
feat/beijing-time-snowflake-id
Draft

Use Beijing time and Snowflake IDs#2
369pro wants to merge 9 commits into
mainfrom
feat/beijing-time-snowflake-id

Conversation

@369pro

@369pro 369pro commented Aug 16, 2026

Copy link
Copy Markdown
Owner

概要

  • MySQL 业务时间统一为北京时间 Asia/Shanghai,API/领域时间携带 +08:00
  • 新数据改用 64 位 Snowflake ID,历史 UUID 与自增 ID 原样兼容
  • 增加 0002 / 0003 迁移,覆盖关系型时间、JSON 检查点与候选人画像
  • 更新 README、规格、领域词汇与 ADR,补齐迁移和边界测试

数据安全

  • 升级前备份已验证:/tmp/interview_agent_before_snowflake_20260816_verified.sql
  • 本机 MySQL 已升级到 0003,历史会话/画像 JSON 时间抽查为 +08:00
  • 迁移不会重写历史 UUID/自增 ID
  • 破坏性 downgrade 会明确拒绝,回退需恢复升级前备份

验证

  • uv run ruff check .
  • uv run mypy src
  • uv run pytest -q → 153 passed, 16 skipped
  • 真实 MySQL 0001 → head(历史 INTEGER AUTO_INCREMENT / DATETIME 形态)→ passed
  • 数据库 Snowflake/北京时间集成测试 → passed
  • node --check src/interview_agent/web/app.js
  • 规格复审与工程标准复审 → PASS
  • /health/ready → MySQL、Redis、Milvus、Embeddings、Reranker、Speech 全部健康

完整 Dockerfile 构建仍受 Docker Hub 匿名令牌 TLS EOF 影响;已基于本地已验证镜像生成增量镜像并完成运行态验收。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant