GitHub user rnewson added a comment to the discussion: Problem: CouchDB not answering to request
No, I don't think it's an oversight on your part, we don't document when couchdb starts the response (we tend to delay it until we can confirm if we should send a 200 OK or some kind of error). You just need to anticipate that the request might time out without a response if there are no changes. Arguably we should change the behaviour to start a response promptly, even if the response body ultimately ends up with no results. GitHub link: https://github.com/apache/couchdb/discussions/5616#discussioncomment-14006878 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
