- Pharo-dev - lists.pharo.org

[Pharo 9.0] Build #332: skip-testReifyTempOperationInstead

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

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

June 4, 2020

OpenSSL binding Re: About strange email related to smalltalkhub read-only on squeak-dev

by Pierce Ng

On Tue, Jun 02, 2020 at 11:17:30AM +0200, Norbert Hartl wrote: > PierceNg has an implementation that implements a subset of openssl. > This implementation is modeled after the library so lots of class > methods. I'd prefer to have something more object model like. A very small subset currently, as my original need was to create an X509 request in code. PRs welcome. https://github.com/PierceNg/OpenSSL-Pharo Pierce

June 4, 2020

Re: [Pharo-dev] #(1 1 1 2 2 2 3 3 3 4 4 4) . 3 -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4))

by Torsten Bergmann

Hi Stef, Â from the (incomplete) sample it is unclear what is really needed: Â Â 1. Both return the same result: #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4))Â which is syntactically equal toÂ #(#(1 1 1) #(2 2 2) #(3 3 3) #(4 4 4)) Â Â So why did you leave out the # for the contained sub-array with 2's and 3's? Â 2. When the result is equal in both examples why give a different argument like 3 and 4?Â Â 3. What about edge case inputs like:Â Â #(1 1 1 2 2 2 4 4 4)Â Â Â Â Â not having sucessors/predecessor order Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â #(2 2 2 1 1 1 3 3 3 4 4 4)Â with different order (not ascending) Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â #(1 1 1 1 2 2 2 3 3 3 4 4 4) where 1 is included more often than the otherÂ Â Â 4. ... Nonetheless: the closest that might possibly be of use is #groupByRuns: message Â Â #(1 1 1 2 2 2 3 3 3 4 4 4) groupByRuns: [:e | e ]Â Â ->Â Â #(#(1 1 1) #(2 2 2) #(3 3 3) #(4 4 4)) Have fun T. Â Â Gesendet:Â Mittwoch, 03. Juni 2020 um 22:53 Uhr Von:Â "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> An:Â "Pharo Development List" <pharo-dev(a)lists.pharo.org> Betreff:Â [Pharo-dev] #(1 1 1 2 2 2 3 3 3 4 4 4) . 3 -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4)) Hi guysÂ Â do you know if we have around a method doing the following? Â #(1 1 1 2 2 2 3 3 3 4 4 4) . 3 -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4))Â Â it could also be another one Â #(1 1 1 2 2 2 3 3 3 4 4 4) . 4 -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4))Â Â S Â -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org[http://www.pharo.org]Â 03 59 35 87 52 Assistant: Aurore DalleÂ FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley,Â Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

June 3, 2020

Re: [Pharo-dev] #(1 1 1 2 2 2 3 3 3 4 4 4) . 3 -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4))

by Todd Blanchard

I don't understand your intent. Do they group together because they have the same value or do they just get grouped into subgroups of size three or do they get grouped as runs? This works: #(1 1 1 2 2 2 3 3 3 4 4 4) groupByRuns: [ :ea | ea ] -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4)) > On Jun 3, 2020, at 1:53 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > Hi guys > > do you know if we have around a method doing the following? > > #(1 1 1 2 2 2 3 3 3 4 4 4) . 3 -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4)) > > it could also be another one > > #(1 1 1 2 2 2 3 3 3 4 4 4) . 4 -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4)) > > S > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> / http://www.pharo.org <http://www.pharo.org/> > 03 59 35 87 52 > Assistant: Aurore Dalle > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France >

June 3, 2020

#(1 1 1 2 2 2 3 3 3 4 4 4) . 3 -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4))

by StÃ©phane Ducasse

Hi guys do you know if we have around a method doing the following? #(1 1 1 2 2 2 3 3 3 4 4 4) . 3 -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4)) it could also be another one #(1 1 1 2 2 2 3 3 3 4 4 4) . 4 -> #(#(1 1 1) (2 2 2) (3 3 3) #(4 4 4)) S -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

June 3, 2020

[Pharo 9.0] Build #331: Rules checking Tests should be in package SUnit-Rules

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

There is a new Pharo build available! The status of the build #331 was: FAILURE. The Pull Request #6304 was integrated: "Rules checking Tests should be in package SUnit-Rules" Pull request url: https://github.com/pharo-project/pharo/pull/6304 Issue Url: https://github.com/pharo-project/pharo/issues/6303 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 3, 2020

[Pharo 9.0] Build #330: Deprecated Slot

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

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

June 3, 2020

[Pharo 8.0] Build #1138: 6420-Backport-5482-to-Pharo8

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

There is a new Pharo build available! The status of the build #1138 was: SUCCESS. The Pull Request #6427 was integrated: "6420-Backport-5482-to-Pharo8" Pull request url: https://github.com/pharo-project/pharo/pull/6427 Issue Url: https://github.com/pharo-project/pharo/issues/6420 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 3, 2020

[Pharo 9.0] Build #329: Fixes changes file flushing issue

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

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

June 3, 2020

[Pharo 9.0] Build #328: Fix #6472

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

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

June 3, 2020