VSCode and Pymakr Broken?

[Ralph]

@ledbelly2142 Thanks for the bugreport, sorry to hear your workflow was interrupted. I'll see if I can reproduce the error on Atom. You are using Atom 1.23.0 on windows 64, correct?

[Ralph]

@ledbelly2142 For the atom issue, try updating to pymakr v1.2.3 (it's been released just now). let me know if it solves your issue with the Atom plugin!

[melisa]

@ralph Any idea on when this will be fixed? I'm on the latest version of VS Code, I'm on Windows 10. Is there a way to roll back pymakr to a previous version?

[Ralph]

@melisa I was testing it today with the help of @robd, but it didn't work yet. Hopefully tomorrow I'll find a solution.

As a workaround you can install the x32 bit version of VSCode, there it will work. Atom is also available as an alternative.

[ledbelly2142]

@ralph I have Atom 1.23.0 x64. I tried to install the Pymakr package 1.2.3 and it failed with this error:

fs.js:640
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open 'C:\Users\****\.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\****\AppData\Local\atom\app-1.23.0\resources\app\apm\node_modules\asar-require\lib\require.js:86:27)
    at C:\Users\****\AppData\Local\atom\app-1.23.0\resources\app\apm\lib\install.js:476:42
    at fn (C:\Users\****\AppData\Local\atom\app-1.23.0\resources\app\apm\node_modules\async\lib\async.js:582:34)
    at Immediate.<anonymous> (C:\Users\****\AppData\Local\atom\app-1.23.0\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)

There was an update to Atom, updated to 1.23.1 x64, so I updated and attempted to install the Pymakr package and received this error:

fs.js:640
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open 'C:\Users\****\.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\****\AppData\Local\atom\app-1.23.1\resources\app\apm\node_modules\asar-require\lib\require.js:86:27)
    at C:\Users\****\AppData\Local\atom\app-1.23.1\resources\app\apm\lib\install.js:476:42
    at fn (C:\Users\****\AppData\Local\atom\app-1.23.1\resources\app\apm\node_modules\async\lib\async.js:582:34)
    at Immediate.<anonymous> (C:\Users\****\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)

[Ralph]

@ledbelly2142 Ok, thanks for the feedback. In this github issue the same thing is going on. I'll look in to it tomorrow and will let you know.

[Ralph]

@ledbelly2142 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 in Pymakr pymakr version 1.2.5. Unfortunately, you will lose the global package settings as a result of this.

[melisa]

@ralph is this fixed for VS Code x64 too?

[Ralph]

@melisa No sorry, that's on my planning for later today!

[Ralph]

We've just uploaded a new version (0.1.6) that works on windows x64. Try it out and let me know if your problem is fixed.