I have no idea what I'm doing. Send help.
Looks good here. Thanks!
Just wanted to add to this that it appears that the 3 day timeout is only half-working. Once I hit the former 12-hour timeout, I can still look at my timeline, but all of my links/buttons are missing. I have to manually type "/admin/logout" to get out and sign back in to fix it.
2.0.0+9a36b0edand things are A LOT better. I think you got it.
I'll keep an eye on the logs, but if you don't hear from me by tomorrow you can mark it as resolved.
2.0.0+20f996d1and it doesn't seem to have improved that much. I'll send you my logs to your email.
I'll update here in a moment and let you know.
I just noticed that the incoming worker seems to be the worst offender. It's hammering single users and trying to do a sign check on random posts in their timeline--around 2-3 per second.
Also should comment that I don't think this was happening before I updated to
2.0.0+602da690this morning. Could just be coincidental, but it might have been affected by the changes from issue #36.
Went to block someone and suddenly my logs are filling up with "database is locked" errors even though the posts do show up.
If I attempt to post anything new, it returns an Internal Server Error with the locked database.
If I unblock the user, the problem seems to go away, or at least isn't anywhere as frequent.
Updated this morning and there seems to be improvement so far. I did have one missing avatar, but when I clicked on "Reload Image" from Firefox, the image finally loaded.
Progress! : )
I've been noticing this a lot more lately in regards to remote Mastodon instances, specifically from a shared item.
Looking at the logs, attempting to retrieve the avatar from the instance returns a 404:
2022-10-07 00:45:55.929 | INFO | app.main:serve_proxy_media_resized:1108 | 1b7d0c25531c7568 - failed to proxy https://cdn.mastodon.la/accounts/avatars/108/489/072/088/012/978/original/5d6b08e86b3676a9.png, got 404 INFO: xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx - "GET /proxy/media/aHR0cHM6Ly9jZG4ubWFzdG9kb24ubGEvYWNjb3VudHMvYXZhdGFycy8xMDgvNDg5LzA3Mi8wODgvMDEyLzk3OC9vcmlnaW5hbC81ZDZiMDhlODZiMzY3NmE5LnBuZw%3D%3D/50 HTTP/1.0" 404 Not Found 2022-10-07 00:45:55.929 | INFO | app.main:__call__:167 | 1b7d0c25531c7568 - status_code=404 elapsed_time=0.05s
If I manually go to the user's timeline, their avatar is there and opening up the image in a new tab shows a slightly different URL for the avatar. In the example above, this turned out to be the correct URL:
I'm not sure if this is necessarily a bug on the microblog.pub side or potentially an incorrect URL being returned from the Mastodon API, but I figured I'd report it just in case.
Let me know if you need anything else. Thanks!