decky-loader icon indicating copy to clipboard operation
decky-loader copied to clipboard

[BUG] Already installed plugins fail to load if GitHub is experiencing issues

Open milroneth opened this issue 6 months ago • 1 comments

Please confirm

  • [X] I have searched existing issues
  • [X] This issue is not a duplicate of an existing one
  • [X] I have checked the common issues section in the readme file
  • [ ] I have attached logs to this bug report (failure to include logs will mean your issue may not be responded to).

Bug Report Description

This one is weird, I promise. Also, I have no logs unfortunately and cannot currently reproduce, so not 100% confident.

During today's GitHub outage I was doing testing for #683, restarting the Decky loader service multiple times. I was on v3.0.0-pre10 on Steam Beta.

I did not notice the GitHub issues until I tried changing Decky channel to some testing version or even stable just to trigger a Decky reload, when it was unable to find any version at all. Since my network was ok, I thought it peculiar, but I just restarted my Deck completely to clean up the environment. I was still unaware of GitHub being down.

Upon boot, Decky failed to load multiple of my plugins, which made me believe I had broken something, tried "updating" to stable again, nothing would load, restarted again, same issue. I booted to the Desktop once in the mid of this and unless I'm confused, when I opened big picture the plugins did load ok! Could this be because they get loaded later? I then rebooted, only for them to fail again.

20240815024905_1

At that point I noticed the GitHub issues, imagined it might be relevant, rebooted with WiFi off and everything was ok, rebooted again with WiFi on and plugins broke again. And at my next reboot GitHub was semi-fine again and couldn't have this happen again, plugins worked normally.

I tried sending github.com, githubusercontent.com, and raw.githubusercontent.com to 1.1.1.1 through my local DNS, but since that only resulted in certificate errors, it wouldn't trigger the problem either, we need GitHub to be half-broken for this (give an actual answer, that just is not what was expected.)

I will repeat, I might be off here since this is all unverifiable. But unless that "Failed to fetch" error means something specific that points to another direction, I'm pretty sure I got this right. Or it's late and I've done more testing than I could handle...

Expected Behaviour

Decky Loader shouldn't be unable to properly load plugins because of GitHub issues?

SteamOS version

SteamOS Beta 3.6

Selected Update Channel

Prerelease

Have you modified the read-only filesystem at any point?

No

Backend Logs

--

Frontend Logs

--

milroneth avatar Aug 15 '24 02:08 milroneth