plexus

Apr  7 17:42:00 marceline NetworkManager[1776]: <info>  [1712504520.3629] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Apr  7 17:42:00 marceline NetworkManager[1776]: <info>  [1712504520.3630] manager: NetworkManager state is now ASLEEP
Apr  7 17:42:00 marceline ModemManager[1815]: <info>  [sleep-monitor-systemd] system is about to suspend
Apr  7 17:42:00 marceline systemd[1]: Reached target sleep.target - Sleep.
Apr  7 17:42:00 marceline systemd[1]: Starting systemd-suspend.service - System Suspend...
Apr  7 17:42:00 marceline systemd-sleep[24417]: Entering sleep state 'suspend'...
Apr  7 17:42:00 marceline kernel: PM: suspend entry (deep)
Apr  7 17:42:06 marceline kernel: Filesystems sync: 0.003 seconds
Apr  7 17:42:06 marceline kernel: Freezing user space processes
Apr  7 17:42:06 marceline kernel: Freezing user space processes completed (elapsed 0.001 seconds)

plexus

----- Error --------------------------------------------------------------------
Type:     clojure.lang.ExceptionInfo
Message:  
Data:     {:type "class java.lang.NullPointerException"}
Location: /home/arne/.gitlibs/libs/babashka/tools.bbuild/b0ff7daeaed20ac4e73c1f600ce6bef3cd49f257/src/main/clojure/clojure/tools/build/util/pod.clj:1:29

----- Context ------------------------------------------------------------------
1: (ns clojure.tools.build.util.pod
                               ^--- 
2:   (:require [clojure.string :as str]))

plexus

(ns pie-a-la-mode)

;; Concurrency example from The Pragmatic Programmers. Waiters check if there's
;; enough pie and ice cream before they sell an order, but if they don't
;; coordinate it's still possible to sell more than we have.
;;
;; The below code should return either :ok or :not-available for a given order.
;; If we oversell, then it will throw an exception.
;;
;; How would you change this to ensure that that doesn't happen?

plexus

• overtone/overtone#283

  A ten year old PR about sync-event being broken. Does no one actually use sync-event? The diff looks plausible, it adds a bunch of tests as well, but unsurprisingly it no longer applies cleanly.

  What we need here is for someone to open a REPL, verify that sync-event is indeed broken, and if so to rebase this branch on current main and submit a new PR.

plexus

Today we are happy and proud to announe the first public release of Piglet, a new programming language and dynamic runtime in the Lisp tradition, for the web age.

Piglet itself is written in JavaScript and Piglet. It can run in any modern JavaScript runtime, be it inside or out of the browser. We've been working hard on Piglet for the past six months, and are happy with how far it's come already.

That said we've been hesitant to make a public announcement. We have a big vision for Piglet, and bringing that vision into being is going to take time. We

plexus

POST /resolve

{:data {}
 :query [{:airtable/bases
          [{:airtable.base/tables
            [:airtable.table/id
             :airtable.table/base-id
             :airtable.table/fields
             :airtable.table/records
             #_:airtable.records/next

plexus

(setq tailwind-shorthands
      '((":float-right" "float: right")
        (":float-left" "float: left")
        (":float-none" "float: none")
        (":min-w-0" "min-width: 0")
        (":min-w-full" "min-width: 100%")
        (":row-auto" "grid-row: auto")
        (":row-span-1" "grid-row: span1/span1")
        (":row-span-2" "grid-row: span2/span2")
        (":row-span-3" "grid-row: span3/span3")

plexus

(module encode_decode
  (:import
    [fs :from "node:fs"]))

(def in (fs.readFileSync "/home/arne/tmp/screenshot_00.png"))
(def out (js:ArrayBuffer. (* 2 (count in))))
(def out-arr (js:Uint8Array. out))

(def [widx ridx] [0 0])

plexus

release:
  #!/bin/bash
  git clean -xfd ext
  export VERSION=$(just version_bump_version)
  just update_changelog "${VERSION}"
  git add .
  git commit -m "Release v${VERSION}"
  git tag "v${VERSION}"

update_changelog version:

plexus

;; Logging is a bit of a lost art. I see people use it the same way they use
;; println debugging, putting in lots of (log/debug "HERE") kind of stuff, and
;; then removing it afterwards.
;;
;; But with a good logging library these logging statements can continue to
;; provide value, even if (especially if) most of the time you turn them off.
;; For this you need to make good use of log levels like
;; error/warn/info/debug/trace. What follows is an illustrated example of how I
;; tend to use them.