Repository navigation
Bound and expire custodial upgrade challenges - #125
LIghtJUNction wants to merge 1 commit into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
复核 head 我使用真实 PostgreSQL、Ed25519/age 升级流程,推进时间后单独应用本 PR 的无状态筛选清理谓词,重加密状态保留和完成结果查询两项回归均失败。当前主线已有 已在独立修复 PR #142 中保留既有保护,只回收可丢弃的 pending/failed 挑战;新增实际升级、回执查询和清理回归。没有修改本 PR 的分支。#142 原始组合本地相关回归 110 项通过,发布时主线刚合入 #119,正在对齐新主线;原补丁不宜直接合并。 |
Motivation
custodial_upgradescaused by repeated abandonedidentity.custodial_upgrade_startrequests.Description
custodial_upgrade_start, delete expired challenges for the subject, serialize concurrent starts with a no-op update, and reject a new start while a live pending challenge exists by returningcustodial_upgrade_in_progress(changes insrc/msg/plugins/identity.py).custodial_upgradesand report the number removed (changes insrc/msg/workers/maintenance.py).tests/test_custodial_upgrade.pyandtests/test_operations_admin.py).Testing
git diff --checkpassed successfully.python -m compileall(run through the project'suvhelper) completed successfully for the targeted files.ruffon touched files reported pre-existing import-order and unused-import issues unrelated to the new logic.pytestruns were attempted for the modified tests but the environment lacks PostgreSQL tools (notablyinitdb), causing test setup errors; as a result full automated test execution could not complete in this environment.Codex Task