Skip to content

refactor: migrate web server to Actix Web #412

refactor: migrate web server to Actix Web

refactor: migrate web server to Actix Web #412

Triggered via pull request September 19, 2024 19:31
@robjtederobjtede
synchronize #229
actix-web
Status Failure
Total duration 1m 22s
Artifacts

premerge.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 5 warnings
the method `to_string` exists for reference `&ServerError`, but its trait bounds were not satisfied: src/server/error.rs#L70
error[E0599]: the method `to_string` exists for reference `&ServerError`, but its trait bounds were not satisfied --> src/server/error.rs:70:26 | 11 | pub(crate) enum ServerError { | --------------------------- doesn't satisfy `server::error::ServerError: derive_more::Display` or `server::error::ServerError: std::string::ToString` ... 70 | self.to_string(), | ^^^^^^^^^ method cannot be called on `&ServerError` due to unsatisfied trait bounds | = note: the following trait bounds were not satisfied: `server::error::ServerError: derive_more::Display` which is required by `server::error::ServerError: std::string::ToString` `&server::error::ServerError: derive_more::Display` which is required by `&server::error::ServerError: std::string::ToString` note: the trait `derive_more::Display` must be implemented --> /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/fmt/mod.rs:728:1 = help: items from traits can only be used if the trait is implemented and in scope = note: the following trait defines an item `to_string`, perhaps you need to implement it: candidate #1: `std::string::ToString`
the method `to_string` exists for reference `&ServerError`, but its trait bounds were not satisfied: src/server/error.rs#L62
error[E0599]: the method `to_string` exists for reference `&ServerError`, but its trait bounds were not satisfied --> src/server/error.rs:62:26 | 11 | pub(crate) enum ServerError { | --------------------------- doesn't satisfy `server::error::ServerError: derive_more::Display` or `server::error::ServerError: std::string::ToString` ... 62 | self.to_string(), | ^^^^^^^^^ method cannot be called on `&ServerError` due to unsatisfied trait bounds | = note: the following trait bounds were not satisfied: `server::error::ServerError: derive_more::Display` which is required by `server::error::ServerError: std::string::ToString` `&server::error::ServerError: derive_more::Display` which is required by `&server::error::ServerError: std::string::ToString` note: the trait `derive_more::Display` must be implemented --> /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/fmt/mod.rs:728:1 = help: items from traits can only be used if the trait is implemented and in scope = note: the following trait defines an item `to_string`, perhaps you need to implement it: candidate #1: `std::string::ToString`
the method `to_string` exists for reference `&ServerError`, but its trait bounds were not satisfied: src/server/error.rs#L54
error[E0599]: the method `to_string` exists for reference `&ServerError`, but its trait bounds were not satisfied --> src/server/error.rs:54:26 | 11 | pub(crate) enum ServerError { | --------------------------- doesn't satisfy `server::error::ServerError: derive_more::Display` or `server::error::ServerError: std::string::ToString` ... 54 | self.to_string(), | ^^^^^^^^^ method cannot be called on `&ServerError` due to unsatisfied trait bounds | = note: the following trait bounds were not satisfied: `server::error::ServerError: derive_more::Display` which is required by `server::error::ServerError: std::string::ToString` `&server::error::ServerError: derive_more::Display` which is required by `&server::error::ServerError: std::string::ToString` note: the trait `derive_more::Display` must be implemented --> /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/fmt/mod.rs:728:1 = help: items from traits can only be used if the trait is implemented and in scope = note: the following trait defines an item `to_string`, perhaps you need to implement it: candidate #1: `std::string::ToString`
the method `to_string` exists for reference `&ServerError`, but its trait bounds were not satisfied: src/server/error.rs#L48
error[E0599]: the method `to_string` exists for reference `&ServerError`, but its trait bounds were not satisfied --> src/server/error.rs:48:69 | 11 | pub(crate) enum ServerError { | --------------------------- doesn't satisfy `server::error::ServerError: derive_more::Display` or `server::error::ServerError: std::string::ToString` ... 48 | ServerError::PopularItemsFailed => res.body(render(self.to_string(), "").0), | ^^^^^^^^^ method cannot be called on `&ServerError` due to unsatisfied trait bounds | = note: the following trait bounds were not satisfied: `server::error::ServerError: derive_more::Display` which is required by `server::error::ServerError: std::string::ToString` `&server::error::ServerError: derive_more::Display` which is required by `&server::error::ServerError: std::string::ToString` note: the trait `derive_more::Display` must be implemented --> /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/fmt/mod.rs:728:1 = help: items from traits can only be used if the trait is implemented and in scope = note: the following trait defines an item `to_string`, perhaps you need to implement it: candidate #1: `std::string::ToString`
`server::error::ServerError` doesn't implement `derive_more::Display`: src/server/error.rs#L44
error[E0277]: `server::error::ServerError` doesn't implement `derive_more::Display` --> src/server/error.rs:44:48 | 44 | let mut res = HttpResponse::build(self.status_code()); | ^^^^^^^^^^^ `server::error::ServerError` cannot be formatted with the default formatter | = help: the trait `derive_more::Display` is not implemented for `server::error::ServerError` = note: in format strings you may be able to use `{:?}` (or {:#?} for pretty-print) instead note: required by a bound in `actix_web::ResponseError::status_code` --> /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/actix-web-4.9.0/src/error/response_error.rs:26:39 | 26 | pub trait ResponseError: fmt::Debug + fmt::Display { | ^^^^^^^^^^^^ required by this bound in `ResponseError::status_code` ... 31 | fn status_code(&self) -> StatusCode { | ----------- required by a bound in this associated function
`server::error::ServerError` doesn't implement `derive_more::Display`: src/server/error.rs#L31
error[E0277]: `server::error::ServerError` doesn't implement `derive_more::Display` --> src/server/error.rs:31:24 | 31 | impl ResponseError for ServerError { | ^^^^^^^^^^^ `server::error::ServerError` cannot be formatted with the default formatter | = help: the trait `derive_more::Display` is not implemented for `server::error::ServerError` = note: in format strings you may be able to use `{:?}` (or {:#?} for pretty-print) instead note: required by a bound in `actix_web::ResponseError` --> /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/actix-web-4.9.0/src/error/response_error.rs:26:39 | 26 | pub trait ResponseError: fmt::Debug + fmt::Display { | ^^^^^^^^^^^^ required by this bound in `ResponseError`
linting
Clippy had exited with the 101 exit code
build-and-test
Process completed with exit code 101.
linting
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
linting
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
linting
Unexpected input(s) 'clippy', valid inputs are ['toolchain', 'target', 'components', 'cache']
linting
Unexpected input(s) 'clippy', valid inputs are ['toolchain', 'target', 'components', 'cache']
build-and-test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/