Open ItsProfessional opened 1 year ago
Temporary workaround: I made a patch to add a 50ms delay between checking each mod 0001-sleep.patch.txt
This issue is caused by too many requests being made simultaneously, and is sometimes a result of a flaky internet connection. Instead of adding a delay, it should also be possible to decrease the number of threads created (75 by default). When resolving latest versions: https://github.com/gorilla-devs/ferium/blob/340470c9f4fec5030b8bb09c2530dd7a581c7d95/src/download.rs#L122 When downloading mods: https://github.com/gorilla-devs/ferium/blob/340470c9f4fec5030b8bb09c2530dd7a581c7d95/src/subcommands/upgrade.rs#L76
Can you add an option to change that hardcoded 75 value as a command line flag in the next version?
Same issue here; it's made the whole program useless. How did you apply that temporary workaround? Did you recompile after editing the code?
Nevermind, I figured it out! First time compiling something on rust :)
Can we expect a patched release soon? I installed using Homebrew and integrated it into automation and therefore can only use a release available from Homebrew.
I managed to build from source and limit the threads both in the source files and using the "-t" attribute, but am still getting the error ONLY when using "ferium upgrade." Exact command:
ferium -t 1 upgrade
Are there any solutions to this? It can't even download one mod at a time. Listing mods with verbose works, but upgrading does not.
EDIT: I found that the current limit is 64 mods (ironic) from Modrinth. I'm not sure how to implement the cooldown, and limiting the threads does not work for me. I am on macOS (I know, calm down- it's what I have).
are you sure you're using the compiled build? your comment only shows "ferium", without any path. Which means (not sure about mac, but on linux) it will just use the one from your system path, i.e. from your package manager.
I found that the current limit is 64 mods
False. It only started happening for me on about 120 mods iirc.
For me, it was 64 mods, tested on two computers, both running macOS Ventura, one using the latest released version of ferium, and the other using a current compiled version.
are you sure you're using the compiled build? your comment only shows "ferium", without any path. Which means (not sure about mac, but on linux) it will just use the one from your system path, i.e. from your package manager.
I compiled it using Homebrew. I verified that it was using the latest version and modified thread limit I put in place of 25 directly in the code.
Description
When upgrading a ton of modrinth mods, this error occurs. This only started to occur today, it was working fine yesterday.
Steps to reproduce
Operating System
Linux
Are you using the latest version of ferium?
Additional Information
Command output: