Shawn Cicoria

I have an older Razer Blade with a 970 NVidia 0 so, not much memory relative to the 10x series. Was seeing the error in the logs totalMemory: 6.00GiB freeMemory: 5.02GiB 2018-12-13 21:56:56.358056: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1511] Adding visible

Leaving this here as just a simple get an env variable and 'cast' to boolean is a PITA. But this is what I ended up with... const skipTestSetting = process.env.BOT_SKIP_KNOWN_FAILED_TESTS; export const shouldSkip = (t: TestObj): boolean => { const noSkip = skipTestSetting === 'true'

First - WHY WHY WHY doesn't the installer just deal with this error? What's clear from the message, or at least to me, is that the Developer Mode package added in "Developer Mode" is some sort of problem. First I tried DISM to repiar.

Performance of WSL and Disk IO The core performance killer is related to Windows Defender, and a primary scenarios is running Node package installers that are pulling down 100s, perhaps 1000s of files during an npm install <package>. For example, when I ran nvm install --lts --latest-npm it

I must be missing it, but I could never find the Travis CLI already built and published on Docker Hub. So, I just pulled together on. It's really simple. Really the only complexity is passing in the VOLUME mappings (2 of them) when you run the container. All

If you're launching VS Code from the WSL prompt there are 2 annoyances. The first is the logging messages that appear. The second is it's blocked and doesn't return. While there are some issues and requests for PRs for me this is working for