You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Reliable way to tell whether server is running #1001
which makes it difficult to time when the server is actually started (think tests).
One way to fix this is to print that message (and possibly also "Running swagger Docs at ..."), or something else, between httpuv::startServer and httpuv::servicehere, by using those directly instead of relying on the httpuv::runServer abstraction.
I believe the messages could be printed in a later::later(function() { message("SERVER STARTED") }, delay = 0). This would delay the message until the R process releases control back to {later} processing loop.
Activity
ElianHugh commentedon Jan 18, 2026
FWIW, a workaround is to have a dummy endpoint and ping it using httr2/whatever and return FALSE on error
I use this pattern in my autoreloader to check if the api is up
https://github.com/ElianHugh/hotwater/blob/main/R/middleware.R#L85-L105
schloerke commentedon Jan 20, 2026
I believe the messages could be printed in a
later::later(function() { message("SERVER STARTED") }, delay = 0). This would delay the message until the R process releases control back to{later}processing loop.