mlafeldt

Amazon Ion 1.1: Major Upgrades to Encoding, Performance, and Macros

Amazon Ion 1.1 represents the most significant update to the Ion data format since its public release, introducing a macro system for templated data, switching to little-endian encoding for 1.5-3x performance gains, and adding delimited containers for streaming writes—all while maintaining full backward compatibility with Ion 1.0. The specification's final comment period closed in March 2025, but official finalization remains pending as of late December 2025. ion-rust serves as the reference implementation with full Ion 1.1 support, while ion-java offers preview support. The update has also attracted criticism for its complexity, with some observers noting "second system syndrome" patterns in the ambitious scope of changes and the slow pace of both specification finalization and library adoption.

What Amazon Ion Is and Why It Matters

Amazon Ion is a richly-typed, self-describing, hierarchical data serialization format

mlafeldt

❯ CGO_CFLAGS="-I$DUCKDB_SRC/src/include"
CGO_LDFLAGS="-L$DUCKDB_SRC/build/debug/src -lduckdb -Wl,-rpath,$DUCKDB_SRC/build/debug/src"
go build -tags "duckdb_use_lib" -gcflags="all=-N -l" -o simple_debug ./examples/simple
# github.com/duckdb/duckdb-go/v2/examples/simple
ld: warning: duplicate -rpath '/Users/mathias/devel/duckdb/duckdb/build/debug/src' ignored
ld: warning: duplicate -rpath '/Users/mathias/devel/duckdb/duckdb/build/debug/src' ignored
ld: warning: ignoring duplicate libraries: '-lduckdb'

❯ lldb ./simple_debug
(lldb) target create "./simple_debug"

mlafeldt

#!/usr/bin/env bash
# Calculate bundle sizes for Cloudflare Pages worker modules.
# Output similar to `wrangler pages dev`.

set -euo pipefail

cd "$(dirname "$0")/.."

DIST_DIR="${1:-dist/_worker.js}"

mlafeldt

import { defineConfig } from 'drizzle-kit'
import crypto from 'node:crypto'
import { mkdirSync } from 'node:fs'
import path from 'node:path'

// Based on https://github.com/cloudflare/workers-sdk/blob/64710904ad4055054bea09ebb23ededab140aa79/packages/miniflare/src/plugins/shared/index.ts#L194
function idFromName(uniqueKey: string, name: string) {
  const key = new Uint8Array(crypto.createHash('sha256').update(uniqueKey).digest())
  const nameHmac = new Uint8Array(crypto.createHmac('sha256', key).update(name).digest().subarray(0, 16))
  const hmac = new Uint8Array(crypto.createHmac('sha256', key).update(nameHmac).digest().subarray(0, 16))

mlafeldt

EMAILENGINE LICENSE AGREEMENT

Version 2.1, 17 October 2023

PLEASE CAREFULLY READ THIS EMAILENGINE LICENSE AGREEMENT ("AGREEMENT"). THIS AGREEMENT CONSTITUTES A LEGALLY BINDING AGREEMENT BETWEEN YOU AND POSTAL SYSTEMS OÜ AND GOVERNS YOUR USE OF THE SOFTWARE (DEFINED BELOW). IF YOU DO NOT AGREE WITH THIS AGREEMENT, YOU MAY NOT USE THE SOFTWARE. IF YOU ARE USING THE SOFTWARE ON BEHALF OF A LEGAL ENTITY, YOU REPRESENT AND WARRANT THAT YOU HAVE AUTHORITY TO AGREE TO THIS AGREEMENT ON BEHALF OF SUCH ENTITY. IF YOU DO NOT HAVE SUCH AUTHORITY, DO NOT USE THE SOFTWARE IN ANY MANNER.

This Agreement is entered into by and between Postal Systems OÜ and you, or the legal entity on behalf of whom you are acting (as applicable, "You" or "Your").

1. DEFINITIONS

mlafeldt

#!/usr/bin/env -S deno run --allow-env=CLERK_API_KEY --allow-net=api.clerk.dev --no-check

import {
  ClerkAPIResponseError,
  ClerkBackendAPI,
  User,
} from "https://cdn.skypack.dev/@clerk/backend-core?dts";

const ClerkAPI = new ClerkBackendAPI({
  apiClient: {

mlafeldt

"""Webhook implementation for Github"""

import os
import json
import urllib.parse
import base64
import hmac
import hashlib
from cgi import parse_header
import boto3

mlafeldt

import { useState, useEffect } from 'react'
import { useAuth0 } from '@auth0/auth0-react'

export const useAuth0WithToken = () => {
  const auth0 = useAuth0()
  const [token, setToken] = useState('')
  const [error, setError] = useState()

  useEffect(() => {
    if (!auth0.isAuthenticated) return

mlafeldt

# kubectl run my-shell --rm -it --restart=Never --image alpine --command sh
apk add curl jq
BASEURL=http://169.254.169.254/latest/meta-data
ROLE=$(curl -s $BASEURL/iam/security-credentials)
CREDS=$(curl -s $BASEURL/iam/security-credentials/$ROLE)
AZ=$(curl -s $BASEURL/placement/availability-zone)
echo "export AWS_REGION=${AZ::-1}"; echo "$CREDS" | jq -r '{AWS_ACCESS_KEY_ID: .AccessKeyId, AWS_SECRET_ACCESS_KEY: .SecretAccessKey, AWS_SESSION_TOKEN: .Token} | to_entries | .[] | "export " + .key + "=" + .value'
# Paste the result into any shell and run `aws sts get-caller-identity` etc.
# What you can do about it:
# https://docs.aws.amazon.com/eks/latest/userguide/best-practices-security.html#restrict-ec2-credential-access

mlafeldt

Bug Report

AWS Landing Zone version 2.4.1 is currently broken. More specifically, validation of manifest.yaml has been broken since Dec 30 when version 1.8.0 of https://pypi.org/project/pykwalify was released. This release requires schemas to be written in YAML 1.2. However, Landing Zone's current schema and manifest file adhere to YAML 1.1 (where Yes|yes still means true). The result is that the Build step of AWS-Landing-Zone-CodePipeline currently fails during schema validation.

Hotfix

Update the buildspec of AWS-Landing-Zone-CodeBuild like this:

- - pip install --upgrade pykwalify