WebSocket Example on homepage no longer working

[xiaoas]

Describe the bug
I recently updated salvo from 1.16 to 1.29. Sadly my webSocket server would no longer compile.
So I went grab the example at the bottom of salvo homepage, that one ain't compiling as well.

Cargo.toml:

[package]
name = "noname-server"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
salvo = { version = "0.*", features = ["full"] }
tokio = { version = "1", features = ["full"] }
tokio-stream = "*"
futures = "*"
futures-util = "0.3"
once_cell = "1"
tracing = "0.1"
tracing-subscriber = "0.2.0"
serde = { version = "1.0", features = ["derive"] }
serde_json = "1"
rand = "0.8"
thiserror = "1"

Error:

error[E0412]: cannot find type `HttpError` in this scope
 --> src/main.rs:6:71
  |
6 | async fn connect(req: &mut Request, res: &mut Response) -> Result<(), HttpError> {
  |                                                                       ^^^^^^^^^ not found in this scope

error[E0698]: type inside `async` block must be known in this context
 --> src/main.rs:5:1
  |
5 | #[handler]
  | ^^^^^^^^^^ cannot infer type
  |
note: the type is part of the `async` block because of this `await`
 --> src/main.rs:5:1
  |
5 | #[handler]
  | ^^^^^^^^^^
  = note: this error originates in the attribute macro `handler` (in Nightly builds, run with -Z macro-backtrace for more info)

Some errors have detailed explanations: E0412, E0698.
For more information about an error, try `rustc --explain E0412`.
error: could not compile `noname-server` due to 2 previous errors

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
The example should compile(hopefully).

Screenshots

Desktop (please complete the following information):

• OS: macos
• Version 0.29.1

[xiaoas]

I tried https://github.com/salvo-rs/salvo/blob/main/examples/ws/src/main.rs

That one is working.🥲

[chrislearn]

You use salvo = { version = "0.*", features = ["full"] } here, can you confirm is latest salvo version is used? Please check your Cargo.lock

[chrislearn]

Try change HttpError to StatusError.

[xiaoas]

You use salvo = { version = "0.*", features = ["full"] } here, can you confirm is latest salvo version is used? Please check your Cargo.lock

Yes I'm using the latest version of salvo.

Changing HttpError to StatusError fixes the issue.