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

Feed stops receiving new posts after about 8 hours #19

Closed
seanthegeek opened this issue Dec 6, 2024 · 6 comments
Closed

Feed stops receiving new posts after about 8 hours #19

seanthegeek opened this issue Dec 6, 2024 · 6 comments

Comments

@seanthegeek
Copy link
Contributor

Hello. When using this template, I've noticed that it will stop receiving new posts after about 8 hours like clockwork until I restart the service. The service will try to load the posts that it missed in the meantime, but it can never catch up, so I delete the feed database before starting the service again.

I'm not sure if some sort of keepalive needs to happen and/or more graceful error handling.

I'm attaching two tracebacks, although this last time I noticed that there was no exception or traceback generated when the feed stopped receiving posts.

bluesky.log

@MarshalX
Copy link
Owner

MarshalX commented Dec 6, 2024

Hello. As I can see from your logs it is this issue MarshalX/atproto#430

@seanthegeek
Copy link
Contributor Author

I still have an issue with the feed occasionally not having any new posts until the server is restarted. This time it is not related to that other issue, because there are no errors or earnings in the logs. I'm still researching the cause.

@p1timmy
Copy link

p1timmy commented Dec 11, 2024

I still have an issue with the feed occasionally not having any new posts until the server is restarted.

I had that same exact issue too and found out it's caused by a bug in the ATproto SDK code where there's no timeout in receiving messages, I filed an issue about it in MarshalX/atproto#489.

Also I've seen the firehose client do nothing and stall on some but not all days, most of them happened couple minutes after the client got spammed with 503 Service Unavailable errors.

@seanthegeek
Copy link
Contributor Author

Turns out this was a client-side issue.

@MarshalX
Copy link
Owner

@seanthegeek could you share more details? For others

@seanthegeek
Copy link
Contributor Author

deck.blue sometimes won't updated the feed automatically like it should until the page it refreshed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants