Treat passphrase like password in import-recovery-device
#19646
FirelightFlagboyci.yml
on: pull_request
dispatch
4s
Matrix: rust / test-rust-non-linux
rust
/
🐧 Linux: 🦀 Rust tests
4m 29s
docs
/
Build & Check documentations
python
/
(🐧 Linux only): 🐍 Python server tests
web
/
🌐 Web tests
⭐ CI is happy ⭐
4s
Annotations
3 errors and 3 warnings
|
rust / 🐧 Linux: 🦀 Rust tests:
cli/src/commands/device/import_recovery_device.rs#L39
useless conversion to the same type: `zeroize::Zeroizing<std::string::String>`
|
|
rust / 🐧 Linux: 🦀 Rust tests
Process completed with exit code 101.
|
|
⭐ CI is happy ⭐
Process completed with exit code 1.
|
|
rust / 🍎 macOS: 🦀 Rust tests
You are using macOS 12.
We (and Apple) do not provide support for this old version.
It is expected behaviour that some formulae will fail to build in this old version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.
|
|
rust / 🍎 macOS: 🦀 Rust tests
macOS's Gatekeeper has been disabled for this Cask
|
|
rust / 🍎 macOS: 🦀 Rust tests
You are using macOS 12.
We (and Apple) do not provide support for this old version.
It is expected behaviour that some formulae will fail to build in this old version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.
|