error[E0277]: `?` couldn't convert the error to `aws_sdk_ec2::Error` --> src/main.rs:26:51 | 26 | let s3_result = s3.list_buckets().send().await?; | ^ the trait `From<SdkError<ListBucketsError>>` is not implemented for `aws_sdk_ec2::Error` | = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait = help: the following implementations were found: <aws_sdk_ec2::Error as From<SdkError<AcceptReservedInstancesExchangeQuoteError, R>>> <aws_sdk_ec2::Error as From<SdkError<AcceptTransitGatewayMulticastDomainAssociationsError, R>>> <aws_sdk_ec2::Error as From<SdkError<AcceptTransitGatewayPeeringAttachmentError, R>>> <aws_sdk_ec2::Error as From<SdkError<AcceptTransitGatewayVpcAttachmentError, R>>> and 518 others = note: required because of the requirements on the impl of `Into<aws_sdk_ec2::Error>` for `SdkError<ListBucketsError>` = note: required because of the requirements on the impl of `From<SdkError<ListBucketsError>>` for `MyError` = note: required because of the requirements on the impl of `FromResidual<Result<Infallible, SdkError<ListBucketsError>>>` for `Result<(), MyError>`
Rust から OS の通知を使ってみようと思って notify-rust を動かそうとしたらエラーが出たのに対処したメモ。 発生したエラーは以下のやつ。(/home/mihyaeru/tmp/notification はプロジェクトディレクトリ)
1 2 3 4 5 6 7 8
$ cargo build Compiling libdbus-sys v0.2.1 error: failed to run custom build command for `libdbus-sys v0.2.1`
Caused by: process didn't exit successfully: `/home/mihyaeru/tmp/notification/target/debug/build/libdbus-sys-bb7c2267590697eb/build-script-build` (exit code: 101) --- stderrthread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Failure { command: "\"pkg-config\" \"--libs\" \"--cflags\" \"dbus-1\" \"dbus-1 >= 1.6\"", output: Output { status: ExitStatus(ExitStatus(256)), stdout: "", stderr: "Package dbus-1 was not found in the pkg-config search path.\nPerhaps you should add the directory containing `dbus-1.pc\'\nto the PKG_CONFIG_PATH environment variable\nNo package \'dbus-1\' found\nPackage dbus-1 was not found in the pkg-config search path.\nPerhaps you should add the directory containing `dbus-1.pc\'\nto the PKG_CONFIG_PATH environment variable\nNo package \'dbus-1\' found\n" } }', src/libcore/result.rs:1084:5 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
↓も確かにエラーになる。
1 2 3 4 5
$ pkg-config --libs --cflags dbus-1 Package dbus-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `dbus-1.pc' to the PKG_CONFIG_PATH environment variable No package 'dbus-1' found
hexo-deployer-s3とhexo-deployer-s3-cloudfrontがあり、CloudFrontを噛ませている場合はInvalidateを実行するために後者の方を使うのが楽そうな感じでした。 が、地味にhexo-deployer-s3からフォークした後に差が開いてしまっているようで、「なんで本家にオプション機能としてマージしなかったんだー」感が強くなってしまい、hexo-deployer-s3を使いつつInvalidateはaws-cliでやることにしました。どっちみち make deploy でラップしているので手間は変わらないかなーという感じです。