Repository navigation
Enable incremental artifact reads on every relay - #8975
Merged
Merged
Conversation
Signed-off-by: Daniel Rouleau <drouleau@squareup.com>
dr0uleau
marked this pull request as ready for review
November 3, 2026 00:26
🔐 Codex Security Review
Review SummaryOverall Risk: NONE
FindingsNo concrete security, correctness, or reliability findings were identified. Notes
Generated by Codex Security Review | |
Signed-off-by: Daniel Rouleau <drouleau@squareup.com>
Signed-off-by: Daniel Rouleau <drouleau@squareup.com>
kazemek21
approved these changes
Nov 3, 2026
This branch was previously deployed
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
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.
Why
Compatible clients need incremental artifact reads for local collections on every Buzz relay.
What
Expose incremental artifact reads and capability discovery on every Buzz relay.
How
Serve incremental queries through the existing authentication and authorization checks. Keep the existing work budgets and the separate WebSocket sync capability. The HTTP test verifies capability discovery and a successful incremental query.
Risk
The relay starts no additional background work. Clients that use incremental reads consume database capacity. The net database load is not yet measured. Serving writers must maintain the modification timestamps.
Testing
Read-only SQL checks on November 3, 2026 verify the prerequisites below. Each database records successful migrations 76–78. All five required columns have the expected types, defaults, and nullability. All five indexes have the expected definitions and are valid, ready, and live.
bb-blockf6f6d9aincludes PR 8523bb-publicf3a7babincludes PR 8523bb-blockb4509deincludes PR 8523The checked columns are
artifact_heads.modified_at,artifact_revisions.modified_at,artifact_revisions.source_channel_id,channel_members.sync_modified_at, andcommunities.artifact_policy_modified_at. The checked indexes areidx_artifact_revisions_artifact,artifact_heads_modified,artifact_heads_channel,channel_members_sync, andartifact_revisions_moves.At commit
62b26ad, all 21 NIP-11 tests and the HTTP capability test pass on Linux with PostgreSQL 17 and Redis. The HTTP test checks capability discovery and a successful incremental query. All required push hooks also pass.No manual testing. Human confirmation remains pending.
Bigger picture
Client PR 1507 uses the advertised capability for local artifact sync. Existing deployments receive this behavior when they deploy the relay version that includes this PR.
Generated with Codex