Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    VSCode and Pymakr Broken?

    Scheduled Pinned Locked Moved Software Tools
    pymakrbug
    16 Posts 4 Posters 3.5k Views 4 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R Offline
      robd
      last edited by

      Hello,
      I have having an issue with pymakr on visual studio code.
      I have been using this and it has been working. When I opened my project tonight, pymakr was not active anymore. I don't get the terminal which you can connect to your devices, key mappings are gone. When I enter a key mapping I get a warning command 'pymakr.connect'(or another command) not found I have uninstalled pymakr and reinstalled but I don't get anything. Generally it is present when I open up visual studio code, it is installed.
      I also did an install on another computer and the same thing is happening.
      How do I enable pymakr or at least reset it to get it working again?

      Thanks,

      1 Reply Last reply Reply Quote 0
      • R Offline
        Ralph
        last edited by

        Hi @robd, We've uploaded an update of Pymakr yesterday, maybe something went wrong with that. First of all make sure you have a reasonably new version of VSCode (1.16 or higher). Can you tell me which version of VSCode you have and what OS you are on?

        R 1 Reply Last reply Reply Quote 0
        • R Offline
          robd @Ralph
          last edited by

          @ralph I just uninstalled VSCode x64 and installed a x32 and Pymakr is working now.
          As for the x64 it was the latest since I uninstalled and then installed it so it would have been 1.18.1 on windows 10. The x32 is also version 1.18.1. Pymakr is version 0.1.5.

          ledbelly2142L 1 Reply Last reply Reply Quote 0
          • R Offline
            Ralph
            last edited by

            @robd thanks for the effort and info! I'll do some tests on my windows 64 machine at home tonight to see if I can find a problem with it. Likely it's a problem with the precompiled serialport library, which is the only part of the plugin that differs between the x32 and x64 install. I'll let you know when I find the solution.

            1 Reply Last reply Reply Quote 0
            • ledbelly2142L Offline
              ledbelly2142
              last edited by ledbelly2142

              Both my Atom with Pymakr and VS Code with Pymakr are still broken. Really frustrated, serious workflow interrupted. Bad timing I guess.

              I uninstalled and reinstalled both (64 bit versions). Is not working.

              Error on Atom version Pymakr on attempted package install:

              Installing “Pymakr@1.2.2” 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\****\.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)

              Looks similar to an error that happened before with one of the updates for Atom.

              Friends don't let friends run with scissors

              R 1 Reply Last reply Reply Quote 0
              • ledbelly2142L Offline
                ledbelly2142 @robd
                last edited by

                @robd Thanks for the quick work around. Loaded 32 bit version and works fine.

                Friends don't let friends run with scissors

                1 Reply Last reply Reply Quote 0
                • R Offline
                  Ralph @ledbelly2142
                  last edited by

                  @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?

                  1 Reply Last reply Reply Quote 0
                  • R Offline
                    Ralph
                    last edited by

                    @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!

                    ledbelly2142L 1 Reply Last reply Reply Quote 0
                    • M Offline
                      melisa
                      last edited by

                      @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?

                      R 1 Reply Last reply Reply Quote 0
                      • R Offline
                        Ralph @melisa
                        last edited by

                        @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.

                        1 Reply Last reply Reply Quote 0
                        • ledbelly2142L Offline
                          ledbelly2142 @Ralph
                          last edited by

                          @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)

                          Friends don't let friends run with scissors

                          R 2 Replies Last reply Reply Quote 0
                          • R Offline
                            Ralph @ledbelly2142
                            last edited by

                            @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.

                            M 1 Reply Last reply Reply Quote 0
                            • R Offline
                              Ralph @ledbelly2142
                              last edited by

                              @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.

                              1 Reply Last reply Reply Quote 0
                              • M Offline
                                melisa @Ralph
                                last edited by

                                @ralph is this fixed for VS Code x64 too?

                                R 2 Replies Last reply Reply Quote 0
                                • R Offline
                                  Ralph @melisa
                                  last edited by

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

                                  1 Reply Last reply Reply Quote 0
                                  • R Offline
                                    Ralph @melisa
                                    last edited by

                                    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.

                                    1 Reply Last reply Reply Quote 1

                                    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                                    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                                    With your input, this post could be even better 💗

                                    Register Login
                                    • 1 / 1
                                    • First post
                                      Last post

                                    Pycom on Twitter

                                    Pycom