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

List auto-selection of next item on delete
by StÃ©phane Ducasse June 30, 2013

June 30, 2013

Hi Is there a way to say to a list that when we delete a selected element, the selection should be the next one if possible? Stef

3 2

Manage a Printer device with Semaphore forMutualExclusion
by Dario Trussardi June 29, 2013

June 29, 2013

Ciao, I work with a seaside application. I have a printer device and i need to manage the use of it at one work at time. I think to use one Semaphore forMutualExclusion defined as variable of the specific printerTicket device Now i defined this code to mange the access : aPrinterTicket accessSema critical:[ stampaok:= [ " i open a IP connection on the device. do the printer and manage relative errors " TicketBaseTipoCentriCarico newOn: dcmModel dettagli: tfDettagli onPrinter: aPrinterTicket ] on: Error do: [:ex | " for error i open dialog to advise the operator " self jqDialog: (DTRCassaDialogConferma openOnException: ex onModel: dcmModel). " repeat until the printer is do without error " ex retry ] ]. " When the printer is do i advise the operator of it and allow the next request " stampaok ifTrue: [self jqDialog:(DTRCassaDialogConferma openOnModel: dcmModel) title: 'Ordinazione confermata']. ] With this code the printer semaphore don't work. The semaphore don't manage the code of the request, and when i have a error, at any loop the excessSignal of the printer semaphore is incremented. Any idea ? Thanks, Dario

2 1

Exploring Heap Size Limits
by Sven Van Caekenberghe June 29, 2013

June 29, 2013

Hi, I wrote a little test to explore the heap size limits of the current Pharo image+VM combination. I did some tests on a 8GB 64-bit Linux machine and the basic conclusion is that using a standard 1GB heap size you can allocate and GC with close to 1GB of actual data. I think that is pretty good news. The machine has 4 effective cores, so could easily run 4 busy images like that. Pushing the limits further, things get weird, up to the point of crashing. Sadly 2, 3 or 4 GB heap size, which should be theoretically possible, fail, thus limiting the amount of data that can be allocated and used. Anyway, my goal is to start the debate around this topic ;-) Here is the test script: t3@coolermaster:smalltalk$ cat memtest.st NonInteractiveTranscript stdout install. ! Transcript show: 'memtest.st'; cr. Smalltalk garbageCollect. Transcript show: SmalltalkImage current vm statisticsReport; cr. ! | count size data timeToRun | count := Smalltalk commandLine arguments first asInteger. size := Smalltalk commandLine arguments second asInteger. Transcript show: ('allocating: {1} times {2} bytes' format: { count. size }); cr. timeToRun := [ data := Array new: count streamContents: [ :out | count timesRepeat: [ out nextPut: (ByteArray new: size) ] ]. ] timeToRun. Transcript show: ('allocated: {1}' format: { (data collect: #size) sum humanReadableSIByteSize }); cr. Transcript show: ('time to run {1}' format: { Duration milliSeconds: timeToRun }); cr. Transcript show: '3 times GC'; cr. timeToRun := [ 3 timesRepeat: [ Smalltalk garbageCollect ] ] timeToRun. Transcript show: ('time to run {1}' format: { Duration milliSeconds: timeToRun }); cr. Transcript show: SmalltalkImage current vm statisticsReport; cr. ! SmalltalkImage current quitPrimitive. And here is a normal result running get.pharo.org/20+vm $ ./pharo Pharo.image memtest.st 512 1024000 memtest.st uptime 0h0m0s memory 25,076,708 bytes old 19,213,624 bytes (76.60000000000001%) young 5,384 bytes (0.0%) used 19,219,008 bytes (76.60000000000001%) free 5,857,700 bytes (23.400000000000002%) GCs 10 (12ms between GCs) full 1 totalling 30ms (25.0% uptime), avg 30.0ms incr 9 totalling 6ms (5.0% uptime), avg 0.7000000000000001ms tenures 0 allocating: 512 times 1024000 bytes allocated: 524.29 MB time to run 0:00:00:02.852 3 times GC time to run 0:00:00:00.196 uptime 0h0m3s memory 546,746,364 bytes old 543,520,476 bytes (99.4%) young 7,184 bytes (0.0%) used 543,527,660 bytes (99.4%) free 3,218,704 bytes (0.6000000000000001%) GCs 356 (9ms between GCs) full 89 totalling 2,743ms (86.4% uptime), avg 30.8ms incr 267 totalling 223ms (7.0% uptime), avg 0.8ms tenures 0 Since last view 346 (9ms between GCs) uptime 3.1s full 88 totalling 2,713ms (88.80000000000001% uptime), avg 30.8ms incr 258 totalling 217ms (7.1000000000000005% uptime), avg 0.8ms tenures 0 It takes about 2.5s to allocate about 512Mb. A GC then takes 30ms. You can play a bit with the 2 parameters to generate different datasets. Not changing any VM parameters, you can successfully do something like $ ./pharo Pharo.image memtest.st 1000 1024000 or $ ./pharo Pharo.image memtest.st 1024000 1000 thus allocating about 1GB. Playing with -mmap gives some weird results and unexpected slowness as well. Consider (the default -mmap is 1024m): $ ./pharo -mmap 1280m Pharo.image memtest.st 500 1024000 memtest.st uptime 0h0m0s memory 25,076,716 bytes old 19,213,480 bytes (76.60000000000001%) young 5,384 bytes (0.0%) used 19,218,864 bytes (76.60000000000001%) free 5,857,852 bytes (23.400000000000002%) GCs 12 (13ms between GCs) full 2 totalling 56ms (37.1% uptime), avg 28.0ms incr 10 totalling 6ms (4.0% uptime), avg 0.6000000000000001ms tenures 0 allocating: 500 times 1024000 bytes allocated: 512.00 MB time to run 0:00:00:13.66 3 times GC time to run 0:00:00:00.192 uptime 0h0m14s memory 533,946,384 bytes old 531,232,232 bytes (99.5%) young 7,644 bytes (0.0%) used 531,239,876 bytes (99.5%) free 2,706,508 bytes (0.5%) GCs 1,011 (14ms between GCs) full 501 totalling 13,819ms (98.7% uptime), avg 27.6ms incr 510 totalling 35ms (0.2% uptime), avg 0.1ms tenures 0 Since last view 999 (14ms between GCs) uptime 13.9s full 499 totalling 13,763ms (99.30000000000001% uptime), avg 27.6ms incr 500 totalling 29ms (0.2% uptime), avg 0.1ms tenures 0 So increasing the heap from 1024 Mb to 1280 Mb slows the allocation down to 14s. Increasing the heap size to 1792 Mb gives the following result: t3@coolermaster:smalltalk$ ./pharo -mmap 1792m Pharo.image memtest.st 1280 1048576 memtest.st uptime 0h0m0s memory 25,076,708 bytes old 19,213,592 bytes (76.60000000000001%) young 5,384 bytes (0.0%) used 19,218,976 bytes (76.60000000000001%) free 5,857,732 bytes (23.400000000000002%) GCs 12 (12ms between GCs) full 2 totalling 55ms (37.9% uptime), avg 27.5ms incr 10 totalling 6ms (4.1000000000000005% uptime), avg 0.6000000000000001ms tenures 0 allocating: 1280 times 1048576 bytes allocated: 1.34 GB time to run 0:00:00:35.258 3 times GC time to run 0:00:00:00.37 uptime 0h0m35s memory -783,340,292 bytes old -786,061,544 bytes (100.30000000000001%) young 7,460 bytes (0.0%) used -786,054,084 bytes (100.30000000000001%) free 2,713,792 bytes (-0.30000000000000004%) GCs 2,572 (14ms between GCs) full 1281 totalling 35,444ms (99.10000000000001% uptime), avg 27.700000000000003ms incr 1291 totalling 93ms (0.30000000000000004% uptime), avg 0.1ms tenures 0 Since last view 2,560 (14ms between GCs) uptime 35.6s full 1279 totalling 35,389ms (99.30000000000001% uptime), avg 27.700000000000003ms incr 1281 totalling 87ms (0.2% uptime), avg 0.1ms tenures 0 The allocation takes a lot longer, but the GC times are stable. I suspect that negative reporting has to do with SmallInteger limitations, but the question is if it is only a cosmetic problem or not. Again, I am not complaining, just exploring/wondering. Sven

3 10

VM ppa question
by Sven Van Caekenberghe June 29, 2013

June 29, 2013

Hi, On a machine where I once installed the VM via the ppa method, I now get apt some errors: t3@coolerslave:smalltalk$ sudo apt-get update [sudo] password for t3: Get:1 http://security.ubuntu.com quantal-security Release.gpg [933 B] Hit http://be.archive.ubuntu.com quantal Release.gpg Ign http://ppa.launchpad.net quantal Release.gpg Get:2 http://security.ubuntu.com quantal-security Release [49.6 kB] Get:3 http://be.archive.ubuntu.com quantal-updates Release.gpg [933 B] Hit http://ppa.launchpad.net quantal Release.gpg Hit http://be.archive.ubuntu.com quantal-backports Release.gpg Hit http://ppa.launchpad.net quantal Release.gpg Ign http://ppa.launchpad.net quantal Release Hit http://be.archive.ubuntu.com quantal Release Get:4 http://be.archive.ubuntu.com quantal-updates Release [49.6 kB] Hit http://ppa.launchpad.net quantal Release Hit http://ppa.launchpad.net quantal Release Ign http://ppa.launchpad.net quantal/main Sources/DiffIndex Hit http://be.archive.ubuntu.com quantal-backports Release Get:5 http://security.ubuntu.com quantal-security/main Sources [51.9 kB] Ign http://ppa.launchpad.net quantal/main amd64 Packages/DiffIndex Hit http://be.archive.ubuntu.com quantal/main Sources Hit http://be.archive.ubuntu.com quantal/restricted Sources Hit http://be.archive.ubuntu.com quantal/universe Sources Hit http://be.archive.ubuntu.com quantal/multiverse Sources Ign http://ppa.launchpad.net quantal/main i386 Packages/DiffIndex Hit http://be.archive.ubuntu.com quantal/main amd64 Packages Get:6 http://security.ubuntu.com quantal-security/restricted Sources [1,833 B] Hit http://be.archive.ubuntu.com quantal/restricted amd64 Packages Get:7 http://security.ubuntu.com quantal-security/universe Sources [19.2 kB] Hit http://be.archive.ubuntu.com quantal/universe amd64 Packages Get:8 http://security.ubuntu.com quantal-security/multiverse Sources [696 B] Hit http://ppa.launchpad.net quantal/main Sources Hit http://be.archive.ubuntu.com quantal/multiverse amd64 Packages Get:9 http://security.ubuntu.com quantal-security/main amd64 Packages [146 kB] Hit http://ppa.launchpad.net quantal/main amd64 Packages Hit http://be.archive.ubuntu.com quantal/main i386 Packages Hit http://be.archive.ubuntu.com quantal/restricted i386 Packages Hit http://ppa.launchpad.net quantal/main i386 Packages Hit http://be.archive.ubuntu.com quantal/universe i386 Packages Get:10 http://security.ubuntu.com quantal-security/restricted amd64 Packages [3,469 B] Hit http://be.archive.ubuntu.com quantal/multiverse i386 Packages Get:11 http://security.ubuntu.com quantal-security/universe amd64 Packages [54.7 kB] Hit http://ppa.launchpad.net quantal/main Sources Get:12 http://security.ubuntu.com quantal-security/multiverse amd64 Packages [1,152 B] Hit http://be.archive.ubuntu.com quantal/main Translation-en Get:13 http://security.ubuntu.com quantal-security/main i386 Packages [144 kB] Hit http://ppa.launchpad.net quantal/main amd64 Packages Hit http://be.archive.ubuntu.com quantal/multiverse Translation-en Hit http://ppa.launchpad.net quantal/main i386 Packages Hit http://be.archive.ubuntu.com quantal/restricted Translation-en Get:14 http://security.ubuntu.com quantal-security/restricted i386 Packages [3,531 B] Get:15 http://security.ubuntu.com quantal-security/universe i386 Packages [55.2 kB] Hit http://be.archive.ubuntu.com quantal/universe Translation-en Get:16 http://be.archive.ubuntu.com quantal-updates/main Sources [106 kB] Get:17 http://security.ubuntu.com quantal-security/multiverse i386 Packages [1,396 B] Hit http://security.ubuntu.com quantal-security/main Translation-en Get:18 http://be.archive.ubuntu.com quantal-updates/restricted Sources [2,564 B] Get:19 http://be.archive.ubuntu.com quantal-updates/universe Sources [88.8 kB] Hit http://security.ubuntu.com quantal-security/multiverse Translation-en Hit http://security.ubuntu.com quantal-security/restricted Translation-en Hit http://security.ubuntu.com quantal-security/universe Translation-en Get:20 http://be.archive.ubuntu.com quantal-updates/multiverse Sources [3,998 B] Get:21 http://be.archive.ubuntu.com quantal-updates/main amd64 Packages [273 kB] Ign http://security.ubuntu.com quantal-security/main Translation-en_US Get:22 http://be.archive.ubuntu.com quantal-updates/restricted amd64 Packages [4,804 B] Ign http://security.ubuntu.com quantal-security/multiverse Translation-en_US Get:23 http://be.archive.ubuntu.com quantal-updates/universe amd64 Packages [195 kB] Ign http://security.ubuntu.com quantal-security/restricted Translation-en_US Ign http://security.ubuntu.com quantal-security/universe Translation-en_US Ign http://ppa.launchpad.net quantal/main Translation-en_US Get:24 http://be.archive.ubuntu.com quantal-updates/multiverse amd64 Packages [10.8 kB] Ign http://ppa.launchpad.net quantal/main Translation-en Get:25 http://be.archive.ubuntu.com quantal-updates/main i386 Packages [272 kB] Err http://ppa.launchpad.net quantal/main Sources 404 Not Found Err http://ppa.launchpad.net quantal/main amd64 Packages 404 Not Found Ign http://ppa.launchpad.net quantal/main Translation-en_US Ign http://ppa.launchpad.net quantal/main Translation-en Ign http://ppa.launchpad.net quantal/main Translation-en_US Ign http://ppa.launchpad.net quantal/main Translation-en Get:26 http://be.archive.ubuntu.com quantal-updates/restricted i386 Packages [4,841 B] Err http://ppa.launchpad.net quantal/main i386 Packages 404 Not Found Get:27 http://be.archive.ubuntu.com quantal-updates/universe i386 Packages [195 kB] Get:28 http://be.archive.ubuntu.com quantal-updates/multiverse i386 Packages [10.9 kB] Hit http://be.archive.ubuntu.com quantal-updates/main Translation-en Hit http://be.archive.ubuntu.com quantal-updates/multiverse Translation-en Hit http://be.archive.ubuntu.com quantal-updates/restricted Translation-en Hit http://be.archive.ubuntu.com quantal-updates/universe Translation-en Hit http://be.archive.ubuntu.com quantal-backports/main Sources Hit http://be.archive.ubuntu.com quantal-backports/restricted Sources Hit http://be.archive.ubuntu.com quantal-backports/universe Sources Hit http://be.archive.ubuntu.com quantal-backports/multiverse Sources Hit http://be.archive.ubuntu.com quantal-backports/main amd64 Packages Hit http://be.archive.ubuntu.com quantal-backports/restricted amd64 Packages Hit http://be.archive.ubuntu.com quantal-backports/universe amd64 Packages Hit http://be.archive.ubuntu.com quantal-backports/multiverse amd64 Packages Hit http://be.archive.ubuntu.com quantal-backports/main i386 Packages Hit http://be.archive.ubuntu.com quantal-backports/restricted i386 Packages Hit http://be.archive.ubuntu.com quantal-backports/universe i386 Packages Hit http://be.archive.ubuntu.com quantal-backports/multiverse i386 Packages Hit http://be.archive.ubuntu.com quantal-backports/main Translation-en Hit http://be.archive.ubuntu.com quantal-backports/multiverse Translation-en Hit http://be.archive.ubuntu.com quantal-backports/restricted Translation-en Hit http://be.archive.ubuntu.com quantal-backports/universe Translation-en Ign http://be.archive.ubuntu.com quantal/main Translation-en_US Ign http://be.archive.ubuntu.com quantal/multiverse Translation-en_US Ign http://be.archive.ubuntu.com quantal/restricted Translation-en_US Ign http://be.archive.ubuntu.com quantal/universe Translation-en_US Ign http://be.archive.ubuntu.com quantal-updates/main Translation-en_US Ign http://be.archive.ubuntu.com quantal-updates/multiverse Translation-en_US Ign http://be.archive.ubuntu.com quantal-updates/restricted Translation-en_US Ign http://be.archive.ubuntu.com quantal-updates/universe Translation-en_US Ign http://be.archive.ubuntu.com quantal-backports/main Translation-en_US Ign http://be.archive.ubuntu.com quantal-backports/multiverse Translation-en_US Ign http://be.archive.ubuntu.com quantal-backports/restricted Translation-en_US Ign http://be.archive.ubuntu.com quantal-backports/universe Translation-en_US Fetched 1,752 kB in 3s (439 kB/s) W: Failed to fetch http://ppa.launchpad.net/cassou/pharo/ubuntu/dists/quantal/main/source/Sour… 404 Not Found W: Failed to fetch http://ppa.launchpad.net/cassou/pharo/ubuntu/dists/quantal/main/binary-amd6… 404 Not Found W: Failed to fetch http://ppa.launchpad.net/cassou/pharo/ubuntu/dists/quantal/main/binary-i386… 404 Not Found E: Some index files failed to download. They have been ignored, or old ones used instead. apt has always been a bit of mystery to me. Maybe the problem is that the ppa moved ? Is there a way to fix this ? Maybe uninstall some stuff ? Thx, Sven

3 3

Question about closure compilation
by Sven Van Caekenberghe June 29, 2013

June 29, 2013

Hi, Does the closure returned from | foo | foo := #( data 1 2 3 ). [ :x | x + 1 ] close over foo ? Since foo is not used, it should not, right ? But it seems that the outer context of the block closure knows about foo, although the value seems nil. And if it closes over foo, foo's value/binding won't be GC-ed so long as there is a reference to the block closure, even though foo is not practically accessible. Sven

3 7

brief explanation of the new class organizer
by Esteban Lorenzano June 29, 2013

June 29, 2013

Hi, So... this is what I made las days (as a conclusion of many days before): The old class organizer was a mess. Basically, it considered all protocols as strings, and for worst it was arranging them into a flat array. While the array stuff is just an internal problem (objects outside doesn't know how are they managed, and that's good), having protocols-as-strings is essentially bad (no need for explanations about that). The new class organizer just do what is more or less obvious: 1) replaces string protocols for first class instances (now instances of Protocol). 2) internally, manages protocols and methods in protocols in a much better and fashion way. (btw, the implementation was made by Ben, thanks!) the real important part is the point 1. Now we can start to assign real behavior to Protocol, For instance, I will create an ExtensionProcol which will contain a direct pointer to it's real package. That means that we do not need weird computations to get a method extension package (and when the tools allows us, we could get rid off the *Blah). I would like also to be able to have "composite" protocols (like "private"+"accesing"), etc. It will allow a refactor of current RPackage implementation, allowing us to simplify the SystemAnnounce mechanism (and speeding up monticello, if my calculous are fine). And like this, there are still a huge room for improvement, I hope many that I do not even thought about :) cheers, Esteban

3 3

[update 3.0] #30235
by StÃ©phane Ducasse June 28, 2013

June 28, 2013

30235 ----- 11071 PasteUpMorph cleaning https://pharo.fogbugz.com/default.asp?11071 11024 Removing>>griddedPoint: https://pharo.fogbugz.com/default.asp?11024 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Base-StephaneDucasse.…

1 0

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

June 28, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=wi… 7 regressions found. KernelTests.Classes.ClassDescriptionTest.testUnCategorizedMethods Tests.CodeImport.ChunkImportTestCase.testImportAClassCategory Tests.Monticello.MCSnapshotBrowserTest.testClassSelected Tests.Monticello.MCSnapshotBrowserTest.testMethodSelected Tests.Monticello.MCSnapshotBrowserTest.testProtocolSelected Tests.Traits.TraitFileOutTest.testFileOutCategory Tests.Traits.TraitFileOutTest.testFileOutTrait

1 0

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

June 28, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=ma… 7 regressions found. KernelTests.Classes.ClassDescriptionTest.testUnCategorizedMethods Tests.CodeImport.ChunkImportTestCase.testImportAClassCategory Tests.Monticello.MCSnapshotBrowserTest.testClassSelected Tests.Monticello.MCSnapshotBrowserTest.testMethodSelected Tests.Monticello.MCSnapshotBrowserTest.testProtocolSelected Tests.Traits.TraitFileOutTest.testFileOutCategory Tests.Traits.TraitFileOutTest.testFileOutTrait

1 0

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

June 28, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… 7 regressions found. KernelTests.Classes.ClassDescriptionTest.testUnCategorizedMethods Tests.CodeImport.ChunkImportTestCase.testImportAClassCategory Tests.Monticello.MCSnapshotBrowserTest.testClassSelected Tests.Monticello.MCSnapshotBrowserTest.testMethodSelected Tests.Monticello.MCSnapshotBrowserTest.testProtocolSelected Tests.Traits.TraitFileOutTest.testFileOutCategory Tests.Traits.TraitFileOutTest.testFileOutTrait

1 0