httpmock VS rust

Static YAML file configuration: This mode allows you to set up a mock server with a static configuration that does not need to change. This approach does not require any test execution or Rust program. Instead, the mock server reads its configuration from YAML mock definition files, which are very similar in structure to the Rust API (see example here).

HTTP mocking libraries allow you to simulate HTTP responses so you can easier test code that depends on third-party APIs. This article shows how you can use httpmock to do this in Rust.

Thad you mean with "async runtime conflicts"? My tests are running agains three different async rutimes (tokio, async_std and actix_rt), seemingly without any problems. I checked that manually and I also see no problems (all green, not conflicts). If you think I am mistaken, please consider reporting it here.

The esp-template issue might be this one: https://github.com/esp-rs/rust/issues/158. Try with --release or updating to 1.68.0 with espup update. I'll take a look at the log as soon as I can, atm Im on the phone and is not that easy to scroll through :(

Sure. Espressif maintains a fork which adds support for their microcontrollers.

I am trying to make a vaccine passport validation for my country using the ESP32 for my micro controller. I have gotten the std rust library to compile using (esp-rs)[https://github.com/esp-rs/rust], but the actual validation library that I use needs openssl which refuses to compile.

Xtensa. They've got a fork of LLVM that supports it that they're working toward getting upstreamed. The community has a fork of rustc that uses it (and a quickstart crate) while we wait for it to get upstreamed.

It only works if you have an Xtensa compiler which takes hours to compile, here: Rust Xtensa (if you don't have it). The network driver is just a function that sets the name of the driver so the Esp32 does something other that blinking.