This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
using Statistics | |
using Printf | |
import Pkg | |
const JULIA_CMD = Base.julia_cmd() | |
run_cmd(cmd) = run(`$JULIA_CMD --startup=no --history-file=no -e $cmd`) | |
const N_STARTUP_RUNS = 5 | |
function run_latency_check() |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
using BenchmarkTools | |
@enum Shape Rock Paper Scissors | |
function play(a::Shape, b::Shape) | |
if a == b | |
return 0 | |
elseif a == Paper && b == Rock | |
return 1 | |
elseif a == Paper && b == Scissors |
- Docker runs on a Linux kernel
Docker can be confusing to PC and Windows users because many tutorials on that topic assume you're using a Linux machine.
As a Linux user, you learn that Volumes are stored in a part of the host filesystem managed by Docker, and that is /var/lib/docker/volumes
. When you're running Docker on a Windows or Mac OS machine, you will read the same documentation and instructions but feel frustrated as that path don't exist on your system. This simple note is my answer to that.
When you use Docker on a Windows PC, you're typically doing one of these two things:
- Run Linux containers in a full Linux VM (what Docker typically does today)
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/usr/bin/env bash | |
#export GITHUB_API_TOKEN="" | |
function log() { | |
printf "%s %s\n" "->" "$1" | |
} | |
CHECK_SYMBOL='\u2713' | |
X_SYMBOL='\u2A2F' | |
function execute_and_wait() { |