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

Re: [Pharo-dev] ZnBufferedReadWriteStream vs SourceFileBufferedReadWriteStream/SourceFileCharacterReadWriteStream

by Sven Van Caekenberghe

> On 11 Oct 2019, at 14:27, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > or the fixes/renaming/usage of Pharo 8 must be back ported as well. it would be the following change https://github.com/pharo-project/pharo/pull/4752 https://github.com/pharo-project/pharo/commit/0f9b7d323e87ffb957b8b638d6867… that needs to be applied to Pharo 7 but since this is quite complex, it would be be done by the original author, tesonep also, please make sure Zn can be loaded safely on top

Oct. 11, 2019

[Pharo 8.0] Build #862: 4881-RBImplementedNotSentRule-is-disabled

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

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

Oct. 11, 2019

Re: [Pharo-dev] ZnBufferedReadWriteStream vs SourceFileBufferedReadWriteStream/SourceFileCharacterReadWriteStream

by Sven Van Caekenberghe

I also do not understand how this was done in Pharo 7 *before* it was finalised/fully debugged in Pharo 8. Back-porting must be done very carefully. > On 11 Oct 2019, at 14:27, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > A new implementation of ZnBufferedReadWriteStream was added to Pharo 7, which gets again (partially) overwritten by Zinc HTTP Components, breaking code loading. > > In Pharo 8 this was fixed by renaming these special (and now changed) class(es) to SourceFileBufferedReadWriteStream/SourceFileCharacterReadWriteStream so that they are moved out of Zinc HTTP Components and cannot be overwritten/broken. > > Either the last 3 commits on the Pharo 7 branch must be reversed, or the fixes/renaming/usage of Pharo 8 must be back ported as well. > > This is urgent. > > Sven

Oct. 11, 2019

ZnBufferedReadWriteStream vs SourceFileBufferedReadWriteStream/SourceFileCharacterReadWriteStream

by Sven Van Caekenberghe

Hi, A new implementation of ZnBufferedReadWriteStream was added to Pharo 7, which gets again (partially) overwritten by Zinc HTTP Components, breaking code loading. In Pharo 8 this was fixed by renaming these special (and now changed) class(es) to SourceFileBufferedReadWriteStream/SourceFileCharacterReadWriteStream so that they are moved out of Zinc HTTP Components and cannot be overwritten/broken. Either the last 3 commits on the Pharo 7 branch must be reversed, or the fixes/renaming/usage of Pharo 8 must be back ported as well. This is urgent. Sven

Oct. 11, 2019

[Pharo 8.0] Build #861: RBRefersToClassRule-should-ignore-isAbstract-methods

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

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

Oct. 11, 2019

[Pharo 8.0] Build #860: Add new #printOneLineString and related methods

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

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

Oct. 11, 2019

[Pharo 8.0] Build #859: Add-command-to-browse-rule-class

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

There is a new Pharo build available! The status of the build #859 was: SUCCESS. The Pull Request #4890 was integrated: "Add-command-to-browse-rule-class" Pull request url: https://github.com/pharo-project/pharo/pull/4890 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…

Oct. 11, 2019

[Pharo 8.0] Build #858: Fix #2853. When removing a class, also log its contained methods

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

There is a new Pharo build available! The status of the build #858 was: SUCCESS. The Pull Request #4832 was integrated: "Fix #2853. When removing a class, also log its contained methods" Pull request url: https://github.com/pharo-project/pharo/pull/4832 Issue Url: https://github.com/pharo-project/pharo/issues/2853 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 11, 2019

[Pharo 8.0] Build #857: 4883-FileSystemResolver-should-let-the-user-add-its-own-origins

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

There is a new Pharo build available! The status of the build #857 was: SUCCESS. The Pull Request #4885 was integrated: "4883-FileSystemResolver-should-let-the-user-add-its-own-origins" Pull request url: https://github.com/pharo-project/pharo/pull/4885 Issue Url: https://github.com/pharo-project/pharo/issues/4883 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 11, 2019

Re: [Pharo-dev] Easy first issues for Pharo contributors?

by ducasse

> On 11 Oct 2019, at 06:20, James Foster <Smalltalk(a)JGFoster.net> wrote: > > Stef, > > I see that you added executable comments tasks to the âSimple Issues for Beginnersâ project. Thanks! > > Another idea I had is method category cleanup. While there is some judgment involved in many of the category names, I see several names that are misspellings (starting with 'accessingâ). I donât know if you want to add a task for that as well, or we can just open pull requests. Yes I have a little tool for that the automatic method categorizer It has some methods for doing analysis and also fixing system wide problems. Stef

Oct. 11, 2019