Skip to content
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

Error when attempting to run ferium list -v #415

Closed
1 task done
PurPur134 opened this issue May 6, 2024 · 5 comments
Closed
1 task done

Error when attempting to run ferium list -v #415

PurPur134 opened this issue May 6, 2024 · 5 comments
Labels
priority I am working on it, or will soon

Comments

@PurPur134
Copy link

Description

If you have a profile that contains a mod that was added via Modrinth and has a license that links to a different website, such as Github, as opposed to most other mods, whose licenses are embedded within Modrinth, and then try to run ferium list -v, it throws an error:

error decoding response body: invalid type: null, expected a string representing a URL at line 1 column x,

where x is some seemingly random number each time the command is run. An example of this is when using the mod Entity Culling, whose owner has issued a custom license they have created themselves and use for almost all of their other mods.

Steps to reproduce

  1. Make sure you have created a profile
  2. Add a mod from Modrinth that has a "unique" license that links to a different page, such as Entity Culling
  3. Run ferium list -v
  4. Expected verbose information about the mod, instead got error

Operating System

Windows

Are you using the latest version of ferium?

  • I am using the latest version of ferium

Additional Information

No response

@PurPur134 PurPur134 added the bug label May 6, 2024
@theRookieCoder theRookieCoder added the priority I am working on it, or will soon label May 10, 2024
@PurPur134
Copy link
Author

Appears to be fixed now; the verbose list now shows and the license for the mod is shown as "Custom" with the link to it in parentheses. I didn't update it or anything or install a new build, and I couldn't find any commits to the repo since the creation of this issue that would have affected this. I also found that a much more popular mod, Sodium, also has its own custom license.

However, I did notice that mods added via CurseForge project IDs did not have a line for their license, let alone the license itself, regardless of whether or not it was custom (all licenses appear to be embedded within the site), so perhaps there should be an issue opened for adding that functionality.

@theRookieCoder
Copy link
Collaborator

theRookieCoder commented Jun 10, 2024

Appears to be fixed now

Hmm I do remember looking into this issue and confirming that it was a bug. I quite don't remember what the issue was though The problem was the field with the link for custom licences didn't exist.

shown as "Custom" with the link to it in parentheses

That is exactly the intended behaviour, it's how I programmed it to show up.

I also found that a much more popular mod, Sodium, also has its own custom license.

They previously had a FOSS licence, but the developers' work was exploited by some people, who reuploading the mod without permission and monetised it. They relicensed the project recently, you can read more about it at CaffeineMC/sodium#2400.

mods added via CurseForge project IDs did not have a line for their license

I have no idea how the website does it, but the third-party API exposed to us does not have any licence information.

@theRookieCoder theRookieCoder closed this as not planned Won't fix, can't repro, duplicate, stale Jun 10, 2024
@PurPur134
Copy link
Author

Why did it just suddenly start working as intended again though? As I said, I didn't install a new version or build of ferium. Did one of the repos it relies on, like libium or furse, or the Modrinth API update?

@theRookieCoder
Copy link
Collaborator

theRookieCoder commented Jun 10, 2024

I'm pretty sure there was a change on the server side. I actually checked modrinth/labrinth for any recent relevant changes but didn't find any, so I believe it's something related to their internal database itself. I can ask the team if you're interested in finding out.

@PurPur134
Copy link
Author

Sure, go ahead. I'd really like to know the root of this problem, so thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority I am working on it, or will soon
Development

No branches or pull requests

2 participants