You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(node:13549) UnhandledPromiseRejectionWarning: OpenError: IO error: ./non-existent-path/_replicator/LOCK: No such file or directory
Despite the warning, we continue on with a non-functional pouchdb object backing those routes. When trying to handle a request, this bit of code gets stuck forever while allocating more and more promises:
// calls itself until usersDBPromise is a available
if(!usersDBPromise){
returnnewPromise(function(resolve){
setImmediate(function(){
resolve(getUsersDB());
});
});
}
returnusersDBPromise;
}
After busylooping while growing to a few gigabytes in size, node gets fed up and terminates.
This could probably be mitigated by only using one promise there and only repeating the setImmediate (or even setTimeout) call, but ultimately we should probably just be erroring out earlier and not let it come that far.
It's a very low impact crash that's easily avoided, but jumping into an unfamiliar codebase and not realizing the significance of the above warning, it took me a while to catch on. :)
The text was updated successfully, but these errors were encountered:
Despite the warning, we continue on with a non-functional pouchdb object backing those routes. When trying to handle a request, this bit of code gets stuck forever while allocating more and more promises:
pouchdb-server/packages/node_modules/express-pouchdb/lib/routes/authentication.js
Lines 55 to 65 in ef24d7d
After busylooping while growing to a few gigabytes in size, node gets fed up and terminates.
This could probably be mitigated by only using one promise there and only repeating the setImmediate (or even setTimeout) call, but ultimately we should probably just be erroring out earlier and not let it come that far.
It's a very low impact crash that's easily avoided, but jumping into an unfamiliar codebase and not realizing the significance of the above warning, it took me a while to catch on. :)
The text was updated successfully, but these errors were encountered: