LOCK does not get removed after nodemon closes about airgram HOT 5 CLOSED

I guess you use PouchDB as a storage? It's a persistent storage so the data hasn't been removed after process termination. By default, PouchDB uses file system (LevelDB) but you may use any other adapter or pouchdb-server.

Some more information you can find in the docs.

If you have more questions please feel free to ask.

from airgram.

Yeah I have used pouchDB. Actually I have used your example as scaffolding for my projects (https://github.com/airgram/airgram-ts-example).
I know its a persistent storage but persistent storages have a lock mechanism which pouchdb has. But it does not remove its own LOCK file from data directory. I think this problem is from pouchdb itself or maybe you forgot to call a close like function for the database.
Anyway I am now using this in the beginning lines of index.ts file:

// remove the LOCK file before any work:
fs.unlink(__dirname + '/../data/airgram/LOCK', (err) => { })

from airgram.

Can you explain why you need to delete the LOCK file?

from airgram.

I found where the real problem was. If my code throws some error and crashes, pouchdb does not close and does not unlock the database before its own exit. Causing errors to occur, saying that database is locked (like the one I mentioned in the first comment).
I dont know if this is a problem of pouchdb or your project but I have managed to get rid of it by removing the LOCK file before performing any action.

from airgram.

Airgram provides an abstract layer for creating data store and does not provide an implementation for any particular database, so we can't check if the 'LOCK' file exists. Please do it by yourself.

Please reopen the issue if you have some more questions.

from airgram.