EspHttpServer.handle_get methods not found at EspHttpServer struct when i test http server demo.

build error:

   Compiling http-server v0.1.0 (/home/iric/code/learn/espressif-trainings/intro/http-server)
error: could not compile `http-server` due to 3 previous errors; 2 warnings emitted
warning: unused imports: `io::Write`, `registry::Registry`
  --> examples/http_server.rs:10:20
   |
10 |     http::server::{registry::Registry, Response},
   |                    ^^^^^^^^^^^^^^^^^^
11 |     io::Write,
   |     ^^^^^^^^^
   |
   = note: `#[warn(unused_imports)]` on by default

error[E0599]: no method named `handle_get` found for struct `EspHttpServer` in the current scope
  --> examples/http_server.rs:31:12
   |
31 |     server.handle_get("/", |_request, response| {
   |            ^^^^^^^^^^ method not found in `EspHttpServer`

error[E0599]: no method named `handle_get` found for struct `EspHttpServer` in the current scope
  --> examples/http_server.rs:41:12
   |
41 |     server.handle_get("/temperature", move |_request, response| {
   |            ^^^^^^^^^^ method not found in `EspHttpServer`

warning: unused import: `Response`
  --> examples/http_server.rs:10:40
   |
10 |     http::server::{registry::Registry, Response},
   |                                        ^^^^^^^^

error: aborting due to 2 previous errors; 2 warnings emitted

PS D:\intro\http-client> cp .\examples\https_client.rs .\src\main.rs       
PS D:\intro\http-client> cargo espflash --release --monitor COM5    
New version of cargo-espflash is available: v2.0.0-rc.1

Serial port: COM5
Connecting...

   Compiling http-client v0.1.0 (D:\intro\http-client)
error: could not compile `http-client` due to 2 previous errors 
error[E0425]: cannot find value `esp_crt_bundle_attach` in crate `esp_idf_sys`
  --> src\main.rs:40:46
   |
40 |         crt_bundle_attach: Some(esp_idf_sys::esp_crt_bundle_attach),
   |                                              ^^^^^^^^^^^^^^^^^^^^^ not found in `esp_idf_sys`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0425`.
PS D:\intro\http-client> 

After following the instructions in the book, I tried building the Hello Board project with cargo build --target riscv32imc-esp-espidf. The build then fails with many errors of the following type:

   Compiling embedded-io v0.3.1
error[E0658]: generic associated types are unstable
  --> /home/<user>/.cargo/registry/src/github.com-1ecc6299db9ec823/embedded-io-0.3.1/src/asynch.rs:17:5
   |
17 | /     type ReadFuture<'a>: Future<Output = Result<usize, Self::Error>>
18 | |     where
19 | |         Self: 'a;
   | |_________________^
   |
   = note: see issue #44265 <https://github.com/rust-lang/rust/issues/44265> for more information
   = help: add `#![feature(generic_associated_types)]` to the crate attributes to enable

My rust toolchain is up to date and the specific version requested in the book is available:

$ rustup toolchain list
stable-x86_64-unknown-linux-gnu (default)
nightly-2022-03-10-x86_64-unknown-linux-gnu (override)

• When we only want to build the project --target is not required as its already specified in the config.toml
• If we only want to open a serial monitor without flashing the device again, we can use the serial-monitor subcommand of cargo-espflash
  • It may also be worth adding a note saying that when no serial device is specified in the cargo-espflash command, it will print a list of the available serial devices so the user can choose.
  • espmonitor is not being installed but its mentioned. espmonitor is no longer required.
  • We will be releasing espflash and cargo-espflash v2.0 soon. With this new release, subcommands will change a bit, so it may be worth waiting for the new release and update all the flashing/monitoring commands at once.
  • We noticed many users having errors to flash, most of those errors were because they were using an old version of espflash/cargo-espflash. It may help add a note so users are using a recent version of it, or having a fixed version on the book so we make sure they all install the same version.
  • We could add a custom runner to allow using cargo run to flash and monitor. by adding the following to .cargo/config.toml:

  [target.riscv32imc-esp-espidf]
  runner = "espflash --monitor"
  

  If we add the custom runner we would also need to install espflash

• The esp-idf-template was improved, and the prompts to configure the project are outdated. We now have the following items:

• Project name: hello-world
• DevContainer Support: false
• STD support: true
• MCU: esp32c3
• ESP-IDF version: 4.4

• The Setup section of HTTP Server has a small typo (http_serve should be http_server ): cargo espflash --release --example **http_serve** --monitor $SERIALDEVICE
• It would be good to have some notes about Wokwi, as we now support some of the examples on it:
  • Training exercises:
    • intro/hardware-check
    • intro/http-client*
    • intro/http-server*
    • intro/mqtt*
    • advanced/i2c-sensor-reading
    • advanced/i2c-driver
    • advanced/button-interrupt Projects with * are building fine but not running properly, they need to be reviewed.
  • Other examples
  • GDB Debugging