- Pharo-dev - lists.pharo.org

Smalltalks 2018 videos are live

by Gabriel Cotelli

Hi, We finished uploading all the videos of the conference. You can get the links and related info here <https://smalltalks2018.fast.org.ar/talks>. Regards, Gabriel in name of FAST

Jan. 16, 2019

Re: [Pharo-dev] Looking for contributor names

by Bernardo Ezequiel Contreras

-vonbecmann: Bernardo E. Contreras On Wed, Jan 16, 2019 at 11:31 AM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > Is that time of the year (well, this time was more than one year) when I > ask for the names of people who contributed to Pharo but didnât put their > names. > I thought this was going to be fixed with the move to GitHub, but seems > that also there, there are people that does not use names :) > > So, Iâm missing this names: > > - vonbecmann > - Karnaj > - dupriezt > - pierretsap > - akevalion > - Marmat21 > > If you are one of those, or you know the name of one of those, please tell > me. > > Esteban > > Ps: Yes, that means we are very-very close of the release :) > -- Bernardo E.C. Sent from a cheap desktop computer in South America.

Jan. 16, 2019

[Pharo 7.0] Build #126: 22891-Callbacks-with-more-than-4-parameters-in-Win64-is-not-working

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

There is a new Pharo build available! The status of the build #126 was: SUCCESS. The Pull Request #2220 was integrated: "22891-Callbacks-with-more-than-4-parameters-in-Win64-is-not-working" Pull request url: https://github.com/pharo-project/pharo/pull/2220 Issue Url: https://pharo.fogbugz.com/f/cases/22891 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 16, 2019

[Pharo 7.0] Build #125: Replace arg1 by aPath

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

There is a new Pharo build available! The status of the build #125 was: SUCCESS. The Pull Request #2253 was integrated: "Replace arg1 by aPath" Pull request url: https://github.com/pharo-project/pharo/pull/2253 Issue Url: https://pharo.fogbugz.com/f/cases/patch Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 16, 2019

Re: [Pharo-dev] Apparently Zodiac plugin can crash VM on Linux

by Sven Van Caekenberghe

> On 16 Jan 2019, at 16:28, Max Leske <maxleske(a)gmail.com> wrote: > > On 15 Jan 2019, at 22:59, Sven Van Caekenberghe wrote: > > Doing HTTPS client calls is part of the standard test suite, so it should work, else we would not have a green build. It works for me and for the CI. > What exactly is he doing ? Is it reproducible ? > > Yes, consistently. How ? > Can he try with a fresh downloaded image+vm ? > > I quote: > > @embee > i have tested https://files.pharo.org/get-files/70/pharo64-linux-stable.zip and https://files.pharo.org/get-files/70/pharo64-linux-latest.zip > i hope those are the right ones. both crash > > @maxleske > Thanks. I'll report that. > Was that also with a fresh image? > i.e. you can also reprocude it with a fresh image, right? > > @embee > yes > > On 15 Jan 2019, at 22:20, Max Leske maxleske(a)gmail.com wrote: > > Hi, > > I'm writing on behalf of Martin (eMBee) who's experiencing crashes when using SSL. You can find a VM crash stack trace here: http://ws.stfx.eu/AKVNLUPMPGLG. > > He says he hasn't updated openssl since December 15th but that the crashes started to happen only recently (within the last couple of days). I asked him to try HTTP only connections and those work. The VM crashes immediately when using SSL. To me it looks like the cuplrit is the Zodiac plugin, or at least the library it works with. > > His system: > linux, fedora 29, and from the system reporter i get: Pharo/vms/70-x64/lib/pharo/5.0-201806281256/pharo > CoInterpreter VMMaker.oscog-eem.2401 uuid: 29232e0e-c9e3-41d8-ae75-519db862e02c Jun 28 2018 > StackToRegisterMappingCogit VMMaker.oscog-eem.2401 uuid: 29232e0e-c9e3-41d8-ae75-519db862e02c Jun 28 2018 > VM: 201806281256 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Thu Jun 28 14:56:30 2018 CommitHash: a8a1dc1 Plugins: 201806281256 https://github.com/OpenSmalltalk/opensmalltalk-vm.git > > cheers, > Max >

Jan. 16, 2019

Re: [Pharo-dev] Apparently Zodiac plugin can crash VM on Linux

by Max Leske

On 15 Jan 2019, at 22:59, Sven Van Caekenberghe wrote: > Doing HTTPS client calls is part of the standard test suite, so it > should work, else we would not have a green build. > > What exactly is he doing ? Is it reproducible ? Yes, consistently. > > Can he try with a fresh downloaded image+vm ? I quote: @embee i have tested https://files.pharo.org/get-files/70/pharo64-linux-stable.zip and https://files.pharo.org/get-files/70/pharo64-linux-latest.zip i hope those are the right ones. both crash @maxleske Thanks. I'll report that. Was that also with a fresh image? i.e. you can also reprocude it with a fresh image, right? @embee yes > >> On 15 Jan 2019, at 22:20, Max Leske <maxleske(a)gmail.com> wrote: >> >> Hi, >> >> I'm writing on behalf of Martin (eMBee) who's experiencing crashes >> when using SSL. You can find a VM crash stack trace here: >> http://ws.stfx.eu/AKVNLUPMPGLG. >> >> He says he hasn't updated openssl since December 15th but that the >> crashes started to happen only recently (within the last couple of >> days). I asked him to try HTTP only connections and those work. The >> VM crashes immediately when using SSL. To me it looks like the >> cuplrit is the Zodiac plugin, or at least the library it works with. >> >> His system: >> linux, fedora 29, and from the system reporter i get: >> Pharo/vms/70-x64/lib/pharo/5.0-201806281256/pharo >> CoInterpreter VMMaker.oscog-eem.2401 uuid: >> 29232e0e-c9e3-41d8-ae75-519db862e02c Jun 28 2018 >> StackToRegisterMappingCogit VMMaker.oscog-eem.2401 uuid: >> 29232e0e-c9e3-41d8-ae75-519db862e02c Jun 28 2018 >> VM: 201806281256 >> https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Thu Jun >> 28 14:56:30 2018 CommitHash: a8a1dc1 Plugins: 201806281256 >> https://github.com/OpenSmalltalk/opensmalltalk-vm.git >> >> cheers, >> Max

Jan. 16, 2019

Re: [Pharo-dev] Looking for contributor names

by ducasse

> On 16 Jan 2019, at 15:30, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > Is that time of the year (well, this time was more than one year) when I ask for the names of people who contributed to Pharo but didnât put their names. > I thought this was going to be fixed with the move to GitHub, but seems that also there, there are people that does not use names :) > > So, Iâm missing this names: > > - vonbecmann Von Becmann > - Karnaj Yoann Geran > - dupriezt Thomas Dupriez > - pierretsap Pierre Tsapliayeu > - akevalion Asbathou Biyalou-Sama <asbathou.biyalou-sama(a)inria.fr> > - Marmat21 > > If you are one of those, or you know the name of one of those, please tell me. > > Esteban > > Ps: Yes, that means we are very-very close of the release :)

Jan. 16, 2019

Re: [Pharo-dev] Looking for contributor names

by Esteban Lorenzano

Got them, thanks ! > On 16 Jan 2019, at 15:30, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > Is that time of the year (well, this time was more than one year) when I ask for the names of people who contributed to Pharo but didnât put their names. > I thought this was going to be fixed with the move to GitHub, but seems that also there, there are people that does not use names :) > > So, Iâm missing this names: > > - vonbecmann > - Karnaj > - dupriezt > - pierretsap > - akevalion > - Marmat21 > > If you are one of those, or you know the name of one of those, please tell me. > > Esteban > > Ps: Yes, that means we are very-very close of the release :)

Jan. 16, 2019

Looking for contributor names

by Esteban Lorenzano

Hi, Is that time of the year (well, this time was more than one year) when I ask for the names of people who contributed to Pharo but didnât put their names. I thought this was going to be fixed with the move to GitHub, but seems that also there, there are people that does not use names :) So, Iâm missing this names: - vonbecmann - Karnaj - dupriezt - pierretsap - akevalion - Marmat21 If you are one of those, or you know the name of one of those, please tell me. Esteban Ps: Yes, that means we are very-very close of the release :)

Jan. 16, 2019

[Pharo 7.0] Build #124: 22737-The-changelog-for-Pharo-7-needs-update

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

There is a new Pharo build available! The status of the build #124 was: FAILURE. The Pull Request #2251 was integrated: "22737-The-changelog-for-Pharo-7-needs-update" Pull request url: https://github.com/pharo-project/pharo/pull/2251 Issue Url: https://pharo.fogbugz.com/f/cases/22737 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 16, 2019