February 2015 - Pharo-dev - lists.pharo.org

MCVersionInfo: 10% of the image

by Marcus Denker

Hi, The current Pharo4 contains *a lot* of MCVersionInfo instances. MCVersionInfo allInstances size 11095 The hold on to strings, Date, UUIDâ¦ a lot of stuff. All in all, this is around 10% of the current image. If you do MCVersionInfo allInstances do: [ :each | each instVarNamed: 'ancestors' put: nil ]. you image is a couple of MB smaller. In the past, when this information started to be >8MB, we did that. With the bad effect that we can not merge anymore across this boundary: we kill the past. Now this information is of course continained in the last MCZ file, too (all of them contain the complete historyâ¦) So would the following work? -> we set the âancestorsâ of MCVersionInfo to #reload -> the accessor, when it sees #reload, takes the name, deduces from that the package, and goes to the repo to load the ancestry info from the MCZFile. This means that e.g when saving a MCZFile, it would first re-create history info and then save it completely (like now), yet someone who just uses the system would never need to have this info in the image. Marcus

Feb. 20, 2015

Re: [Pharo-dev] [FIX (Maybe ; ))]: Issue 14959: MC Hook for Default Credentials

by Sean P. DeNigris

stepharo wrote > I was thinking that we could use Author Ah, yes. That might be a good place. We have KeyChain in the image. I wonder what the status of that is. It seems like it was designed for this purpose... ----- Cheers, Sean -- View this message in context: http://forum.world.st/FIX-Maybe-Issue-14959-MC-Hook-for-Default-Credentials… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 20, 2015

How to get rid of GT-Playground

by Nicolai Hess

instances ? If you open a fresh image and change the setting to use the old workspace open a workspace and execute: GTPlayground allInstances size -> 1 There is already one instance. I tried to get rid of this instance but I couldn't find a way. I think this instance is responsible for issue 14928 <https://pharo.fogbugz.com/default.asp?14928>: SystemNavigation default obsoleteClasses -> an Array(AnObsoleteGLMPageScroller AnObsoleteGLMPagerScrollMorph) And this in turn, is repsonsible for undeleteable references to AnObsoleteKMUntypeableSingleKeyCombination. I need this for issue 14936 <https://pharo.fogbugz.com/default.asp?14936> any idea? nicolai

Feb. 20, 2015

Re: [Pharo-dev] Why was #asLegalSelector removed?

by Stephan Eggermont

On 19/02/15 18:43, Damien Pollet wrote: > I think it would make sense to publish a configuration for > DeprecationFinder in the configuration browser. Does it work on any > Pharo image, or is it written on top of Moose ? I'm trying to see if it still runs atm. Looking good in a Moose 5.1. 50 MB of package cache, 1250 monticello packages and counting. Hmm, found a bug in MooseMonticelloHTTPImporter. VHDL-cipt.24.mcz has a method name ending in _class and that confuse resolveInstanceSide: aNamedEntity I deliberately didn't put this in the configuration browser as running this code without the delay in getAllFrom:thenDo: performs a DOS attack. It also takes a lot of time to run, getting all packages and just creates a data structure that is easy to inspect. DeprecationFinder default findAllUsers just starts downloading and parsing everything. I never bothered creating a UI, as the GTInspector is good enough. Stephan

Feb. 20, 2015

[jenkins] >30 issues for review

by Marcus Denker

Hi, People are busy submitting fixes and improvements.. we should not forget to give them feedback. There are a lot if issues that needs reviewsâ¦ 6 where the monkey ran (or can not run): https://pharo.fogbugz.com/f/filters/45/Review and 26 waiting for the monkey that is down due to CI: https://pharo.fogbugz.com/f/filters/36/Fixed-to-Review Marcus

Feb. 20, 2015

Re: [Pharo-dev] I just crashed sthub

by Stephan Eggermont

