Pike-devel August 2012

pike-devel@lists.lysator.liu.se

6 participants
12 discussions

debugger opcodes
by Bill Welliver 30 Oct '14

30 Oct '14

I noticed that folks have been working on code generation lately. Any chance it might be possible to implement some of the opcodes required to get debugging working (step, break, etc)? I seem to recall someone indicating it wasn't a terribly difficult task, but it's clearly beyond my understanding of the problem. Bill

4 6

Sql.pgsql behavior in case of errors
by aldem-pikedev＠aldem.net 21 Aug '14

21 Aug '14

Hi everyone, I am preparing to use Postgres in my app, found the following strange behavior: ---snip--- Sql.Sql db = Sql.Sql("pgsql://localhost", "test", "test", "test"); db->query("BEGIN"); db->query("INSERT INTO requests (SvTrId) VALUES ('lala')"); catch(db->query("INSERT INTO requests (SvTrId) VALUES ('lala')")); db->query("INSERT INTO requests (SvTrId) VALUES ('juju')"); db->query("ROLLBACK"); ---snip--- Database is opened, row with 'lala' is inserted, second query (obviously) fails as SvTrId is the primary key, but row with 'juju' is inserted *and* appears in the database - i.e. the transaction is *committed*! Studying source code show, that once error is encounter, session is reset, i.e. running transaction is rolled back, everything is closed, temporary tables are deleted and session variables are reset as well, and after that, the next statement(s) will be committed immediately, as there is no active transaction. In my opinion, this is not exactly correct behavior when statement fails, as session still may be needed (especially temporary tables, open cursors etc). Im some cases, this is perfectly normal when SQL statement fails, especially in SERIALIZED transaction isolation level, and it would be more practical to leave the decision as of what to do to the application. Yes, this is true that it is impossible to continue executing statements in failed transaction, but temporary tables etc. may still be needed. Also, silent reconnection is not a good idea too - when there are many transactional statements are executed - it would be nice to have an option to modify this behavior. Best regards, /Alexander

5 6

7.6 release
by H. William Welliver III 30 Aug '12

30 Aug '12

Is there any chance that we could also do a 7.6 maintenance release? Some folks are still using 7.6 and there have been a number of useful bug fixes that would be nice to have available. Any thoughts? Bill

1 0

pike.ida.liu.se
by H. William Welliver III 30 Aug '12

30 Aug '12

I tried updating the website at ida, but can't commit due to EOM error. Can someone look into that? I updated the lysator site, but I don't have shell access, so the files are only on the IDA machine. Bill

1 1

Re: 7.8.700 feedback
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 27 Aug '12

27 Aug '12

To celebrate this, I uploaded a couple more binary dists to the beta directory: Linux (32 and 64 bit) and Solaris 11.

2 1

7.8.700 feedback
by Bill Welliver 26 Aug '12

26 Aug '12

Does anyone have any feedback on 7.8.700? So far things look good on the systems I've tried it on. If I don't hear about any show-stoppers, I'll declare success on Friday. Best, Bill

4 3

New Pike beta: 7.8.700
by Bill Welliver 16 Aug '12

16 Aug '12

In light of the recent problems compiling Pike on NT, I've prepared a new release of 7.8 that hopefully resolves this problem. http://pike.ida.liu.se/download/pub/pike/beta/7.8.700/ As always, please feel free to download and report any problems. Bill

5 5

Re: New 7.8 release candidate: 7.8.696
by Tobias S. Josefowitz 07 Aug '12

07 Aug '12

On Tue, Aug 7, 2012 at 4:05 PM, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > Should anything listen on port 80? pike-git is just for the git > repositories so it should listen on port 9418 for anonymous access and > port 22 for authenticated access, yes? For the general picture, no clue. But the http://pike-git.lysator.liu.se/pike-overlay.xml mentioned at https://github.com/pikelang/pike-overlay and on the pike forum a long time ago used to be retrievable.

1 0

Re: New 7.8 release candidate: 7.8.696
by Tobias S. Josefowitz 07 Aug '12

07 Aug '12

On Thu, Jul 19, 2012 at 11:35 PM, Henrik Grubbström (Lysator) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > Great. I've now added a corresponding ebuild to the pike overlay for Gentoo. While trying to get http://pike-git.lysator.liu.se/pike-overlay.xml I noticed that currently nothing seems to listen on port 80. Tobi

2 1

possible blocker in 7.8.696
by H. William Welliver III 06 Aug '12

06 Aug '12

I was doing some testing of external modules last week and was having problems. At the time I chalked it up to being a corrupt build environment, but now I'm not so sure: The problem is that installation of an external module happens only after a successful verification, and it appears that the verify target is broken when using pike -x module. It's possible that this has been broken for a long time in 7.8, as 7.8.352 also has the same problem. Basically, in 7.6, verify called $(RUNPIKE), which was passed in by the external pike process. In 7.8 (specifically commit 385f54c91 by mast back in 2006 (!)), that's changed to $(FINAL_PIKE), which isn't, and it gets generated using the pike in the original build directory. I'm just not sure how to best fix the problem. Probably the best approach would be to modify pike -x module to also pass FINAL_PIKE with the same value. Honestly, I don't know how this got past me for so long. Any thoughts? Bill

3 3

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 2012