-
Notifications
You must be signed in to change notification settings - Fork 11
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
Database init fails on first/second try #16
Comments
I'm unable to reproduce this issue. Did you create the file you wanted to use as a DB before starting the bot, or did you let the bot create it? |
I let the bot create it. I pretty reliably get this every time I remove the sqlite file before starting the bot. The code is here, if you want to have a look: https://github.com/r-sauna/lemmy-reddit-bot |
While I haven't gotten to running your bot I noticed that you're using a fork that is 18 commits behind the upstream and doesn't have the latest changes to support 0.18.x Lemmy instances. Do you still get the error if you update the dependency? |
I'll set up a dev environment to check that in a few days - but I'd guess it won't change anything: The reason I'm using the fork (and added the prepare script) was that I was hoping the issue was fixed in latest head at that point. |
It can create a DB now - I guess this got accidentally fixed by dropping websockets. I assume before events started coming in before the database was ready, which doesn't happen anymore. Unfortunately with the new version I don't get any events coming in (and based on the issue tracker I'm not alone in that). I also get an error on startup when I'm using minutesBeforeRetryConnection in the connection options. |
@bwachter Do you still run into this issue? Your most recent comment mentions websockets, which were removed from Lemmy's API the better part of a year ago. |
Works fine in memory, on disk tends to take one or two start attempts for it to finish initialisation.
The text was updated successfully, but these errors were encountered: