Repository navigation
didit_with_email: a waiting join's status poll spends no KV write or list - #33
Merged
Merged
Conversation
…dit's answer changes Didit reads are spaced by a new store claim. On KV it lives in the Workers Cache API, so a waiting join's polls spend no KV write or list.
…y why the claim URL is hashed
…pen interval Cause: a claim keeps the interval it was taken with. An unchanged read of a declined or expired session claimed the read key for 300 seconds, and the attempt Continue started next shared that key, so its approval went unseen for up to 5 minutes. Each state now claims under its own key.
… read interval before it tries again
…olds the read interval
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.
Unyt's Cloudflare account hit the Workers Free KV daily limit, and joins then failed with 503 "The service could not record the email." Each status poll of a waiting didit_with_email join spaced its Didit read as a KV event (a put and a list) and saved the whole session after every read: about 480 writes and 240 lists an hour per waiting person.
Didit reads are now spaced by a store claim, which the KV store keeps in the Workers Cache API, and a read is saved only when Didit's answer changed. A waiting person now costs one KV read per poll and no write or list.
Changelog