-
-
Notifications
You must be signed in to change notification settings - Fork 166
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
Github Download Zip Truncation BUG / 404 #81
Comments
Hi @CollinChaffin! Thanks for reporting this issue. I was grabbing the truncated text. It's been fixed in the latest release. |
Hi @Mottie Rob! Thanks so much for looking at this so quickly! I just tested it and as cool as the new addition of the latest release at the bottom of the zip dropdown is, I think there is a new bug related to this addition as well as more importantly the main repo ZIP link seems to now no longer work on any repo, and seems to produce this redirect URL (again adding this weird legacy.zip into the base URL) but now also referring to "switching branches or tags"?: Example Repo: Main repo ZIP link nav bar URL (404) which appears to be common to all repos I've tested so far when attempting to download repo via main Secondary (new) behavior (bug?) specific to only one scenarioWhen a repo DOES have any releases tagged (other than source code), the new dropdown Example repo: Thanks again for these awesome features! Just having the zip ball including the commit (the part not working) has become an invaluable time saver! |
Hi! Hmm, yeah. I guess I need to find a better source to get the current branch. As for the lastest release files dropdown, that should be fixed in a release I just made less than an hour ago. |
Ok, try it now. |
Hey Rob @Mottie! Looks awesome now! The only thing to possibly just note in release notes etc. or if anyone asks, is that the addition of the latest official tagged releases will not reflect a "source code" release. This makes perfect sense to me; however what does NOT make sense to me is why GH ever allows categorizing nothing more than a source zipball which in essence is identical to the front page download to increment the usual As an example, this repo Thanks again for this! -C |
Not sure if this is a recent change, but recently have hit instances where weird truncation is occurring due to branch names, which in turn causes an erroneous 404 and failure.
Here is one example I just hit, where disabling the userscript results in the branch zip download success:
https://github.com/hoppfrosch/Clipjump/tree/hoppfrosch/feature/class_clipjumpdb
With the Zip userscript disabled, the repo zip ball download is:
https://github.com/hoppfrosch/Clipjump/archive/hoppfrosch/feature/class_clipjumpdb.zip
But with the zip userscript enabled, an inspect reveals the link becomes:
https://api.github.com/repos/hoppfrosch/Clipjump/zipball/hoppfrosch/fea…
Which oddly results in the redirect and eventual 404 error and the address bar value of:
https://codeload.github.com/hoppfrosch/Clipjump/legacy.zip/hoppfrosch/fea%E2%80%A6
Note the weird addition of
legacy.zip
in the final redirect url - does that make any sense to you?It's obvious what's happening in the truncation, but without a lot of digging I'm not clear on exactly where in the code it's being thrown off or a root cause, but I'm sure you'll take one look and probably have a good idea. Note I've only seen this occur on longer-named branches other than master.
The text was updated successfully, but these errors were encountered: