Gibson Fahnestock

+1, it's not exactly a big deal, but newer versions of included deps is always nice. e.g. git in the current image doesn't support `git branch --show-current`, which I used...

This is maybe obvious, but until we have this feature, the workaround is to use `.as_str()` on the path, e.g.: ```rust let echo = Utf8Path::new("/bin/echo"); cmd!(echo.as_str(), "hi").run().unwrap(); ```

>Another thought on markdown support, should we support it at runtime, compile time, or both? Compile time only sounds reasonable to me (but I only use the derive API, so...

Update, rules_go moved to downloading this each time: https://github.com/bazelbuild/rules_go/pull/2729

@ljharb Tends to be supporting people who are still using 32 bit (and debugging 32 bit specific issues). The command would be `./configure --dest-cpu=$ARCH` where `$ARCH` is one of https://github.com/nodejs/node/blob/master/configure#L36-L37....

@ljharb But wouldn't that mean building from source? The tarballs should be available on [nodejs.org](https://nodejs.org/dist/v6.9.1/node-v6.9.1-linux-x86.tar.xz), so would it be possible to just specify the arch there?

@ljharb AFAIK running 32 bit binaries on 64 bit machines is something that people do, for lower memory footprint etc. I _think_ we actually run some tests for some of...

>@blorente is this point of contact; I'm happy to act as a backup. >Must have more than one person who is committed to review/approve PRs For what it's worth if...

I tried a few more things, and as far as I can tell: A spantrace is mostly useful if you have `#[instrument]` calls in all your functions. Setting this up...

My workaround for this was to move notifications to the bottom, following https://github.com/rcarriga/nvim-notify/pull/127. In my config (using [lazy.nvim](https://github.com/folke/lazy.nvim)) it looked like https://github.com/gibfahn/dot/commit/f1922ca89e8d9c85be8eeb16979ef4a18eb1c104 : ```lua { "rcarriga/nvim-notify", -- Notification plugin used...