Yarn gets 404 for package tar.gz but file exists

[JonathanWolfe]

What is the current behavior?
Yarn errors out during install with an HTTP 404 for the url: https://codeload.github.com/PolymerElements/test-fixture/tar.gz/26118ef0467501c33c02316e7016a2837baba10f

If the current behavior is a bug, please provide the steps to reproduce.

1. yarn add web-component-tester@<6.0.0

What is the expected behavior?
Yarn correctly resolves the URL

Please mention your node.js, yarn and operating system version.

• node: v8.2.1
• yarn: v0.27.5
• Bash on Ubuntu on Windows
• Windows 10 Enterprise v1703 Build 15063.483

[rally25rs]

Should that be yarn add instead of install? I just tried yarn add web-component-tester@<6.0.0 in a clean/new project and it seemed to work fine, but I'm on OSX. Not sure if it would really make a difference though. That seems like an odd URL. That isn't where Yarn would normally try to download a package from. I wonder if there is a custom install script at play here?

[JonathanWolfe]

Yes, it should have been.

The issue seem isolated to Bash on Ubuntu on Windows as running the command in other environments works fine.

I'm gonna try it when I get home to see if it's the office proxy.

[tommoor]

Do you have always-auth=true set? in our case that seems to cause this to happen.

[stewx]

I have this same problem, for a file that totally exists and I can manually download using curl, for example:
error An unexpected error occurred: "https://codeload.github.com/types/npm-yn/tar.gz/ca75f6c82940fae6a06fb41d2d37a6aa9b4ea8e9: Request failed \"404 Not Found\"".

I am also using yarn 0.27.5 and cannot upgrade because of bug #4451

[brianpeiris]

See also #4042

[valscion]

This issue should have been fixed by #5216. That PR had a description containing this:

Fixes #4157, #4451, #4672, #4119.

and that caused GitHub to only close #4157 automatically when that PR was merged. The other issues should've probably been closed as well.