August 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] moose build - pharo vm crash

by Esteban Lorenzano

where is the report? On Aug 6, 2013, at 4:50 PM, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: > Hi Doru, > > join the club: > > https://swing.fit.cvut.cz/jenkins/view/CalipeL/job/calipel_s_pharo20_benchm… > > I reported presumably same issue 21/06/13, update 10/07/13 :-) > > Best, Jan > > > > On 06/08/13 15:43, Tudor Girba wrote: >> Hi, >> >> It seems that the Moose build crashes the VM since yesterday evening due >> to a failing test. The image is based on Pharo 2.0 and is running a >> stable VM on Ubuntu. >> >> See some details here: >> https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/804/console >> >> The script to reproduce the problem (on Ubuntu) is: >> >> #------------------- >> wget --quiet -O - http://get.pharo.org/20+vm | bash >> >> ./pharo Pharo.image save $JOB_NAME >> >> REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main >> ./pharo $JOB_NAME.image config $REPO ConfigurationOfMoose >> --install=development >> ./pharo $JOB_NAME.image mooseimagesetup >> >> ./pharo $JOB_NAME.image moosetest --junit-xml-output >> >> mv ./pharo-vm/PharoV20.sources ./ >> zip $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes PharoV20.sources >> #------------------- >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com> >> >> "Every thing has its own flow" > >

Aug. 6, 2013

Re: [Pharo-dev] Flamel Update

by StÃ©phane Ducasse

ok I got it this is the difference between expression and method. Stef > Gisela > > why do you say that > > `anObject size. > > size should match a variable? > > you completely lost me there. > > Because `anObject should match > self > x > tmp > > Stef

Aug. 6, 2013

Re: [Pharo-dev] Flamel Update

by StÃ©phane Ducasse

Gisela why do you say that `anObject size. size should match a variable? you completely lost me there. Because `anObject should match self x tmp Stef

Aug. 6, 2013

Re: [Pharo-dev] Keyboard events is broken.

by StÃ©phane Ducasse

thanks guillermo :) Cleaning events at VM level is important. On Aug 6, 2013, at 4:32 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > > On Tue, Aug 6, 2013 at 3:40 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > I changed this method to see better what happens: > HandMorph class>>showDebugEvent: evt > > ShowEvents == true ifTrue: [ > | ofs| > Display fill: (0@0 extent: 500@120) rule: Form over > fillColor: Color white. > ofs := (owner hands indexOf: self) - 1 * 60. > evt printString displayAt: (0@ofs) + (evt isKeyboard > ifTrue: [0@30] > ifFalse: [0@0]). > self keyboardFocus printString displayAt: (0@ofs)+(0@45). > > evt isKeyboard ifTrue: [ Transcript show: evt printString;cr ] > ]. > > > KeyboardEvent>> printOn: aStream > "Print the receiver on a stream" > > aStream nextPut: $[. > aStream nextPutAll: type; nextPutAll: ' '''. > self printKeyStringOn: aStream. > aStream nextPut: $'. > > aStream space; nextPutAll: 'keyValue: ', self keyValue asString. > > aStream nextPut: $] > > set > HandMorph showEvents:true > > Now, pressing single space, gives me this: > > [keyDown ' ' keyValue: 49] > [keystroke ' ' keyValue: 32] > [keyUp ' ' keyValue: 49] > [keyUp ' ' keyValue: 49] > > Pressing delete key (or fn-backspace , for those who having a lot of > spare fingers to use bad keyboards): > > [keyDown ' ' keyValue: 117] > [keystroke 'â¦' keyValue: 188] > [keyUp ' ' keyValue: 117] > [keyUp ' ' keyValue: 117] > > now, can someone tell me , why there is 2 keyUp events for each keyDown? > > That I don't know > > > and of course, main question is why key values are different for > keydown and keystroke events? > > That I'll dive right now into the vm to see what it is :). > > (and why delete key is not 127, but 117 or 188?) > > Editor expecting 127: > > cmdMap at: (127 + 1) put: #forwardDelete:. "del key" > > > > -- > Best regards, > Igor Stasenko. > >

Aug. 6, 2013

Re: [Pharo-dev] moose build - pharo vm crash

by Jan Vrany

Hi Doru, join the club: https://swing.fit.cvut.cz/jenkins/view/CalipeL/job/calipel_s_pharo20_benchm… I reported presumably same issue 21/06/13, update 10/07/13 :-) Best, Jan On 06/08/13 15:43, Tudor Girba wrote: > Hi, > > It seems that the Moose build crashes the VM since yesterday evening due > to a failing test. The image is based on Pharo 2.0 and is running a > stable VM on Ubuntu. > > See some details here: > https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/804/console > > The script to reproduce the problem (on Ubuntu) is: > > #------------------- > wget --quiet -O - http://get.pharo.org/20+vm | bash > > ./pharo Pharo.image save $JOB_NAME > > REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main > ./pharo $JOB_NAME.image config $REPO ConfigurationOfMoose > --install=development > ./pharo $JOB_NAME.image mooseimagesetup > > ./pharo $JOB_NAME.image moosetest --junit-xml-output > > mv ./pharo-vm/PharoV20.sources ./ > zip $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes PharoV20.sources > #------------------- > > Cheers, > Doru > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

Aug. 6, 2013

Re: [Pharo-dev] Flamel Update

by StÃ©phane Ducasse

thanks for the update.. Stef On Aug 6, 2013, at 3:00 PM, Gisela Decuzzi <giseladecuzzi(a)gmail.com> wrote: > Hi, I'm working for the Gsoc project: better rw rule tools and my mentors suggested me to send the weekly progress to the mailing list because other people can be interested. > > Work done: > - defining a basic UI that admit > - write an example expression > - write the matching / transforming pattern > - restrict the scope where running the rule (now select classes or packages) > - run a rule for matching / transforming > > This week progress: > - Show / Navigate the result after matching: > <FlamelUI-WithResultInMatch.png> > - blog post about defining the matching expression: http://pharorwrules.wordpress.com/2013/08/06/just-want-to-match/ > - bugfixing > - middle term evaluation > - fixing repository and package mess (that I've done...) > > For next week: > - correct problems when transforming > - vitualize the result after a transformation (rehuse part of the search result for this) > - add tests for transforming > - blog post about rw engine (how to define a rule from the scratch and why I implemented my own rule that matchs and transforms) > - (if time) define the matching pattern for the expression (is an expression, is a method? Should try with the best?), right now is matching as a method pattern and sometimes is confusing. > > If someone wants to see more planed task can have a look to the Trello board in: https://trello.com/b/XqfJGqeB/flamel > If someone wants to give a try and give me some feedback the code is in smalltalkhub: > MCSmalltalkhubRepository > owner: 'gisela' > project: 'Flamel' > user: '' > password: '' > The blog for this project is: http://pharorwrules.wordpress.com > > Cheers, > Gise.

Aug. 6, 2013

Re: [Pharo-dev] [Pharo-fuel] Fuel API bug

by StÃ©phane Ducasse

> #when:do: is there already ;) even better then :) > #when:send:to: and #when:do:for: should be added though. sounds good. > > Cheers, > Henry > > >

Aug. 6, 2013

moose build - pharo vm crash

by Tudor Girba

Hi, It seems that the Moose build crashes the VM since yesterday evening due to a failing test. The image is based on Pharo 2.0 and is running a stable VM on Ubuntu. See some details here: https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/804/console The script to reproduce the problem (on Ubuntu) is: #------------------- wget --quiet -O - http://get.pharo.org/20+vm | bash ./pharo Pharo.image save $JOB_NAME REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main ./pharo $JOB_NAME.image config $REPO ConfigurationOfMoose --install=development ./pharo $JOB_NAME.image mooseimagesetup ./pharo $JOB_NAME.image moosetest --junit-xml-output mv ./pharo-vm/PharoV20.sources ./ zip $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes PharoV20.sources #------------------- Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Aug. 6, 2013

Re: [Pharo-dev] Fwd: Keyboard events is broken.

by Guillermo Polito

On Tue, Aug 6, 2013 at 3:40 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > I changed this method to see better what happens: > HandMorph class>>showDebugEvent: evt > > ShowEvents == true ifTrue: [ > | ofs| > Display fill: (0@0 extent: 500@120) rule: Form over > fillColor: Color white. > ofs := (owner hands indexOf: self) - 1 * 60. > evt printString displayAt: (0@ofs) + (evt isKeyboard > ifTrue: [0@30] > ifFalse: [0@0]). > self keyboardFocus printString displayAt: (0@ofs)+(0@45). > > evt isKeyboard ifTrue: [ Transcript show: evt > printString;cr ] > ]. > > > KeyboardEvent>> printOn: aStream > "Print the receiver on a stream" > > aStream nextPut: $[. > aStream nextPutAll: type; nextPutAll: ' '''. > self printKeyStringOn: aStream. > aStream nextPut: $'. > > aStream space; nextPutAll: 'keyValue: ', self keyValue asString. > > aStream nextPut: $] > > set > HandMorph showEvents:true > > Now, pressing single space, gives me this: > > [keyDown ' ' keyValue: 49] > [keystroke ' ' keyValue: 32] > [keyUp ' ' keyValue: 49] > [keyUp ' ' keyValue: 49] > > Pressing delete key (or fn-backspace , for those who having a lot of > spare fingers to use bad keyboards): > > [keyDown ' ' keyValue: 117] > [keystroke 'â¦' keyValue: 188] > [keyUp ' ' keyValue: 117] > [keyUp ' ' keyValue: 117] > > now, can someone tell me , why there is 2 keyUp events for each keyDown? > That I don't know > > and of course, main question is why key values are different for > keydown and keystroke events? > That I'll dive right now into the vm to see what it is :). > (and why delete key is not 127, but 117 or 188?) > > Editor expecting 127: > > cmdMap at: (127 + 1) put: #forwardDelete:. "del key" > > > > -- > Best regards, > Igor Stasenko. > >

Aug. 6, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/… 1 regressions found. KernelTests.Numbers.LargePositiveIntegerTest.testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses

Aug. 6, 2013