Torizon IDE Extensions Issue Tracker

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: Each template may have its own particularities, like the Python templates that have a method of creating a virtual environment that only applies to them. We will provide documentation for each template and it will be possible to read it directly on VS Code after you create a new project from a template.

Description: Error pop-up "Cannot read properties of undefined (reading 'globalState')" prevents the connected devices feature to work.

Description: The Qt QML C++ template does not work with the error "qmake: could not exec '/usr/lib/qt5/bin/qmake': No such file or directory".

Description: As Python is a popular development language, Toradex will provide CLI and PySide (Qt QML) templates for the new IDE Extensions.

Description: The new IDE Extension proposal is going to be released in Toradex Labs, thus a webpage for the project will be created, so you can learn the benefits, how to get started, and how to provide feedback.

Update: the page has been released and is available on Toradex Labs.

Description: The new Torizon IDE will have a repository with two types of templates: (1) those maintained by Toradex and (2) those provided and maintained by the community. This task aims to create the repository and structure.

Update: the repository is available on our GitHub as vscode-torizon-templates.

Description: The VS Code Extension for Torizon leverages third-party extensions to improve the development experience.
For a better UX, we let the users know directly in VS Code what extensions are recommended and easily install them.

Description: As reported on Pyhton app ownership issue, the release Dockerfiles for Python pass the wrong argument to "setup.sh", leading to a wrong app ownership issue.

Description: This is a regular maintenance task and not impact users, unless you want to build Moses from source. As versions of libraries used by Moses mismatch, it fails to start with the error "ModuleNotFoundError: No module named 'openapi_spec_validator.handlers'"

Update: if you want to build Moses from source, use the "dev" branch, where this is fixed.

Description: To make it easier for you to set up your own CI pipeline from a project built with VS Code, we plan to write documentation and create an example.

Update: documentation is available on Visual Studio Code Extension for Torizon - Continuous Integration and Conntinuous Delivery.

Description: The Torizon IDE Backend Command-line Interface does not allow building the SDK container for C/C++ projects. Due to this, it is currently not possible to build such projects in a CI environment.

Update: this task has been rejected because SDK operations including build the SDK, are already supported.

Description: The current Torizon QtDesignStudio support plugin asks for a folder where the QtDesignStudio is installed. Any input, even a valid one, triggers a red error saying "URI with a scheme is expected".

Description: The extension currently relies on a number of protocols and ports that are used on the host machine. When access to these are blocked by firewall/antivirus it can cause the extension to fail in ways that aren't obvious to debug.

Additionally, this info is useful to use Moses in a CI environment. This is especially useful given that projects that use an SDK (C/C++) run on a different port.

Description: When creating or opening an existing C/C++ application, a console reports "chgrp: changing group of '/var/run/docker.sock': Operation not permitted".

Workaround: While this message seems alarming at first sight, it has no negative impact and you can ignore it.

Description: When running the command "Torizon: export docker-compose file", the generated Docker Compose file misses cgroup rules configured in the project.

Workaround: Manually add the cgroup_rules to the generated Docker Compose file. Check out the Compose v2 reference doc.

Description: The first time that a c/c++ project is loaded, also every time the devpackages change which lead to a reload and rebuild of the SDK (that uses the devcontainer feature) the extension is not loaded and in fact is disabled.

Workaround: To enable it, the workaround is to reload the window (ctrl+shift+p->→ Reload Window)

Description: This error is a side-effect of another known bug, in which device_cgroup_rules is not being properly added to the autogenerated Docker Compose files.

Description: VS 2019 does not build project if moses is using different port than 5000

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

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.

Description: While we migrate the Uno Platform integration support from experimental to stable, the documentation present on GitHub will be migrated to the Toradex developer website

Description: As we plan a stable release of VS Code, it was decided to update the Uno Platform integration from experimental to supported. It will be updated to the latest version, working with .NET 6.

Documentation on GitHub is deprecated and an updated version of it released on the Developer website

Description: When opening any project without IDs and keys, removed with the command "Torizon: Remove IDs and keys from application", the "appconfig_0/config.yaml" file contents are deleted.

Description: When creating a new TCB project on VS Code, there is an option to select the image currently on the device as the image to initialize the project.
For pre-releases (monthly and nightly images), Artifactory has a pruning policy and there are no guarantees that the image from the device will still be available for fetching. This leads to the project not being fully created.

Description: Recently, the support of some SoMs was dropped (apalis-imx8x, colibri-imx8x-v10b, colibri-imx7, colibri-imx6ull) and others were added (colibri-imx6ull-emmc). We are reviewing the list of supported SoMs, adding the missing ones and removing the obsolete ones.

Description: When creating a new volume in the Torizon properties, if the value of the property is set to an absolute path (for example /tmp), the extension will not allow that with the error: "Value does not appear to be a valid relative file path."

Description: Adding the YAML extension required for some projects as a global dependency causes the extension to fail to start inside the development container for C/C++ projects.

Workaround: Update to the latest version of the VS Code extension for Torizon (early access).

Description: For community devices that returns `aarch64` instead of `arm64` from `arch` command, the Moses back-end does not connect saying it is an `Unsupported architecture`

Description: Microsoft has released .NET 6 as a Long Term Support (LTS) version. We are adding support of .NET 6 to our IDE extension, including templates.
Support for .NET 5 will be kept for existing projects, but it will be omitted from the "create new project" templates.

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

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

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.

Description: The Torizon Platform is envisioned to be an easy-to-use platform for embedded systems. To achieve this goal, Toradex provides the TorizonCore OS as a binary distribution, which means you don't need to build it from source with the Yocto Project, for instance.
To help you customize TorizonCore without having to rebuild the OS, we provide the TorizonCore Builder tool. It is a command-line tool that allows customizing the OS behavior, device tree, splash screen, among other features.
As a further step to improve your end-to-end development experience, we are creating an integration between TorizonCore Builder and the Visual Studio Code Extension for Torizon. This integration will abstract the calls to command-line commands and make it easier and faster to deploy and test your changes to the board, among other benefits.

Learn how to get started on TorizonCore Builder VS Code Integration

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

Description: Verdin iMX8M Plus support in the IDE Extensions.

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

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: Base container for arm64-wayland platform does not include Vivante drivers.

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.

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.

Description: Fix typo in the release container deployment message.

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

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

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

Description: In the VS Code Extension for Torizon 1.x (early access only), the TorizonCore Builder integration has been added to the main extension, as documented on TorizonCore Builder VS Code Integration.

With the creation of version 2.x, also known as ApolloX, it was decided to split the TorizonCore Builder integration into an extension of its own. In ApolloX, a template will be added so users can integrate their OS customization side-by-side with their application development.

Description: For C/C++ projects, the devcontainer fails to load with "Exit code 1". This happens since the Microsoft Remote - Containers version 0.238.2 was released.

We have reported the issue upstream and are following-up on it: Problem when opening a devcontainer on Ubuntu 20.04

Update: Further investigation seems to indicate that a newer version of Docker (20.10.17) fixes the issue.

Workaround: Either downgrade the Remote - Containers extension to version 0.234.0 or upgrade Docker to version 20.10.17

Description: This is not a supported use case.

It is currently not possible to configure a custom base image for the container in a project created via the Torizon Visual Studio Code Extension. This does not affect projects that can use the images that are provided in the templates.

Workaround: If you must start from a base image that is not supported, you must write and build your own Dockerfile.

We are working on a new template-oriented concept for the VS Code IDE Extension, where it will be possible to configure this field.

Description: Running version 1.4.271 of the IDE extension under VSCode for Windows, a customer trying to deploy a .NET Core console “hello world” app gets a popup that “The pipe program ‘ssh’ exited unexpectedly with code 255.”

Starting: "ssh" -T -p %{port} -i %{keypath} -o StrictHostKeyChecking=no -o "UserKnownHostsFile /dev/null" %{devicelogin} "/vsdbg/vsdbg --interpreter=vscode"
Error from pipe program 'ssh': Bad port '%{port}'
The pipe program 'ssh' exited unexpectedly with code 255.

Description: The IDE Extensions debugger comes configured in a way that it’s very easy to debug the application source code. It does not include symbols and source code for the Debian packages in the SDK, though.
This makes it one step harder for users to get more meaningful stack traces or “step into“ library functions, often useful to debug potential issues with the libraries themselves.

Workaround: To shorten this gap, it was documented one way to allow library debugging on Add Debug Symbols and Source Code From Debian Feeds.

Description: At the moment, often the Torizon configuration files are modified and Git keeps stating they have changed. It contains info that is not essential to the project. Let's call this info *environment configuration*.
On the other hand, the same file has very important info that is essential to the project and that only changes when you modify them, let's call it *project configuration*.
It is annoying to keep being asked to commit environment configuration if needed at all. We plan to split it into two files and keep the environment configuration in .gitignore.

Description: When you deploy and debug a Python application for the second time in a row, VS Code may not switch focus from the terminal to the debug console.

Workaround: Manually click on the debug console to switch focus.

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.

Description: The project configuration is autogenerated and stored on a "config.yaml" file in the project directory. When this file is changed manually - for example, on a "git checkout" - the IDE does not recognizes changes, which leads to build errors.

Workaround: Whenever you check out a new git branch, reload the VS Code window.

Description: At the moment, we only support creating Torizon projects using the VS Code command palette. For new users, it may be interesting to have a button that guides them through their first project creation.

Workaround: Create and configure a project from the command palette.

Description: A customer with 7 keys in their SSH agent has reported that the IDE Extension fails to connect to the board with the error "Received disconnect from 192.168.17.89 port 22:2: Too many authentication failures".

Workaround: Some SSH servers have a configurable option for the number of authentication failures before it throws an error. To overcome that, you may either (1) change the config to a bigger number or (2) remove some keys from your agent.

Description: We plan to make some changes to .gitignore files, deprecating project-specific entries. With that, we will also document what is supported and what is expected from users with regards to .gitignore files generated by the IDE Extension.

Description: Currently, when exporting a Docker Compose file, the default name is "# docker-compose.yml", but sometimes it is reported by users that the file name defaults to whatever name of the directory you plan to save it to.

Workaround: Rename your file before saving it for the first time. If you have already saved it with the wrong name, rename the file to your liking.

Description: VS Code has a feature to remote access another development machine through remote SSH connections.
You may have two machines where you do development: (1) is a headless machine where the processing is done, and (2) is a computer where you run VS Code and do the programming.
Also, the same mechanism is used by VS Code when you have (1) an instance of VS Code installed on Windows and (2) want to create a Torizon C/C++ project in WSL.

In such situations, when creating a Torizon C/C++ project you will get the following error: The Remote-Containers extension (ms-vscode-remote.remote-containers) is required to develop C/C++ applications on Torizon.

Workaround: Currently, it is only possible to create a new Torizon C/C++ project on a local machine, without the use of the remote SSH connection. Please create your project on the same machine you have VS Code installed and don’t use WSL.

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.

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.

Description: Often when developing an app that has a remote UI or any kind of back-end server over the network, one has to do the following:

• Open browser
• Find IP or copy hostname, e.g. `apalis-imx8-01234567.local`
• Paste on browser