iliana etaoin

`tailscale ssh` does not support the `-l` option to set the username

4

### What is the issue? I am attempting to use Tailscale SSH in GitHub Actions to rsync some stuff around. Here is an experience I'd like: 1. I don't have...

### What is the issue? If a user's home directory doesn't exist: ``` dreamweaver 0 ~ $ grep www-deploy /etc/passwd www-deploy:x:996:996::/nonexistent:/bin/bash dreamweaver 0 ~ $ ls -d ~www-deploy ls: cannot...

Exhaustive license searching

1

**Is your feature request related to a problem? Please describe.** In Bottlerocket, we use cargo-deny for [enforcing a license policy](https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/deny.toml), as well as [bottlerocket-license-scan](https://github.com/bottlerocket-os/bottlerocket-sdk/tree/develop/license-scan) to identify license files in vendored...

modeled_types: Use FromStr instead of TryFrom<&str>

3

[`FromStr`](https://doc.rust-lang.org/std/str/trait.FromStr.html) and [`TryFrom`](https://doc.rust-lang.org/std/convert/trait.TryFrom.html) are functionally equivalent traits, but the former has existed since Rust 1.0.0 and has much wider support across the ecosystem; `serde_plain` is a key example of this.

Misskey compatibility

8

I’d like to be able to use Pinafore with a Misskey instance. Would you be interested in pull requests for this? (I imagine that an incremental approach is likely best...

eeeee: https://linuxwit.ch/blog/2018/12/everything-that-lives-is-designed-to-end/ (The code of conduct still applies even though I've archived this repository. Please report any issues you've had with interactions outside GitHub to us.)

Support AsErrorSource for error sources that don't implement std::error::Error

3

Since starting to use SNAFU I've repeatedly run into libraries whose error types implement Debug + Display but not std::error::Error. Two options I can think of that might make this...

Get Travis to run full integration tests

5

Travis should compile and run all examples in AWS Lambda and verify output on pull requests. This is, of course, questionable from an AWS account security perspective. Some thoughts on...

The changes between 0.2.0 and 0.3.0 are significant enough to worth mentioning in a changelog, perhaps with a "follow these steps" to upgrade section.

handler should probably require FnMut, not just FnOnce

9

In this function signature: https://github.com/ilianaw/rust-crowbar/blob/0b1b1b72308faa6f0c176a8e9f5ef061dea4a951/src/lib.rs#L242-L250 FnOnce does not imply that the provided function can be called multiple times, which is an assumption made by Lambda. Perhaps FnMut is more appropriate?