- Pharo-dev - lists.pharo.org

[Pharo-project] cool to see pier, and other running on 1.3
by StÃ©phane Ducasse July 29, 2011

July 29, 2011

Hi lukas this is cool to see all your projects running on 1.3. I see that somewhere (tweet) but could not find it anymore (too many windows open and too much information). but this is cool. Stef

9 41

Re: [Pharo-project] [Pharo-users] 1.4 update is broken do not use it
by Marcus Denker July 29, 2011

July 29, 2011

On Jul 29, 2011, at 4:42 PM, Torsten Bergmann wrote: >> so now updating from https://gforge.inria.fr/frs/download.php/28827/Pharo-1.4-14065.zip > > Is this a core or a full image? If core (which one can use to update further) shouldnt this be reflected in the ZIP's name? In 1.4, there is only one image. This simplifies everything.... Marcus -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [Pharo-users] 1.4 update is broken do not use it
by Torsten Bergmann July 29, 2011

July 29, 2011

>so now updating from https://gforge.inria.fr/frs/download.php/28827/Pharo-1.4-14065.zip Is this a core or a full image? If core (which one can use to update further) shouldnt this be reflected in the ZIP's name? Thx T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

1 0

[Pharo-project] 1.4 update is broken do not use it
by StÃ©phane Ducasse July 29, 2011

July 29, 2011

Hi guys apparently (I suspect some changes we did with Sven I will check), the updates mechanism only download the latest of the issues and skips all the ones in between. So if you want to use 1.4 use for now https://gforge.inria.fr/frs/download.php/28827/Pharo-1.4-14065.zip stef

2 1

[Pharo-project] ConfigurationOf### in PharoKernel 1.4
by Adrien BARREAU July 29, 2011

July 29, 2011

Hi all, I'm triying to load some code (Coral) in the Pharo Kernel 1.4 image. Marcus told me to use the image with Gofer and Network. I suceeded to load the ConfigurationOfCoral package, but I can not load it. I tried to load another ConfigurationOf### and the result is the same, it raises an error on "ensureMetacello" method. Here is the error: 'retry with alternate repository failed: ''SubscriptOutOfBounds: 1''. I don't know what I can do about it. I tried to load Coral in the PharoKernel 1.4 Reload image, and the result is the same. Of course, on a Pharo 1.4 image, it works. Adrien.

1 0

[Pharo-project] [update 1.4] #14066
by StÃ©phane Ducasse July 29, 2011

July 29, 2011

14066 ----- - reverting old method newUpdates for now. Now looking for the bug in the previous code. Stef

1 0

[Pharo-project] [ANN] pre-build 1.4#14065
by Marcus Denker July 29, 2011

July 29, 2011

https://gforge.inria.fr/frs/download.php/28827/Pharo-1.4-14065.zip PLEASE NOTE To me it looks like there is a problem that 1.4 just loads the *last* update from the stream... http://code.google.com/p/pharo/issues/detail?id=4569 this needs to be checked / fixed before we can move on... (I build this by updating from 14025, which worked. 14044 it seems to just load the last update). Marcus -- Marcus Denker -- http://marcusdenker.de

2 2

[Pharo-project] new pre-build Core1.3#13291
by Marcus Denker July 29, 2011

July 29, 2011

... with the build servers not working, one done by hand: https://gforge.inria.fr/frs/download.php/28826/PharoCore-1.3-13291.zip Marcus -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 1.3] #13291
by Marcus Denker July 29, 2011

July 29, 2011

13291 ----- Issue 4561: Monticello GUI is broken -- Marcus Denker -- http://marcusdenker.de

1 0

Re: [Pharo-project] cool to see pier, and other running on 1.3
by Marcus Denker July 29, 2011

July 29, 2011

On Jul 29, 2011, at 11:57 AM, Mariano Martinez Peck wrote: > > > On Fri, Jul 29, 2011 at 11:51 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > >> Zinc can nicely play out the keep-alive. Kom doesn't support > >> keep-alive. With Swazoo a lot of requests fail if keep-alive is > >> enabled (so I disabled it). Details in the attachment. > > > > what is keep-alive? > > The server keeps the socket open after a request-response cycle and > allows clients (browsers) to reuse the same socket for multiple > requests. This is typically faster than to open a new socket for each > request. > In addition to not having to set up a new connection, the other thing that is a problem with short lived TCP request is TCP slow-start: http://en.wikipedia.org/wiki/Slow-start A new TCP connection "probes" by sending a little and then it slowly increases. If you use short-lived TCP connections, it can happen that you are never leaving the slow-start discovery phase. Marcus -- Marcus Denker -- http://marcusdenker.de

1 0