Working Further #140
Annotations
6 errors and 10 warnings
`std::sync::Arc<operations::v2::IterativeDataset>` is not a future:
azure-kusto-data/src/client.rs#L359
error[E0277]: `std::sync::Arc<operations::v2::IterativeDataset>` is not a future
--> azure-kusto-data/src/client.rs:359:10
|
354 | Ok(IterativeDataset::from_async_buf_read(
| ____________-
355 | | body.into_stream()
356 | | .map_err(|e| std::io::Error::other(e))
357 | | .into_async_read(),
358 | | )
| |_________- this call returns `std::sync::Arc<operations::v2::IterativeDataset>`
359 | .await)
| -^^^^^
| ||
| |`std::sync::Arc<operations::v2::IterativeDataset>` is not a future
| help: remove the `.await`
|
= help: the trait `futures::Future` is not implemented for `std::sync::Arc<operations::v2::IterativeDataset>`
= note: std::sync::Arc<operations::v2::IterativeDataset> must be a future or must implement `IntoFuture` to be awaited
= note: required for `std::sync::Arc<operations::v2::IterativeDataset>` to implement `std::future::IntoFuture`
|
no method named `clone` found for enum `error::Error` in the current scope:
azure-kusto-data/src/operations/v2.rs#L303
error[E0599]: no method named `clone` found for enum `error::Error` in the current scope
--> azure-kusto-data/src/operations/v2.rs:303:54
|
303 | [e] => Partial::Err((Some(dataset), (*e).clone())),
| ^^^^^ method not found in `Error`
|
::: azure-kusto-data/src/error.rs:10:1
|
10 | pub enum Error {
| -------------- method `clone` not found for this enum
|
= help: items from traits can only be used if the trait is implemented and in scope
= note: the following trait defines an item `clone`, perhaps you need to implement it:
candidate #1: `std::clone::Clone`
|
the trait bound `error::ParseError: derive_more::From<url::parser::ParseError>` is not satisfied:
azure-kusto-data/src/client.rs#L375
error[E0277]: the trait bound `error::ParseError: derive_more::From<url::parser::ParseError>` is not satisfied
--> azure-kusto-data/src/client.rs:375:60
|
375 | let mut request = Request::new(url.parse().map_err(ParseError::from)?, Method::Post);
| ^^^^^^^^^^ the trait `derive_more::From<url::parser::ParseError>` is not implemented for `error::ParseError`
|
= help: the following other types implement trait `derive_more::From<T>`:
<error::ParseError as derive_more::From<serde_json::Error>>
<error::ParseError as derive_more::From<uuid::Error>>
<error::ParseError as derive_more::From<rust_decimal::Error>>
<error::ParseError as derive_more::From<time::error::Parse>>
<error::ParseError as derive_more::From<std::num::ParseFloatError>>
<error::ParseError as derive_more::From<std::num::ParseIntError>>
<error::ParseError as derive_more::From<std::str::ParseBoolError>>
<error::ParseError as derive_more::From<{type error}>>
|
the trait bound `error::ParseError: derive_more::From<url::parser::ParseError>` is not satisfied:
azure-kusto-data/src/client.rs#L375
error[E0277]: the trait bound `error::ParseError: derive_more::From<url::parser::ParseError>` is not satisfied
--> azure-kusto-data/src/client.rs:375:40
|
375 | let mut request = Request::new(url.parse().map_err(ParseError::from)?, Method::Post);
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `derive_more::From<url::parser::ParseError>` is not implemented for `error::ParseError`
|
= help: the following other types implement trait `derive_more::From<T>`:
<error::ParseError as derive_more::From<serde_json::Error>>
<error::ParseError as derive_more::From<uuid::Error>>
<error::ParseError as derive_more::From<rust_decimal::Error>>
<error::ParseError as derive_more::From<time::error::Parse>>
<error::ParseError as derive_more::From<std::num::ParseFloatError>>
<error::ParseError as derive_more::From<std::num::ParseIntError>>
<error::ParseError as derive_more::From<std::str::ParseBoolError>>
<error::ParseError as derive_more::From<{type error}>>
|
unresolved import `oauth2`:
azure-kusto-data/src/error.rs#L3
error[E0432]: unresolved import `oauth2`
--> azure-kusto-data/src/error.rs:3:5
|
3 | use oauth2::url;
| ^^^^^^ use of undeclared crate or module `oauth2`
|
build-data
Clippy had exited with the 101 exit code
|
unused import: `crate::request_options::Options`:
azure-kusto-data/src/client.rs#L18
warning: unused import: `crate::request_options::Options`
--> azure-kusto-data/src/client.rs:18:5
|
18 | use crate::request_options::Options;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
unused import: `crate::operations`:
azure-kusto-data/src/client.rs#L14
warning: unused import: `crate::operations`
--> azure-kusto-data/src/client.rs:14:5
|
14 | use crate::operations;
| ^^^^^^^^^^^^^^^^^
|
unused import: `Response`:
azure-kusto-data/src/client.rs#L9
warning: unused import: `Response`
--> azure-kusto-data/src/client.rs:9:71
|
9 | ClientOptions, Context, CustomHeaders, Method, Pipeline, Request, Response, ResponseBody,
| ^^^^^^^^
|
= note: `#[warn(unused_imports)]` on by default
|
build-data
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/clippy-check@v1, codecov/codecov-action@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
build-data
At least one of the FILES, JUNIT_FILES, NUNIT_FILES, XUNIT_FILES, or TRX_FILES options has to be set! Falling back to deprecated default "*.xml"
|
build-data
Could not find any files for *.xml
|
build-data
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-data
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-data
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-data
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|