Skip to content

Continue on registry error - #29

Merged
matentzn merged 1 commit into
mapping-commons:mainfrom
cthoyt:continue-on-registry-error
Sep 15, 2026
Merged

matentzn merged 1 commit into
mapping-commons:mainfrom
cthoyt:continue-on-registry-error

Conversation

@cthoyt

@cthoyt cthoyt commented Sep 15, 2026

Copy link
Copy Markdown
Member

Closes #28

@matentzn matentzn left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How will we ever know though that some registries are not parsed / displayed?

@cthoyt

cthoyt commented Sep 15, 2026 •

Copy link
Copy Markdown
Member Author

It will be in the logs for the automated build. It could also be possible to engineer a more sophisticated solution, such as having the python script open an issue on the repo saying a registry is down and somebody should check.

Do you have another idea for how to recover from data being missing? Currently, the result of a registry being unavailable is automated update isn't possible

@matentzn

Copy link
Copy Markdown
Contributor

I have many ideas, but maybe lets just roll with it for now.

We could have a cronjob GHA check every week if all registries still parse, and if not, file an issue and assign to me for investigation. But IMO not worth it now.

@matentzn
matentzn merged commit b78f922 into mapping-commons:main Sep 15, 2026
1 check passed
@cthoyt
cthoyt deleted the continue-on-registry-error branch September 15, 2026 13:03
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

Successfully merging this pull request may close these issues.

Chronological refresh is failing

2 participants