- Pharo-dev - lists.pharo.org

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

by Henrik Johansen

On Oct 7, 2013, at 4:36 , Igor Stasenko <siguctua(a)gmail.com> wrote: > 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 :) > Uhm, I didn't read your implementation, but the proper thing to do for a VM which doesn't care about the external objects table (splObjs at: 39) growing, is returning nil from maxExternalSemaphores, like it will for pre-Cog VM's. Otherwise, you'll get a domain error when you eventually (yes,yes, it'll take awhile) run out, and maxExternalSemaphoresSilently: tries to set the new max to a value that won't fit in the 16bit header field where it expects to put itâ¦ Cheers, Henry

Oct. 7, 2013

[pharo-project/pharo-core]

by GitHub

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

Oct. 7, 2013

[pharo-project/pharo-core] fda431: 30461

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: fda431fecd8dea237857af496c265b289a1b4f13 https://github.com/pharo-project/pharo-core/commit/fda431fecd8dea237857af49… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-07 (Mon, 07 Oct 2013) Changed paths: M Monticello-Announcements.package/MCVersionCreated.class/definition.st R Monticello-Announcements.package/MCVersionCreated.class/instance/accessing/name_.st M Monticello-Repositories.package/MCFtpRepository.class/definition.st A Monticello-Repositories.package/MCVersionNotification.class/instance/accessing/messageText.st R Monticello-Repositories.package/MCVersionNotification.class/instance/as yet unclassified/initializeWithVersion_repository_.st R Monticello-Repositories.package/MCVersionNotification.class/instance/as yet unclassified/messageText.st R Monticello-Repositories.package/MCVersionNotification.class/instance/as yet unclassified/notify_.st A Monticello-Repositories.package/MCVersionNotification.class/instance/error handling/notify_.st A Monticello-Repositories.package/MCVersionNotification.class/instance/initialize-release/initializeWithVersion_repository_.st M Monticello-Storing.package/MCDataStream.class/instance/write and read/next.st M Monticello-Versioning.package/MCMergeRecord.class/README.md M Monticello-Versioning.package/MCMergeRecord.class/definition.st M Monticello-Versioning.package/MCWorkingCopy.class/definition.st R Monticello.package/MCDirtyPackageInfo.class/class/as yet unclassified/initialize.st R Monticello.package/MCDirtyPackageInfo.class/class/as yet unclassified/wantsChangeSetLogging.st A Monticello.package/MCDirtyPackageInfo.class/class/compiling/wantsChangeSetLogging.st A Monticello.package/MCDirtyPackageInfo.class/class/initialization/initialize.st A Monticello.package/MCMockDefinition.class/class/accessing/token_.st R Monticello.package/MCMockDefinition.class/class/as yet unclassified/token_.st R Monticello.package/MCMockDefinition.class/class/as yet unclassified/wantsChangeSetLogging.st A Monticello.package/MCMockDefinition.class/class/compiling/wantsChangeSetLogging.st M Ring-Core-Containers.package/RGAbstractContainer.class/instance/iterating elements/elementsDo_.st M Ring-Core-Containers.package/RGAbstractContainer.class/instance/testing/includesElementNamed_in_.st M Ring-Core-Containers.package/RGContainer.class/instance/image class and method loading/loadTraitUsers.st M Ring-Core-Kernel.package/RGBehaviorDefinition.class/instance/accessing class hierarchy/allSuperclassesDo_.st M Ring-Core-Kernel.package/RGBehaviorDefinition.class/instance/testing/includesProtocol_.st M Ring-Core-Kernel.package/extension/SourceFileArray/instance/sourcedDataAt_.st M Ring-Core-Kernel.package/extension/Trait/instance/asRingDefinitionWithMethods_withSuperclasses_withSubclasses_withPackageKeys_in_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script116.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30461.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Support.package/SystemNavigation.class/instance/message sends/allSendersOf_inClass_.st R System-Support.package/SystemNavigation.class/instance/query/allPrimitiveMethodsInCategories_.st R Tools.package/extension/SystemNavigation/instance/doWithProgressBar_forUnsentMessagesInPackageNamed_.st R Tools.package/extension/SystemNavigation/instance/unsentMessagesWithProgressBarInPackageNamed_.st Log Message: ----------- 30461 11808 Small critic cleanup if Ring https://pharo.fogbugz.com/f/cases/11808 11809 Fix failing tests SystemNavigation https://pharo.fogbugz.com/f/cases/11809 11788 Trivial critic cleanup of Monticello https://pharo.fogbugz.com/f/cases/11788

Oct. 7, 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… 1 regressions found. Tests.Release.ReleaseTest.testUndeclared

Oct. 7, 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=ma… 1 regressions found. Tests.Release.ReleaseTest.testUndeclared

Oct. 7, 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=li… 1 regressions found. Tests.Release.ReleaseTest.testUndeclared

Oct. 7, 2013

Re: [Pharo-dev] WhatsUp from: 2013-10-07 until: 2013-10-20

by Damien Cassou

### Here's what I've been up to since the last WhatsUp: - write project proposals to attract students (http://damiencassou.github.io) - work on the Gutemberg project to generate books from Pier syntax - some cleaning to the PBE 1 website - updates to the pharo.org and book's websites - update to the Ubuntu packaging of Pharo so it now has a Pharo launcher (https://launchpad.net/~pharo/+archive/stable/) - try to understand why, on some linux window managers, "Squeak" still appears in the menus. - some work on the Pharo Launcher to make it easier to understand and use (please use it and give feedback: https://ci.inria.fr/pharo-contribution/job/PharoLauncher) - pair-program with Esteban on ConfigurationOfPierVoyage (http://www.smalltalkhub.com/#!/~estebanlm/Voyage) ### What's next, until 2013-10-20 (*): - clean Pier document model and parser so that it is easier to reuse outside of the CMS (for example to generate books and to visualize class/package documentation within Nautilus) -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Oct. 7, 2013

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

by Igor Stasenko

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 :) i just found that after one merge, my changes get lost we're just plugged them back in, and it should be back again with newer VMs.. but the problem could be more than just semaphores.. if merge broken this, it may break many other things, so we need time to check On 7 October 2013 12:31, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 07.10.2013 um 11:28 schrieb Henrik Johansen < > henrik.s.johansen(a)veloxit.no>: > > > On Oct 7, 2013, at 11:16 , Norbert Hartl <norbert(a)hartl.name> wrote: > > As I need an image that runs longer than 24 hours I'm looking at some > stuff and wonder. Can anybody explain me the rationale for a code like this > > maxExternalSemaphores: aSize > "This method should never be called as result of normal program > execution. If it is however, handle it differently: > - In development, signal an error to promt user to set a bigger size > at startup immediately. > - In production, accept the cost of potentially unhandled interrupts, > but log the action for later review. > See comment in maxExternalObjectsSilently: why this behaviour is > desirable, " > "Can't find a place where development/production is decided. > Suggest Smalltalk image inProduction, but use an overridable temp > meanwhile. " > | inProduction | > self maxExternalSemaphores > ifNil: [^ 0]. > inProduction := false. > ^ inProduction > ifTrue: [self maxExternalSemaphoresSilently: aSize. > self crTrace: 'WARNING: Had to increase size of semaphore signal handling > table due to many external objects concurrently in use'; > crTrace: 'You should increase this size at startup using > #maxExternalObjectsSilently:'; > crTrace: 'Current table size: ' , self maxExternalSemaphores printString] > ifFalse: ["Smalltalk image" > self error: 'Not enough space for external objects, set a larger size at > startup!' > "Smalltalk image"] > > I have reported this once but got no feedback so I like to have a few > opinions. > > The report is here: https://pharo.fogbugz.com/f/cases/10839/ > > Norbert > > > The rationale is that inProduction would be some global setting, not yet > in place when the code was writtenâ¦ > Excessive simultaneous Semaphore usage is something that should be caught > during development, in which case it's better to get an active > notification, than having it logged somewhere. > > > Agreed. But didn't work in my case because it needed roughly 20 hours and > an instable remote backend to trigger the problem. And somehow I forgot to > install my logger as Transcript so there is no warning message. I saw only > dead images in the morning. > This not satisfactory but on the other hand this type of problems are hard > to solve anyway. My feeling tells me there is more to discover. Sockets > resources get unregistered at finalization time but this didn't work > either. I would have said that the unlikely situation that no garbage > collection ran could be the case. But it can't because in > ExternalSemaphoreTable>>#freedSlotsIn:ratherThanIncreaseSizeTo: there is > explicit garbage collection. > > If I've understood correctly, it's moot on newer Pharo VM's, where there's > no limit on the semtable size, but for legacy code a startup item setting > size using maxExternalObjectsSilently: (as suggested in the Warning text), > is still a more proper fix than setting inProduction to true and crossing > your fingers hoping no signals will be lost during table growth. > > > Ah, I didn't know about the risk of loosing signals while resizing the > table. Thanks for that. Don't get me wrong I wasn't proposing to set > inProduction in effect. I don't think that automatically growing resource > management is a proper way to design a system. There is always a range of > resources you need for your use case. Not setting an upper bound for this > just covers leaking behavior. > > Norbert > > > -- Best regards, Igor Stasenko.

Oct. 7, 2013

Re: [Pharo-dev] R: full version of a Lint Chapter for Entreprise Pharo forthcoming book :)

by Camillo Bruni

Mind the newline in the middle of the link posted by stef: https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ws/Lint/Li… On 2013-10-07, at 16:30, "Lorenzo Schiavina" <lorenzo(a)edor.it> wrote: > Hi Stef, > > I cannot download the paper; can you check if there is any problem? > > Grazie > > -----Messaggio originale----- > Da: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] Per conto di > StÃ©phane Ducasse > Inviato: domenica 6 ottobre 2013 09:41 > A: Pharo Development List; Any question about pharo is welcome > Oggetto: [Pharo-dev] full version of a Lint Chapter for Entreprise Pharo > forthcoming book :) > > Hi Pharoers > > since we believe in quality and automation, here is a new chapter on Lint > rule support in Pharo :) > > > https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ws/Lint/Lin > t.pier.pdf > > Stef > >

Oct. 7, 2013

R: full version of a Lint Chapter for Entreprise Pharo forthcoming book :)

by Lorenzo Schiavina

Hi Stef, I cannot download the paper; can you check if there is any problem? Grazie -----Messaggio originale----- Da: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] Per conto di StÃ©phane Ducasse Inviato: domenica 6 ottobre 2013 09:41 A: Pharo Development List; Any question about pharo is welcome Oggetto: [Pharo-dev] full version of a Lint Chapter for Entreprise Pharo forthcoming book :) Hi Pharoers since we believe in quality and automation, here is a new chapter on Lint rule support in Pharo :) https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ws/Lint/Lin t.pier.pdf Stef

Oct. 7, 2013