atom-python-run icon indicating copy to clipboard operation
atom-python-run copied to clipboard

Getting an error while installing you package using Atom.

Open kotharan opened this issue 6 years ago • 2 comments

I tried intsalling it varios times but it results in the same error.

error

In case the photo isn't visible, the error goes like :

fs.js:922
  return binding.mkdir(pathModule._makeLong(path),
                 ^

Error: EPERM: operation not permitted, mkdir 'C:\PROGRA~1\Java\JDK18~1.0_1\bin\d-118624-8948-f5tgww.gqmyhqia4i'
    at Error (native)
    at Object.fs.mkdirSync (fs.js:922:18)
    at Object.mkdirSync (C:\Users\DELL\AppData\Local\atom\app-1.28.2\resources\app\apm\node_modules\temp\lib\temp.js:137:6)
    at Request.<anonymous> (C:\Users\DELL\AppData\Local\atom\app-1.28.2\resources\app\apm\lib\install.js:335:41)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:188:7)
    at Request.onRequestResponse (C:\Users\DELL\AppData\Local\atom\app-1.28.2\resources\app\apm\node_modules\request\request.js:1062:10)
    at emitOne (events.js:96:13)
    at ClientRequest.emit (events.js:188:7)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:474:21)

Thanks for your help.

kotharan avatar Jul 24 '18 18:07 kotharan

Hello you there?

kotharan avatar Jul 25 '18 19:07 kotharan

You can out put a list of other installed packages (that way we can see if one is conflicting with this one for example) by using apm (atom package manager cli tool).

$ apm list --installed

and you can just copy and paste the contents there. This may be an issue with atom or with the package. My best guess is it may be Atom and/or a conflicting package seeing as the error seems to be occurring within a package dependency fs.js on line 922.

Sometimes you have to rebuild the module cache which apm can do for you.

$ apm rebuild-module-cache

Sometimes certain JS pacakges need to be recompiled and reconfigured for one reason or another and this can fix that issue. Other than that, I really don't know without more info.

Sometimes you need to disable certain packages to see if that's the issue. Easiest way is to move the ~/.atom folder to somewhere else as ~/.atom.bak and then open atom and see if everything is working as expected. no need to uninstall or reinstall atom altogether.

$ apm help

apm - Atom Package Manager powered by https://atom.io

Usage: apm <command>

where <command> is one of:
    clean, config, dedupe, deinstall, delete, dev, develop, disable, docs,
    enable, erase, featured, home, i, init, install, link, linked, links, list,
    ln, lns, login, ls, open, outdated, publish, rebuild, rebuild-module-cache,
    remove, rm, search, show, star, starred, stars, test, uninstall, unlink,
    unpublish, unstar, update, upgrade, view.

Run `apm help <command>` to see the more details about a specific command.

Options:
  --color        Enable colored output                                     [boolean] [default: true]
  -v, --version  Print the apm version
  -h, --help     Print this usage message

  Prefix an option with `no-` to set it to false such as --no-color to disable
  colored output.

You can check out these links and hopefully they lead to something useful.

You may also want to check out these alternative resources and check out atom.io forums and see if others have faced a similar issue.

With some web searching, and some patience, you may find that it might be something else entirely that's keeping you from installing the package. It has happened to me before, but with another package and I found out it was the way I had atom set up. Going through the intro docs helps you get orientated as well.

ghost avatar Jul 28 '18 16:07 ghost