- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30465 Home: https://github.com/pharo-project/pharo-core

Oct. 9, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=wi… 2 regressions found. Zinc.Tests.ZnServerTests.testEntityTooLarge Zinc.Tests.ZnServerTests.testHeaderLineTooLong

Oct. 9, 2013

Re: [Pharo-dev] [pharo-project/pharo-core] 4ac391: 30464

by Esteban Lorenzano

so cool this :) is super cool how now we can track changes and even comment on them... now I need to modify the integration process so we do not produce so much "garbage methods", but well... with a bit of time... Esteban On Oct 9, 2013, at 8:17 AM, GitHub <noreply(a)github.com> wrote: > Branch: refs/heads/3.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 4ac39149fd226cfce8204908aeb9a8212a912832 > https://github.com/pharo-project/pharo-core/commit/4ac39149fd226cfce8204908… > Author: Jenkins Build Server <board(a)pharo-project.org> > Date: 2013-10-08 (Tue, 08 Oct 2013) > > Changed paths: > R Polymorph-Widgets-Themes.package/MorphicUIManager.class/instance/ui requests/messageNames_inMorphicWindowWithInitialSearchString_.st > R Polymorph-Widgets-Themes.package/MorphicUIManager.class/instance/ui requests/messageSet_inMorphicWindowLabeled_.st > A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script119.st > A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30464.st > M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st > A Spec-Tools-VersionBrowser.package/NewVersionBrowser.class/class/protocol/browseVersionsForClass_selector_.st > R Tools-Base.package/AbstractTool.class/instance/class/browseCommentVersionsOf_.st > R Tools-Changes.package/ClassCommentVersionsBrowser.class/README.md > R Tools-Changes.package/ClassCommentVersionsBrowser.class/class/instance creation/browseCommentOf_.st > R Tools-Changes.package/ClassCommentVersionsBrowser.class/class/menu/classCommentVersionsListMenu_.st > R Tools-Changes.package/ClassCommentVersionsBrowser.class/class/utilities/commentRecordsOf_.st > R Tools-Changes.package/ClassCommentVersionsBrowser.class/class/utilities/timeStampFor_class_reverseOrdinal_.st > R Tools-Changes.package/ClassCommentVersionsBrowser.class/class/window color/patchworkUIThemeColor.st > R Tools-Changes.package/ClassCommentVersionsBrowser.class/definition.st > R Tools-Changes.package/ClassCommentVersionsBrowser.class/instance/basic function/diffedVersionContents.st > R Tools-Changes.package/ClassCommentVersionsBrowser.class/instance/basic function/reformulateList.st > R Tools-Changes.package/ClassCommentVersionsBrowser.class/instance/basic function/scanVersionsOf_.st > R Tools-Changes.package/ClassCommentVersionsBrowser.class/instance/basic function/updateListsAndCodeIn_.st > R Tools-Changes.package/ClassCommentVersionsBrowser.class/instance/menu/compareToCurrentVersion.st > R Tools-Changes.package/ClassCommentVersionsBrowser.class/instance/menu/offerVersionsHelp.st > R Tools-Changes.package/ClassCommentVersionsBrowser.class/instance/menu/versionsMenu_.st > R Tools-Changes.package/ClassCommentVersionsBrowser.class/instance/misc/classCommentIndicated.st > R Tools-Changes.package/ClassCommentVersionsBrowser.class/instance/misc/contentsSymbolQuints.st > R Tools-Changes.package/ClassCommentVersionsBrowser.class/instance/misc/priorSourceOrNil.st > R Tools-Changes.package/ClassCommentVersionsBrowser.class/instance/misc/selectedClass.st > R Tools-Changes.package/ClassCommentVersionsBrowser.class/instance/shout/shoutAboutToStyle_.st > M Tools.package/extension/StringHolder/instance/browseVersions.st > > Log Message: > ----------- > 30464 > 11822 remove ClassCommentVersionBrowser > https://pharo.fogbugz.com/f/cases/11822 > > 11824 NewVersionBrowser: add #browseVersionsForClass: selector: > https://pharo.fogbugz.com/f/cases/11824 > > 11823 remove unneded builder methods (messagenames, messageset) from MorphicUIManager > https://pharo.fogbugz.com/f/cases/11823 > > http://files.pharo.org/image/30/30464.zip > > >

Oct. 9, 2013

Re: [Pharo-dev] How to delete an obsolete class ?

by Pavel Krivanek

You need to check if it still does have some instances and kill them. Then find and remove all references to the class. SystemNavigation default obsoleteClasses. SystemNavigation default obsoleteClasses collect: #allSubInstances. SystemNavigation default obsoleteClasses first allSubInstances first pointersTo. etc... Good hunt -- Pavel 2013/10/9 Olivier Auverlot <olivier.auverlot(a)gmail.com>: > Hi, > > In my project, my code has a strange behavior when I'm reading all subclasses of an another class. > > The following code must visit all the subclasses of PVEStatus but I get a bad result. > > PVEStatus allSubclasses > do: [ :statusDatatype | > (aRawStatus at: 'type') = statusDatatype type > ifTrue: [ ^ statusDatatype getStatus: aRawStatus callback: self ] ] > > The answer contains #AnObsoletePVENodeStatus and this class doesn't exist. She doesn't appear in the class browser. I suppose that it's a rest of refactoring. How can I delete this obsolete class ? > > Best regards > Olivier ;-) > > >

Oct. 9, 2013

Re: [Pharo-dev] external semaphoresâ¦again

by Igor Stasenko

On 8 October 2013 22:03, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Igor, > > > On Tue, Oct 8, 2013 at 2:27 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> >> >> >> On 7 October 2013 18:36, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> >>> Am 07.10.2013 um 16:36 schrieb Igor Stasenko <siguctua(a)gmail.com>: >>> >>> 1 thing. >>> >>> can you tell me what given expression yields for your VM/image: >>> >>> Smalltalk vm maxExternalSemaphores >>> >>> (if it gives you number less than 10000000 then i think i know what is >>> your problem :) >>> >>> It is 10000000 >>> >>> What would be the problem if it would be smaller? >>> >>> >> that just means your VM don't have external object size cap. >> I changed the implementation to not have hard limit (the arbitrary large >> number >> is there just to be "compatible" with previous implementation). >> > > If you've really done this why haven't you pushed changes back to me? You > think I like the limit ?!? ;-). But is your new implementation lock-free? > I went to some lengths to make sure that the Cog implementation is > thread-safe, by making signalling lock-free. But making it lock-free while > allowing growing was too much work. If your new implementation isn't > lock-free and/or isn't thread-safe then IMO the cure is worse than the > disease, because signals can get lost and that's much harder to diagnose > than deal with a limit that can only be set at startup. > > I understand your concerns. And inviting you to verify my implementation. It should be lock-free and thread-safe. All changes are in single file, so you can just take it and replace existing one.. https://github.com/pharo-project/pharo-vm/blob/master/platforms/Cross/vm/sq… should be easy to pick up for you. > If you don't remember, in short, i changed the way to it works, by accumulating signals into static-sized buffer, which then flushed upon each interrupt. As long as time between two interrupts remain relatively small, it is highly improbable that this buffer will be overrun. -- Best regards, Igor Stasenko.

Oct. 9, 2013

How to delete an obsolete class ?

by Olivier Auverlot

Hi, In my project, my code has a strange behavior when I'm reading all subclasses of an another class. The following code must visit all the subclasses of PVEStatus but I get a bad result. PVEStatus allSubclasses do: [ :statusDatatype | (aRawStatus at: 'type') = statusDatatype type ifTrue: [ ^ statusDatatype getStatus: aRawStatus callback: self ] ] The answer contains #AnObsoletePVENodeStatus and this class doesn't exist. She doesn't appear in the class browser. I suppose that it's a rest of refactoring. How can I delete this obsolete class ? Best regards Olivier ;-)

Oct. 9, 2013

Re: [Pharo-dev] Please try to reproduce this bug

by Damien Cassou

On Tue, Oct 8, 2013 at 11:40 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > BTW, I had issues w/ ppa this week end during a Hackathon. I wanted my > teammate to install pharo on his Wheezy 7 Debian and it failed. what did you try? If you tried my PPA, then this was a bad idea. The PPA is for Ubuntu only. If someone wants to push Pharo to Debian, I can help. > Now, we had to enable multiarch to get things running. Pretty out of reach > for basic users. multiarch is enabled by default on Debian. And I can't imagine someone using Debian be named a "basic user" :-). > As I had to put stuff on a Wheezy 7 server down the line, the get.pharo.org > thing worked better as I had no admin rights. For sure! -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Oct. 9, 2013

Re: [Pharo-dev] Metacello preview in Pharo 2.0

by StÃ©phane Ducasse

> Hi guys, > > because I had problems with Metacello for loading > ConfigurationOfPierVoyage in Pharo 2.0, I tried Metacello Preview > following an advice from Dale. Metacello Preview worked perfectly for > my complex use case. It looks like the Metacello embedded in Pharo 2.0 > is quite buggy. Dale proposes us to include Metacello Preview in Pharo > 2.0 so we don't run into these bugs anymore. > > What do you think? lot of work from what we saw. It took us a lot of time to get Preview in 3.0 > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

Oct. 9, 2013

Re: [Pharo-dev] Monticello requiring network access to save a package in a local repository?

by phil＠highoctane.be

Here is the preference for doing just that: http://www.smalltalkhub.com/#!/~philippeback/HOExtras/packages/Settings-Met… In fact, I noticed there was no Settings-Metacello and I created one, along with that single pref in it. Maybe will be useful for future things The metacelloPlatformAttributes has been changed like this and put in a *settings-metacello protocol instead of being in "miscellaneous". metacelloPlatformAttributes "Returns the tags for the conditional platform loading in Metacello. Pay attention the order is important: from most to least general." "For release integrators, we should not have #'pharo1.3x' **and** #'pharo1.4.x'" ^ SmalltalkImage Pharo2Compatible ifTrue: [ #(#squeakCommon #pharo #'pharo2.x' #'pharo2.0.x') ] ifFalse: [ #(#squeakCommon #pharo #'pharo3.x' #'pharo3.0.x') ] . Feel free to integrate :-) Phil

Oct. 9, 2013

Metacello preview in Pharo 2.0

by Damien Cassou

Hi guys, because I had problems with Metacello for loading ConfigurationOfPierVoyage in Pharo 2.0, I tried Metacello Preview following an advice from Dale. Metacello Preview worked perfectly for my complex use case. It looks like the Metacello embedded in Pharo 2.0 is quite buggy. Dale proposes us to include Metacello Preview in Pharo 2.0 so we don't run into these bugs anymore. What do you think? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Oct. 9, 2013