libera/#commonlisp - IRC Chatlog

16:47:59 fade ** NICK Fade

17:26:20 Posterdati gsll is broken again on openbsd :)

17:29:22 Josh_2 Wish there was a minimal version of clog

17:29:35 Josh_2 adding it as dependency broke my build pipeline because it depends on sqlite... :sob:

17:29:50 Josh_2 Version of clog without gui, without sqlite, only websocket!!

17:46:24 Josh_2 Time to rewrite clog :skull:

17:47:56 Josh_2 https://plaster.tymoon.eu/view/3964#3964

17:48:03 Josh_2 I am going to :man: :gun:

17:48:27 Josh_2 Why is cl-isaac like this

17:50:29 Posterdati :(

17:53:18 Josh_2 All these stupid CI pipelines do not aid rapid development

17:57:06 semarie Posterdati: could you define "broken" a bit more ? which lisp implementation ? which error ? etc...

17:59:10 semarie here, gsll passed 3480 on 3588 assertions (openbsd 7.4-beta, sbcl-2.3.8~, x86-64)

18:00:06 semarie and same question for cffi

18:00:23 Posterdati openbsd 7.3 amd64

18:01:44 Posterdati I fixed gsll and cffi to work on openbsd long ago...

18:02:28 semarie you are using sbcl from ports ? (it is an old version)

18:02:34 Posterdati no

18:02:39 semarie good :)

18:02:40 Posterdati sbcl-2.2.5-threads

18:02:56 semarie ah. still an old version

18:03:15 Posterdati but it worked

18:08:04 Josh_2 computers :angry:

18:08:20 Josh_2 can't I just be left alone with my lisp image and me :sob:

18:08:25 Josh_2 Why must I communicate with the outside world!!!

18:08:47 dlowe so your program can have a test load

18:09:09 dlowe it's like fuzzing except you get paid for it

18:09:53 Josh_2 :skull:

18:11:44 Josh_2 Had to grab upstream cl-isaac to fix lack :skull:

18:12:07 Josh_2 Had an old commit of lack because of broken cl-isaac :skull:

18:15:38 ecraven elephant is not developed any longer, right?

18:15:52 Josh_2 Right

18:16:03 ecraven is there a generic database library, that can do sql queries to different database backends?

18:16:09 Josh_2 Yes

18:16:33 ecraven could you tell me what it's called?

18:16:37 Josh_2 https://github.com/fukamachi/cl-dbi?ysclid=lmqmzleesd833248078

18:16:40 Josh_2 There might be a few

18:16:51 Josh_2 Personally I just use Postgres

18:25:39 jjnkn when i tried cl-dbi i encountered an issue with executing multiple sql statements at once; i wanted to run an sql script, so i just read the whole file and tried to execute its contents but cl-dbi signaled an error

18:59:08 Posterdati fixed!

19:38:36 Josh_2 Some choices with CLOG annoy me :skull:

19:39:08 Josh_2 I wish I could specify the listening URL :skull:

19:41:04 Josh_2 It is omnificent :sunglasses:

21:23:01 gendl__ Hi, is it true that Bordeaux-threads doesn't have shared read-locks and write-locks, where multiple readers can hold the lock at the same time as long as no writer holds the lock? You'd have to implement those yourself?

21:26:20 gendl__ (i know there's a pretty formulaic way to build readlocks/writelocks given basic mutexes and condition variables)

21:30:14 bike gendl__: as you can see here https://sionescu.github.io/bordeaux-threads/locks/

22:16:30 fe[nl]ix gendl__: that's correct. there's a feature request open: https://github.com/sionescu/bordeaux-threads/issues/77

22:16:43 fe[nl]ix I hope to address it before the release of 1.0

22:21:11 Josh_2 There is book Little Book of Semaphores

22:21:13 Josh_2 Might come in handy

4:11:04 gendl__ fe[nl]ix: https://github.com/sionescu/bordeaux-threads/issues/77#issuecomment-1726829485

4:15:12 gendl__ just made a👆 naive implementation which apparently works for my use case, may or may not be useful as a reference. It's naive because it doesn't do anything about "fairness" and it'd be possible for the lock to get swamped by constant overlapping readers (i.e.in an application where the reader count never gets to zero, a writer might be locked out indefinitely). So some kind of "fairness" heuristic should probably be

4:15:12 gendl__ added.