Pike-devel

pike-devel@lists.lysator.liu.se

2 participants
3046 discussions

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

Pike 8.0.462 beta/release candidate
by Peter Bortas 14 Jul '17

14 Jul '17

Pike 8.0.462 beta/release candidate: https://pike.lysator.liu.se/pub/pike/beta/8.0.462/Pike-v8.0.462.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/beta/8.0.462/Pike-v8.0.462-Darwin-15.4… https://pike.lysator.liu.se/pub/pike/beta/8.0.462/Pike-v8.0.462-win32-oldli… Hopefully Bill has time to update it with better mac builds before we release it. Changes since last beta: * Debug.Peek renamed Debug.Inspect -- Peter Bortas

1 0

Pike 8.0.460 beta
by Peter Bortas 12 Jul '17

12 Jul '17

Pike 8.0.460 beta candidate: https://pike.lysator.liu.se/pub/pike/beta/8.0.460/Pike-v8.0.460.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/beta/8.0.460/Pike-v8.0.460-Darwin-15.4… https://pike.lysator.liu.se/pub/pike/beta/8.0.460/Pike-v8.0.460-win32-oldli… This is not a release candidate. There are some changes without CHANGES and I'm not quite comfortable with the namespace the Debug.Peek functionality is living in. 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 Filesystem.Monitor - 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. 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. o Debug.Peek 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.Peek("/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 Search Fixed a race condition when updating the database. o Parser.HTML Fixed a condition where Pike would run out of stack space for large documents. o ADT.Heap Fixed heap corruption when the same object is pushed more than once. It will now be considered as calling adjust(). o Inotify Addressed an issue where the backend might be stuck in pending indefinitely. o FSEvents EventStreamMonitor now works with other backends. o Standards.BSON Fixed incorrect encoding/decoding of Binary data. o Stdio.Buffer Fixed a crash when attempting to create a rewind key on a buffer returned by read_buffer(). 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 Sql.pgsql 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. -- Peter Bortas

2 6

module dumping when using buildroot
by H William Wellliver III 06 Jul '17

06 Jul '17

I've noticed that the module dumping portion of the installer fails to work properly when using a buildroot (for packaging purposes). It seems that the call to pike -x dump clears the module path, which causes pike to try to use a module path reflective of the final installed location, which doesn't exist yet. This causes compilation of dump to fail because (at least) Getopt can't be found. I'm not sure why -DFAKEROOT and friends don't avoid this problem. I didn't really dig too far into that aspect of the problem. I can confirm that setting a PIKE_MODULE_PATH containing the built module directories from the pike dist as part of the create_process call that starts dump causes the initial compilation problem to go away. I'm not sure whether dump's module path should be those from the build directory, or from the fakeroot-installed directory. The problem has been replicated on linux and solaris by doing "make install buildroot=/tmp". Any thoughts? Bill

1 0

executable bit set on non-executable files in lib
by H. William Welliver III 05 Jul '17

05 Jul '17

I’ve been working on a pike configuration for pkgsrc, and in the process, pkgsrc has noticed that there are a number of files in lib that are set executable. I know that there are a few files that can be run standalone, but these don’t seem to be in that category. Any objection to me updating those files so that they’re not executable? Examples: Web.pmod/Api.pmod/Twitter.pmod Parser.pmod/LR.pmod/GrammarParser.pmod Any thoughts? Bill

2 1

pgsql fixes and improvements are in 8.0 and 8.1
by Stephen R. van den Berg 27 Jun '17

27 Jun '17

I've been running a large regression-suite-test here locally on the pgsql driver. Out came some problems in the case of multiple statements running on the same connection in parallel raising one or more errors. The driver sometimes got out of sync with the database because they did not agree on which of the multiple running statements needed to be canceled early. These issues have been fixed. Regression tests now show zero problems. I'm running both 8.1: 66d6ffe9de148d15a4d52e25f23a66d81e98e0f8 and 8.0: 83a8fde6fd9d74a7f35361390fe4e3c1ad9d77ea on all my production systems as of now. Anyone using PostgreSQL with Pike is invited to test as well. -- Stephen.

