docs: note that Memcached get_and_delete raises after 16 lost CAS attempts - #221
Merged
Merged
Conversation
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.
Follow-up to #218 (#175).
docs/BACKENDS.md,docs/STATE.mdand their zh-TW translations described the CAS retry in Memcachedget_and_delete()but not what happens when it runs out. They now say it raisesCacheXErrorafter 16 attempts in a row lose to a concurrent writer, rather than report the key or state as missing.CLAUDE.mdis updated the same way.CHANGELOG.md: remove the blank lines between the Unreleased### Fixedentries (and the doubled blank line before## [0.3.7]), and wrap the Memcached get_and_delete can return a value it did not delete #175 entry heading at ~78 columns.No code changes.
tests/test_changelog_release.pypasses and both docs builds (--strict, en and zh-TW) are clean.