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

Mw/cache no fail #49

Merged
merged 1 commit into from
Oct 2, 2023
Merged

Mw/cache no fail #49

merged 1 commit into from
Oct 2, 2023

Conversation

michaelwood
Copy link
Member

@michaelwood michaelwood commented Sep 4, 2023

Makes the cache mechanism more robust and avoids errors being fatal. Fixes #48

@michaelwood michaelwood requested a review from R2ZER0 September 4, 2023 16:18
getter/cache.py Outdated Show resolved Hide resolved
Make cache exceptions non fatal

If the cache fails for whatever reason then carry on without it. We
generally don't want cache errors to be fatal but they are useful to
know about so we just print the exceptions which will get picked up by
the monitoring.

Fixes: #48
Copy link
Contributor

@R2ZER0 R2ZER0 left a comment

Choose a reason for hiding this comment

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

Code looks good, merge if testing passes!

@michaelwood michaelwood merged commit 58fae3d into master Oct 2, 2023
6 checks passed
@michaelwood michaelwood deleted the mw/cache_no_fail branch October 2, 2023 13:44
@michaelwood
Copy link
Member Author

Now deployed thanks

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.

cache: If file remote name changes we get a uniqueness error
2 participants