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

[ANN] Ephemeron Support is Ready
by Guille Polito June 30, 2016

June 30, 2016

Hi All, Since this morning, in Pharo #60065, Ephemeron support is in the image. Most of the changes are infrastructural, so far transparent for the users. It is important to notice that even while the support is there, it is not enabled by default. Also, this required changes in the virtual machine that are not yet distributed everywhere. For the ones that would like more detail, I invite you to read the following :) * On the infrastructure side - There is support to create Ephemeric classes and load them from monticello - There is a new finalization mechanism (by default disabled) that will process Ephemerons using a finalization queue. This will avoid scanning collections in look for weak objects to finalize ,as it happens now with the WeakDependent mechanism in WeakArray. - System-Finalization features two new classes *Ephemeron* and *EphemeronRegistry*. For the ones that want more details on Ephemerons, you can read the associated paper [1], or the class comment of Ephemeron: I represent ephemeric key-value objects. Ephemerons are key-value objects (subclasses of Association) with special semantics during garbage collection. My special behavior can resumed as follows: - The garbage collection will iterate my instances only if the key is not referenced strongly by another object. - Then, if no strong references to the key are found, then the values of this ephemeron are hold weakly. - Otherwise, the values are hold strongly. In this implementation, an Ephemeron can hold more than one value, which are all treated in the same manner. This ephemeron instance knows its container, which allows the ephemeron to remove itself from a container (such as a Dictionary) upon finalization. !! Example usages In general terms, do not use myself directly. Use instead an Ephemeric container like EphemeronRegistry. An Ephemeron registry will guarantee the collection of keys and values of the object inside the Ephemeron. Otherwise, if you want to use it, you can create an Ephemeron as any association: ephemeron := Ephemeron key: aKey value: aValue. ephemeron container: aContainer. !! Ephemeron Finalization When an ephemeron's key is hold strongly just by the ephemeron itself, the Ephemeron will be mourned (finalized). That means that the VM will: - put the Ephemeron in the mourning queue waiting for the image to take care of mourning - make the Ephemeron non ephemeric. That is, the ephemeron instance cannot be reused. On the image side, the finalization process will send the message #mourn to an Ephemeron. #mourn will #finalize the Ephemeron's key, and remove the Ephemeron from it's container to allow its collection during a subsequent garbage collection. !! More Documentation You can read the associated paper to understand better the semantics of ephemerons: [1]Ephemerons: A New Finalization Mechanism. Barry Hayes. OOPSLA '97 - WARNING: to be able to use ephemerons, you need to use the *latestVm* that has several fixes for making ephemerons work, and you need to enable ephemerons on the image side by evaluating: Smalltalk supportsQueueingFinalization: true. - With latest vm and ephemerons enabled, tests should be green, otherwise they are skipped * From the user point of view: - The Weak registries were not yet migrated to the new finalization mechanism. - We expect nothing will change from the user point of view. Just less memory leaks. * Next steps (in order) 1) Bless the latest vm as stable 2) Enable queueing finalization by default 3) Replace Weak Registry by Ephemeron Registry. Informed by: Guille

6 8

Fwd: Subscription Form to FogBugz
by Tomas Saez Binelli June 30, 2016

June 30, 2016

Hi everybody! I was trying to create an account on Fogbugz during a Sprint using the link posted here: https://pharo.fogbugz.com/ But after filling the form and submiting it, i received the following message: "Incorrect password or username" This is a little bit strange because i was not able to finish the registration and create an account. Sending this email to make the error public. Bye! Tomas

4 5

[pharo-project/pharo-core]
by GitHub June 30, 2016

June 30, 2016

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

1 0

The .changes file should be bound to a single image
by Max Leske June 30, 2016

June 30, 2016

Hi, Opening the same image twice works fine as long as no writes to the .changes file occur. When both images write to the .changes file however it will be broken for both because the offsets for the changes are wrong. This can lead to lost data and predominantly to invalid method source code, which is a pain with Monticello. I suggest that we implement a kind of lock mechanism to ensure that only one image (the first one opened) can write to the .changes file. Iâve opened an issue for Pharo here: https://pharo.fogbugz.com/f/cases/18635/The-changes-file-should-be-bound-to… Cheers, Max

4 8

[pharo-project/pharo-core]
by GitHub June 30, 2016

June 30, 2016

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

1 0

[pharo-project/pharo-core] 59ad9e: 60127
by GitHub June 30, 2016

June 30, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 59ad9eafc76334d06cdba97d22a8ce2c38010146 https://github.com/pharo-project/pharo-core/commit/59ad9eafc76334d06cdba97d… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-06-30 (Thu, 30 Jun 2016) Changed paths: M Kernel-Tests.package/RecursionStopperTest.class/README.md M Kernel-Tests.package/RecursionStopperTest.class/definition.st A Kernel-Tests.package/RecursionStopperTest.class/instance/as yet unclassified/mixedMethod.st A Kernel-Tests.package/RecursionStopperTest.class/instance/as yet unclassified/recursion.st A Kernel-Tests.package/RecursionStopperTest.class/instance/as yet unclassified/setUp.st A Kernel-Tests.package/RecursionStopperTest.class/instance/as yet unclassified/tearDown.st A Kernel-Tests.package/RecursionStopperTest.class/instance/as yet unclassified/testMixedMethod.st M Kernel-Tests.package/RecursionStopperTest.class/instance/as yet unclassified/testNoRecursion.st A Kernel-Tests.package/RecursionStopperTest.class/instance/as yet unclassified/testThreadSafe.st M Kernel-Tests.package/RecursionStopperTest.class/instance/as yet unclassified/testWithRecursion.st A Kernel-Tests.package/RecursionStopperTest.class/instance/as yet unclassified/threadSafe.st M Kernel.package/Halt.class/class/halting/once.st M Kernel.package/Halt.class/class/once-reset/resetHaltOnCount.st M Kernel.package/Halt.class/class/once-reset/resetHaltOnce.st M Kernel.package/RecursionStopper.class/README.md R Kernel.package/RecursionStopper.class/class/api/check.st A Kernel.package/RecursionStopper.class/class/api/default.st M Kernel.package/RecursionStopper.class/class/api/during_.st R Kernel.package/RecursionStopper.class/class/api/off.st R Kernel.package/RecursionStopper.class/class/api/on.st M Kernel.package/RecursionStopper.class/definition.st A Kernel.package/RecursionStopper.class/instance/as yet unclassified/initialize.st A Kernel.package/RecursionStopper.class/instance/as yet unclassified/stopMethod_during_.st A Reflectivity-Tools.package/FlagIconStyler.class/README.md A Reflectivity-Tools.package/FlagIconStyler.class/definition.st A Reflectivity-Tools.package/FlagIconStyler.class/instance/defaults/highlightColor.st A Reflectivity-Tools.package/FlagIconStyler.class/instance/defaults/iconFor_.st A Reflectivity-Tools.package/FlagIconStyler.class/instance/defaults/iconLabel_.st A Reflectivity-Tools.package/FlagIconStyler.class/instance/testing/shouldStyleNode_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60126.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60127.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60126.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60127.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60127 18628 can not put haltOnce in RBScanner methods https://pharo.fogbugz.com/f/cases/18628 18644 IconStyler for "self flag:" https://pharo.fogbugz.com/f/cases/18644 http://files.pharo.org/image/60/60127.zip

1 0

Re: [Pharo-dev] [squeak-dev] The .changes file should be bound to a single image
by David T. Lewis June 29, 2016

June 29, 2016

On Wed, Jun 29, 2016 at 02:00:19PM -0400, David T. Lewis wrote: > Let's not solve the wrong problem folks. I only looked at this for 10 > minutes this morning, and I think (but I am not sure) that the issue > affects the case of saving the image, and that the normal writing of > changes is fine. I am wrong. I spent some more time with this, and it is clear that two images saving chunks to the same changes file will result in corrupted change records in the changes file. It is not just an issue related to the image save as I suggested above. In practice, this is not an issue that either Chris or I have noticed, probably because we are not doing software development (saving method changes) at the same time that we are running RemoteTask and similar. But I can certainly see how it might be a problem if, for example, I had a bunch of students running the same image from a network shared folder. Dave > > Max was running on Pharo, which may or may not be handling changes the > same way. I think he may be seeing a different problem from the one I > confirmed. > > So a bit more testing and verification would be in order. I can't look at > it now though. > > Dave > > > > >> On 29-06-2016, at 10:35 AM, Eliot Miranda <eliot.miranda(a)gmail.com> > >> wrote: > >> > > {snip much rant} > > > >> The most obvious place where this is an issue is where two images are > >> using the same changes file and think they???re appending. Image A seeks > >> to the end of the file, ???writes??? stuff. Image B near-simultaneously > >> does the same. Eventually each process gets around to pushing data to > >> hardware. Oops! And let???s not dwell too much on the problems possible > >> if either process causes a truncation of the file. Oh, wait, I think we > >> actually had a problem with that some years ago. > >> > >> The thing is that this problem bites even if we have a unitary primitive > >> that both positions and writes if that primitive is written above a > >> substrate that, as unix and stdio streams do, separates positioning from > >> writing. The primitive is neat but it simply drives the problem further > >> underground. > > > > > > Oh absolutely - we only have real control over a small part of it. It > > would probably be worth making use of that where we can. > > > >> > >> A more robust solution might be to position, write, reposition, read, > >> and compare, shortening on corruption, and retrying, using exponential > >> back-off like ethernet packet transmission. Most of the time this adds > >> only the overhead of reading what's written. > > > > Yes, for anything we want reliable that???s probably a good way. A limit > > on the number of retries would probably be smart to stop infinite > > recursion. Imagine the fun of an error causing infinite retries of writing > > an error log about an infinite recursion. On an infinitely large Beowulf > > cluster! > > > > It???s all yet another example of where software meeting reality leads to > > nightmares. > > > > > > tim > > -- > > tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim > > If it was easy, the hardware people would take care of it. > > > > > > >

1 0

Catalog Browser timed out
by Ben Coman June 29, 2016

June 29, 2016

When opening the Catalog Browser I am getting connection timed out. Tested from two different Images: * a fresh generator.image from running newImage.sh of the pharo-vm. * my usual PharoLauncher image cheers -ben

2 1

[pharo-project/pharo-core]
by GitHub June 29, 2016

June 29, 2016

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

1 0

[pharo-project/pharo-core] b5353c: 60126
by GitHub June 29, 2016

June 29, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: b5353c0c1e5a672f661df5c23e2a3af5488316c1 https://github.com/pharo-project/pharo-core/commit/b5353c0c1e5a672f661df5c2… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-06-29 (Wed, 29 Jun 2016) Changed paths: M Kernel.package/ManifestKernel.class/class/meta-data - dependency analyser/ignoredDependencies.st A Kernel.package/Object.class/instance/message performing/perform_with_with_with_with_.st M Kernel.package/PharoKernelAssembly.class/class/meta-data/parts.st M Metacello-MC.package/MetacelloPackageSpec.class/instance/gofer/workingCopyNameFor_.st A Rubric-Tests.package/RubAbstractTextAreaTest.class/README.md A Rubric-Tests.package/RubAbstractTextAreaTest.class/definition.st A Rubric-Tests.package/RubEditingAreaTest.class/README.md A Rubric-Tests.package/RubEditingAreaTest.class/definition.st A Rubric-Tests.package/RubEditingAreaTest.class/instance/convenience/sendDoubleClickAt_withShift_.st A Rubric-Tests.package/RubEditingAreaTest.class/instance/convenience/sendMouseClickAt_withShift_.st A Rubric-Tests.package/RubEditingAreaTest.class/instance/convenience/setSelectionFrom_to_text_.st A Rubric-Tests.package/RubEditingAreaTest.class/instance/instance creation/newCharacterBlockIndex_text_.st A Rubric-Tests.package/RubEditingAreaTest.class/instance/running/setUp.st A Rubric-Tests.package/RubEditingAreaTest.class/instance/tests-accessing selection/testMarkBlockPointBlock.st A Rubric-Tests.package/RubEditingAreaTest.class/instance/tests-accessing selection/testModifySelection.st A Rubric-Tests.package/RubEditingAreaTest.class/instance/tests-accessing selection/testMouseClickShiftClick.st A Rubric-Tests.package/RubEditingAreaTest.class/instance/tests-accessing selection/testMouseMoveAfterDoubleClick.st M Rubric.package/RubAbstractTextArea.class/instance/event handling/mouseMove_.st A SUnit-UITesting.package/extension/Morph/instance/simulateClickWith_position_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60125.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60126.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60125.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60126.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60126 18624 SlotIntegrationTest>>testSlotScopeParallelism https://pharo.fogbugz.com/f/cases/18624 18637 Do not use #name method call in MetacelloPackageSpec>>#workingCopyNameFor: https://pharo.fogbugz.com/f/cases/18637 18634 add Object>>perform:with:with:with:with (4 arguments) https://pharo.fogbugz.com/f/cases/18634 18347 Extending current selection after double click does not work https://pharo.fogbugz.com/f/cases/18347 18604 update kernel manifest https://pharo.fogbugz.com/f/cases/18604 http://files.pharo.org/image/60/60126.zip

1 0