Pike-devel January 2007

pike-devel@lists.lysator.liu.se

6 participants
16 discussions

Process.run
by Peter Bortas (nu med mindre Opera) ＠ Pike (-) developers forum 15 Jul '08

15 Jul '08

I just checked in a Process.run() in 7.7: http://pike.ida.liu.se/development/cvs/diff.xml?module=Pike&file=7.7/lib/mo… The rational for that is that I was once again reminded by a user this week that getting Process.create_process() or Process.Process right without some corner case blocking is hard. It's not obvious that if you bind pipes to booth stderr and stdout you have to take in to account that OS buffers are not limetless. Process.run() is a thin wrapper around Process.Process that collects stdout, stderr and exitcode and return them in a mapping. This could potentially result in huge strings, but will do what most users want and even already do when they call create_process() with both pipes bound. Something like this should be in 7.8, but I'm open to suggestions for other things that might be usefull to return in the mapping or for changing member names.

5 7

Returning 0 vs throwing errors in Stdio
by Peter Bortas ＠ Pike developers forum 27 Apr '07

27 Apr '07

I'd like someone to expand on the advantages of the following change in 7.7: > o Stdio > The functions read_file(), read_bytes(), write_file() and > append_file() now always throw errors upon errors, to allow easier > use as errno doesn't have to be checked. read_file() and > read_bytes() still returns 0 if the file does not exists. Specificly for read_file() on files you lack permissions for. > Stdio.read_file("/etc/shadow"); (1) Result: 0 vs > Stdio.read_file("/etc/shadow"); Failed to open "/etc/shadow": Permission denied /pkg/pike/intel-debian3_1/7.7.13/pike/7.7.13/lib/modules/Stdio.pmod/module.pmod:1820: Stdio->read_file("/etc/shadow",UNDEFINED,UNDEFINED) As I see it it only makes it harder to properly handle errors. If Pike had a well developed system for handling errors it would be an improvement, but now it's only going to lead to more and buggier code. Unless someone can come up with a good explanation* for why it should be changed it should be reverted. * Like for example "I've extended and documented the error classes. It's obvious and clear how to use them now!". That'd be nice.

7 16

7.6.102 beta
by Peter Bortas ＠ Pike developers forum 18 Feb '07

18 Feb '07

http://pike.ida.liu.se/pub/pike/beta/7.6.102/Pike-v7.6.102.tar.gz There are two changes since 7.6.100: * A builfix for Darwin PPC * A fix for a broken treeopt rule.

7 19

7.6.100 beta
by Peter Bortas ＠ Pike developers forum 30 Jan '07

30 Jan '07

http://pike.ida.liu.se/pub/pike/beta/7.6.100/Pike-v7.6.100.tar.gz I reverted all the rsif changes on 7.6. The interesting change since 7.6.98 is the fix for the SSL trouble Erik supplied a test case for recently. Protest now if you don't think this should be the next stable for some reason.

3 4

7.7 optimization
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 29 Jan '07

29 Jan '07

Comparing pike -x benchmark for 7.6 and 7.7 shows a performance decrease in most areas. I read this as - possibly a performance issue somewhere central, affecting most tests - a performance issue in append array, since it's almost twice as slow. - a performance issue with sort integers, as it's 1.3 times as slow. Ackermann.................. 1.089 Append array............... 1.985 Append mapping............. 1.002 Append multiset............ 0.967 Array & String Juggling.... 0.992 Clone null-object.......... 1.013 Clone object............... 1.046 Compile & Exec............. 1.062 Compile.................... 1.138 GC......................... 1.050 Insert in mapping.......... 0.993 Insert in multiset......... 0.995 Loops Nested (global)...... 0.658 Loops Nested (local)....... 0.635 Loops Recursed............. 1.000 Matrix multiplication...... 0.874 Read binary INT128......... 0.997 Read binary INT16.......... 1.042 Read binary INT32.......... 1.004 Sort equal integers........ 1.356 Sort ordered integers...... 1.253 Sort unordered integers.... 1.362 Sort unordered objects..... 1.032

1 0

ssl communication stalls
by ee (erik eriksson) ＠ Pike (-) developers forum 27 Jan '07

27 Jan '07

(filed as bug #4304) Below is a test case for a problem where communication between two Pike processes over SSL stalls with Pike 7.6.86. To reproduce, run in two different terminals on the same computer. Start as 1) pike bug.pike server 2) pike bug.pike client Expected behaviour: a lot of communication back and forth between the two processes: ping?, pong!, etc Observed behaviour: 7.6.51: works as expected 7.6.66: works as expected 7.6.76: works as expected 7.6.86: communication stalled after first message sent 7.7: communication stalled after first message sent Some hints: - Reason for problem seems to be that the read callback is deregistred from the underlying file object. - A workaround for the problem seems to be to pass 1 as 3rd argument to macro RUN_MAYBE_BLOCKING in method direct_write in SSL.pmod/sslfile.pike instead of SSL_INTERNAL_READING, preventing the callback to be unregistred (possible side effects of workaround unknown) bug.pike: #!/usr/bin/env pike int i = 0; class Server { // from http.server string my_certificate = MIME.decode_base64( "MIIBxDCCAW4CAQAwDQYJKoZIhvcNAQEEBQAwbTELMAkGA1UEBhMCREUxEzARBgNV\n" "BAgTClRodWVyaW5nZW4xEDAOBgNVBAcTB0lsbWVuYXUxEzARBgNVBAoTClRVIEls\n" "bWVuYXUxDDAKBgNVBAsTA1BNSTEUMBIGA1UEAxMLZGVtbyBzZXJ2ZXIwHhcNOTYw\n" "NDMwMDUzNjU4WhcNOTYwNTMwMDUzNjU5WjBtMQswCQYDVQQGEwJERTETMBEGA1UE\n" "CBMKVGh1ZXJpbmdlbjEQMA4GA1UEBxMHSWxtZW5hdTETMBEGA1UEChMKVFUgSWxt\n" "ZW5hdTEMMAoGA1UECxMDUE1JMRQwEgYDVQQDEwtkZW1vIHNlcnZlcjBcMA0GCSqG\n" "SIb3DQEBAQUAA0sAMEgCQQDBB6T7bGJhRhRSpDESxk6FKh3iKKrpn4KcDtFM0W6s\n" "16QSPz6J0Z2a00lDxudwhJfQFkarJ2w44Gdl/8b+de37AgMBAAEwDQYJKoZIhvcN\n" "AQEEBQADQQB5O9VOLqt28vjLBuSP1De92uAiLURwg41idH8qXxmylD39UE/YtHnf\n" "bC6QS0pqetnZpQj1yEsjRTeVfuRfANGw\n"); string my_key = MIME.decode_base64( "MIIBOwIBAAJBAMEHpPtsYmFGFFKkMRLGToUqHeIoqumfgpwO0UzRbqzXpBI/PonR\n" "nZrTSUPG53CEl9AWRqsnbDjgZ2X/xv517fsCAwEAAQJBALzUbJmkQm1kL9dUVclH\n" "A2MTe15VaDTY3N0rRaZ/LmSXb3laiOgBnrFBCz+VRIi88go3wQ3PKLD8eQ5to+SB\n" "oWECIQDrmq//unoW1+/+D3JQMGC1KT4HJprhfxBsEoNrmyIhSwIhANG9c0bdpJse\n" "VJA0y6nxLeB9pyoGWNZrAB4636jTOigRAiBhLQlAqhJnT6N+H7LfnkSVFDCwVFz3\n" "eygz2yL3hCH8pwIhAKE6vEHuodmoYCMWorT5tGWM0hLpHCN/z3Btm38BGQSxAiAz\n" "jwsOclu4b+H8zopfzpAaoB8xMcbs0heN+GNNI0h/dQ==\n"); void create(Stdio.File file) { write("server: got connection\n"); SSL.context ctx = SSL.context(); ctx->random = Crypto.Random.random_string; ctx->rsa = Standards.PKCS.RSA.parse_private_key(my_key); ctx->certificates = ({ my_certificate }); SSL.sslfile f = SSL.sslfile(file, ctx, 0, 0); f->set_nonblocking(lambda(mixed id, string data) { write("server: (%d) got data <%s>, sending pong\n", i++, data); f->write("pong!"); }, lambda() { }, lambda() { write("server: close callback, exiting\n"); exit(-1); }, 0, 0, lambda() { write("server: handshake done, waiting for client to initiate\n"); }); } } class Client { void create(Stdio.File file) { SSL.context ctx = SSL.context(); ctx->random = Crypto.Random.random_string; SSL.sslfile f = SSL.sslfile(file, ctx, 1, 0); write("client: connected\n"); f->set_nonblocking(lambda(mixed id, string data) { write("client: (%d) got data <%s>, sending ping\n", i++, data); f->write("ping?"); }, lambda() { }, lambda() { write("client: close callback\n"); exit(-1); }, 0, 0, lambda() { write("client: handshake done, sending ping\n"); f->write("ping?"); }); } } void main(int argc, array argv) { int port = 12345; if (argc == 2 && argv[1] == "server") { Stdio.Port p = Stdio.Port(); p->bind(port, lambda() { Server(p->accept()); }); write("server: waiting for connection\n"); } else if (argc == 2 && argv[1] == "client") { write("client: connecting\n"); Stdio.File socket = Stdio.File(); socket->connect("localhost", port); Client(socket); } else { write("specify client or server\n"); exit(-1); } while (1) { Pike.DefaultBackend(); } }

2 2

pike crash
by ee (erik eriksson) ＠ Pike (-) developers forum 25 Jan '07

25 Jan '07

>the following program crashes my pike. tested on various installations >(debian or ubuntu, all running pike v 7.6.86). > >ee@sprint:~/tmp$ cat crash.pike >class S { > SSL.context s; > void ss(Parser.XML.NSTree.NSNode sss) > { > Parser.XML.NSTree.NSNode ssss = sss[0]; > } >} >void main(){} >ee@sprint:~/tmp$ pike crash.pike >Segmenteringsfel (core dumped) >ee@sprint:~/tmp$ cat nocrash.pike >class S { > void ss(Parser.XML.NSTree.NSNode sss) > { > Parser.XML.NSTree.NSNode ssss = sss[0]; > } > SSL.context s; >} >void main(){} >ee@sprint:~/tmp$ pike nocrash.pike >ee@sprint:~/tmp$ pike -v >Pike v7.6 release 86 Copyright %Gï¿½%@ 1994-2006 Link%Gï¿½%@ping University >Pike comes with ABSOLUTELY NO WARRANTY; This is free software and you are >welcome to redistribute it under certain conditions; Read the files >COPYING and COPYRIGHT in the Pike distribution for more details. filed as bug #4302 / ee (erik eriksson) Previous text: >15166557 2007-01-22 15:20 /29 lines/ ee (erik eriksson) >Recipients: Pike (-) erfarenhetsutbyte >Subject: pike crash >-------------------------------------------------------------------- >the following program crashes my pike. tested on various installations >(debian or ubuntu, all running pike v 7.6.86). > >ee@sprint:~/tmp$ cat crash.pike >class S { > SSL.context s; > void ss(Parser.XML.NSTree.NSNode sss) > { > Parser.XML.NSTree.NSNode ssss = sss[0]; > } >} >void main(){} >ee@sprint:~/tmp$ pike crash.pike >Segmenteringsfel (core dumped) >ee@sprint:~/tmp$ cat nocrash.pike >class S { > void ss(Parser.XML.NSTree.NSNode sss) > { > Parser.XML.NSTree.NSNode ssss = sss[0]; > } > SSL.context s; >} >void main(){} >ee@sprint:~/tmp$ pike nocrash.pike >ee@sprint:~/tmp$ pike -v >Pike v7.6 release 86 Copyright %Gï¿½%@ 1994-2006 Link%Gï¿½%@ping University >Pike comes with ABSOLUTELY NO WARRANTY; This is free software and you are >welcome to redistribute it under certain conditions; Read the files >COPYING and COPYRIGHT in the Pike distribution for more details. > >(15166557) /ee (erik eriksson)/------------------------------------- >

1 0

Re: Pike + Perl? Any issues?
by bertrand.lupart＠linkeo.com 25 Jan '07

25 Jan '07

> It also seems someone has removed it from Pike7.7, so that particular > someone apparently doesn't want it maintained either. Noone was actually maintaining it, nor using it until now, apparently. If this module isn't maintained enough to be distributed mainstream, it would be good to have it in Monger with a big warning concerning it's usability. -- Bertrand

1 0

Pike + Perl? Any issues?
by Alexander Demenshin 24 Jan '07

24 Jan '07

Hi, I would like to use Perl from Pike, are there any issues? How stable/leak-free is Perl module? /Al

3 2

Instant rsif:esque functionality
by Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum 22 Jan '07

22 Jan '07

In needing a tool to convert files between utf8 and ascii with above-ascii code points escaped \xXX or \uXXXX, I just ended up refactoring rsif a bit. We now have a shiny process_files.pike in Tools.Standalone which you can inherit, providing a process callback of your own. This is what rsif looks like now: #! /usr/bin/env pike inherit Tools.Standalone.process_files; string version = ("$Revision: 1.5 $"/" ")[1]; string description = "Replaces strings in files."; string usage = #"[options] <from> <to> <files> rsif (\"replace string in file\") replaces all occurrences of the string <from> with the string <to> in listed files. The name of the files that were changed are written to stdout. Directories may be given instead of files, in which case all the files in that directory will be processed. Available options: " + default_flag_docs; int want_args = 2; string process( string input, string from, string to ) { if( has_value( input, from ) ) return replace( input, from, to ); } Complete documentation is available in refdoc comments in the file; http://pike.ida.liu.se/development/cvs/view.xml?module=Pike&file=7.6/lib/mo… As this makes writing rsif style hacks a mere pike expression or two, a logical next step would be some lazy person bringing this power kit right up to the pike command line, for instant ad-hoc directory tree processing goodness à la pike -e 'something'. That could make rsif the equivalent of "pike -p2 'replace(arg1,arg2)'" or similar. My own side dish hack quota just ran out for the day, but feel very free to pick up the ball! (Checked in to Pike 7.6 and 7.7.)

4 8

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel January 2007