Proposed change

Leaving an app's log page, or reloading it, makes the frontend abort its logs/follow stream. The handler in HassIOView gets cancelled, but the response from the Supervisor never gets released, so its connection stays in use until Core restarts.

Most of the time that's fine, since aiohttp releases the connection by itself once the body has been fully read. A follow stream never finishes though, and NO_TIMEOUT gives it no total timeout. So each visit to a log page leaks a connection, and after 100 of them every Supervisor call times out: the apps page won't load and ingress panels just hang.

The fix opens the request with async with, so the response is released when the handler exits, including when it's cancelled. The test helper's mock response now releases on exit too, like aiohttp's.

I added a test that cancels the stream partway through and checks the response gets released. It fails on dev without this change.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue: Add Hassio HTTP logs/follow to allowed paths #126606
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies a diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.