| Torizon IDE Extension for VS Code 2.5.0 |
 TIE-855 | Feature Request | As a user, I want to know how to add and debug extra files (shared library binaries, etc), including those that are outside the project's workspace | Not applicable | Torizon IDE Extension 2 | |
Description: Commonly, developers want to use shared libraries available on their PCs in other directories outside the Torizon project workspace. It is clumsy to have to copy them inside the Torizon workspace and keep them up-to-date.
Support for this use case has been added to the Torizon IDE Extension for VS Code and documented on Torizon IDE Extension - Add Packages, Libraries and Tools Workaround: Use the pre-release version of the extension until 2.5.0 is released. |
| TIE-825 | Feature Request | Deprecate the IDE 1 on the VS Code Marketplace | Not applicable | Visual Studio Code Extension | |
Description: The IDE 1 is in maintenance mode, and new projects must use the IDE 2. To clarify this with new users, the version 1 is being set as deprecated on the VS Code marketplace, so you don't install it by mistake and start using it on a new project. |
| TIE-823 | Known Issue | Unable to debug Python apps on Ubuntu 22.04 due to error "no such option: --break-system packages" | Not applicable | Torizon IDE Extension 2 | Low |
Description: Due to the version of pip available on the Ubuntu 22.04 LTS package feeds being too old, an error installing dependencies with pip prevents the Python debug to work. Workaround: Upgrade pip with "pip install --upgrade pip" instead of using the apt package manager. |
| TIE-810 | Known Issue | When using WSL, due to performance penalties, the user must not be allowed to save a project on "/mnt/c" | Not applicable | Torizon IDE Extension 2 | Low |
Description: If you save a project in the Windows file system, a huge performance drawback will happen due to this Windows-Linux file system translation being done through a network protocol, leading to 10x slower build times. Workaround: Create a project in a folder that is not "/mnt/c" |
| TIE-808 | Known Issue | When using WSL, avahi-resolve does not work, thus not resolving the hostnames properly | Not applicable | Torizon IDE Extension 2 | Low |
Description: For Windows users, the Toradex SoMs IP are listed instead of their hostname, which makes the user experience of the IDE Extension less optimal. |
| TIE-791 | Known Issue | Wrong network interface is selected when host has two interfaces | Not applicable | Torizon IDE Extension 2 | Low |
Description: When the host PC has more than one network interface, the extension will pick the first one, which may not be the interface that the target device is connected to. This leads to the extension not being able to connect to the target. Workaround: Edit the "host_ip" in the VS Code settings.json to use the IP address of the network interface that is the same one the target is connected to. |
| TIE-787 | Known Issue | VS Code prints the warning ""No qmlls can be found in current Python environment."" related to QML and python, when using a C++ QML project | Not applicable | Torizon IDE Extension 2 | Low |
Description: When using a C++ Qt QML project, a warning about Python is printed "No qmlls can be found in current Python environment." Workaround: Just ignore the warning. |
| TIE-785 | Known Issue | "Try Update Template" fails for TorizonCore Builder template with the error "Cannot find path '/home/username/.apollox/tcb/.conf/update.json' because it does not exist." | Not applicable | Torizon IDE Extension 2 | Low |
Description: The Torizon IDE Extension 2 has a feature that allows a user to update their project against the latest version of the template that created it, so they get the latest features and fixes at the template level.
For TorizonCore Builder templates, this feature does not work, and the following error is displayed: "Cannot find path '/home/username/.apollox/tcb/.conf/update.json' because it does not exist." |
| TIE-784 | Feature Request | As a user, I want a better description about the "WARNING: THIS DEVICE IS IN ENGINEERING MODE", so I can understand the impact of this feature and how to get back to normal mode | Not applicable | Torizon IDE Extension 2 | |
Description: After connecting a device to the IDE Extension 2 for the first time, the following message is printed in the device debug UART or SSH session: WARNING: THIS DEVICE IS IN ENGINEERING MODE
To provide a more meaningful message, a hyperlink to https://developer.toradex.com/torizon/application-development/ide-extension/ is printed so you can learn more about it. |
| TIE-762 | Known Issue | Torizon IDE Extension 2 does not connect to the device if the password has special characters, with error "undefined" | Not applicable | Torizon IDE Extension 2 | Low |
Description: The Torizon IDE Extension 2 does not connect to the device if the password has special characters, with the error "undefined". |
| TIE-758 | Known Issue | Templates for Debian Bookworm using graphic interface are not enabling hardware acceleration by the GPU on i.MX8 | Not applicable | Torizon IDE Extension 2 | Low |
Description: As reported on Limited Support for graphical acceleration on downstream-based modules #51, the templates for i.MX8 are not accelerated by the GPU. |
| TIE-752 | Known Issue | If the default device IP changes, the extension does not update the insecure registry entry in the daemon.json, generating a device not reached error | Not applicable | Torizon IDE Extension 2 | Low |
Description: As reported in a community post , when a device IP changes, the insecure registry entry is not updated in the daemon.json. This generates a "Device not reached! Please check if the device is turned on and connected to the network" warning message followed by a device not reached error. Workaround: Remove the device from the IDE extension device list and re-add it. |
| TIE-726 | Known Issue | "Create Production Docker Image" task shows a "Successfully Finished" message even when the task fails | Not applicable | Torizon IDE Extension 2 | Low |
Description: The "Create Production Docker Image" task shows a "Successfully Finished" message even when some part of the task has failed. |
| TIE-747 | Feature Request | As a user, I want to be able to run CI/CD pipelines from ApolloX templates in Gitlab CI | Not applicable | VS Code Extension 2.0 | |
Description: The Toradex templates for the IDE 2.0 come with integrated CI pipelines for popular platforms. In this task, GitLab CI integration is added. |
| TIE-737 | Feature Request | As a user, I want to be able to update my application against the latest template updates over time, so I can get the latest and greatest features and fixes | Not applicable | VS Code Extension 2.0 | |
Description: In IDE 2.0 also known as ApolloX, once you create a project from a template, you have the freedom to modify the template to your project needs, and the ownership to maintain it. To make things easier for you to rebase your project against updates in the templates, we plan to introduce a feature that starts the rebase, allows you to resolve conflicts, and ultimately makes it possible for you to keep your projects up-to-date over their lifecycle. |
| TIE-733 | Feature Request | As a user, I want to have a ASP.NET Blazor Server template to create a project on the extension | Not applicable | VS Code Extension 2.0 | |
Description: As ASP.NET is a popular web development framework, Toradex will provide a ASP.NET Blazor Server template for the new IDE Extensions. |
| TIE-730 | Feature Request | As a user, I want to have documentation about the specifics of each template directly on VS Code, so I learn how to configure and use my project following the template proposal | Not applicable | VS Code Extension 2.0 | |
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. |
| TIE-729 | Feature Request | As a user, I want to be able to change the default user to run my application (run as root for example) | Not applicable | VS Code Extension 2.0 | |
Description: In a few scenarios, setting the user inside the container as "root" instead of "torizon" is required. The IDE Extensions debugger process needs to know this information somehow, in addition to setting it on the Dockerfile or the Docker Compose file. |
| TIE-728 | Known Issue | Error pop-up "Cannot read properties of undefined (reading 'globalState')" prevents the connected devices feature to work | Not applicable | VS Code Extension 2.0 | Low |
Description: Error pop-up "Cannot read properties of undefined (reading 'globalState')" prevents the connected devices feature to work. |
| TIE-722 | Known Issue | .NET Console and .NET Uno templates debugging not working on the board with error "unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /var/rootdirs/home/torizon/Dockerfile.debug: no such file or directory" | Not applicable | VS Code Extension 2.0 | Low |
Description: The .NET Console and Uno templates are not working when deployed to the board, with the error "unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /var/rootdirs/home/torizon/Dockerfile.debug: no such file or directory". |
| TIE-720 | Known Issue | Qt QML C++ template debugging not working with error "qmake: could not exec '/usr/lib/qt5/bin/qmake': No such file or directory" | Not applicable | VS Code Extension 2.0 | Low |
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". |
| TIE-715 | Feature Request | As a user, I want to create and update a project for any active TorizonCore version on VS Code | Not applicable | VS Code Extension 2.0 | |
Description: Different TorizonCore releases may use different versions of Debian Containers for Torizon. For example, in TorizonCore 5, containers are based on Debian Bullseye whereas, in TorizonCore 6, they are based on Debian Bookworm.
Due to this, a mechanism to allow you to create a project for the version of the Debian containers that matches the version of TorizonCore you are using is required. |
| TIE-713 | Known Issue | ApolloX installed as UI extension on Windows tries to run scripts on \bin\bash | Not applicable | VS Code Extension 2.0 | Low |
Description: The new IDE Extension, also known as ApolloX, is not meant to be installed on Windows directly. It is only meant to be installed on WSL 2. On this task, the option to install it on Windows will be disabled to prevent errors such as "\bin\bash does not exist". |
| TIE-671 | Feature Request | As a user, I want the VS Code extension integrated with the Platform Services API as soon as I create a project from the template, so I can adopt a DevOps-enabled workflow with low effort | Not applicable | VS Code Extension 2.0 | |
Description: In the IDE 2.0, also known as ApolloX, it is envisioned that the integration with the Torizon Platform Services - possible through their API - is part of the development workflow and the project lifecycle from day 1, and not just a command to run at the end of the development cycle right before release.
To achieve such goal, we plan to setup projects around a DevOps-oriented workflow where the CI pipelines already have steps that integrate with the Torizon Platform Services, including operations such as pushing the application to the platform and deploying it to a test fleet of devices.
The CI pipelines will be provided for GitHub Actions. |
| TIE-665 | Feature Request | As a user, I want to have Python templates to create a project on the extension | Not applicable | VS Code Extension 2.0 | |
Description: As Python is a popular development language, Toradex will provide CLI and PySide (Qt QML) templates for the new IDE Extensions. |
| TIE-663 | Feature Request | As a user, I want to use the VS Code extension with Docker Compose V2 | Not applicable | VS Code Extension 2.0 | |
Description: In the latest Docker installation instructions for Ubuntu which is the Linux distro we test ApolloX against, Docker Compose V2 is installed. Therefore, all templates are being updated to call Docker Compose V2 as "docker compose" instead of "docker-compose", which was the default way for Compose V1. Workaround: Either install Docker Compose V2 on your development PC (recommended), or symlink/alias the "docker-compose" to point to "docker compose". |
| TIE-652 | Feature Request | As a user, I want a Toradex Labs page, so I learn about the new IDE Extension and its value proposition | Not applicable | VS Code Extension 2.0 | |
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. |
| TIE-651 | Feature Request | As a user, I want to learn what is the proposed development workflow for the new VS Code IDE Extension | Not applicable | VS Code Extension 2.0 | |
Description: Documentation for ApolloX will be released as it gets promoted to stable. |
| TIE-650 | Feature Request | As a user, I want an easy way to configure a multi-container workspace from templates | Not applicable | VS Code Extension 2.0 | |
Description: Throughout the existence of our IDE Extension for VS Code V1.x, several customers requested the ability to develop multi-container applications. Given this requirement, on the new IDE Extension for VS Code 2.x, multi-container support will be added. |
| TIE-647 | Feature Request | As a user, I want a public repository for the Torizon IDE templates, so I can freely modify and contribute to the templates | Not applicable | VS Code Extension 2.0 | |
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. |
| TIE-643 | Feature Request | As a user, I want minimal documentation for the new IDE Extension for VS Code, so I can evaluate it as early as possible | Not applicable | VS Code Extension 2.0 | |
Description: As we come up with a new concept for the IDE Extensions on Toradex Labs, it is planned to release documentation as early as possible so you can test and provide feedback about it as early as possible.
Update: documentation is available on toradex/torizon-experimental-torizon-ide-v2-docs. |
| TIE-583 | Feature Request | As a user, I want to learn about what is provided and what is expected of me about .gitignore files, so I understand what I must maintain by myself during the project lifecycle | Not applicable | Visual Studio Code Extension | |
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. |
| TIE-259 | Feature Request | As a user, I want to be prompted to install third-party extensions that are required by the Torizon extension | Not applicable | VS Code Extension 2.0 | |
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. |
| TIE-717 | Known Issue | On Python templates, the release Dockerfile has the argument debug instead of release for the setup.sh and cleanup.sh scripts | Not applicable | Moses (IDE Backend), Visual Studio Code Extension | Low |
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. |
| TIE-670 | Known Issue | Documentation about Torizon IDE Backend Command-line Interface needs to be updated to include information about the CI/CD pipeline generation command | Not applicable | Moses (IDE Backend) | Low |
Description: The IDE extension CLI documentation is outdated, missing the information about the new CI/CD Pipeline Generation Command and it should be updated.
Also, the IDE Extensions back-end is built and published as a standalone package, meant to be used in CI scripts. It is available on our artifacts server.
The documentation on how to install it is outdated, stating that one must also install either the Visual Studio or the VS Code extension, while it is not necessary anymore. |
| TIE-662 | Known Issue | Moses fails to start due to a dependency problem, with the error "ModuleNotFoundError: No module named 'openapi_spec_validator.handlers'" | Not applicable | Moses (IDE Backend) | Low |
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. |
| TIE-658 | Known Issue | Publish application to OTA Server error "FileNotFoundError: [Errno 2] No such file or directory: '/credentials/credentials.zip'" for C/C++ applications | Not applicable | Visual Studio Code Extension | Low |
Description: The error "FileNotFoundError: [Errno 2] No such file or directory: '/credentials/credentials.zip'" happens when trying to push files to OTA from the VS Code extension on a C/C++ project. |
| TIE-655 | Feature Request | As a user, I want documentation on how to create a CI/CD pipeline for my project | Not applicable | Visual Studio Code Extension | |
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. |
| TIE-640 | Feature Request | As a user, I want to build my application in a CI/CD environment as I'm using the F5 from VS Code without write the docker run command | Not applicable | Moses (IDE Backend) | |
Description: Today in a CI/CD environment, you need to write a "docker run" command to build the application. This disrupts the IDE Extensions experience since while on the IDE this is made by VS Code behind the scenes, using data present in "launch.json" and "tasks.json".
We will introduce a command on VS Code that generates the build instructions, so the UX of setting up a DevOps CI pipeline is simplified.
Update: the command is available in the early access release, and documentation on how to use it in the Visual Studio Code Extension for Torizon. |
| TIE-595 | Feature Request | As a user, I want to build SDK containers with tdskt | Not applicable | Moses (IDE Backend) | Low |
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. |
| TIE-594 | Feature Request | As a user, I want an update the list of supported SoMs in VS Code, so I can create a new project that supports my SoM | Colibri iMX6ULL, Colibri iMX7, Colibri iMX8X | Moses (IDE Backend) | |
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. |
| TIE-573 | Known Issue | Input validation failure on QTDesignStudio preferences "URI with a scheme is expected" | Not applicable | Qt Design Studio Extension for VS Code | Low |
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". |
| TIE-497 | Feature Request | As a user, I want to be able to install the IDE-backend on servers/containers without having to install an IDE-extension | Not applicable | Moses (IDE Backend) | |
Description: The IDE Backend for our VS and VS Code extensions is bundled with the IDE Extensions installers. This means that, in practice, if you want to install it you must also install an extension.
This is not ideal for CI/CD pipelines, therefore we plan to release the backend standalone, so it can be easily integrated.
Update: this is done and Moses is being published on https://artifacts.toradex.com:443/artifactory/ideextension-moses-prod-frankfurt/moses-linux.zip. |
| TIE-352 | Feature Request | As a user, I want public documentation of ports/protocols used by VS Code, VS and the IDE Backend | Not applicable | Moses (IDE Backend) | Low |
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. |
| Visual Studio 2019 IDe Extension V1.6.0 |
| TIE-352 | Feature Request | As a user, I want public documentation of ports/protocols used by VS Code, VS and the IDE Backend | Not applicable | Moses (IDE Backend) | Low |
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. |
| TIE-627 | Feature Request | "Torizon: Build release container for the application" does not compile the source code for Qt projects with error "make: *** No rule to make target 'install'. Stop.". A similar issue also happens for C and C++ singlefile projects | Not applicable | Visual Studio Code Extension | Low |
Description: When trying to execute the command Torizon: Build release container for the applicationon Qt-based C/C++ projects the source code does not compile, showing the following error: make: *** No rule to make target 'install'. Stop. Workaround: Workaround: Switching to the release configuration with the command `Torizon C/C++: Switch to release configuration`, executing the default build, deploy and run on debug mode command by pressing `F5` and them running the command `Torizon: Build release container for the application` |
| TIE-560 | Known Issue | build_release task not working on Qt Based projects | Not applicable | Visual Studio Code Extension | Low |
Description: There was a report that the build_release for Qt-based projects is not working. We will investigate it and, if the bug is confirmed, fix it. Workaround: You can edit the ".vscode/tasks.json" manually and add the missing property "dependsOn: qmake_release" to the "build_release" task. |
| TIE-639 | Feature Request | As a user, I want the TorizonCore Builder IDE integration supported on VS Code IDE V2.0 (ApolloX) | Not applicable | TorizonCore Builder Extension for VS Code, Visual Studio Code Extension | |
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.
In the version 2.x, also known as ApolloX, we reintegrated the TorizonCore Builder support. ApolloX uses TorizonCore Builder VS Code extension as a dependency for OS customization features. |
| TIE-642 | Known Issue | Enable ARM emulation inside a dev container fails with error "Command 'Torizon: Enable ARM emulation for docker containers' resulted in an error (command 'torizon.enableARMemulation' not found)" | | Visual Studio Code Extension | Low |
Description: When a C/C++ project is opened inside a container on VS Code - which is common - it is not possible to enable ARM emulation. This is because ARM emulation must be enabled on the host. Workaround: Either (1) close the remote container and run the command again or (2) run the command from the command-line. |
| TIE-636 | Known Issue | VS Code Extension C/C++ environment "Exit code 1" | Not applicable | Visual Studio Code Extension | Critical |
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 |
| TIE-630 | Known Issue | A ASP.NET created with the extension is not using the right EnvironmentName while in Debug Mode | Not applicable | Visual Studio Code Extension | Low |
Description: The EnvironmentName on an ASP.NET project is being defined as Production even if you are developing in Debug Mode.
Update: there are no plans to fix this potential bug, because it is considered a configuration issue. A potential fix might adversely impact other customers' projects. Workaround: Add the following line to your project's ".vscode/launch.json" file:
"env": { "ASPNETCORE_ENVIRONMENT": "Development" }, |
| TIE-629 | Known Issue | The baseimage configuration of a project is ignored | | Visual Studio Code Extension | Low |
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. |
| TIE-624 | Known Issue | Network connections not being made when using WebSockets on ASP.NET applications | Not applicable | Visual Studio Code Extension | Low |
Description: An end-user has a specific application that uses WebSockets to connect back to a PC running a standalone application. When running their app in a container manually on the target, the connections to the PC go through. However, when debugging their app from within the IDE extension, those connections are never seen by the PC.
Update: this task has been rejected because the issue was on misuse of "System.Net.WebSockets". As general advice, if you face a similar issue, and you can use a library that provides a higher level of abstraction, that might help prevent such type of error. |
| TIE-612 | Known Issue | Creating a new "Torizon Image Customization Project" with a quarterly build sets "build-date: NaN" in tcbuild.yaml | Not applicable | Visual Studio Code Extension | Low |
Description: When creating a new TorizonCore Customization Project with the VSCode IDE Extension, it prompts you to select the TorizonCore version to be used. After the setup is finished, the generated template tcbuild.yaml sets the property "build-date" as "NaN" Workaround: For quarterly or LTS images, remove the "build-date" field. |
| TIE-606 | Known Issue | IDE Extension on Windows fails due to undefined variable "%{port}" | Not applicable | Visual Studio Code Extension | Low |
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. |
| TIE-593 | Feature Request | As a user, I want a more obvious command to add a new Torizon project configuration | Not applicable | Moses (IDE Backend) | |
Description: A new project configuration is useful in some cases, for example when adding support for two different platforms (32-bit and 64-bit) in the same project, or testing a new configuration for the same platform.
In the command palette, the command to add a new configuration will be rephrased from "Torizon: Add support for a different platform" to "Torizon: Add a new configuration". |
| TIE-584 | Feature Request | As a user, I want to easily debug Debian libs | Not applicable | Moses (IDE Backend), Visual Studio Code Extension | Low |
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. |
| TIE-581 | Feature Request | As a user, I never want project IDs and keys committed to my Git repository by default | Not applicable | Moses (IDE Backend) | Low |
Description: As of today, to keep IDs and keys outside a Git repository, you need to run the command Torizon: Remove IDs and keys from application
We plan to deprecate this command and keep all related files ignored in the .gitignore that generated when you create a new Torizon project from template. |
| TIE-580 | Feature Request | As a user, I want to split Torizon configuration files in version-controlled and ignored with .gitignore | Not applicable | Moses (IDE Backend) | |
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. |
| TIE-576 | Known Issue | When I export a docker-compose file and then do a "Save As", the default name should be docker-compose.yml | | Visual Studio Code Extension | Low |
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. |
| TIE-533 | Known Issue | As a user, I want to be able to create C/C++ projects on WSL or any other remote connection by VS Code | Not applicable | Visual Studio Code Extension | Low |
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. |
| TIE-523 | Known Issue | As a user, I want to push application to OTA Server directly from IDE Extensions | | Moses (IDE Backend), Visual Studio Code Extension | Low |
Description: It was only possible to reproduce it in the case that the tag parameter was set as "" instead of "/". But this is not a bug, as the proper way to push images to Dockerhub (or another registry) is by using the tag as "/".
Refer to the Docker tag reference for more information. |
| TIE-517 | Known Issue | VS Code doesn't automatically switch focus to the debug console when running a Python application for the second time | Not applicable | Visual Studio Code Extension | Low |
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. |
| TIE-465 | Feature Request | As a user, I want to develop CMake-based projects with Visual Studio | Not applicable | Visual Studio Extension | Low |
Description: The Visual Studio Extension for Torizon does not support a CMake oriented workflow. Workaround: We focus our development on the Visual Studio Code Extension for Torizon. It is a cross-platform environment, supports the C/C++ workflows and already provides templates for CMake.
Read the article C/C++ Development and Debugging on TorizonCore Using Visual Studio Code to learn more. |
| TIE-428 | Feature Request | As a user, I want container rebuilds to happen only when I changed properties that can be used inside the generated dockerfile. | | Moses (IDE Backend) | |
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. |
| TIE-397 | Feature Request | As a user, I want to configure extra arguments to be sent to Docker commands using the command-line syntax instead of the Docker Python API | Not applicable | Moses (IDE Backend), Visual Studio Code Extension | |
Description: As of now, the IDE extensions provide a field name "extraparams" that allows users to pass extra arguments to the Docker calls when running a container. Those extra arguments are expected in the Docker Python API syntax, since it is the same API used by Moses, the IDE back-end.
This is a bit confusing, since everywhere else in our documentation we use the command-line syntax instead. Therefore, to bridge this gap, we are introducing a configuration field named "dockercmdline" that has the same purpose as "extraparams" but accepts the command-line syntax instead of the Python API syntax. Workaround: Use "extraparams" with the Docker Python API syntax |
| TIE-376 | Feature Request | As a user, I want to be able to manually change the config.yaml file in the source directory | Not applicable | Visual Studio Code Extension | |
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. |
| TIE-369 | Feature Request | As a user, I want to see human-readable numbers on VS Code devices and containers info panel | Not applicable | Visual Studio Code Extension | Low |
Description: In the VS Code IDE Extension info panel, some memory numbers are presented in full, instead of using engineering notation (for example kB, MB, GB, etc.). This makes it hard to read those numbers. |
| TIE-368 | Feature Request | As a user, I want a button to create a new Torizon project on VS Code | Not applicable | Visual Studio Code Extension | Low |
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. |
| 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-118 | Feature Request | As a user, I want a button to open my default browser pointing to the board IP address or hostname | Not applicable | Visual Studio Code Extension | |
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
We already provide a shortcut button to open a terminal. In this task, we add a button that allows you to quickly open a browser pointing at your application |
| TIE-761 | Known Issue | Creating a multi container project with TCB templates hangs the system | Not applicable | Torizon IDE Extension 2 | Low |
Description: Although it is possible to choose and add a TCB template to create a multi-container project, this is not supported yet. |
| TIE-660 | Known Issue | A computer with many keys in the SSH agent might lead to the error "Received disconnect from 192.168.17.89 port 22:2: Too many authentication failures" when connecting to the board | Not applicable | Torizon IDE Extension 2, Visual Studio Code Extension | Low |
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. |
| TIE-582 | Feature Request | As a user, I want documentation stating that I need to maintain project-specific .gitignore entries, while Toradex only focuses on Torizon-specific .gitignore entries | Not applicable | Torizon IDE Extension 2 | |
Description: We don't have resources to add and - especially - maintain .gitignore files for all technologies we support (C Makefile, autotools, CMake, Qt QML, Qt Widgets, and so on). Let's call this project-specific entries.
We want, though, to keep .gitignore for everything that we create and users should not keep versioned. Let's call this Torizon-specific entries.
For this reason, we are removing support for project-specific entries and keeping only the Torizon-specific ones. |
| TIE-545 | Known Issue | Misleading warning about C/C++ toolchain not being found "Cannot find arm-linux-gnueabi-gcc" | Not applicable | Visual Studio Code Extension | Low |
Description: On a Makefile or CMake based project, in the "c_cpp_properties.json" file, there is the "compilerPath" variable that (by default) is set to "${env:CC}". This seems to be ok since "$CC" holds (by default) "arm-linux-gnueabihf-gcc" and this compiler is accessible from the terminal.
The Issue is that the “PROBLEMS” tab shows a warning "Cannot find arm-linux-gnueabi-gcc" and there is the squiggle under the "${env:CC}". Workaround: Just ignore the warning, everything works as expected. |
| TIE-518 | Known Issue | Invalid docker-compose.yml exported when using the field extraparams to set the "cap_add" property | Not applicable | Visual Studio Code Extension | Low |
Description: When exporting a docker-compose.yml using the VS Code extension, the "cap_add" field is formatted in a way that makes the YML file invalid. This required manual intervention to fix the file syntax after exporting it.
There are many scenarios where you'd need to set the "cap_add" field. One of them would be to configure the container to use the host network, required for using the CAN on TorizonCore. Workaround: Manually fix the syntax issue. |
| TIE-467 | Known Issue | Error when running commands during the VS Code extension startup | | Visual Studio Code Extension | Low |
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-459 | Known Issue | SDK container not existing notification is not displayed when re-opening an existing C/C++ project | | Visual Studio Code Extension | Low |
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-451 | Known Issue | Possible Incompatibility between our extension and VS 16.10.2 | | Visual Studio Extension | Low |
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-449 | Known Issue | rsync issues when application container is running as root | | Moses (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 |
| Torizon IDE Extension 2 for VS Code Next |
| TIE-821 | Known Issue | Github Actions does not work with private registries | Not applicable | Torizon IDE Extension 2 | Low |
Description: As reported on the Toradex community, GitHub Actions does not work with private registries. Workaround: Use the latest pre-release 2.1.100 or newer, where it has already been fixed. |
| TIE-796 | Feature Request | As a user, I want the tasks from the "task runner" and their properties well-described, so I can use the IDE Extension without asking the Toradex support for help | Not applicable | Torizon IDE Extension 2 | |
Description: As reported in the Toradex community, on the post Specify the GPU using ApolloX - create-production-image, some tasks and their respective required properties are not well-described, thus leading users to not be able to use them without asking the Toradex support. |
