search

sg-wireless / pymakr-atom

Adds a REPL console to Atom that connects to your Pycom board. It can run code on the board or synchronize your project files.
Other
35 stars 11 forks source link

Install failure atom 1.23.1 #49

Closed patmolloy closed 6 years ago

patmolloy commented 6 years ago

Hi, The installer is saying it wants to install pymakr 1.0.3 ("the latest that is compatible with your version of Atom"). On installing I get ..

Installing “Pymakr@1.0.3” failed.Hide output… fs.js:640 return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode); ^

Error: ENOENT: no such file or directory, open 'C:\Users\patmo.atom\packages\Pymakr\package.json' at Error (native) at Object.fs.openSync (fs.js:640:18) at Proxy.fs.readFileSync (fs.js:508:33) at Proxy.fs.readFileSync (C:\Users\patmo\AppData\Local\atom\app-1.23.1\resources\app\apm\node_modules\asar-require\lib\require.js:86:27) at C:\Users\patmo\AppData\Local\atom\app-1.23.1\resources\app\apm\lib\install.js:476:42 at fn (C:\Users\patmo\AppData\Local\atom\app-1.23.1\resources\app\apm\node_modules\async\lib\async.js:582:34) at Immediate. (C:\Users\patmo\AppData\Local\atom\app-1.23.1\resources\app\apm\node_modules\async\lib\async.js:498:34) at runCallback (timers.js:649:20) at tryOnImmediate (timers.js:622:5) at processImmediate [as _immediateCallback] (timers.js:594:5)

kukaoo commented 6 years ago

I have a similar issue.

RalphHogenbirk commented 6 years ago

You can now update to Pymakr v1.2.3, which will solve the issue!

patmolloy commented 6 years ago

Am still seeing this .. completely fresh install of atom.

Installing “Pymakr@1.2.3” failed.Hide output… fs.js:640 return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode); ^

Error: ENOENT: no such file or directory, open 'C:\Users\patmo.atom\packages\Pymakr\package.json' at Error (native) at Object.fs.openSync (fs.js:640:18) at Proxy.fs.readFileSync (fs.js:508:33) at Proxy.fs.readFileSync (C:\Users\patmo\AppData\Local\atom\app-1.23.1\resources\app\apm\node_modules\asar-require\lib\require.js:86:27) at C:\Users\patmo\AppData\Local\atom\app-1.23.1\resources\app\apm\lib\install.js:476:42 at fn (C:\Users\patmo\AppData\Local\atom\app-1.23.1\resources\app\apm\node_modules\async\lib\async.js:582:34) at Immediate. (C:\Users\patmo\AppData\Local\atom\app-1.23.1\resources\app\apm\node_modules\async\lib\async.js:498:34) at runCallback (timers.js:649:20) at tryOnImmediate (timers.js:622:5) at processImmediate [as _immediateCallback] (timers.js:594:5)

From: Ralph [mailto:notifications@github.com] Sent: 14 December 2017 14:36 To: pycom/pymakr-atom pymakr-atom@noreply.github.com Cc: Pat Molloy pat.molloy@outlook.com; Author author@noreply.github.com Subject: Re: [pycom/pymakr-atom] Install failure atom 1.23.1 (#49)

You can now update to Pymakr v1.2.3, which will solve the issue!

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpycom%2Fpymakr-atom%2Fissues%2F49%23issuecomment-351728065&data=02%7C01%7C%7C829664af954f4334f22f08d543000f6e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636488589889963076&sdata=2AFA%2FCSlvzpIsJ8CNqqMRkD4VPyCiXqTQdmhZ3c1hlY%3D&reserved=0, or mute the threadhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAEPGGdSTmqRI0SJf8lg9N8Pp2H9ZllZ_ks5tATJqgaJpZM4RBYOH&data=02%7C01%7C%7C829664af954f4334f22f08d543000f6e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636488589889963076&sdata=fUBcOWhGp8tccyrqUUArScdM9ER%2FBw3%2BzmT2om%2BvyJw%3D&reserved=0.

RalphHogenbirk commented 6 years ago

Sorry @patmolloy, I'll investigate this tomorrow and will post a solution for you!

RalphHogenbirk commented 6 years ago

This issue has finally been fixed today. The problem was that Atom stopped supporting package names with uppercase. It's been changed to lowercase now. Unfortunately, you will lose the global package settings as a result of this.