fix: chat_server disconnect #692
Triggered via pull request
September 10, 2024 16:36
Arichy
Status
Success
Total duration
3m 25s
Artifacts
–
clippy-fmt.yml
on: pull_request
rustfmt check
27s
clippy check
3m 15s
Annotations
1 error and 1 warning
|
clippy check:
websockets/chat-actorless/src/handler.rs#L119
[clippy] reported by reviewdog 🐶
error[E0277]: `()` is not a future
--> websockets/chat-actorless/src/handler.rs:119:37
|
119 | chat_server.disconnect(conn_id).await;
| -^^^^^
| ||
| |`()` is not a future
| help: remove the `.await`
|
= help: the trait `futures_util::Future` is not implemented for `()`, which is required by `(): std::future::IntoFuture`
= note: () must be a future or must implement `IntoFuture` to be awaited
= note: required for `()` to implement `std::future::IntoFuture`
Raw Output:
websockets/chat-actorless/src/handler.rs:119:37:e:error[E0277]: `()` is not a future
--> websockets/chat-actorless/src/handler.rs:119:37
|
119 | chat_server.disconnect(conn_id).await;
| -^^^^^
| ||
| |`()` is not a future
| help: remove the `.await`
|
= help: the trait `futures_util::Future` is not implemented for `()`, which is required by `(): std::future::IntoFuture`
= note: () must be a future or must implement `IntoFuture` to be awaited
= note: required for `()` to implement `std::future::IntoFuture`
__END__
|
|
clippy check
The following actions use a deprecated Node.js version and will be forced to run on node20: giraffate/clippy-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|