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

Badge Image Links Not Working #23

Open
Davoleo opened this issue Aug 31, 2019 · 5 comments
Open

Badge Image Links Not Working #23

Davoleo opened this issue Aug 31, 2019 · 5 comments

Comments

@Davoleo
Copy link

Davoleo commented Aug 31, 2019

once again lul :P
Old issue: #12

image

@way2muchnoise
Copy link
Owner

Main endpoints are working again since 16e24e1, need to figure out how to do all the pack related stuff

@BitBlitObviMormon
Copy link

CurseForgeBadge errors

What did these look like originally? I might be able to help, but I have no idea what they're supposed to look like in the end.

@way2muchnoise
Copy link
Owner

They used to be counters for dependencies and dependants.
/packs -> how many packs is your mod?
/mods -> how many mods depend on your mod?
/supported -> how many mods integrate with your mod?

Used to be based of the relations tab on CurseForge, but I haven't seen a way to get this info over the CF API.

@ramazansancar
Copy link

@way2muchnoise
The place where you get the 500 error seems to be the curseforge API service. My guess is that it is stuck on a limit such as rate limit and that is why the problem occurs.

My solution suggestion is to create a cache system and provide recurring requests with a cache held by disk or RAM.

@ramazansancar
Copy link

I witnessed a similar problem on the readme page of the ATM-9 Package, seeing that the first packages were installed but the last package was not.

When I refreshed the page again, the last package arrived.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants