Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[upcoming branch] Request stream error masks potential server response #59

Open
natevw opened this issue Jun 24, 2016 · 2 comments
Open

Comments

@natevw
Copy link
Owner

natevw commented Jun 24, 2016

If CouchDB gets upset, it may simply close the incoming pipe as it sends a repsonse. Rather than getting the response as an error, fermata returns only:

{ Error: write EPIPE
    at exports._errnoException (util.js:1007:11)
    at WriteWrap.afterWrite (net.js:793:14) code: 'EPIPE', errno: 'EPIPE', syscall: 'write' }
@natevw
Copy link
Owner Author

natevw commented Sep 21, 2016

To clarify, I think this is talking about a situation where the request is still in progress when the server decides to send its response.

@natevw
Copy link
Owner Author

natevw commented Sep 21, 2016

This is related to #52 as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant