lrworth
lrworth
@neongreen I keep looking for this package. If you point me at a WIP branch I can help develop a PR. EDIT: as for motivation, see [aws-arn](https://github.com/bellroy/aws-arn): it uses only...
Also, I needed to add ` StrictHostKeyChecking accept-new` for nix-docker, because the host was not listed in any known_hosts file. Unsure what is actually best practice here.
I have just seen the same thing from `bundle exec rails db:migrate`, and I'm using nix as well.
I've found the problem: libsass is being compiled with `-flto` resulting in LLVM bitcode objects which can't be linked with the `ld` provided by nix's clang. See: ``` ➜ file...
+1 for this feature that would give devs a low-friction pathway to improving documentation. Some suggestions for a first implementation, hopefully to fuel further discussion: - Make comments only accessible...
> vast array of other cases It could be useful for adding X-Ray tracing to AWS calls.
I get a very similar problem with `split-3.4.1`. Perhaps I'm using it incorrectly?
Probably related to #563.
Interesting. I’m not sure how I got my database into such a state but clearing Redis seems to have done the trick. If it’s always the case that participation_count >=...
nixpkgs 1.2.0 formats this block like this: ``` let in # Line 1 # Line 2 { } ``` The second comment line should be aligned with the first.