38050fa460
# Description Since the `TaskExecutor` currently requires a `Weak<Runtime>`, it's impossible to use it in an async test where the `Runtime` is created outside our scope. Whilst we *could* create a new `Runtime` instance inside the async test, dropping that `Runtime` would cause a panic (you can't drop a `Runtime` in an async context). To address this issue, this PR creates the `enum Handle`, which supports either: - A `Weak<Runtime>` (for use in our production code) - A `Handle` to a runtime (for use in testing) In theory, there should be no change to the behaviour of our production code (beyond some slightly different descriptions in HTTP 500 errors), or even our tests. If there is no change, you might ask *"why bother?"*. There are two PRs (#3070 and #3175) that are waiting on these fixes to introduce some new tests. Since we've added the EL to the `BeaconChain` (for the merge), we are now doing more async stuff in tests. I've also added a `RuntimeExecutor` to the `BeaconChainTestHarness`. Whilst that's not immediately useful, it will become useful in the near future with all the new async testing.
15 lines
384 B
TOML
15 lines
384 B
TOML
[package]
|
|
name = "task_executor"
|
|
version = "0.1.0"
|
|
authors = ["Sigma Prime <contact@sigmaprime.io>"]
|
|
edition = "2021"
|
|
|
|
[dependencies]
|
|
tokio = { version = "1.14.0", features = ["rt-multi-thread"] }
|
|
slog = "2.5.2"
|
|
futures = "0.3.7"
|
|
exit-future = "0.2.0"
|
|
lazy_static = "1.4.0"
|
|
lighthouse_metrics = { path = "../lighthouse_metrics" }
|
|
sloggers = { version = "2.1.1", features = ["json"] }
|