Search by Tags

Torizon IDE Extensions Issue Tracker

 

The following table contains known issues, scheduled bug fixes, and feature improvements for the Torizon IDE Extensions. The tickets are split in two major states:

  • Submitted (open): new features and bug fixes for Torizon IDE Extensions versions that have not yet been released. They may be scheduled for a specific release version; not planned; or in our backlog. All of them have one of the following states:
    • Known Issue: a bug or unexpected behavior that has been reported and pending a fix. Once fixed, the status will transition to Fixed.
    • Feature Request: a new feature that may be added to a future release. Once released, the status will transition to New Feature.
  • Released (closed): new features and bug fixes for BSP versions that have already been released. All of them have one of the following states:
    • Fixed: a bug that has been fixed and released.
    • New Feature: something that didn't exist before and was added to a new release.

Any schedules are not guaranteed but reflect the current planning. The planning could be shifted due to priority changes.
Issues that are scheduled for a specific version will be integrated into the mentioned version of the BSP.

We will update this table continuously in order to always provide the latest state of our development plan.

Clear Filter
Issue #StatusSubjectModuleComponentsSeverity

Visual Studio 1.5.0 (Release date: 2021-12-15)
Visual Studio 2019 IDE Extension V1.5.0
TIE-489Feature RequestAs a user, I want an option to store securely my password and credentials and not being prompted at every push/publish operation.Not applicableVisual Studio Code Extension, Visual Studio ExtensionLow

Description: Add the capability in the IDE Extensions to securely store credentials (Docker Hub, Torizon OTA, etc).

TIE-475Feature RequestVSCode: Add debugging capabilties for Qt data typesNot applicableVisual Studio Code ExtensionLow

Description: Currently when developing Qt applications there seems to be a limitation with debugging Qt data types/objects. For example when debugging the value of a `QString`, you'll see basic information like the size of the data, but it won't actually show the value of the string. This is due to Qt implementing somewhat complex data types that can't be easily parsed by GDB. So we should seek to improve the debugging experience for Qt applications, by at least allowing proper debugging of Qt-specific data types, if possible.

TIE-415Feature RequestAs a user I want to have the mnemonic tag used instead of the image name in dockerfile and command lineNot applicableMoses (IDE Backend)Low

Description: When a tag is configured, it should be used by the generated commandline and docker-compose file to make them more generic.

TIE-370Feature RequestAs a user, I want to be asked to (re)build a container before pushing it to a container registryNot applicableVisual Studio Code ExtensionLow

Description: If the release image is not available or has never been built, an error is raised. The extensions should ask if the user wants to build a container, instead. If the container exists, ask if the user wants to rebuild it.

TIE-254Feature RequestAs a user, I want the IDE extension to automatically push docker-compose files to Torizon OTA, so I don't have to manually do itAll supported modulesMoses (IDE Backend), Visual Studio Code Extension, Visual Studio ExtensionLow

Description: The IDE Extensions should be able to push docker-compose files to Torizon OTA.

VS Code 1.4.0 (Release date: 2021-12-15)
Visual Studio Code IDE Extension V1.4.0
TIE-489Feature RequestAs a user, I want an option to store securely my password and credentials and not being prompted at every push/publish operation.Not applicableVisual Studio Code Extension, Visual Studio ExtensionLow

Description: Add the capability in the IDE Extensions to securely store credentials (Docker Hub, Torizon OTA, etc).

TIE-475Feature RequestVSCode: Add debugging capabilties for Qt data typesNot applicableVisual Studio Code ExtensionLow

Description: Currently when developing Qt applications there seems to be a limitation with debugging Qt data types/objects. For example when debugging the value of a `QString`, you'll see basic information like the size of the data, but it won't actually show the value of the string. This is due to Qt implementing somewhat complex data types that can't be easily parsed by GDB. So we should seek to improve the debugging experience for Qt applications, by at least allowing proper debugging of Qt-specific data types, if possible.

TIE-415Feature RequestAs a user I want to have the mnemonic tag used instead of the image name in dockerfile and command lineNot applicableMoses (IDE Backend)Low

Description: When a tag is configured, it should be used by the generated commandline and docker-compose file to make them more generic.

