January 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo issues on Google

by StÃ©phane Ducasse

Me too I had to restart safari. Stef On Jan 17, 2011, at 12:20 PM, Gary Chambers wrote: > IFor that url I get: > > > Google Error > > Server Error > > The server encountered an error and could not complete your request. > If the problem persists, please report your problem and mention this error message and the query that caused it. > > > > Regards, Gary > > ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Saturday, January 15, 2011 8:02 AM > Subject: Re: [Pharo-project] Pharo issues on Google > > >> what do you mean >> not sending notification? >> not sending mails? >> >> I get the list >> http://code.google.com/p/pharo/issues/list >> >> Stef >> On Jan 14, 2011, at 6:15 PM, Gary Chambers wrote: >> >>> Is the Pharo issues google site not working? >>> >>> Regards, Gary >> > >

Jan. 17, 2011

Re: [Pharo-project] 502 Bad Gateway

by Guillermo Polito

It seems squeaksource went down. It looks ok now( http://www.squeaksource.com) can you try again? Cheers, Guille On Sun, Jan 16, 2011 at 11:28 PM, HwaJong Oh <daliot.oh(a)gmail.com> wrote: > > I have this error while copying mcz file from my directory repo to > pharoInbox. > It was working well a minute ago. > > 'HTTP/1.1 502 Bad Gateway > Date: Mon, 17 Jan 2011 02:20:01 GMT > Server: Apache/1.3.41 (Darwin) mod_jk/1.2.6 mod_ssl/2.8.31 OpenSSL/0.9.7l > PHP/4.4.9 > Last-Modified: Fri, 22 Dec 2006 12:14:34 GMT > ETag: "ee86f-a68-458bcc2a" > Accept-Ranges: bytes > Content-Length: 2664 > Connection: close > Content-Type: text/html<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 > Strict//EN" > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> > > <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> > <head> > <link rel="stylesheet" type="text/css" href="/squeaksource/style.css" /> > <meta name="verify-v1" > content="aYJ5chz2x0fRQuxMBS4pW+Ikb7hgtaBsysf18Fbt3q8=" /> > <title>SqueakSource</title> > </head> > > <body> > <div id="container"> > <div id="top"> > </div> > > <div id="sstoolbar"> > http://www.squeaksource.com/ Home > http://www.squeaksource.com/ Projects > http://www.squeaksource.com/ Tags > http://www.squeaksource.com/ Members > http://www.squeaksource.com/ Groups > http://www.squeaksource.com/ Help > </div> > > <div id="page"> > <div id="navigation"> > <div class="title"> > Actions > </div> > <div class="item"> > http://www.squeaksource.com/ Refresh > </div> > </div> > > <div id="contents"> > <h1>SqueakSource Down</h1> > > <p style="font-weight: bold; margin-left: 20px; margin-right: 220px; > line-height: 1.5em"> > SqueakSource is currently down. We are sorry for the > inconvenience and > working on the problem. In the meantime you can still commit > to a > directory repository on your disk and later copy the > versions to > SqueakSource.</p> > > <p>This service is brought to you for free: it is backed up daily. > Still, please make sure that you have your own proper backups and > note > that we cannot give any accessibility guarantees. However, if you > wish > you can set up your own SqueakSource server. It is self-hosted and > can > be downloaded from SqueakMap.</p> > > <p>Please report any problems or suggestions to the Squeak > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/squeak-dev > Mailing-List . Enjoy!</p> > > <p>We gratefully acknowledge the support of the > http://www.iam.unibe.ch/%7Escg/ Software Composition Group and > the http://www.unibe.ch/ University of Bern for hosting > this service.</p> > </div> > > <div id="bottom"> > <table width="100%" border="0" cellspacing="0" cellpadding="0"> > <tr> > <td align="left"> > http://validator.w3.org/check/referer XHTML > | http://jigsaw.w3.org/css-validator/check/referer CSS > </td> > <td align="right">It''s a sad day</td> > </tr> > </table> > </div> > </div> > </body> > </html> > ' > -- > View this message in context: > http://forum.world.st/502-Bad-Gateway-tp3220636p3220636.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

Jan. 17, 2011

Re: [Pharo-project] Issue 3542 in pharo: Add SmalltalkImage>>#gcBiasToGrow: and friends to core

by pharo＠googlecode.com

Updates: Cc: marianopeck renggli Comment #4 on issue 3542 by Torsten....(a)astares.de: Add SmalltalkImage>>#gcBiasToGrow: and friends to core http://code.google.com/p/pharo/issues/detail?id=3542 Added Mariano and Lukas to this issue, Mariano seems to have most commits on ImageForDevelopers and Lukas may be able to tell us where #initializeMemorySettingsProfileSeaside is best integrated into Seaside. Thanks in advance!

Jan. 17, 2011

[Pharo-project] [ANN 1.2] pre-build core 1.2#12308

by Marcus Denker

https://gforge.inria.fr/frs/download.php/28154/PharoCore-1.2beta-12308.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 17, 2011

Re: [Pharo-project] Issue 3542 in pharo: Add SmalltalkImage>>#gcBiasToGrow: and friends to core

by pharo＠googlecode.com

Updates: Status: Comment Comment #3 on issue 3542 by adrian.l...(a)gmail.com: Add SmalltalkImage>>#gcBiasToGrow: and friends to core http://code.google.com/p/pharo/issues/detail?id=3542 Thanks for the review, Torsten. Those are valid concerns. We can leave out #initializeMemorySettingsProfileSeaside and suggest to the Seaside folks to add this method as an extension. I included it in the changeset because in the Pharo-dev image it doesn't make sense as many people probably deploy with PharoCore. The important part of the change is to have #gcBiasToGrow: in core. Also, we should remove the moved methods from http://www.squeaksource.com/ImageForDevelopers.html. Is somebody actively maintaining this package?

Jan. 17, 2011

Re: [Pharo-project] Issue 3498 in pharo: remove:ifAbsent: in linked list leads to interruption/sync problems

by pharo＠googlecode.com

Updates: Status: Closed Comment #13 on issue 3498 by marcus.d...(a)gmail.com: remove:ifAbsent: in linked list leads to interruption/sync problems http://code.google.com/p/pharo/issues/detail?id=3498 12308

Jan. 17, 2011

[Pharo-project] [update 1.2] #12308

by Marcus Denker

12308 ----- Issue 3541: TextConverter should take into account iso Issue 3498: remove:ifAbsent: in linked list leads to interruption/sync problems -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 17, 2011

Re: [Pharo-project] Issue 3541 in pharo: TextConverter should take into account iso

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 3541 by marcus.d...(a)gmail.com: TextConverter should take into account iso http://code.google.com/p/pharo/issues/detail?id=3541 12308

Jan. 17, 2011

Re: [Pharo-project] Issue 3542 in pharo: Add SmalltalkImage>>#gcBiasToGrow: and friends to core

by pharo＠googlecode.com

Updates: Cc: stephane.ducasse Comment #2 on issue 3542 by Torsten....(a)astares.de: Add SmalltalkImage>>#gcBiasToGrow: and friends to core http://code.google.com/p/pharo/issues/detail?id=3542 So #12307 also adds #initializeMemorySettingsProfileSeaside to the core image? Why? Seaside is important, but I would like to see this in one of the "Seaside-Pharo" packages on the seaside, not in the core pharo image. Otherwise we will end up with #initializeMemorySettingsProfileMoose #initializeMemorySettingsProfileGlamour #initializeMemorySettingsProfileMyFavouriteApp ... Or is it just the name? And we should name it initializeMemorySettingsProfileForMostUseCases ;) Also take care: the changeset was from "Pharo-1.1-11411" and has recategorizations in it. Dont know if this has side effects on already recategorized/repackaged methods in SmalltalkImage.

Jan. 17, 2011

[Pharo-project] Was not able to update with #12304

by Torsten Bergmann

Looks like a Cog issue, I was able to reproduce it: When I download "PharoCore-1.2.zip" from https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/126/ (which is a Pharo 1.2 Core #12303 image) and I directly start the image with the latest Win32 Cog VM from Eliot then I'm not able to go through update #12304 via the update mechanism as I already wrote in [1]. I get this error: => ClassBuilder(Object)>>doesNotUnderstand: #reshapeClass:toSuper: When I use the standard VM I'm able to update correctly to the latest version pharo core 1.2 #12307 Maybe Eliot is able to reproduce and fix it. Until then I switch to standard VM. Thx Torsten [1] http://lists.gforge.inria.fr/pipermail/pharo-project/2011-January/039747.ht… -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

Jan. 17, 2011