csabaxyz commented on issue #356:
URL: https://github.com/apache/couchdb-nano/issues/356#issuecomment-3287835196
> Curious what led up to this? What operation was being performed?
Essentially I was in the process of implementing a minimal migration script
to setup the database before the rest of the code runs, and that code runs when
the Docker containers are coming online, so the initial connection can actually
go to a non-existent database service. So, when the error happens the request
looks like this:
```js
{
url: "http://couch:5984/_session";,
method: "post",
headers: {
accept: "application/json",
"user-agent": "nano/11.0.0 (Node.js v24.3.0)",
"Accept-Encoding": "deflate, gzip",
"content-type": "application/x-www-form-urlencoded; charset=utf-8",
},
credentials: "include",
body: URLSearchParams {
"name": "***",
"password": "***",
},
redirect: "error",
signal: undefined,
bodyTimeout: 0,
}
```
But you are right, when I was using `v10` the error was swallowed in the
retry logic. I downgraded to see what the error was before:
```
152 | return
153 | }
154 |
155 | log({ err: 'socket', body, headers: responseHeaders })
156 | if (reject) {
157 | reject(new Error(`error happened in your connection. Reason:
${response.message}`))
^
error: error happened in your connection. Reason: ECONNREFUSED
at responseHandler (/opt/src/node_modules/nano/lib/nano.js:157:16)
at <anonymous> (/opt/src/node_modules/nano/lib/nano.js:456:13)
```
--
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: notifications-unsubscr...@couchdb.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
