Repository navigation
Conversation
Preserve resolved alert history and allow a recurrence to open one new alert. Batch alert bookkeeping without rewriting unchanged rows; expose resolved_at and filter active quarantines in Directus. Refs PRD-1201 Published from local commits 5b311e1, c9f9a23, and 2408391 through the GitHub connector because the environment blocks shell Git transport. The published tree exactly matches local HEAD 2408391483a9ef757b21b60d266c230601da2250.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📜 Recent review details
📝 Summary
Merge Risk: ⚪ Minimal · up to
|
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Docstring Coverage |  |
Docstring coverage is 66.67% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 15 functions across 9 files. (5 skipped: … | Write docstrings for the functions missing them to satisfy the coverage threshold. |
-
Check name Status Explanation Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Description check The description directly explains the snapshot alert episode changes, migration 030, alert reconciliation, Directus updates, validation, and release requirements. Title check The title clearly and concisely describes the primary change: alerts now fire once per snapshot episode and can recur after resolution.
Full details: Docstring Coverage
-
Explanation
Docstring coverage is 66.67% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 15 functions across 9 files. (5 skipped: 5 unsupported.)
- Fix all pre-merge checks with AI
✨ Finishing Touches 💡 1
-
📝 Generate docstrings 💡
-
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Warning
MCP server "posthog" is unavailable: the server marks every selected tool as able to make changes, and CodeRabbit only uses read-only tools.
MCP server "posthog" is unavailable: the server marks every selected tool as able to make changes, and CodeRabbit only uses read-only tools.
I’m a rabbit; alerts now open when troubles appear.
A fix marks the episode resolved and clear.
If trouble returns, a new alert can begin.
The old row stays saved as a record within.
I nibble a carrot and hop past the queue.
Each snapshot checks what is missing anew.
Comment @coderabbitai help to get the list of available commands.
Oba-One
added
the
automated/codex
ChatGPT Codex Connector
Keep the current chapter image-copy scripts and operator documentation while adding the snapshot alert proof command and episode history notes.
|
@coderabbitai review |
✅ Action performedReview finished.
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Order content reads and alert changes with a transaction-scoped advisory lock. Remove the grace period so a brief observed recovery ends its episode immediately. Savepoints preserve public snapshot delivery and independent alert kinds when a queue statement fails. Refs PRD-1201
This branch has not been deployed
1 participant
Summary
A quarantined record or withheld chapter image previously alerted once per record forever. Migration 030 adds
resolved_atand scopes the existing unique indexes to open episodes, retaining notification history. A recovery resolves the episode, and a later recurrence opens one new alert.resolved_atin Directus and show only open episodes in the Quarantined records bookmark. Unchanged renders do not rewrite notification rows.Refs PRD-1201.
Validation
On the exact PR-head checkout plus these fixes:
bun run typecheckbun run test:agent— 78 agent tests and 14 moderation testsbun run test:content— 33 testsbun run build— 47 pagesbun run plans:validated5dc288f5f69082246dd16353b4eb5033f5dc3f7.The previous scratch database proof passed during implementation. The updated proof now includes immediate recurrence and deliberately overlapping Postgres renders. It has not run on the new implementation: local Postgres is unavailable, and the user requested proceeding with tests that do not need it. Live Directus field/bookmark proof also remains pending. Rendered browser proof: none.
CodeRabbit approved the preceding head
ad3c081without actionable findings. The two additional correctness defects found in our review are fixed by9bf6e9d; that approval is not evidence for the latest head.Release
The Network repository uses
mainand has nodevelopbranch. Applying migration 030, merging/deploying, and rerunning Directus setup require separate authorization. Merging tomainauto-deploys the Fly agent. After applying the migration, clear the Directus cache and rundirectus:content:setupanddirectus:studio:setup.Sensitive manifest change in the overall PR: one test script in
package.json, with no dependency or lockfile change. The review fixes change only five runtime/test/documentation files.Publication uses the connected GitHub API because shell Git transport/signing is unavailable. The isolated checkout is kept at the exact published head; the original local branch history is preserved.