Validate lazily loaded classes in deploy checks #12135
Labels
enhancement
Adding or requesting a new feature.
good first issue
Opportunity for newcoming contributors.
hacktoberfest
This is suitable for Hacktoberfest. Don’t try to spam.
help wanted
Extra attention is needed.
Describe the issue
I run weblate in docker with an Apache reverse proxy setup. The docker-compose configuration contains a setting for
WEBLATE_ADD_ADDONS
. Now, I recently discovered that there was a "typo" in one of the add-ons listed there: weblate.addons.consistency.LangaugeConsistencyAddon. I then though, that I might have caused this typo myself, "fixed" it, and restarted the instance. Soon after, I started to observe internal server errors that were caught by Sentry. The Sentry backtrace shows this:Now, I do understand the error, and I changed the add-on name back to what seems to be the correct name. But shouldn't weblate handle this situation more gracefully than causing an internal server error? In my case, the error was thrown while I was creating a new component, which lead to empty translations in that component.
I already tried
Steps to reproduce the behavior
WEBLATE_ADD_ADDONS=weblate.addons.consistency.LanguageConsistencyAddon
.Expected behavior
Handle the situation more gracefully without causing an internal server error.
Screenshots
No response
Exception traceback
How do you run Weblate?
Docker container
Weblate versions
Weblate deploy checks
Additional context
No response
The text was updated successfully, but these errors were encountered: