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

Re: [Pharo-dev] [Mm10s] 2019-11-25

by ducasse

Thanks Esteban this is great The underlying message is not only that users understand what we are doing but also that they can raise questions and notify us in case we have missed some key PR or issues. ### Last week: - [Pharo] making sure enlumineur the new formatter is loading perfectly - [Mooc] Analysing videos - [Pharo] Starting to work on fluid class parser ### This week (starting 2019-11-25): - [PBE 8] - [Mooc] Analysing videos - [Pharo] Adding enlumineur ### Pipeline - [Pharo] Fix broken executable comments - [Pharo] Help release - [PBE 8] - [Mooc]

Nov. 25, 2019

[Pharo 8.0] Build #1008: Completion: Fix emebdded Browser

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

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

Nov. 25, 2019

[Mm10s] 2019-11-25

by Esteban Lorenzano

Hello, still working on enhance our communication, this week the core team will start informing our weekly todo. This is something we were using internally with success but now we will make it public, and it will include three points : last week work, this week work and what we have in our pipeline. (NOTE: This mail does not replaces the monthly report but complements it). So, I will start :) ### Last week: - [Spec2] Add search capability to lists/tables/trees. - [Spec2+Gtk3] Ensuring the parts that needs to run on main thread are correctly deferred there. - [VM] Adding ways to control whether we run the VM on main thread or worker thread. - [VM] Merging AIO interrupt branch, Worker thread branch and headless branch. - [VM] Preparing a linux machine to debug the vm and gtk3 spec2 backend there. ### This week (starting 2019-11-25): - [Spec2] Add search capability to lists/tables/trees. - [Spec2+Gtk3] Ensuring the parts that needs to run on main thread are correctly deferred there. - [VM] Verify some problems where AIO should interrupt and it does not doit, causing the vm to not respond to events. ### Pipeline - [Release] Prepare checklist to release of Pharo 8. - [Spec2] Search and filters on list/tables/trees. - [Spec2] Fix radio buttons. - [VM] debug AIO and worker thread VMs on linux and windows. - [NewTools] Create miller list paginator to make inspector panes more visible. - [NewTools] Enhance Inspector (several tasks here).

Nov. 25, 2019

VM crash investigations

by Alistair Grant

Hi All, At the moment I'm spending pretty much all of my working time tracking down VM crashes. It sounds like there may be others working on the same issue (Guille?, Pablo?), if so it would be good to be able to exchange notes and hopefully reach a resolution a little earlier. So my status... I'm currently focusing on two corruptions that I've seen: 1. Frame Pointers aren't being updated when the receiver or rcvr/clsr they point to is moved during scavenging / compaction. 2. The current frame pointer (framePointer) contains an address that is in a free stack page. I'm doing all the investigation using a Pharo minimal image, so there's no FreeType, and from what I've seen FFI isn't being used. The script I'm using to reproduce the crash is at: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/444#issuecomment-5… (the good part about this is that even the memory addresses are consistent across runs, so it is highly reproducible). For the Frame Pointers not being updated, what I'm seeing is that after a scavenge has finished copying all the referenced objects, but before the survivor spaces are exchanged, the call stack looks like: (gdb) call printCallStack() 0x7ffffffe3f70 I SessionManager>launchSnapshot:andQuit: 0x1508860: a(n) SessionManager 0x7ffffffe3fe0 I [] in SessionManager>snapshot:andQuit: 0x1508860: a(n) SessionManager 0x7ffffffe4020 I [] in INVALID RECEIVER>newProcess 0x118a728 0x118a728 is a forwarded object to 0x488fca0 of slot size 7 hdr8 ..... Once the survivor spaces have been exchanged: (gdb) call printCallStack() 0x7ffffffe3f70 I SessionManager>launchSnapshot:andQuit: 0x1508860: a(n) SessionManager 0x7ffffffe3fe0 I [] in SessionManager>snapshot:andQuit: 0x1508860: a(n) SessionManager 0x7ffffffe4020 I [] in INVALID RECEIVER>newProcess 0x118a728 is in new space For the framePointer containing an address in a free stack page: adding a check during the scavenge shows that the framePointer is in a free page. I'm assuming it is never valid for the framePointer to be in a free stack page, and that the receiver and rcvr/clsr should never be in new space. If my assumptions are wrong please let me know. If you'd like any more information, please let me know. Thanks, Alistair

Nov. 25, 2019

Re: [Pharo-dev] DrTest - strange UI effect and some feedback

by Stephan Eggermont

Julien Delplanque <julien.delplanque(a)inria.fr> wrote: > For the "Select none" I am not sure that we want to support that action > because it feels a bit odd. Why would one want to have nothing selected? > But if one can justify why this is needed, we can add it of course. > > "Select inversion" could be added but again I think this is a bit odd > feature. If you support select all you need at least one of invert selection and select none. All actions are supposed to be reversible as far as possible. Stephan

Nov. 25, 2019

[ANN] Next Pharo Sprint: Nov 29

by Marcus Denker

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

Nov. 25, 2019

[Pharo 8.0] Build #1007: 5213-Little-pass-on-DrTests

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

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

Nov. 24, 2019

Re: [Pharo-dev] Bugs still open on traits

by Tudor Girba

No worries. We are here to complement the effort :). Cheers, Doru > On Nov 23, 2019, at 8:07 PM, ducasse <stepharo(a)netcourrier.com> wrote: > > Ok I tagged them for Pharo80 and now they are in our radar. > Thanks andrei. > We are doing too many things. > >> On 23 Nov 2019, at 19:17, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: >> >> Hey! >> >> They are: >> https://github.com/pharo-project/pharo/issues/3158 >> https://github.com/pharo-project/pharo/issues/4565 >> >> Cheers, >> Andrei >> >> On Sat, Nov 23, 2019 at 12:39 PM ducasse <stepharo(a)netcourrier.com> wrote: >> Hi andrei >> >> can you tell us the bug that you mentioned to me on traits and that skipped our radar? >> >> Stef >> >> >> > -- feenk.com "To utilize feedback, you first have to acquire it."

Nov. 24, 2019

[Pharo 8.0] Build #1006: Reflectivity: ASTCacheReset not needed

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

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

Nov. 23, 2019

Re: [Pharo-dev] Bugs still open on traits

by ducasse

Ok I tagged them for Pharo80 and now they are in our radar. Thanks andrei. We are doing too many things. > On 23 Nov 2019, at 19:17, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Hey! > > They are: > https://github.com/pharo-project/pharo/issues/3158 <https://github.com/pharo-project/pharo/issues/3158> > https://github.com/pharo-project/pharo/issues/4565 <https://github.com/pharo-project/pharo/issues/4565> > > Cheers, > Andrei > > On Sat, Nov 23, 2019 at 12:39 PM ducasse <stepharo(a)netcourrier.com <mailto:stepharo@netcourrier.com>> wrote: > Hi andrei > > can you tell us the bug that you mentioned to me on traits and that skipped our radar? > > Stef > > >

Nov. 23, 2019