Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check for updates button doesn't check for updates #12324

Open
peppy opened this issue Apr 7, 2021 · 7 comments
Open

Check for updates button doesn't check for updates #12324

peppy opened this issue Apr 7, 2021 · 7 comments
Labels
area:settings priority:2 Moderately important. Relied on by some users or impeding the usability of the game

Comments

@peppy
Copy link
Sponsor Member

peppy commented Apr 7, 2021

Seems to do nothing.

@peppy peppy added priority:0 Showstopper. Critical to the next release. area:settings labels Apr 7, 2021
@frenzibyte
Copy link
Member

Looks to work fine on my end. Both on macOS and Windows with Squirrel, even with removing the automatic update checking at UpdateManager.LoadComplete().

@peppy
Copy link
Sponsor Member Author

peppy commented Apr 12, 2021

I can still reproduce it not checking at my end:

2021-04-13_01-58-50.mp4

Haven't had a chance to look into it further yet.

@peppy peppy self-assigned this Apr 15, 2021
@peppy
Copy link
Sponsor Member Author

peppy commented Apr 15, 2021

I've further tested this on macOS and can't reproduce the issue. It's likely some kind of web request caching logic within Squirrel if anything.

For what it's worth, this came up when i had osu! already running and pushed a new release. Pressing the "Check for updates" button had no effect, but restarting the game found the update immediately.

@peppy peppy added priority:2 Moderately important. Relied on by some users or impeding the usability of the game and removed priority:0 Showstopper. Critical to the next release. labels May 14, 2021
@Joehuu
Copy link
Member

Joehuu commented Oct 8, 2021

Having the same issue on macOS. Not sure if it's the same cause as yours, but upon checking https://api.github.com/repos/ppy/osu/releases/latest, this is returned. Haven't done anything weird, apart from installing old versions to reproduce a unrelated bug.

{"message":"API rate limit exceeded for <IP>. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)","documentation_url":"https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting"}

Seems realistic to get this because of the limit, though (https://docs.github.com/en/rest/overview/resources-in-the-rest-api#rate-limiting):

For unauthenticated requests, the rate limit allows for up to 60 requests per hour. Unauthenticated requests are associated with the originating IP address, and not the user making requests.


After an hour, everything works again. Doing some experiment, I pressed that button 60 times before it stopped working again.

@peppy
Copy link
Sponsor Member Author

peppy commented Oct 8, 2021

That's a different issue altogether, but also one we likely want to address. Were you clicking the button or restarting osu! a lot when this happened?

@Joehuu
Copy link
Member

Joehuu commented Oct 8, 2021

I never pressed the button until I realized there was no update notification at the start when testing older releases, and I don't think I restarted osu! that much.

Only thing I can think of is that other apps I was using at the time were using the api (e.g. some VSCode extension), and I can remember restarting that an abnormal amount of times.

@peppy
Copy link
Sponsor Member Author

peppy commented Oct 8, 2021

Yeah, quite feasible since it's per IP at that point. The eventual plan would be to not rely on github in the first place for these calls, but we could consider creating an access key for the client to bypass the rate limiting.

@peppy peppy removed their assignment Jul 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:settings priority:2 Moderately important. Relied on by some users or impeding the usability of the game
Projects
None yet
Development

No branches or pull requests

3 participants