On 20/02/15 12:26, Esteban Lorenzano wrote: > >> On 20 Feb 2015, at 12:21, Stephan Eggermont <stephan(a)stack.nl> wrote: >> In the last green build of the 3.0 SmalltalkHub image I cannot load your changes. Some compiler bug. > > Iâm aware, fixing now. A, good. > >> >> - ShTeamsHandler>>searchTeamNamed: should use #name instead of #username > > I never touched anything like that :) I know. >> http://smalltalkhub.com/hub/projects?term=c >> >> VOMongoError: Lazy reference not found ShTeam: OID(3583374428) > > againâ¦ no idea and nothing to do with my changesâ¦ > > Soâ¦ are you reporting previous bugs? I do not understand :P I'm trying to update DeprecationFinder. It seems to work as is, just loading in a Moose 5.1. It starts with users and asks them for their projects, but that means it misses team projects (like Pharo, Seaside, Magritte, Moose...). I wanted to start from teams now, and found I couldn't. Finding a team doesn't work because of the username/name bug and using a regex often results in the mongo error. And of course I need to check in SmalltalkHub to see how to access this. Stephan

Feb. 20, 2015

Re: [Pharo-dev] I just crashed sthub

by Esteban Lorenzano

> On 20 Feb 2015, at 12:21, Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 19/02/15 14:31, Esteban Lorenzano wrote: >> is restoredâ¦ but I couldnât applied the change I wantedâ¦ maybe tomorrow :) >> >>> On 19 Feb 2015, at 14:24, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>> >>> Thank you Esteban. >>> >>> >>>> On 19 Feb 2015, at 14:18, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>> is temporal >>>> and for the better good. >>>> >>>> please, be patient :) > > Always asking for the impossible... > > In the last green build of the 3.0 SmalltalkHub image I cannot load your changes. Some compiler bug. Iâm aware, fixing now. > > - ShTeamsHandler>>searchTeamNamed: should use #name instead of #username I never touched anything like that :) > > searchTeamNamed: aString > <get> > <path: '?term={aString}'> > <produces: 'text/json'> > > ^self renderJson: [ > (ShTeam select: {'name' -> { > '$regex' -> aString. > '$options' -> 'i' } asDictionary } asDictionary) collect: #name ] > > The configuration should use #release versions of Seaside/Magritte/Grease. We support multiple versions on a platform. > > http://smalltalkhub.com/hub/projects?term=c > > VOMongoError: Lazy reference not found ShTeam: OID(3583374428) againâ¦ no idea and nothing to do with my changesâ¦ Soâ¦ are you reporting previous bugs? I do not understand :P Esteban > > Cheers, > Stephan > >

Feb. 20, 2015

Re: [Pharo-dev] I just crashed sthub

by Stephan Eggermont

On 19/02/15 14:31, Esteban Lorenzano wrote: > is restoredâ¦ but I couldnât applied the change I wantedâ¦ maybe tomorrow :) > >> On 19 Feb 2015, at 14:24, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >> Thank you Esteban. >> >> >>> On 19 Feb 2015, at 14:18, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> is temporal >>> and for the better good. >>> >>> please, be patient :) Always asking for the impossible... In the last green build of the 3.0 SmalltalkHub image I cannot load your changes. Some compiler bug. - ShTeamsHandler>>searchTeamNamed: should use #name instead of #username searchTeamNamed: aString <get> <path: '?term={aString}'> <produces: 'text/json'> ^self renderJson: [ (ShTeam select: {'name' -> { '$regex' -> aString. '$options' -> 'i' } asDictionary } asDictionary) collect: #name ] The configuration should use #release versions of Seaside/Magritte/Grease. We support multiple versions on a platform. http://smalltalkhub.com/hub/projects?term=c VOMongoError: Lazy reference not found ShTeam: OID(3583374428) Cheers, Stephan

Feb. 20, 2015

Re: [Pharo-dev] CI Server still down...

by Christophe Demarey

Le 20 fÃ©vr. 2015 Ã 11:22, Tudor Girba a Ã©crit : > Thank you for keeping an eye on this. > > Just a note: while the servers being down can induce some frustration we should remember that INRIA is very kind to offer this support for our community. So, thanks for all the hard work that happens behind the scene! And this upgrade is the first mandatory step to enable OS X slaves on the Inria CI service.

Feb. 20, 2015

Re: [Pharo-dev] CI Server still down...

by Tudor Girba

Thank you for keeping an eye on this. Just a note: while the servers being down can induce some frustration we should remember that INRIA is very kind to offer this support for our community. So, thanks for all the hard work that happens behind the scene! Cheers, Doru On Fri, Feb 20, 2015 at 11:03 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > CI Servers are still down. > > Until they are up we can not do any integration nor run the automatic check > on submitted things. > > Marcus > > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 20, 2015