kocolosk commented on issue #3939: URL: https://github.com/apache/couchdb/issues/3939#issuecomment-1048944382
Yes, that's correct @jcoglan. The question I've been mulling over for the past few minutes is whether an interactive edit conflict is detected by `PARSER`, or whether we have the same issue there because the attachment writers are never spawned. Should be pretty straightforward to test; in the worst case _any_ `multipart/related` request that results in an edit conflict would hit the timeout, no data race required. But I was hoping to track down that logic in the codebase itself, and as you're well aware that's a challenging exercise for this bit of functionality. I'm OK with the suggestion for the `FABRIC` coordinator process to inform the `PARSER` that a writer won't be requesting data. I'm still curious to understand what happens in the case of an interactive edit conflict. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
