Geoff Bourne
Geoff Bourne
Looking at the code I can confirm that would be missing. FYI Ctrl-D will end the interactive session, but I know that's the most intuitive exit operation.
Regarding questions: ### Version Response It would be ideal to ping the backend once at startup and retain its version/protocol; however, in the spirit of incremental PRs I'm fine with...
> It seems that `waker` is non-nil even with auto scale up disabled. > Do you think pass the global autoScaleUp config value as a field in `Connector` struct is...
> I'm pretty new to golang. Sorry if the code is a bit messy. I think that my `time.Sleep(backendRetryInterval)` isn't something to do as it block the whole main thread?...
Sorry for the delay getting back to your PR. I'm focusing on #405 and then after that's merged can shift to yours.
Previous PR is now merged, so now I can focus on yours after you get merge conflicts caught up.
Thanks @alexfrs69 @Sammcb since you've been in some this code recently I was wondering if you could help look at this PR also?
@alexfrs69 just noticed the PR is still in draft. Want to mark it ready for review?
> If a client repeatedly refreshes the server status page, each status request is handled sequentially, causing a backlog and significant response delays. This could potentially lead to a DoS...
Perhaps we need to scale back the features and behavior to simply what @L-Wehmschulte said > showed a nice motd and kept the user hanging I had forgotten a lot...