Open FireMasterK opened 12 months ago
I would suggest that you just ignore it and either run it in pm2 or just catch it with
process.on("uncaughtException", (error) => { console.log("uncaught error:"); console.log(error); });
Could you give some information on your setup? I have a couple of bots running in production and have never encountered this issue.
I have been running it with docker: https://github.com/TeamPiped/lemmy-piped-link-bot/blob/main/docker-compose.yml https://github.com/TeamPiped/lemmy-piped-link-bot/blob/main/Dockerfile
I'll try running one of my bots in a docker container. I've used systemd processes for production, so that may be why I haven't experienced issues.
@FireMasterK This issue is from several versions ago. Are you still getting this issue?
Some weird database issues..