June 2020 - Pharo-dev - lists.pharo.org

[Pharo 9.0] Build #423: FAILURE

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

There is a new Pharo build available! The status of the build #423 was: FAILURE. Could not extract further issue information from commit message: Create mergeable.yml Experiment: instead of requiring a review to be green, we require a review to be mergeable Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 26, 2020

[Pharo 9.0] Build #422: ByteArray asWideString should be in conversion

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

There is a new Pharo build available! The status of the build #422 was: FAILURE. The Pull Request #6685 was integrated: "ByteArray asWideString should be in conversion" Pull request url: https://github.com/pharo-project/pharo/pull/6685 Issue Url: https://github.com/pharo-project/pharo/issues/6684 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 26, 2020

[Pharo 9.0] Build #421: 6549-Better-comment-for-WordArray-and-friends

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

There is a new Pharo build available! The status of the build #421 was: FAILURE. The Pull Request #6686 was integrated: "6549-Better-comment-for-WordArray-and-friends" Pull request url: https://github.com/pharo-project/pharo/pull/6686 Issue Url: https://github.com/pharo-project/pharo/issues/6549 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 26, 2020

[Pharo 9.0] Build #420: Refactor monstrous Process>>#terminate method

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

There is a new Pharo build available! The status of the build #420 was: FAILURE. The Pull Request #6328 was integrated: "Refactor monstrous Process>>#terminate method" Pull request url: https://github.com/pharo-project/pharo/pull/6328 Issue Url: https://github.com/pharo-project/pharo/issues/processTerminateRefactor Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 26, 2020

[Pharo 9.0] Build #419: Nilled weak reference was found in a dictionary

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

There is a new Pharo build available! The status of the build #419 was: FAILURE. The Pull Request #6678 was integrated: "Nilled weak reference was found in a dictionary" Pull request url: https://github.com/pharo-project/pharo/pull/6678 Issue Url: https://github.com/pharo-project/pharo/issues/6677 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 25, 2020

[Pharo 9.0] Build #418: 6532-Incomplete-state-of-method-AST

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

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

June 25, 2020

[Pharo 9.0] Build #417: Introduce Collections-Stack-Tests

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

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

June 25, 2020

Re: [Pharo-dev] Completion Setting Split-Up

by Esteban Lorenzano

Hi Sean, Because NECPreferences is attached to Settings subsystem which is a Morphic component and it will pull all morphic/tools/etc. dependences whenever included/referenced. That way, if we want to split the completion framework from Moprhic/Rubric, we need to inverse the dependency (instead NEEntry depending on NECPreferences, NECPreferences depending on NECEntry). Esteban > On 24 Jun 2020, at 23:34, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Why has NECPreferences `#spaceAfterCompletion` been moved to NECEntry in > Pharo 9? Usability seems a bit worse because the user now has to know about > two objects to configure it. Also, it was originally held in a class-side > instVar, which made it seem like different NECEntry subclasses might have > different behavior and might justify the move, but it is now a class var, > shared by all, and so the behavior seems the same... > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

June 25, 2020

looking for project using Voyage in order to test a redis Driver implementation

by ClÃ©ment Dutriez

Hello, I'm interning for telna (today -> August 2020) , I'm working on implementation of a voyage redis driver. I have finished the first iteration, all voyage-kernel tests are green, so functionally it's work. but in production, I think it will fail. So I'm looking for projects using voyage to test my implementation. if you have advice, qualities criteria, in order to improve my implementation please let me know. RoadMap: 1- [ ] add documentations - [ ] implementation documentation - [ ] documentation in the project (class description ...) 2- [ ] test on other projects I will send another mail with documentation in a few days. Thank you ! -- Dutriez ClÃ©ment

June 25, 2020

[Pharo 9.0] Build #416: Object centric installer reflective view on objects

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

There is a new Pharo build available! The status of the build #416 was: FAILURE. The Pull Request #6673 was integrated: "Object centric installer reflective view on objects" Pull request url: https://github.com/pharo-project/pharo/pull/6673 Issue Url: https://github.com/pharo-project/pharo/issues/Object Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 25, 2020