IRC channel logs

2026-04-20.log

back to list of logs

<jfred>I meant to try cloning it earlier, but since git-annex is finally in guix on aarch64... is something up with the public archive at files.spritely.institute? It's online and I can browse the linked directories in a browser, but I seem to get 503s from the server if I run a `git annex pull`: https://paste.sr.ht/~jfred/15c0c8b3356477f98259bfa4ff546f49dfa6554b
<jfred>possible I'm doing something wrong/misunderstanding something too
<jfred>(also: still getting the hang of git-annex, but it's *very* cool)
<dthompson>janneke: (web socket) in hoot mimicks the api of (web socket) in guile-websocket. it creates a port that you can read/write from like any other, without the use of websocket-send and websocket-receive.
<dthompson>we haven't yet implemented websocket-send and websocket-receive for hoot
<janneke>dthompson: ah right
<dthompson>I found this helpful for implementing a repl that works in the browser, so I added it. that's why the rest of the websockets api isn't there... I just didn't need it.
<dthompson>also part of the api might not be implementable given the way the websocket web api works... idk
<dthompson>janneke: out of curiousity, what are you building with hoot? it's exciting to see you trying it
<janneke>dthompson: it's probably more playing than building, as it turns out i probably need very little new/own javascript in the browser...
<janneke>i've been building a client and deamon as part of an emacs-dezyne-interface, to show dezyne-generated graphs (a system view, a state view, and a trace) as generated from command-line tools in the browser
<janneke>it's using https://gitlab.com/rma.wieringa/depyct
<janneke>i did the initial integration with hoot, which was pretty fun
<janneke>but (still) quite a lot of red tape, almost as much as all of my javascript code right now
<janneke>took me a bit to get JSON.parse working from scheme
<janneke>if we ever need to adopt maintenance of depyct, we'd probably want to rewrite that in guile/hoot (it's about 7000 loc of javascript, yuck)
<janneke>also, the import (scheme base) vs individual or parts of (hoot ..) was ... interesting :)
<janneke>ACTION has still to show this experiment to regtur, he might like to switch to using hoot early?
<dthompson>we've got a pure scheme json parser hanging out at https://codeberg.org/guile/guile/pulls/1 if you want one ;)
<dthompson>getting rid of a JSON.parse import all the associated complexity might help
<dthompson>jfred: I can reproduce that error. I will look at it.
<dthompson>thanks for letting us know
<dthompson>getting git-annex setup in this way was difficult and I guess something broke since we deployed it
<dthompson>a-ha, the service that is supposed to be running is stopped...
<dthompson>okay if I manually run the same command that the service is supposed to then it works
<jfred>dthompson: thanks! :)
<dthompson>now I'm trying to figure out why the service is borked
<jfred>guix service I assume? (I was actually kinda wanting something like that recently haha)
<dthompson>yeah
<dthompson>it's a custom one I wrote that isn't upstream
<dthompson>but it's just a glorified wrapper script around 'git-annex p2phttp'
<dthompson>which is a feature that guix's git-annex supports that I *did* upstream a patch for
<dthompson>I don't know why this service doesn't work! everything looks correct
<jfred>I know that feeling
<dthompson>the error I'm seeing in the shepherd log is the error I see when I start the daemon under the wrong user... but the service definition explicitly asks for the daemon to be started as that user
<dthompson>I don't think I will be able to fix this today
<jfred>that's fine! I'm sure there's a lot more important stuff to get done haha