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

Re: [Pharo-dev] PhD starting in January/February 2020 on Advanced debugging with Pharo

by jean baptiste arnaud

I really tried to be nice here but you really do not make my task easy here. So, let's be more specific: I strongly dislike the usage of this interview of me in this specific context. Next time please use my linked in account it is also public. Or better ask me, before. I dont care if you really understand why this piss me off that hard. And I really consider there are enough toxicity in this community to not add my bile here. You are at a crossroad here, been correct, professional and respectful. And say: "ok, it will not happen again" And respect me as a person. And we can continue this strange and friendly relationship. Or: Continue on the "I do whatever I want this is public." And finally showing me that you have literally 0 respect for me. Your life your choice. Huge bonus is you say "I am sorry" even in private, but I guess this is stopping be you. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#m_-796003953242991761_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> Le jeu. 10 oct. 2019 Ã 15:03, ducasse <stepharo(a)netcourrier.com> a Ã©crit : > JB I think that this blog post is not yours. > And this is not even ours. It is available. We just listed it here because > it was available. > > Stef > > > On 10 Oct 2019, at 14:57, jean baptiste arnaud <jbaptiste.arnaud(a)gmail.com> > wrote: > > It is really nice to put me as reference here, even if it is without my > consent. Whatever I will embrace the charge if someone is interested by > conduct a PhD with rmod I will be more than happy to share my experience > feedback with them. The good part, they are a lot of them and the bad part, > they are some of them. Feel free to contact me. > But please the next time ask me before. > > >> >> >> >

Oct. 11, 2019

[Pharo 8.0] Build #866: Remove-code-that-should-not-be-in-pharo

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

There is a new Pharo build available! The status of the build #866 was: FAILURE. The Pull Request #4895 was integrated: "Remove-code-that-should-not-be-in-pharo" Pull request url: https://github.com/pharo-project/pharo/pull/4895 Issue Url: https://github.com/pharo-project/pharo/issues/Remove 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 Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > it would be the following change This seems to be non-backward compatible (e.g. removal of `FileReference >> binaryReadWriteStream`). That doesn't seem like a good idea on a released stable version with a new version due for release in months. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 11, 2019

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

by Sven Van Caekenberghe

> On 11 Oct 2019, at 17:03, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Sven, > > > On Fri., 11 Oct. 2019, 15:05 Sven Van Caekenberghe, <sven(a)stfx.eu> wrote: > > > > On 11 Oct 2019, at 14:49, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > > > On Fri, Oct 11, 2019 at 2:32 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> > >> 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. > >> > > > > Hi Sven, > > > > One thing that must be know is that everything going in the Pharo 7 > > branch is not released directly. > > The changes you talk about are in no release currently. A release is > > launched manually currently when important changes are backported and > > stabilized. > > Hmm, OK, the /64/70+vm zeroconf version is indeed Pharo 7.0.4 build: 168, commit: ccd1f64 which does still load Zn correctly, I just tested that again. > > But how come some users are reporting problems then ? Is there a way they can access that unreleased version, maybe via the launcher ? > > Exactly... The launcher appears to download the latest snapshot. That is not good then, at least we should tell regular users *not* to do that, but pick the latest *stable* release. > Cheers, > Alistair > (on phone)

Oct. 11, 2019

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

by Alistair Grant

Hi Sven, On Fri., 11 Oct. 2019, 15:05 Sven Van Caekenberghe, <sven(a)stfx.eu> wrote: > > > > On 11 Oct 2019, at 14:49, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> > wrote: > > > > On Fri, Oct 11, 2019 at 2:32 PM Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > >> > >> 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. > >> > > > > Hi Sven, > > > > One thing that must be know is that everything going in the Pharo 7 > > branch is not released directly. > > The changes you talk about are in no release currently. A release is > > launched manually currently when important changes are backported and > > stabilized. > > Hmm, OK, the /64/70+vm zeroconf version is indeed Pharo 7.0.4 build: 168, > commit: ccd1f64 which does still load Zn correctly, I just tested that > again. > > But how come some users are reporting problems then ? Is there a way they > can access that unreleased version, maybe via the launcher ? > Exactly... The launcher appears to download the latest snapshot. Cheers, Alistair (on phone) > > >

Oct. 11, 2019

[Pharo 8.0] Build #865: FAILURE

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

There is a new Pharo build available! The status of the build #865 was: FAILURE. Could not extract further issue information from commit message: Update stale.yml - Set to true to ignore issues in a project - Set to true to ignore issues with an assignee Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 11, 2019

[Pharo 8.0] Build #864: Revert "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 #864 was: FAILURE. The Pull Request #4894 was integrated: "Revert "Add new #printOneLineString and related methods"" Pull request url: https://github.com/pharo-project/pharo/pull/4894 Issue Url: https://github.com/pharo-project/pharo/issues/revert 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

> On 11 Oct 2019, at 14:49, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > On Fri, Oct 11, 2019 at 2:32 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> 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. >> > > Hi Sven, > > One thing that must be know is that everything going in the Pharo 7 > branch is not released directly. > The changes you talk about are in no release currently. A release is > launched manually currently when important changes are backported and > stabilized. Hmm, OK, the /64/70+vm zeroconf version is indeed Pharo 7.0.4 build: 168, commit: ccd1f64 which does still load Zn correctly, I just tested that again. But how come some users are reporting problems then ? Is there a way they can access that unreleased version, maybe via the launcher ? >> >> > > > -- > Cyril Ferlicot > https://ferlicot.fr >

Oct. 11, 2019

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

by Cyril Ferlicot

On Fri, Oct 11, 2019 at 2:32 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > 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. > Hi Sven, One thing that must be know is that everything going in the Pharo 7 branch is not released directly. The changes you talk about are in no release currently. A release is launched manually currently when important changes are backported and stabilized. > > -- Cyril Ferlicot https://ferlicot.fr

Oct. 11, 2019

[Pharo 8.0] Build #863: Improve-browse-rule-command

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

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

Oct. 11, 2019