search

microsoft / devicescript

TypeScript for Tiny IoT Devices (ESP32, RP2040, ...)
https://microsoft.github.io/devicescript/
MIT License
3.34k stars 122 forks source link

`devicescript devtools --vscode` terminated with exit code: 100 #611

Open xmeow opened 1 year ago

xmeow commented 1 year ago

Describe the bug The devicescript service failed to start, please see the screen shoot. And hardware connection is not available. Vscode will stuck at the context, and the only way to resolve is to kill all vscode process.

To Reproduce When try to click the button 'connect device'.

Screenshots image

Additional context From the electron devtools it says that the bus is undefined at the codeline: this.extensionState.bus.setCustomServiceSpecifications

Nasreddine commented 1 year ago

check if following ports are not used by other processes. http : http://localhost:8081 websocket: ws://localhost:8081 tcpsocket: tcp://localhost:8082 dbgserver: tcp://localhost:8083

pelikhan commented 1 year ago

we should be sniffing for unused ports...

pelikhan commented 1 year ago

@xmeow we had an unneeded dependency on serialport. is this still failing?

xmeow commented 1 year ago

It looks decent on latest devicescript extension build.

pelikhan commented 1 year ago

[like] Peli de Halleux reacted to your message:

From: Riven @.> Sent: Tuesday, November 7, 2023 1:14:30 PM To: microsoft/devicescript @.> Cc: Comment @.>; Subscribed @.> Subject: Re: [microsoft/devicescript] devicescript devtools --vscode terminated with exit code: 100 (Issue #611)

It looks decent on latest devicescript extension build.

— Reply to this email directly, view it on GitHubhttps://github.com/microsoft/devicescript/issues/611#issuecomment-1798483168 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA73QKPIWZ6BA7NG3TIA4HTYDIX3PBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVIZTSMRYGAZTOOJYGOSG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJUGY4TQNJXGUZTJAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDCOBVGYYDCOJZGY3IFJDUPFYGLJLMMFRGK3FFOZQWY5LFVIZTSMRYGAZTOOJYGOTXI4TJM5TWK4VGMNZGKYLUMU. You are receiving this email because you commented on the thread.

Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

reggi commented 10 months ago

I found that I ran into this when I'd run "Connect Device" in vs code, then try to hit the play button on the debugger.

The workflow is much better to run npm run start, and then just save your main file to upload it.