-
Notifications
You must be signed in to change notification settings - Fork 1
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
maven-metadata.xml hashes can't reliably be checked for Yarn #10
Comments
Thanks for reporting this, I'll probably migrate yarn (and maybe also intermediary?) to the metadata api, but Idk when I'll get some time for this |
I've disabled checking hashes for yarn metadata for now |
I am running into this issue too with my modpack. stackdeobfuscator sees hash mismatches and doesn't load the mappings, which makes reading the error logs I'm getting from players quite a bit harder to read. Due to said modpack being quite complex I am unfortunately stuck on 1.20.1. Is there a chance the fix could be backported to that version? |
The fix will be available for 1.20.1 As this mod only uses very simple injection points, it can be used with 1.14 to 1.20.6 (so 1.20.1 too) |
great to hear. for now I've switched the configs for my modpack to use quilt mappings despite being on fabric, and now it seems to be working as it should. |
Describe the bug
When trying to download the mod for the first time when a Yarn update has recently been pushed,
https://maven.fabricmc.net/net/fabricmc/yarn/maven-metadata.xml.sha256
may return two or more different hashes. This prevents Stack Deobfuscator from downloading the mappings successfully. In my testing, this was happening for up to an hour after they pushed an update, and I was unable to install Stack Deobfuscator on multiple servers during this period.Proposed solutions
I spoke to modmuss in the Fabric Discord about the issue, as it also affected some of our internal tooling. They had two suggestions:
Use the metadata API
Fabric has an API for fetching version metadata, which is used by their launchers: https://meta.fabricmc.net/
This API isn't vulnerable to the same caching issues. You can get the latest yarn version by calling
GET https://meta.fabricmc.net/v2/versions/yarn
.Don't check the hash
modmuss's other suggestion in the Fabric discord was to not check the hash of maven-metadata.xml. While they could tighten up cache timings on their side, this is kind of a design flaw in maven that can't be fully solved on Fabric's end.
Logs
Error log
The text was updated successfully, but these errors were encountered: