revert #105
Annotations
3 errors and 1 warning
`match` arms have incompatible types:
src/app/from_string.rs#L420
error[E0308]: `match` arms have incompatible types
--> src/app/from_string.rs:420:37
|
418 | let artifact = match artifact_id {
| ----------------- `match` arms have incompatible types
419 | Some(r) => r,
| - this is found to be of type `std::string::String`
420 | None => self.prompt_string_filled(
| _____________________________________^
421 | | "Artifact?",
422 | | if urlstr.starts_with(&suggest) {
423 | | urlstr
... |
430 | | },
431 | | ),
| |_____________________________^ expected `String`, found `Result<String, Error>`
|
= note: expected struct `std::string::String`
found enum `std::result::Result<std::string::String, anyhow::Error>`
help: use the `?` operator to extract the `std::result::Result<std::string::String, anyhow::Error>` value, propagating a `Result::Err` value to the caller
|
431 | )?,
| +
|
mismatched types:
src/app/from_string.rs#L423
error[E0308]: mismatched types
--> src/app/from_string.rs:423:37
|
423 | / ... urlstr
424 | | ... .strip_prefix(&suggest)
425 | | ... .unwrap()
426 | | ... .split('/')
427 | | ... .find(|x| !x.is_empty())
| |__________________________________________________^ expected `&str`, found `Option<&str>`
|
= note: expected reference `&str`
found enum `std::option::Option<&str>`
help: consider using `Option::expect` to unwrap the `std::option::Option<&str>` value, panicking if the value is an `Option::None`
|
427 | .find(|x| !x.is_empty()).expect("REASON")
| +++++++++++++++++
|
publish
buildx failed with: ERROR: failed to solve: process "/bin/sh -c cargo build --target x86_64-unknown-linux-musl --release && cp /app/target/x86_64-unknown-linux-musl/release/mcman /app/mcman" did not complete successfully: exit code: 101
|
publish
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, docker/setup-buildx-action@v2, docker/login-action@v2, docker/metadata-action@v4, docker/build-push-action@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|