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

Error on install 404 on https://registry.yarnpkg.com/har-validator/-/har-validator-5.1.2.tgz #6702

Closed
jaimeagudo opened this issue Nov 19, 2018 · 6 comments
Assignees
Labels

Comments

@jaimeagudo
Copy link

Do you want to request a feature or report a bug?

What is the current behavior?

yarn install                                                                                                                                             1 ↵
yarn install v1.12.3
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
error https://registry.yarnpkg.com/har-validator/-/har-validator-5.1.2.tgz: Extracting tar content of undefined failed, the file appears to be corrupt: "Unexpected end of data"

What is the expected behavior?
packages are installed
Please mention your node.js, yarn and operating system version.
node -v
v8.6.0
Mac OS Mojave 10.14 (18A391)

curl -vvv https://registry.yarnpkg.com/har-validator/-/har-validator-5.1.2.tgz
*   Trying 104.16.27.35...
* TCP_NODELAY set
* Connected to registry.yarnpkg.com (104.16.27.35) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-ECDSA-CHACHA20-POLY1305
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=US; ST=CA; L=San Francisco; O=CloudFlare, Inc.; CN=registry.yarnpkg.com
*  start date: May 28 00:00:00 2018 GMT
*  expire date: May 28 12:00:00 2019 GMT
*  subjectAltName: host "registry.yarnpkg.com" matched cert's "registry.yarnpkg.com"
*  issuer: C=US; ST=CA; L=San Francisco; O=CloudFlare, Inc.; CN=CloudFlare Inc ECC CA-2
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7f85c080b600)
> GET /har-validator/-/har-validator-5.1.2.tgz HTTP/2
> Host: registry.yarnpkg.com
> User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)
> Accept: */*
> Referer:
>
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 404
< date: Mon, 19 Nov 2018 12:57:05 GMT
< content-type: application/json
< content-length: 21
< set-cookie: __cfduid=d7e68e92738c0f183986c8126fdb2a49e1542632225; expires=Tue, 19-Nov-19 12:57:05 GMT; path=/; domain=.registry.yarnpkg.com; HttpOnly
< cf-cache-status: MISS
< cache-control: max-age=432000
< cf-ray: 47c2d72e9adb2f3b-MAD
< expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
< server: cloudflare
<
* Connection #0 to host registry.yarnpkg.com left intact
{"error":"Not found"}%

@ghost ghost assigned BYK Nov 19, 2018
@ghost ghost added the triaged label Nov 19, 2018
@jaimeagudo
Copy link
Author

Same happens with v1.12.1

@jaimeagudo
Copy link
Author

Downgrading to 1.10.1 seems to be the workaround atm.

For those curious you can download the official script and pick other versions

curl --compressed -o- -L https://yarnpkg.com/install.sh && chmod +x ./install.sh && ./install.sh --version 1.10.1

@arcanis
Copy link
Member

arcanis commented Nov 19, 2018

@arcanis arcanis closed this as completed Nov 19, 2018
@cooperka
Copy link

On mac: brew switch yarn 1.10.1

@cooperka
Copy link

Deleting yarn.lock and trying again was actually the solution for me.

@giltotherescue
Copy link

I was able to solve this error by running npm login and logging in again.

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

No branches or pull requests

5 participants