[Pkg-javascript-devel] Bug#977781: Bug#977781: real issue is, it does not pull not-yet-cached modules

2020-12-21 Thread Akshay S Dinesh


There are some 4 pipes before the finish event. I'm looking through each 
one of them to see if there's a mismatch.




It seems to be tar-fs

Please see https://salsa.debian.org/js-team/node-yarnpkg/-/merge_requests/4

I've just downloaded the latest version from the github of tar-fs and 
replace in the directory. Not sure if this is the way to do it.


--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#977781: Bug#977781: real issue is, it does not pull not-yet-cached modules

2020-12-21 Thread Akshay S Dinesh
 > >I think the real issue is that it does not pull not-yet-cached 
modules.

 >


I did some console.log debugging yesterday.

The tarball-fetcher, for whatever be the reason, doesn't ever trigger 
the .on('finish' event


https://salsa.debian.org/js-team/node-yarnpkg/-/blob/master/src/fetchers/tarball-fetcher.js#L164

There are some 4 pipes before the finish event. I'm looking through each 
one of them to see if there's a mismatch.


--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#977781: Bug#977781: real issue is, it does not pull not-yet-cached modules

2020-12-21 Thread Pirate Praveen
On Mon, 21 Dec 2020 14:24:57 +0530 Pirate Praveen 
 wrote:
> >I think the real issue is that it does not pull not-yet-cached 
modules.

>
> I think the failure is after it downloaded. I can see some files in 
~/.cache/yarn created after it is cleaned after yarnpkg add. Could it 
be a problem with extracting the tar ?


You were correct, these are empty directories, so the failure seems to 
be in downloading.


$ ls ~/.cache/yarn/v6/
npm-d3-color-2.0.0-8d625cab42ed9b8f601a1760a389f7ea9189d62e-integrity
pravi@mahishi:/tmp$ rm -rf ~/.cache/yarn/v6/
pravi@mahishi:/tmp$ yarnpkg add d3-color
yarn add v1.22.10
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[-] 0/1pravi@mahishi:/tmp$ ls ~/.cache/yarn/v6/
npm-d3-color-2.0.0-8d625cab42ed9b8f601a1760a389f7ea9189d62e-integrity
pravi@mahishi:/tmp$ ls 
~/.cache/yarn/v6/npm-d3-color-2.0.0-8d625cab42ed9b8f601a1760a389f7ea9189d62e-integrity/

node_modules
pravi@mahishi:/tmp$ ls 
~/.cache/yarn/v6/npm-d3-color-2.0.0-8d625cab42ed9b8f601a1760a389f7ea9189d62e-integrity/node_modules/

d3-color
pravi@mahishi:/tmp$ ls 
~/.cache/yarn/v6/npm-d3-color-2.0.0-8d625cab42ed9b8f601a1760a389f7ea9189d62e-integrity/node_modules/d3-color/

pravi@mahishi:/tmp$

--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#977781: Bug#977781: real issue is, it does not pull not-yet-cached modules

2020-12-21 Thread Pirate Praveen


On 2020, ഡിസംബർ 21 1:46:31 PM IST, Paolo Greppi  wrote:
>Hi Pirate,
>
>what you want to put in ~/.yarnrc.yml could be installed globally to 
>/etc/yarn/config or /etc/yarnrc, but that does not actually fix it.

I agree, I wanted to see if it can be used to update to yarn 2 (so yarnpkg just 
becomes an installer for yarn 2). I was able to use yarn 2 successfully in 
gitlab.

This commit makes the switch to yarn 2.

https://salsa.debian.org/ruby-team/gitlab/-/commit/43df5d0233cef3936b3d5abab334c5fdeeafa717

>I think the real issue is that it does not pull not-yet-cached modules.

I think the failure is after it downloaded. I can see some files in 
~/.cache/yarn created after it is cleaned after yarnpkg add. Could it be a 
problem with extracting the tar ?

>To reproduce:
>
>   # clear cache
>   rm -rf ~/.cache/yarn
>   # actual test
>   cd `mktemp -d`
>   yarnpkg init -y
>   yarnpkg add d3-color
>
>Adding the nodeLinker: "node-modules" option to ~/.yarnrc.yml or the global 
>locations does not help.

It helps if you switch to yarn 2 by running yarnpkg set version berry. See the 
patch linked above for gitlab. It was failing with yarn 1, but worked after 
switching to berry.

We cannot set version to berry globally, it has to be set per project.

>It would be interesting to debug the JavaScript execution after it prints 
>"Fetching packages..."
>

I think we need to revert this patch and fix the error.

https://salsa.debian.org/js-team/node-yarnpkg/-/commit/c122f5c26eefb0b68e0c680eb0d65aae86ef4f9e
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel