(#4078) - simple fix for ETag bug #4079
Closed
Conversation
This file contains 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
|
Heh, it's funny. I just realized the only reason I noticed this bug was because I accidentally removed the cache-busting in another PR. |
|
I filed a bug on couch for this, https://issues.apache.org/jira/browse/COUCHDB-2764, 👍 for the workaround for now |
|
Merged in 7c16604 |
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.
Simple solution to the problem: don't put ourselves
in a situation where the ETag bug can bite us.
Changes the document IDs to be more unique, and also
adds
barvalues to the documents so we get moremeaningful errors than "couldn't read undefined.should".