As is tradition a release has been prepared at the new years party with Champagne in one hand and keyboard in the other waiting for the clock to hit 24:00.
Pike 8.0.528 release candidate:
https://pike.lysator.liu.se/pub/pike/beta/8.0.528/Pike-v8.0.528.tar.gz
Other builds:
https://pike.lysator.liu.se/pub/pike/beta/8.0.528/Pike-v8.0.528-Darwin-15.4.... https://pike.lysator.liu.se/pub/pike/beta/8.0.528/Pike-v8.0.528-win32-oldlib...
Real Mac build comes when Bill has time to have a look at that.
Changes since Pike 8.0.498 (release 11) ----------------------------------------------------------------------
New Features ------------
o Sql.pgsql
- Added support for PostgreSQL 10's stronger password authentication (SCRAM-SHA-256). - Slightly reduced overhead. - Support IEEE binary float database-wireformat. - Prevent new queries from starting in the local_backend.
o Crypto.Hash.SCRAM
New class to support SCRAM authentication.
o Thread.ResourceCount
New module to allow threadsafe race-condition-free counting of resources.
o SSL.File
Support query_fd() and set_buffer_mode() methods.
o Toole.Standalone.check_http
- Allow redirect responses. - Support --expect option.
Bug fixes ---------
o Compiler
Improved variant robustness.
o Calendar
Updated tzdata to 2017c.
o Crypto.CCM
Fixed initialization of the iv.
o Filesystem.Monitor
- Fixed issue with next_poll being set to zero causing polling every second.
- Fixed indexing the NULL value error when InotifyMonitor was used in combination with a filter_file() that doesn't accept everything.
o HTTPLoop:
Fixed some potential race conditions.
o Image.Image
- Improved argument checking in apply_curve(). Non-integer array values lead to use of uninitialized curve values.
o Image.PVR
Fixed size check for twiddled images.
o MIME
Support trailing newline in MIME part epilogues.
o Protocols.HTTP
Fixed incoming chunked transfers (timed async works now, chunk options are properly 'parsed').
o Protocols.LDAP
Fixed race condition on initializing LDAPS.
o Search.Utils
Updated debug string format.
o Sql.pgsql
- Suppress spurious 'File not open' blurts on stderr when the connection is still pending and we inspect the connection object.
- Signal EOF early before closing the SQL result portal and thoroughly cleanup bufcon/stashcount to prevent occasional deadlocks on asynchronous object destructions.
- Suppress rare "access in destructed object" messages.
- Rip out fundamentally flawed reconnect logic, made failures consistent.
- Repair SSL connect logic.
- Update documentation.
- Repair fetch_row_array().
o mktime/System.TM
Make timezone management consistent (especially UTC handling).
o Standards.IIM
Disabled debug output for unknown segment markers.
o Stdio.send_file
Improved support for TLS/SSL; wait for TLS handshake to complete before calling the sendfile done callback when sending an empty string. This fixes the issue where the connection got closed before TLS handshaking was completed, confusing the other side.
o Image
Creating images with mode "grey" now works as documented, e.g. Image.Image(10,10,"grey",123);
Optimizations -------------
o mktime/System.TM
Considerable speedup and a reduction in codesize.
Building & Tools ----------------
o Image.SVG
Fall back to using the unprefixed pkg-config if the arch-prefixed doesn't exist.
o Mysql
Support MariaDB 10.2 headerfiles.
o precompile
Support precompilation with Pike 8.1 again.
o smartlink
Fixed multiple issues on Darwin & NetBSD.
o Whitefish
Use the standard VPATH.
o Yp
Support using libtirpc. Glibc 2.26 has removed the Sun RPC implementation...
Regards,
Peter Bortas wrote:
Pike 8.0.528 release candidate:
In case you didn't notice, I ported over a memory leak fix Martin found. It has been there for a long time already, so maybe it's not critical for most users; then again, leaks are never good (just ask Intel ;-).
Peter Bortas wrote:
As is tradition a release has been prepared at the new years party with Champagne in one hand and keyboard in the other waiting for the clock to hit 24:00.
Pike 8.0.528 release candidate:
Paraphrasing Al Lowe: Release early, release often... Maybe we should have another go at an official 8.0?
Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote:
I can make another build this week. Can you do the Mac build Bill?
I have a few more NT-related fixes I'd like to get in.
As it turns out, I still have one particularly pesky deadlock case which I'm chasing for pgsql (which preferably should be fixed). So let's aim for Tuesday next week?
On Wed, May 9, 2018 at 3:50 PM Stephen R. van den Berg srb@cuci.nl wrote:
Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote:
I can make another build this week. Can you do the Mac build Bill?
I have a few more NT-related fixes I'd like to get in.
As it turns out, I still have one particularly pesky deadlock case which
I'm
chasing for pgsql (which preferably should be fixed). So let's aim for Tuesday next week?
Are these regressions compared to the last build? If not I'm going to make the build this week. It's a long weekend this week, next week is going to be hectic, so probably not going to happen. I'm OK with with delaying the build until Friday.
Regards,
Not regressions as such. I'll try and wrap it up Friday morning the last.
On Wed, May 9, 2018 at 9:24 PM, Peter Bortas bortas@gmail.com wrote:
On Wed, May 9, 2018 at 3:50 PM Stephen R. van den Berg srb@cuci.nl wrote:
Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote:
I can make another build this week. Can you do the Mac build Bill?
I have a few more NT-related fixes I'd like to get in.
As it turns out, I still have one particularly pesky deadlock case which
I'm
chasing for pgsql (which preferably should be fixed). So let's aim for Tuesday next week?
Are these regressions compared to the last build? If not I'm going to make the build this week. It's a long weekend this week, next week is going to be hectic, so probably not going to happen. I'm OK with with delaying the build until Friday.
Regards,
Peter Bortas
Stephen R. van den Berg wrote:
Stephen R. van den Berg wrote:
Not regressions as such. I'll try and wrap it up Friday morning the last.
Ah well, hunting deadlocks is always a tricky business. Found the cause, just now. Committing the fix shortly.
Done. All (my) CHANGES have been documented (already).
pike-devel@lists.lysator.liu.se