September 2019 - Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #786: 4670-Deprecation-transfrom-make-sure-the-fallback-is-signal
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2019

Sept. 26, 2019

There is a new Pharo build available! The status of the build #786 was: FAILURE. The Pull Request #4723 was integrated: "4670-Deprecation-transfrom-make-sure-the-fallback-is-signal" Pull request url: https://github.com/pharo-project/pharo/pull/4723 Issue Url: https://github.com/pharo-project/pharo/issues/4670 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #785: OpalSemanticCleanup
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2019

Sept. 26, 2019

There is a new Pharo build available! The status of the build #785 was: FAILURE. The Pull Request #4731 was integrated: "OpalSemanticCleanup" Pull request url: https://github.com/pharo-project/pharo/pull/4731 Issue Url: https://github.com/pharo-project/pharo/issues/OpalSemanticCleanup Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

PharoLauncher not opening Pharo 7 image on Mac
by Tudor Girba Sept. 26, 2019

Sept. 26, 2019

Hi, Does any of you ever had the problem of a PharoLauncher that does not want to open the image on Mac? We just installed a PharoLauncher from today, added it in /Applications, and when pressing the play button for a Pharo 7 image, nothing happens. Running the same image with the VM that PharoLauncher downloaded works though. Any idea of what could be wrong? Cheers, Doru -- feenk.com "Some battles are better lost than fought."

1 0

[Pharo 8.0] Build #784: 4701-Review-asInteger-
by ci-pharo-ci-jenkins2＠inria.fr Sept. 25, 2019

Sept. 25, 2019

There is a new Pharo build available! The status of the build #784 was: SUCCESS. The Pull Request #4714 was integrated: "4701-Review-asInteger-" Pull request url: https://github.com/pharo-project/pharo/pull/4714 Issue Url: https://github.com/pharo-project/pharo/issues/4701 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #783: Improve-stability-of-Docking-bar-morph
by ci-pharo-ci-jenkins2＠inria.fr Sept. 25, 2019

Sept. 25, 2019

There is a new Pharo build available! The status of the build #783 was: FAILURE. The Pull Request #4724 was integrated: "Improve-stability-of-Docking-bar-morph" Pull request url: https://github.com/pharo-project/pharo/pull/4724 Issue Url: https://github.com/pharo-project/pharo/issues/Improve Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #782: 4704-reduce-direct-calls-of-debuggerMap-rangeForPCcontextIsActiveContext
by ci-pharo-ci-jenkins2＠inria.fr Sept. 25, 2019

Sept. 25, 2019

There is a new Pharo build available! The status of the build #782 was: FAILURE. The Pull Request #4707 was integrated: "4704-reduce-direct-calls-of-debuggerMap-rangeForPCcontextIsActiveContext" Pull request url: https://github.com/pharo-project/pharo/pull/4707 Issue Url: https://github.com/pharo-project/pharo/issues/4704 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Difficulty to use Iceberg
by Jan Vrany Sept. 25, 2019

Sept. 25, 2019

Hi, I'm experiencing difficulties (code loss, even) when trying to commit code using Iceberg. I have a project with consist of some Pharo code and some C++ code. Both parts kind of depend on each other. Imagine I start from commit A --- A and build and open Pharo image. Then I do some work in Pharo and commit, leaving me at B: --- A --- B Now I need to make some changes to the C++ code, say C & D: --- A --- B --- C --- D And work little more on C++ but do not commit (therefore I have modified C++ files and/or staged changes). Now imagine I need to do more changes in Pharo image and commit (should be commit E) Now there's the problem. Pharo image thinks it is still at commit B and starts complaining about image being out if sync. What is the correct workflow to end up with: --- A --- B --- C --- D --- E !!! AND !!! with my local modifications to C++ code preserved in working copy? I'd be nice to preserve staged changes too, but I'd be OK to unstage all changes if necessary. Any suggestions? Best, Jan

5 6

[Pharo 8.0] Build #781: Add-example-to-RBRenameClassRefactoring
by ci-pharo-ci-jenkins2＠inria.fr Sept. 25, 2019

Sept. 25, 2019

There is a new Pharo build available! The status of the build #781 was: FAILURE. The Pull Request #4725 was integrated: "Add-example-to-RBRenameClassRefactoring" Pull request url: https://github.com/pharo-project/pharo/pull/4725 Issue Url: https://github.com/pharo-project/pharo/issues/Add Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #780: 2523-Use-NativeFileSystemBrowser-instead-of-just-NativeBrowser
by ci-pharo-ci-jenkins2＠inria.fr Sept. 25, 2019

Sept. 25, 2019

There is a new Pharo build available! The status of the build #780 was: FAILURE. The Pull Request #4631 was integrated: "2523-Use-NativeFileSystemBrowser-instead-of-just-NativeBrowser" Pull request url: https://github.com/pharo-project/pharo/pull/4631 Issue Url: https://github.com/pharo-project/pharo/issues/2523 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #779: Fixed typo in category
by ci-pharo-ci-jenkins2＠inria.fr Sept. 24, 2019

Sept. 24, 2019

There is a new Pharo build available! The status of the build #779 was: FAILURE. The Pull Request #4717 was integrated: "Fixed typo in category" Pull request url: https://github.com/pharo-project/pharo/pull/4717 Issue Url: https://github.com/pharo-project/pharo/issues/fixed Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0