TIE-370Feature RequestAs a user, I want to be asked to (re)build a container before pushing it to a container registryNot applicableVisual Studio Code ExtensionLow

Description: If the release image is not available or has never been built, an error is raised. The extensions should ask if the user wants to build a container, instead. If the container exists, ask if the user wants to rebuild it.

TIE-254Feature RequestAs a user, I want the IDE extension to automatically push docker-compose files to Torizon OTA, so I don't have to manually do itAll supported modulesMoses (IDE Backend), Visual Studio Code Extension, Visual Studio ExtensionLow

Description: The IDE Extensions should be able to push docker-compose files to Torizon OTA.

Visual Studio 1.4.0 (Release date: 2021-09-01)
Visual Studio 2019 IDE Extension V1.4.0
TIE-445New FeatureOptimize Dockerfile templates in the IDE backendNot applicableMoses (IDE Backend)Low

Description: Optimize Dockerfile templates in the IDE backend.

TIE-443New FeatureAs a user, I want Verdin iMX8MP support in the IDE ExtensionsVerdin iMX8M PlusMoses (IDE Backend), Visual Studio Code Extension, Visual Studio ExtensionLow

Description: Verdin iMX8M Plus support in the IDE Extensions.

TIE-427FixedExport of volumes to docker-compose file generates wrong syntaxNot applicableMoses (IDE Backend)Low

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.

TIE-400FixedBase container for arm64-wayland platform does not include Vivante driversNot applicableMoses (IDE Backend)Low

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

TIE-398FixedExport of volumes to command line generates wrong syntaxNot applicableMoses (IDE Backend)Low

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.

TIE-360FixedPlatform docker-compose file is not considered when exporting docker-composeNot applicableMoses (IDE Backend)Low

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.

TIE-325FixedNew application wizard closes when VS Code window loses focusNot applicableVisual Studio Code ExtensionLow

Description: This can be fixed by forcing the different controls using during app creation to ignore focus change. The user will have to press ESC to abort project creation.

TIE-311New FeatureLocal Docker registry supportAll supported modulesMoses (IDE Backend), Visual Studio Code Extension, Visual Studio ExtensionLow

Description: Using a local Docker registry improves performance and decreases dependencies on external projects.

TIE-309New FeatureAs a user, I want to use .NET 5 runtime in the IDE Extensions, so I can leverage the new runtime with bug fixes and new featuresAll supported modulesMoses (IDE Backend)Low

Description: Update .NET runtime version to 5.

TIE-306New FeatureAs a user, I want to use the IDE Extensions to develop on Colibri iMX6ULL, so I can be more productive developing software for my productsColibri iMX6ULLMoses (IDE Backend), Visual Studio Code Extension, Visual Studio ExtensionLow

Description: Add support to Colibri iMX6ULL in the IDE extensions.

TIE-253New FeaturePush containers to a registryAll supported modulesMoses (IDE Backend), Visual Studio Code Extension, Visual Studio ExtensionLow

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

TIE-179New FeatureInvestigate and implement the feedback flow for IDE ExtensionsVerdin iMX8M Plus, Verdin iMX8M Mini, Apalis iMX8X, Colibri iMX8X, Colibri iMX7, Colibri iMX6ULL, Apalis iMX6, Colibri iMX6, Apalis iMX8Visual Studio Code Extension, Visual Studio ExtensionLow

Description: Implement a mechanism to collect feedback from users.

TIE-178New FeatureIDE Extensions: feedback flowVerdin iMX8M Plus, Verdin iMX8M Mini, Apalis iMX8X, Colibri iMX8X, Colibri iMX7, Colibri iMX6ULL, Apalis iMX6, Colibri iMX6, Apalis iMX8Visual Studio Code Extension, Visual Studio ExtensionLow

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

TIE-158New FeatureGenerate Dockerfile, command line and docker-compose file to run release containerAll supported modulesMoses (IDE Backend), Visual Studio Code Extension, Visual Studio ExtensionLow

Description: Add support to generated Dockerfiles and docker-compose files in the IDE Extensions.

VS Code 1.3.0 (Release date: 2021-08-11)
Visual Studio Code IDE Extension V1.3.0
TIE-472FixedCMake library template ignores project nameNot applicableVisual Studio Code ExtensionLow

