Been waiting for this forever.

What would be the suitable place to place retry button?

• at the top beside Update available
• at the bottom after release notes ( where apply update button appears when successful )

My suggestion would be to place it beside update available.
@jandubois , @mook-as need your inputs before I start implementing

Personally, I'd be inclined to put it next to update available. But if you put it there, the button shouldn't be labeled "Retry", just "Check for updates"

But, arguably any place would be fine. Technically, it's logically more appropriate to put it after "There was an error checking for updates."

Given that there's already a flow with a button below:

It's probably best to put the button below.

I don't understand the discussion. Why would you need a retry button if you already have the update available?

I thought you just wanted a way to force Rancher Desktop to check for updates right away instead of waiting for up to an hour when it would check again automatically. So the button would only be displayed when there are no release notes.

I think the best placement would be to move the "Check for updates automatically" checkbox to the left to make enough space behind it for a "Check now" button:

I thought you just wanted a way to force Rancher Desktop to check for updates right away instead of waiting for up to an hour when it would check again automatically.

Rereading the top of the thread I see now that you had an error situation where the release notes have been fetched, but the update data download has failed. I don't believe this is a common scenario. Did this happen more than once (personally I have never seen it).

I'm pretty sure we saw it recently on a coworker's laptop...

Did this happen more than once
It happened with me once

but I agree with your suggestion @jandubois ,
We can have check for update button which can also do retry when something fails.

When there is no failure

When there is failure

Retry Update isn't really correct, that would imply that updating failed and that the button would attempt to update again. This is really Recheck for available updates or something...

@jsoref renamed it

@jandubois I had a doubt, commented on the MR itself, could you clarify me please :)

I don't think we need different text for failed update checks. It just makes the code more complex for no real benefit. It is also hard to test if that code actually works.

I think the button should just say "Check Now". "[X] Check for updates automatically (Check for Updates)" is less clear than "Check Now" in my opinion.

Something like this (from a different app):

@jandubois yup, seems better changed the MR.

Could you help me with this (validating) - #8189 (comment)

Yes, Check Now is great.