VSC Extension has null device

Hi all and @valter.tx,
I’m having a problem with the extension. A null device has appeared and I can’t delete it, it also seems to prevent other devices appearing in the list:

All help appreciated, this currently prevents me from working.

I have tried reinstalling the extension but no luck.

[03-20 09:50:18.167] Error: Required parameter deviceId was null or undefined when calling deviceDelete.

device configuration is stored in the user’s home folder ($HOME/.moses/devices in Linux, %USERPROFILE%/.moses/devices on Windows).
There you should find folders named with the serial number of the devices, by removing the one of the “offending” devices you should be able to work again.
If you can:

  • collect the output of the IDE-backend from the terminals list
  • the content of the devices and send it to me
    That would help me in trying to figure out what happened and fix the issue.

Serving on http://kubernetes.docker.internal:5000
INFO:root:REST → /api/version
INFO:root:REST ← /api/version - 200
INFO:root:REST → /api/version/docker
INFO:root:REST ← /api/version/docker - 200
INFO:root:REST → /api/devices
INFO:root:REST → /api/setup/enableemulation
INFO:root:REST ← /api/devices - 200
INFO:root:REST → /api/devices/06760593/images
INFO:root:SSH - Creating tunnel to 06760593
INFO:root:REST ← /api/setup/enableemulation - 200
INFO:root:REST → /api/applications/load
INFO:root:REST ← /api/applications/load - 200
INFO:root:REST → /api/platforms/arm64v8-debian-python3_bullseye
INFO:root:REST ← /api/platforms/arm64v8-debian-python3_bullseye - 200
INFO:root:REST → /api/eulas
INFO:root:REST ← /api/eulas - 200
INFO:root:SSH - Tunnel to 06760593 activated
INFO:root:REST ← /api/devices/06760593/images - 200
INFO:root:REST → /api/devices/06760593/containers
INFO:root:REST ← /api/devices/06760593/containers - 200
INFO:root:REST → /api/devices/06760593/processes
INFO:root:SSH - Connecting to device 06760593
INFO:root:SSH - Connected to device 06760593
INFO:root:REST ← /api/devices/06760593/processes - 200
INFO:root:REST → /api/devices/06760593/storage
INFO:root:REST ← /api/devices/06760593/storage - 200
INFO:root:REST → /api/devices/06760593/memory
INFO:root:REST ← /api/devices/06760593/memory - 200
INFO:root:REST → /api/platforms/arm64v8-debian-python3_bullseye/compatibledevices
INFO:root:REST ← /api/platforms/arm64v8-debian-python3_bullseye/compatibledevices - 200

Only device seems to be 06612160 in that folder

Removing it does not seem to help .moses folder is empty. I can try a restart.

I see requests also for 06760593 and the device seems to reply to those requests.
This seems quite strange…

That is a real device that is working. Do you have time for a call? If you email me on ed.waugh@cloudcycle.com I can make a zoom meeting.

Device list is reloaded on backend startup, restarting should lead to an empty devices list.

e-mail sent

Looks like @valter.tx has found the problem and will release a new version of the extension later today.

Hi @edwaugh,

Just a heads up I got notice that a fix for this is now available on the latest version of the early access variant of the extension. Specifically version 1.3.119. Please let us know if the issue is still occurring.

Best Regards,
Jeremias

Confirmed that 119 fixes the issue for me.

That’s great to hear, thanks for confirming!