- Pharo-dev - lists.pharo.org

Techtalk starting: Genetic Algorithms
by Marcus Denker Jan. 30, 2018

Jan. 30, 2018

TechTalk is starting now. Link is: https://www.youtube.com/watch?v=ZB1U259wPaA Pharo TechTalk: Genetic Algorithms https://association.pharo.org/event-2757884

1 0

[Pharo 7.0-dev] Build #480: 21179-sendersOfCritic-should-not-use-AbstractTool
by ci-pharo-ci-jenkins2＠inria.fr Jan. 30, 2018

Jan. 30, 2018

There is a new Pharo build available! The status of the build #480 was: SUCCESS. The Pull Request #774 was integrated: "21179-sendersOfCritic-should-not-use-AbstractTool" Pull request url: https://github.com/pharo-project/pharo/pull/774 Issue Url: https://pharo.fogbugz.com/f/cases/21179 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #479: 21171-allMethodsWithSourceStringmatchCase-should-not-sort-
by ci-pharo-ci-jenkins2＠inria.fr Jan. 30, 2018

Jan. 30, 2018

There is a new Pharo build available! The status of the build #479 was: SUCCESS. The Pull Request #775 was integrated: "21171-allMethodsWithSourceStringmatchCase-should-not-sort-" Pull request url: https://github.com/pharo-project/pharo/pull/775 Issue Url: https://pharo.fogbugz.com/f/cases/21171 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #478: 21164-EncoderForSistaV1-update
by ci-pharo-ci-jenkins2＠inria.fr Jan. 30, 2018

Jan. 30, 2018

There is a new Pharo build available! The status of the build #478 was: SUCCESS. The Pull Request #741 was integrated: "21164-EncoderForSistaV1-update" Pull request url: https://github.com/pharo-project/pharo/pull/741 Issue Url: https://pharo.fogbugz.com/f/cases/21164 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Issue Tracker] Problem with Spam
by Marcus Denker Jan. 30, 2018

Jan. 30, 2018

Hi, Since some days we get ~20 spam cases per day on the issue tracker. -> I have asked on the Forums what we can do -> As long as there is no solution, I am closing them the morning. Marcus

2 3

[Pharo 7.0-dev] Build #477: 21175-ReleaseTest-testUndeclared-should-allow-stubs-for-test-purpose
by ci-pharo-ci-jenkins2＠inria.fr Jan. 30, 2018

Jan. 30, 2018

There is a new Pharo build available! The status of the build #477 was: SUCCESS. The Pull Request #773 was integrated: "21175-ReleaseTest-testUndeclared-should-allow-stubs-for-test-purpose" Pull request url: https://github.com/pharo-project/pharo/pull/773 Issue Url: https://pharo.fogbugz.com/f/cases/21175 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

How to add a new rule?
by Stephane Ducasse Jan. 30, 2018

Jan. 30, 2018

Hi yuriy We defined a new rule subclass of RBTransformationRule and we did not get why the rule was not taken into account. We put an halt in another class such as ifNotNilDo: in - initialize (is there a cache)? - checkMethod: and it did not stop. We started to to watch your ESUG videos to read your PhD but it did not help us. Stef

2 5

How to get rid of empty XML nodes?
by Stephane Ducasse Jan. 29, 2018

Jan. 29, 2018

)Hi we are manipulating an XML document and I would like to get rid of the spurious empty string. We saw that the gt panes are doing it. (aNodeWithElements isStringNode and: [aNodeWithElements isEmpty or: [aNodeWithElements isWhitespace]] Is there a way not to produce empty nodes? Is there a simple way not to have to handle them Now each time we are dealing with a node with have to check. Stef

3 10

Iceberg UI feedback - synchronise v. status
by Ben Coman Jan. 29, 2018

Jan. 29, 2018

I hear Iceberg UI is getting a redesign. To feed into that... I'm trying to analyse myself, why I've not been comfortable with the "Synchronise..." menu item. I think maybe its because that term feels like an "action" that going to "do something" when I'm not sure what that something is. But as I'm getting familiar with Iceberg it seems that "Synchronise" might not change the state of anything, but first shows current "status" like a combination of `git status` and `git diff` from the shell, and presents buttons and tabs where you *then* perform actions that actually change the state of the system. So I may have the wrong end of the stick, but perhaps replacing "Synchronise..." with "Status..." might seem less intimidating. HTH, cheers -ben

2 2

CI Hickups ...
by Torsten Bergmann Jan. 29, 2018

Jan. 29, 2018

While our general build from Pharo 7 is (more or less often) green https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… I've noticed more and more that the CI builds for the PR's to Pharo 7 even for trivial changes are often broken and not green https://github.com/pharo-project/pharo/pulls which is annoying and one still has the feeling to break the builds. As always I think getting a more stable CI is dependent on time, resources and priorities. But does anyone know if this is a general issue or something that is already worked on? Thx T.

4 7