mirror of https://github.com/home-assistant/supervisor.git synced 2025-12-25 04:46:25 +00:00

Go to file

Stefan Agner f996e60784 Fix docker image pull progress blocked by small layers

Small Docker layers (typically <100 bytes) can skip the downloading phase
entirely, going directly from "Pulling fs layer" to "Download complete"
without emitting any progress events with byte counts. This caused the
aggregate progress calculation to block indefinitely, as it required all
layer jobs to have their `extra` field populated with byte counts before
proceeding.

The issue manifested as parent job progress jumping from 0% to 97.9% after
long delays, as seen when a 96-byte layer held up progress reporting for
~50 seconds until it finally reached the "Extracting" phase.

Set a minimal `extra` field (current=1, total=1) when layers reach
"Download complete" without having gone through the downloading phase.
This allows the aggregate progress calculation to proceed immediately
while still correctly representing the layer as 100% downloaded.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-11-05 14:40:16 +01:00

.devcontainer

Update Python to 3.13 (#5564 )

2025-01-21 11:57:30 +01:00

.github

Bump getsentry/action-release from 3.3.0 to 3.4.0 (#6284 )

2025-11-05 12:17:51 +01:00

.vscode

Migrate to Ruff for lint and format (#4852 )

2024-02-05 11:37:39 -05:00

rootfs/etc

Avoid empty newlines in Supervisor logs (#4698 )

2023-11-13 20:12:17 +01:00

script

Add mypy to ci and precommit (#5969 )

2025-06-24 11:48:03 +02:00

supervisor

Fix docker image pull progress blocked by small layers

2025-11-05 14:40:16 +01:00

tests

Fix docker image pull progress blocked by small layers

2025-11-05 14:40:16 +01:00

.dockerignore

…

.gitignore

Storage space usage API (#6046 )

2025-08-19 10:54:53 +02:00

.ha-frontend-version

Update frontend to version 20250925.1 (#6120 )

2025-09-26 12:42:39 +02:00

.hadolint.yaml

Revert "Revert "Update base images to 3.11-alpine3.18 (#4639 )" (#4646 )" (#4657 )

2023-11-02 11:29:15 +01:00

.pre-commit-config.yaml

Bump ruff from 0.14.2 to 0.14.3 (#6280 )

2025-10-31 11:42:39 -04:00

.vcnignore

Sign code folder (#2725 )

2021-03-16 15:47:40 +01:00

AGENTS.md

Add AGENTS.md symlink (#6237 )

2025-10-08 10:44:49 +02:00

build.yaml

Bump cosign to v2.5.3 (#6204 )

2025-09-23 16:43:03 +02:00

CLAUDE.md

Add GitHub Copilot/Claude instruction (#5986 )

2025-07-04 07:05:05 +02:00

codecov.yaml

Remove annotations (#2007 )

2020-09-03 16:36:09 +02:00

Dockerfile

Bump uv to 0.8.9 (#6097 )

2025-08-13 16:27:56 +02:00

LICENSE

Update LICENSE

2020-07-29 14:45:37 +02:00

MANIFEST.in

…

pyproject.toml

Bump setuptools from 80.8.0 to 80.9.0 (#5919 )

2025-05-27 12:13:06 +02:00

README.md

Add OHF logo to README (#5316 )

2024-09-30 18:42:08 +02:00

requirements_tests.txt

Bump ruff from 0.14.2 to 0.14.3 (#6280 )

2025-10-31 11:42:39 -04:00

requirements.txt

Bump sentry-sdk from 2.42.1 to 2.43.0 (#6279 )

2025-10-30 14:24:50 -04:00

setup.py

Use version which is treated CalVer by AwesomeVersion (#5572 )

2025-01-24 09:59:50 +01:00

tox.ini

Migrate to Ruff for lint and format (#4852 )

2024-02-05 11:37:39 -05:00

README.md

Home Assistant Supervisor

First private cloud solution for home automation

Home Assistant (former Hass.io) is a container-based system for managing your Home Assistant Core installation and related applications. The system is controlled via Home Assistant which communicates with the Supervisor. The Supervisor provides an API to manage the installation. This includes changing network settings or installing and updating software.

Installation

Installation instructions can be found at https://home-assistant.io/getting-started.

Development

For small changes and bugfixes you can just follow this, but for significant changes open a RFC first. Development instructions can be found here.

Release

Releases are done in 3 stages (channels) with this structure:

Pull requests are merged to the main branch.
A new build is pushed to the dev stage.
Releases are published.
A new build is pushed to the beta stage.
The stable.json file is updated.
The build that was pushed to beta will now be pushed to stable.