Stajo
March 9, 2023, 5:12am
1
Did anyone else experienced upgrade fail to latest core? My upgrade procedure was just spinning like 20 minutes or so, until I restarted my rpi4. After restart it is not upgraded.
No, but you may want to hold off until the next patch, as there is a bug in this one for Supervised/HAOS users.
1 Like
myle
March 9, 2023, 5:31am
4
hay bro
the fix was put in 2023.03.1
please read again
tom_l
March 9, 2023, 5:36am
5
Not sure that is what they were referring to.
"Failed to get add-on documentation, Unknown error, see supervisor logs" - #7 by benchr is the specific thing I’m talking about. I don’t know if anyone has reported it on GitHub, though.
1 Like
tom_l
March 9, 2023, 6:00am
8
Looks like a fix for that has been merged for the next version,
home-assistant:dev ← home-assistant:addon-docs-changelog
opened 11:09PM - 08 Mar 23 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Add paths to the changelog and documentation APIs
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [x] 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
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [ ] The code has been formatted using Black (`black --fast homeassistant tests`)
- [x] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] 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 link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
Stajo
March 9, 2023, 7:22am
9
Thanks. Ill hold my horses and wait for the next one. Not wise to be so triggerhappy, especially when running pi unobtanium
1 Like
I did read that the same way
My update also failed initially but retried a couple of times and it was ok.
1 Like
Stajo
March 10, 2023, 5:17am
12
3.3 came up for grabs now, and it chewed through alright:)
Oughton
September 1, 2023, 5:41pm
13
Jumping in on this now, I’m having this same issue.
I’m running Generic X86-64 on a 6th Gen i5 with 8gb ram and a 250gb ssd (HP ProDesk 400 G2 Mini)
I’ve had no time for maintenance as a new father and I would really appreciate if anyone has any tips!
