9:09:55flip214jeosol: that's what I already used, yeah.
9:17:54MrMcI am trying to use parenscript with the Chartist javascript library how do I get parenscript to emmit new Chartist.Line('.ct-chart', data);
9:20:17MrMcThe challenge is that this is wrapped as a function returning new Chartist.Line('.ct-chart', data)
10:52:20phoeIs postmodern capable of handling multiple parallel requests to postgres?
10:57:57antoszkaphoe: have you tried running them with, say, lparallel?
11:01:22phoeantoszka: I have no idea how postmodern works on the inside. Even if I use multiple threads in my code, they may block on a single connection for example.
11:41:52flip214I guess you should be using (with-connection (... :pooled-p T) body) and not ever set *DATABASE* at all.
11:42:23flip214also note that (connect-toplevel) *does* set *database*
11:43:35flip214phoe: and also be aware of potential problems if you (need to) give the database connection up, eg. because of multiple independent requests via hunchentoot
11:44:15flip214a SELECT FOR UPDATE will not work, because a) the old transaction might/will be aborted, and b) you might get assigned some other connection
13:47:18schweersupgrading asdf is supposed to be pretty painless, right?
13:47:52schweersso I don’t necessarily have to install a new version for the whole system, but can drop it somewhere where the installed asdf can find it?
13:48:27svillemotschweers: /usr/local/share/common-lisp/source should be the right system-wide path
13:49:53shrdlu68schweers: This may help: https://common-lisp.net/project/asdf/asdf/Replacing-your-implementation_0027s-ASDF.html#Replacing-your-implementation_0027s-ASDF
13:52:14svillemotmy understanding is that schweers uses the ASDF from the Debian package, not from its implem, which is 3.1.7 in Debian "Stretch" 9
13:52:56schweersI’m not entirely sure whether asdf comes from the implementation (sbcl) or from debian. Is there a way to check which version is currently loaded?
13:53:22schweersIt seems that the cl-asdf package from debian testing is new enough, maybe I’ll use that or build a newer sbcl from source
13:53:56svillemotschweers: indeed you can install the one from testing, it will probably work
14:33:51schweersdo I have to hold on to the return value of LAUNCH-PROGRAM?
14:34:24schweersIt seems to me that the process dies in my program (where I do not care about the return value, other than the stream it contains)
14:37:44phoeschweers: I don't think so, if you want it to be fire-and-forget
14:37:57phoeon my machine it gives me a process-info structure of some sort
14:38:56flip214schweers: you'll need to PROCESS-CLOSE or similar when it's done.
14:39:02schweersI want to compress my output with bzip2. So instead of just opening the file (as I did until now), I create a bzip2 process. I give it as output the filename I previously opened directly and return the input stream, promptly forgetting the process-info value itself
14:39:22flip214schweers: that won't work in practice.
14:41:00schweersI get your point, but still: why do the processes seem to simply die? is it because the return value of launch-program is garbage collected?
14:46:49schweersthe thing is that I’m just working this into a somewhat complex program. so pasting the relevant bits isn’t really a straightforward process :/
15:17:29schweersturns out that I am giving some wrong parameters in. I gave a broken pathname, gave :rename-and-delete (which is illegal), and :error-output t is also apparently illegal