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

Checking for pack updates on Modrinth without a project id causes errors #877

Closed
2 tasks done
RyanTheAllmighty opened this issue Feb 27, 2024 · 1 comment
Closed
2 tasks done
Labels
bug Confirmed bugs or reports that are very likely to be bugs. low-priority Low priority to be addressed.

Comments

@RyanTheAllmighty
Copy link
Member

What happened?

When the updater checks for pack updates to Modrinth instances, if there is a missing project ID for some reason, it still attempts to do the call, which will just error out.

We should not be doing the calls to check for updates if either the project or version id's are missing

Operating System

Windows

Relevant log output

[27/02/2024 19:16:30 p.m.] com.atlauncher.network.DownloadException: https://api.modrinth.com/v2/project//version request wasn't successful: Response{protocol=http/1.1, code=404, message=Not Found, url=https://api.modrinth.com/v2/project//version}
	at com.atlauncher.network.Download.execute(Download.java:334)
	at com.atlauncher.network.Download.asTypeWithThrow(Download.java:179)
	at com.atlauncher.network.Download.asType(Download.java:186)
	at com.atlauncher.network.Download.asType(Download.java:200)
	at com.atlauncher.utils.ModrinthApi.getVersions(ModrinthApi.java:242)
	at com.atlauncher.utils.ModrinthApi.getVersions(ModrinthApi.java:192)
	at com.atlauncher.managers.ModrinthModpackUpdateManager.lambda$checkForUpdates$2(ModrinthModpackUpdateManager.java:91)
	at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(Unknown Source)
	at java.base/java.util.stream.ReferencePipeline$2$1.accept(Unknown Source)
	at java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Unknown Source)
	at java.base/java.util.stream.AbstractPipeline.copyInto(Unknown Source)
	at java.base/java.util.stream.ForEachOps$ForEachTask.compute(Unknown Source)
	at java.base/java.util.concurrent.CountedCompleter.exec(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinTask.doExec(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.helpComplete(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinPool.helpComplete(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinTask.awaitDone(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinTask.invoke(Unknown Source)
	at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateParallel(Unknown Source)
	at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateParallel(Unknown Source)
	at java.base/java.util.stream.AbstractPipeline.evaluate(Unknown Source)
	at java.base/java.util.stream.ReferencePipeline.forEach(Unknown Source)
	at com.atlauncher.managers.ModrinthModpackUpdateManager.checkForUpdates(ModrinthModpackUpdateManager.java:90)
	at com.atlauncher.Launcher.lambda$checkForExternalPackUpdates$9(Launcher.java:340)
	at java.base/java.lang.Thread.run(Unknown Source)

Additional Information

No response

Is this actually a launcher bug?

  • I am sure this is a bug with the launcher and not an issue with running Minecraft

Code of Conduct

  • I agree to follow this project's Code of Conduct
@RyanTheAllmighty RyanTheAllmighty added bug Confirmed bugs or reports that are very likely to be bugs. low-priority Low priority to be addressed. awaiting-release Issues where the fix/feature has been merged and is awaiting a release. labels Feb 27, 2024
RyanTheAllmighty added a commit that referenced this issue Feb 28, 2024
@atlauncher-bot
Copy link
Contributor

This has been fixed with version 3.4.35.9

@atlauncher-bot atlauncher-bot removed the awaiting-release Issues where the fix/feature has been merged and is awaiting a release. label Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs. low-priority Low priority to be addressed.
Development

No branches or pull requests

2 participants