Skip to content

fix: replay an active topic ban without promoting recovery - #145

Merged
LIghtJUNction merged 3 commits into
mainfrom
fix/topic-ban-apply-20260928
Sep 29, 2026
Merged

LIghtJUNction merged 3 commits into
mainfrom
fix/topic-ban-apply-20260928

Conversation

@LIghtJUNction

Copy link
Copy Markdown
Contributor

Summary

Test plan

  • CI 跑 tests/test_task_a_recovery_checkpoint.py:apply 与 lift 分别作用在不同话题上,第二次重放 changed == 0,promotion 仍为 blocked。

Made with Cursor

A restored database can omit a ban that the pinned log still requires. Record that ban locally, keep lift deny-only, and state why promotion stays blocked.

Co-authored-by: Cursor <cursoragent@cursor.com>
Copilot AI lite review requested due to automatic review settings September 28, 2026 15:03

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
🔒 Security Review ✅ Completed 2026-09-28T15:08:29.251662Z f87ea8c PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

LIghtJUNction and others added 2 commits September 28, 2026 23:33
The one_root index allows only one parentless resource, so a second root topic made the topic_ban.apply fixture fail with constraint_conflict on PostgreSQL.

Co-authored-by: Cursor <cursoragent@cursor.com>
The published 0.x line is a different series. This source version does not claim a PyPI release or a finished production migration.

Co-authored-by: Cursor <cursoragent@cursor.com>
@LIghtJUNction
LIghtJUNction changed the base branch from fix/capacity-recovery-20260928 to main September 28, 2026 18:29
@LIghtJUNction
LIghtJUNction merged commit 4bfeece into main Sep 29, 2026
11 checks passed
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.

2 participants