Description: The project name specified by the uset is not taken in account by the template that uses dummy-000 as base name.

Workaround: Change the CMakeList.txt files manually and set the exename property to the right file name.

TIE-462New FeatureAs a user, I want a sample application that shows how to build multiple components in the same project.Not applicableVisual Studio Code ExtensionLow

Description: This can be done using CMake and may be provided as a template. The project should be minimal, building a library with one function and an executable calling it. It could be used to show how to do this and also how such a thing can be debugged.

TIE-445New FeatureOptimize Dockerfile templates in the IDE backendNot applicableMoses (IDE Backend)Low

Description: Optimize Dockerfile templates in the IDE backend.

TIE-443New FeatureAs a user, I want Verdin iMX8MP support in the IDE ExtensionsVerdin iMX8M PlusMoses (IDE Backend), Visual Studio Code Extension, Visual Studio ExtensionLow

Description: Verdin iMX8M Plus support in the IDE Extensions.

TIE-434FixedExtension activation high CPU usage when checking if Docker is runningVisual Studio Code ExtensionLow

Description: The IDE Extension causes a high CPU usage when checking if Docker is running.

TIE-427FixedExport of volumes to docker-compose file generates wrong syntaxNot applicableMoses (IDE Backend)Low

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.

TIE-425FixedEULA Accept License does not workNot applicableMoses (IDE Backend), Visual Studio Code ExtensionLow

Description: After installing the latest Early Access on Visual Studio Code, every time Visual Studio Code is opened, the user is prompt to accept the NXP EULA.

TIE-424FixedInvalid device appears in devices list and debug and other features no longer worksNot applicableVisual Studio Code ExtensionLow

Description: Using VSCode version 1.55.2 or newer a random invalid device appears in the devices list and features like starting the debugger or creating a new project stop working.

TIE-421FixedInvalid device appears in devices list and debug and other features no longer worksNot applicableVisual Studio Code ExtensionLow

Description: Using VSCode version 1.55.2 or newer a random invalid device appears in the devices list and features like starting the debugger or creating a new project stop working.

TIE-418FixedDeleting a configuration does not refresh the configurations listNot applicableVisual Studio Code ExtensionLow

Description: When deleting a configuration, the configuration is removed, the message about activation of a different configuration is shown (when needed), but the deleted configuration is still visible in the list.

Workaround: Reloading the window using the "Developer: Reload Window" command fixes the issue.

TIE-412FixedDocker error when setting network mode to hostNot applicableVisual Studio Code ExtensionLow

Description: When the extra-parameter "network_mode" is set to "host" the debugger stops working.

Workaround: Issue has been fixed in v1.3.117, available via early access on marketplace.

TIE-404FixedUsing a docker volume target with a comma in the filename results in an error.Not applicableVisual Studio Code ExtensionLow

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.

TIE-403FixedC/C++ Template code does not generate immediate outputNot applicableVisual Studio Code ExtensionLow

Description: Our template code does not append a newline after the message, this means that no output is visible in the output terminal until a new line is printed or execution terminates. Since this may be confusing for new users doing step-by-step execution, we should add a line ending to fix the issue.

TIE-400FixedBase container for arm64-wayland platform does not include Vivante driversNot applicableMoses (IDE Backend)Low

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

TIE-398FixedExport of volumes to command line generates wrong syntaxNot applicableMoses (IDE Backend)Low

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.

TIE-396FixedVSCode: C/C++ Dev-container fails to build with buildx enabled.Not applicableVisual Studio Code ExtensionLow

Description: When buildx is enabled (this is the default in latest docker releases, at least on Windows), build of SDK container fails because system is not able to find the source image. Error message is not very clear and seem to imply some missing access rights on docker.io.

Workaround: Issue has been fixed in v1.3.117, available on early access channel in visual studio marketplace.

TIE-395FixedPython setup script may fail on windows machines if git converts line-endingsNot applicableVisual Studio Code ExtensionLow

Description: If a user configured git to convert line ending from the original format to Windows CR+LF this will change the setup.sh and cleanup.sh scripts, generating an error when those are executed in the Linux container during build.

