freenode/#lisp - IRC Chatlog
Search
14:35:36
beach
Xach: Do you still check Quicklisp systems with SICL LOOP? I am asking because Alexandria contains two illegal LOOP forms.
14:43:44
phoe
unless you have a separate alexandria dist, which would be the first time I've seen one!
14:44:00
phoe
anyway - I'd clone alexandria into your local-projects and checkout whatever commit you need
15:01:19
troydm
doesn't seem so, as only variables that are used inside thread is global *server* and local port
15:02:39
troydm
basicly what I'm doing is debugging why https://github.com/cxxxr/cl-lsp is not working on MacOS as expected, as when I start cl-lsp with args tcp 10003
15:04:15
troydm
but it doesn't seems like it's something cl-lsp related, more probably related to jsonrpc and bordeaux-threads
15:45:37
troydm
it seems like jsonrpc is designed this way that when you bind a server on tcp it needs to load (ql:quickload "jsonrpc/transport/tcp" :silent t)
16:26:19
SpaceIgor2075
Hello! Can anybody recommend any resources to learn about modules,packages, asdf and projects? i am a newbie
16:27:23
phoe
once you've absorbed this document and played in the REPL with the knowledge you've gained this way, please come back for a bit more about ASDF, systems, and projects
16:32:33
Xach
i don't like its POV of "isn't this dumb system dumb? well, here's how it works" - I'd prefer an explanation from someone with less contempt for it.
16:33:53
beach
Xach: It's OK. I see Alexandria fixed the incorrect clause order. That's all I need for now.
16:34:33
Xach
beach: whenever i increase strictness (by updating my sbcl), something that is 5-10 years since last maintenance breaks
16:34:58
Xach
the current problem is a widely-used library named "access" which uses function designators wrong
16:35:36
phoe
Xach: is it possible for you to also test on high safety/debug settings? this exposes bugs that are not exposed otherwise, like this cl-unicode bug that I just encountered
16:47:52
phoe
I assume that is why this cl-unicode issue was not noticed by Xach when preparing the QL distribution
16:51:09
heisig
In case anyone is wondering, the correct way to restrict SBCL's compiler policy is (sb-ext:restrict-compiler-policy 'safety 3).
17:11:00
VincentVega
guys, i am reading the cl-containers docs for red-black trees and don't get one thing: is there really no function to find the closest element to a given or am i just not seeing it?
17:11:04
VincentVega
https://common-lisp.net/project/cl-containers/documentation/metabang.cl-containers-package/class-red--black--tree.html
17:27:32
ck_
yes, looks that way. It depends on what you mean by 'closest' then. If you're looking for something like a range test for the ordering that the tree uses.. well I don't see one either
17:35:03
ck_
if you need this type of look-up often or mostly, maybe a different data structure would be a better choice
18:21:29
benjamindc
IS there a way to get "(asdf:test-system "system")" to return an exit code of 1 when executed in a script for CI pipelines?
18:24:47
phoe
benjamindc: the convention is generally that if asdf:test-system signals an error, then it has failed
18:25:56
phoe
so you can do it like (handler-bind ((error (lambda (x) (print x) (print stacktrace) (exit 1)))) (asdf:test-system :foo) (exit 0))
18:29:28
aeth
benjamindc: In general, just ignore asdf:test-system in CI pipelines and just directly use the non-portable return value of whatever test suite you're using. ASDF doesn't want to have asdf:test-system return a non-portable return value, making it near-useless for CI
18:29:58
aeth
phoe's answer is the correct answer, but it winds up being like 5 lines of code just to return something that your test suite already returns that asdf:test-system is blocking...
18:34:15
aeth
benjamindc: Sorry, phoe's answer is almost the correct answer. You want to exit with (uiop:quit 1)
18:34:49
aeth
no, but I'm not very happy with any of them having used almost all of them in different projects of mine over the years
18:40:28
benjamindc
aeth i follow your advice, but my script returns 0 when there are failing tests: https://pastebin.com/zgKD6F4n
18:42:32
phoe
if your test framework returns gracefully when you run the test suite and there are failures, then you get what you see
18:42:49
aeth
benjamindc: most of them return the number of failed tests or can be configured to do so
18:42:50
phoe
you'll need to analyze the results manually and if there are any failures then you'll need to (exit 1)
20:17:02
emma
Not exactly lisp but do any of you enjoy electronic music like trance, house, or techno?
21:36:47
phoe
I can imagine the generated code must contain much more debug information and runtime checks
21:57:43
Xach
phoe: http://report.quicklisp.org/2021-01-02/failure-report.html has the report but there's a lot of noise from the things sbcl broke recently
21:58:24
phoe
Unhandled SIMPLE-CONDITION in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001A50103}>: break
21:59:22
phoe
The constant MINUTES-PER-INTERNAL-TIME-UNIT is being redefined (from 1.6666668e-8 to 1.6666666e-8)
21:59:59
Xach
i don't get the increased # of arithmetic error COMMON-LISP:FLOATING-POINT-INVALID-OPERATION signalled
22:01:53
phoe
the current master includes some floating point stuff that me and mfiano have coerced stassats into adding
22:03:13
phoe
(SB-KERNEL:MAKE-NUMERIC-TYPE :CLASS COMMON-LISP:FLOAT :FORMAT COMMON-LISP:SINGLE-FLOAT :COMPLEXP :REAL :LOW #<SINGLE-FLOAT quiet NaN> :HIGH #<SINGLE-FLOAT quiet NaN> :ENUMERABLE COMMON-LISP:NIL)
22:10:06
phoe
in here in particular: https://github.com/brown/protobuf/blob/master/protocol-buffer.lisp#L109-L121
22:17:04
Xach
i don't think that would help my recent problems, which stem from SBCL detecting more invalid code at compile-time.
22:21:22
phoe
(cl:define-symbol-macro foo #.(sb-kernel:make-single-float -1)) works fine on default safety/speed
22:26:50
mfiano
Minimum reproducible error: (compile nil (lambda () #.(sb-kernel:make-single-float -1)))
22:41:47
mfiano
Wasn't me this time. I did find about a dozen SBCL bugs over the last few weeks that have all been fixed, but not this one