Control: tags -1 pending
On Tue, Dec 22, 2020 at 1:20 pm, Akshay S Dinesh
wrote:
gbp:error: upstream/1.22.10+_cs18.39.16 is not a valid treeish
indeed your fork only has 33 tags, whereas js-team/node-yarnpkg has
37.
Please pull those tags and push them to your fork, then force
restart
gbp:error: upstream/1.22.10+_cs18.39.16 is not a valid treeish
indeed your fork only has 33 tags, whereas js-team/node-yarnpkg has 37.
Please pull those tags and push them to your fork, then force restart the CI
pipeline.
This would help us to see if your proposed fix works.
Pushing
Hi Akshay, many thanks for the debugging ! see below
Il 22/12/20 06:06, Akshay S Dinesh ha scritto:
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
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
> >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
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
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
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 think the real issue is that it does not pull not-yet-cached modules.
To reproduce:
# clear cache
rm -rf ~/.cache/yarn
# actual test
8 matches
Mail list logo