Workaround: Convert startup.sh, cleanup.sh and requirements.txt to unix-style line endings.

TIE-394Fixedmounts specified in extraparms are not exported to command lineNot applicableVisual Studio Code ExtensionLow

Description: When adding an extra parameter like: mounts : [{ type: "bind", source: "/media", target: "/media", propagation; "shared" }] The parameter is used when running the container, but it's not exported when generating the command line.

TIE-393FixedgetHostTriplet commands returns an invalid stringNot applicableVisual Studio Code ExtensionLow

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.

TIE-388FixedMessage for release container deployment says "deployin" instead of deploying.Not applicableVisual Studio Code ExtensionLow

Description: Fix typo in the release container deployment message.

TIE-386FixedInfo tab is not in sync with current state of objectNot applicableVisual Studio Code ExtensionLow

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.

TIE-385FixedVS Code Unable to Prepend Volumes With Application IDNot applicableVisual Studio Code ExtensionLow

Description: VS Code unable to prepend volumes with application ID.

TIE-384FixedChanging configuration may lead to invalid executableNot applicableVisual Studio Code ExtensionLow

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.

TIE-383FixedRebuild and reload in container command doesn't open container when executed in local modeNot applicableVisual Studio Code ExtensionLow

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.

TIE-382New FeatureAs a user, I want the Uno Platform integrated in the VS Code IDE extensionNot applicableVisual Studio Code ExtensionLow

Description: Uno Platform templates integrated into the IDE Extensions.

TIE-381FixedVSCode: Building a python project in the debug configuration without debug/deploying first failsNot applicableVisual Studio Code ExtensionLow

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

TIE-378FixedIssues building wayland applications targeting imx8 using vscode extensionVerdin iMX8M Plus, Verdin iMX8M Mini, Apalis iMX8X, Colibri iMX8XMoses (IDE Backend), Visual Studio Code ExtensionLow

Description: Fix a change in packages for vivante-imx8 specific libraries that broke the platform template used by the extension.

TIE-377FixedWhen a device is deleted from the device list, all the devices which are listed below are also removedNot applicableVisual Studio Code ExtensionLow

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.

TIE-360FixedPlatform docker-compose file is not considered when exporting docker-composeNot applicableMoses (IDE Backend)Low

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.

TIE-334FixedError Exporting Docker Compose FileVerdin iMX8M Plus, Verdin iMX8M Mini, Apalis iMX8X, Colibri iMX8X, Colibri iMX7, Colibri iMX6ULL, Apalis iMX6, Colibri iMX6, Apalis iMX8Visual Studio Code ExtensionLow

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

ValueError: too many values to unpack (expected 2)

This happens when ",rw" or similar attribute is appended to destination for volumes.

TIE-325FixedNew application wizard closes when VS Code window loses focusNot applicableVisual Studio Code ExtensionLow

Description: This can be fixed by forcing the different controls using during app creation to ignore focus change. The user will have to press ESC to abort project creation.

TIE-311New FeatureLocal Docker registry supportAll supported modulesMoses (IDE Backend), Visual Studio Code Extension, Visual Studio ExtensionLow

Description: Using a local Docker registry improves performance and decreases dependencies on external projects.

TIE-309New FeatureAs a user, I want to use .NET 5 runtime in the IDE Extensions, so I can leverage the new runtime with bug fixes and new featuresAll supported modulesMoses (IDE Backend)Low

Description: Update .NET runtime version to 5.

TIE-306New FeatureAs a user, I want to use the IDE Extensions to develop on Colibri iMX6ULL, so I can be more productive developing software for my productsColibri iMX6ULLMoses (IDE Backend), Visual Studio Code Extension, Visual Studio ExtensionLow

Description: Add support to Colibri iMX6ULL in the IDE extensions.

TIE-253New FeaturePush containers to a registryAll supported modulesMoses (IDE Backend), Visual Studio Code Extension, Visual Studio ExtensionLow

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

TIE-179New FeatureInvestigate and implement the feedback flow for IDE ExtensionsVerdin iMX8M Plus, Verdin iMX8M Mini, Apalis iMX8X, Colibri iMX8X, Colibri iMX7, Colibri iMX6ULL, Apalis iMX6, Colibri iMX6, Apalis iMX8Visual Studio Code Extension, Visual Studio ExtensionLow

