test(repro): reproduce partition catch-all collision and missing deletion audit entries - #1
Open
frodoHost wants to merge 2 commits into
Open
test(repro): reproduce partition catch-all collision and missing deletion audit entries#1frodoHost wants to merge 2 commits into
frodoHost wants to merge 2 commits into
Conversation
added 2 commits
July 31, 2026 23:07
…tion audit entries
Two new #[ignore = "requires Postgres"] integration tests, wired into the
existing Backend Integration CI job against its own ephemeral Postgres/Redis:
- buzz-db::partition::tests::current_month_partition_is_never_created_once_a_future_catchall_exists
schema/schema.sql and migrations/0001_initial_schema.sql both hardcode
monthly partitions only through 2026-06, then attach events_p_future /
delivery_log_p_future FROM ('2026-07-01') TO (MAXVALUE). Confirms
ensure_future_partitions neither creates a dedicated partition for the
current month nor surfaces any error once that catch-all exists.
- buzz-relay::handlers::event::tests::pubsub_fanout::standard_deletion_writes_no_audit_entry
Dispatches a real signed kind:5 NIP-09 deletion through handle_side_effects
(the same entry point handlers/ingest.rs uses in production), confirms the
target is genuinely soft-deleted, and asserts no 'event_deleted' row lands
in audit_log -- while the same event's creation, audited moments earlier in
the same test run, does.
Reproduction only, not a fix. Neither test's failure mode is expected to
change existing behavior; they exist to give the corresponding bug reports
CI evidence from a real build, isolated from any production deployment.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reproduction only, not a fix. Two new #[ignore = "requires Postgres"] tests wired into the existing Backend Integration CI job:
current_month_partition_is_never_created_once_a_future_catchall_exists(buzz-db)standard_deletion_writes_no_audit_entry(buzz-relay)Opened against this fork's own main purely to trigger Actions in isolation -- not intended for upstream block/buzz.