-
-
Notifications
You must be signed in to change notification settings - Fork 325
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
Mastodon: "Fatal chain event" on post #382
Comments
I'll have to check out the backtrace, but it's probably worth bumping the go-mastodon dependency one way or another. Let me know if you run into this again! |
Okey dokey! 😁 |
I got that again:
|
And again yesterday...
|
I still get:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @muesli, I got this in my beehive Docker container (latest). I don't know if this helps...
My Mastodon bee usually works, it just stopped working, so I restarted the container after getting below message (I don't know yet if it works again).
The text was updated successfully, but these errors were encountered: