Pike-devel August 2017

pike-devel@lists.lysator.liu.se

4 participants
14 discussions

Proposal: Create Stdio.Port from systemd-provided socket
by Chris Angelico 22 Nov '17

22 Nov '17

Branch: rosuav/systemd-sockets Currently, you can create a Stdio.Port("stdin") as a means of accepting a socket handed to you as FD 0. However, there's no way to accept a socket given as any other FD, making it impossible to use this for systemd's sockets. Example: $ cat /etc/systemd/system/listendemo.service [Unit] Description=Listen Demo Requires=listendemo.socket [Service] User=rosuav ExecStart=/usr/local/bin/pike /home/rosuav/listendemo.pike WorkingDirectory=/home/rosuav $ cat /etc/systemd/system/listendemo.socket [Socket] ListenStream=123 $ cat listendemo.pike object mainsock = Stdio.Port("systemd", acceptloop); void acceptloop() { while (object sock=mainsock->accept()) { write("Accepted sock: %O\n", sock); sock->write("Stub\n"); sock->close(); } } int main() { write("Main sock: %O\n", mainsock); return -1; } Note that the "User=rosuav" directive means that Pike is run as a non-root user. This spares the application the hassle of managing privileges securely, as it never gets root privileges (assuming, of course, that the only reason it needed root was to bind to a privileged port, which is true for a lot of programs). As with "stdin" mode, the second parameter is optional (blocking vs nonblocking). This won't break on non-systemd systems for two reasons: firstly, all it ever does is query environment variables, and secondly, it does this only if the application requests it explicitly, so you have to actually ask for it. Is this something that would be useful? Feel free to bikeshed the API - it's not in 8.1 yet, so anything can change. ChrisA

3 6

Roadtrip through Scandinavia, spontaneous meetup(s)?
by Stephen R. van den Berg 03 Aug '17

03 Aug '17

As it happens, I'm doing a roadtrip (with my wife, and 2 kids (19 and 7)) through Scandinavia right now. Our itinerary is a little bit flexible, we're planning and booking one day ahead, however, it looks like we are going to be in and around the following places in the next few days (actually, these are the places we plan on spending the nights on that day, so we're going to be in that place the following morning until lunch (at least) as well): Fri Aug 4th: Copenhagen Sat Aug 5th: Goteborg Sun Aug 6th: Linkoping Mon Aug 7th: Stockholm Tue Aug 8th: Stockholm Wed Aug 9th: Oslo If any Pikers think it'd be nice to meet up casually for lunch, dinner or just a beer, in and around those dates/cities, drop me a note. Incidentally, I can only read email replies, since the mailinglist gateway is still down (I presume). -- Stephen. <srb(a)cuci.nl>

2 2

Pike 8.0.466 beta/release candidate
by Peter Bortas 03 Aug '17

03 Aug '17

Pike 8.0.466 beta/release candidate: https://pike.lysator.liu.se/pub/pike/beta/8.0.466/Pike-v8.0.466.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/beta/8.0.466/Pike-v8.0.466-Darwin-15.4… https://pike.lysator.liu.se/pub/pike/beta/8.0.466/Pike-v8.0.466-win32-oldli… Last months release candidate never got promoted to release, so the changes is very similar. Changes since Pike 8.0.438 (release 9) ---------------------------------------------------------------------- New Features ------------ o Concurrent The Concurrent module simplifies asynchronous code by synchronizing events in different ways. As an example the connect() function shown below will respond with a Concurrent.Future object that at some point will represent either a connected socket or a failure. Concurrent.Future connect(string host, int port) { Stdio.File con = Stdio.File(); Concurrent.Promise p = Concurrent.Promise(); if( !con->async_connect(host, port, lambda(int success) { if(success) p->success(con); else p->failure("Failed to connect to "+host+":"+port+"\n"); })) { p->failure("Failed to open socket.\n"); } return p->future(); } The returned future can then be used in various ways. // On success, call make_request(con, query). On failure call // werror(msg). connect(host, port) ->on_failure(werror) ->on_success(make_request, query); // On success, call make_request(con, query1) followed by // make_request(resp, query2), where resp is the return value from // make_reqest. connect(host, port) ->then(make_request, werror, query1) ->then(make_request, werror, query2); // Call bridge_ports(con1, con2) when both connections are // established. Concurrent.all(connect(host1, port1), connect(host2, port2)) ->then(bridge_ports, failure); // Call make_request(con) once either of the connections are // established. Concurrent.race(connect(host1, port1), connect(host2, port2)) ->then(make_requet, query); o Debug.Inspect Allows for interactive debugging and live data structure inspection in both single- and multi-threaded programs. Example: In the program you'd like to inspect, insert the following one-liner: Debug.Inspect("/tmp/test.pike"); Then start the program and keep it running. Next you create a /tmp/test.pike with the following content: void create() { werror("Only once per modification of test.pike\n"); } int main() { werror("This will run every iteration\n"); werror("By returning 1 here, we disable the stacktrace dumps\n"); return 0; } void destroy() { werror("destroy() runs just as often as create()\n"); } Whenever you edit /tmp/test.pike, it will automatically reload the file. Bug fixes --------- o ADT.Heap Fixed heap corruption when the same object is pushed more than once. It will now be considered as calling adjust(). o FSEvents EventStreamMonitor now works with other backends. o Filesystem.Monitor - Reduced initialization latency. - Changed the polling heuristic. This is intended to reduce poll (and notification) delays in some circumstances. - Improved robostness of adjust_monitor(). - Removed some dead and obsolete code. - Scan accelerated monitors too. Both the Inotify and FSEvents APIs claim that they support notifications on eg network file systems, and while they will succeed in notifying on changes performed by the local host on such file systems, they will not on changes performed by other hosts. To avoid missing such changes these monitors need to be actively scanned too. - Fixed lost acceleration with InotifyMonitor Recover from race-condition where when a file was repeatedly created and deleted, acceleration was lost. - Fixed symlink issue with InotifyMonitor. - Added support for more fine-grained tracing of monitors. o Inotify Addressed an issue where the backend might be stuck in pending indefinitely. o mappings Fixed an off by one error in random(mapping) that randomly caused values of type PIKE_T_FREE from the freelist to be exposed to Pike. o Nettle.Hash Fixed NULL-dereference in Nettle.Hash()->crypt_hash(). o Parser.HTML Fixed a condition where Pike would run out of stack space for large documents. o Search Fixed a race condition when updating the database. o Sql.pgsql - Sped up BEGIN/COMMIT statements. - Preserve the initial error message in case of multiple error messages during the same transaction. - Flush out unseen error messages upon connection close to stderr. - Closed a prepared-statement-cache race when the same statement is offered multiple times before it finalises the cache entry. - Fix sync errors with the database in case of multiple running statements on a single connection that generate multiple errors. - Eliminate spurious sync errors on pipe-lined transactions (multiple transactions in flight on a single file descriptor). - CancelRequests (to cancel running queries) caused sync errors with the database when multiple queries were in flight. - Eliminate transient error messages on database restarts. o Sql.SQLite When using query bindings, strings are now always stored as strings; previously, 8-bit strings were stored as binary objects (BLOBs) and wide strings were stored as unicode strings, which caused 8-bit strings to be unequal (and thus not returned) when used in a standard string query. Binary values may be stored as BLOBs using bindings by wrapping the binary string in a multiset. For example, to store the value "myBinary" as a BLOB value using a binding, use: (<"myBinary">). o Standards.BSON - Fixed incorrect encoding/decoding of Binary data. - Bugfixes for the decoding of Binary values of subtype 2, Binary values of subtypes above 0x7f and Datetime values with negative values. o Standards.JSON Fixed integer overflow in decode() on 64-bit platforms. o Stdio.Buffer - Fixed a crash when attempting to create a rewind key on a buffer returned by read_buffer(). - Fixed integer overflow in read_json(). Building -------- o Configure Attempt to detect the tool prefix depending on ABI. Improves detection of pkg-config. o Java Detect system installation of JavaVM framework on MacOS X. o Stdio Improved support for NetBSD. Regards, -- Peter Bortas

2 1

problems with configure and smartlink
by H William Wellliver III 01 Aug '17

01 Aug '17

I've been working on getting pike packages set up using pkgsrc, and I've run into some strange behavior on (at least) Linux: The configure scripts for modules seem to be using the smartlink binary and the generated Makefiles use the smartlink script at bin/smartlink. Is that intentional? Also, I think the configure test that controls how the smartlink binary works is broken (or at least different than the script), and causes configure and compilation to work incorrectly when using the pkgsrc cwrappers: The smartlink script converts -R options to -Wl,-rpath,..., and that the smartlink binary at least on the current system I'm using, seems to just drop them in favor of environment variables. For example (I modified the script to print the command it would run): [root@pkgsrc-pbulk Pike-v8.0.462]# SMARTLINK_DEBUG=true ./smartlink gcc -R/tmp -L/tmp SMARTLINK: gcc -L/tmp -L/tmp ... [root@pkgsrc-pbulk Pike-v8.0.462]# SMARTLINK_DEBUG=true bin/smartlink gcc -R/tmp -L/tmp SMARTLINK: gcc -L/tmp -Wl,-rpath,/tmp ... It seems to be because of the results of this test: checking for ld.so run path method... use LD_LIBRARY_PATH/LD_RUN_PATH It would seem like using the environment variables would be a use case of last resort. Perhaps -Wl should be used for more than just Linux 2.x? bill

1 0

2026

2025

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 August 2017