vue: ENOENT: no such file or directory
Closed, ResolvedPublic
Actions

Description

I'm seeing this error on repeated attempts to +2 a patch for ReportIncident:

21:34:27 npm ERR! invalid json response body at https://registry.npmjs.org/vue reason: Invalid response body while trying to fetch https://registry.npmjs.org/vue: ENOENT: no such file or directory, stat '/cache/_cacache/content-v2/sha512/10/7b/e370427ffe4e193775a1c2853769e5522a871ec504b60c8481eba2f574ce60c68cf1d8bdfebb25aefcdcd3946a1ff387fba3fd5158a08988a9bb3293eb02'

See https://integration.wikimedia.org/ci/job/mwgate-node16-docker/82126/console

Related Objects

Mentioned In: T358312: Wikibase CI blocked by castor cache corruption issue
T352305: Multiple extensions' CI blocked again by cache corruption error in mwgate-node16-docker
T348243: Wikibase CI is broken
Mentioned Here: T295351: npm cache saved by castor get corrupted for unknown reason

Event Timeline

kostajh created this task.Oct 29 2023, 8:44 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 29 2023, 8:44 PM

kostajh added subscribers: hashar, Dreamy_Jazz.Oct 29 2023, 8:45 PM

Dreamy_Jazz triaged this task as High priority.Oct 29 2023, 8:56 PM

Dreamy_Jazz added a project: Incident-Reporting-System.Oct 29 2023, 9:05 PM

Restricted Application added a project: Trust and Safety Tools Team Backlog. · View Herald TranscriptOct 29 2023, 9:05 PM

Affects GrowthExperiments as well.

It looks like we might be rate limited at the registry's side or something? The URL, https://registry.npmjs.org/vue, works on my end with no issues. Tagging CI infra and releng as such.

Jakob_WMDE subscribed.Oct 30 2023, 10:58 AM

Muhammad_Yasser_Jazirahly_WMDE subscribed.Oct 30 2023, 11:11 AM

Mentioned in SAL (#wikimedia-releng) [2023-10-30T11:18:39Z] <hashar> integration-castor05: clearing corrupted npm cache: sudo rm -fR /srv/castor/castor-mw-ext-and-skins/master/mwgate-node16-docker # T349986

That is the CI central cache (Castor) being corrupted, most probably due to a race condition of a build fetching a cache that is being updated by another build :/ I have cleaned out that cache.

Thanks for fixing this. The problem is no longer present on gate-and-submit for the ReportIncident extension.

Lucas_Werkmeister_WMDE mentioned this in T348243: Wikibase CI is broken.Oct 30 2023, 11:49 AM

Thanks!

I don't know if this is the same root issue:

21:04:33 npm ERR! code E500
21:04:33 npm ERR! 500 Internal Server Error - GET https://registry.npmjs.org/@vue/shared/-/shared-3.2.37.tgz - KV GET failed: 401 Unauthorized

https://integration.wikimedia.org/ci/job/mwgate-node16-docker/82496/console

Mentioned in SAL (#wikimedia-releng) [2023-10-30T20:29:22Z] <James_F> Ran sudo rm -fR /srv/castor/castor-mw-ext-and-skins/master/mwgate-node16-docker/ on integration-castor05 too for T349986

I just ran jforrester@integration-castor05:~$ sudo rm -fR /srv/castor/castor-mw-ext-and-skins/master/mwext-node16-rundoc-docker to clear this out for the mwext-node16-rundoc-docker job; looks like upstream might have flaked and broken everyone briefly? I've now run it for mwgate…-node16- too, which might help?

In T349986#9290736, @hashar wrote:

That is the CI central cache (Castor) being corrupted

(⇒ T295351: npm cache saved by castor get corrupted for unknown reason)

Jakob_WMDE mentioned this in T352305: Multiple extensions' CI blocked again by cache corruption error in mwgate-node16-docker.Nov 29 2023, 3:29 PM

Jakob_WMDE mentioned this in T358312: Wikibase CI blocked by castor cache corruption issue.Feb 23 2024, 9:00 AM

invalid json response body at https://registry.npmjs.org/vue reason: Invalid response body while trying to fetch https://registry.npmjs.org/vue: ENOENT: no such file or directoryClosed, ResolvedPublicActions

Description

Related Objects

Event Timeline

invalid json response body at https://registry.npmjs.org/vue reason: Invalid response body while trying to fetch https://registry.npmjs.org/vue: ENOENT: no such file or directory
Closed, ResolvedPublic
Actions