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

[Composer\Downloader\TransportException] file could not be downloaded, got redirect without Location (HTTP/1.1 300 Multiple Choices) #437

Open
nigelwhite opened this issue Feb 14, 2022 · 18 comments

Comments

@nigelwhite
Copy link

I did
composer require --dev drupal/core-dev:8.9.20 --update-with-all-dependencies
Composer starts installing stuff but then errors

[Composer\Downloader\TransportException]                                                                                                                 
  The "https://github.com/dargullin/icheck/archive/1.0.2.zip" file could not be downloaded, got redirect without Location (HTTP/1.1 300 Multiple Choices)
@MatrixOfDeath
Copy link

Having same issue, a patch is out here for webform contrib module who is requiring this jquery/icheck library : https://www.drupal.org/project/webform/issues/3264249

@prudloff-insite
Copy link

prudloff-insite commented Feb 14, 2022

This potentially breaks the deployment of tens of thousands of websites using the webform module for Drupal.
The root cause is that https://github.com/dargullin/icheck/archive/1.0.2.zip returns this weird error:

the given path has multiple possibilities: #<Git::Ref:0x00007f0f498260b8>, #<Git::Ref:0x00007f0f49825b68>

Edit: the problem is caused by the fact that 1.0.2 is both a tag and a branch

@LaravZ
Copy link

LaravZ commented Feb 14, 2022

@prudloff-insite installing the patch (for webform 6.1.2 at least) will resolve the issue for now as long as you make sure the composer lock file is updated correctly. I would not be surprised if updating webform will be the solution to this problem since the webform module links to github/fronteed which in turn links to this repo.

@prudloff-insite
Copy link

The webform patch does indeed fix the issue but it will require patching a lot of websites.
In the mean time, renaming the 1.0.2 branch could instantly fix the problem for everyone.

@jcnventura
Copy link

Please remove the branches with the same name as tags.. A tag can be somewhat considered a 'named branch'. If you ever need to checkout 1.0.1 simply do that: git checkout 1.0.1. It just works.

Deleting the 1.0.2 and 1.0.3 branches will fix the Github release URLs: https://github.com/dargullin/icheck/archive/1.0.2.zip

@AnnoyedDeveloper
Copy link

AnnoyedDeveloper commented Feb 14, 2022

To the team managing this project:

This issue causes a big problem while upgrading a Drupal website to v9.

Please fix this right away.

@mgbellaire
Copy link

This is breaking the developer workflow of anyone trying to use this package. Please remove the branches for 1.0.2 and 1.0.3.

@belray
Copy link

belray commented Feb 14, 2022

this patch for webform worked for us
https://www.drupal.org/files/issues/2022-02-14/3264249-6.2.x.patch

@neclimdul
Copy link

@dargullin sorry for the direct ping but this is still broken.

@z3cka
Copy link

z3cka commented Feb 23, 2022

I also got bit by this today. Please fix.

@ericjgruber
Copy link

Having the same issue.

@z3cka
Copy link

z3cka commented Feb 24, 2022

Removing icheck's entry in my project's composer.lock file and then re-running composer install fixed the issue for me.

@belray
Copy link

belray commented Feb 24, 2022 via email

@cherouvim
Copy link

Please remove the branches.

@timcorkerton
Copy link

Same here, please remove branches

@munsinator
Copy link

Same issue.

@jaylenw
Copy link

jaylenw commented Apr 21, 2022

In the composer.lock file I tried replacing https://github.com/fronteed/icheck/archive/1.0.2.zip with https://github.com/dargullin/icheck/archive/refs/tags/1.0.2.zip and it worked when running composer install. It is not a perfect solution. Got the idea from https://www.drupal.org/project/webform/issues/3264249#comment-14422171

@andykillen
Copy link

yep, same here for both Drupal 8 and Drupal 9. gonna go with @jaylenw hack, its not nice but it works. Better if you re-name the branches not to be the same as the tags.

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

No branches or pull requests