ferium scan does not work if either API is unavailable

[DasPauluteli]

Description

At the time of this writing, the Curseforge API is unavailable: '503 Service Temporarily Unavailable'
I tried to scan a mod folder and update current mods with Ferium. Both failed. Even when using "--platform modrinth", Ferium still encounters an error.

Steps to Reproduce

Running ferium scan --platform modrinth outputs the following
HTTP status server error (503 Service Unavailable) for url (https://api.curseforge.com/v1/fingerprints), although Modrinth is selected as the primary source and is accessible.

Operating System

Linux

Installation Method

Pacstall

Ferium version

ferium 4.7.1

Additional Information

No response

[DasPauluteli]

To clarify: I primarily use Modrinth and use Ferium to keep my dedicated Minecraft server up to date. Therefore, it does not make sense to me that Ferium does not function when the Curseforges API is down.

[theRookieCoder]

This issue is specific to the scan subcommand. The way the platform flag currently works is that it provides a preference, so when you specify --platform modrinth ferium still queries both curseforge and modrinth, but it just picks modrinth whenever a mod is available on both. That means if a mod is only available on curseforge it'll still get added.

The solution is to provide more configuration to allow excluding a platform, or to ignore the error when a platform that's not preferred errors out.