mirror of https://github.com/home-assistant/supervisor.git synced 2026-04-20 15:32:51 +00:00

Go to file

Stefan Agner 07f02a23be Prevent Sentry event feedback loop from warning handler (#6700 )

The custom warning_handler sends warnings to Sentry via
capture_exception. When the Sentry SDK's own HTTP transport triggers a
warning (e.g. urllib3 InsecureRequestWarning due to broken CA certs),
this creates a self-inducing feedback loop: the warning is captured,
sent to Sentry, which triggers another warning, and so on.

Skip capture_exception for warnings originating from Sentry SDK
background threads (identified by the "sentry-sdk." thread name
prefix). Warnings are still logged normally via _LOGGER.warning.

A dedicated test validates that the SDK's BackgroundWorker thread uses
the expected naming convention, so any future SDK change will be caught.

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-07 17:20:06 +02:00

.devcontainer

Adapt devcontainer.json for systemd-based devcontainer image (#6693 )

2026-04-02 14:40:54 +02:00

.github

Fix version/requirements parsing in setup.py, set version in Dockerfile (#6692 )

2026-04-01 16:01:46 +02: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

Prevent Sentry event feedback loop from warning handler (#6700 )

2026-04-07 17:20:06 +02:00

tests

Prevent Sentry event feedback loop from warning handler (#6700 )

2026-04-07 17:20:06 +02:00

wheels

Use unpublished local wheels during PR builds (#6374 )

2025-12-02 14:08:07 +01:00

.dockerignore

Use unpublished local wheels during PR builds (#6374 )

2025-12-02 14:08:07 +01:00

.gitignore

Use unpublished local wheels during PR builds (#6374 )

2025-12-02 14:08:07 +01: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

CLAUDE.md

Add GitHub Copilot/Claude instruction (#5986 )

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

codecov.yaml

Improve codecov settings for more sensible defaults (#6676 )

2026-03-30 13:24:22 +02:00

Dockerfile

Fix version/requirements parsing in setup.py, set version in Dockerfile (#6692 )

2026-04-01 16:01:46 +02:00

LICENSE

Update LICENSE

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

MANIFEST.in

Add Audio layer / PulseAudio (#1523 )

2020-02-25 18:37:06 +01:00

pyproject.toml

Use Python 3.14(.3) in CI and base image (#6586 )

2026-03-05 21:11:25 +01:00

README.md

Add OHF logo to README (#5316 )

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

requirements_tests.txt

Bump ruff from 0.15.8 to 0.15.9 (#6701 )

2026-04-03 10:17:15 +02:00

requirements.txt

Bump dbus-fast from 4.0.0 to 4.0.4 (#6697 )

2026-04-02 10:27:47 +02:00

setup.py

Fix version/requirements parsing in setup.py, set version in Dockerfile (#6692 )

2026-04-01 16:01:46 +02: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.