Weblate 4.3.x bug?

[mareksuscak]

Ever since we upgraded to Weblate 4.3, we've been getting the "too many open files" error which we have never seen before and we've been using Weblate for years. I ran git gc a number of times and we have not added new repositories or translations in a long while so the environment is the same. It seems that 4.3 introduced some change and possibly a leak that's causing it.

There's also one more issue we're running into where Weblate keeps removing our non-primary translations from one of the projects and the only change we did there is that we changed the file pattern and the file pattern includes a + character.

Something along these lines:

translations/messages+intl-icu.*.yaml

I wonder if this has to do anything with the "too many open files" issue and also why weblate keeps removing those translations. For more context, when I click Add Translation and select the missing languages, they're added no problem and also the strings from those files are added successfully to weblate database (though I don't know if weblate displays the old entries from before the renaming).

I'd appreciate any help.

[nijel]

The issue with + in mask will be addressed in 4.3.2 and is fixed by 155b489.

Too many open files is unrelated and I haven't seen it so far, can check which files have the process open?

[mareksuscak]

We're running the official Docker container on Kubernetes (GKE) and lsof is not available in the slim version of the Debian docker image. I guess I need to build a custom docker image w/ lsof utility or is there any other way in your knowledge?

[nijel]

You can install anything during the container runtime: apt update && apt install lsof

You can also list the process open files in proc filesystem by looking at /proc/<PID>/fd (but that won't give much information on sockets).

[mareksuscak]

I can't because the container is not running as root and kubectl exec does not support switching users yet.

[nijel]

Ah okay, I thought it works same as with pure docker. Anyway the proc filesystem should still work and would give an answer in case these are real files and not sockets...