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

Better handle transient feed errors #775

Open
Altonss opened this issue Jan 8, 2025 · 1 comment
Open

Better handle transient feed errors #775

Altonss opened this issue Jan 8, 2025 · 1 comment
Labels
help wanted Extra attention is needed import regarding the download & import of data sources

Comments

@jbruechert
Copy link
Collaborator

jbruechert commented Jan 13, 2025

I think this requires a redesign of the current issue reporting.

fetch.py could write the issues into a json file / sqlite database (per region file so we don't need to deal with locking).
It could also write things like exact error causes and count the number of identical error messages, timestamps etc.
Then in a second pass we could go over the generated reports in another script to make decisions what to open issues for.

Then for specific errors like timeouts, issues could only be opened after the issue occurs for more than a day or so.

@jbruechert jbruechert added import regarding the download & import of data sources help wanted Extra attention is needed labels Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed import regarding the download & import of data sources
Development

No branches or pull requests

2 participants