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

[Pharo 8.0] Build #874: AbstractTool DeadCode remove

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

There is a new Pharo build available! The status of the build #874 was: SUCCESS. The Pull Request #4918 was integrated: "AbstractTool DeadCode remove" Pull request url: https://github.com/pharo-project/pharo/pull/4918 Issue Url: https://github.com/pharo-project/pharo/issues/AbstractToolDeadCode Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 16, 2019

[Pharo 8.0] Build #873: Fix Issue 4693

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

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

Oct. 16, 2019

[Pharo 8.0] Build #872: CodeCompletionLessSorting

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

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

Oct. 15, 2019

[Pharo 8.0] Build #871: 4910-OCCleanBokTest-should-be-renamed

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

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

Oct. 15, 2019

[Pharo 8.0] Build #870: Improve #printString implementations

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

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

Oct. 14, 2019

[Pharo 8.0] Build #869: Completion: Reduce Copying of intermediate collections

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

There is a new Pharo build available! The status of the build #869 was: FAILURE. The Pull Request #4899 was integrated: "Completion: Reduce Copying of intermediate collections" Pull request url: https://github.com/pharo-project/pharo/pull/4899 Issue Url: https://github.com/pharo-project/pharo/issues/CompletionReduceCopying Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 14, 2019

[Pharo 8.0] Build #868: 4817-Epicea-Monticello-save-event-only-adds-noise-to-log

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

There is a new Pharo build available! The status of the build #868 was: FAILURE. The Pull Request #4901 was integrated: "4817-Epicea-Monticello-save-event-only-adds-noise-to-log" Pull request url: https://github.com/pharo-project/pharo/pull/4901 Issue Url: https://github.com/pharo-project/pharo/issues/4817 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 14, 2019

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

by jean baptiste arnaud

I saw you hand are tied here. Yeah, really strange that Rmod have difficulty to attract Ph.D student, indeed. So be it then. <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…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> Le sam. 12 oct. 2019 Ã 10:42, ducasse <stepharo(a)netcourrier.com> a Ã©crit : > Jean-Baptiste I think that you are overreacting but I cannot do much. > I do not see why when we refer to a public link on internet we would have > to ask > for permissions to use it. > Now you can ask the author of the interview to remove the page if you do > not like it. > I cannot do much. > And since you are into be professional. > Try it you will see it does not hurt. > > Stef > > > On 11 Oct 2019, at 23:09, jean baptiste arnaud <jbaptiste.arnaud(a)gmail.com> > wrote: > > 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…> > > 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. 14, 2019

[Pharo 8.0] Build #867: 4843-Semantic-Analysis-add-a-temp-variable-for-the-Temp-Vector-Copied-Var

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

There is a new Pharo build available! The status of the build #867 was: FAILURE. The Pull Request #4893 was integrated: "4843-Semantic-Analysis-add-a-temp-variable-for-the-Temp-Vector-Copied-Var" Pull request url: https://github.com/pharo-project/pharo/pull/4893 Issue Url: https://github.com/pharo-project/pharo/issues/4843 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 13, 2019

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

by ducasse

Jean-Baptiste I think that you are overreacting but I cannot do much. I do not see why when we refer to a public link on internet we would have to ask for permissions to use it. Now you can ask the author of the interview to remove the page if you do not like it. I cannot do much. And since you are into be professional. Try it you will see it does not hurt. Stef > On 11 Oct 2019, at 23:09, jean baptiste arnaud <jbaptiste.arnaud(a)gmail.com> wrote: > > 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…> <x-msg://51/#m_-796003953242991761_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > Le jeu. 10 oct. 2019 Ã 15:03, ducasse <stepharo(a)netcourrier.com <mailto:stepharo@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 <mailto:jbaptiste.arnaud@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. 12, 2019