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
Change not committed if user full name has accent #2850
Comments
Do you get any errors? Most likely it will be in celery logs. |
When I force a commit, I see no error in the logs. |
Is celery worker running? Can you see the commit task in their logs? |
I guess as I see logs like "Received task" and changes from other users (without accent, only ASCII) are committed. |
Issue #2850 Signed-off-by: Michal Čihař <michal@cihar.com>
It can hardly disappear without any trace. In the main celery log there should be something like:
An then followed in the worker log:
|
We need to have either all units saved and updated or rollback. Issue #2850 Signed-off-by: Michal Čihař <michal@cihar.com>
There should be no uncommitted changes in the repo, so in past something has probably failed. Can you check what changes are there? It seems that in some corner cases flushing changes is not properly executed in a transaction (see 8188c4b), so there was probably some bug in the past where it failed. It really doesn't have to be related to accents because this should work fine (tested on myself). |
They are only changes I made with accented full name and one that I made today. But if it is not related to the full name, what should I do to commit those changes? |
Without finding the actual exception in the logs, it's only guessing what has happened. We do have unit tests for commit with unicode name and I'm usually the one to hit such problems, so it has definitely received some coverage. On the other side Mercurial backend is way less used than Git, so it's possible it's some issue with that. |
Apparently we can not expect everybody to setup error collection and log should indicate the problems. Celery does swallow the exceptions (actually it stores them as result, but Weblate doesn't care for results for most of the operations), see https://stackoverflow.com/q/16658371/225718 Issue #2813 Issue #2850 Signed-off-by: Michal Čihař <michal@cihar.com>
Hmm, it turns out that the error would not be logged because of Celery nog logging such errors. Can you please retry after applying 4170919? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I did not have time yet to test the patch because I have only a docker setup in production and not any development environment. So it would be a pity to close the issue without a fix. |
True, the bot just kicks in when there is nothing new for two weeks. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Today, when testing new CI platform, I got test failure on the commit with Unicode name, see https://cloud.drone.io/WeblateOrg/weblate/7/1/3 It turns out that Mercurial chokes on that when the locale is not present. |
Thank you for your report, the issue you have reported has just been fixed.
|
Describe the bug
If the full name contains an accent, weblate shows modification on the repository but does not commit them.
Server configuration and status
Additional context
The repository is using mercurial.
The text was updated successfully, but these errors were encountered: