Search
Friday, 13th of July 2018, 1:46:08 UTC
1:59:08
blep-on-external
ACTION uploaded an image: lukd.png (106KB) < https://matrix.org/_matrix/media/v1/download/ponies.im/7b926b5e35069d2e9bca6fa0e6fe5605 >
1:59:10
blep-on-external
a small comparison
2:43:38
beach
Good morning everyone!
4:51:34
beach
A new version of the specification of the SICL memory allocator is now available in case someone feels like reviewing it: http://metamodular.com/allocator.pdf
5:51:58
stacksmith
beach: looks good!
5:52:12
beach
It works too it seems. :)
5:53:18
stacksmith
That's even better than just looking good.
6:43:53
beach
shrdlu68: I think that book has some very deep insight. It is quite hard to read though, so I am taking my time. But it has already given me some interesting understanding of some parts of society that concern me.
6:47:07
beach
shrdlu68: I don't know whether the author is going to mention it, but it occurred to me right away that commercial software development is an inadequate equilibrium, which is why free software is often able to do "better" in terms of some quality metric.
6:51:07
shrdlu68
beach: Indeed, the book made me appreciate how powerful behavioral economics is at creating useful models of complex systems.
6:53:27
TMA
shrdlu68: beach: which book are you talking about? I am unable to find it in logs
6:53:54
beach
https://equilibriabook.com/toc/
8:55:20
shrdlu68
hajovonta: Morning.
10:59:18
jmercouris
how to go from '(0 1 2 3) to '((0 1) (2 3))?
10:59:56
jmercouris
I can think of a naieve loop based way to do it
11:00:00
jmercouris
but there must be a better way
11:02:40
dim
alexandria:plist-alist does that I think
11:03:01
dim
well no it gives ((0 . 1) (2 . 3)) of course
11:03:03
jmercouris
dim: close enough, it makes a list of cons cells
11:03:06
jmercouris
I can work with that
11:03:33
dim
I like higher order naming for those structures based on cons cells
11:37:53
jdz
I think in other languages/libraries this is called "chunk".
11:38:06
jdz
Take a sequence, and cut it into chunks.
13:17:19
phoe
I ended up writing a lot of cod
13:17:35
phoe
it's time to take a step back, document and refactor it
13:23:44
phoe
ebrasca: https://github.com/phoe/waveflow/
13:25:26
phoe
There is no documentation and little tests though.
13:27:59
dim
mmm, how to debug a “Control stack exhausted (no more space for function call frames).” when you can't reproduce the bug?!
13:30:32
phoe
dim: give us the (whole long) stacktrace
13:31:10
phoe
or rather - look for repetitions inside it
13:31:23
phoe
if there's a function or a group of functions that keeps on repeating, that's where you need to look
13:31:35
dim
https://github.com/dimitri/pgloader/issues/810#issuecomment-404822140
13:31:37
phoe
and if there's not - the case becomes much, *much* more interesting
13:31:41
dim
I don't have such information phoe
13:31:59
dim
I guess it was more a rhetoric question
13:32:11
phoe
dim: well then, rhetoric question, rhetoric answer (:
13:32:32
phoe
if you can't reproduce it then it's not an issue; if you can reproduce it, then you can get a stacktrace
13:33:16
dim
pgloader is a little different from other CL systems, it's an application that I'm not typically the user of
13:33:25
dim
so I have users who reports bug, and sometimes I can't reproduce
13:33:54
phoe
dim: when it encounters fatal errors, it SHOULD save stacktraces somewhere.
13:34:13
phoe
if the user reports a bug, then they should give you the respective stacktrace as a part of the bug report.
13:34:43
phoe
if it is not designed to save stacktraces, then you have a thing to implement. (:
13:34:45
dim
--debug reports the stacktrace
13:34:51
dim
I'm not sure why not in that case
13:35:49
dim
see https://github.com/dimitri/pgloader/blob/master/src/main.lisp#L295
13:36:33
dim
oh I see, the error is caught in the handler-case, not the handler-bind, somehow, preventing the stacktrace from being printed out...
13:36:55
jmercouris
is there any way to get the path of the currently running lisp image? (from a saved binary)
13:37:02
dim
(because it seems like I have hooked the stack trace printing at the wrong place)
13:37:07
phoe
jmercouris: from the OS, I think?
13:37:12
jmercouris
phoe: Can you expand?
13:37:22
jmercouris
maybe someone has wrapped this in UIOP? or somethign?
13:37:33
dim
you might find it somewhere in /proc/<pid>?
13:37:52
Bike
if you mean a dumped executable, couldn't you use argv[0]
13:38:16
jmercouris
how do I access argv within lisp?
13:38:24
phoe
dim: the first thing I saw when I looked at that was "handler-case on top of handler-bind... this sounds fishy"
13:38:28
jmercouris
is it implementation specific?
13:38:43
dim
it prints KABOOM!, it should print the backtrace
13:39:15
jmercouris
ah, simple as that, thank you
13:39:21
phoe
jmercouris: as long as you deployed using UIOP tools.
13:40:23
jmercouris
Damnit, that doesn't show the full path
13:40:32
jmercouris
well, depending on how the OS launches
13:40:52
jmercouris
well, it is a start, gotta go for now
13:43:18
Bike
what are you using it for?
13:43:34
Bike
if you have resources in the same directory, i think uiop has specific things forthat
Friday, 13th of July 2018, 13:46:08 UTC