Closed Bubu closed 11 months ago
GITLAB_CREDENTIALS is not configured, and thus GitLab integration is available, but some of your components are using that. Maybe you were using an old configuration for that, which was deprecated in 4.14 and dropped in 4.16?
This issue has been marked as a question by a Weblate team member. Why? Because it belongs more to the professional Weblate Care or community Discussions than here. We strive to answer these reasonably fast here, too, but purchasing the support subscription is more responsible and faster for your business. And it makes Weblate stronger as well. Thanks!
In case your question is already answered, making a donation is the right way to say thank you!
Thanks for your reply.
I'm pretty certain that gitlab credentials (via the new or the old way) were never configured for this weblate instance.
The Django admin UI shows the configured VCS is gerrit
but it points to a gitlab installation (https://gitgud.io/hyphae/skin.confluencemod)?
I have no idea what's going on to be honest...
It probably shows "Gerrit" as it is first one alphabetically. Just switch it to "Git" and it should work.
I still have no clue how unsupported VCS were saved in the configuration.
Right, so changing this to Git
makes the component work again. (Even though gerrit is actually selectable from the user facing component admin page, switching to it again doesn't break the component again. So, as you suspected, this seems to have nothing to do with it.)
I still have no clue how unsupported VCS were saved in the configuration.
The only thing I can imagine right now (but it might be completely off, I'm just guessing here) is a restore from backup from another instance where this carried over from? Would something like this be possible?
(Anyway, the exceptions and email spam are gone for now, and I know how to solve this in the future as well, if it should reoccur, so feel free to close or keep this open as you seem fit.)
Project backups definitely don't validate this, so restoring it could lead to this error, https://github.com/WeblateOrg/weblate/pull/10622 will fix that.
Thank you for your report; the issue you have reported has just been fixed.
Describe the issue
Since around the time we upgraded to 5.2.1 (not sure if this caused the issue to appear or just coincided with it) browsing https://translate.codeberg.org/projects/confluencemod/main/ throws 500 errors.
The error the server produces is
KeyError at /projects/confluencemod/main/ -
'gitlab'`. Full logs below.I already tried
Steps to reproduce the behavior
Expected behavior
Component renders or at least a useful error message is produced in case something is misconfigured.
Screenshots
No response
Exception traceback
How do you run Weblate?
Docker container
Weblate versions
Weblate deploy checks
Additional context
No response