Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

platfomio install @ atom error #18412

Closed
1 of 4 tasks
PvlGrd opened this issue Sep 6, 2017 · 1 comment
Closed
1 of 4 tasks

platfomio install @ atom error #18412

PvlGrd opened this issue Sep 6, 2017 · 1 comment

Comments

@PvlGrd
Copy link

PvlGrd commented Sep 6, 2017

I'm opening this issue because:

  • npm is crashing.
  • npm is producing an incorrect install.
  • npm is doing something I don't understand.
  • Other (see below for feature requests):

What's going wrong?

During platformio installation with Atom

How can the CLI team reproduce the problem?

install Atom Version 1.19.5 x64, search for platformio package and try to install it.

supporting information:

Installing “platformio-ide@2.0.0-rc.1” failed.Hide output…

npm ERR! tar.unpack error reading /tmp/d-11785-25944-142tfqt.dqbprpb9/package.tgz
npm ERR! addLocal Could not install /tmp/d-11785-25944-142tfqt.dqbprpb9/package.tgz
npm ERR! Linux 3.8.11
npm ERR! argv "/usr/share/atom/resources/app/apm/bin/node" "/usr/share/atom/resources/app/apm/node_modules/npm/bin/npm-cli.js" "--globalconfig" "/home/redstone/.atom/.apm/.apmrc" "--userconfig" "/home/redstone/.atom/.apmrc" "install" "/tmp/d-11785-25944-142tfqt.dqbprpb9/package.tgz" "--runtime=electron" "--target=1.6.9" "--arch=x64" "--global-style"
npm ERR! node v6.9.5
npm ERR! npm v3.10.10

npm ERR! 0-byte tarball
npm ERR! Please run npm cache clean
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues

npm ERR! Please include the following file with any support request:
npm ERR! /tmp/apm-install-dir-11785-25944-dvvmma.8917s6ecdi/npm-debug.log

@npm-robot
Copy link

We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining WeAllJS and asking your question in its #npm channel. The npm CLI team is all present there, but there are also lots of other folks who can help you too.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants