August 2013 - Pharo-dev - lists.pharo.org

why can we interrupt the UI thread?
by StÃ©phane Ducasse Aug. 19, 2013

Aug. 19, 2013

2 2

[update 3.0] #30337
by Marcus Denker Aug. 19, 2013

Aug. 19, 2013

30337 ----- 11394 Needed support for traits in ClassFactoryForTestCase https://pharo.fogbugz.com/f/cases/11394 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/SUnit-Tests-MarcusDenker.23.d… http://smalltalkhub.com/mc/Pharo/Pharo30/main/SUnit-Core-MarcusDenker.92.di…

3 3

Large images reasons [WAS] Re: [Pharo-users] Pharo 2.0 with Seaside + DBXTalk + GlorpDBX + Magritte 3 + TWBS is getting slower and slower
by Mariano Martinez Peck Aug. 19, 2013

Aug. 19, 2013

OK, this was was my experiment.... Image fresh with all my app and dependencies loades: 30MB After using it for some days/weeks: 160MB. SpaceTally new printSpaceAnalysis showed: Class code space # instances inst space percent inst average size ByteString 2785 413144 116244078 69.90 281.36 Array 3712 181772 8466668 5.10 46.58 ByteArray 8574 1319 8186802 4.90 6206.82 Bitmap 3653 303 6656340 4.00 21968.12 CompiledMethod 22467 90554 5685374 3.40 62.78 After executing ImageCleaner cleanUpForRelease: 36MB Then...I searched which part of #cleanUpForRelease: was making the difference, and it was: Smalltalk cleanUp: true except: #() confirming: false. So now it was time to know WHICH class did the diference, so I modified #cleanUp: aggressive except: exclusions confirming: aBool in these lines: "Run the cleanup code" classes do:[:aClass| Transcript show: 'Image size before cleaning ', aClass name, ' : ', Smalltalk imagePath asFileReference size asString. aClass cleanUp: aggressive. 3 timesRepeat: [Smalltalk garbageCollect]. Smalltalk snapshot: true andQuit: false. Transcript show: 'Image size after cleaning ', aClass name, ' : ', Smalltalk imagePath asFileReference size asString. ] displayingProgress: [:aClass| 'Cleaning up in ', aClass name]. I then opened a Transcript, and evaluated Smalltalk cleanUp: true except: #() confirming: false. I went to prepare Mate, and when I come back, the result was, of course: "Image size after cleaning MCFileBasedRepository : 39744008" That clean up ends up doing: flushAllCaches self allSubInstancesDo: [:ea | ea flushCache] So it sends #flushCache to all instances of MCHttpRepository and MCFileBasedRepository. Now what I wanted to see if it there was a particular repo that could take most of the space (like package-cache). And indeed, it was...I modified #flushCaches to: flushAllCaches | file | file := 'repos.txt' asFileReference writeStream text. self allSubInstancesDo: [:each | file nextPutAll: 'Image size before cleaning ', each printString, ' : ', Smalltalk imagePath asFileReference size asString; cr. each flushCache. 3 timesRepeat: [Smalltalk garbageCollect]. Smalltalk snapshot: true andQuit: false. file nextPutAll: 'Image size after cleaning ', each printString, ' : ', Smalltalk imagePath asFileReference size asString;cr. ]. file flush; close. And then I looked in the 'repos.txt' file. My package cache repo cleaned 60 MB. Glorp cleaned 35MB. Seaside30 cleaned 10MB. So...cleaning cache of just 3 repos frees approx 100MB. The question is....can we flush the cache safely? If they are called "cache", then I guess yes, we can. Thoughts? Thanks, On Wed, Jul 31, 2013 at 10:48 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Guys, I have images also with seaside, magritte, glorp, postgresV2, etc > and it is also around 200MB. > I will try to do some research today and let you know. > > Cheers, > > > On Tue, Jul 30, 2013 at 8:55 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > >> >> On Jul 30, 2013, at 1:49 PM, "phil(a)highoctane.be" <phil(a)highoctane.be> >> wrote: >> >> > the changes file contained passwords and I replaced the text. So >> offsets may be wrong due to that. >> > >> Yes, the first thing I wanted to do is to recompile everything. Does not >> work. >> >> > Memorymonitor is not doing fanct stuff. It just counts instances. >> > >> Yes, but maybe it holds on to these instances? >> >> Marcus >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > -- Mariano http://marianopeck.wordpress.com

