Torizon IDE Extensions Issue Tracker

Description: As reported on ApolloX Multicontainer Project generates files with absolute path, having absolute paths on multicontainer projects leads to a bad UX when sharing the project with other colleagues, who will download the project in different directories .

Description: The new IDE 2.0 Extension for Torizon, also known as ApolloX, is meant to be a tool that simplifies the development workflows for TorizonCore. This includes OS customization and integration tests.

By providing a TorizonCore Builder template, we allow customers to easily develop their application against a custom TorizonCore, as well as simplify the deployment of such apps and custom OS on a CI pipeline.

Description: To learn more about this bug, refer to the community post Visual Studio 2019 remote connection issue on Verdin iMX8M Mini

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

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

Description: Even though support for Qt data types has been added, it doesn't seem to be working as expected in debug mode.

Description: When creating a new C/C++ project of type QT/Widgets, and then trying to run the build, the error "command 'torizon.ccpp.getTargetFolder' not found" happens.

Workaround: This has been addressed and the issue has been fixed.

Description: When trying to build a Python Qt UI project the following error is shown: "Variable ${config:python.pythonPath} can not be resolved because setting 'python.pythonPath' not found."

Description: Verdin iMX8M Plus support in the IDE Extensions.

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: Using a local Docker registry improves performance and decreases dependencies on external projects.

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

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

Description: The versions of .NET Core 3 and .NET 6 must be bumped to the latest. This is in preparation for our upcoming stable release.

Description: We have found a high-severity vulnerability in the NPM package simple-get tracked by CVE-2022-0355 when running "npm audit" in our CI pipeline. If you are using the extension V1.3.0, please switch to the latest early access release.

Description: When creating a new ASP.net application, you will see the following error: Internal server error :: Error (500) - 'PlatformConfig' object has no attribute 'init_validation_tables'

Description: When trying to set device_cgroup_rules in the extraparams property, a syntax validation error prevents from proceeding.
If setting up the property as device_cgroup_rule just to be able to continue and after that edit the YAML, another syntax validation error happens when trying to set the rules to \[ "c 199:* rmw" , "c 226:* rmw" ].

Workaround: Edit the property manually inside the file "appconfig_0/config.yaml".

Description: A vulnerability in the NPM package "follows-redirects" has been patched and we must update to using the patched version as soon as possible. Learn more about the vulnerability on CVE-2022-0155: Exposure of sensitive information in follow-redirects

Description: When editing environment variables in the tasks.json file, for example when configuring a C/C++ build, the extension overwrites - and therefore ignores - them during the build process.

Workaround: This is fixed. Update to the latest early access of the VS Code extension.

Description: Due to validation files missing for .NET Blazor applications, it is not possible to create projects for the provided Blazor templates.

Description: To make the user experience with the extensions more reliable, we have introduced input fields validation. With it, file paths with some characters like dot (.) and dash (-) were evaluated as invalid, even though they are actually valid.

Description: A customer reported that when he tries to deploy his application using the VS Code Extension, it was taking way too long. He noticed that each time he tried to build the image, a new appconfig_0 folder would be created inside of the previous one, in a loop-like format. This issue only affects .NET projects.

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.

Description: Often during development, you may need to reboot your device. We are conveniently adding reboot and shutdown buttons to our IDE Extensions, so the task is made easier.

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

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: 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.

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".

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.

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

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.

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.

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.

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.

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: 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.

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: 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.

Description: Uno Platform templates integrated into the IDE Extensions.

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

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: 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.

Description: Update .NET runtime version to 5.

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

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: Add support to Debian Bullseye in the IDE extensions

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.

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: 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: 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.

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: Add support to Debian Bullseye in the IDE extensions

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

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

Description: Qt applications development support in VS Code.

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: 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.

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.

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.

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