November 2017 - Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #280: 17654-SpecPreDebugWindow-and-subclasses-relies-on-doesNotUnderstand-delegation-to-find-the-stackPane
by ci-pharo-ci-jenkins2＠inria.fr Nov. 10, 2017

Nov. 10, 2017

There is a new Pharo build available! The status of the build #280 was: SUCCESS. The Pull Request #461 was integrated: "17654-SpecPreDebugWindow-and-subclasses-relies-on-doesNotUnderstand-delegation-to-find-the-stackPane" Pull request url: https://github.com/pharo-project/pharo/pull/461 Issue Url: https://pharo.fogbugz.com/f/cases/17654 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Metacello we need automated conflict resolution between Baselines and Configurations
by Peter UhnÃ¡k Nov. 10, 2017

Nov. 10, 2017

Hi, as people are increasingly starting to move to git and baselines, it is becoming more and more common that there are loading issues: A depends on B and C B depends on ConfigurationOfX C depends on BaselineOfX and then loading fails on MetacelloConflictingProjectError: Load Conflict between existing BaselineOfStateSpecs [baseline] from github://dionisiydk/StateSpecs:v2.4.x and ConfigurationOfStateSpecs stable from http://www.smalltalkhub.com/mc/dionisiy/StateSpecs/main I imagine that this will become more and more common. Can this be resolved in some automated fashion? Thanks, Peter

2 3

Catalog problem
by Ben Coman Nov. 10, 2017

Nov. 10, 2017

Today I downloaded Pharo and found Catalog to be empty. http://files.pharo.org/platform/Pharo6.1-64-linux.zip cheers -ben

3 3

Tonel line end convention
by Sven Van Caekenberghe Nov. 10, 2017

Nov. 10, 2017

Hi, I am wondering if the current approach regarding the Tonel line end convention is a good idea. TonelWriter>>#newLine ^ OSPlatform current lineEnding Although it is no problem to write Pharo code that transparently deals with (accepts) any line end convention, not specifying a fixed line end convention is bound to lead to version control problems, in my opinion. Person 1 on platform A has line end convention #cr. After editing a single method, the .class.st is generated. Now the whole file is using #cr. From the standpoint of the version control system, *every* line is now potentially changed (when the previous line end convention was different). Or am I missing something that mitigates this ? Sven

4 4

[Pharo 7.0-dev] Build #279: 20363-ThemeIconsdownloadTo-has-an-argument-which-is-never-referenced-in-code
by ci-pharo-ci-jenkins2＠inria.fr Nov. 10, 2017

Nov. 10, 2017

There is a new Pharo build available! The status of the build #279 was: SUCCESS. The Pull Request #453 was integrated: "20363-ThemeIconsdownloadTo-has-an-argument-which-is-never-referenced-in-code" Pull request url: https://github.com/pharo-project/pharo/pull/453 Issue Url: https://pharo.fogbugz.com/f/cases/20363 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

CRC checks of downloads fail really often
by Guillermo Polito Nov. 10, 2017

Nov. 10, 2017

Hi, In the travis jobs of many projects (pillar, ossubprocess), I see often this failure: image.eqoxhz/Pharo7.0-32bit-b648168.image bad CRC 298b4e64 (should be 85ee6276) This is happening all the time for large builds, generally in 1 out of 4 jobs: https://travis-ci.org/marianopeck/OSSubprocess/builds/299269491 https://travis-ci.org/pillar-markup/pillar/jobs/298538119 Of course restarting the job (to retry the download) solves the problem eventually. Is this because of the inria infrastructure working funny? -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

4 4

[Pharo 7.0-dev] Build #278: 20667-Be-able-to-install-breakpoints-by-clicking-on-segment-icons-area
by ci-pharo-ci-jenkins2＠inria.fr Nov. 9, 2017

Nov. 9, 2017

There is a new Pharo build available! The status of the build #278 was: SUCCESS. The Pull Request #459 was integrated: "20667-Be-able-to-install-breakpoints-by-clicking-on-segment-icons-area" Pull request url: https://github.com/pharo-project/pharo/pull/459 Issue Url: https://pharo.fogbugz.com/f/cases/20667 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[IMPORTANT] Is there a bug in Tonel with category:
by Stephane Ducasse Nov. 9, 2017

Nov. 9, 2017

Hi I was working in cleaning the users of asLayoutFrame and when I commit I see - #category : 'Morphic-Base-Layouts' + #category : #Morphic-Base-Layouts but #category : #Morphic-Base-Layouts is not a valid symbol. So is it a bug? Stef

8 23

LayoutFrame bug
by Nicolas Cellier Nov. 9, 2017

Nov. 9, 2017

Hi, don't you get nice red-cross when opening a browser and selecting comment? (Pharo7.0-32bit-b5ec533.image) The problem is LayoutFrame having a Point instead of Number in fraction/offset inst. var. So I defined two horrible hacks in order to be able to work with Pharo Point>>@ n ^x @ n Point>>asInteger ^x asInteger then could instrument the LayoutFrame inst. var. setters with horrible checks like: aNumber isNumber ifFalse: [ self halt]. And after a few seconds of IDE usage: AbstractNautilusUI>>buildCodePanelWithCommentOnRight ...snip... sourceCodePanel addMorph: commentWidget fullFrame: (LayoutFrame identity leftFraction: 0.5@0 ; leftOffset: delta). Huh! it's as pleasant as not eating own dog food I think this comes from a recent refactoring. I can hardly use in image tools to trace it. Iceberg bugs, MC has lost ancestry and is just good at synchronizing disk working copy with image working copy, but there is github & git API: https://github.com/pharo-project/pharo/commit/042baad47fddb63db2dd0beefeec6… As it's nearly impossible to make giant refactorings like this without human error, and as it's as impossible to review pull request with many lines of code, I wonder if it is possible to automate those with rewrite rules... I let you finish the work (open issue, patch, commit, etc...)

4 5

[Pharo 7.0-dev] Build #273: 20661-Fixing-test-from-debugger-should-mark-test-as-green-when-proceed-
by ci-pharo-ci-jenkins2＠inria.fr Nov. 9, 2017

Nov. 9, 2017

There is a new Pharo build available! The status of the build #273 was: SUCCESS. The Pull Request #456 was integrated: "20661-Fixing-test-from-debugger-should-mark-test-as-green-when-proceed-" Pull request url: https://github.com/pharo-project/pharo/pull/456 Issue Url: https://pharo.fogbugz.com/f/cases/20661 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

2 1