Description: Implement a mechanism to collect feedback from users.

TIE-178New FeatureIDE Extensions: feedback flowVerdin iMX8M Plus, Verdin iMX8M Mini, Apalis iMX8X, Colibri iMX8X, Colibri iMX7, Colibri iMX6ULL, Apalis iMX6, Colibri iMX6, Apalis iMX8Visual Studio Code Extension, Visual Studio ExtensionLow

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

TIE-158New FeatureGenerate Dockerfile, command line and docker-compose file to run release containerAll supported modulesMoses (IDE Backend), Visual Studio Code Extension, Visual Studio ExtensionLow

Description: Add support to generated Dockerfiles and docker-compose files in the IDE Extensions.

Visual Studio 1.3.0 (Release date: 2021-01-08)
Visual Studio 2019 IDE Extension V1.3.X
TIE-263FixedImages in marketplace page are no longer rendered correctlyAll supported modulesVisual Studio ExtensionLow

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

TIE-261FixedSDK build not working when buildkit is enabledMoses (IDE Backend)Low

Description: When buildkit is enabled you can't reference local images. This prevents multi-stage builds or Dockerfile referencing a local image from working. SDK uses a container that is generated on the fly and kept on the local machine and this fails.

Workaround: Disable buildkit on the local Docker installation.

TIE-260FixedBuild of SDK container fails on WindowsMoses (IDE Backend)Low

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.

TIE-249New FeaturePython Tools for Visual Studio debug server is deprecatedVisual Studio Code ExtensionLow

Description: Internal task

Workaround: This issue has not impact in the short-term, since ptvsd is still available and working on our devices, we plan to replace it with debugpy that is officially maintained.

TIE-234FixedMultiple Devices with Different user cause duplicate volumesVisual Studio Code ExtensionLow

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.

TIE-201FixedDownload/Update base containers operation never completes if there is a download errorVisual Studio ExtensionLow

Description: When a download error happens the operation will not complete, no error message is shown and the menu option remains grayed out until visual studio is restarted.

TIE-97FixedVisual Studio Plugin Project Build ErrorVisual Studio ExtensionLow

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.

TIE-12FixedSometimes Visual Studio displays the message "Visual Studio stopped responding for X seconds"Visual Studio ExtensionLow

Description: Sometimes Visual Studio displays the message "Visual Studio stopped responding for X seconds. Disabling the extension Torizon Visual Studio Development Tools might help". It may be possible to optimize the plugin to avoid it from happening. Despite the latency caused by Visual Studio becoming non-responsive, there are no side-effects reported.

Workaround: Just click "Don't report this extension again".

VS Code 1.2.0 (Release date: 2021-01-08)
Visual Studio Code IDE Extension V1.2.X
TIE-268FixedEPERM trying to run the "Torizon: Rebuild SDK and reload"All supported modulesVisual Studio Code ExtensionLow

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

TIE-261FixedSDK build not working when buildkit is enabledMoses (IDE Backend)Low

Description: When buildkit is enabled you can't reference local images. This prevents multi-stage builds or Dockerfile referencing a local image from working. SDK uses a container that is generated on the fly and kept on the local machine and this fails.

Workaround: Disable buildkit on the local Docker installation.

TIE-260FixedBuild of SDK container fails on WindowsMoses (IDE Backend)Low

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.

TIE-249New FeaturePython Tools for Visual Studio debug server is deprecatedVisual Studio Code ExtensionLow

Description: Internal task

Workaround: This issue has not impact in the short-term, since ptvsd is still available and working on our devices, we plan to replace it with debugpy that is officially maintained.

TIE-234FixedMultiple Devices with Different user cause duplicate volumesVisual Studio Code ExtensionLow

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.

TIE-212FixedUse backend to resolve hostname for debug connectionsVisual Studio Code ExtensionMedium

Description: When debugger is started the project is correctly built and deployed, but then debugger fails to start

Workaround: Add .local as suffix to the device hostname or replace hostname with the device IP address.

TIE-1New FeatureSupport C/C++ development in VS Code providing cross-compiling and remote debuggingVisual Studio Code ExtensionLow

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.

