-
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Notifications fail to load #1491
Comments
Part of the nginx log that might be related, and console log in firefox. Seems like other people have the same problem https://ohai.su/users/lutoma/updates/146 [EDIT] nginx is no longer showing me these errors and yet the problem persists |
This was following upgrading to master from v1.1.1. I basically followed the production guide:
|
Possibly related commit (which is after 1.1.1) - 12f72e1 |
Rerolling to v1.1.1 AND downgrading the assets fixes it (I'm dumb) |
* When avatar/header are GIF, generate static versions. Account API returns "avatar"/"avatar_static", "header"/"header_static" Static version is the same as original for other cases Web UI de-animates avatars in toots, lists of users Fix #441, fix #596, prerequisite for #1064 * Fix JS test * Add rake task to generate static avatars/headers from GIF ones, add test
Notifications were still streaming, and working in the Android app. Unlikely that a server change would do that. And it seems I accidentally hid it, but the actual error is |
Same happening to my instance (“Ops! An unexpected error occurred.” message). Notifications are blank. Running latest master, dockerised. |
Reverted to 0687ab8 and it works again. |
looking over my draft of an integration test #1499 , Follow notifications don't have a |
@riking That seems to be the case. My notifications are loading until I scroll down to where the latest follow notification is at which point it stops loading and fails with the error |
Could someone post the temporary fix for this? Will a |
@Fastidious |
@wxcafe I am on Docker. For anyone wanting to temporarily fix this using Docker, the steps are:
|
I found the source of the issue, preparing a PR. |
fwiw, i'm only seeing it when i attempt to search something. will check out the fix. |
appears to be fixed with that commit |
…ing for exclude_types
Merge upstream changes
Bad commit 12f72e1
The text was updated successfully, but these errors were encountered: