Tomás Grüner
Tomás Grüner
This is a continuation of PR https://github.com/proger/eflame/pull/15, that was Fixes https://github.com/proger/eflame/issues/13 The change added is moving the `Mode` and `OutputFile` parameters to `Options`. Note this is a **breaking change**.
It's taking too long to run, and it should be easy to partition into multiple jobs that run in parallel.
This includes reacting to flags inside the `Formatter` struct received by `Display` and `Debug`, and also implementing other formatting traits like [`LowerHex`](https://doc.rust-lang.org/std/fmt/trait.LowerHex.html).
PR #367 adds some shaders used for tests only. These should be included only when compiling for tests. We could solve this by splitting the shaders into two: release and...
We could maybe use a trait or enum to replace `IsFFTField::field_name`. The idea is to prioritize running on GPU, defaulting to CPU execution if it's not possible.
Context: #1013 ERC-2335 keystores have a `path` field with a [EIP-2333](https://eips.ethereum.org/EIPS/eip-2333) path for deriving the secret. We should support non-empty values of that field.
We have a race condition. If this measurement is called before `Db` is started, the measurement fails with the message: ``` Error when calling MFA defined by measurement: 'Elixir.LambdaEthereumConsensus.Telemetry' db_size...
It might have some useful tests. See https://github.com/ethpandaops/assertoor-github-action and https://github.com/ethpandaops/assertoor
We should fetch a block from each one, and then compare them, failing if they aren't equal.