-
Notifications
You must be signed in to change notification settings - Fork 6
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
New LanguageTool release 6.4 #29
Comments
Thank you for the reminder. I just pushed the updated image. |
It seems the built-in healthcheck is broken. My instance was on "auto-update" and in a restarting frenzy since yesterday when it updated to the new version. |
Even after disabling the healthcheck it was stuck on 100% CPU and wasn't working. I couldn't see any errors in the logs so I went back to |
Interesting observation. I am not sure why you experience what you experience. On my container host it makes no difference whether I use 6.4 or 6.3a-5. Have you tried setting the environment Can you share your compose file, so I can try to reproduce with your exact settings? |
Well, let me add a few words before sharing the compose file. I use autoheal, to restart unhealthy containers. When the healthcheck of LanguageTool broke, autoheal continued restarting it. I tried disabling the healthcheck with:
Which did the trick, except it was stuck on 100% CPU and wasn't working o I went back to meyay/LanguageTool:6.3a-5 and all is perfectly working again. I will gladly try with the log-level set to debug this evening and report back. Here is my docker-compose.yml in case you can spot something wrong there.
|
OK, I switched back to the latest tag with LOG_LEVEL=DEBUG. The healthcheck fails, CPU usage is pretty high even after this. LT is not reachable. I don't see anything useful in the logs are some excerpts, the rest is just more of the same. Not sure why Russian is mentioned here at all, I don't speak or read it, and it's not selected in my Chrome extension to be checked!? I am the only user of this instance. I checked the logs, there really is nobody else accessing it. Disabling the healthcheck does nothing, same behaviour as described above. Switching back to image:
|
I tried your compose file and it indeed results in cpu utilization, which might be related to the prewarming, which seems wanting to load the ngrams of all known languages.
The CPU utilization gets even worse if you set the environment variable If you comment out the custom configuration for the prewarming, the cpu clogging disappears. Please feel free to ask anything regarding the mechanics of the image itself, but when it comes to the implementation of LanguageTool itself, I can only suggest that you raise an issue in the LanguageTool Github repository and file a bug report for version 6.4. |
Thanks for having a look, I totally understand it's related to LT, so I will check out their forums and reply here if there are any results. |
Btw. I set I opened my own thread on the LT page here: languagetool-org/languagetool#10488 |
Can I close this issue, as it's not really related to the image mechanics itself? |
Sure, thanks for asking and taking the time to look into it. |
Hi.
Just to notify that a new LanguageTool version has been released: https://github.com/languagetool-org/languagetool/blob/master/languagetool-standalone/CHANGES.md#64-2024-03-28
The text was updated successfully, but these errors were encountered: