arrdem

The uv v0.2 extension & its architecture.

Bazel's "modules" system as of Bazel 6+ divides the world into "modules", each one of which can invoke "extensions" to request side-effects and configuration above and beyond the "normal" Bazel build graph. pip.parse() and the new uv.project() machinery are extensions.

Extensions' view of the world is a global one. They see all the requested configurations from all modules "at once", so they can do things like global reuse of generated targets.

The new uv extension's world is one of projects, being a (pyproject.toml, uv.lock) pair. This allows us to do [dependency-groups] which don't exist in the uv.lock alone, and compute extra activation modes.

Notionally the reworked architecture is simple and follows the same pattern as the original version. Translate every wheel in any uv.lock into a whl_file__* repo, ...Translate every sdist in any uv.lock into a sdist_file__* repo, containing the fileFor every versioned package in each lock with a sdist, create a `sdist_b

arrdem

Monoversion

This script exists to compute the 'monoversion' of the repo. The monoversion is designed to represent in a somewhat human readable format what commit was released and roughly what repository state that represents.

This script is intended for use under Bazel as a --workspace_status_command, so that we can build artifacts out of Bazel which include a somewhat meaningful version numbers.

arrdem

First things first, obviously I work on SRE and EE. The thing that originally got me hyped about software was when I realized I could write tools that wrote more tools, or gave me leverage over the tasks at hand. I have net-negative interest in repetitive tasks and want to see us find ways to move faster with more confidence.

To me, classical specification-driven tools for parser or test or what have you generation are good examples of success in this field. You take a formal specification of some sort and begin to iterate on it and poke holes in it until you've arrived at something which produces the correct behavior. From a certain perspective, all of these tools are compilers. Sounds a lot like an LLM, but the basis in formal evaluation semantics brings confidence in the results of the tool. In theory at least, proof in software being what it is.

Current generation LLMs are best understood as a probabilistic recall database with lossy compression. An LLM is not a formal system, nor does it have any under

arrdem

// A mostly complete implementation of the PromQL parse grammar

?start: expr+

// PromQL defines a bunch of suffix modifiers which we have to support
expr: simple_expr vector_range? vector_offset? vector_at?
?simple_expr: parenthetical | binary | invocation | vector_expr | literal

parenthetical: "(" expr ")"

arrdem

#!/usr/bin/env python3

"""
Usage:
  find src/app -name "*.scss" -exec ./scss-use-vars -I <your-theme.scss> {} \+

About:
  This is a quick and dirty implementation of part of an SCSS decompiler.
  It parses obvious color definitions, and replaces inline colors with definitions where possible.

arrdem

diff --git a/libs/metadata/src/main/kotlin/io/elten/metadata/models/LogEntry.kt b/libs/metadata/src/main/kotlin/io/elten/metadata/models/LogEntry.kt
index b90704e78..b7fd96d64 100644
--- a/libs/metadata/src/main/kotlin/io/elten/metadata/models/LogEntry.kt
+++ b/libs/metadata/src/main/kotlin/io/elten/metadata/models/LogEntry.kt
@@ -1,5 +1,6 @@
 package io.elten.metadata.models
 
+import io.elten.models.OrgEvent
 import org.hibernate.annotations.Generated
 import org.hibernate.annotations.GenerationTime

arrdem

"""An I2C driver for the ClusterCTRL/ClusterHAT device(s)."""

from enum import Enum
from itertools import chain, repeat
from time import sleep
from typing import Union

import smbus

arrdem

---
openapi: 3.0.0
info:
  title: A simple message queue over HTTP

tags:
  - name: message
    description: |
      Operations pertaining to messages.

arrdem

---
filters:
  - name: Assigned, Reported, Commented and not resolved
    jql: |
      (assignee = currentUser() OR reporter = currentUser() OR comment ~ currentUser()) AND status != Resolved ORDER BY updated DESC

  - name: My open issues
    jql: |
      assignee = currentUser() AND resolution = Unresolved order by updated DESC

arrdem

package me.arrdem.ox;

import io.lacuna.bifurcan.IList;
import io.lacuna.bifurcan.Lists;
import kotlin.jvm.functions.Function0;
import org.jetbrains.annotations.NotNull;

import java.math.BigInteger;

public final class Nat implements Comparable<Nat> {