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

yarn can not get integrity value #6676

Open
junchen1 opened this issue Nov 14, 2018 · 4 comments
Open

yarn can not get integrity value #6676

junchen1 opened this issue Nov 14, 2018 · 4 comments
Assignees
Labels

Comments

@junchen1
Copy link

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

It's a bug.

E:\React1>yarn
yarn install v1.12.1
[1/4] Resolving packages...
[2/4] Fetching packages...
error https://outlookweb.pkgs.visualstudio.com/_packaging/owa-npm/npm/registry/@microsoft/load-themed-styles/-/load-themed-styles-1.7.73.tgz: Integrity check failed for "@microsoft/load-themed-styles" (computed integrity doesn't match our records, got "sha1-2jmj7l5rSw0yVb/vlWAYkK/YBwk=")

Yarn failed to get the integrity value from network package.

How can I get the above issue fixed?
Even after I manually clear yarn cache folder, the following cmd also fails.
E:\React1>yarn cache clean
yarn cache v1.12.1

<--- Last few GCs --->

[9480:000002B86B71D500] 69592 ms: Scavenge 1389.1 (1423.6) -> 1388.2 (1424.1) MB, 3.5 / 0.0 ms (average mu = 0.221, current mu = 0.193) allocation failure
[9480:000002B86B71D500] 69598 ms: Scavenge 1389.2 (1424.1) -> 1388.3 (1424.6) MB, 3.3 / 0.0 ms (average mu = 0.221, current mu = 0.193) allocation failure
[9480:000002B86B71D500] 69605 ms: Scavenge 1389.2 (1424.6) -> 1388.3 (1425.1) MB, 3.5 / 0.0 ms (average mu = 0.221, current mu = 0.193) allocation failure

<--- JS stacktrace --->

==== JS stack trace =========================================

0: ExitFrame [pc: 000000C198ED0361]
1: StubFrame [pc: 000000C198E8E03A]

Security context: 0x012f1ae1d949
2: resolve [0000018C79802201] [path.js:~138] [pc=000000C198FC4437](this=0x036c07082219 )
3: arguments adaptor frame: 1->0
4: afterGlob [000001A00278DBA9] [C:\Program Files (x86)\Yarn\lib\cli.js:~126638] [pc=000000C198FD2C41](this=0x01f52f204df1 ,0x00a294c822...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 00007FF63FB521C5
2: 00007FF63FB2A056
3: 00007FF63FB2AA40
4: 00007FF63FF7499E
5: 00007FF63FF748D7
6: 00007FF64024D804
7: 00007FF640243444
8: 00007FF640241B18
9: 00007FF64024B487
10: 00007FF64024B506
11: 00007FF63FE0C311
12: 00007FF640566DEA
13: 000000C198ED0361

What is the current behavior?

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

What is the expected behavior?

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

@ghost ghost assigned kaylie-alexa Nov 14, 2018
@ghost ghost added the triaged label Nov 14, 2018
@MLoughry
Copy link

One important note: "sha1-2jmj7l5rSw0yVb/vlWAYkK/YBwk=" is the result you get when hashing null

@rally25rs
Copy link
Contributor

@imsnif is this related to the integrity work that you did a few months back?

@imsnif
Copy link
Member

imsnif commented Nov 17, 2018

The error is. I think what's happening here is that we're trying to calculate the integrity of null (as @MLoughry mentioned) and comparing it to our local integrity of, well... not null. :)
I don't know about the yarn cache clean error, but I'd imagine this would be fixed as soon as network connectivity comes back, wouldn't it? The heap issue is alarming, but I don't think it's related.

@junchen1
Copy link
Author

when it happens, my network seems totally fine.

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