Scott Robinson quad

vgmstream/src/meta/opus.c

#include "meta.h"
#include "../coding/coding.h"
#include "../layout/layout.h"
#include "opus_interleave_streamfile.h"

/* Nintendo OPUS - from Switch games, including header variations (not the same as Ogg Opus) */

cinch: supervisor trees for Rust

Constraints

Intra-task concurrent, because the child tasks can opt-in to multi-task concurrency.

Types

pub trait Service {

Don't use log levels, use structured logging

I read [an argument for only two log levels: INFO and ERROR][only-info-error]. I [responded][log-response] essentially saying:

I lightly agree that we could get away with two log levels.
I strongly disagree that we only need two ways to log.

Like the blog post's author, most of systems that I've worked on have had poor logging practices. But unlike the blog post's author, I strongly suspect that's because most logging APIs offer poor affordances.

The Hybrid Service Architecture

I haven't found a description of the service architecture I frequently see; but, the Internet is lousy with descriptions of three tier and event driven architectures.

This write-up is for Future Me to point at when asked how to design a network service.

tl;dr

A server cluster, scaled horizontally
A queue cluster, scaled vertically or sharded

What is this architecture called?

I rarely see the classical three-tier architecture in the wild; I frequently see a different architecture.

I don't know this architecture's name. Do you?

The Three-Tier Architecture

The "three-tier architecture" has been the reference pattern for Internet services:

Classics 📜

Technical writing I don't believe will ever get old.

Mandatory

Why can't I start a service?

I can start a thread, if I want shared memory parallelism
I can start a process, if I want shared storage parallelism
I cannot start a service, if I want shared network parallelism

What would it take to add a start API?

Overly literal examples

Interceptors Are Functions Too

I could not agree more with my colleague and friend Travis Johnson's opinion that "[INTERCEPTORS ARE SO COOL][iasc]!" In that post, he succinctly describes the [Interceptor pattern][pattern] as used adroitly by [OkHttp][okhttp]. But, as is often the case, I believe a complicated object-oriented pattern obscures the simple functional gem within it.

What is an Interceptor?

I'll quote liberally from [OkHttp's documentation on the topic][okhttp-interceptor]:

Interceptors are a powerful mechanism that can monitor, rewrite, and retry calls. […] >

	from cryptography.hazmat.primitives.asymmetric.ec import ECDSA
	from cryptography.hazmat.primitives.hashes import SHA256
	from cryptography.hazmat.primitives.serialization import Encoding, PublicFormat
	from ykman.device import list_all_devices
	from ykman.logging import init_logging
	from yubikit.core import TRANSPORT
	from yubikit.core.smartcard import SmartCardConnection
	from yubikit.logging import LOG_LEVEL
	from yubikit.management import CAPABILITY
	from yubikit.openpgp import EcAttributes, KEY_REF, OID, OpenPgpSession

	function sync() {
	const srcId = "[email protected]";
	const syncWindowInDays = 7;
	const syncStatuses = [
	null,
	CalendarApp.GuestStatus.MAYBE,
	CalendarApp.GuestStatus.OWNER,
	CalendarApp.GuestStatus.YES,
	];