February 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] were the fixes of Mark integrated? Because rename instance variable looks broken

by Marcus Denker

> On 26 Feb 2015, at 16:09, stepharo <stepharo(a)free.fr> wrote: > > When I select an instance variable shortcut and I want to rename it using Smart Suggestions > I get > > shortcutHolderHolder in my method. > everything is integrated. Marcus

Feb. 26, 2015

instance variable rename is deeply broken....

by stepharo

This was a BAD IDEA to rename naively accessors when we rename an instance variable. Now I cannot use instance renaming because of the ripple effects I do not control. And I just got an emergency evaluator when I simply wanted to rename an instance variable in ButtonModel :( Mark do you know if your changes go integrated? Because now I will work without refactoring and I have all the spec classes to change. Not fun. Stef

Feb. 26, 2015

[pharo-project/pharo-core]

by GitHub

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

Feb. 26, 2015

[pharo-project/pharo-core] a5b1bb: 40514

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: a5b1bb2acb02b3580a0ad2bb2792a3468bf619da https://github.com/pharo-project/pharo-core/commit/a5b1bb2acb02b3580a0ad2bb… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-02-26 (Thu, 26 Feb 2015) Changed paths: M AsmJit-Tests.package/AJx64AssemblerTests.class/instance/tests/testStringOps64Mnemonics.st M AsmJit-Tests.package/AJx86AssemblerTests.class/instance/tests/testStringOpMnemonics.st M AsmJit-x86.package/AJx86InstructionDescription.class/instance/emitting/emitsmnemonic_operand1_operand2_operand3_.st A Reflectivity-Tests.package/ReflectiveMethodTest.class/README.md A Reflectivity-Tests.package/ReflectiveMethodTest.class/definition.st A Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - creation/testCreateReflectiveMethod.st A Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - creation/testCreateReflectiveMethodAndInvalidate.st A Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - creation/testInvalidate.st A Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - creation/testInvalidateWithLinCount.st A Reflectivity-Tests.package/ReflectivityExamples.class/README.md A Reflectivity-Tests.package/ReflectivityExamples.class/definition.st A Reflectivity-Tests.package/ReflectivityExamples.class/instance/as yet unclassified/exampleMethod.st A Reflectivity.package/ReflectiveMethod.class/README.md A Reflectivity.package/ReflectiveMethod.class/class/as yet unclassified/on_.st A Reflectivity.package/ReflectiveMethod.class/definition.st A Reflectivity.package/ReflectiveMethod.class/instance/accessing/ast.st A Reflectivity.package/ReflectiveMethod.class/instance/accessing/compiledMethod_.st A Reflectivity.package/ReflectiveMethod.class/instance/accessing/linkCount.st A Reflectivity.package/ReflectiveMethod.class/instance/accessing/linkCount_.st A Reflectivity.package/ReflectiveMethod.class/instance/evaluation/recompileAST.st A Reflectivity.package/ReflectiveMethod.class/instance/evaluation/run_with_in_.st A Reflectivity.package/ReflectiveMethod.class/instance/invalidate/createTwin.st A Reflectivity.package/ReflectiveMethod.class/instance/invalidate/destroyTwin.st A Reflectivity.package/ReflectiveMethod.class/instance/invalidate/invalidate.st A Reflectivity.package/ReflectiveMethod.class/instance/reflective operations/doesNotUnderstand_.st A Reflectivity.package/ReflectiveMethod.class/instance/testing/hasLinks.st A Reflectivity.package/extension/CompiledMethod/instance/createTwin.st A Reflectivity.package/extension/CompiledMethod/instance/destroyTwin.st A Reflectivity.package/extension/CompiledMethod/instance/invalidate.st A Reflectivity.package/extension/CompiledMethod/instance/reflectiveMethod.st A Reflectivity.package/extension/CompiledMethod/instance/reflectiveMethod_.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script513.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script514.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40513.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40514.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot.package/WeakSlot.class/README.md A Slot.package/WeakSlot.class/definition.st A Slot.package/WeakSlot.class/instance/as yet unclassified/emitStore_.st A Slot.package/WeakSlot.class/instance/as yet unclassified/emitValue_.st A Slot.package/WeakSlot.class/instance/as yet unclassified/initialize_.st A Slot.package/WeakSlot.class/instance/as yet unclassified/read_.st A Slot.package/WeakSlot.class/instance/as yet unclassified/wantsInitalization.st A Slot.package/WeakSlot.class/instance/as yet unclassified/write_to_.st Log Message: ----------- 40514 14999 Twin: add base for Reflectivity https://pharo.fogbugz.com/f/cases/14999 14033 Failing test: AJx64AssemblerTests>#testStringOps64Mnemonics https://pharo.fogbugz.com/f/cases/14033 14998 Add WeakSlot https://pharo.fogbugz.com/f/cases/14998 http://files.pharo.org/image/40/40514.zip

Feb. 26, 2015

Recording user actions in GTools

by Andrei Chis

Hi, In order to better understand how people use the GT tools we would like to integrate, before the Pharo code freeze, a small extension to GT tools (300 lines of code) that records and sends usage data. The recording of data will be opt-out: *you have to explicitly agree with sending usage data*. The first time you open a GT tool, that tool will embed a small UI asking you if you want to enable data submission. We will save the setting in the your preference directory so it will be shared between all your local images. You can change this setting at any time from the Settings Browser. For now we will only like to collect data about Spotter. *By default we will only collect anonymous data *about various actions you do in spotter (open, close, search, dive-in, dive-out, select element, etc) without collecting any data what about what query you enter or what search results you get. We would also add an optional setting for sending the query text and selected elements. We will send then the data periodically to our server and when you close the image. The data that will be send is rather small: 1000 actions require 7kb of data. Thus sending an entire day worth of recordings, if all you did that day was searching, should be around 1MB of data. The recording does not influence the performance of Spotter. Spotter already generates all events of interest as announcements. To enable recording we just register a subscriber with the Spotter announcer and store the events of interest. We would like to get your opinion on this. Cheers, GT team

Feb. 26, 2015

were the fixes of Mark integrated? Because rename instance variable looks broken

by stepharo

When I select an instance variable shortcut and I want to rename it using Smart Suggestions I get shortcutHolderHolder in my method. Stef

Feb. 26, 2015

Re: [Pharo-dev] OSProcess bug ?

by Ben Coman

On Thu, Feb 26, 2015 at 12:05 AM, David T. Lewis <lewis(a)mail.msen.com> wrote: > Hi Jannik, > > One other thing I just thought of: Check and see if your rostopic program > is actually writing to standard output, as opposed to writing directly to > /dev/tty. From a terminal window, I think you could do this: > > $ rostopic > out.txt > > > Would using a pipe better represent the interaction with OSProcess? e.g... $ rostopic | tail cheers -ben

Feb. 26, 2015

Re: [Pharo-dev] [regression reporter]regression occurred

by Sven Van Caekenberghe

> On 26 Feb 2015, at 15:35, Ben Coman <btc(a)openInWorld.com> wrote: > >> On Feb 25, 2015 3:58 PM, "Sven Van Caekenberghe" <sven(a)stfx.eu> wrote: >> Number>>#brickValue: must die ! >> >> > On 25 Feb 2015, at 15:53, no-reply(a)ci.inria.fr wrote: >> > >> > https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-2.1-Validation-A-L/labe… >> > >> > 1 regressions found. >> > KernelTests.Numbers.NumberTest.testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses >> >> > > On Wed, Feb 25, 2015 at 4:07 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> On 25 Feb 2015, at 16:04, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: >> It is already fixed and will be integrated with GT >> > When will this happen? this test fails since *WEEKS*, yet I could have fixed it in 5 minutes. But I canât. > We make ourselves completely powerless. This does not make me feel good. > > On Wed, Feb 25, 2015 at 11:11 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > > Normally GT should be released more often. This time while Jenkins was down we did a lot of changes and now it takes some time to prepare everything for integration. Also at the moment of previous release moose didn't run tests like BehaviourTest and others. :) > > > > Thats a fair reason, but philosophically we still have a feature branch holding up a bug fix, because we have a a single-branch workflow. Consider a future where Pharo has more external packages, where a hypothetical package (with less diligent developers than GT) has a longer feature development cycle. Should bug fixes be held up? Or should external packages have a bug-fix-branch and a feature-development-branch - with a workflow where before the feature-development-branch is integrated, it merges in any bug-fix-branch commits. I think that in certain cases (something urgent, something really annoying) it would be OK to patch it directly. It is then up to the external package maintainers to pick up the change up stream. Working with components/modules should not limit what we do. Of course, for new features this would not be OK. > p.s. It would be interesting if we could get a github-style commit network graph derived from mcz files. > > cheers -ben >

Feb. 26, 2015

Re: [Pharo-dev] [pharo-project/pharo-core]

by Serge Stinckwich

There is a git tag for each Pharo releases: https://github.com/pharo-project/pharo-core/releases On Thu, Feb 26, 2015 at 3:32 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Just wondering: is there any meaning to these emails from github? > > Cheers, > Alexandre > > >> On Feb 26, 2015, at 11:29 AM, GitHub <noreply(a)github.com> wrote: >> >> Branch: refs/tags/40513 >> Home: https://github.com/pharo-project/pharo-core > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Feb. 26, 2015

Re: [Pharo-dev] [pharo-project/pharo-core]

by Marcus Denker

> On 26 Feb 2015, at 15:32, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Just wondering: is there any meaning to these emails from github? > No. Maybe https://zapier.com <https://zapier.com/> is a solutionâ¦ they have a very good email parser. -> send this mail to zapper -> swallow it -> the other mail, parse out the interesting stuff and send a new mail to the list. It is on my TODO, like 1000 other things. Marcus

Feb. 26, 2015