espresso-sequencer
espresso-sequencer copied to clipboard
Closes #845 ### This PR: Avoids developers running into compilation errors due to RUSTFLAGS. The RUSTFLAGS in `.cargo/config.toml` will be used for all rustc invocations unless the RUSTFLAGS env var...
I think running `cargo check` is enough here. ``` env RUSTFLAGS='--cfg async_executor_impl="tokio" --cfg async_channel_impl="tokio"' cargo check ``` Not a high priority now because we'll make it less easy to mess...
This is super useful for debugging and not easy to get once the node is running Edit: Any sensitive values such as private keys should be hidden.
See [batch submit](https://github.com/EspressoSystems/hotshot-builder-core/issues/114) and [no write locking](https://github.com/EspressoSystems/hotshot-builder-core/issues/115)
Bumps [crate-ci/typos](https://github.com/crate-ci/typos) from 1.19.0 to 1.21.0. Release notes Sourced from crate-ci/typos's releases. v1.21.0 [1.21.0] - 2024-04-30 Fixes Updated the dictionary with the April 2024 changes v1.20.10 [1.20.10] - 2024-04-23 Fixes...
We currently mix the two which may make things harder to read than necessary. Example (the type signature of `metadata`) https://github.com/EspressoSystems/espresso-sequencer/blob/2e98bccaceef0334d7ed5253142d8d9c26817263/sequencer/src/header.rs#L246-L259
DO NOT MERGE/REVIEW. IT IS JUST FOR TESTING.
Scan all `ESPRESSO_SEQUENCER_*` variables in environment, warn about ones that aren't recognizede
It's annoying for debugging and it feels like it shouldn't take that long to start our dev chain, since it starts mining blocks a lot earlier than that.
https://github.com/EspressoSystems/espresso-sequencer/pull/1307#discussion_r1568678160