Chris Pick

I created PR #347 with the solution I landed on. @matyix if we didn't already have a CoreOS vault-operator installation and we were installing from scratch I think we would...

Ok, from doing a quick bit of reading on the RTC alarm it sounds like the problem is that it can only be set wake the Kobo up at one...

It looks like this is because `fzf` does [`awk`-like tokenization by default](https://github.com/junegunn/fzf/blob/a0b42e6538092dc6dea9f918a7a74c9408e44d4c/src/tokenizer.go#L146) (unless a delimiter is provided). I think changing the various default `DELIMITER_STR`s from `[\t\n ]+` to `[^\t\n ][\t\n...

It makes sense to me to specifically identify authentication issues and only exit when one is detected. @pracucci: > We're experiencing small gaps in the metrics exported by the stackdriver...

I hit this error as well. I added a test case (`de::tests::enum_::internally_tagged::collection_struct::attributes`) in the [vec-invariant branch](https://github.com/cpick/quick-xml/tree/vec-in-variant) on my fork. It fails with: ``` ---- de::tests::enum_::internally_tagged::collection_struct::attributes stdout ---- thread 'de::tests::enum_::internally_tagged::collection_struct::attributes' panicked...

I haven't thoroughly experimented yet, but brew-based services don't seem to show up in `launchctl list` until `brew services foo start` is run for the first time so I'm not...

I ran into this same issue. I ran `mas list` and noticed an ID for a manually-installed App was missing (eg: 123456). I then ran `mas info 123456` after which...

Thanks for having a look! > But it creates a layering violation by layering one public API atop another. To my eye this is reasonable because the upper layer is...

I've also added a (loosely) related/complementary proposal to add safe functions to ignore and restore signals' actions in #2191.

> Could you suggest a complete API, or better yet post a PR? Sure thing. I've opened #2190 with my suggested implementation.