ERR_PNPM_TARBALL_EXTRACT about pnpm HOT 13 OPEN

@zkochan , @rstacruz , @gluxon , could anyone of you or the rest of the pnpm team help resolve this blocker ASAP? Thanks for your help!

from pnpm.

Is the current latest pnpm version (v8.15.1) the right version to try reproducing? The pnpm version in the issue report is blank. Giving a similar test on macOS, I don't see an ERR_PNPM_TARBALL_EXTRACT error.

from pnpm.

I'm realizing others have seen this issue recently. #7529

There should be a bit more to the log output. Could that be shared? For example, others in the issue linked above are seeing:

 ERR_PNPM_TARBALL_EXTRACT  Failed to unpack the tarball from "https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz":
  TypeError: object null is not iterable (cannot read property Symbol(Symbol.iterator))

 ERR_PNPM_TARBALL_EXTRACT  Failed to unpack the tarball from "https://[our_private_npm]/@yarnpkg/parsers/-/parsers-3.0.0-rc.48.1.tgz":
  Error: Invalid checksum for TAR header at offset 208384. Expected 0, got 5578

Thanks!

from pnpm.

Is the current latest pnpm version (v8.15.1) the right version to try reproducing? The pnpm version in the issue report is blank. Giving a similar test on macOS, I don't see an ERR_PNPM_TARBALL_EXTRACT error.

yes. pnpm 8.15.1 is the version where we ran into the issue @gluxon @zkochan

from pnpm.

Is the current latest pnpm version (v8.15.1) the right version to try reproducing? The pnpm version in the issue report is blank. Giving a similar test on macOS, I don't see an ERR_PNPM_TARBALL_EXTRACT error.

It happens when we install pnpm and then install packages with pnpm install

from pnpm.

Thanks. How about the other question? Is there more to the ERR_PNPM_TARBALL_EXTRACT error at the bottom of the pnpm install log?

from pnpm.

here is a more in depth screenshot of the issue I'm facing when I run dlp-cli frontend install

from pnpm.

@gluxon see above ^^^

from pnpm.

Thanks. There's still a bit more that would be helpful to debug: The pnpm install command will eventually fail and show more details about what caused ERR_PNPM_TARBALL_EXTRACT. See #7529 for an example of more complete logs. The command is still running in the screenshots above.

I'm having trouble reproducing on my end, so help would be appreciated!

from pnpm.

Might be an issue with the registry. It is unlikely that pnpm would fail to extract so many different packages. I've seen this error in other issues and it is always only one of the packages that is broken somehow. So, my assumption is that this would also fail with npm CLI or Yarn.

To see the error earlier, you can set fetch-retries=0 in .npmrc

from pnpm.

Hey @zkochan and @gluxon, it was taking really long to generate but this is the error that's showing up at the end of the chain of warnings. Is there any way to fix this? We've already tried hard reseting our environment and pnpm.

from pnpm.

@Omanshb Is there anything strange about that file path or the folders leading up to it?

❯ cd ~/Library/pnpm/store/v3/files/78

❯ ls -l

I'm not sure what we're looking for specifically, but to seed a few questions:

• Does the file path exist? (I'm guessing it does not.)
• Is the parent folder owned by your user? (i.e. omanshbainsla)
• Is the parent folder (or any leading up to it) owned by admin? I'd guess something like that could happen if sudo pnpm install was ran in the past.
• Can you create files in that folder? I'd try touch test && rm test.

from pnpm.

We need to fix error reporting. Currently a lot of different unrelated errors are thrown with the ERR_PNPM_TARBALL_EXTRACT error code. In this case the real error code is EACCESS. As a result, people are posting unrelated issues to the same open issues.

from pnpm.