Thomas Leonard's work notes

(see roscidus.com for my main blog)

(Eio 1.5, Prometheus)

I've mostly been on holiday, but Eio 1.5 is now released. The main new features are support for Windows paths and the ability to set socket options before connecting. There's also an important fix for errors when using unconfined paths.

Eio

PR review:

  • Pre-connect socket options (follow up to #713) #875.

Release:

  • Prepare release #924.
  • [new release] eio (5 packages) (1.5) #30518.
  • Add "available" to opam files #921.

Prometheus

Testing the new Prometheus release with opam-repo-ci, it turned out that it broke more programs than expected:

  • [new release] prometheus (3 packages) (1.4) #30439.

To fix that, I switched to using mtime to measure times. Using a monotonic clock is the right thing to do for time-spans anyway, and using mirage-mtime allows it to work with unikernels too:

  • Use mtime to measure times #70.

Anil released the fixed 1.4, and then made a series of PRs towards 2.0, which I've been reviewing:

  • Move the Lwt logic out of the prometheus core #65.
  • Split prometheus-app into prometheus-reporter and add eio #71.
  • Lwt: Allow specifying an address to bind to as well as a port #72.
  • Add a config constructor to build config values directly #73.
  • prometheus-app: allow serving a registry other than the default one #74.

OCluster/OBuiler

Some minor PR reviews:

  • store_spec: fix the store lists in the error messages #218.
  • store_spec: make of_t's store argument non-optional #219.
  • worker: make --obuilder-store optional again #264.

Tangled

With GitHub down earlier this week, I had a look Tangled instead, learning a bit about AT protocol in the process. The idea is that you can self-host the actual repositories and the public metadata (e.g. follows), and manage your identity, but still use their web front-end.

On sign-up, I got given the handle talex5.tngl.sh but it was easy enough to change it to talex5.roscidus.com by adding a DNS entry. I'm not sure what this gets me, though. My handle resolves to did:plc:josqf6vymgz5nq5wjr4smc5y, and this is what gets recorded (e.g. in a follow), so although I could point my handle at a new DID it wouldn't take any of my history with it I think.