You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Coming here after fighting with LibreTranslate for hours and attempting to figure out why or what is causing startup to be incredibly slow. Like, insanely so. In my search, I came across this project here as a dependency and within the Settings.md, I got to find ARGOS_DEBUG=1.
But...even so, and with a little bit of hacking and smacking an installation together under uv/uvx, I get to this:
...and this is the state since two hours. That shouldn't be the problem, because I am on a legit 600/300mbit/s up/down link (FTTH).
Any other methods to "debug" this?
I have been trying on...
Windows, Ryzen 9 3900X, py3.11.x, x86_64
Linux, Debian 12 (Armbian), RockChip RK3588 (armv8/aarch64), Docker image (both from Docker hub and self built)
Linux, Ubuntu 24.04, 4 vCPU cores of an Ampere CPU (hoster wouldn't say which skew) (aarch64), Docker with image from hub and self built
That last node was the most successful but with 4c/4t, and 8GB RAM and a small remaining rootfs storage, I did only run it there to see if it worked or not.
Thanks in advance!
Kind regards,
Ingwie
The text was updated successfully, but these errors were encountered:
export ARGOS_DEBUG=1; argospm install translate-nl_en results in a similar error as the OP stated: ('Get https://argos-net.com/v1/translate-nl_en-1_8.argosmodel',)
Hello!
Coming here after fighting with LibreTranslate for hours and attempting to figure out why or what is causing startup to be incredibly slow. Like, insanely so. In my search, I came across this project here as a dependency and within the
Settings.md
, I got to findARGOS_DEBUG=1
.But...even so, and with a little bit of hacking and smacking an installation together under uv/uvx, I get to this:
...and this is the state since two hours. That shouldn't be the problem, because I am on a legit 600/300mbit/s up/down link (FTTH).
Any other methods to "debug" this?
I have been trying on...
That last node was the most successful but with 4c/4t, and 8GB RAM and a small remaining rootfs storage, I did only run it there to see if it worked or not.
Thanks in advance!
Kind regards,
Ingwie
The text was updated successfully, but these errors were encountered: