Open ButteredCats opened 1 month ago
This kinda just stopped happening after a little while and everything is back to normal. Not sure what's up with that.
Hm. I'm hoping it was a regular old site-wide outage. I'll look into it further and see if it happens again - if it does, please send a message here!
Describe the bug
As of about 3:20pm EDT today my Redlib containers have stopped functioning, with the dreaded rate limit exceeded error coming back.
Building a debug version of Redlib on my desktop and giving it whirl sits at
Starting Redlib...
for a couple of minutes and eventually producesthread 'tokio-runtime-worker' panicked at src/oauth.rs:110:44
and then goes forward withRunning Redlib v0.35.1 on [::]:8080!
. From there Redlib is accessible.However, on my public instance it quickly runs into the rate limit exceeded errors after Redlib starts.
Steps to reproduce the bug
Run Redlib and watch it's output, on a public instance observe it get ratelimited shortly after
Running Redlib v0.35.1 on [::]:8080!
is printed.What's the expected behavior?
Redlib doesn't take multiple minutes to start and properly rotates the oauth token when it gets ratelimited.
Additional context / screenshot
Console output with
RUST_BACKTRACE=1
: