| Visual Studio Code IDE Extension V1.2.X |
 TIE-268 | Fixed | EPERM trying to run the "Torizon: Rebuild SDK and reload" | All supported modules | Visual Studio Code Extension | Low |
Description: Run "Torizon: Rebuild SDK and reload in container" results in an EPERM error (3). |
| TIE-212 | Fixed | Use backend to resolve hostname for debug connections | | Visual Studio Code Extension | Medium |
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-1 | New Feature | Support C/C++ development in VS Code providing cross-compiling and remote debugging | | Visual Studio Code Extension | Low |
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. |
| TIE-263 | Fixed | Images in marketplace page are no longer rendered correctly | All supported modules | Visual Studio Extension | Low |
Description: It seems that images that include extra attributes are no longer converted to HTML in the right way by the website. |
| TIE-261 | Fixed | SDK build not working when buildkit is enabled | | Moses (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-260 | Fixed | Build of SDK container fails on Windows | | Moses (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-249 | New Feature | Python Tools for Visual Studio debug server is deprecated | | Visual Studio Code Extension | Low |
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-234 | Fixed | Multiple Devices with Different user cause duplicate volumes | | Visual Studio Code Extension | Low |
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. |
| Visual Studio 2019 IDE Extension V1.3.X |
| TIE-263 | Fixed | Images in marketplace page are no longer rendered correctly | All supported modules | Visual Studio Extension | Low |
Description: It seems that images that include extra attributes are no longer converted to HTML in the right way by the website. |
| TIE-261 | Fixed | SDK build not working when buildkit is enabled | | Moses (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-260 | Fixed | Build of SDK container fails on Windows | | Moses (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-249 | New Feature | Python Tools for Visual Studio debug server is deprecated | | Visual Studio Code Extension | Low |
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-234 | Fixed | Multiple Devices with Different user cause duplicate volumes | | Visual Studio Code Extension | Low |
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-201 | Fixed | Download/Update base containers operation never completes if there is a download error | | Visual Studio Extension | Low |
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-97 | Fixed | Visual Studio Plugin Project Build Error | | Visual Studio Extension | Low |
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-12 | Fixed | Sometimes Visual Studio displays the message "Visual Studio stopped responding for X seconds" | | Visual Studio Extension | Low |
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". |
| Visual Studio Code IDE Extension V1.1.0 |
| TIE-314 | Known Issue | Download of debian package lists fails on Windows | | Visual Studio Code Extension, Visual Studio Extension | Low |
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-299 | Known Issue | .NET 5.0 applications can't be debugged on ARM32 architectures | | Visual Studio Code Extension | Low |
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-203 | Feature Request | Adapt IDE Extensions to Debian Bullseye | All supported modules | Moses (IDE Backend) | Low |
Description: Add support to Debian Bullseye in the IDE extensions |
| TIE-191 | Known Issue | NPM Pointing Security Vulnerability on VS Code build | | Visual Studio Code Extension | Medium |
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-184 | Feature Request | Preview releases for IDE extensions | All supported modules | Visual Studio Code Extension, Visual Studio Extension | Low |
Description: Publish one additional extension in the marketplace (for each IDE) called Preview to release development versions of the Extensions. |
| TIE-183 | Known Issue | .NET Console Application template with wrong indentation | | Visual Studio Code Extension | Low |
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-150 | Known Issue | Using VS Code Insiders version with the C/C++ Template returns "Error property 'program' is missing or empty" | | Visual Studio Code Extension | Low |
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-148 | Known Issue | C/C++ support does not work on insider's builds of VSCode | | Visual Studio Code Extension | Low |
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-147 | Feature Request | Qt applications development support in VS Code | | Visual Studio Code Extension | Low |
Description: Qt applications development support in VS Code. |
| TIE-137 | Known Issue | Debugger does not connect if network mode of the container is set to host | | Visual 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-98 | Known Issue | VS Extension: Adding outside files/folder to the project causes compilation to fail | All supported modules | Moses (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-76 | Known Issue | Visual Studio Code for Linux fails attempting to add a device via serial | All supported modules | Moses (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-94 | Known Issue | Command to create ASP.NET application fails if the extension is not loaded | | Visual Studio Code Extension | Low |
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-74 | Known Issue | SSH error on Windows when debugging a .NET application from a folder that is not under user's home | | Visual Studio Code Extension | Low |
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-6 | Feature Request | ASP.NET templates for Visual Studio Code Extensions | | Visual Studio Code Extension | Low |
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-71 | Known Issue | Weird behavior in the appconfig_0 folder | | Visual Studio Code Extension | Low |
Description: An error was causing a weird behavior in the appconfig_0 folder of the VSCode plugin. |
| TIE-14 | Known Issue | Apply environment settings to Dockerfile and ssh connection in debug builds | | Visual Studio Code Extension | Low |
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-62 | Known Issue | VS Code Extension - Error Deploying to Device using WSL 2: can't find a valid IP for apalis-imx8 | | Visual Studio Code Extension | Low |
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-65 | Known Issue | Error adding device: this.refresh is not a function in VS Code Extension | | Visual Studio Code Extension | Low |
Description: Error in Visual Studio Code extension when adding device from network |
| TIE-108 | Known Issue | Error on 64-bit .NET Core containers | | Visual Studio Code Extension | Low |
Description: 64-bit .NET Core container does not work |
| Visual Studio 2019 IDE Extension V1.2.0 |
| TIE-314 | Known Issue | Download of debian package lists fails on Windows | | Visual Studio Code Extension, Visual Studio Extension | Low |
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-203 | Feature Request | Adapt IDE Extensions to Debian Bullseye | All supported modules | Moses (IDE Backend) | Low |
Description: Add support to Debian Bullseye in the IDE extensions |
| TIE-184 | Feature Request | Preview releases for IDE extensions | All supported modules | Visual Studio Code Extension, Visual Studio Extension | Low |
Description: Publish one additional extension in the marketplace (for each IDE) called Preview to release development versions of the Extensions. |
| TIE-98 | Known Issue | VS Extension: Adding outside files/folder to the project causes compilation to fail | All supported modules | Moses (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-76 | Known Issue | Visual Studio Code for Linux fails attempting to add a device via serial | All supported modules | Moses (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-308 | Known Issue | Can't use spaces in log file path for IDE backend | Colibri iMX7 | Visual Studio Extension | Low |
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-211 | Feature Request | DeprecationWarning: Buffer() is deprecated due to security and usability issues | | Visual Studio Code Extension | Low |
Description: No public description, this is a developer warning Workaround: No public workaround, this is a develop warning |
| TIE-77 | Known Issue | extraparms setting not available in Visual Studio 2019 Application Properties dialog | | Visual 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-64 | Known Issue | Visual Studio error: Object reference not set to an instance of an object | | Moses (IDE Backend), Visual Studio Extension | Low |
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. |
| TIE-139 | Known Issue | .NET containers use port 22 for debug ssh and can't run in host mode | | Visual 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-17 | Feature Request | Provide LICENSE file for VS Code extension | | Visual Studio Code Extension | Low |
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-82 | Known Issue | Error (500) When Try to Debug .NET App | | Visual Studio Code Extension | Low |
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. |
