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
Describe the bug
If the API Server errors (e.g. returning an err on demand in apiServer.Start() on demand) when running daytona serve, the serve process doesn't exit for ~30 seconds until the "waiting" for API server to start function finishes.
Expected behavior
The "waiting" for API server function before printing the "You may start developing with Daytona" box should be run asynchronously, allowing the select call that listens to error channels the correctly detect any errors
The text was updated successfully, but these errors were encountered:
Describe the bug
If the API Server errors (e.g. returning an err on demand in apiServer.
Start()
on demand) when runningdaytona serve
, the serve process doesn't exit for ~30 seconds until the "waiting" for API server to start function finishes.Expected behavior
The "waiting" for API server function before printing the "You may start developing with Daytona" box should be run asynchronously, allowing the
select
call that listens to error channels the correctly detect any errorsThe text was updated successfully, but these errors were encountered: