Posting a status to a list causes mastoFE to crash #95

Open
opened 2021-02-13 20:36:01 +00:00 by deadsuperhero · 1 comment
Member

Hey there!

I'm in the process of building Sporadic*: a Diaspora-clone frontend for Pleroma! One of the features I was interested in supporting was the recreation of Aspects, which is basically a way to post a private status to a specified group of people.

I was trying this out for the first time today, and while it seems to have gone through, mastoFE immediately freaked out.

Here's what was in the payload:

-----------------------------34318860801516679447438874830
Content-Disposition: form-data; name="status"

Testing a private status sent to List 6 only. No one else should be able to see this.
-----------------------------34318860801516679447438874830
Content-Disposition: form-data; name="visibility"

list:6
-----------------------------34318860801516679447438874830
Content-Disposition: form-data; name="content_type"

text/markdown
-----------------------------34318860801516679447438874830
Content-Disposition: form-data; name="in_reply_to_id"

undefined
-----------------------------34318860801516679447438874830--

and the stacktrace as well:
https://pastebin.com/XLb2SkXf

Attached is also the JSON of the resulting status, for posterity.
list-status.json

Hey there! I'm in the process of building [Sporadic*](https://git.feneas.org/deadsuperhero/sporadic): a Diaspora-clone frontend for Pleroma! One of the features I was interested in supporting was the recreation of Aspects, which is basically a way to post a private status to a specified group of people. I was trying this out for the first time today, and while it seems to have gone through, mastoFE immediately freaked out. Here's what was in the payload: ``` -----------------------------34318860801516679447438874830 Content-Disposition: form-data; name="status" Testing a private status sent to List 6 only. No one else should be able to see this. -----------------------------34318860801516679447438874830 Content-Disposition: form-data; name="visibility" list:6 -----------------------------34318860801516679447438874830 Content-Disposition: form-data; name="content_type" text/markdown -----------------------------34318860801516679447438874830 Content-Disposition: form-data; name="in_reply_to_id" undefined -----------------------------34318860801516679447438874830-- ``` and the stacktrace as well: https://pastebin.com/XLb2SkXf Attached is also the JSON of the resulting status, for posterity. [list-status.json](/attachments/0d98f742-c663-412d-89c7-a2fccc6d44d8)
Author
Member

Also of note: deleting the offending status makes mastoFE go right back to working normally. 😅

What's curious is that the error message about an ID value missing...but, from what I can tell, everything that is needed is present?

Also of note: deleting the offending status makes mastoFE go right back to working normally. :sweat_smile: What's curious is that the error message about an ID value missing...but, from what I can tell, everything that is needed is present?
Commenting is not possible because the repository is archived.
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pleroma/mastofe#95
No description provided.