Couchdb replication bug report #4299
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
|
If the normal node fetch does not work, we should fix that first. |
|
@pubkey I tested it just now with |
|
Pls adapt the test so that the CI reproduces your problem |
|
Done. |
|
Thank you so much. Fixed in 657de00 |
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.
Hello,
As requested, here is a pull that reproduces the CouchDB replication bug.
Had to add
node-fetch@2because replicationfetchwould fail during the test.Other than that just have a CouchDB instance running, edit the credentials and give it a try.
As always, thank you for your time.