- Pharo-dev - lists.pharo.org

Problems with Penelope
by Davide Varvello June 3, 2013

June 3, 2013

Hi, http://bugs.pharo.org/issues returns Error 503 Davide -- View this message in context: http://forum.world.st/Problems-with-Penelope-tp4691333.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

1 0

about Announcement weak on: do:
by StÃ©phane Ducasse June 2, 2013

June 2, 2013

Hi igor after our discussions about the fact that we should not use weak with block, I checked and WeakSubscriptionBuilder>>on: anAnnouncementClass do: aValuable ^ self subscribe: anAnnouncementClass do: aValuable Does not look like raising error. Stef

3 3

Rubric screencast
by plantec June 1, 2013

June 1, 2013

Hi all, It shows how one can use user defined selection and icons to manage text parts. http://vimeo.com/67400546 cheers Alain

7 13

Re: [Pharo-dev] [Pharo-users] Pharo consultants
by Sven Van Caekenberghe June 1, 2013

June 1, 2013

On 01 Jun 2013, at 17:28, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Jun 1, 2013, at 10:42 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> Am 01.06.2013 um 08:10 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >>> Hi guys >>> >>> I think that we are doing a poor job selling ourselves. I think that the quality of our community is in >>> general excellent but we do not sell it. I think that we are not using well the association. >>> I think that this is REALLY important for a larger adoption of Pharo that the world >>> knows that we have excellent guys around that can consult. >>> >>> So what do you think? >>> I would use the association in a much clearer way. >> >> I think you need to elaborate here. On this level of detail the only answer could be: good idea! I cannot see what you have on your mind when you like to use the association in a clearer way. > > I mean that we could use the association as a show room for talented person > "selling" their expertise :) Yes, we should do something like that - we need to think about the amount/kind of information we want to place in the 'fiche' describing each consultant. It should be enough, but not too much either. >> I would like to have consultancy for consultants. I mean I read that sometimes that developers are just too shy to sell services with smalltalk or do not dare to introduce it to their IT. There should be an instance encouraging those people or be just an address to target questions to. > > I would like to show to the world that if they start business around Pharo they can find experts. >> >> Norbert >> >> > >

1 0

Pharo 3.0 software update corrupts Pharo
by dimitris chloupis June 1, 2013

June 1, 2013

I created a bug report -> https://pharo.fogbugz.com/default.asp?10832#78704 Also I wanted to ask , how to browse the bug reports I have created ? I cant find it.

4 3

CI down
by Camillo Bruni June 1, 2013

June 1, 2013

It seems like the cloudstack issues emerging yesterday are continuing. => All slaves are offline (pharo, pharo-contribution, rmod) We have to wait until monday to get this resolved.

1 0

Fwd: Vm-dev Digest, Vol 83, Issue 46
by Max Leske June 1, 2013

June 1, 2013

Begin forwarded message: > On Fri, May 31, 2013 at 1:11 PM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > >> >> >> On Fri, May 31, 2013 at 12:54 AM, Max Leske <maxleske(a)gmail.com> wrote: >> >>> >>> Bump. >>> >>> Doesn't anybody feel that corrupt blocks are a problem? IMHO that's >>> something that should *never* happen. >>> >> >> But what's happening here is that the Fuel serializer is allowing the >> serialization of blocks without serializing their outer context and method, >> and later the reconstruction of blocks against the *wrong* version of a >> method. This is a Fuel bug. IMO the right solution is for Fuel to >> serialize the method of the block, and on reconstruction replace the >> reconstructed method with the method in the system iff the reconstructed >> method is the same as that in the system, but substitute the recinstructed >> method if it differs from the system's version (or of course if the >> system;s version is missing). this mimics the system's behaviour with >> unbound methods, where e.g. a block holds onto a method and the code of a >> class is recompiled, resulting iun that block holding onto an unbound >> method. >> > > Sorry, "without serializing their outer context and method" is wrong; > "without serializing their method"

1 0

[update 3.0] #30178
by Marcus Denker May 31, 2013

May 31, 2013

30178 ----- 10714 General update https://pharo.fogbugz.com/f/cases/10714 10816 ReleaseTest>>#testUndeclared fails in Opal RegressionTests https://pharo.fogbugz.com/f/cases/10816 10815 failing in Opal regressionTEst: DebuggerTest.testBasic https://pharo.fogbugz.com/f/cases/10815 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/ToolsTest-MarcusDenker.denker… http://smalltalkhub.com/mc/Pharo/Pharo30/main/NewList-MarcusDenker.44.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Base-MarcusDenker.5.d…

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr May 31, 2013

May 31, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=wi… 3 regressions found. FuelTests.FLMethodContextSerializationTest.testDoIt Tests.Release.ReleaseTest.testObsoleteBehaviors Tests.Release.ReleaseTest.testObsoleteClasses

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr May 31, 2013

May 31, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=ma… 3 regressions found. FuelTests.FLMethodContextSerializationTest.testDoIt Tests.Release.ReleaseTest.testObsoleteBehaviors Tests.Release.ReleaseTest.testObsoleteClasses

1 0