Skip to content
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] Missing posts from timeline since 0.17 after instance restarts #3568

Open
kouya opened this issue Nov 25, 2024 · 3 comments
Open

[bug] Missing posts from timeline since 0.17 after instance restarts #3568

kouya opened this issue Nov 25, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@kouya
Copy link

kouya commented Nov 25, 2024

Describe the bug with a clear and concise description of what the bug is.

When I restart gotosocial, accounts have missing posts in their timelines. It's always the recent ones, it fixes itself after while.

What's your GoToSocial Version?

0.17.3

GoToSocial Arch

amd64 binary

What happened?

I have multiple accounts on my instance, including one that posts automated every hour. When the server gets restarted (Debian unattended upgrades in this case), the home timelines of some/all accounts have missing posts in them backwards some time from the point of restart. Newly posted things get shown normally. Eventually the missing posts show up again after a day or so.

All posts show up on the website or when using the account view (I'm using phanpy or Tusky). The posts also all federate correctly. Only the timeline view seems affected. It certainly feels like some caching issue.

Sadly it does not seem to happen always and not to all accounts on the server.

I only noticed it after 0.17, never before.

What you expected to happen?

Timeline regenerated correctly after instance restart.

How to reproduce it?

  • Restart the instance
  • Look onto the home timeline of an account where you know that posts should be there and recent ones (or maybe others) are missing

Anything else we need to know?

I have this additional information from when we tried to figure out what happened:

To get the home timeline there is the api /api/v1/timelines/home
Phanpy is using /api/v1/timelines/home?limit=20
It fixed itself when I manually used /api/v1/timelines/home?limit=20&since_id=… where the id was of some recent status.

I think the cache fixed itself when less than specified max number of statuses is fetched.

@kouya kouya added the bug Something isn't working label Nov 25, 2024
@kouya
Copy link
Author

kouya commented Nov 28, 2024

Update after few days: for some reason the feeds of the affected accounts did not update yet. I can for example verify there are posts every day on https://icy.arcticfluff.eu/@arcticfoxbot yet the home feed for that account in both Phanpy and Tusky show no posts between Nov 20th and 25th for some reason.

@tsmethurst
Copy link
Contributor

Hiya! Sorry, we've been late getting to this as we've been off on our holidays :) Is the issue still showing up?

@kouya
Copy link
Author

kouya commented Jan 22, 2025

Hiya! Not a problem, hope you enjoyed your holidays. :3

The issue still exists. My server where GTS is running on, was auto restarted from Debian unattended updates few days ago. I can easiest verify it via a bot account posting a daily picture. Both of them show a "hole" of 10 of their own posts on their home feeds. The posts are all there though when I go to the account view directly in tusky or the website generated by GTS.

It certainly feels like an issue of some sort of cache that builds the home feed. Though it didn't fix itself like I stated in my original post.

I only notice this when GTS starts and the home feed never seems to "lose" items while it runs.

I hope it's clear enough but if you want any more information let me know please.

Edit: Of course after rebooting the server again due to updates, this time it didn't happen. The only difference was that GTS had less uptime than before, like 2 weeks or so since the last service restart.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants