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

Re: [Pharo-dev] Pharo Process question

by Stephane Ducasse

Well I would dream to give my superpower to attract bugs to anybody else. Because sometimes this is tiring. Yesterday a class comment changes of mine broke our jenkins process. Do not ask me why and how it is possible. But it did. Stef On Wed, Oct 25, 2017 at 12:40 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > But don't complain for the coming weeks about things not working ;) > > Norbert > > Am 25.10.2017 um 12:16 schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: > > Thanks guys. > Let us move to tonel :) > So I have to watch out then before pushing the button ;) > Stef > > > On Wed, Oct 25, 2017 at 10:10 AM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> >> >> On Tue, Oct 24, 2017 at 9:49 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >>> >>> >>> > On 24 Oct 2017, at 21:47, Stephane Ducasse <stepharo.self(a)gmail.com> >>> wrote: >>> > >>> > Hi >>> > >>> > are the pending PR reevaluated when one PR is integrated? >>> >> >> Unfortunately not on every integration... We should do it that way but >> there are some problems with Jenkins allocating space in the master machine. >> >> Christophe was telling me he would contact the people from jenkins to see >> if there is a solution for that. >> >>> >>> it was, but Guille disabled it because it was killing the server. >>> when we jump to tonel we can re-evaluate the problem :) >>> >>> Esteban >>> >>> > >>> > Stef >>> > >>> >>> >>> >> >> >> -- >> >> 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 <+33%206%2052%2070%2066%2013> >> > > >

Oct. 25, 2017

Re: [Pharo-dev] feenk log

by Aliaksei Syrel

Hi Denis, The reason for BlVector2D is that we also have BlVector*3*D. In case of translation a Point (x@y) should be converted to (x,y,0). For scale it is converted as (x,y,1). You see, the same Point object has different meanings when it comes to different transformations. Additionally, Point does not represent the intent correctly because all affine transformations involve vectors. Of course, we made Vectors polymorphic with points, so users can write: element translateBy: (20@20) instead of element translateBy: (BlVector x: 20 y: 20). - How often this vector will be constructed by hands in user code? It is > related to my question about comma message: is it really needed? In lineare algebra vectors are represented as (x, y, z). Beautiful! Cheers, Alex

Oct. 25, 2017

Re: [Pharo-dev] feenk log

by Stephane Ducasse

Personally (10, 20) for a vector is not really nice and I would really like to have a discussion before. On Wed, Oct 25, 2017 at 6:45 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Doru having a few tweets is nice but I do not think that you > communicate well around bloc. > > What I would like to get is a roadmap for Bloc V1.0. > - Here are the missing features (documentation), > - Here are where we are. > Because else it feels like Bloc will never ends. > You will argue and tell me that you experiments. But without a feature > list then > people cannot join and do not know when you get a 1.0. > > Not measuring is the best way to arrive to a point where you did not wanted. > > You see for Brick we need > Button > CheckBox > DropList > List > Table > Pane > InputField > Text > Scrollbar > Menu > And with that we can get a first Widget set. > But again without a roadmap I have some doubts. > > Stef > > > Stef > > > On Wed, Oct 25, 2017 at 6:38 PM, Stephane Ducasse > <stepharo.self(a)gmail.com> wrote: >> Doru using comma for creating vectors is not really because it will >> just make the life of type inferencers more difficult. >> >> >> On Wed, Oct 25, 2017 at 5:53 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> Hi, >>> >>> Our team is working on a couple of projects that are relevant for the core of Pharo, namely GT and Bloc/Brick. At ESUG we were asked by several people, and Stef in particular, to make the progress on these projects more transparent. To this end, we will start two streams of signals: >>> - fine grained info bits on out Twitter account (several times a week): https://twitter.com/feenkcom >>> - a less often but regular (probably every 2 weeks) activity log message sent to this mailing list >>> >>> Please let us know if you see an issue with this. >>> >>> In the meantime, letâs start. >>> >>> Bloc: >>> - Over the past couple of weeks Alex worked on transformations and measurements in the core system. It turns out that there was room for quite a number of performance optimizations and for making the system more debuggable. >>> - At the low level, this involved adding matrix and vector support. >>> https://twitter.com/feenkcom/status/923123870537863168 >>> https://twitter.com/feenkcom/status/916300180848349185 >>> - At a higher level, it implies keeping track of measurements >>> https://twitter.com/AliakseiSyrel/status/915203525931622400 >>> - And of transformations: >>> https://twitter.com/feenkcom/status/919603739656417281 >>> https://twitter.com/feenkcom/status/917116164484096001 >>> - The BlScalableElement is now working properly >>> >>> GT Examples: >>> - The current repository with unary-based examples is at: https://github.com/feenkcom/gtoolkit-examples >>> - We now have a runner in the inspector that allows us to both see the source code and run and play with the resulting object: >>> https://twitter.com/feenkcom/status/923210686204989442 >>> - Andrei made the âafterâ behavior to work with unary examples. >>> >>> Cheers, >>> The feenk team >>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "Being happy is a matter of choice." >>> >>> >>> >>> >>>

Oct. 25, 2017

Re: [Pharo-dev] feenk log

by Stephane Ducasse

Doru having a few tweets is nice but I do not think that you communicate well around bloc. What I would like to get is a roadmap for Bloc V1.0. - Here are the missing features (documentation), - Here are where we are. Because else it feels like Bloc will never ends. You will argue and tell me that you experiments. But without a feature list then people cannot join and do not know when you get a 1.0. Not measuring is the best way to arrive to a point where you did not wanted. You see for Brick we need Button CheckBox DropList List Table Pane InputField Text Scrollbar Menu And with that we can get a first Widget set. But again without a roadmap I have some doubts. Stef Stef On Wed, Oct 25, 2017 at 6:38 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Doru using comma for creating vectors is not really because it will > just make the life of type inferencers more difficult. > > > On Wed, Oct 25, 2017 at 5:53 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> Hi, >> >> Our team is working on a couple of projects that are relevant for the core of Pharo, namely GT and Bloc/Brick. At ESUG we were asked by several people, and Stef in particular, to make the progress on these projects more transparent. To this end, we will start two streams of signals: >> - fine grained info bits on out Twitter account (several times a week): https://twitter.com/feenkcom >> - a less often but regular (probably every 2 weeks) activity log message sent to this mailing list >> >> Please let us know if you see an issue with this. >> >> In the meantime, letâs start. >> >> Bloc: >> - Over the past couple of weeks Alex worked on transformations and measurements in the core system. It turns out that there was room for quite a number of performance optimizations and for making the system more debuggable. >> - At the low level, this involved adding matrix and vector support. >> https://twitter.com/feenkcom/status/923123870537863168 >> https://twitter.com/feenkcom/status/916300180848349185 >> - At a higher level, it implies keeping track of measurements >> https://twitter.com/AliakseiSyrel/status/915203525931622400 >> - And of transformations: >> https://twitter.com/feenkcom/status/919603739656417281 >> https://twitter.com/feenkcom/status/917116164484096001 >> - The BlScalableElement is now working properly >> >> GT Examples: >> - The current repository with unary-based examples is at: https://github.com/feenkcom/gtoolkit-examples >> - We now have a runner in the inspector that allows us to both see the source code and run and play with the resulting object: >> https://twitter.com/feenkcom/status/923210686204989442 >> - Andrei made the âafterâ behavior to work with unary examples. >> >> Cheers, >> The feenk team >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Being happy is a matter of choice." >> >> >> >> >>

Oct. 25, 2017

Re: [Pharo-dev] feenk log

by Stephane Ducasse

Doru using comma for creating vectors is not really because it will just make the life of type inferencers more difficult. On Wed, Oct 25, 2017 at 5:53 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Our team is working on a couple of projects that are relevant for the core of Pharo, namely GT and Bloc/Brick. At ESUG we were asked by several people, and Stef in particular, to make the progress on these projects more transparent. To this end, we will start two streams of signals: > - fine grained info bits on out Twitter account (several times a week): https://twitter.com/feenkcom > - a less often but regular (probably every 2 weeks) activity log message sent to this mailing list > > Please let us know if you see an issue with this. > > In the meantime, letâs start. > > Bloc: > - Over the past couple of weeks Alex worked on transformations and measurements in the core system. It turns out that there was room for quite a number of performance optimizations and for making the system more debuggable. > - At the low level, this involved adding matrix and vector support. > https://twitter.com/feenkcom/status/923123870537863168 > https://twitter.com/feenkcom/status/916300180848349185 > - At a higher level, it implies keeping track of measurements > https://twitter.com/AliakseiSyrel/status/915203525931622400 > - And of transformations: > https://twitter.com/feenkcom/status/919603739656417281 > https://twitter.com/feenkcom/status/917116164484096001 > - The BlScalableElement is now working properly > > GT Examples: > - The current repository with unary-based examples is at: https://github.com/feenkcom/gtoolkit-examples > - We now have a runner in the inspector that allows us to both see the source code and run and play with the resulting object: > https://twitter.com/feenkcom/status/923210686204989442 > - Andrei made the âafterâ behavior to work with unary examples. > > Cheers, > The feenk team > > -- > www.tudorgirba.com > www.feenk.com > > "Being happy is a matter of choice." > > > > >

Oct. 25, 2017

Re: [Pharo-dev] feenk log

by Denis Kudriashov

Hi. Good initiative. Here is my twitter questions: - What the reason to introduce BlVector2D instead of using existing Point? - How often this vector will be constructed by hands in user code? It is related to my question about comma message: is it really needed? Now you can evaluate (10*,* 20) to get vector instance. And if it is only to simplify scripting and examples then why not use Point for this? As you said point can be converted to vector. Best regards, Denis 2017-10-25 17:53 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > Our team is working on a couple of projects that are relevant for the core > of Pharo, namely GT and Bloc/Brick. At ESUG we were asked by several > people, and Stef in particular, to make the progress on these projects more > transparent. To this end, we will start two streams of signals: > - fine grained info bits on out Twitter account (several times a week): > https://twitter.com/feenkcom > - a less often but regular (probably every 2 weeks) activity log message > sent to this mailing list > > Please let us know if you see an issue with this. > > In the meantime, letâs start. > > Bloc: > - Over the past couple of weeks Alex worked on transformations and > measurements in the core system. It turns out that there was room for quite > a number of performance optimizations and for making the system more > debuggable. > - At the low level, this involved adding matrix and vector support. > https://twitter.com/feenkcom/status/923123870537863168 > https://twitter.com/feenkcom/status/916300180848349185 > - At a higher level, it implies keeping track of measurements > https://twitter.com/AliakseiSyrel/status/915203525931622400 > - And of transformations: > https://twitter.com/feenkcom/status/919603739656417281 > https://twitter.com/feenkcom/status/917116164484096001 > - The BlScalableElement is now working properly > > GT Examples: > - The current repository with unary-based examples is at: > https://github.com/feenkcom/gtoolkit-examples > - We now have a runner in the inspector that allows us to both see the > source code and run and play with the resulting object: > https://twitter.com/feenkcom/status/923210686204989442 > - Andrei made the âafterâ behavior to work with unary examples. > > Cheers, > The feenk team > > -- > www.tudorgirba.com > www.feenk.com > > "Being happy is a matter of choice." > > > > > >

Oct. 25, 2017

Re: [Pharo-dev] [Pharo 7.0-dev] Build #227: 20589-update-iceberg-to-062

by Pavel Krivanek

copy of the changelog: v0.6.2 This is a bugfix release. Issues: #486 Failing cloning behind a proxy bug #490 trying to browse an iceberg package in monticello raises error bug #457 Iceberg fails to parse valid URLs bug #489 timeout when trying to clone a private gitlab repo bug #488 remoteurl fails to parse urls with dash ($-) bug #481 iceberg fails to load private bitbucket repositories bug #485 Correct usage of bitbucket typed repository #473 Url handling enhancement 2017-10-25 18:10 GMT+02:00 <ci-pharo-ci-jenkins2(a)inria.fr>: > There is a new Pharo build available! > > The status of the build #227 was: SUCCESS. > > The Pull Request #397 was integrated: "20589-update-iceberg-to-062" > Pull request url: https://github.com/pharo-project/pharo/pull/397 > > Issue Url: https://pharo.fogbugz.com/f/cases/20589 > Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending% > 20pull%20request%20and%20branch%20Pipeline/job/development/227/ >

Oct. 25, 2017

[Pharo 7.0-dev] Build #227: 20589-update-iceberg-to-062

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

There is a new Pharo build available! The status of the build #227 was: SUCCESS. The Pull Request #397 was integrated: "20589-update-iceberg-to-062" Pull request url: https://github.com/pharo-project/pharo/pull/397 Issue Url: https://pharo.fogbugz.com/f/cases/20589 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 25, 2017

Re: [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerations

by henry

I disabled vatId authorization in version 3, located in SessionOperations>>processIWant | SessionOperations>>processIAm:. I was asked to disseminate my news to Pharo Users, hello there. I was asked to describe ParrotTalk well, provide use cases and adopters of its use. Alright, I will give an attempt. ParrotTalk is an encrypted connection framework. Currently allowing anonymous 2048-bit key negotiation to establish user-provided encryption cipher and user-provided encoding and decoding, both through a provided SessionAgentMap to a starting SessionAgent server. Please look in the test case ThunkHelloWorldTest for building these maps and running a connection iwth data passing after encryption is established. There is a 4-way negotiation, from ProtocolOffered/Accepted to Go/GoToo. In using RSA 2048 signature validation and DH 2048 primes to establish the key used within the selected Cipher. The Cipher and Encoder are selected by name through the negotiation protocol. Currently three Ciphers are selectable, AESede, DESede, and DES. There are two encoders tested, asn1der, and Bytes. This protocol is described here, in this document. https://github.com/ZiroZimbarra/callistohouse/blob/master/docs/ParrotTalkFr… For as to use cases, this encrypted connection has no third party, man-in-the-middle situation by not using Certificates. As such, this is a tight implementation of NSA-proof encryption without explicit authorization beyond knowledge of a host:port. The use cases involve any communication desired to be encrypted with such high encryption. The support will last my lifetime, so we have a settled solution, here in the third version, provided here. It requires version 111 of Cryptography, as a prerequisite. Both run on Squeak and Pharo. http://www.squeaksource.com/Cryptography/Cryptography-zzz.111.mcz http://www.squeaksource.com/Cryptography/ParrotTalk-HenryHouse.3.mcz The current use is with my hubbub system, a promise-based distributed object implementation. I am working to bring ParrotTalk to Java and allow hubbub to operate interdependently between Squeak, Pharo, Java and any other languages which can support ParrotTalk and STON. My latest efforts with hubbub are to bring STON as the Layer 6 encoding. Hubbub depends on eLinda. http://www.squeaksource.com/Cryptography/elinda-HenryHouse.14.mcz http://www.squeaksource.com/Oceanside/hubbub-HenryHouse.38.mcz Hubbub currently fails to load correctly in Pharo. In Squeak the two ParrotRemoteTestCases: LookupTestCase and OperationalTestCase really screw everything up, do not save an image after running. I never run these tests until I get a better handle of serialization. Currently, do to a shift in progress to STON, the serialization tests fail, just the way we like it. Fix the tests then the system starts to work right. The shift away from vatId authorization should not adversely affect hubbub, we hope! When STON starts to work, and I think I need to turn off jsonMode, then traffic between vats can start to be analyzed and figure out how resolving is working with redirectors invoked remotely. - HH > -------- Original Message -------- > Subject: Re: [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerations > Local Time: October 25, 2017 12:43 AM > UTC Time: October 25, 2017 4:43 AM > From: btc(a)openinworld.com > To: henry <henry(a)callistohouse.club>, Pharo Development List <pharo-dev(a)lists.pharo.org> > Stephane Ducasse <stepharo.self(a)gmail.com> > > If I google... parrottalk protocol > nothing seems related. So what is ParrotTalk? > > P.S... since this is not "part of" pharo, [pharo-users] would be a better place for discussion than [pharo-dev]. > Could you re-announce there, with some description of use cases and who/where the protocol is used? > > cheers -ben > > On Wed, Oct 25, 2017 at 1:42 AM, henry <henry(a)callistohouse.club> wrote: > >> Please excuse all the low-level detail, if inappropriate to the discussion. The protocol changes are here specified. >> >> - HH >> >> On Tue, Oct 24, 2017 at 13:40, henry <henry(a)callistohouse.club> wrote: >> >>> In order to bring ParrotTalk-3.6 support, alongside historical 3.5 support, the frame header stays the same and the processing of the ProtocolOffered would select "ParrotTalk-3.6" to use the compact protocol of >>> >>> - ProtocolOffered { offered, preferred } >>> - ProtocolAccepted { accepted } >>> - IWant|GiveInfo|ReplyInfo { vatId, domain, publicKey, cryptoProtocols, dataEncoders } >>> - IAm|ReplyInfo { vatId, domain, publicKey, cryptoProtocol, dataEncoder, dhParam } >>> - Go { cryptoProtocol, dataEncoder, dhParam, signature } >>> - GoToo { signature } >>> >>> Using eLinda : >>> >>> http://www.squeaksource.com/Cryptography/elinda-HenryHouse.14.mcz >>> >>> Above the FrameBuffer, below the SessionOperations for each version of the protocol, an ELindaSession could be inserted. This session think would have the stacks for each protocol version SessionOperation registered by protocol in a Tuple, for eventual callback. When the ProtocolOffered comes in we publish the tuple frame, with set selected version, to route to the correct SessionOperation to support each version of the protocol. >>> >>> With a non-specific vatId required, anonymous connections would be supported. >>> >>> - HH >>> >>> On Tue, Oct 24, 2017 at 12:52, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>> >>>> Hi henry thanks for this announce. Can you tell where such protocols are used? Stef On Tue, Oct 24, 2017 at 6:33 PM, henry wrote: > Hi all, > > I am happy to announce the release of version 3.5 of ParrotTalk, for Squeak > and Pharo, found here: > > http://www.squeaksource.com/Cryptography/ParrotTalk-zzz.2.mcz > > It follows this specification: > https://github.com/ZiroZimbarra/callistohouse/blob/master/docs/ParrotTalkFr… > > One item of note, in version 3.5, the system connecting to a server, sending > the IWant msg, must know the vatId of the system being connected to. I am > considering changing this to version 3.6 by removing one round-trip in > messaging. Therefore, these messages would be combined: IWant/GiveInfo, > IAm/ReplyInfo. I will keep ProtocolOffered and ProtocolAccepted to allow > eLindaSession to support both versions: 3.5 and 3.6. > > Thoughts please? > > - HH

Oct. 25, 2017

feenk log

by Tudor Girba

Hi, Our team is working on a couple of projects that are relevant for the core of Pharo, namely GT and Bloc/Brick. At ESUG we were asked by several people, and Stef in particular, to make the progress on these projects more transparent. To this end, we will start two streams of signals: - fine grained info bits on out Twitter account (several times a week): https://twitter.com/feenkcom - a less often but regular (probably every 2 weeks) activity log message sent to this mailing list Please let us know if you see an issue with this. In the meantime, letâs start. Bloc: - Over the past couple of weeks Alex worked on transformations and measurements in the core system. It turns out that there was room for quite a number of performance optimizations and for making the system more debuggable. - At the low level, this involved adding matrix and vector support. https://twitter.com/feenkcom/status/923123870537863168 https://twitter.com/feenkcom/status/916300180848349185 - At a higher level, it implies keeping track of measurements https://twitter.com/AliakseiSyrel/status/915203525931622400 - And of transformations: https://twitter.com/feenkcom/status/919603739656417281 https://twitter.com/feenkcom/status/917116164484096001 - The BlScalableElement is now working properly GT Examples: - The current repository with unary-based examples is at: https://github.com/feenkcom/gtoolkit-examples - We now have a runner in the inspector that allows us to both see the source code and run and play with the resulting object: https://twitter.com/feenkcom/status/923210686204989442 - Andrei made the âafterâ behavior to work with unary examples. Cheers, The feenk team -- www.tudorgirba.com www.feenk.com "Being happy is a matter of choice."

Oct. 25, 2017