-
Notifications
You must be signed in to change notification settings - Fork 90
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
AttributeError: 'NoneType' object has no attribute 'uri_domain' (in call to /api/v1/timelines/home) #690
Comments
@virtualmarc 574 is a lot. wondering if it has been a bug. you may select |
@alphatownsman I just checked some of them (not all since these are too many). Some are using software that is currently incompatible with Takahe and are probably fixed with #682 (not only GoToSocial, but also bird.makeup, a.gup.pe, some other twitter mirrors. some are friendica or write.as, where I haven't actively observed federation issues but am not sure if they really work). Most of them are instances not available anymore (either responding with 404, timing out or no dns records anymore). One I checked was a moved profile on Mastodon. Some few are normal Mastodon accounts that are still available. While looking at the Activity Pub JSON's of some of the identities, they sometimes look weird. This one for example is from a friendica instance missing most information:
This one is from a mastodon instance from a moved account, also missing most information:
When fetching some of the actor uri's of failing mastodon instances with curl (like the nafo.uk example or at cupoftea.social) I'm getting the browser check page of Cloudflare, this can also be a problem that the request is blocked by the Cloudflare (or any other CDN) WAF (at least when I try it from my server, fetching fine from my home connection, so the WAF is probably blocking the datacenter ip's). |
Thanks. at least one of these domain are fixable, which is for the rest, Fediverse data are always chaos, guess we just need to use I'll put some patches together. |
When loading the Home Timeline Takahe 0.10.1 responds with an Error 500 and the following Traceback:
This suddenly startet around 12h ago for one user, so I think an incomplete post came in at that time.
I had no problems loading the local or federated timeline. Other user's had no problems loading their timelines so far.
Now, 12h later, the affected user is able to load his home timeline again, so I think this post is now out of the view.
If I scroll down far enough to the posts around 12h before, with the affected user, the error occurs again.
I tried to find the Post in the Django Admin console with no luck, but I guessed that this is an identity without a domain, so I selected
users_identity
withdomain_id is null
and got 574 rows.The text was updated successfully, but these errors were encountered: