Retry setup after transient source fetch failures#6983
Open
PrzemyslawKlys wants to merge 1 commit into
Open
Conversation
This was referenced Jul 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses #6981.
Summary
SourceShell.fetch()report success without discarding cached entries or refresh time on failureunknownThis targets the stable
masterbranch and is intentionally independent of the v3 source architecture.Validation
python -m pytest -q— 38 passedCI dependency
The current base workflow installs unsupported Home Assistant 2023.7.3 under Python 3.10, so its validation job fails while importing
DeviceInfobefore these tests can run. #6987 aligns the base validation environment with the advertised Home Assistant 2023.12 minimum.