newlispfanclub.alh.net

Try escaping the ampersand as &. × is the multiplication cross sign...

I was thinking of creating something that would allow running untrusted newLISP code (think serverless, function-as-a-service et c) as a CGI, only allowing to act on submittes post data and do calculations and spit out the result. Now, with pledge() and newLISP running in a chroot already, the idea ...

On OpenBSD pledge() system call forces the current process into a restricted-service operating mode. I know newLISP can import function from shared libraries, but I have never done so yet. So I thought I'd give it a try with pledge(): > (import "/usr/lib/libc.so.96.0" "pledge") pledge@F99015DECD0 > ...

Hi, Lutz

Are there any checksums/signatures to verify downloads?

Kirill

rickyboy wrote:

Kirill wrote:Happy Easter!

With a name like Kirill, surely you know that Easter (Pascha) is really next week. ;) Христос воскресе!

Indeed - I'll be celebrating a week later :)

Hi, all HTTPS (and other TLS variants) is becoming more and more common. I'm seeing this as a certain pain for myself on client side (as server side is more easily solvable) (not a huge pain, I can easily use other tool in that case, but newLISP would be nice). The LibreSSL projects provides a libra...

Thank you, both! Good to know that it wasn't someone trying to hijack systems running newLISP. :)

What is the correct SHA1 checksum for the release? In http://www.newlisp.org/downloads/development/SHA1.txt it says SHA1(newlisp-10.7.4.tgz)= 5a3ce129f43138773abdc479a03512699e8a4256 But I'm getting a different SHA1 when fetching tgz myself: km ~/src $ ftp http://www.newlisp.org/downloads/developmen...

Thanks, Lutz! I had a feeling it had to do with (pretty-print) default change, but didn't try to figure out what was the default before the change, so that I could restore it.

And here was the "fix" for me for now:

Well, that didn't happen earlier. I became aware of the issue when my SLA calculator became "broken".

Could the issue be caused by this change in 10.6.0?

The pretty-print default float setting has been changed to "%1.15g"

newLISP v.10.6.2 on FreeBSD 10.1 (on NearlyFreeSpeech) represents floats in some trange way: uptime:/home/public> newlisp newLISP v.10.6.2 64-bit on BSD IPv4/6 UTF-8 libffi, options: newlisp -h > (float 99.0) 99 > (float [b]99.1[/b]) [b]99.09999999999999[/b] > (float 99.2) 99.2 > (float 99.7) 99.7 >...

Yet another newLISP powered tool (http://uptime.is):

https://github.com/km/uptime

Lutz:

I've done a couple of fixes in the docs for yubi.lsp here: http://km.krot.org/code/newlisp/

Kirill

Thank you, Lutz. Two things: (1) I believe the version you diffed against is not the current 3.2 online - may be you have to hit refresh in your browser. See the position of the (set 'post-data "") statement, which has to come after the 'when'. This was the change from 3.11 to 3.2. Yes, the diff was...

cgi.lsp has been updated again, to version 3.2 : http://www.newlisp.org/code/modules/cgi.lsp.html Thanks, Lutz! The file online does not seem to include the change below, though --- cgi.lsp.orig 2012-12-05 00:48:29.632208151 +0000 +++ cgi.lsp 2012-12-05 00:51:34.799112862 +0000 @@ -132,10 +132,13 @...

The issue is solved, so I remove the test CGI scripts. Thanks.

When running on nfshost.com, make sure you do not run with /usr/local/bin/newlisp, which probably is a very old version of newLISP. Instead compile your own version of newLISP on nfshost and put it in e.g: /home/public/bin/newlisp, and of course put #!/home/public/bin/newlisp as the first line in y...

And here's a patch for web.lsp: http://km.krot.org/code/web.lsp.patch

Patch for cgi.lsp: http://km.krot.org/code/cgi.lsp.patch

Now http://km.krot.org/cgitest3.cgi works properly as well.

I have a fix! http://km.krot.org/cgitest4.cgi

Patch will follow shortly...

This updated version 3.1 of cgi.lsp should fix this: http://www.newlisp.org/code/modules/cgi.lsp.html ps: see also here http://newlisponrockets.com/rockets-item.lsp?p=67 ps: updated to 3.11 cgi.lsp a few minutes later Thanks, but now CGI:get returns nothing at all: http://km.krot.org/cgitest3.cgi

I suspect the issue is with newLISP, as perl works just fine:

http://km.krot.org/cgitest2.cgi (source: http://km.krot.org/cgitest2.txt).

All clues welcome!

Kirill

Hi, all, I've had an issue that bothered me for a while now. Several times I've noticed that data, which newLISP receives from CGI, is incomplete. I don't know if it's a newLISP issue or not, but I've experienced it with CGI under both Apache (behind Squid on NearlyFreeSpeech) and mathopd (behind ng...

hilti wrote:No. But seems indeed possible to solve.

How did You manage to get CouchDB working? Because I think the interface is only accessible via https.

Cheers
Hilti

Try with "curl" bindings, maybe (https://gist.github.com/1119771)?