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

[ANN] Next Pharo Sprint: March 29

by Marcus Denker

We will organize a Pharo sprint / Moose dojo March 29, starting at 10:00am. (Local Time Paris). Goals of this sprint: - Pharo 7 backports, Pharo 8, - Check issues from old Issue tracker Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events We have added a (right now empty) Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 Known Local Sprint meetings Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come

March 22, 2019

[Pharo 8.0] Build #170: 2972-MailAddressTokenizer-doesnt-handle-non-ascii-characters

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

There is a new Pharo build available! The status of the build #170 was: SUCCESS. The Pull Request #2973 was integrated: "2972-MailAddressTokenizer-doesnt-handle-non-ascii-characters" Pull request url: https://github.com/pharo-project/pharo/pull/2973 Issue Url: https://pharo.fogbugz.com/f/cases/2972 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 22, 2019

[Pharo 8.0] Build #169: 2955-speedup-isAccessedIn-in-BooleanSlot-and-PropertySlot

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

There is a new Pharo build available! The status of the build #169 was: FAILURE. The Pull Request #2956 was integrated: "2955-speedup-isAccessedIn-in-BooleanSlot-and-PropertySlot" Pull request url: https://github.com/pharo-project/pharo/pull/2956 Issue Url: https://pharo.fogbugz.com/f/cases/2955 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 22, 2019

Re: [Pharo-dev] [Issue Tracker] installed some robots

by Ben Coman

Thanks. This is useful. On Thu, 21 Mar 2019 at 17:34, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Request Info: Requests more info on issues and pull requests with the > default title or an empty body. > it sets the more-information-needed flag. > https://probot.github.io/apps/request-info/ > Can more info be added to the generic message... > We would appreciate it if you could provide us with more info about this issue/pr! "This issue has either a default title or empty body. We would appreciate it if you could provide more info about this issue/pr!" Stale: Close stale Issues and Pull Requests > > https://github.com/probot/stale > Issues: daysUntilStale: 240, daysUntilClose: 60 > Pulls: daysUntilStale: 20, daysUntilClose: 10 > Same general thing about Stalebot comments, I opened... https://github.com/pharo-project/pharo/issues/2971 cheers -ben

March 22, 2019

Re: [Pharo-dev] Missing tests for FFI in CI

by Stephan Eggermont

Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> >> BOOL GetExitCodeProcess( >> HANDLE hProcess, >> LPDWORD lpExitCode >> ); >> > > what are your mappings for BOOL, HANDLE and LPDWORD? Those are user defined > types :) > I downloaded the stable version of OSWindows from the catalog Stephan

March 21, 2019

Re: [Pharo-dev] Missing tests for FFI in CI

by Guillermo Polito

Hi Stephan, Le jeu. 21 mars 2019 Ã 21:39, Stephan Eggermont <stephan(a)stack.nl> a Ã©crit : > ducasse <stepharo(a)netcourrier.com> wrote: > > Hello Stefan > > > > Can you report the exact call you were doing? > > I talked with G and Pablo and the bug they fixed is not the same. > > Now they would like to experiment and write tests for all the platform. > > BOOL GetExitCodeProcess( > HANDLE hProcess, > LPDWORD lpExitCode > ); > what are your mappings for BOOL, HANDLE and LPDWORD? Those are user defined types :) > I was trying to get the exit code of a running process on windows. That > didnât work, so we started again with OSWindows on a clean Pharo 8. There > we noticed that the currentProcess was not [ 255 255 255 255 255 255 255 > 255] but [ 255 255 255 255 0 0 0 0]. That (and the test being green in 32 > bit) triggered the idea. We did a quick and dirty change to verify, and > then found out that the Squeak code had cleaner fixes. > > Stephan > > > > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

March 21, 2019

Re: [Pharo-dev] How to download a patched file?

by Gabriel Cotelli

See my previous email. I've just clicked the already available buttons in the diff view: "View File" and then "Raw" in the next page opened. On Thu, Mar 21, 2019 at 5:32 PM Max Leske <maxleske(a)gmail.com> wrote: > Hi Eliot, > > > On 21 Mar 2019, at 21:00, Eliot Miranda wrote: > > > Hi GitHub mavens, > > > > how does one download a specific patched file from GitHub? I > > want to > > test Pablo's fix here: > > > > https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/381 > > platforms/iOS/vm/OSX/sqSqueakOSXOpenGLView.m > > <https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/381/files#diff-0 > > > > > > I don't want to go through "View File", or clone, or anything else. I > > just > > want the file itself. How do I get it? > > You'll have to know the commit hash, then you can grap it by path: > > https://raw.githubusercontent.com/OpenSmalltalk/opensmalltalk-vm/1a09bae437… > > AFAIK, there's no direct way to get to the file directly from the diff > view. > > Max > > > > > _,,,^..^,,,_ > > best, Eliot > > > >

March 21, 2019

Re: [Pharo-dev] Missing tests for FFI in CI

by Stephan Eggermont

ducasse <stepharo(a)netcourrier.com> wrote: > Hello Stefan > > Can you report the exact call you were doing? > I talked with G and Pablo and the bug they fixed is not the same. > Now they would like to experiment and write tests for all the platform. BOOL GetExitCodeProcess( HANDLE hProcess, LPDWORD lpExitCode ); I was trying to get the exit code of a running process on windows. That didnât work, so we started again with OSWindows on a clean Pharo 8. There we noticed that the currentProcess was not [ 255 255 255 255 255 255 255 255] but [ 255 255 255 255 0 0 0 0]. That (and the test being green in 32 bit) triggered the idea. We did a quick and dirty change to verify, and then found out that the Squeak code had cleaner fixes. Stephan

March 21, 2019

Re: [Pharo-dev] How to download a patched file?

by Max Leske

Hi Eliot, On 21 Mar 2019, at 21:00, Eliot Miranda wrote: > Hi GitHub mavens, > > how does one download a specific patched file from GitHub? I > want to > test Pablo's fix here: > > https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/381 > platforms/iOS/vm/OSX/sqSqueakOSXOpenGLView.m > <https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/381/files#diff-0> > > I don't want to go through "View File", or clone, or anything else. I > just > want the file itself. How do I get it? You'll have to know the commit hash, then you can grap it by path: https://raw.githubusercontent.com/OpenSmalltalk/opensmalltalk-vm/1a09bae437… AFAIK, there's no direct way to get to the file directly from the diff view. Max > > _,,,^..^,,,_ > best, Eliot

March 21, 2019

Re: [Pharo-dev] How to download a patched file?

by Gabriel Cotelli

Clicked "View File" button, then "Raw" button in the new page that gets opened. On Thu, Mar 21, 2019 at 5:21 PM Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Gabriel, > > On Thu, Mar 21, 2019 at 1:15 PM Gabriel Cotelli <g.cotelli(a)gmail.com> > wrote: > >> >> https://raw.githubusercontent.com/OpenSmalltalk/opensmalltalk-vm/1a09bae437… >> and save as ? >> > > great. This works (provided one selects "Page Source"). But how did you > get to that link? > > >> >> On Thu, Mar 21, 2019 at 5:01 PM Eliot Miranda <eliot.miranda(a)gmail.com> >> wrote: >> >>> Hi GitHub mavens, >>> >>> how does one download a specific patched file from GitHub? I want >>> to test Pablo's fix here: >>> >>> https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/381 >>> platforms/iOS/vm/OSX/sqSqueakOSXOpenGLView.m >>> <https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/381/files#diff-0> >>> >>> I don't want to go through "View File", or clone, or anything else. I >>> just want the file itself. How do I get it? >>> >>> _,,,^..^,,,_ >>> best, Eliot >>> >> > > -- > _,,,^..^,,,_ > best, Eliot >

March 21, 2019