6 17

Anyone in St Petersburg?
by Alexandre Bergel Aug. 18, 2013

Aug. 18, 2013

Hi! I am spending the week in Russia to attend ESEC/FSE. Just wondering whether some of the Russian crew here are up to a drink this week. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 1

I would prefer to see the diff from Smalltalkhub than Git commits
by StÃ©phane Ducasse Aug. 18, 2013

Aug. 18, 2013

Hi could we avoid to get the github commits. I would prefer to get diff from Smalltalkhub. Stef

3 6

Re: [Pharo-dev] I would prefer to see the diff from Smalltalkhub than Git commits
by Stephan Eggermont Aug. 18, 2013

Aug. 18, 2013

Camillo wrote: >- they are auto generate, no manual intervention needed to send them So they should go to the issue tracker list >- the github repository is the place where you go to find changes, it's simply impossible to figure out when > something broke on smalltalkhub since you cannot compare multiple packages over multiple times Sounds like it's time to migrate Torch. Stephan

2 1

pharo.changes write failed
by jannik.laval Aug. 17, 2013

Aug. 17, 2013

Hi, This night, the jenkins job of Phratch failed because of an error to write the .changes file. Trying manually gives the same. For information, I do not change anything in the Phratch code source. ==== Image ----- /Users/janniklaval/Desktop/phratchDev/phratch.image Pharo2.0 Latest update: #20619 Unnamed Virtual Machine --------------- /Users/janniklaval/Desktop/phratchDev/pharo-vm/Pharo.app/Contents/MacOS/Pharo NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 git://gitorious.org/cogvm/blessed.git Commit: 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 Mac Cocoa Cog 5.8b12 21-Sep-10 >1B0534FA-246C-47C5-AB29-7A76C81CCDCB< VMMaker versionString git://gitorious.org/cogvm/blessed.git Commit: 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 ====

3 4

Requested origin error on win8 ?
by Erwan Douaille Aug. 17, 2013

Aug. 17, 2013

Hi a creenshot of what happened when i opened latest 3.0 image with cogVM on win 8. Is it a known issue ?[image: Images intÃ©grÃ©es 1] Thanks :) -- Best regards, Douaille Erwan <douaille.erwan(a)gmail.com>

1 0

Aug. 17, 2013

Hi guys I started to be fed up about protocol inconsistencies. So I will propose a set of rules (and a tool - I'm working on it) to automatically categorize methods. The first on the list was printOn: in printing and I clean many methods already with a kind of happy smile on my face. Now we discussed today with esteban for initialize* we will use 'initialization' I hope that this is ok for you because I'm fed up to have the following: {269->'initialization'. 248->'initialize-release'. 48->'as yet unclassified'. 15->'accessing'. 14->'private'. 12->'initializing'. 2->'instance creation'. 2->'testing'. 2->'initalize-release'. 2->'protocol'. 2->'display'. 1->'cleaning'. 1->'intializing'. 1->'like fullCopy'. 1->'keymapping'. 1->'ui-building'. 1->'initialize - release'. 1->'initialization-release'. 1->'intialize'. 1->'styling'. 1->'scrolling'. 1->'morphic ui'. 1->'world state'. 1->#'parts bin'} Please enjoy this gift from life, I love so much 'like fullCopy' as a category for initialize that I'm a bit sad to clean this kind of poem (minimal haiku) so we will keep it for us :) Yes there is no little steps to get a bright system, every little clean is stop. No broken window! No dirt on the floor in Pharo. Stef

7 15

Uniformizing Pharo
by Torsten Bergmann Aug. 17, 2013

Aug. 17, 2013

Instead of category 'setup' for #setUp and #tearDown I would like to see 'running' since this follows the original SUnit and tearDown has nothing to do with setting up the test case, more with cleaning up. What about binary messages like = for comparing? I would also like to see one for methods matching example... to be in examples. Beside is... for 'testing' there could also be was...., it should take into account the next Character is Uppercase. What about also taking pragmas into account? With that NB Api wrappers could be categorized into 'api' or 'primitive' (which is more general)

2 1