- Pharo-dev - lists.pharo.org

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/./Run=run%201,VM=vm,label=win… 1 regressions found. KernelTests.Classes.ClassDescriptionTest.testUnCategorizedMethods

July 1, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/./Run=run%201,VM=vm,label=lin… 1 regressions found. KernelTests.Classes.ClassDescriptionTest.testUnCategorizedMethods

July 1, 2013

Jenkins build became unstable: Pharo-2.0-Tests Â» run 1,vm,linux #254

by no-reply＠ci.inria.fr

See <https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/./Run=run%201,VM=vm,label=lin…>

July 1, 2013

Re: [Pharo-dev] [ANN] SS3 the canary site

by Tobias Pape

Am 01.07.2013 um 12:03 schrieb Stephan Eggermont <stephan(a)stack.nl>: > That site is fast! Well done, Tobias. > Good new features: package history is nice, and browsing code too. Hehe, those aren't new features, I think they are just more accessible now with the icons in the action bar. > > When browsing SqueakSource-Core-topa.99.mcz I noticed > there is supposed to be an extension made to Color, but I can't select it. yes, because it is on the class side. (sadly, you have to guess that and I currently do not know a way around. would look better on Squeak, tho) > With GRPlatform it is not clear if I'm looking at instance or class side. I made a better indication of what is selected :) best -Tobias

July 1, 2013

Re: [Pharo-dev] How do can we set up a crowdsourcing for pharo

by Norbert Hartl

Am 01.07.2013 um 14:47 schrieb Stephan Eggermont <stephan(a)stack.nl>: > Esteban wrote: >> 512 GB is "reasonable" maximum for a single threaded app? Certainly it >> is "reasonable" high! :-) > > Engineering is about trade-offs. 10K euro's: ram, or engineering time. > >> Altough I think 4GB might be small, for me it is better to think about >> scaling out, instead of up. > > Latency & bandwidth are no solved problems, AFAIK. > As long as we connect images through HTTP, the amount of copying > involved is going to seriously affect scalability. There is a reason > Gemstone uses shared pages > GemStone uses a shared page cache in order to avoid disk read/writes. It is only a cache and coordinator for everything read/write that needs to have access to disks. Well, it coordinates transactions as well to have a consistent set of pages in a concurrent environment. Each client in the shared memory situation still copies all of the data needed into its private memory section. Apart from that I think the use case dictates the best approach. For a web application or any application that has low memory profile per process but highly concurrent usage horizontal scaling is much easier. A few bucks put into can give some good results. In your use case it is completely different because you operate with one application on a huge graph. In this scenario the copying would be my smallest problem. I first would like to find a reliable way to manage a graph over multiple images :) In this case scaling vertical is most of the time the only way to go. Norbert

July 1, 2013

Re: [Pharo-dev] SmalltalkHub upgrade!

by Nicolas Petton

we could, but Helios is supposed to be an environment, not just a code browser. I'll see. Nico On Jul 1, 2013, at 3:20 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > but can we reuse Helios as the SmalltalkHub mcz browser? -- Nicolas Petton http://www.nicolas-petton.fr

July 1, 2013

Re: [Pharo-dev] How do can we set up a crowdsourcing for pharo

by Igor Stasenko

On 1 July 2013 14:47, Stephan Eggermont <stephan(a)stack.nl> wrote: > > Latency & bandwidth are no solved problems, AFAIK. > As long as we connect images through HTTP, the amount of copying > involved is going to seriously affect scalability. There is a reason > Gemstone uses shared pages > :) +1000 people often forget about it.. especially today in era of horizontal scaling (since vertical scaling hit the wall of physical limits don't works anymore). > Stephan > > > -- Best regards, Igor Stasenko.

July 1, 2013

Re: [Pharo-dev] SmalltalkHub upgrade!

by Damien Cassou

On Mon, Jul 1, 2013 at 9:17 AM, Nicolas Petton <petton.nicolas(a)gmail.com> wrote: > > Helios will be shipped with the next release of Amber. The stepping debugger won't make it into the release though, it's not ready yet. but can we reuse Helios as the SmalltalkHub mcz browser? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

July 1, 2013

Re: [Pharo-dev] WhatsUp from: 2013-07-01 until: 2013-07-14

by Stephan Eggermont

### Here's what I've been up to since the last WhatsUp: - Made some progress with Diego parsing Delphi code with PetitDelphi, units, classes, methods http://farm6.staticflickr.com/5539/9148484341_0405d8a261_o.png http://farm3.staticflickr.com/2829/9148515659_788742e646_o.png and forms http://farm4.staticflickr.com/3723/9184232826_fff1e2cffc_o.png - ran out of memory a few times uninterruptibly, so took a look at 10569 ### What's next, until 2013-07-14 (*): Parsing more of Delphi Help release Moose 4.8 Help Dusty with LightHouse issue tracker

July 1, 2013

Re: [Pharo-dev] WhatsUp from: 2013-07-01 until: 2013-07-14

by Guillermo Polito

On Mon, Jul 1, 2013 at 7:00 AM, <seaside(a)rmod.lille.inria.fr> wrote: > Hi! We're sending this automatic email twice a month, to give the > community an opportunity to easily know what's happening and to coordinate > efforts. Just answer informally, and feel free to spawn discussions > thereafter! > > ### Here's what I've been up to since the last WhatsUp: > > - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS > Creating very simple (but not yet perfect :) jobs on jenkins for benchmarking and vm acceptance test: - https://ci.inria.fr/pharo/view/VM/job/PharoVM-AcceptanceTest/ - https://ci.inria.fr/pharo/view/VM/job/PharoVM-Benchmarks/ Fixing some quick easy stuff in pharo sprint > ### What's next, until 2013-07-14 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION > This week vacations, but I'll do something around the real pharo bootstrap ;) > > (*) we'll be expecting results by then ;) > >

July 1, 2013