- Pharo-dev - lists.pharo.org

[Issue tracker] Help needed
by Marcus Denker Oct. 8, 2013

Oct. 8, 2013

Hello, There are still many,many reports that are stuck. E.g. the last comment was "I can not see a committed Slice" or "X, can you have a look?". There is *nothing* that anyone other than the original person meant in the last comment can do. Or maybe a good question: If you are that person X, what do you expect? How do *you* think the issue can be moved forward? Marcus

2 1

[pharo-project/pharo-core] fda431: 30461
by GitHub Oct. 8, 2013

Oct. 8, 2013

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

6 5

full version of a Lint Chapter for Entreprise Pharo forthcoming book :)
by StÃ©phane Ducasse Oct. 8, 2013

Oct. 8, 2013

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/Li… Stef

4 4

External Semaphores leaking in Socket
by Norbert Hartl Oct. 7, 2013

Oct. 7, 2013

I took some time to analyze my current problem with external semaphores. I was just reluctant to raise the limit in my image because I want the problem solved. I logged the management of external semaphores and discovered that the table fills if a connection times out. The problem turns out to be in Socket>>#connectTo: hostAddress port: port waitForConnectionFor: timeout "Initiate a connection to the given port at the given host address. Waits until the connection is established or time outs." self connectNonBlockingTo: hostAddress port: port. self waitForConnectionFor: timeout ifTimedOut: [ConnectionTimedOut signal: 'Cannot connect to ' , (NetNameResolver stringFromAddress: hostAddress) , ':' , port asString] When a socket is created three external semaphores are registered in the ExternalSemaphoreTable. If a connection times out the exception is thrown but the Socket still has his resources attached. So e.g. in SocketStream class>>#openConnectionToHost: hostIP port: portNumber timeout: timeout | socket | socket := Socket new. socket connectTo: hostIP port: portNumber waitForConnectionFor: timeout. ^self on: socket it holds locally a socket (with semaphores registered) but on exception time the reference to the socket gets lost and the semaphores stay registered. The only way to unregister is on finalization time but I think it should work better. So I would add a destroy before the exception is raised. Socket>>#connectTo: hostAddress port: port waitForConnectionFor: timeout "Initiate a connection to the given port at the given host address. Waits until the connection is established or time outs." self connectNonBlockingTo: hostAddress port: port. self waitForConnectionFor: timeout ifTimedOut: [ self destroy. ConnectionTimedOut signal: 'Cannot connect to ' , (NetNameResolver stringFromAddress: hostAddress) , ':' , port asString] I opened a ticket at https://pharo.fogbugz.com/f/cases/11797 but I'm not sure how I am supposed to provide fixes made against a pharo2.0 image. Probably I should fix this againt 3.0 but then I'm still a 2.0 user :) Norbert

4 4

How to test the same behavior with different data
by Noury Bouraqadi Oct. 7, 2013

Oct. 7, 2013

Hi, Last ESUG I attended the cool katas session organized by Stephan Eggermont and Laurent Laffont. That was a good opportunity to step back and think about my TDD practices . To experiment with the style proposed by Laurent, I started writing tests for a pong. I ended up having groups of nearly identical tests: -they use exactly the same objects, send the same messages, -but they differ only by values. An example, is testing the motion of the ball towards different directions or collisions with obstacles at different locations or speeds. Now, I wonder what is the best way to express those similar tests? In a short discussion before I leave, Stephane told me about tables of values. It seem that there is such a support in the ruby world in the cucumber framework. Do we have anything similar in Smalltalk world? BTW, the full ESUG conference was great. Thanx to local organizers, and all people that contributed to make it a success. Thanx, Noury Ecole des Mines de Douai http://car.mines-douai.fr/noury --

6 10

[pharo-project/pharo-core]
by GitHub Oct. 7, 2013

Oct. 7, 2013

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

1 0

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

Oct. 7, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=wi… 1 regressions found. Tests.Release.ReleaseTest.testUndeclared

1 0

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

Oct. 7, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=ma… 1 regressions found. Tests.Release.ReleaseTest.testUndeclared

1 0

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

Oct. 7, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=li… 1 regressions found. Tests.Release.ReleaseTest.testUndeclared

1 0

WhatsUp from: 2013-10-07 until: 2013-10-20
by seaside＠rmod.lille.inria.fr Oct. 7, 2013

Oct. 7, 2013

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2013-10-20 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

3 2