🇺🇦 Sviatoslav Sydorenko (Святослав Сидоренко) webknjaz

Learn Git

Please read&learn the following:

Learn to write good commit message and description

According to common commit style guides, it is required to write messages in an imperative manner. Make them actionable. Also avoid using -m as you

$ MACOS_VM_VERSION=12.4
$ MACOS_VM_CODENAME=$(softwareupdate --list-full-installers 2>&1 | grep "Version:\s$(echo "${MACOS_VM_VERSION}" | sed 's#\.#\\.#g')[0-9.]*," | awk -F' macOS ' '{print$2}' | awk -F, '{print$1}' | uniq)
$ MACOS_VM_NAME="ansible-core-ci-template-macos-${MACOS_VM_VERSION}-playground"
$ MACOS_INSTALLER_NAME="Install macOS ${MACOS_VM_CODENAME}"
$ MACOS_INSTALLER_VOLUME_NAME="${MACOS_VM_CODENAME}"-"${MACOS_VM_VERSION}"
$ MACOS_INSTALLER_VOLUME_PATH="/Volumes/${MACOS_INSTALLER_VOLUME_NAME}"
$ MACOS_DOWNLOADED_INSTALLER_APP_PATH="/Applications/${MACOS_INSTALLER_NAME}.app"
$ MACOS_CREATEINSTALLMEDIA_BIN_PATH="${MACOS_DOWNLOADED_INSTALLER_APP_PATH}/Contents/Resources/createinstallmedia"
$ MACOS_ORIGINAL_INSTALLER_VOLUME_PATH="/Volumes/${MACOS_INSTALLER_NAME}"

MPRIS is a mechanism for controlling players (including in-browser ones). It is usually bound to multimedia key presses. DEs usually have this integrated but WMs don't. To make this work in Awesome WM, playerctl can be used. It's subcommands just need to be bound to the multimedia keys.

Reproduce the launcher folder layout after the initial data sync
Fingerprint
Font size -> XL
Night Mode / Vision Comfort / Digital Wellbeing
Bitwarden
- Set up as a Passkey manager
- Set up buffer auto-clean
- Set up refresh on pull
FreeOTP+
MojeID klíč

💭 Thoughts

I want to have:

3 APs that would approximately evenly cover:
- ground floor
- second floor
- garage space
- bonus: reach some of the backyard/garden
~~Multipath connections between the APs~~
Bonded channels between the APs and the managed network switches (LACP 1+1 = 2Gbps)

Huh?

I've got an idea to fill the void of the non-existent PEP 517 build requirements provisioning. The problem is that currently there's no first-class citizen support for reproducible builds in the PEP 517 world. People usually set lower bounds on their build backend of choice and that's about it. Even if some will set exact pins in their pyproject.toml, it's not enough because those entries may contain unpinned (transitive) dependencies. One way to do this with python -m build is to set PIP_CONSTRAINTS environment variable (I haven't actually tested this yet but I expect it to work).

That workaround is suboptimal and leaves the users with no answer on how to manage the invocations and the

	for (const line of $x('/html/body/div[1]/div/div/div[2]/div[2]/div[2]/div/div[5]/div/div/div/div/table/tbody/a')) {
	if (!line.querySelector('.fontSizeMS>.text-ellipsis').textContent.includes("Batched CI for "))
	{
	continue;
	}
	line.style.display = 'none'; // don't .remove() because it breaks the page
	}

	from contextlib import contextmanager


	@contextmanager
	def show_start_end():
	print('START')
	try:
	yield
	finally:
	print('THE END')