- Pharo-dev - lists.pharo.org

Moving from mc to tonel?
by Martin Dias Jan. 25, 2018

Jan. 25, 2018

Hi all, I'm considering to move Epicea (+Ombu+Hiedra) to github. I read that tonel is the new format and there is Peter's git-migration, which could be the tool to do it. Is it good idea to move now? Is it the right tool? Bests, MartÃn

9 20

Re: [Pharo-dev] [ANN] Next Pharo release moved to end of year
by philippe.back＠highoctane.be Jan. 25, 2018

Jan. 25, 2018

Sounds like a realistic plan. Good to read that. I have the impression that Pharo 3, Pharo 5, Pharo 7 will be the solid releases. Are we having a pattern here? Phil On Jan 23, 2018 14:20, "Esteban Lorenzano" <estebanlm(a)gmail.com> wrote: Hi all, After some analysis of current condition of development, we decided to move the upcoming release to end of the year (and not May, as usual). The reason is that we are taking more time than expected to finish/polish a quantity of things that needs to be finish to call this a âsuccessful releaseâ to make us feel confortable with a release early this year. Thing isâ¦ we were very ambitious with this version, because a lot of small pieces get into position and we decided to act. Now, to deliver a good version, we need to finish them. For example, along with all the stabilisation phase we need to operate on P7 (an usual task for every version), we still need to finish this important changes: - fullblocks as default - vm 64bits: stabilise and add win64 - stateful traits - calypso (and nautilus removal) - iceberg: fix the UI We (the core team and the community) have a deep commitment with the progress of Pharo, and we will continue get things right to make the continue improvement a pleasant experience. Say that, expect new announcement of things finished and ready to test next weeks :) cheers! Esteban

1 0

Pavel's ChangeLog week of 2018-01-15
by Pavel Krivanek Jan. 24, 2018

Jan. 24, 2018

Hi, - continuing on Ring 2 integration - work on Magma port to Pharo. It's very far from being in a usable state but some progress has been done: - make packages from the version 1.6-tests loadable, baseline - fix tests for collections (except two weak related) are green - fix indexing tests - object serialization tests are green except the tests for serialization of context Cheers, -- Pavel

3 2

[Pharo 7.0-dev] Build #446: 21046-small-speedup-for-reading-code-of-methods-with-EmbeddedSource
by ci-pharo-ci-jenkins2＠inria.fr Jan. 24, 2018

Jan. 24, 2018

There is a new Pharo build available! The status of the build #446 was: SUCCESS. The Pull Request #709 was integrated: "21046-small-speedup-for-reading-code-of-methods-with-EmbeddedSource" Pull request url: https://github.com/pharo-project/pharo/pull/709 Issue Url: https://pharo.fogbugz.com/f/cases/21046 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #444: 20896-ImagePresenter-comment-show-code-that-does-not-exist
by ci-pharo-ci-jenkins2＠inria.fr Jan. 24, 2018

Jan. 24, 2018

There is a new Pharo build available! The status of the build #444 was: FAILURE. The Pull Request #704 was integrated: "20896-ImagePresenter-comment-show-code-that-does-not-exist" Pull request url: https://github.com/pharo-project/pharo/pull/704 Issue Url: https://pharo.fogbugz.com/f/cases/20896 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #443: 20912-GoferOperationTestrunCase-method-just-calls-super---can-we-remove-it
by ci-pharo-ci-jenkins2＠inria.fr Jan. 24, 2018

Jan. 24, 2018

There is a new Pharo build available! The status of the build #443 was: FAILURE. The Pull Request #702 was integrated: "20912-GoferOperationTestrunCase-method-just-calls-super---can-we-remove-it" Pull request url: https://github.com/pharo-project/pharo/pull/702 Issue Url: https://pharo.fogbugz.com/f/cases/20912 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Two small changes to get.pharo.org: Link to 64 bit and SSL
by Marcus Denker Jan. 24, 2018

Jan. 24, 2018

Hi, We did two small changes to http://get.pharo.org <http://get.pharo.org/> 1) all links are https: links. -> important to not use http for security (man in the middle attacks) 2) We added an explicit link to https://get.pharo.org/64/ <https://get.pharo.org/64/> Pharo 64bit version Pharo 64bit versions can be found here: https://get.pharo.org/64 <https://get.pharo.org/64> Marcus

1 0

[Pharo 7.0-dev] Build #442: 21018-Add-truncate-methods-on-WriteStreams
by ci-pharo-ci-jenkins2＠inria.fr Jan. 24, 2018

Jan. 24, 2018

There is a new Pharo build available! The status of the build #442 was: SUCCESS. The Pull Request #695 was integrated: "21018-Add-truncate-methods-on-WriteStreams" Pull request url: https://github.com/pharo-project/pharo/pull/695 Issue Url: https://pharo.fogbugz.com/f/cases/21018 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #441: 21043-ContextlookupSymbol-implements-a-wrong-lookup-and-should-reuse-the-lookup-of-the-rest-of-the-image
by ci-pharo-ci-jenkins2＠inria.fr Jan. 24, 2018

Jan. 24, 2018

There is a new Pharo build available! The status of the build #441 was: SUCCESS. The Pull Request #699 was integrated: "21043-ContextlookupSymbol-implements-a-wrong-lookup-and-should-reuse-the-lookup-of-the-rest-of-the-image" Pull request url: https://github.com/pharo-project/pharo/pull/699 Issue Url: https://pharo.fogbugz.com/f/cases/21043 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Cannot debug startUp methods
by Vincent.Blondeau＠lamresearch.com Jan. 23, 2018

Jan. 23, 2018

Hi, In the latest version of Pharo (Build 439 - sha 4810710), I would like to debug a startup script, but when I set up an halt in the method, the image is not able to start anymore... For example, when putting an halt in LanguageEnvironment class>>startUp self halt. self clearDefault. And restarting the image, I got this trace: [0mLanguageEnvironment class>>startUp LanguageEnvironment class(Behavior)>>startUp: ClassSessionHandler>>startup: [ :arg2 | arg2 startup: arg1 ] in WorkingSession>>runStartup: in Block: [ :arg2 | arg2 startup: arg1 ] [ arg2 value: arg3 ] in [ :arg3 | [ arg2 value: arg3 ] on: Exception do: [ :arg4 | self errorHandler handleError: arg4 ] ] in WorkingSession>>runList:do: in Block: [ arg2 value: arg3 ] BlockClosure>>on:do: [ :arg3 | [ arg2 value: arg3 ] on: Exception do: [ :arg4 | self errorHandler handleError: arg4 ] ] in WorkingSession>>runList:do: in Block: [ :arg3 | ... Array(SequenceableCollection)>>do: WorkingSession>>runList:do: WorkingSession>>runStartup: WorkingSession>>start: SessionManager>>launchSnapshot:andQuit: [ tmp3 := self launchSnapshot: arg1 andQuit: arg2. tmp1 signal ] in SessionManager>>snapshot:andQuit: in Block: [ tmp3 := self launchSnapshot: arg1 andQuit: arg2....etc... [ self value. Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value.... WorkingSession>> runList:do: should have catched the exception and opened the image, but I do not seems too.... What can I do to resolve this issue? I forgot to say that I am under Windows 10 ;) Thanks in advance for your help, Cheers, Vincent

1 0