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

Re: [Pharo-dev] Metacello/Iceberg detached head of cascade loaded requirements

by Gabriel Cotelli

If the dependencies are pinned to a git tag it's a normal situation. You don't need to do nothing unless you want to change some of the code in the dependencies in which case just create a branch On Sat, May 11, 2019, 05:40 Ben Coman <btc(a)openinworld.com> wrote: > I have a query about "Detached HEAD" status after a Metacello/Iceberg > cascade load of required packages. Starting with the general questions... > Is that a common status for this scenario? > How to leave the status looking good as "Up to date"? > > Here is a case example... > To avoid the a Filetree repo "filename too long" error on Windows, > I pre-cloned the repo to specify s shorter path name... > Repositories > Add > Clone from github.com > Owner: dionisiydk > Project name: Mocketry > Local directory: C:\Temp\Mocketry > Protocol: SSH > > Then in Playground evaluated... > Metacello new > baseline: 'Mocketry'; > repository: 'github://dionisiydk/Mocketry'; > load > > This cascade loaded Ghost and StateSpecs repos leaving them > with a status of "Detached HEAD". > What does this mean? > And how to have these load cleanly so they are left "Up to date" ? > > To ease others testing on Windows, I forked the repo and converted to > Tonel, > so the same result comes by just evaluating.... > Metacello new > baseline: 'Mocketry'; > repository: 'github://bencoman/Mocketry'; > load > > cheers -ben > > P.S. I've issued a PR upstream for the Tonel conversion. > >

May 11, 2019

Metacello/Iceberg detached head of cascade loaded requirements

by Ben Coman

I have a query about "Detached HEAD" status after a Metacello/Iceberg cascade load of required packages. Starting with the general questions... Is that a common status for this scenario? How to leave the status looking good as "Up to date"? Here is a case example... To avoid the a Filetree repo "filename too long" error on Windows, I pre-cloned the repo to specify s shorter path name... Repositories > Add > Clone from github.com Owner: dionisiydk Project name: Mocketry Local directory: C:\Temp\Mocketry Protocol: SSH Then in Playground evaluated... Metacello new baseline: 'Mocketry'; repository: 'github://dionisiydk/Mocketry'; load This cascade loaded Ghost and StateSpecs repos leaving them with a status of "Detached HEAD". What does this mean? And how to have these load cleanly so they are left "Up to date" ? To ease others testing on Windows, I forked the repo and converted to Tonel, so the same result comes by just evaluating.... Metacello new baseline: 'Mocketry'; repository: 'github://bencoman/Mocketry'; load cheers -ben P.S. I've issued a PR upstream for the Tonel conversion.

May 11, 2019

[Pharo 8.0] Build #266: Fix wording typo

by ci-pharo-ci-jenkins2＠inria.fr

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

May 11, 2019

[Pharo 8.0] Build #265: 3312-KMKeymapnotifyPartialMatchTo-leads-to-an-error

by ci-pharo-ci-jenkins2＠inria.fr

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

May 10, 2019

[Pharo 8.0] Build #264: 3328-SubclassResponsibility-error-when-running-RBParserparseFaultyMethod

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #264 was: SUCCESS. The Pull Request #3329 was integrated: "3328-SubclassResponsibility-error-when-running-RBParserparseFaultyMethod" Pull request url: https://github.com/pharo-project/pharo/pull/3329 Issue Url: https://github.com/pharo-project/pharo/issues/3328 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 10, 2019

introducing my GSoC project - Improving Code Completion

by Myroslava Romaniuk

Hi everyone, My name is Myroslava, I'm a 3rd year CS student in Ukraine, and my project Improving Code Completion has been selected for this year's GSoC. Some of you might know me from the 2 ESUGs I was at or maybe remember me previously doing GSoC in 2017, in any case I'm very happy to have been given this opportunity and I look forward to working with you! I started working on code completion last year during my internship at RMoD with Marcus and Stef, and I really want to make even more progress with code completion this summer and properly implement it inside Pharo as one of the options to use. You can read more about what has been done last summer and what is yet to be done this summer in my proposal (see attached). If you have any feedback or questions, don't hesitate to email me. Help and suggestions throughout my work on the project will be incredibly welcome too, as there's a lot to figure out how to do best. If you are interested in updates or want to keep in touch, I'm also on twitter <https://twitter.com/myroslavarm>, and I have a blog <https://medium.com/@myroslavarm> where I used to post about my progress in the last GSoC and about my internship at RMoD, and I will be writing there this summer, too. I'll also try to be more active in the mailing list and on discord :) Cheers, Myroslava

May 9, 2019

[Pharo 8.0] Build #263: [Fork2]2938 - Fixing FFIConstantHandleType externalType wrong in 64 bit

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #263 was: SUCCESS. The Pull Request #3252 was integrated: "[Fork2]2938 - Fixing FFIConstantHandleType externalType wrong in 64 bit " Pull request url: https://github.com/pharo-project/pharo/pull/3252 Issue Url: https://github.com/pharo-project/pharo/issues/2938 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 9, 2019

[Pharo 8.0] Build #262: 2261-DarkTheme-depends-on-Shout

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #262 was: SUCCESS. The Pull Request #3210 was integrated: "2261-DarkTheme-depends-on-Shout" Pull request url: https://github.com/pharo-project/pharo/pull/3210 Issue Url: https://github.com/pharo-project/pharo/issues/2261 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 9, 2019

[Pharo 8.0] Build #261: 2598-isSpecial-is-not-an-explicit-name-for-a-method

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #261 was: FAILURE. The Pull Request #3318 was integrated: "2598-isSpecial-is-not-an-explicit-name-for-a-method" Pull request url: https://github.com/pharo-project/pharo/pull/3318 Issue Url: https://github.com/pharo-project/pharo/issues/2598 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 9, 2019

[Pharo 8.0] Build #260: 3316-Slots-more-tests-improve-comments-improve-Initialized-slots

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #260 was: SUCCESS. The Pull Request #3317 was integrated: "3316-Slots-more-tests-improve-comments-improve-Initialized-slots" Pull request url: https://github.com/pharo-project/pharo/pull/3317 Issue Url: https://github.com/pharo-project/pharo/issues/3316 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 8, 2019