mirror of
https://github.com/facebook/sapling.git
synced 2024-10-11 01:07:15 +03:00
83cd9eec54
Summary: Well, we don't have a Tokio Compat runtime in Actix. This means Tokio 0.2 code (e.g. Tokio 0.2 timers) blows up when executed in the API Server. How do we fix this? By not running Mononoke code on Actix's runtime, and instead running in on a Mononoke runtime we instantiated. How do we do that? By passing a Tokio Compat Executor all the way down to the place where Actix is about to consume our stream ... and at that point, we spawn the stream on our runtime, and give Actix a dumb receiver that does work when polled on a Tokio 0.1 runtime. This feels like the end of the road for the API Server. Nothing about this is even remotely sane, but it should take us through the API Server's eventual demise and replacement with the Gotham-based EdenAPI Server, which runs on the runtime of our choice (i.e. Tokio 0.2). Reviewed By: farnz Differential Revision: D20222294 fbshipit-source-id: 1646e35fe05b131b030e4962c8a7f68f72995035 |
||
|---|---|---|
| .. | ||
| client/src | ||
| if | ||
| src | ||