Visual Studio 1.2.0 (Release date: 2020-09-02)
Visual Studio 2019 IDE Extension V1.2.0
TIE-314FixedDownload of debian package lists fails on WindowsVisual Studio Code Extension, Visual Studio ExtensionLow

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.

TIE-308FixedCan't use spaces in log file path for IDE backendColibri iMX7Visual Studio ExtensionLow

Description: When configuring the log file paths you can't use a path that include spaces, this leads to a failure when starting the IDE backend.

Workaround: Configure a path with no spaces for the log file.

TIE-211New FeatureDeprecationWarning: Buffer() is deprecated due to security and usability issuesVisual Studio Code ExtensionLow

Description: No public description, this is a developer warning

Workaround: No public workaround, this is a develop warning

TIE-203New FeatureAdapt IDE Extensions to Debian BullseyeAll supported modulesMoses (IDE Backend)Low

Description: Add support to Debian Bullseye in the IDE extensions

TIE-184New FeaturePreview releases for IDE extensionsAll supported modulesVisual Studio Code Extension, Visual Studio ExtensionLow

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

TIE-77Fixedextraparms setting not available in Visual Studio 2019 Application Properties dialogVisual Studio Extension

Description: This setting can be used to configure additional settings related to container execution. It's available in Visual Studio Code UI, but not in Visual Studio 2019.

TIE-98FixedVS Extension: Adding outside files/folder to the project causes compilation to failAll supported modulesMoses (IDE Backend)Low

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.

TIE-76FixedVisual Studio Code for Linux fails attempting to add a device via serialAll supported modulesMoses (IDE Backend)Low

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

TIE-64FixedVisual Studio error: Object reference not set to an instance of an objectMoses (IDE Backend), Visual Studio ExtensionLow

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.

VS Code 1.1.0 (Release date: 2020-09-02)
Visual Studio Code IDE Extension V1.1.0
TIE-314FixedDownload of debian package lists fails on WindowsVisual Studio Code Extension, Visual Studio ExtensionLow

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.

TIE-299Fixed.NET 5.0 applications can't be debugged on ARM32 architecturesVerdin iMX8M Plus, Verdin iMX8M Mini, Apalis iMX8X, Colibri iMX8X, Colibri iMX7, Colibri iMX6ULL, Apalis iMX6, Colibri iMX6, Apalis iMX8Visual Studio Code ExtensionLow

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.

TIE-203New FeatureAdapt IDE Extensions to Debian BullseyeAll supported modulesMoses (IDE Backend)Low

Description: Add support to Debian Bullseye in the IDE extensions

TIE-191FixedNPM Pointing Security Vulnerability on VS Code buildVisual Studio Code ExtensionMedium

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

TIE-184New FeaturePreview releases for IDE extensionsAll supported modulesVisual Studio Code Extension, Visual Studio ExtensionLow

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

TIE-183Fixed.NET Console Application template with wrong indentationVisual Studio Code ExtensionLow

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

TIE-150FixedUsing VS Code Insiders version with the C/C++ Template returns "Error property 'program' is missing or empty"Visual Studio Code ExtensionLow

Description: Using VS Code Insiders version with the C/C++ Template returns "Error property 'program' is missing or empty"

Workaround: This is an internal version, so no public workaround

TIE-148FixedC/C++ support does not work on insider's builds of VSCodeVisual Studio Code ExtensionLow

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.

TIE-147New FeatureQt applications development support in VS CodeVisual Studio Code ExtensionLow

Description: Qt applications development support in VS Code.

TIE-137FixedDebugger does not connect if network mode of the container is set to hostVisual Studio Code Extension

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

TIE-98FixedVS Extension: Adding outside files/folder to the project causes compilation to failAll supported modulesMoses (IDE Backend)Low

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.

TIE-76FixedVisual Studio Code for Linux fails attempting to add a device via serialAll supported modulesMoses (IDE Backend)Low

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

TIE-94FixedCommand to create ASP.NET application fails if the extension is not loadedVisual Studio Code ExtensionLow

Description: Visual studio code activates the extensions on different event. Torizon extension is activated and loaded when an existing project is opened, when a new python or .NET application is create or when the Torizon bar is used. ASP.NET app creation command was not considered an activation event and so it fails if you try to execute it when the extension is not already loaded.

Workaround: Open the torizon bar by clicking on the Torizon logo in the Visual Studio code Activity Bar on the left side of VS Code main window, this will activate the extension and allow you to run the ASP.NET application create command.

TIE-74FixedSSH error on Windows when debugging a .NET application from a folder that is not under user's homeVisual Studio Code ExtensionLow

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.

TIE-6New FeatureASP.NET templates for Visual Studio Code ExtensionsVisual Studio Code ExtensionLow

Description: ASP.NET provides multiple application types. Current template uses basic MVC, but this may not fit customer’s requirement. New templates has been added for most of the ASP.NET application types supported by the “dotnet new” command. A more flexible template definition (via YAML file) has been added and may allow definition of more templates also for other languages.

TIE-71FixedWeird behavior in the appconfig_0 folderVisual Studio Code ExtensionLow

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

TIE-14FixedApply environment settings to Dockerfile and ssh connection in debug buildsVisual Studio Code ExtensionLow

Description: Currently settings added via the "env" property are applied only when the application runs in the release container. Debugger connects over SSH and those variables are not defined when the application runs.

TIE-62FixedVS Code Extension - Error Deploying to Device using WSL 2: can't find a valid IP for apalis-imx8Visual Studio Code ExtensionLow

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.

TIE-65FixedError adding device: this.refresh is not a function in VS Code ExtensionVisual Studio Code ExtensionLow

Description: Error in Visual Studio Code extension when adding device from network

TIE-108FixedError on 64-bit .NET Core containersVisual Studio Code ExtensionLow

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

Not Planned
TIE-139Known Issue.NET containers use port 22 for debug ssh and can't run in host modeVisual Studio Code Extension

Description: It's possible to fix the issue by configuring a custom port in launch.json (replacing the ${port} entry) and by adding to buildcommands a command that changes it in sshd configuration.

TIE-17Feature RequestProvide LICENSE file for VS Code extensionVisual Studio Code ExtensionLow

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

TIE-82Known IssueError (500) When Try to Debug .NET AppVisual Studio Code ExtensionLow

Description: The issue is that launching a debugger for a .NET app in Visual Studio code sometimes a popup reporting error 500 appears, but it seems we are not able to reproduce it anymore.

Backlog
TIE-467Known IssueSometimes invoking commands implemented by the extension generates an error.Visual Studio Code ExtensionLow

Description: If a command is invoked very early during vscode startup the extension may not have registered the appropriate handlers and this will lead to an error.

Workaround: Wait until extension initializazion has been completed before using the commands.

TIE-459Known IssueSDK container not existing notification is not displayed when re-opening an existing C/C++ projectVisual Studio Code ExtensionLow

Description: When opening a project that has no SDK container the tool should prompt for a rebuild. Unfortunately this does not happen 100% of the times.

Workaround: Rebuild SDK container manually when re-opening the project on a different machine or after having removed containers from your development machine.

TIE-451Known IssuePossible Incompatibility between our extension and VS 16.10.2Visual Studio ExtensionLow

Description: When upgrading to release 16.10 build and other features no longer work, due to changes in VS2019 workflow for Linux.

Workaround: Keep using VS2019 16.7 until a fix is released.

TIE-449Known Issuersync issues when application container is running as rootMoses (IDE Backend)

Description: After adding the --delete flag to ensure that files removed from application folder on dev PC are also removed from the host there is an issue with the __pycache__ folder, created by the python interpreter. When root is used as container user, the folder is owned exclusively by root and can't be deleted by rsync running as torizon.

Workaround: There are multiple workarounds: - run the application as torizon user until issue is fixed - add ENV PYTHONDONTWRITEBYTECODE="1" as env property to avoid cache generation from python interpreter - manually cleanup the pycache folder before deployment

TIE-428Feature RequestAs a user, I want container rebuilds to happen only when I changed properties that can be used inside the generated dockerfile.Moses (IDE Backend)Low

Description: Actually, any change to the configuration will force a rebuild of the container. This, in addition to the need of re-deploying it to the device, increases development time.