-
-
Notifications
You must be signed in to change notification settings - Fork 899
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
[Bug]: AP_ID with 'http://changeme.invalid/' + 24 chars #5444
Comments
0.19.3 was released in january of last year. But also I can see that in |
That changeme url is the default value for the database field, which gets updated by a trigger to the correct id. Seems like the trigger was not executed for some reason. cc @MrKaplan-lw |
That's odd. It also doesn't seem to be incorrect anymore at this point, I haven't checked the code yet, were there cases in 0.19.3 where this was changed outside of the insert transaction? Since triggers are synchronous within the DB transaction those IDs should then never be exposed to another query. If this was the case in 0.19.3, what about 0.19.9? Does 0.19.9 have logic where these IDs would exist temporarily outside of the insert transaction? |
I got another one, as it was Announced this time, rather than my server trying to fetch something that was Liked or replied to. It has the correct AP_ID now - it's at https://lemmy.world/comment/15251256, but when it was Announced, the IDs were:
My guess would be that other Lemmy servers initially rejected it, but it had internally fixed itself by the time other people replied to it, so they were then able to fetch it (it looks like it was fetched, because the score is 0, but no-one has downvoted it) |
Requirements
Summary
I have been receiving activities for which my server hasn't been able to fetch the relevant object, and have finally tracked one down.
The activity was:
I searched for that object on LW, and it returned a comment: https://lemmy.world/search?q=http%3A%2F%2Fchangeme.invalid%2F4bcffd164a915f319fc412df&type=All&listingType=All&page=1&sort=TopAll
Requesting that comment via the API returned that it had that URL for its ap_id:
curl https://lemmy.world/api/v3/comment?id=15207268 | jq .comment_view.comment
Steps to Reproduce
curl https://lemmy.world/api/v3/comment?id=15207268 | jq .comment_view.comment
(EDIT: I don't have the activities for these, but have also discovered):
2.
curl https://lemmy.world/api/v3/comment?id=15208607 | jq .comment_view.comment
3.
curl https://lemmy.world/api/v3/comment?id=15186242 | jq .comment_view.comment
Technical Details
The ones I've found so far are from LW accounts, and they're a bit funny about staying up to date, so hopefully this is a bug that you already know about and is fixed (I couldn't find any other relevant Issues though).
Version
BE: 0.19.3-7-g527ab90b7
Lemmy Instance URL
lemmy.world
The text was updated successfully, but these errors were encountered: