Search by Tags

Torizon Platform Issue Tracker

 

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

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

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

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

Clear Filter
Issue #StatusSubjectModuleSeverity

Backlog
OTA-611Known IssueOSTree packages do not list a size in the UILow

Description: OSTree packages do not list a size in the OTA UI, making it difficult to plan for the amount of bandwidth required.

Workaround: The size of the download for OSTree packages depends on the objects already available on the targeted device, so the effective size will differ depending on which device is being updated. To properly calculate the size of the download for a particular device, you would need to download and process all of the commit metadata for the commits in question. libostree does not currently have an easy API for this, unfortunately. For the moment, the only workaround we can suggest is to test one update and measure.

OTA-482Feature RequestAdd a "Refresh" button on most pagesLow

Description: Add a "Refresh" button on Devices Panel

Workaround: Refresh all of OTA dashboard

OTA-409Feature RequestFrontend to support displaying toradex delegated targets (toradex published targets)All supported modulesLow

Description: Support displaying Toradex delegated targets

OTA-102Feature RequestTorizon OTA API Documentation

Description: The Torizon OTA API allows, for instance, CI/CD integration.