WIP: watcher: add optional SQS subscription for crate index changes - #3349
Draft
syphar wants to merge 79 commits into
Draft
WIP: watcher: add optional SQS subscription for crate index changes#3349syphar wants to merge 79 commits into
syphar wants to merge 79 commits into
Conversation
github-actions
Bot
added
the
S-waiting-on-review
syphar
changed the title
Wrap typed change payloads in a conventional event envelope with id, occurred_at, source, and schema_version.
Rename the current wire payload to ChangeV1 and make the event envelope generic for future schema versions.
Remove event source metadata and store occurred_at as an RFC 3339 OffsetDateTime.
Replace time::OffsetDateTime with chrono::DateTime<Utc> for RFC 3339 event timestamps.
Treat duplicate version deletion events as a no-op so temporary event-based handling can safely replay them.
Add watcher config fields for an SQS queue URL and region to support an event-based path.
Use url::Url for the watcher SQS queue URL config so invalid values fail during config loading.
Update Cargo.lock after making docs_rs_watcher depend directly on url.
Remove the redundant schema_version field from the crates.io event envelope and keep versioning in the typed payloads.
This comment has been minimized.
This comment has been minimized.
syphar
commented
Jun 3, 2026
Rename the SQS subscriber entrypoints to better reflect the transport, body-handling, and event-processing layers.
Supervise the SQS subscriber separately in mixed mode so SQS failures are logged and restarted without stopping the legacy registry watcher.
Add starter counters and histograms for SQS intake, failures, retries, processing time, event lag, and applied change types, and record them from the subscriber flow.
Add buckets around the one-minute visibility timeout so slow message handlers are easier to spot in metrics.
syphar
commented
Jul 17, 2026
| .add(messages.len() as u64, &[]); | ||
|
|
||
| for message in messages { | ||
| match handle_message_body(context, config, metrics, message.body.as_deref()).await { |
Member
Author
There was a problem hiding this comment.
can we have some graceful shutdown here?
otherwise, if the watcher is stopped while handling a message, the msg will be in-flight in SQS, so sqs will wait delivering any message for the visibility timeout.
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
2 participants
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.
idea is: