frontend icon indicating copy to clipboard operation
frontend copied to clipboard

No loading indicator for backups

Open uberchris2 opened this issue 2 years ago • 5 comments

Checklist

  • [X] I have updated to the latest available Home Assistant version.
  • [X] I have cleared the cache of my browser.
  • [X] I have tried a different browser to see if it is related to my browser.
  • [X] I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

My backups are stored in a network location with high latency (several seconds). When I access the Backups settings page, I am shown the (incorrect) message "You don't have any backups yet" until the backups list loads. There is no indication that HA is loading the list of backups.

Describe the behavior you expected

I would expect to see a loading spinner or message until HA has decided if there are actually backups to show.

Steps to reproduce the issue

  1. Configure HA to use a NAS as the primary backup storage
  2. Open Backups settings page (Settings > System > Backups)
  3. Observe the message "Yon don't have any backups yet." for several seconds, until the list of backups populates.

What version of Home Assistant Core has the issue?

core-2024.3.3

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

No response

Which operating system are you using to run this browser?

No response

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

uberchris2 avatar Apr 02 '24 17:04 uberchris2

i'm having the same issue, no backups appear, but backups work

ma10as123 avatar Apr 21 '24 13:04 ma10as123

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Jul 20 '24 13:07 github-actions[bot]

This issue still persists on the latest version.

On Jul 20, 2024, at 6:02 AM, github-actions[bot] @.***> wrote:



There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/frontend/issues/20334#issuecomment-2241146081, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEC3ROU7ATA4X6INZLTADPDZNJNWNAVCNFSM6AAAAABFT3BJZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBRGE2DMMBYGE. You are receiving this because you authored the thread.Message ID: @.***>

uberchris2 avatar Jul 20 '24 13:07 uberchris2