Search
Thursday, 4th of June 2020, 16:33:36 UTC
16:39:01
jackdaniel
ralt: also, pointing out potential problems in the code is something to be thanked for, not to be sorry about, hence thank you! :)
16:39:46
ralt
It's more the "point out a problem, point out another problem in the next iteration" thing I'm apologizing for
16:39:57
ralt
Could've done both at once
16:41:35
ralt
jackdaniel: your argument probably works in the general case but starts failing in the case of under pressure environments
16:41:51
ralt
Whether you care or not is up to you guys
16:42:08
jackdaniel
I can do both, I'll wait for fe[nl]ix decision
16:42:16
ralt
Processes get preempted etc.
16:42:46
ralt
Well, if you do the timeout for lock, then every signature needs to have the timeout, including the count ones
16:43:41
ralt
The "read fixnum without lock" thing should be easy to test, actually
16:43:58
ralt
Just spawn 1k threads reading the value, another 100 threads modifying it after taking a lock, and see if everything dies
16:44:59
jackdaniel
regarding timeout for count ones, why would that be necessary? if I call mailbox-empty-p I would assume, that it will wait until the lock can be taken
16:45:25
jackdaniel
sorry, I need to go now (I'll read a backlog and check the PR later)
16:55:36
ralt
Why if you don't want to block?
17:01:31
axion
I'm having a lot of fun working on a new library for a change for creating generative art :)
17:08:18
scymtym
axion: is it wave function collapse?
17:09:27
axion
Nah, though I started working on a port the same author's ConvChain a while ago, which can be guaranteed to terminate, unlike WFC :)
17:10:20
axion
Just doing basic noise algorithms and a composition pipeline https://gist.github.com/mfiano/0ae825095bd26c4b6eda3e203b38da7d
21:33:25
jmercouris
I'm looking at Qlot right now, at this function specifically https://github.com/fukamachi/qlot/blob/master/install/quicklisp.lisp#L16
21:33:34
jmercouris
how does it fetch the installer???
21:33:51
jmercouris
it is supposed to call http-fetch, but it is just not actually fetching..
21:34:46
jcowan
How can I find standard functions that return two values, either the result or #t if there is a result, or #f #f if there isn't one? hashref works like this, but what else
21:36:43
jcowan
sorry, make that T and NIL
21:37:02
Shinmera
There's also no hashref
21:37:35
jmercouris
(ql::http-fetch "http://beta.quicklisp.org/quicklisp.lisp" #P"/Users/jmercouris/Downloads/quicklisp-JBCUCRBI.lisp")
21:37:37
Shinmera
As for 'how', you'll have to go through the symbol index.
21:37:39
jmercouris
Does not make a file, why not?
21:38:05
jmercouris
can anyone confirm if ql:http-fetch is working on their machines as I expect it to be for myself?
21:38:45
jmercouris
I also tried the variation: (ql-http:http-fetch "http://beta.quicklisp.org/quicklisp.lisp" #P"/Users/jmercouris/Downloads/quicklisp-JBCUCRBI.lisp")
21:39:07
jcowan
Anyway, what else uses that result protocol?
21:39:12
_death
function-lambda-expression returns 3 values, that you can think of as generalized booleans.. same goes for get-properties
21:40:23
Shinmera
Not sure about standard functions, but a bunch of libraries make use of that convention.
21:43:19
jmercouris
hm, that's frustrating
21:43:26
jmercouris
it must be OS specific or configuration specific
21:43:28
Shinmera
jmercouris: if it didn't work, the quicklisp-installer wouldn't work either.
21:43:43
jmercouris
Yes, that's what I deduced
21:43:51
_death
jmercouris: you could try wireshark.. or adding print statements..
21:44:14
jmercouris
adding print statements? where is http-fetch even defined?
21:44:36
_death
don't think you can trace CL operators
21:44:38
jmercouris
I don't even know to which system the ql-http package belongs
21:45:18
jmercouris
it puts me to a strange file
21:45:28
jmercouris
it takes me to here: /Users/jmercouris/Source/Lisp/qlot/proxy.lisp
21:45:44
Shinmera
_death: it's not required to work but you can do it
21:46:14
jmercouris
I don't understand all of this indrection in proxy.lisp
21:46:29
jmercouris
I'm sure there is some reasoning, what it is, I can't know
21:46:32
_death
jmercouris: does it redefine ql-http:http-fetch?
21:46:40
jmercouris
(setf (fdefinition (find-symbol (string '#:http-fetch) '#:ql-http))
21:47:16
jmercouris
I mean it kind of makes sense I guess, maybe
21:47:22
jmercouris
probably a lot of hacks to get Qlot to work
21:47:42
jmercouris
https://github.com/fukamachi/qlot/blob/master/proxy.lisp
21:48:56
_death
well, now can see which one is to blame.. (I've a good guess)
21:48:56
jmercouris
_death: to clarify, did ql-http:http-fetch work for you?
21:49:05
_death
yes.. but I don't have qlot
21:49:15
jmercouris
yes, let me try in a fresh image without qlot quickloaded
21:49:30
jmercouris
this time, it worked
21:49:38
seoushi
http-fetch works for me. Had to be in the ql package tho since http-fetch is not external
21:49:54
jmercouris
you must have ql::http-fetch or ql-http:http-fetch
21:50:15
jmercouris
_death: what is your guess?
21:51:02
jmercouris
also what is qlot://localhost/???
21:51:18
jmercouris
qlot is a protocol now?
21:52:16
jmercouris
hm I changed it to #-quicklisp, and it worked
21:52:44
jmercouris
can you enlighten me what this is trying to do? add proxy support to quicklisp?
21:55:47
_death
if the url begins with the qlot prefix, it makes sure *proxy-url* is nil
21:56:14
jmercouris
what does that achieve?
21:56:26
jmercouris
the branch I can understand no problem
21:56:35
jmercouris
I'm wondering about a bigger picture explanation
21:56:41
jmercouris
why would this ever be necessary???
21:56:58
jmercouris
anyways, thanks for the debugging help
21:57:19
_death
I don't know much about qlot
22:05:40
_death
Shinmera: interesting that it works (for OPEN).. thanks
23:08:33
Lord_of_Life_
** NICK Lord_of_Life
3:10:08
beach
Good morning everyone!
4:10:49
emacsomancer
morning, beach!
Friday, 5th of June 2020, 4:33:36 UTC