-
Notifications
You must be signed in to change notification settings - Fork 165
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
More understandable error message when max_document_size has been reached #343
Comments
Can you check if it comes from this line? It's 442 in the error message, but something different in the current code. If you can still reproduce the issue, can you also patch that bit by adding I guess, this can be improved by patching streamResponseHandler; can you share a more specific message you'd expect? Like "max_document_size has been reached when/for ..." |
I reproduced this by decreasing the max_document_size and tried an insert operation. "max_document_size has been reached" this is a understandable error i guess. maybe we could provide the solution also like: go to config -> go to section couchdb -> add or increase max_document_size option or something like this, would be very helpful. what do you think? @YakovL Here is the console.log(e)
Here is the initial error
|
Hi @pana87, good thinking about making the error message helpful, may be it can read "max_document_size has been reached, you may want to open config [what config?], ...". However, the problem here is that the error doesn't seem to be specific enough to be attributed to the |
Expected Behavior
Understandable error message
Current Behavior
I was getting this error suddenly on every insert operation:
Error: users at responseHandler (../node_modules/nano/lib/nano.js:193:20) at ../node_modules/nano/lib/nano.js:442:13 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Possible Solution
I updated the max_document_size in the couchdb configs
Context
I spent 3 days trying to find out what this error meant. Maybe it would be useful for developers if the error message was a bit more understandable.
The text was updated successfully, but these errors were encountered: