[bug] Formatted post is truncated #697

New Issue

Closed

opened 2024-02-18 21:59:02 +00:00 by a1batross · 3 comments

a1batross commented

2024-02-18 21:59:02 +00:00

Your setup

From source

Extra details

No response

Version

3.10.4

PostgreSQL version

No response

What were you trying to do?

Fetch post https://friends.deko.cloud/display/d0446be5-2065-d1b0-b609-8a1225466893

What did you expect to happen?

Read the post in its full glory.

What actually happened?

The post got truncated right after the word "особой", written in italic text.

I asked on Fedi, if anybody on Akkoma sees the same bug, it actually happened on outerheaven.club but didn't on fops.cloud. Both are running almost the same Akkoma version, though the set of MRFs (and probaby some other configuration) is different. My instance is running stable branch.

I tried to re-fetch this post but after deleting it, backend refuses it to fetch it again. 🤷

Logs

No response

Severity

I cannot use it as easily as I'd like

Have you searched for this issue?

I have double-checked and have not found this issue mentioned anywhere.

### Your setup From source ### Extra details _No response_ ### Version 3.10.4 ### PostgreSQL version _No response_ ### What were you trying to do? Fetch post https://friends.deko.cloud/display/d0446be5-2065-d1b0-b609-8a1225466893 ### What did you expect to happen? Read the post in its full glory. ### What actually happened? The post got truncated right after the word "особой", written in italic text. I asked on Fedi, if anybody on Akkoma sees the same bug, it actually happened on outerheaven.club but didn't on fops.cloud. Both are running almost the same Akkoma version, though the set of MRFs (and probaby some other configuration) is different. My instance is running stable branch. I tried to re-fetch this post but after deleting it, backend refuses it to fetch it again. 🤷 ### Logs _No response_ ### Severity I cannot use it as easily as I'd like ### Have you searched for this issue? - [ ] I have double-checked and have not found this issue mentioned anywhere.

a1batross added the

bug

label 2024-02-18 21:59:02 +00:00

ilja commented

2024-02-20 06:06:43 +00:00

Contributor

I tried to re-fetch this post but after deleting it, backend refuses it to fetch it again

If you deleted through the user interface, that's normal. A tombstone is left behind so that posts wouldn't be refetched. This is because deleting remote posts is generally because of moderation, so you wouldn't want your instance to refetch it. I think the tombstones are removed in Akkoma after a while, but I'm unsure how long it takes. You can try to find the post in the database and delete it there (objects table, and it will also be referenced from the activities table).

> I tried to re-fetch this post but after deleting it, backend refuses it to fetch it again If you deleted through the user interface, that's normal. A tombstone is left behind so that posts wouldn't be refetched. This is because deleting remote posts is generally because of moderation, so you wouldn't want your instance to refetch it. I think the tombstones are removed in Akkoma after a while, but I'm unsure how long it takes. You can try to find the post in the database and delete it there (objects table, and it will also be referenced from the activities table).

Oneric commented

2024-04-11 23:22:10 +00:00

Member

fwiw fetching this post i nfull works fine for me on current develop 1135935cbe with a fairly basic config. Without knowing which setting causes this, likely nothing can be done

By now the tombstone and delete activity should’ve been deleted (they’re kept for about 30 days). If you do further refetch tests, SQL queries to purge tombstone & delete for this post immediately are:

DELETE FROM objects WHERE data->>'type' = 'Tombstone'
  AND data->>'id' = 'https://friends.deko.cloud/objects/d0446be5-2065-d1b0-b609-8a1225466893';

DELETE FROM activities WHERE data->>'type' = 'Delete'
  AND data->>'object' = 'https://friends.deko.cloud/objects/d0446be5-2065-d1b0-b609-8a1225466893';

You might need to restart the server afterwards (or wait) to clear runtime caches.

fwiw fetching this post i nfull works fine for me on current develop 1135935cbe66043708ab0729e12b476e2d55a54c with a fairly basic config. Without knowing which setting causes this, likely nothing can be done By now the tombstone and delete activity should’ve been deleted (they’re kept for about 30 days). If you do further refetch tests, SQL queries to purge tombstone & delete for this post immediately are: ```sql DELETE FROM objects WHERE data->>'type' = 'Tombstone' AND data->>'id' = 'https://friends.deko.cloud/objects/d0446be5-2065-d1b0-b609-8a1225466893'; DELETE FROM activities WHERE data->>'type' = 'Delete' AND data->>'object' = 'https://friends.deko.cloud/objects/d0446be5-2065-d1b0-b609-8a1225466893'; ``` You might need to restart the server afterwards (or wait) to clear runtime caches.

a1batross commented

2024-04-12 10:05:41 +00:00

Author

It seems it got fixed, don't know exact commit but doesn't happen on current stable: 26a91d5c9e

Closing.

It seems it got fixed, don't know exact commit but doesn't happen on current stable: https://akkoma.dev/AkkomaGang/akkoma/commit/26a91d5c9eef1b2c75d3e0e7cc792d62e953cb30 Closing.

a1batross closed this issue

2024-04-12 10:05:41 +00:00

No Milestone

No project

No Assignees

3 Participants

Notifications

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: AkkomaGang/akkoma#697

No description provided.