Torizon IDE Extensions Issue Tracker

Description: Base container for arm64-wayland platform does not include Vivante drivers.

Description: It's possible to specify a docker-compose file for an application and it will be merged with additional parameters to run the application. The docker-compose file can be specified also by the platform (ex: for platforms who need to run weston), but it is ignored during export.

Description: Update .NET runtime version to 5.

Description: The IDE extensions should be able to push container image to a registry.

Description: Implement a way for users of IDE Extensions to fill out a survey to provide feedback.

Description: It seems that images that include extra attributes are no longer converted to HTML in the right way by the website.

Description: Docker on Windows generates an internal exception when the IDE backed checks if the SDK container is actually running. This behavior is not reproducible on all Windows 10 machines, even when they run the same docker ad Windows 10 releases.

Description: If you are connecting multiple devices and these devices are using different users the IDE backend will create a duplicate volume entry for the project for each user.

Workaround: Select the debug configuration and manually delete the duplicate volume entry for the user that you want.

Description: During the first build of a C++ project with Visual Studio Plugin, one may see the following error message: "error : Error calling ApplicationUpdatesdk: {"code": 500, "description": "Internal server error"

Workaround: Build the project again.

Description: When building an image, during the apt-get update command execution you may get the following error: {code:bash} Release file for http://snapshot.debian.org/archive/debian/20200908T070000Z/dists/bullseye/InRelease is not valid yet (invalid for another 18513d 2h 11min 31s). Updates for this repository will not be applied. {code} When this happens time on the linux/arm platform seem to be set to the wrong date (usually the beginning of unix epoch). You can test this by running a standard debian image: {code:bash} docker run -it --rm --platform linux/arm debian:bullseye-slim Unable to find image 'debian:bullseye-slim' locally bullseye-slim: Pulling from library/debian 5ed966da184b: Pull complete Digest: sha256:6dd2509b000570c24fbf0dd6ea4c907227e36f77b8a7ca2b818464bbff8287dc Status: Downloaded newer image for debian:bullseye-slim root@cb280c464483:/# date Thu Jan 1 00:00:00 UTC 1970 {code}

Workaround: Usually just running the container build multiple times solves the issue. Restarting docker also works, but if you are using VSCode inside a container this will force you to exit the system.

Description: No public description, this is a developer warning

Workaround: No public workaround, this is a develop warning

Description: Publish one additional extension in the marketplace (for each IDE) called Preview to release development versions of the Extensions.

Description: When trying to add files/folder that are located outside of the the main VS project folder the project folder structure then gets altered. This alteration of the folder structure then causes things like compilation and debugging to fail.

Description: On one of the PCs where the extension has been tested, when executing "Deploy and Debug Torizon Application", a dialog pops-up with the error "Object reference not set to an instance of an object". From this point onwards, it is impossible to deploy and debug Torizon applications, even if a new project is created or Visual Studio is restarted. There are issues also accessing the debugging options of the project and of any project created using the Visual Studio for Linux extension.

Workaround: Uninstall and Reinstall Visual Studio.

Description: The rw mount specifier is appended to the mount point name using the wrong separator, this leads to an incorrect mount point name inside the container.

Description: the torizon.ccpp.getHostTriplet command that can be used in tasks returns a string that is missing the last character, this can lead to build errors.

Description: This may happen when a device is deleted or when the information is refreshed, the info panel content is not refreshed and may show old information.

Workaround: Click on the object to refresh the information.

Description: When the command is executed while the project is already opened in a container, it works. When executed without a container ready (ex: opening the project on a different machine) it rebuilds the container but does not switch to container mode.

Workaround: After container build has completed, reload project in a container using the Remote-Containers/Reload in container command.

Description: Building a python project in the debug configuration without debug/deploying first fails.

Description: When a device is deleted from the device list, all the devices which are listed below are also removed, and we have to include them again.

Description: When exporting a docker-compose file you get the error:

ValueError: too many values to unpack (expected 2)

Description: Update .NET runtime version to 5.

Description: The IDE extensions should be able to push container image to a registry.

Description: Implement a way for users of IDE Extensions to fill out a survey to provide feedback.

Description: Run "Torizon: Rebuild SDK and reload in container" results in an EPERM error (3).

Description: Docker on Windows generates an internal exception when the IDE backed checks if the SDK container is actually running. This behavior is not reproducible on all Windows 10 machines, even when they run the same docker ad Windows 10 releases.

Description: If you are connecting multiple devices and these devices are using different users the IDE backend will create a duplicate volume entry for the project for each user.

Workaround: Select the debug configuration and manually delete the duplicate volume entry for the user that you want.

Description: Developing applications in C/C++ will be supported by the Visual Studio Code extension for Torizon. Cross-compilation and remote debugging will be supported.

Description: This is a known issue of the VS debugger that is used by VSCode and Visual Studio 2019 to debug .NET Core applications: https://github.com/OmniSharp/omnisharp-vscode/issues/4210 https://github.com/nforgeio/RaspberryDebugger Issue has been reported to MS and may be fixed in a new release of the debugger, but no timeline has been given.

Workaround: Keep using .NET Core 3.1 if using a 32 bit target.

Description: No need public description, this is a development issue, we need to update the npm library lodash

Workaround: No need public description, this is a development issue, we need to update the npm library lodash

Description: When a .NET Console project is created using VS Code extension, the program.cs file is not created with the correct indentation

Workaround: Select the block with the incorrect indentation and apply a TAB

Description: The extension registers itself to run inside the container by creating a subfolder in the folder where VSCode keeps its extensions. Unfortunately this path is different between stable and insiders builds and so extension does not run there.

Description: When "network_mode" extraproperty of configuration is set to "host" the container runs in host mode, but debugger can't connect.

Description: Customer in referenced community post has an issue in the VScode extension where attempting to add a device via serial seems to fail.

Description: When developing a .NET application that is stored in a folder that is not under the user home or is accessible to all users, you get an error when trying to start debugger. On the debug console you can see an error message from SSH complaining about the fact that the permissions for the key file are too open.

Workaround: Move your project under your home folder or change it's access rights to make it accessible only from your user.

Description: An error was causing a weird behavior in the appconfig_0 folder of the VSCode plugin.

Description: On Windows 10 Home and WSL 2, when deploying to a device, the following error occurs several times: "Error (545) - Can't find a valid IP for board name". NOTE: Windows 10 Home and WSL 2 are not supported at the moment.

Workaround: Retry to deploy (press F5 for instance) until it works. It may work on 1 out of 10 tries.

Description: 64-bit .NET Core container does not work

Description: The Visual Studio marketplace allows providing license information for extensions. Visual Studio Code extension for Torizon has an empty license at the moment.

Description: In the Visual Studio Code extension, specifying a docker volume target with a comma in the filename results in a `Remote docker exception`.

Workaround: Do not use a comma in the filename of the container-side mapping. The comma in the host side volume specification works as expected.

Description: In C/C++ projects when changing configuration from arm32 to arm64 or vice-versa the system may not rebuild the final executable (depending on the build system) and this may lead to a wrong exe being executed on the target during debug/release.

Workaround: Manually rebuild application when changing active configuration.