-
-
Notifications
You must be signed in to change notification settings - Fork 349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There are no exceptions with run_async() #885
Comments
It fails in the constructor of the server due to asio::ip::address::from_string and throws an exception, therefore never a notification will be sent in run() and wait_for_server_start() waits forever. |
In general I think a overload for Is there a way to achieve something with the current crow implementation? |
I agree, a timeout would be generally useful. I would assume that it is easily possible. |
Somehow config errors are suppressed if the the server runs in async mode.
For example if i'm using a invalid
.bindaddr("127.0.0")
. If used with.run()
i get a exception(maybe not the greatest exception but good enough)
If i do the same with
.run_async()
it just hangs onwait_for_server_start()
with out any exceptions.Is that on purpose?
Is there a way to wait or crash or maybe find out if the server crashed?
Am i holding it wrong? 😅
Full example:
The text was updated successfully, but these errors were encountered: