-
Notifications
You must be signed in to change notification settings - Fork 230
Serial monitor not works after VSCode updated to 1.49.0 #1097
Comments
I face same issue too. Modify at 22:40 : (Sorry for anbiguous comment, I'm not good at node.js and electron...) |
Yup! Me too! :< |
UP, me too :/ |
I'm having the same issue, any workaround for this? |
Yes, I downloaded version 1.48.2, and it worked again.
|
I was having the same issue. The 1.48.2 version of vscode is worked for me too. |
Same problem, it would be nice if the VSCode platform included at least one serialport native binding that all extension makers could use to avoid everone needing to setup a CI/CD just to avoid this breaking. |
See #922 for more history on this. The only solution is to go back to Code 1.48.2 until an updated extension version is released. |
Got the same issue |
i got same. |
worked for me too. |
Same issue under GNU/Linux (Kubuntu 18.04) for VSCode 1.49.1 |
Same issue under Windows 10 for VSCode 1.49.1 |
@Josverl while I agree that the right place to fix this is in VSCode, how did you fix this? I'm looking at your repo https://github.com/Josverl/pymakr-vsc and I have two questions.
We can put your suggestion on the VS Code backlog by raising it as an issue and getting 20 people to vote for it, but an even faster way to get it done is to submit a PR. This is why I'm interested in how you did it. |
the approach was to :
something like the above would be needed for each Project but as you can see , also pymakr had the same issue as there was still a manual step to watch the CI/CD against for the insiders build. I agree that N-API would be much better, and shift the responsibility to the creators of library , but the suggestion for that seems 3 year old with no followup that i could find. |
Same issue under Windows 10 for VSCode 1.49.2. |
Yes, I reached similar conclusions.
What I have done instead is create a whole new extension that integrates the new Arduino-CLI.
This is currently an incomplete prototype but progress is rapid. So far I have support for
* Choose board (and by implication toolchain, header files and compatible programmers)
* Choose programming method (a port or a compatible programmer)
* Choose libraries (which causes them to be installed if necessary)
I also have working proofs of concept for
* Compile
* Flash board
* Flash bootloader
But these use hardcoded values and must be reworked to use selections after I finish writing the environment management aspects. At the moment I’m working on managing compiler paths based on library selections.
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
From: Jos Verlinde<mailto:notifications@github.com>
Sent: Monday, 28 September 2020 8:35 PM
To: microsoft/vscode-arduino<mailto:vscode-arduino@noreply.github.com>
Cc: Peter Wone<mailto:peter.wone@outlook.com>; Mention<mailto:mention@noreply.github.com>
Subject: Re: [microsoft/vscode-arduino] Serial monitor not works after VSCode updated to 1.49.0 (#1097)
@PeterWone<https://github.com/PeterWone>
the approach was to :
1. download the native bindings for upcoming VSCode versions --> Electron Versions --> native Bindings
* this required some creative manners to get that information
* then additional creativity to download the native bindings
* then even more to find that some of the pre-comibles offered were actually broken
2 - figure out a way to store multipole versions / platforms of ntive bindings that can be located by the load-libraries used by serialport
2 create test projects to run against electron version N on Platform X , with bitness Y , with the downloaded binaries
3 run CI/CD [Nightly / on Commit / PR ] using GitHub actions that flags if upcoming versions ( ie Insiders ) will be broken
4 [did not Implement] create a automated PR with new native bindings as they are released
5 requires manual action on failed CI/CD Builds
something like the above would be needed for each Project
Please refer to:
pycom/pymakr-vsc#59<pycom/pymakr-vsc#59>
( i learned more than i wanted to know when figuring out a workaround for something that i assumed was a trivial fix ....)
but as you can see , also pymakr had the same issue as there was still a manual step to watch the CI/CD against for the insiders build.
and even including Serialport in VSCode will not solve the problem , only shift it to a place where it can be managed, but actually it should not need to be managed/contained, it should be prevented.
I agree that N-API would be much better, and shift the responsibility to the creators of library , but the suggestion for that<serialport/node-serialport#1186> seems 3 year old with no followup that i could find.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#1097 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABJ6QOCCPB7Y2SRTQX3PDYLSIBRGHANCNFSM4RGJN2GQ>.
|
Same problem here. Looking forward to a fix! |
check the solution proposed here #1113 (comment) if have a proper build environment on your machine. |
I think the point is not that that (rebuilding the native module) can or cannot be done by some users, on some machines. In my view a user should not need to compile from source to use a published vscode add-in . that is similar to to getting a car (for free or paid) only to find that you need to rebuild the clutch every 5 months. The current serial implementation is using the old-tech NAN , the requires a rebuild after very bump in the road .
so if you care , please ask the serialport maintainers to support one of these APIs , or if you have skills in C / C++ help pitch in the create or test that |
@Josverl i'm not realy deep enough into the architecture of the vscode extensions but normaly it should be sufficient to simply distribute the platform dependend extensions from a central point like serialport is doing but i dont know if this is done with vscode extensions at all. But to be true i'm neither going to run after the maintainers from this scary piece of software nor i want to be integrated into it at all. |
I just update the engines section in //in package.json
"engines": {
"vscode": "^1.5.0"
}, update like that "engines": {
"vscode": "^1.34.0"
}, |
It has conditional compiles and platform specific code for calls into native code. Porting their method to Node will end up with exactly the same problems you are currently experiencing. That is why I chose the approach I am using. |
Prerelease build for the serial port issue is here: https://github.com/microsoft/vscode-arduino/releases/tag/v0.3.3-rc I plan to publish a release with this fix tomorrow, Oct 30. |
Resolved in release 0.3.3 |
Upgraded to version 1.51.1. The Problem was fixed. |
Hi, "Failed to open serial port COM8 due to error: + Error: The module '\?\c:\Users\Jalbarra.vscode\extensions\vsciot-vscode.vscode-arduino-0.3.4\out\node_modules\usb-detection\build\Release\detection.node' I have this versions, |
Problem still occurs on 1.53.0 (Mac OS):
Version: 1.53.0 |
Just had the same problem with 1.53.2 on Windows.
Fixed it by following #1198 (comment) |
Also having the same issue. I can upload if I manually set COM port in arduino.json but can not monitor it from within VSCode.
|
@Benargee - #1198 (comment) works |
Same problem as others in this thread on opening the serial monitor. I succumbed to a forced upgrade. I am getting so sick of all these frigin bugs in the Arduino extension. |
Serial monitor not works after VSCode updated to 1.49.0 with Electron 9.2.1 . Error:
Failed to open serial port COM3 due to error: + Error: The module '\\?\c:\Users\***\.vscode\extensions\vsciot-vscode.vscode-arduino-0.3.2\out\node_modules\usb-detection\build\Release\detection.node' was compiled against a different Node.js version using NODE_MODULE_VERSION 75. This version of Node.js requires NODE_MODULE_VERSION 80. Please try re-compiling or re-installing the module (for instance, using `npm rebuild` or `npm install`).
The text was updated successfully, but these errors were encountered: