January 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Moose-dev] feenk log

by Tudor Girba

Hi, > On Jan 21, 2018, at 10:37 PM, Ben Coman <btc(a)openInWorld.com> wrote: > > On 21 January 2018 at 23:55, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> Hi, >> >> There is a difference in performance. The Announcement is slower (about 2-3x slower). However, for 1M events the difference is measured in a 200-400ms, which is very small. > > So you mean each event <1ms difference? > btw, what is the biggest usage of events? I guess mouse movements? > How many such events typically in 1 second of movement? > How is performance on StackInterpreter VM? > I guess we should keep that performant for platforms lacking JIT like > iPads, etcâ¦ It depends on the scene. We are still looking into how to evaluate this. Thatâs why we still have both implementations around. >> The benefit of using Announcement is that we can reuse the tooling around Announcement, such as blogging and debugging. > > This looks really useful. Can you describe the difference between the > red and blue lines in the picture of the first link? Each event goes through two passes, like in JavaScript: - The first is called âcapturingâ (or filtering) and goes from the root to the leaf. This is to allow a parent to prevent a child to react to an event. - The second one is called âbubblingâ (or handling) and goes from the leaf to the root. This is to find the most specific element to handle the event. Cheers, Tudor > cheers -ben > >> >> Still, the way it is used in Bloc is different from the typical usage in that Bloc registers to all Events (which are Announcements) and then dispatches through them to specific Element method (like BlEventListener>>clickEvent:). Still the cool thing is that you also can still register from the outside to a specific event using a normal when:do:. >> >> We will write a piece of doc about it. >> >> Cheers, >> Tudor >> >> >>> On Jan 21, 2018, at 4:46 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>> this looks really cool. >>> For the event I remember the discussion with glenn about the difference and I forgot. >>> >>> Stef >>> >>>> On 21 Jan 2018, at 15:54, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> >>>> Hi, >>>> >>>> Here is an update of the work on Bloc and GT. As always, please do let us know what you think. >>>> >>>> Bloc: >>>> - Eventing saw a deep overhaul. They are now dispatched using the Announcements engine. The previous mechanism is still in place in order to help people compare the impact. In the process, we also cleaned the propagation of events, and we made them debuggable through inspector extensions: >>>> https://twitter.com/feenkcom/status/955086133519618048 >>>> https://twitter.com/feenkcom/status/946482609680539649 >>>> - Embedding Bloc elements in Morphic is even easier now: >>>> https://twitter.com/feenkcom/status/946676667002556416 >>>> - We continued the work towards an interactive creation of a graphical scene: >>>> https://twitter.com/feenkcom/status/948492946541858816 >>>> - Theme experiment >>>> >>>> GT: >>>> - The documentation of Mondrian is available when you download the code and can be viewed using GT Documenter: >>>> https://twitter.com/feenkcom/status/939394586115563520 >>>> - The Mondrian extensions of BlElement are now extracted in a more general package that enables Bloc elements to be used in graph scenes. >>>> >>>> Have fun, >>>> The feenk team >>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> www.feenk.com >>>> >>>> "Obvious things are difficult to teach." >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)list.inf.unibe.ch >>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>> >>> -------------------------------------------- >>> StÃ©phane Ducasse >>> http://stephane.ducasse.free.fr >>> http://www.synectique.eu / http://www.pharo.org >>> 03 59 35 87 52 >>> Assistant: Julie Jonas >>> 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 >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)list.inf.unibe.ch >>> https://www.list.inf.unibe.ch/listinfo/moose-dev >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Beauty is where we see it." >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com "Every thing should have the right to be different."

Jan. 21, 2018

Re: [Pharo-dev] [Pharo-users] ZnClient in Pharo 6.1 not working for Https on Windows

by phil＠highoctane.be

Back from the grave on this one but the current 6.1 is not fixed on that front and the antivirus (Defender) does not delete anything. This makes 6.1 an unusable target on Windows and 70 is also unusable. So, the only viable thing is a 50. This is not really serious. What's the point of piling features upon features if basic stuff is not working? Phil On Fri, Oct 6, 2017 at 6:32 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > both now I do not see what we can do if a third party tools consider > that we are a virus. > > On Fri, Oct 6, 2017 at 6:09 PM, Cyril Ferlicot D. > <cyril.ferlicot(a)gmail.com> wrote: > > Le 06/10/2017 Ã 13:02, kmo a Ã©crit : > >> I was trying to Soup on Windows 7 and found I could not access https > sites > >> > >> On windows 7 and 10 the following code fails: > >> > >> ZnEasy get:'https://genius.com/Alice-nuvole-lyrics'. > >> > >> This works fine in Pharo 5 on Windows. Also works fine with Pharo 6.1 > (32 > >> bit) on Linux. > >> > >> The problem is Pharo 6.1 on Windows. > >> > >> The error is: > >> > >> "SSL/TLS plugin initialization failed (VM plugin missing ? OS libraries > >> missing ?)" > >> > >> I know that his has been seen on Linux in the past - see > >> http://forum.world.st/SSL-TLS-plugin-initailization-failed- > VM-plugin-missing-OS-libraries-missing-td4945857.html > >> > >> I'm running the latest vm and 6.1 image. > >> > >> > >> > >> -- > >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >> > > > > I just saw that Windows Defender consider this plugin as a Trojan and > > delete it. > > > > Name of the menace: Trojan:Win32/Azden.A!cl > > > > Should this be reported on Pharo's issue tracker or on opensmalltalk one? > > > > -- > > Cyril Ferlicot > > https://ferlicot.fr > > > > http://www.synectique.eu > > 2 rue Jacques PrÃ©vert 01, > > 59650 Villeneuve d'ascq France > > > >

Jan. 21, 2018

Re: [Pharo-dev] [Moose-dev] Re: feenk log

by Ben Coman

On 21 January 2018 at 23:55, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > There is a difference in performance. The Announcement is slower (about 2-3x slower). However, for 1M events the difference is measured in a 200-400ms, which is very small. So you mean each event <1ms difference? btw, what is the biggest usage of events? I guess mouse movements? How many such events typically in 1 second of movement? How is performance on StackInterpreter VM? I guess we should keep that performant for platforms lacking JIT like iPads, etc... > The benefit of using Announcement is that we can reuse the tooling around Announcement, such as blogging and debugging. This looks really useful. Can you describe the difference between the red and blue lines in the picture of the first link? cheers -ben > > Still, the way it is used in Bloc is different from the typical usage in that Bloc registers to all Events (which are Announcements) and then dispatches through them to specific Element method (like BlEventListener>>clickEvent:). Still the cool thing is that you also can still register from the outside to a specific event using a normal when:do:. > > We will write a piece of doc about it. > > Cheers, > Tudor > > >> On Jan 21, 2018, at 4:46 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> this looks really cool. >> For the event I remember the discussion with glenn about the difference and I forgot. >> >> Stef >> >>> On 21 Jan 2018, at 15:54, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi, >>> >>> Here is an update of the work on Bloc and GT. As always, please do let us know what you think. >>> >>> Bloc: >>> - Eventing saw a deep overhaul. They are now dispatched using the Announcements engine. The previous mechanism is still in place in order to help people compare the impact. In the process, we also cleaned the propagation of events, and we made them debuggable through inspector extensions: >>> https://twitter.com/feenkcom/status/955086133519618048 >>> https://twitter.com/feenkcom/status/946482609680539649 >>> - Embedding Bloc elements in Morphic is even easier now: >>> https://twitter.com/feenkcom/status/946676667002556416 >>> - We continued the work towards an interactive creation of a graphical scene: >>> https://twitter.com/feenkcom/status/948492946541858816 >>> - Theme experiment >>> >>> GT: >>> - The documentation of Mondrian is available when you download the code and can be viewed using GT Documenter: >>> https://twitter.com/feenkcom/status/939394586115563520 >>> - The Mondrian extensions of BlElement are now extracted in a more general package that enables Bloc elements to be used in graph scenes. >>> >>> Have fun, >>> The feenk team >>> >>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "Obvious things are difficult to teach." >>> >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)list.inf.unibe.ch >>> https://www.list.inf.unibe.ch/listinfo/moose-dev >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr >> http://www.synectique.eu / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Julie Jonas >> 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 >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.tudorgirba.com > www.feenk.com > > "Beauty is where we see it." > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

Jan. 21, 2018

Re: [Pharo-dev] [Moose-dev] Re: feenk log

by StÃ©phane Ducasse

Thanks doru. Indeed having a good doc of bloc is important. I will try to get some times to have fun with boids butâ¦. Iâm more than full over the last 6 months. Stef > On 21 Jan 2018, at 16:55, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > There is a difference in performance. The Announcement is slower (about 2-3x slower). However, for 1M events the difference is measured in a 200-400ms, which is very small. > > The benefit of using Announcement is that we can reuse the tooling around Announcement, such as blogging and debugging. > > Still, the way it is used in Bloc is different from the typical usage in that Bloc registers to all Events (which are Announcements) and then dispatches through them to specific Element method (like BlEventListener>>clickEvent:). Still the cool thing is that you also can still register from the outside to a specific event using a normal when:do:. > > We will write a piece of doc about it. > > Cheers, > Tudor > > >> On Jan 21, 2018, at 4:46 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> this looks really cool. >> For the event I remember the discussion with glenn about the difference and I forgot. >> >> Stef >> >>> On 21 Jan 2018, at 15:54, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi, >>> >>> Here is an update of the work on Bloc and GT. As always, please do let us know what you think. >>> >>> Bloc: >>> - Eventing saw a deep overhaul. They are now dispatched using the Announcements engine. The previous mechanism is still in place in order to help people compare the impact. In the process, we also cleaned the propagation of events, and we made them debuggable through inspector extensions: >>> https://twitter.com/feenkcom/status/955086133519618048 >>> https://twitter.com/feenkcom/status/946482609680539649 >>> - Embedding Bloc elements in Morphic is even easier now: >>> https://twitter.com/feenkcom/status/946676667002556416 >>> - We continued the work towards an interactive creation of a graphical scene: >>> https://twitter.com/feenkcom/status/948492946541858816 >>> - Theme experiment >>> >>> GT: >>> - The documentation of Mondrian is available when you download the code and can be viewed using GT Documenter: >>> https://twitter.com/feenkcom/status/939394586115563520 >>> - The Mondrian extensions of BlElement are now extracted in a more general package that enables Bloc elements to be used in graph scenes. >>> >>> Have fun, >>> The feenk team >>> >>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "Obvious things are difficult to teach." >>> >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)list.inf.unibe.ch >>> https://www.list.inf.unibe.ch/listinfo/moose-dev >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr >> http://www.synectique.eu / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Julie Jonas >> 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 >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.tudorgirba.com > www.feenk.com > > "Beauty is where we see it." > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas 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

Jan. 21, 2018

Re: [Pharo-dev] [Moose-dev] Re: feenk log

by Tudor Girba

Hi, There is a difference in performance. The Announcement is slower (about 2-3x slower). However, for 1M events the difference is measured in a 200-400ms, which is very small. The benefit of using Announcement is that we can reuse the tooling around Announcement, such as blogging and debugging. Still, the way it is used in Bloc is different from the typical usage in that Bloc registers to all Events (which are Announcements) and then dispatches through them to specific Element method (like BlEventListener>>clickEvent:). Still the cool thing is that you also can still register from the outside to a specific event using a normal when:do:. We will write a piece of doc about it. Cheers, Tudor > On Jan 21, 2018, at 4:46 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > this looks really cool. > For the event I remember the discussion with glenn about the difference and I forgot. > > Stef > >> On 21 Jan 2018, at 15:54, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> Here is an update of the work on Bloc and GT. As always, please do let us know what you think. >> >> Bloc: >> - Eventing saw a deep overhaul. They are now dispatched using the Announcements engine. The previous mechanism is still in place in order to help people compare the impact. In the process, we also cleaned the propagation of events, and we made them debuggable through inspector extensions: >> https://twitter.com/feenkcom/status/955086133519618048 >> https://twitter.com/feenkcom/status/946482609680539649 >> - Embedding Bloc elements in Morphic is even easier now: >> https://twitter.com/feenkcom/status/946676667002556416 >> - We continued the work towards an interactive creation of a graphical scene: >> https://twitter.com/feenkcom/status/948492946541858816 >> - Theme experiment >> >> GT: >> - The documentation of Mondrian is available when you download the code and can be viewed using GT Documenter: >> https://twitter.com/feenkcom/status/939394586115563520 >> - The Mondrian extensions of BlElement are now extracted in a more general package that enables Bloc elements to be used in graph scenes. >> >> Have fun, >> The feenk team >> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Obvious things are difficult to teach." >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > http://www.synectique.eu / http://www.pharo.org > 03 59 35 87 52 > Assistant: Julie Jonas > 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 > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com "Beauty is where we see it."

Jan. 21, 2018

Re: [Pharo-dev] [Moose-dev] feenk log

by StÃ©phane Ducasse

this looks really cool. For the event I remember the discussion with glenn about the difference and I forgot. Stef > On 21 Jan 2018, at 15:54, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > Here is an update of the work on Bloc and GT. As always, please do let us know what you think. > > Bloc: > - Eventing saw a deep overhaul. They are now dispatched using the Announcements engine. The previous mechanism is still in place in order to help people compare the impact. In the process, we also cleaned the propagation of events, and we made them debuggable through inspector extensions: > https://twitter.com/feenkcom/status/955086133519618048 > https://twitter.com/feenkcom/status/946482609680539649 > - Embedding Bloc elements in Morphic is even easier now: > https://twitter.com/feenkcom/status/946676667002556416 > - We continued the work towards an interactive creation of a graphical scene: > https://twitter.com/feenkcom/status/948492946541858816 > - Theme experiment > > GT: > - The documentation of Mondrian is available when you download the code and can be viewed using GT Documenter: > https://twitter.com/feenkcom/status/939394586115563520 > - The Mondrian extensions of BlElement are now extracted in a more general package that enables Bloc elements to be used in graph scenes. > > Have fun, > The feenk team > > > -- > www.tudorgirba.com > www.feenk.com > > "Obvious things are difficult to teach." > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas 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

Jan. 21, 2018

feenk log

by Tudor Girba

Hi, Here is an update of the work on Bloc and GT. As always, please do let us know what you think. Bloc: - Eventing saw a deep overhaul. They are now dispatched using the Announcements engine. The previous mechanism is still in place in order to help people compare the impact. In the process, we also cleaned the propagation of events, and we made them debuggable through inspector extensions: https://twitter.com/feenkcom/status/955086133519618048 https://twitter.com/feenkcom/status/946482609680539649 - Embedding Bloc elements in Morphic is even easier now: https://twitter.com/feenkcom/status/946676667002556416 - We continued the work towards an interactive creation of a graphical scene: https://twitter.com/feenkcom/status/948492946541858816 - Theme experiment GT: - The documentation of Mondrian is available when you download the code and can be viewed using GT Documenter: https://twitter.com/feenkcom/status/939394586115563520 - The Mondrian extensions of BlElement are now extracted in a more general package that enables Bloc elements to be used in graph scenes. Have fun, The feenk team -- www.tudorgirba.com www.feenk.com "Obvious things are difficult to teach."

Jan. 21, 2018

[Pharo 70] Report period: 9 December 2017 to 20 January 2018

by Stephane Ducasse

Thank you all for all these improvements... * 20953-Gitlab Private Project Support (via Iceberg) >> Includes pharo-vcs/iceberg#558: Gitlab Private Project Support Issue URL: https://pharo.fogbugz.com/f/cases/20953 PR URL: https://github.com/pharo-project/pharo/pull/667 Diff URL: https://github.com/pharo-project/pharo/pull/667/files Thanks to seandenigris * 20992-Use-Stdio-class-instead-of-VTermOutputDriver >> Remove dependency to VTermOutputDriver in InspectorNavigator >> Fix consistency pb in Stdio class Issue URL: https://pharo.fogbugz.com/f/cases/20992 PR URL: https://github.com/pharo-project/pharo/pull/691 Diff URL: https://github.com/pharo-project/pharo/pull/691/files Thanks to VincentBlondeau * 20942-Integrate-Epicea-826-in-Ph7 >> Upgrade Epicea to 8.2.7 (but keep Cyril's contribution in this repository which is not copied upstream yet). >> >> Changes: >> >> - Fix case 20223. >> - Fix EpLog and OmFileStore #entryReferences, the result must have the same order as #entries. >> - Improve apply preview of class comments. >> - Sync with changes in Pharo 7: remove override of ZnBufferedWriteStream>>#cr since it''s already present in latest version of Zinc. >> - Improve some code comments. >> - Fix refactoring apply (general case) >> - Fix class rename refactoring Issue URL: https://pharo.fogbugz.com/f/cases/20942 PR URL: https://github.com/pharo-project/pharo/pull/690 Diff URL: https://github.com/pharo-project/pharo/pull/690/files Thanks to tinchodias * 20972-ShiftClassInstaller-do-not-announce-ClassModificationApplied-event >> Class changes should notify ClassModificationApplied for Pharo6 compatibility >> >> https://pharo.fogbugz.com/f/cases/20972/ShiftClassInstaller-do-not-announce… Issue URL: https://pharo.fogbugz.com/f/cases/20972 PR URL: https://github.com/pharo-project/pharo/pull/684 Diff URL: https://github.com/pharo-project/pharo/pull/684/files Thanks to dionisiydk * 20962-Rubric-should-not-depends-on-NautilusCommons2 >> RubCommentAnnotationDisplayer is moved to Nautilus under tag Rubric >> >> https://pharo.fogbugz.com/f/cases/20962/Rubric-should-not-depends-on-Nautil… Issue URL: https://pharo.fogbugz.com/f/cases/20962 PR URL: https://github.com/pharo-project/pharo/pull/688 Diff URL: https://github.com/pharo-project/pharo/pull/688/files Thanks to dionisiydk * 20979-Introducing-DoubleWord-and-DoubleByte-arrays >> https://pharo.fogbugz.com/f/cases/20979/Introducing-DoubleWord-and-DoubleBy… >> >> (Needed for VMMaker compatibility) Issue URL: https://pharo.fogbugz.com/f/cases/20979 PR URL: https://github.com/pharo-project/pharo/pull/689 Diff URL: https://github.com/pharo-project/pharo/pull/689/files Thanks to clementbera * 20978-PharoIssueTest-should-be-long-time-test >> 1 minute time limit for PharoIssueTest. >> >> https://pharo.fogbugz.com/f/cases/20978/PharoIssueTest-should-be-long-time-… Issue URL: https://pharo.fogbugz.com/f/cases/20978 PR URL: https://github.com/pharo-project/pharo/pull/687 Diff URL: https://github.com/pharo-project/pharo/pull/687/files Thanks to dionisiydk * 20936-64bit-primitiveFailure-for-10-largeIdentityHash >> https://pharo.fogbugz.com/f/cases/20936/64bit-primitiveFailure-for-1-0-larg… Issue URL: https://pharo.fogbugz.com/f/cases/20936 PR URL: https://github.com/pharo-project/pharo/pull/653 Diff URL: https://github.com/pharo-project/pharo/pull/653/files Thanks to Ducasse * 20976-wrong-FLPharo7Platform-initialization >> https://pharo.fogbugz.com/f/cases/20976/wrong-FLPharo7Platform-initializati… Issue URL: https://pharo.fogbugz.com/f/cases/20976 PR URL: https://github.com/pharo-project/pharo/pull/686 Diff URL: https://github.com/pharo-project/pharo/pull/686/files Thanks to pavel-krivanek * 20975-Fix-baselines-after-Fuel-update-case-20970 >> https://pharo.fogbugz.com/f/cases/20975/Fix-baselines-after-Fuel-update-cas… Issue URL: https://pharo.fogbugz.com/f/cases/20975 PR URL: https://github.com/pharo-project/pharo/pull/685 Diff URL: https://github.com/pharo-project/pharo/pull/685/files Thanks to pavel-krivanek * 20970 remove pharo 6 platform class from pharo 7 >> Added Fuel platform class for Pharo 7. >> Removed Fuel platform class for Pharo 6. >> >> Replaces https://github.com/pharo-project/pharo/pull/674. >> >> https://pharo.fogbugz.com/f/cases/20970/Remove-Pharo-6-platform-class-from-… >> >> https://github.com/theseion/Fuel/issues/227 Issue URL: https://pharo.fogbugz.com/f/cases/20970 remove pharo 6 platform class from pharo 7 PR URL: https://github.com/pharo-project/pharo/pull/682 Diff URL: https://github.com/pharo-project/pharo/pull/682/files Thanks to theseion * 20952 Super setUp need to be called in ExampleSetTest, SessionManagerRegistrationOrderTest, GTS and GLM prefixed tests >> add missing super setUp calls. >> >> https://pharo.fogbugz.com/f/cases/20952/Super-setUp-need-to-be-called-in-Ex… Issue URL: https://pharo.fogbugz.com/f/cases/20952 Super setUp need to be called in ExampleSetTest, SessionManagerRegistrationOrderTest, GTS and GLM prefixed tests PR URL: https://github.com/pharo-project/pharo/pull/666 Diff URL: https://github.com/pharo-project/pharo/pull/666/files Thanks to astares * 20968 Unused temps in various GML methods >> >> Fix unused temps in >> >> GLMWizard>>#updateWhenPrevious >> GLMExpanderLabelNodeModel>>#elementColumn >> GLMListMorphicTest>>#testTextBackgroundColor >> GLMPortTest>>#testTransientValue" >> GLMPresentationTest>>#testCopyTheTransformation >> GLMTabulatorMorphicTest>>#testMultipleInitialSelection >> GLMTextMorphicTest>>#testResettingTheSelection >> GLMWizard>>#updatePane >> >> https://pharo.fogbugz.com/f/cases/20968/Unused-temps-in-various-GML-methods Issue URL: https://pharo.fogbugz.com/f/cases/20968 Unused temps in various GML methods PR URL: https://github.com/pharo-project/pharo/pull/680 Diff URL: https://github.com/pharo-project/pharo/pull/680/files Thanks to astares * 20967 Unused temps in CompiledMethodTest>>#testOrigin >> fix unsed temp var >> >> https://pharo.fogbugz.com/f/cases/20967/Unused-temps-in-CompiledMethodTest-… Issue URL: https://pharo.fogbugz.com/f/cases/20967 Unused temps in CompiledMethodTest>>#testOrigin PR URL: https://github.com/pharo-project/pharo/pull/678 Diff URL: https://github.com/pharo-project/pharo/pull/678/files Thanks to astares * 20964 Unused temp variables in ConfigurationCommandLineHandler >> remove unused temp var >> >> https://pharo.fogbugz.com/f/cases/20964/Unused-temp-variables-in-Configurat… Issue URL: https://pharo.fogbugz.com/f/cases/20964 Unused temp variables in ConfigurationCommandLineHandler PR URL: https://github.com/pharo-project/pharo/pull/675 Diff URL: https://github.com/pharo-project/pharo/pull/675/files Thanks to astares * 20965 Unused temp variables in BaselineOfBasicTools and BaselineOfMorphic >> fix unsued temp variables Issue URL: https://pharo.fogbugz.com/f/cases/20965 Unused temp variables in BaselineOfBasicTools and BaselineOfMorphic PR URL: https://github.com/pharo-project/pharo/pull/676 Diff URL: https://github.com/pharo-project/pharo/pull/676/files Thanks to astares * 20966 Unused temps in Base64MimeConverterTest>>#testDecodeMimeHeader >> remove unused temp vars Issue URL: https://pharo.fogbugz.com/f/cases/20966 Unused temps in Base64MimeConverterTest>>#testDecodeMimeHeader PR URL: https://github.com/pharo-project/pharo/pull/677 Diff URL: https://github.com/pharo-project/pharo/pull/677/files Thanks to astares * 20921 PackageChecker>>check not needed anymore >> It is the only method in this class. We move this class to Deprecated70 to remove it in Pharo 8 >> >> https://pharo.fogbugz.com/f/cases/20921/PackageChecker-check-not-needed-any… Issue URL: https://pharo.fogbugz.com/f/cases/20921 PackageChecker>>check not needed anymore PR URL: https://github.com/pharo-project/pharo/pull/679 Diff URL: https://github.com/pharo-project/pharo/pull/679/files Thanks to astares * 20963-Corrupted-SmartSuggestions-package >> https://pharo.fogbugz.com/f/cases/20963/Corrupted-SmartSuggestions-package Issue URL: https://pharo.fogbugz.com/f/cases/20963 PR URL: https://github.com/pharo-project/pharo/pull/673 Diff URL: https://github.com/pharo-project/pharo/pull/673/files Thanks to pavel-krivanek * 20971 - Class comment and method format fixes >> Removed invalid characters from Dictionary class comment. >> Removed '.' at the end of selectors. >> >> https://pharo.fogbugz.com/f/cases/20971/Class-comment-and-method-format-fix… Issue URL: https://pharo.fogbugz.com/f/cases/20971 PR URL: https://github.com/pharo-project/pharo/pull/683 Diff URL: https://github.com/pharo-project/pharo/pull/683/files Thanks to theseion * 20969 Unused temp var in ZnRequestTests>>#testCookiesWriting >> https://pharo.fogbugz.com/f/cases/20969/ Issue URL: https://pharo.fogbugz.com/f/cases/20969 Unused temp var in ZnRequestTests>>#testCookiesWriting PR URL: https://github.com/pharo-project/pharo/pull/681 Diff URL: https://github.com/pharo-project/pharo/pull/681/files Thanks to astares * 20961 Broken Tonel file in FuelTests in pharo-project/pharo repo >> Fix Tonel format (Bug 20961) >> >> https://pharo.fogbugz.com/f/cases/resolve/20961/Broken-Tonel-file-in-FuelTe… Issue URL: https://pharo.fogbugz.com/f/cases/20961 Broken Tonel file in FuelTests in pharo PR URL: https://github.com/pharo-project/pharo/pull/670 Diff URL: https://github.com/pharo-project/pharo/pull/670/files Thanks to astares * 20960-Move-ExecutionDisplayPlugin-from-Reflectivity-Examples-directly-to-Nautilus- >> ExecutionDisplayPlugin and ExecutionDisplayMorph are moved to the Nautilus under 'Plugins-Examples' tag. >> >> https://pharo.fogbugz.com/f/cases/20960/Move-ExecutionDisplayPlugin-from-Re… Issue URL: https://pharo.fogbugz.com/f/cases/20960 PR URL: https://github.com/pharo-project/pharo/pull/671 Diff URL: https://github.com/pharo-project/pharo/pull/671/files Thanks to dionisiydk * 20958-SmartSuggestions-should-not-depends-on-Nautilus >> SmartSuggestions do not depends on Nautilus anymore. >> Nautilus depends on it Issue URL: https://pharo.fogbugz.com/f/cases/20958 PR URL: https://github.com/pharo-project/pharo/pull/669 Diff URL: https://github.com/pharo-project/pharo/pull/669/files Thanks to dionisiydk * 20913 Gofer-Tests package cleanup (solve critiques) >> - use assert:equals: instead of = >> - use cascading where possible >> cosmetic changes only, no change of functionality Issue URL: https://pharo.fogbugz.com/f/cases/20913 Gofer PR URL: https://github.com/pharo-project/pharo/pull/638 Diff URL: https://github.com/pharo-project/pharo/pull/638/files Thanks to astares * Updated Fuel to 2.2.0 with the 64 bit adaptations >> https://pharo.manuscript.com/f/cases/20120/Fuel-is-not-64bits-ready Issue URL: https://pharo.fogbugz.com/f/cases/Updated Fuel to 2.2.0 with the 64 bit adaptations PR URL: https://github.com/pharo-project/pharo/pull/654 Diff URL: https://github.com/pharo-project/pharo/pull/654/files Thanks to theseion * 20879-ZnCrPortableWriteStreamnextPut-swallows-LFs >> 20879 ZnCrPortableWriteStream>>nextPut: swallows LFs >> >> - Fix ZnCrPortableWriteStream>>nextPut: so that Character lf is correctly written. >> - Add ZnCrPortableWriteStreamTests to confirm fix. >> >> Fogbugz: https://pharo.fogbugz.com/f/cases/20879 Issue URL: https://pharo.fogbugz.com/f/cases/20879 PR URL: https://github.com/pharo-project/pharo/pull/613 Diff URL: https://github.com/pharo-project/pharo/pull/613/files Thanks to akgrant43 * 20949 Use category "utilities" instead of "utils" in TheManifestBuilder >> "utilities" instead of "utils" recategorization >> >> https://pharo.fogbugz.com/f/cases/20949/Use-category-utilities-instead-of-u… Issue URL: https://pharo.fogbugz.com/f/cases/20949 Use category "utilities" instead of "utils" in TheManifestBuilder PR URL: https://github.com/pharo-project/pharo/pull/665 Diff URL: https://github.com/pharo-project/pharo/pull/665/files Thanks to astares * 20938-Add-PrimitiveError-to-Pharo >> 20938-Add-PrimitiveError-to-Pharo >> >> Add PrimitiveError and update the SmalltalkImage special objects array to point to it. >> >> See: https://pharo.fogbugz.com/f/cases/20938/ Issue URL: https://pharo.fogbugz.com/f/cases/20938 PR URL: https://github.com/pharo-project/pharo/pull/660 Diff URL: https://github.com/pharo-project/pharo/pull/660/files Thanks to akgrant43 * 20946-Modifying-a-class-with-read-only-instances-should-raise-a-proper-error >> Modifying a class with read only instances should raise a proper error. >> When a class is modified and it has read-only instances the migration process is not possible. >> The class installer should report a proper error. >> Also all the subinstances should be checked. >> >> Issue: https://pharo.fogbugz.com/f/cases/20946/Modifying-a-class-with-read-only-in… Issue URL: https://pharo.fogbugz.com/f/cases/20946 PR URL: https://github.com/pharo-project/pharo/pull/662 Diff URL: https://github.com/pharo-project/pharo/pull/662/files Thanks to tesonep * Add Shift class builder, Tonel and other improvements to Welcome changeLog >> https://pharo.fogbugz.com/f/cases/20955/Add-Shift-class-builder-Tonel-and-o… Issue URL: https://pharo.fogbugz.com/f/cases/Add Shift class builder, Tonel and other improvements to Welcome changeLog PR URL: https://github.com/pharo-project/pharo/pull/668 Diff URL: https://github.com/pharo-project/pharo/pull/668/files Thanks to astares * 20947-NautilusRefactoring-package-should-not-depends-on-Nautilus-package >> It was almost all about method extensions which reference Nautils or NautilusUI but was packaged as NautilusRefactoring. >> So now they are extended directly by Nautilus package Issue URL: https://pharo.fogbugz.com/f/cases/20947 PR URL: https://github.com/pharo-project/pharo/pull/663 Diff URL: https://github.com/pharo-project/pharo/pull/663/files Thanks to dionisiydk * 20948-Remove-dependency-from-Nautilus-form-FT-examples >> Now actionIcon is constantly #scriptManagerIcon. >> >> https://pharo.fogbugz.com/f/cases/20948/Remove-dependency-from-Nautilus-for… Issue URL: https://pharo.fogbugz.com/f/cases/20948 PR URL: https://github.com/pharo-project/pharo/pull/664 Diff URL: https://github.com/pharo-project/pharo/pull/664/files Thanks to dionisiydk * 20945-Dependency-browser-should-not-depends-on-Nautilus >> All dependency to Nautilus is fixed. And all nautilus based names are renamed Issue URL: https://pharo.fogbugz.com/f/cases/20945 PR URL: https://github.com/pharo-project/pharo/pull/661 Diff URL: https://github.com/pharo-project/pharo/pull/661/files Thanks to dionisiydk * 20936-64bit-primitiveFailure-for-1-0-largeIdentityHash >> https://pharo.manuscript.com/f/cases/20936/64bit-primitiveFailure-for-1-0-l… >> >> Fixes on all identityHash and basicIdentityHash methods to make them work in 32 and 64 bits. >> Be careful not to create large integers Issue URL: https://pharo.fogbugz.com/f/cases/20936 PR URL: https://github.com/pharo-project/pharo/pull/658 Diff URL: https://github.com/pharo-project/pharo/pull/658/files Thanks to clementbera * 20934-Missing-implementation-for-supporting-read-only-onjects >> Added implementations and tests for read-only objects. A lot of methods do not throw an exception if a primitive fails through read-only-ness. Furthermore some assumptions about failing primitives are wrong in pharo and these have been corrected in order to handle properly a modification error. Made ModificationForbidden an exception instead of an error because it can be resumed. Issue URL: https://pharo.fogbugz.com/f/cases/20934 PR URL: https://github.com/pharo-project/pharo/pull/656 Diff URL: https://github.com/pharo-project/pharo/pull/656/files Thanks to noha * 20939-Updating-Shift-to-v1-0-2 >> Updating to the new version of Shift Class Builder and Installer (v1.0.2). >> >> Issue: https://pharo.manuscript.com/f/cases/20939 >> >> It fixes: >> >> - It copies the slots that have indexes in a better way. This fixes a problem with migrating instances when there is changes in different levels of the hierarchy. >> - Fixes a problem that was losing the category of class side methods when some changes where produced. >> - Adding tests for all these situations. >> - Extending the class installer to have an installation environment separate from the build environment. >> - Fixes also Issue 20882. https://pharo.fogbugz.com/f/cases/20882/New-class-installer-adds-anonymous-… >> Issue URL: https://pharo.fogbugz.com/f/cases/20939 PR URL: https://github.com/pharo-project/pharo/pull/655 Diff URL: https://github.com/pharo-project/pharo/pull/655/files Thanks to tesonep * 16969-Use-a-Rectangle-instead-of-a-Margin >> redo the broken Stef's PR https://github.com/pharo-project/pharo/pull/601 Issue URL: https://pharo.fogbugz.com/f/cases/16969 PR URL: https://github.com/pharo-project/pharo/pull/650 Diff URL: https://github.com/pharo-project/pharo/pull/650/files Thanks to pavel-krivanek * Fix broken Tonel for #nonEmptyWithCopyNonIdentical >> All details in >> >> https://pharo.fogbugz.com/f/cases/20932/ Issue URL: https://pharo.fogbugz.com/f/cases/Fix broken Tonel for #nonEmptyWithCopyNonIdentical PR URL: https://github.com/pharo-project/pharo/pull/651 Diff URL: https://github.com/pharo-project/pharo/pull/651/files Thanks to astares * 20875-Alternative-dictionary-creation-method >> - Re-adding newFromKeys:andValues: to dictionary. >> - Adding it to SmallDictionary and OrderedDictionary. >> - Adding tests to such classes too. >> - All tests are green. Issue URL: https://pharo.fogbugz.com/f/cases/20875 PR URL: https://github.com/pharo-project/pharo/pull/617 Diff URL: https://github.com/pharo-project/pharo/pull/617/files Thanks to Ducasse * 20925 Super setUp need to be called in UnifiedFFI tests >> call super setUp in >> - FFICalloutMethodBuilderTest>>setUp >> - FFICalloutTests>>setUp >> - FFIExternalStructureFieldParserTests>>setUp >> >> and add some more class comments >> >> https://pharo.fogbugz.com/f/cases/20925/Super-setUp-need-to-be-called-in-Un… Issue URL: https://pharo.fogbugz.com/f/cases/20925 Super setUp need to be called in UnifiedFFI tests PR URL: https://github.com/pharo-project/pharo/pull/645 Diff URL: https://github.com/pharo-project/pharo/pull/645/files Thanks to astares * 20926-Super-setUp-need-to-be-called-in-MCWorkingCopyBrowserTest >> call super setUp in setUp >> >> https://pharo.fogbugz.com/f/cases/20926/Super-setUp-need-to-be-called-in-MC… Issue URL: https://pharo.fogbugz.com/f/cases/20926 PR URL: https://github.com/pharo-project/pharo/pull/646 Diff URL: https://github.com/pharo-project/pharo/pull/646/files Thanks to astares * 20924 Fix unused var tutorial in TutorialPlayerTestWithMockTutorial>>setUp >> make use of tutorial variable Issue URL: https://pharo.fogbugz.com/f/cases/20924 Fix unused var tutorial in TutorialPlayerTestWithMockTutorial>>setUp PR URL: https://github.com/pharo-project/pharo/pull/644 Diff URL: https://github.com/pharo-project/pharo/pull/644/files Thanks to astares * 20916 Use category "utilities" instead of "utils" in Kernel classes >> utils -> utilities >> >> only recategorization, no change in behavior Issue URL: https://pharo.fogbugz.com/f/cases/20916 Use category "utilities" instead of "utils" in Kernel classes PR URL: https://github.com/pharo-project/pharo/pull/640 Diff URL: https://github.com/pharo-project/pharo/pull/640/files Thanks to astares * Cleanup of SimpleButtonMorph newWithLabel to have a yourself >> add missing yourself >> (the brace is not necessary but for better readability according to BPP) >> >> >> https://pharo.fogbugz.com/f/cases/20909/SimpleButtonMorph-newWithLabel-shou… Issue URL: https://pharo.fogbugz.com/f/cases/Cleanup of SimpleButtonMorph newWithLabel to have a yourself PR URL: https://github.com/pharo-project/pharo/pull/635 Diff URL: https://github.com/pharo-project/pharo/pull/635/files Thanks to astares * 20927 - Super setUp need to be called in FileSystem-Tests >> call super setUp in >> - FileReferenceTest >> - FileSystemHandleTest >> - FileSystemResolverTest >> - FileSystemTest >> >> https://pharo.fogbugz.com/f/cases/20927/Super-setUp-need-to-be-called-in-Fi… Issue URL: https://pharo.fogbugz.com/f/cases/20927 PR URL: https://github.com/pharo-project/pharo/pull/647 Diff URL: https://github.com/pharo-project/pharo/pull/647/files Thanks to astares * 20920 RPackageOrganizer should use packageClass instead of RPackage references >> https://pharo.fogbugz.com/f/cases/20920/RPackageOrganizer-should-use-packag… Issue URL: https://pharo.fogbugz.com/f/cases/20920 RPackageOrganizer should use packageClass instead of RPackage references PR URL: https://github.com/pharo-project/pharo/pull/648 Diff URL: https://github.com/pharo-project/pharo/pull/648/files Thanks to astares * 20911 Cleanup MCClassDefinitionTest >> - categorize methods >> - use assert:equal: instead of = >> >> no change in behavior >> >> https://pharo.fogbugz.com/f/cases/20911/Cleanup-MCClassDefinitionTest Issue URL: https://pharo.fogbugz.com/f/cases/20911 Cleanup MCClassDefinitionTest PR URL: https://github.com/pharo-project/pharo/pull/637 Diff URL: https://github.com/pharo-project/pharo/pull/637/files Thanks to astares * 20918 Super setUp need to be called in Collections-Tests >> call super setUp in setUp method Issue URL: https://pharo.fogbugz.com/f/cases/20918 Super setUp need to be called in Collections PR URL: https://github.com/pharo-project/pharo/pull/642 Diff URL: https://github.com/pharo-project/pharo/pull/642/files Thanks to astares * 20922-Update-Iceberg-to-v066 >> https://pharo.fogbugz.com/f/cases/20922/Update-Iceberg-to-v0-6-6 >> >> Update Iceberg to v0.6.6 Issue URL: https://pharo.fogbugz.com/f/cases/20922 PR URL: https://github.com/pharo-project/pharo/pull/643 Diff URL: https://github.com/pharo-project/pharo/pull/643/files Thanks to pavel-krivanek * Categorize methods in MCMczInstallerTest >> https://pharo.fogbugz.com/f/cases/20910/Categorize-methods-in-MCMczInstalle… Issue URL: https://pharo.fogbugz.com/f/cases/Categorize methods in MCMczInstallerTest PR URL: https://github.com/pharo-project/pharo/pull/636 Diff URL: https://github.com/pharo-project/pharo/pull/636/files Thanks to astares * 20917-Super-setUp-need-to-be-called-in-Debugger-Tests >> call super setUp >> >> https://pharo.fogbugz.com/f/cases/20917/Super-setUp-need-to-be-called-in-De… Issue URL: https://pharo.fogbugz.com/f/cases/ 20917 PR URL: https://github.com/pharo-project/pharo/pull/641 Diff URL: https://github.com/pharo-project/pharo/pull/641/files Thanks to astares * 20914-remove-remaining-halt >> remove halt. >> >> fixes issue #20914 Issue URL: https://pharo.fogbugz.com/f/cases/20914 PR URL: https://github.com/pharo-project/pharo/pull/639 Diff URL: https://github.com/pharo-project/pharo/pull/639/files Thanks to estebanlm * 20891-Changesorter-should-prompt-with-a-file-dialog >> first version for https://pharo.fogbugz.com/f/cases/20891/Changesorter-should-prompt-with-a-f… Issue URL: https://pharo.fogbugz.com/f/cases/20891 PR URL: https://github.com/pharo-project/pharo/pull/628 Diff URL: https://github.com/pharo-project/pharo/pull/628/files Thanks to Ducasse * 20899-Add-comments-to-Color-methods >> Adding comments to instance method and introducing more protocols + removing broken code from class comments. >> https://pharo.fogbugz.com/f/cases/20899/Add-comments-to-Color-methods Issue URL: https://pharo.fogbugz.com/f/cases/20899 PR URL: https://github.com/pharo-project/pharo/pull/633 Diff URL: https://github.com/pharo-project/pharo/pull/633/files Thanks to Ducasse * 20823-sumNumbers-without-block-is-missing-for-collections >> sumNumbers is added as missing handy function to sum array items which are numbers Issue URL: https://pharo.fogbugz.com/f/cases/20823 PR URL: https://github.com/pharo-project/pharo/pull/619 Diff URL: https://github.com/pharo-project/pharo/pull/619/files Thanks to dionisiydk * 20797-Exception-class-missing-a-method >> Adding a new constructor to exception to include the tag. >> And adding a test for it. Issue URL: https://pharo.fogbugz.com/f/cases/20797 PR URL: https://github.com/pharo-project/pharo/pull/622 Diff URL: https://github.com/pharo-project/pharo/pull/622/files Thanks to tesonep * 20888-printOndelimiter-is-broken >> https://pharo.fogbugz.com/f/cases/20888/printOn-delimiter-is-broken >> >> write the delimiter as string, not as printString Issue URL: https://pharo.fogbugz.com/f/cases/20888 PR URL: https://github.com/pharo-project/pharo/pull/626 Diff URL: https://github.com/pharo-project/pharo/pull/626/files Thanks to pavel-krivanek * 20694-Do-we-need-Objecthead-and-Objecttail- >> Renamed the #head and #tail methods injected by the Morphic-Base package into the Object and Association class to #treeNodeHead and #treeNodeTail. >> Reflected the change to the code of the MorphTreeNodeMorph class that was using these two methods. Issue URL: https://pharo.fogbugz.com/f/cases/20694 PR URL: https://github.com/pharo-project/pharo/pull/623 Diff URL: https://github.com/pharo-project/pharo/pull/623/files Thanks to dupriezt * 19913-Nautilus-Class-pane-have-a-weird-behavior-when-we-hold-shift-while-clicking-on-classes >> >> Fixing the nautilus class selection to work properly in both scenarios, when selecting only one or multiple. >> >> https://pharo.fogbugz.com/f/cases/19913 Issue URL: https://pharo.fogbugz.com/f/cases/19913 PR URL: https://github.com/pharo-project/pharo/pull/625 Diff URL: https://github.com/pharo-project/pharo/pull/625/files Thanks to tesonep * 20886-Undeclared-RBMethodHasNoTimeStampRule- >> https://pharo.fogbugz.com/f/cases/20886/Undeclared-RBMethodHasNoTimeStampRu… >> >> remove undeclared reference Issue URL: https://pharo.fogbugz.com/f/cases/20886 PR URL: https://github.com/pharo-project/pharo/pull/624 Diff URL: https://github.com/pharo-project/pharo/pull/624/files Thanks to pavel-krivanek * 20817-Disable-or-remove-RBMethodHasNoTimeStampRule >> https://pharo.fogbugz.com/f/cases/20817/ >> >> remove RBMethodHasNoTimeStampRule Issue URL: https://pharo.fogbugz.com/f/cases/20817 PR URL: https://github.com/pharo-project/pharo/pull/620 Diff URL: https://github.com/pharo-project/pharo/pull/620/files Thanks to pavel-krivanek * 20813-Improve-comments-of-ifNotNil-and-ifNotNilifNil >> https://pharo.fogbugz.com/f/cases/20813/ >> >> ifNil.cs by Stef Issue URL: https://pharo.fogbugz.com/f/cases/20813 PR URL: https://github.com/pharo-project/pharo/pull/618 Diff URL: https://github.com/pharo-project/pharo/pull/618/files Thanks to pavel-krivanek * 20861-split-and-friends-should-have-better-comments >> https://pharo.fogbugz.com/f/cases/20861/split-and-friends-should-have-bette… Issue URL: https://pharo.fogbugz.com/f/cases/20861 PR URL: https://github.com/pharo-project/pharo/pull/611 Diff URL: https://github.com/pharo-project/pharo/pull/611/files Thanks to Ducasse * 20880-failing-test-testIfCompletelyBroken >> https://pharo.fogbugz.com/f/cases/20880/failing-test-testIfCompletelyBroken >> fix the exected numbers Issue URL: https://pharo.fogbugz.com/f/cases/20880 PR URL: https://github.com/pharo-project/pharo/pull/614 Diff URL: https://github.com/pharo-project/pharo/pull/614/files Thanks to pavel-krivanek * 20876-Drag-and-drop-of-methods-is-broken >> Nautilus widgets should return TransferPresenter instead of TransferMorph because Nautilus uses data source of Spec component which supposed to work with presenters. >> It fixes drag and drop in Nautilus. >> >> AbstractWidgetPresenter fix in wants drop check. It allow only #isTransferable draggedMorphs. It fixes general drag of windows over spec based fast tables . >> >> https://pharo.manuscript.com/f/cases/20876/Drag-and-drop-of-methods-is-brok… Issue URL: https://pharo.fogbugz.com/f/cases/20876 PR URL: https://github.com/pharo-project/pharo/pull/616 Diff URL: https://github.com/pharo-project/pharo/pull/616/files Thanks to dionisiydk * 15473-Float-round-to-n-decimal-places-is-not-in-agreement-with-printShowingDecimalPlaces >> This is issue: >> https://pharo.fogbugz.com/f/cases/15473/Float-round-to-n-decimal-places-is-… >> >> It also fixes: >> https://pharo.fogbugz.com/f/cases/15472/Fraction-rounding-to-n-decimal-plac… >> https://pharo.fogbugz.com/f/cases/15471/Can-t-round-Float-fmax-to-2-decimal… >> >> Note: the new implementation does round exact tie away from zero exactly like #round do. >> It is also in agreement with printShowingDecimalPlaces: >> >> If you wish to roundToNearestTieToEven, then please open a new issue >> (but it will be better to also modify printShowingDecimalPlaces: then) >> >> The new implementation is a bit slower but it is correct. >> >> It was proposed to deprecate round: in >> >> Iâm not so sure - round: can be useful for monetary apps and is available in other languages (Python, etcâ¦) >> banker rounding (tie to even) might be a better option though. >> >> Last, Iâve replaced the `< expr: foo result: bar>` annotation with `â foo >>> bar â` >> The reason is that the expr:result: form only works for a literal result which is SEVERLY limited. Issue URL: https://pharo.fogbugz.com/f/cases/15473 PR URL: https://github.com/pharo-project/pharo/pull/514 Diff URL: https://github.com/pharo-project/pharo/pull/514/files Thanks to nicolas-cellier-aka-nice * 20872-WidgetExamples-classexampleDialogs-is-broken-in-Pharo-7 >> 20872 WidgetExamples class>>exampleDialogs is broken in Pharo 7 >> >> See: https://pharo.fogbugz.com/f/cases/20872/WidgetExamples-class-exampleDialogs… Issue URL: https://pharo.fogbugz.com/f/cases/20872 PR URL: https://github.com/pharo-project/pharo/pull/610 Diff URL: https://github.com/pharo-project/pharo/pull/610/files Thanks to akgrant43 * 20796-String-should-understand-readStreamDowriteStreamDo-to-be-polymorph-with-FileReference >> Add #readStreamDo: and #writeStreamDo: to SequeanceableCollection with a comment and a test in StringTest >> >> Case 20796 : String should understand #readStreamDo:/#writeStreamDo: to be polymorph with FileReference Issue URL: https://pharo.fogbugz.com/f/cases/20796 PR URL: https://github.com/pharo-project/pharo/pull/605 Diff URL: https://github.com/pharo-project/pharo/pull/605/files Thanks to jecisc * 20808 createRepositoryURLtoNameMappings needs to be more flexible >> https://pharo.fogbugz.com/f/cases/20808/createRepositoryURLtoNameMappings-n… Issue URL: https://pharo.fogbugz.com/f/cases/20808 createRepositoryURLtoNameMappings needs to be more flexible PR URL: https://github.com/pharo-project/pharo/pull/587 Diff URL: https://github.com/pharo-project/pharo/pull/587/files Thanks to astares * 20869-Add-tooltips-to-world-menu-entries >> - Add help to every menu entry of the world menu >> - Be sur every help begin with an uppercase and end with a dot >> - Add a release test to be sure we do not integrate a tool without help menu later >> >> Case 20869 : https://pharo.fogbugz.com/f/cases/20869/Add-tooltips-to-world-menu-entries >> >> /!\/!\/!\ To integrate after https://github.com/pharo-vcs/iceberg/pull/538 for the release test /!\/!\/!\ Issue URL: https://pharo.fogbugz.com/f/cases/20869 PR URL: https://github.com/pharo-project/pharo/pull/606 Diff URL: https://github.com/pharo-project/pharo/pull/606/files Thanks to jecisc * 20864-add-examples-to-SequenceableCollectionaggregateRuns >> rename aggregateRuns: to groupByRuns: and add some examples. Deprecate the coriginal method >> >> https://pharo.fogbugz.com/f/cases/20864/add-examples-to-SequenceableCollect… Issue URL: https://pharo.fogbugz.com/f/cases/20864 PR URL: https://github.com/pharo-project/pharo/pull/607 Diff URL: https://github.com/pharo-project/pharo/pull/607/files Thanks to pavel-krivanek * 20836-Cleaning-comments >> https://pharo.fogbugz.com/f/cases/20836/Cleaning-comments Issue URL: https://pharo.fogbugz.com/f/cases/20836 PR URL: https://github.com/pharo-project/pharo/pull/595 Diff URL: https://github.com/pharo-project/pharo/pull/595/files Thanks to Ducasse * 20870-Spec-FastTable-badly-support-drag-and-drop >> missing methods are added. >> I tested them in Commander-Examples Issue URL: https://pharo.fogbugz.com/f/cases/20870 PR URL: https://github.com/pharo-project/pharo/pull/608 Diff URL: https://github.com/pharo-project/pharo/pull/608/files Thanks to dionisiydk * 20684-Categorizer-should-categorize-reset-methods-in-initialization-protocol >> Categorizer should categorize #reset methods in 'initialization' protocol. >> >> ML subject: http://forum.world.st/Convention-for-quot-reset-quot-methods-td5019493.html >> >> Resolve case 20684 : Categorizer should categorize #reset methods in 'initialization' protocol Issue URL: https://pharo.fogbugz.com/f/cases/20684 PR URL: https://github.com/pharo-project/pharo/pull/604 Diff URL: https://github.com/pharo-project/pharo/pull/604/files Thanks to jecisc * 20859-Update-Hermes-to-detect-new-Undeclared-and-overwritten-methods-and-classes >> Integrating the version 2.3.0 that detects if new Undeclared are created when loading a package and if methods and classes are overwritten. >> >> This is to detect no well resolved dependencies during the bootstrap. >> >> https://pharo.fogbugz.com/f/cases/20859/Update-Hermes-to-detect-new-Undecla… Issue URL: https://pharo.fogbugz.com/f/cases/20859 PR URL: https://github.com/pharo-project/pharo/pull/597 Diff URL: https://github.com/pharo-project/pharo/pull/597/files Thanks to tesonep * 20832-boostrap-process-should-use-IceProxyMCVersionInfo-instead-system-repositories >> fix case #20832 >> >> THIS CHANGES THE CONTRIBUTION PROCESS SO DO NOT INTEGRATE UNTIL I HAVE TIME TO EXPLAIN IN LISTS ;) Issue URL: https://pharo.fogbugz.com/f/cases/20832 PR URL: https://github.com/pharo-project/pharo/pull/584 Diff URL: https://github.com/pharo-project/pharo/pull/584/files Thanks to estebanlm * 20680-Add-comments-to-FileSystem-packages >> Add packages comments to FileSystem packages. >> >> See case 20680 : https://pharo.fogbugz.com/f/cases/20680/Add-comments-to-FileSystem-packages >> >> Please, review them. My english is far from been good :) Issue URL: https://pharo.fogbugz.com/f/cases/20680 PR URL: https://github.com/pharo-project/pharo/pull/603 Diff URL: https://github.com/pharo-project/pharo/pull/603/files Thanks to jecisc * 20498-Replace-actual-Class-Installer-with-a-newer-modular-Version >> New try to integrate this PR. I had to reconstruct it because of migrating to Tonel. >> >> Still I didn't implemented the comments of Pavel, I will do when I got to the same state I was in the old PR. >> >> https://github.com/pharo-project/pharo/pull/334/files >> >> https://pharo.fogbugz.com/f/cases/20498/Replace-actual-Class-Installer-with… Issue URL: https://pharo.fogbugz.com/f/cases/20498 PR URL: https://github.com/pharo-project/pharo/pull/585 Diff URL: https://github.com/pharo-project/pharo/pull/585/files Thanks to tesonep * 20865-update-iceberg-to-065 >> using iceberg 0.6.5 >> >> fix case #20865 Issue URL: https://pharo.fogbugz.com/f/cases/20865 PR URL: https://github.com/pharo-project/pharo/pull/599 Diff URL: https://github.com/pharo-project/pharo/pull/599/files Thanks to estebanlm * 20866-revert-retryTimes-parameter-on-CI >> https://pharo.fogbugz.com/f/cases/20866/revert-retryTimes-parameter-on-CI Issue URL: https://pharo.fogbugz.com/f/cases/20866 PR URL: https://github.com/pharo-project/pharo/pull/600 Diff URL: https://github.com/pharo-project/pharo/pull/600/files Thanks to pavel-krivanek * 20773 - Unused temps in BlockClosure value, value:, value:value:, ... >> Remove unused temps from >> >> BlockClosure>>#value:value:value:value: >> BlockClosure>>#value:value:value: >> BlockClosure>>#value >> BlockClosure>>#value: >> BlockClosure>>#value:value: Issue URL: https://pharo.fogbugz.com/f/cases/20773 PR URL: https://github.com/pharo-project/pharo/pull/558 Diff URL: https://github.com/pharo-project/pharo/pull/558/files Thanks to astares * 20860-Cursor-webLink-is-initialized-wrongly-and-transparent >> https://pharo.manuscript.com/f/cases/20860 >> >> set weblink cursor shape Issue URL: https://pharo.fogbugz.com/f/cases/20860 PR URL: https://github.com/pharo-project/pharo/pull/598 Diff URL: https://github.com/pharo-project/pharo/pull/598/files Thanks to pavel-krivanek * 20857-Confirm-dialog-return-nil-when-closed-by-cmd-w >> https://pharo.manuscript.com/f/cases/20857 >> >> fix by Henrik Nergaard Issue URL: https://pharo.fogbugz.com/f/cases/20857 PR URL: https://github.com/pharo-project/pharo/pull/596 Diff URL: https://github.com/pharo-project/pharo/pull/596/files Thanks to pavel-krivanek

Jan. 20, 2018

[Pharo 7.0-dev] Build #438: 20953-Gitlab Private Project Support (via Iceberg)

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

There is a new Pharo build available! The status of the build #438 was: FAILURE. The Pull Request #667 was integrated: "20953-Gitlab Private Project Support (via Iceberg)" Pull request url: https://github.com/pharo-project/pharo/pull/667 Issue Url: https://pharo.fogbugz.com/f/cases/20953 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 20, 2018

Re: [Pharo-dev] Random corrupted data when copying from very large byte array

by Alistair Grant

Hi Eliot, On 19 January 2018 at 23:04, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Alistair, Hi ClÃ©ment, > > On Fri, Jan 19, 2018 at 12:53 PM, Alistair Grant <akgrant0710(a)gmail.com> > wrote: >> >> Hi ClÃ©ment, >> >> On 19 January 2018 at 17:21, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> > Hi ClÃ©ment, >> > >> > On 19 January 2018 at 17:04, ClÃ©ment Bera <bera.clement(a)gmail.com> >> > wrote: >> >> Does not seem to be related to prim 105. >> >> > > > I suspect that the problem is the same compactor bug I've been trying to > reproduce all week, and have just fixed. Could you try and reproduce with a > VM built from the latest commit? Happy to, but I'm out all day today, so it will be tomorrow or Monday. Cheers, Alistair (on the run...) > Some details: > The SpurPlanningCompactor works by using the fact that all Spur objects have > room for a forwarding pointer. The compactor make three passes: > > - the first pass through memory works out where objects will go, replacig > their first fields with where they will go, and saving their first fields in > a buffer (savedFirstFieldsSpace). > - the second pass scans all pointer objects, replacing their fields with > where the objects referenced will go (following the forwarding pointers), > and also relocates any pointer fields in savedFirstFieldsSpace > - the final pass slides objects down, restoring their relocated first fields > > The buffer used for savedFirstFieldsSpace determines how many passes are > used. The system will either use eden (which is empty when compaction > occurs) or a large free chunk or allocate a new segment, depending on > whatever yields the largest space. So in the right circumstances eden will > be used and more than one pass required. > > The bug was that when multiple passes are used the compactor forgot to > unmark the corpse left behind when the object was moved. Instead of the > corpse being changed into free space it was retained, but its first field > would be that of the forwarding pointer to its new location, not the actual > first field. So on 32-bits a ByteArray that should have been collected > would have its first 4 bytes appear to be invalid, and on 64-bits its first > 8 bytes. Because the heap on 64-bits can grow larger it could be that the > bug shows itself much less frequently than on 32-bits. When compaction can > be completed in a single pass all corpses are correctly collected, so most > of the time the bug is hidden. > > This is the commit: > commit 0fe1e1ea108e53501a0e728736048062c83a66ce > Author: Eliot Miranda <eliot.miranda(a)gmail.com> > Date: Fri Jan 19 13:17:57 2018 -0800 > > CogVM source as per VMMaker.oscog-eem.2320 > > Spur: > Fix a bad bug in SpurPlnningCompactor. > unmarkObjectsFromFirstFreeObject, > used when the compactor requires more than one pass due to insufficient > savedFirstFieldsSpace, expects the corpse of a moved object to be > unmarked, > but copyAndUnmarkObject:to:bytes:firstField: only unmarked the target. > Unmarking the corpse before the copy unmarks both. This fixes a crash > with > ReleaseBuilder class>>saveAsNewRelease when non-use of cacheDuring: > creates > lots of files, enough to push the system into the multi-pass regime. > >> >> >> HTH, >> Alistair >> >> >> >> > Cheers, >> > Alistair >> > >> > >> > >> >> On Thu, Jan 18, 2018 at 7:12 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> >> >> wrote: >> >>> >> >>> I would suspect a bug in primitive 105 on byte objects (it was changed >> >>> recently in the VM), called by copyFrom: 1 to: readCount. The bug >> >>> would >> >>> likely by due to specific alignment in readCount or something like >> >>> that. >> >>> (Assuming you're in 32 bits since the 4 bytes are corrupted). >> >>> >> >>> When I get better I can have a look (I am currently quite sick). >> >>> >> >>> On Thu, Jan 18, 2018 at 4:51 PM, Thierry Goubier >> >>> <thierry.goubier(a)gmail.com> wrote: >> >>>> >> >>>> Hi Cyril, >> >>>> >> >>>> try with the last vms available at: >> >>>> >> >>>> https://bintray.com/opensmalltalk/vm/cog/ >> >>>> >> >>>> For example, the last Ubuntu 64bits vm is at: >> >>>> >> >>>> https://bintray.com/opensmalltalk/vm/cog/201801170946#files >> >>>> >> >>>> Regards, >> >>>> >> >>>> Thierry >> >>>> >> >>>> 2018-01-18 16:42 GMT+01:00 Cyrille Delaunay <cy.delaunay(a)gmail.com>: >> >>>>> >> >>>>> Hi everyone, >> >>>>> >> >>>>> I just added a new bug entry for an issue we are experimenting since >> >>>>> some times: >> >>>>> >> >>>>> >> >>>>> >> >>>>> https://pharo.fogbugz.com/f/cases/20982/Random-corrupted-data-when-copying-… >> >>>>> >> >>>>> Here is the description: >> >>>>> >> >>>>> >> >>>>> History: >> >>>>> >> >>>>> This issue has been spotted after experimenting strange behavior >> >>>>> with >> >>>>> seaside upload. >> >>>>> After uploading a big file from a web browser, the modeled file >> >>>>> generated within pharo image begins with 4 unexpected bytes. >> >>>>> This issue occurs randomly: sometimes the first 4 bytes are right. >> >>>>> Sometimes the first 4 bytes are wrong. >> >>>>> This issue only occurs with Pharo 6. >> >>>>> This issue occurs for all platforms (Mac, Ubuntu, Windows) >> >>>>> >> >>>>> Steps to reproduce: >> >>>>> >> >>>>> I have been able to set up a small scenario that highlight the >> >>>>> issue. >> >>>>> >> >>>>> Download Pharo 6.1 on my Mac (Sierra 10.12.6): >> >>>>> https://pharo.org/web/download >> >>>>> Then, iterate over this process till spotting the issue: >> >>>>> >> >>>>> => start the pharo image >> >>>>> => execute this piece of code in a playground >> >>>>> >> >>>>> 1: >> >>>>> 2: >> >>>>> 3: >> >>>>> 4: >> >>>>> 5: >> >>>>> 6: >> >>>>> >> >>>>> ZnServer startDefaultOn: 1701. >> >>>>> ZnServer default maximumEntitySize: 80* 1024 * 1024. >> >>>>> '/Users/cdelaunay/myzip.zip' asFileReference writeStreamDo: [ :out | >> >>>>> out binary; nextPutAll: #[80 75 3 4 10 0 0 0 0 0 125 83 67 73 0 0 0 >> >>>>> 0 0 >> >>>>> 0]. >> >>>>> 18202065 timesRepeat: [ out nextPut: 0 ] >> >>>>> ]. >> >>>>> >> >>>>> => Open a web browser page on: http://localhost:1701/form-test-3 >> >>>>> => Upload the file zip file previously generated ('myzip.zip'). >> >>>>> => If the web page displays: "contents=000000000a00..." (or anything >> >>>>> unexpected), THIS IS THE ISSUE ! >> >>>>> => If the web page displays: "contents=504b03040a00..", the upload >> >>>>> worked fine. You can close the image (without saving) >> >>>>> >> >>>>> >> >>>>> >> >>>>> Debugging: >> >>>>> >> >>>>> >> >>>>> >> >>>>> Bob Arning has been able to reproduce the issue with my scenario. >> >>>>> He dived into the code involved during this process, till reaching >> >>>>> some >> >>>>> "basic" methods where he saw the issue occuring. >> >>>>> >> >>>>> Here are the conclusion till there: >> >>>>> => A corruption occurs while reading an input stream with method >> >>>>> ZnUtils >> >>>>> class>>readUpToEnd:limit: >> >>>>> The first 4 bytes may be altered randomely. >> >>>>> => The first 4 bytes are initially correctly written to an >> >>>>> outputStream. >> >>>>> But, the first 4 bytes of this outputStream gets altered >> >>>>> (corrupted), >> >>>>> sometimes when the inner byte array grows OR when performing the >> >>>>> final >> >>>>> "outputStream contents" >> >>>>> => Here is a piece of code that reproduce the issue (still >> >>>>> randomely. >> >>>>> stopping an restarting the image may change the behavior) >> >>>>> >> >>>>> 1: >> >>>>> 2: >> >>>>> 3: >> >>>>> 4: >> >>>>> 5: >> >>>>> 6: >> >>>>> 7: >> >>>>> 8: >> >>>>> 9: >> >>>>> 10: >> >>>>> 11: >> >>>>> 12: >> >>>>> 13: >> >>>>> 14: >> >>>>> 15: >> >>>>> 16: >> >>>>> 17: >> >>>>> 18: >> >>>>> 19: >> >>>>> 20: >> >>>>> >> >>>>> test4"self test4" | species bufferSize buffer totalRead >> >>>>> outputStream >> >>>>> answer inputStream ba byte1 | ba := ByteArray new: >> >>>>> 18202085. >> >>>>> ba atAllPut: 99. 1 to: 20 do: [ :i | ba at: i put: (#[80 75 >> >>>>> 3 4 10 7 >> >>>>> 7 7 7 7 125 83 67 73 7 7 7 7 7 7] at: i) ]. inputStream := ba >> >>>>> readStream. >> >>>>> bufferSize := 16384. species := ByteArray. >> >>>>> buffer := species new: bufferSize. >> >>>>> totalRead := 0. >> >>>>> outputStream := nil. >> >>>>> [ inputStream atEnd ] whileFalse: [ | readCount | >> >>>>> readCount := inputStream readInto: buffer startingAt: 1 >> >>>>> count: >> >>>>> bufferSize. >> >>>>> totalRead = 0 ifTrue: [ >> >>>>> byte1 := buffer first. >> >>>>> ]. >> >>>>> totalRead := totalRead + readCount. >> >>>>> >> >>>>> outputStream ifNil: [ >> >>>>> inputStream atEnd >> >>>>> ifTrue: [ ^ buffer copyFrom: 1 to: readCount ] >> >>>>> ifFalse: [ outputStream := (species new: bufferSize) >> >>>>> writeStream ] ]. >> >>>>> outputStream next: readCount putAll: buffer startingAt: 1. >> >>>>> byte1 = outputStream contents first ifFalse: [ self halt ]. >> >>>>> ]. >> >>>>> answer := outputStream ifNil: [ species new ] ifNotNil: [ >> >>>>> outputStream contents ]. >> >>>>> byte1 = answer first ifFalse: [ self halt ]. ^answer >> >>>>> >> >>>>> >> >>>>> >> >>>>> suspicions >> >>>>> >> >>>>> This issue appeared with Pharo 6. >> >>>>> >> >>>>> Some people suggested that it could be a vm issue, and to try my >> >>>>> little >> >>>>> scenario with the last available vm. >> >>>>> >> >>>>> I am not sure where to find the last available vm. >> >>>>> >> >>>>> I did the test using these elements: >> >>>>> >> >>>>> https://files.pharo.org/image/60/latest.zip >> >>>>> >> >>>>> https://files.pharo.org/get-files/70/pharo-mac-latest.zip/ >> >>>>> >> >>>>> >> >>>>> >> >>>>> The issue is still present >> >>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>>> -- >> >>>>> Cyrille Delaunay >> >>>> >> >>>> >> >>> >> >>> >> >>> >> >>> -- >> >>> ClÃ©ment BÃ©ra >> >>> Pharo consortium engineer >> >>> https://clementbera.wordpress.com/ >> >>> BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq >> >> >> >> >> >> >> >> >> >> -- >> >> ClÃ©ment BÃ©ra >> >> Pharo consortium engineer >> >> https://clementbera.wordpress.com/ >> >> BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq >> > > > > -- > _,,,^..^,,,_ > best, Eliot

Jan. 20, 2018