1 0

Constants with program with parent dependency
by Arne Goedeke 27 Jun '17

27 Jun '17

Hi all, the following code does not work anymore in pike 8: constant fail = ({ A }); class A { array foo = fail; } As far as I can tell the reason was that previously unfinished programs were not considered to use their parent and so the reference of A in the array ended up being a program instead of the function. The commit which introduced this change in behavior was 86ce26dde736531829bbf1466c0d2504e8973466 My feeling is that the new behavior is actually correct, or is this a regression? Arne

1 0

Major problem with SQLite binding handling
by H. William Welliver III 22 Jun '17

22 Jun '17

I’ve noticed an odd problem a few years ago with using parameter bindings with SQLite and never really took the time to figure out the cause until now. I think it’ a pretty major problem that can be easily fixed, though would cause problems for anyone relying on the (imo) currently broken behavior. Basically, the problem is that when using parameter bindings with strings, the pike glue determines the type of the data based on the width of the string: if it’s a wide string, the parameter is bound as a text, but if it’s 8 bit, it’s bound as a blob. The problem is that text and blob values aren’t evaluated the same, so even though a text value and blob value may be identical byte-wise, they are not equal when doing comparisons and so queries that would seem to match actually don’t. This is compounded by the fact that SQLite has no restrictions on what may be stored in a field (type definitions on a table are merely default suggestions) and SQLite will happily store whatever you want (such as a blob value in a text field). For example, imagine a table m with an integer field id and a char field value: s->query(“INSERT INTO m VALUES(1, 'value a’)); s->query(“INSERT INTO m VALUES(2, :value)”, ([“:value”, “value a”])); s->query(“SELECT * FROM m where value=‘value a’”); The third query will return 1 record instead of the expected 2 because the field value in the second row is stored as a blob and thus does not match a text query. In order to retrieve both records, you must use LIKE or know to cast the value to text using “AS TEXT” in the query, which is obviously a lot less ideal in most cases. If all of your data is stored using the pike glue, and you’re always using parameters, it’s possible never to see the problem, but if not, this causes all kinds of problems because of the need for constantly casting values and possibly using blob literals, which are not human readable when you’re really trying to query for a non-wide string. My suggestion is to change the binding type for 8 bit string parameters to text in order to match the rest of the string handling. It would be good to have a datatype that caused a parameter to be bound as a blob, either a native byte array or some object that wraps an 8 bit string (Sql.BinaryString?) in order to cause the binding to act accordingly. Of course, this causes a compatibility problem for anyone who was using pike binding with bindings previously (is there anyone who us doing this and hasn’t run into this problem?), as any 8-bit strings that weren’t binary data would be stored as blobs, even if they were in a text typed field. These records would need to be re-stored with the proper text type, which could be done with a query to update the table. My sense is that this is the proper thing to do, as blob fields should be reserved for data that’s actually binary data (as opposed to text). Thoughts?

3 3

Pike 8.0.450 beta
by Peter Bortas 18 Jun '17

18 Jun '17

Onl popular demand, Pike 8.0.450 beta: https://pike.lysator.liu.se/pub/pike/beta/8.0.450/Pike-v8.0.450.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/beta/8.0.450/Pike-v8.0.450-Darwin-15.4… https://pike.lysator.liu.se/pub/pike/beta/8.0.450/Pike-v8.0.450-win32-oldli… This is not a release candidate, just something that includes Concurrent to play with until there is a real release. Changes since Pike 8.0.438 (release 9) ---------------------------------------------------------------------- New Features ------------ o Concurrent The Concurrent module simplify asynchronous code by synchronizing events in different ways. As an example the connection() function shown will repond with Concurrent.Promise object that at some point will represent either a connected socket or a failure. Concurrent.Promise connection(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; } The returned promise could the be used in various ways. // On success, call make_request(con, query). On failure call // werror(msg). connection(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. connection(host, port) ->then(make_request, werror, query1) ->then(make_request, werror, query2); // Call bridge_ports(con1, con2) when both connections are // established. Concurrent.all(connection(host1, port1), connection(host2, port2)) ->then(bridge_ports, failure); // Call make_request(con) once either of the connections are // established. Concurrent.race(connection(host1, port1), connection(host2, port2)) ->then(make_requet, query); Bug fixes --------- o Search Fixed a race condition when updating the database. o Parser.HTML Fixed a condition where Pike would run out of stack space for large documents. o ADT.Heap Fixed heap corruption when the same object is pushed more than once. It will now be considered as calling adjust(). o Inotify - Addressed an issue where the backend might be stuck in pending indefinitely. - EventStreamMonitor now works with other backends. o Standards.BSON Fixed incorrect encoding/decoding of Binary data. o Stdio.Buffer Fixed a crash when attempting to create a rewind key on a buffer returned by read_buffer(). 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.

1 0

Pike 8.0 release 9 RC1
by Peter Bortas 11 Jun '17

11 Jun '17

Pike 8.0.438 beta/release candidate: https://pike.lysator.liu.se/pub/pike/beta/8.0.438/Pike-v8.0.438.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/beta/8.0.438/Pike-v8.0.438-Darwin-15.4… https://pike.lysator.liu.se/pub/pike/beta/8.0.438/Pike-v8.0.438-win32-oldli… Changes since Pike 8.0.404 (release 8) ---------------------------------------------------------------------- New Features ------------ o Calendar Updated Calendar to use timezonedata from tzdata2017a. o GL & GLUT Prefer Quartz implementation on systems that have it (OS X). o GTK2 - Add -x objective-c for Darwin. - Support linking against other implementations than X11. o Protocols.HTTP Connecting to HTTP proxies over HTTPS is now supported. o Web.decode_jwk() Support decoding of symmetric (ie HMAC) keys. o Web.encode_jws() and Web.decode_jws() Added simplified API for dealing with JSON Web Signature values. Bug fixes --------- o Runtime - Variant dispatcher Improved string range checking. Fixes mismatches due to te lazy string range (ed string(8bit)) exceeding the typed string range (eg string(7bit)) for narrow strings. o mkpackage Support multiple sub-packages with the same name. Gnu-tar doesn't like being asked to extract the same file multiple times from the same tar-file. It claims that the second file doesn't exist in the archive. This can happen when a sub-package has been replaced with a fixed version. o smartlink Don't override MACOS_DEPLOYMENT_TARGET if it's been specified. This should prevent "compiled against version x but linking against version y" warnings. o Arg & ADT.Struct Survive use by old (ie 8.0.232) pike binaries. Roxen 6.0.130 uses a Pike 8.0.232 binary with current modules. o Backend.PollDeviceBackend Make set_signal_event_callback() optional. This fixes the warning "An expression of type function({ Backend = object(implements _static_modules.Builtin()->defaultBackendClass) } : void) cannot be assigned to a variable of type function({ Backend = object(implements _static_modules.Builtin()->Backend) } : void).". o bool Make sure that 0 is part of the range for the bool type. o Charset Fixed encoding errors for two characters in the GSM-03.38 charset. o Debug Fixed typo in mask in check_callback_chain(). Fixes infinite loop in circularity detection. o Gdbm Support building with gdbc 1.13. Fixes obscure compilation error when building with gdbm 1.13 due to a symbol clash with the symbol "fatal" used as an argument in the macro definition of gdbm_set_errno(). o Mapping Removed extraneous and conflicting prototype. Fixes linking issues on NT. o Protocols.HTTP - Fixed do_async_proxied_method() losing the timeout during TLS negotiation. - Now fails immediately if Query is unable to open a socket, instead of waiting 120 seconds for a time out. - Allow connection reuse also when the server is a hostname. o Thread.Mutex - Perform a thread yield on mutex onlock in an attempt to reduce thread starvation. o Sql.pgsql - Added an extra synchronisation condition, and increased parallelisation to resolve all detected race conditions (which in rare circumstances (many parallel queries on a single filedescriptor) could have resulted in a deadlock). -- Peter Bortas

1 0

Jump to page:

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