Pike-devel

pike-devel@lists.lysator.liu.se

2 participants
3046 discussions

Pike 8.0.164 release candidate
by Peter Bortas 08 Feb '16

08 Feb '16

New build with Parser.Markdown removed. Still plan to release tomorrow Pike 8.0.164 release candidate for your testing: https://pike.lysator.liu.se/pub/pike/beta/8.0.164/Pike-v8.0.164.tar.gz Windows build: https://pike.lysator.liu.se/pub/pike/beta/8.0.164/Pike-v8.0.164-win32-oldli… Changes since 8.0.162 (yesterday) -------------------------------------------------------------- * Reverted inclusion of Parser.Markdown * Ratelimiting (of sorts) of error messages from Filesystem.Monitor Regards, -- Peter Bortas, NSC

1 0

Pike 8 release candidate today
by Peter Bortas ＠ Pike developers forum 07 Feb '16

07 Feb '16

A release candidate for 8.0 will be tagged within 30min to test-feed to primarily the Windows build machinery. If there are any other fixes you want in let me know before 18:00 and I will do another pull before doing final builds. -- Peter Bortas

1 1

Re: Protocols.IRC unmaintained - want me to give it some TLC?
by Chris Angelico 07 Feb '16

07 Feb '16

On Sun, Feb 7, 2016 at 11:20 AM, Peter Bortas @ Pike developers forum <10353(a)lyskom.lysator.liu.se> wrote: > Please do. > > I have (after a bit of head-scratching) figured out how the key > management works. I think. Try it. Thank you, seems to be working! Much appreciated. Ran into a problem with the githelper hook using the 7.8/8.0 way of calling up Charset, so I stuck in a #if to support the 8.0/8.1 way as well. ChrisA

1 0

Protocols.IRC unmaintained - want me to give it some TLC?
by Chris Angelico 07 Feb '16

07 Feb '16

The Protocols.IRC module basically hasn't been touched in years. I'm looking at making some use of it (building a Twitch.tv chatbot); want me to do up the module a bit while I'm at it (add docs and stuff, mainly)? I'm waiting on Grubba (or someone) to register my public key with the server, but other than that, happy to do a bit of documenting. ChrisA

2 1

Pike 8 release next weekend
by Peter Bortas 06 Feb '16

06 Feb '16

I'm aiming for a release of Pike 8 next weekend on Sunday the 7th. This is my current list of "blockers", please speak up if you have any others or if you have input on any of the existing: ** random() might now be really random (incompatible change) Will not be backed out. We should provide a pseudo-random() that is seedable, and preferably does not have a name that includes "random". I don't want to hold the release for that unless someone has a real application that needs it or have a finished implementation with a well thought out API by next Saturday. ** OpenBSD compile failures (regression) I will not hold the release for this unless someone with a OpenBSD machine tells me that they are actively working on it. ** Windows support libraries are old (not a regression, just regrettable) Will make an effort to build new versions of GMP och Nettle, and see if we can bundle a newer GTK release. Since this is not a regression I will not hold back a release for it though. Cheers, -- Peter Bortas, NSC

2 3

Change of public key
by Chris Angelico 28 Jan '16

28 Jan '16

I've just suffered a major hard drive meltdown, which wiped out one of my private keys. This is not a compromise, so there's no panic; but it means I've lost access to anything that it granted. Attached is my new public key, and a GPG signature so you know it's mine. Sorry for the hassle... welcome to security, where stuff sometimes goes wrong :) ChrisA

1 0

keypair loop
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 25 Jan '16

25 Jan '16

>The PIKE_MAPPING_KEYPAIR_LOOP is not enabled by default. Is this work >in progress? Is it worth keeping? Yes. It would allow for a more static traversal order for mappings.

1 0

Over-eager optimization in Pike 8.1
by Chris Angelico 12 Jan '16

12 Jan '16

int main() { array(int) positions=({4,3}); int pos=1; array unrolled=({}); foreach (positions, int nextpos) { write("Extending to %d\n",nextpos); for (;pos<=nextpos;++pos) unrolled+=({"Spam"}); } } The basic concept is that it should unroll an array of counts into individual entries. (Think run-length decoding or something.) There's a bug in it, that the second position is lower than the first. A naive implementation would simply note that pos isn't less than or equal to nextpos, ergo it should skip the loop altogether; and in Pike 7.8.352, this is what happens. In Pike 8.1 current, this results in an infinite loop that allocates gobs of memory. I tried to bisect to find the problem, but it's been there for a very long time, and a lot of the old builds won't compile on my system for some reason. ChrisA

3 2

lookup of named inherits with modules
by Arne Goedeke 12 Jan '16

12 Jan '16

The following artificial example generates a syntax error. What is the correct syntax? main.pike: class B { inherit FOO.A; void f() { FOO.A::f(); } } FOO.pmod: class A { void f() {} } Arne

2 1

Pike 8: pgsql doesn't disconnect when destructed
by Jeff Hungerford 11 Jan '16

11 Jan '16

Greetings, I've been testing Pike 8.0.147, and I've noticed that pgsql connections to postgres don't appear to disconnect when the objects are destroyed, they linger until pike exits. For example, when I run: int main() { object foo = Sql.Sql("pgsql://hungerf3@localhost:5432/hungerf3"); destruct(foo); gc(); sleep(60); } I still see an active connection in the pg_stat_activity view in the database until the script exits. The same script drops the database connection as soon as the object is destructed in 7.8.941 In both cases, I've been testing against Postgres 9.5 on FreeBSD. -Jeff

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