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
I need to run a Tide server in tests. Each test starts a server, performs some checks, and stops the server. How can one shut down a running Tide server?
The easiest thing is to drop the executor. Tide uses async-std which uses async_global_executor. I couldn't figure out how to drop the global executor.
Meta comment: Tide's framework style makes it cumbersome to do anything that is not built-in. I wish Tide was modular. For example, I want to do my own routing. But it would be helpful to have a stand-alone way to parse urls into variables. I also need handlers to return a custom error type. The top level handler must perform logging and translate errors into appropriate responses. All of this is hard to do with Tide. Tide's mono-lithic design also makes debugging extremely difficult. I really need an async version of rouille.
The text was updated successfully, but these errors were encountered:
I need to run a Tide server in tests. Each test starts a server, performs some checks, and stops the server. How can one shut down a running Tide server?
The easiest thing is to drop the executor. Tide uses
async-std
which usesasync_global_executor
. I couldn't figure out how to drop the global executor.This is not a request for graceful shutdown #528.
Meta comment: Tide's framework style makes it cumbersome to do anything that is not built-in. I wish Tide was modular. For example, I want to do my own routing. But it would be helpful to have a stand-alone way to parse urls into variables. I also need handlers to return a custom error type. The top level handler must perform logging and translate errors into appropriate responses. All of this is hard to do with Tide. Tide's mono-lithic design also makes debugging extremely difficult. I really need an async version of rouille.
The text was updated successfully, but these errors were encountered: