Conversation
…contract, a Store seam, an in-process Dispatcher and Worker, Verify for receivers One signed POST per event (t=…,v1=… HMAC-SHA256 over t.body, two v1 values during a secret rotation; event-type and delivery-id headers, names configurable). 2xx delivered; 429, 5xx or no answer retried after 1m, 5m, 30m, 2h, 8h, 24h with jitter, then dead-lettered; any other 4xx dropped. At least once. Store interface with an in-memory implementation, sql/ carries the reference table shape. Tests include a fuzz target on the header parser and an end-to-end worker run on an injected clock. Signed-off-by: GatisB <l22exc@gmail.com>
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
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.
— the receiver-facing contract, a Store seam, an in-process Dispatcher and Worker, Verify for receivers
One signed POST per event (t=…,v1=… HMAC-SHA256 over t.body, two v1 values during a secret rotation; event-type and delivery-id headers, names configurable). 2xx delivered; 429, 5xx or no answer retried after 1m, 5m, 30m, 2h, 8h, 24h with jitter, then dead-lettered; any other 4xx dropped. At least once. Store interface with an in-memory implementation, sql/ carries the reference table shape. Tests include a fuzz target on the header parser and an end-to-end worker run on an injected clock.