[bug] Broken federation with WriteFreely (and probably other platforms) #963
Labels
No labels
approved, awaiting change
broken setup
bug
cannot reproduce
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs change/feedback
needs docs
needs tests
not a bug
not our bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AkkomaGang/akkoma#963
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Your setup
OTP
Extra details
Arch Linux
Version
3.15.2
PostgreSQL version
17.5
What were you trying to do?
Summary
When federating an ActivityPub
Updateactivity from WriteFreely (and similar platforms), Akkoma/Pleroma crashes with the following error:Steps to Reproduce
Updateactivity from a remote server, where:"type": "Update"objectis a standardNote(orArticle) with valid fields:id,type,content,published,url, etc.Additional Notes
side_effects.exand the use of.dataon anilvalue.How to reproduce from scratch
Proposed Fix
What did you expect to happen?
Akkoma/Pleroma should either:
What actually happened?
(KeyError) key :data not found in: nil.Logs
Severity
I cannot use it as easily as I'd like
Have you searched for this issue?
This appears to be a duplicate of #888 and while an odd fluke, usually does not affect federation. Only if it repeatedly fails exhausting all retries will the received object actually be (ungracefully) dropped. By default it’s 5 attempts spread out over about half an hour.
Updates for unknown objects are already handled gracefully; the processing getting far enough to be in side effects implies it was able to dereference the object before.