June 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] squeaksource is down (again ...)

by Geert Claes

Down again now... http://forum.world.st/file/n2268082/Squeaksource_down_again.png -- View this message in context: http://forum.world.st/squeaksource-is-down-again-tp2266603p2268082.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 25, 2010

Re: [Pharo-project] squeaksource is down (again ...)

by Geert Claes

Feature wise, I don't think SqueakSource's "Groups" is very useful, but I agree with the suggestion that it would be nice to have an integrated Issue Tracking (maybe Gjallar?) system (even an integrated Wiki/CMS). Looking at systems like Trac, it has proven to very successful. Looking at other online source code repositories is probably a good idea. BitBucket for example doens't use the term "project" but actually let's you add a "Repository" which terminology wise blends better with Pharo as well. I am happy to help out a bit from a usability design point of view. -- View this message in context: http://forum.world.st/squeaksource-is-down-again-tp2266603p2268069.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 25, 2010

Re: [Pharo-project] squeaksource is down (again ...)

by laurent laffont

On Fri, Jun 25, 2010 at 8:21 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > restart a nice application with a nice model. > Squeaksource was developed literally a couple of days. I remember when they > said monday "wait until friday" :) > What should be in ? I'm thinking of: Important: - fork / merge tracking (like github, so we can contribute to a package even if we don't have write access on main repository) - scriptable API (automate patch integration from PharoInbox, image building) - easy mirroring Would be nice: - documentation integration (automatically display HelpSystem doc. on web page) - issues tracking + project management Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/ > > Stef > > On Jun 25, 2010, at 12:33 AM, Richard Durr wrote: > > > What could such a solution be? > > > > On Thu, Jun 24, 2010 at 7:52 PM, Lukas Renggli <renggli(a)gmail.com> > wrote: > >> I think it is the time to let squeaksource.com die. After all it > >> served its purpose and made Monticello what it is today: the standard > >> code and versioning system of Smalltalk fully supported by Pharo, > >> Squeak, and GemStone; and partially by Cincom Smalltalk and VA > >> Smalltalk. > >> > >> I doubt that something can rescue squeaksource.com as it is now. Any > >> change means an incredible investment of work and the people that set > >> it up about 7 years ago are moving elsewhere. > >> > >> I think somebody should jump in and provide a much better solution. > >> > >> Lukas > >> > >> On 24 June 2010 14:52, Philippe Marschall > >> <philippe.marschall(a)netcetera.ch> wrote: > >>> On 06/24/2010 12:17 PM, GÃ¶ran Krampe wrote: > >>>> On 06/24/2010 10:04 AM, laurent laffont wrote: > >>>>> What can be done / how can we help / what's needed to improve > >>>>> squeaksource uptime ? > >>>> > >>>> I am not sure how SS is being deployed but one option might be to move > >>>> to another web server as a frontend and use FastCGI or SimpleCGI > >>>> (Blackfoot on SM). > >>> > >>> Believe me when I tell you, the web server is the least of the issues. > >>> What mostly happens are Socket/Semaphore related issues, eg. a thousand > >>> Processes hanging on the same Semaphore. > >>> > >>> What could be done is moving to an up to date image/vm but this is a > bit > >>> of work. > >>> > >>> Cheers > >>> Philippe > >>> > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project(a)lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> > >> > >> -- > >> Lukas Renggli > >> www.lukas-renggli.ch > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 25, 2010

Re: [Pharo-project] squeaksource is down (again ...)

by Geert Claes

Maybe this is the time to re-visit/build upon SourceTalk ... but for Monticello 1? -- View this message in context: http://forum.world.st/squeaksource-is-down-again-tp2266603p2268039.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 25, 2010

Re: [Pharo-project] squeaksource is down (again ...)

by StÃ©phane Ducasse

restart a nice application with a nice model. Squeaksource was developed literally a couple of days. I remember when they said monday "wait until friday" :) Stef On Jun 25, 2010, at 12:33 AM, Richard Durr wrote: > What could such a solution be? > > On Thu, Jun 24, 2010 at 7:52 PM, Lukas Renggli <renggli(a)gmail.com> wrote: >> I think it is the time to let squeaksource.com die. After all it >> served its purpose and made Monticello what it is today: the standard >> code and versioning system of Smalltalk fully supported by Pharo, >> Squeak, and GemStone; and partially by Cincom Smalltalk and VA >> Smalltalk. >> >> I doubt that something can rescue squeaksource.com as it is now. Any >> change means an incredible investment of work and the people that set >> it up about 7 years ago are moving elsewhere. >> >> I think somebody should jump in and provide a much better solution. >> >> Lukas >> >> On 24 June 2010 14:52, Philippe Marschall >> <philippe.marschall(a)netcetera.ch> wrote: >>> On 06/24/2010 12:17 PM, GÃ¶ran Krampe wrote: >>>> On 06/24/2010 10:04 AM, laurent laffont wrote: >>>>> What can be done / how can we help / what's needed to improve >>>>> squeaksource uptime ? >>>> >>>> I am not sure how SS is being deployed but one option might be to move >>>> to another web server as a frontend and use FastCGI or SimpleCGI >>>> (Blackfoot on SM). >>> >>> Believe me when I tell you, the web server is the least of the issues. >>> What mostly happens are Socket/Semaphore related issues, eg. a thousand >>> Processes hanging on the same Semaphore. >>> >>> What could be done is moving to an up to date image/vm but this is a bit >>> of work. >>> >>> Cheers >>> Philippe >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 25, 2010

[Pharo-project] OSCog updated

by Eliot Miranda

Hi All, I've updated http://ftp.squeak.org/Cog with new source, OpenSourceCog-oscog.16.tar.gz/VMMaker-oscog.16.mcz that fixes the three issues people have found: Nicholas' crash on loading SUnit.dtl.?? which was a very nasty bug in the GC'ing of some trace logs the VM maintains. It was down to a difference between Smalltalk's \\ and C's %, specifically that the latter can answer something of different sign to the modulus. The failure of GeneratorTest, superficially due to cannotReturn: crashes, but fundamentally to do with inter-page returns to frames within the page not preserving the frames above, which can be in use due to co-routining (swapSender: usage). I hope this will fix Seaside on Cog. Please let me know. Crashes due to temps occurring in very simple blocks (that Cog compiles frameless) e.g. [ | b | 5 ] value. HTH Eliot

June 24, 2010

Re: [Pharo-project] squeaksource is down (again ...)

by Richard Durr

What could such a solution be? On Thu, Jun 24, 2010 at 7:52 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > I think it is the time to let squeaksource.com die. After all it > served its purpose and made Monticello what it is today: the standard > code and versioning system of Smalltalk fully supported by Pharo, > Squeak, and GemStone; and partially by Cincom Smalltalk and VA > Smalltalk. > > I doubt that something can rescue squeaksource.com as it is now. Any > change means an incredible investment of work and the people that set > it up about 7 years ago are moving elsewhere. > > I think somebody should jump in and provide a much better solution. > > Lukas > > On 24 June 2010 14:52, Philippe Marschall > <philippe.marschall(a)netcetera.ch> wrote: >> On 06/24/2010 12:17 PM, GÃ¶ran Krampe wrote: >>> On 06/24/2010 10:04 AM, laurent laffont wrote: >>>> What can be done / how can we help / what's needed to improve >>>> squeaksource uptime ? >>> >>> I am not sure how SS is being deployed but one option might be to move >>> to another web server as a frontend and use FastCGI or SimpleCGI >>> (Blackfoot on SM). >> >> Believe me when I tell you, the web server is the least of the issues. >> What mostly happens are Socket/Semaphore related issues, eg. a thousand >> Processes hanging on the same Semaphore. >> >> What could be done is moving to an up to date image/vm but this is a bit >> of work. >> >> Cheers >> Philippe >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 24, 2010

Re: [Pharo-project] Seaside app crashing - does it sound familiar?

by Schwab,Wilhelm K

Philippe, I got it going, and I might even understand why it failed :) I used SIXX to serialize some user data (a poor-man's access control list). Loading the "list" from SIXX output loads the data and the mutex; replacing the mutex with a new mutex seems to allow things to work. IIRC, this arises in Dolphin too. I have copied Masashi just in case that raises any alarms. If I am correct about this, I sent the image crashing head on into a defective mutex, so the vm might have been correct to squawk about nothing being available to run. Thanks! Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K [bschwab(a)anest.ufl.edu] Sent: Thursday, June 24, 2010 1:47 PM To: pharo-project(a)lists.gforge.inria.fr Cc: seaside(a)lists.squeakfoundation.org Subject: [Pharo-project] Seaside app crashing - does it sound familiar? Hello all, I am trying to pick up after a few months on a Seaside app. A lot has happened in that time, and I am not certain of its state, except to say that I recall seeing it display some pages. Now it's not working. At least some other Seaside apps are working, and going back to my 1.0 image, it is crashing with "scheduler could not find a runnable process." Are there any common mis-configurations or programming errors that can lead to that? I'll keep digging, but I wanted to post this just in case it's a known punishment for a common crime. Bill _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 24, 2010

Re: [Pharo-project] ConfigurationOfOSProcessCommandShell

by Schwab,Wilhelm K

Henry, Thanks for the quick response! My shameless hack appears to be covering for it, so I will probably just hold there. If only my torching Seaside app were as easily tamed :( It is very likely just a stupid mistake on my part. My one complaint about Seaside is that doing something stupid can lead to ugly meltdowns, I suspect due to continuations. I will ponder in the open whether this might be due to my ConnectionQueue changes, but then it would have to explain why only one app goes down in flames while others work as expected. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Henrik Johansen Sent: Thursday, June 24, 2010 1:10 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] ConfigurationOfOSProcessCommandShell On Jun 24, 2010, at 3:33 07AM, Henrik Sperre Johansen wrote: > On 24.06.2010 02:41, Henrik Sperre Johansen wrote: >> On 23.06.2010 23:13, Schwab,Wilhelm K wrote: >>> To get going again, I hacked FileDirectory>>fileExists: to answer true when passed '/bin/sh' and suddenly I can pipe again, so there has been some kind of change in testing for files. >>> >>> >>> >>> -----Original Message----- >>> From: pharo-project-bounces(a)lists.gforge.inria.fr >>> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of >>> Schwab,Wilhelm K >>> Sent: Wednesday, June 23, 2010 4:05 PM >>> To: Pharo-project(a)lists.gforge.inria.fr >>> Subject: Re: [Pharo-project] ConfigurationOfOSProcessCommandShell >>> >>> PipeableOSProcess is broken on Linux. It appears to be because >>> >>> FileDirectory default fileExists:'/bin/sh' >>> >>> is returning false in 1.1. Any ideas? >>> >>> Bill >> > Difference between the links was sh was relative (sh -> dash), while my replacement was absolute (sh -> /bin/dash). > FilePlugin primitiveFileOpen opens the latter, but returns nil with the first, thus fileExists fails... > I wrote a small c program simply opening sh with fopen, and that > worked as expected, so there's probably an error in the wrapping > plugin code somewhere :/ > > Cheers, > Henry After some investigation, and a report to the dev list, it turned out a fix was already present in Cog :) If you need a VM working with 1.1 urgently, the modified file (for a 2202 build) is attached to the 4th post in http://forum.world.st/Unix-VM-alias-resolving-bug-td2267360.html#a2267360 . Cheers, Henry _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 24, 2010

Re: [Pharo-project] ConfigurationOfOSProcessCommandShell

by Henrik Johansen

On Jun 24, 2010, at 3:33 07AM, Henrik Sperre Johansen wrote: > On 24.06.2010 02:41, Henrik Sperre Johansen wrote: >> On 23.06.2010 23:13, Schwab,Wilhelm K wrote: >>> To get going again, I hacked FileDirectory>>fileExists: to answer true when passed '/bin/sh' and suddenly I can pipe again, so there has been some kind of change in testing for files. >>> >>> >>> >>> -----Original Message----- >>> From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K >>> Sent: Wednesday, June 23, 2010 4:05 PM >>> To: Pharo-project(a)lists.gforge.inria.fr >>> Subject: Re: [Pharo-project] ConfigurationOfOSProcessCommandShell >>> >>> PipeableOSProcess is broken on Linux. It appears to be because >>> >>> FileDirectory default fileExists:'/bin/sh' >>> >>> is returning false in 1.1. Any ideas? >>> >>> Bill >> > Difference between the links was sh was relative (sh -> dash), while my replacement was absolute (sh -> /bin/dash). > FilePlugin primitiveFileOpen opens the latter, but returns nil with the first, thus fileExists fails... > I wrote a small c program simply opening sh with fopen, and that worked as expected, so there's probably an error in the wrapping plugin code somewhere :/ > > Cheers, > Henry After some investigation, and a report to the dev list, it turned out a fix was already present in Cog :) If you need a VM working with 1.1 urgently, the modified file (for a 2202 build) is attached to the 4th post in http://forum.world.st/Unix-VM-alias-resolving-bug-td2267360.html#a2267360 . Cheers, Henry

June 24, 2010