luckily we caught this early before monyetbot had a lot of posts. anyway, i think what’s even more important is the keypair in the db, so it is good the problems monyetbot had were not related to that.
by the way, you may want to do a sql dump and search if there’s any other reference to frank_bot that can be updated. i heard lemmy 0.18.3 (out last night) has quite a bit of db optimizations, so don’t want any outdated reference to cause issues with that.
I tried checking the foreign key contrainsts in the db but it seems like there aren’t any tables referencing actor_id, usually just the id(PK column) of the person table.
okay, anyway maybe there’ll be a lemmy 0.18.4 soon.
they’re finding all sorts of bugs including a duplicate comment bug, and another one that makes the lemmy version in the instances list become 2.0 instead of 0.18.x.
i wonder if someone was dreaming about an early lemmy 2.0, lol.
luckily we caught this early before monyetbot had a lot of posts. anyway, i think what’s even more important is the keypair in the db, so it is good the problems monyetbot had were not related to that.
by the way, you may want to do a sql dump and search if there’s any other reference to
frank_botthat can be updated. i heard lemmy 0.18.3 (out last night) has quite a bit of db optimizations, so don’t want any outdated reference to cause issues with that.I tried checking the foreign key contrainsts in the db but it seems like there aren’t any tables referencing actor_id, usually just the id(PK column) of the person table.
okay, anyway maybe there’ll be a lemmy 0.18.4 soon.
they’re finding all sorts of bugs including a duplicate comment bug, and another one that makes the lemmy version in the instances list become
2.0instead of0.18.x.i wonder if someone was dreaming about an early lemmy 2.0, lol.
lol 2.0 😂