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

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

by Andrei Chis

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 > > > >

Nov. 23, 2019

[Pharo 7.0] Build #175: Backport-5072-MCClassTraitDefinition-should-take-category-into-account-for-equality

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

There is a new Pharo build available! The status of the build #175 was: FAILURE. The Pull Request #5075 was integrated: "Backport-5072-MCClassTraitDefinition-should-take-category-into-account-for-equality" Pull request url: https://github.com/pharo-project/pharo/pull/5075 Issue Url: https://pharo.fogbugz.com/f/cases/Backport Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 23, 2019

Bugs still open on traits

by ducasse

Hi andrei can you tell us the bug that you mentioned to me on traits and that skipped our radar? Stef

Nov. 23, 2019

[Pharo 8.0] Build #1005: Improve-AssertEquals-Rule

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

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

Nov. 22, 2019

[Pharo 8.0] Build #1004: UseNecEntrySubclasses

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

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

Nov. 22, 2019

[Pharo 8.0] Build #1003: Rollback to setStrokePaint for issue: Remove use of StrokePaintCache #5199

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

There is a new Pharo build available! The status of the build #1003 was: SUCCESS. The Pull Request #5201 was integrated: "Rollback to setStrokePaint for issue: Remove use of StrokePaintCache #5199" Pull request url: https://github.com/pharo-project/pharo/pull/5201 Issue Url: https://github.com/pharo-project/pharo/issues/Pharo8.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 22, 2019

[Pharo 8.0] Build #1002: #flatCollect: implement using #streamContents:

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

There is a new Pharo build available! The status of the build #1002 was: SUCCESS. The Pull Request #5204 was integrated: "#flatCollect: implement using #streamContents:" Pull request url: https://github.com/pharo-project/pharo/pull/5204 Issue Url: https://github.com/pharo-project/pharo/issues/flatcollectstreamcontents Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 22, 2019

[Pharo 8.0] Build #1001: Cleanup #allClassVarNames

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

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

Nov. 22, 2019

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

by ducasse

Julien I like inversion because sometimes this is faster to click on the things you do not want. We will have to check the cmd+A because on some lists it is not working. >> 2. The old TestRunner had (after filtering the package) an additional useful context menu >> with "Select all" and "Select none", "Select inversion", .... which allowed >> easier focusing on the test classes I want to check. >> Would be nice if a similar one could be added. > > For "Select all" it is possible to do it via Cmd+A or Ctrl+A, as it is the standard for list selection in UI frameworks. > > 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. > > Now you have to know that DrTests is a side project for me and for right now I can not allocate that much time on it. > So I will do my best to fix urgent issues ASAP. I already have a great list of issues since the integration (which is normal). :-) Thanks for your time julien. > > However, until next friday, I am in a rush for another deadline.

Nov. 22, 2019

[Pharo 8.0] Build #1000: Replace-assert-equals-from-non-test-methods

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

There is a new Pharo build available! The status of the build #1000 was: SUCCESS. The Pull Request #5198 was integrated: "Replace-assert-equals-from-non-test-methods" Pull request url: https://github.com/pharo-project/pharo/pull/5198 Issue Url: https://github.com/pharo-project/pharo/issues/Replace Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 22, 2019

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

by Julien Delplanque

Hello Torsten, First of all, thanks for your feedback. Le 22/11/19 Ã 09:15, Torsten Bergmann a Ã©critÂ : > Hi, > > DrTest is integrated into Pharo 8 now - but there seems to be a strange bug > in overlapping widgets when one uses the grouping selection box. > > See attached screenshot. > > I opened an issue for that: https://github.com/pharo-project/pharo/issues/5205 > for Pharo. Dont know if that is known bug or even already fixed in the original repo > of DrTest. Would be good if the authors (Julien or Dayne) could check. I am not sure what causes this bug, I will need to check with Spec2 developers because I think as Spec2 users we do not have control on such behaviour of the droplist. > > Additional feedback: > > It's really a nice tool - but I see myself still switching back to old TestRunner again. > Two reasons: > > 1. Compared to the regular TestRunner where one is able to see the failing tests > directly in DrTest one always has to have additional clicks in the > grouping tree on the left before getting the final results. > > So the default grouping of the results as a tree could be disturbing because it > requires more clicking around. > > Would be a nice addition if there would be an additional "no grouping" mode as well > so the results are just shown in a list like in reglar TestRunner. I agree with you, an additional iteration needs to be done on the grouping feature. We will take your feedback into account. > > 2. The old TestRunner had (after filtering the package) an additional useful context menu > with "Select all" and "Select none", "Select inversion", .... which allowed > easier focusing on the test classes I want to check. > Would be nice if a similar one could be added. For "Select all" it is possible to do it via Cmd+A or Ctrl+A, as it is the standard for list selection in UI frameworks. 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. Now you have to know that DrTests is a side project for me and for right now I can not allocate that much time on it. So I will do my best to fix urgent issues ASAP. I already have a great list of issues since the integration (which is normal). :-) However, until next friday, I am in a rush for another deadline. Julien

Nov. 22, 2019

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

by ducasse

Yes we are not really happy (this is why we will move it to preview for the release since it will probably happen sooner that planned). I also detected that the executable comment execution looks not working. S > On 22 Nov 2019, at 09:15, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > DrTest is integrated into Pharo 8 now - but there seems to be a strange bug > in overlapping widgets when one uses the grouping selection box. > > See attached screenshot. > > I opened an issue for that: https://github.com/pharo-project/pharo/issues/5205 > for Pharo. Dont know if that is known bug or even already fixed in the original repo > of DrTest. Would be good if the authors (Julien or Dayne) could check. > > Additional feedback: > > It's really a nice tool - but I see myself still switching back to old TestRunner again. Me too. :) We all share your analysis. > Two reasons: > > 1. Compared to the regular TestRunner where one is able to see the failing tests > directly in DrTest one always has to have additional clicks in the > grouping tree on the left before getting the final results. > > So the default grouping of the results as a tree could be disturbing because it > requires more clicking around. > > Would be a nice addition if there would be an additional "no grouping" mode as well > so the results are just shown in a list like in reglar TestRunner. > > 2. The old TestRunner had (after filtering the package) an additional useful context menu > with "Select all" and "Select none", "Select inversion", .... which allowed > easier focusing on the test classes I want to check. > Would be nice if a similar one could be added. Yes we agreed on that. Tx torsten > > Thanks > T. > > <drtest.png>

Nov. 22, 2019

DrTest - strange UI effect and some feedback

by Torsten Bergmann

Hi, DrTest is integrated into Pharo 8 now - but there seems to be a strange bug in overlapping widgets when one uses the grouping selection box. See attached screenshot. I opened an issue for that: https://github.com/pharo-project/pharo/issues/5205 for Pharo. Dont know if that is known bug or even already fixed in the original repo of DrTest. Would be good if the authors (Julien or Dayne) could check. Additional feedback: It's really a nice tool - but I see myself still switching back to old TestRunner again. Two reasons: 1. Compared to the regular TestRunner where one is able to see the failing tests directly in DrTest one always has to have additional clicks in the grouping tree on the left before getting the final results. So the default grouping of the results as a tree could be disturbing because it requires more clicking around. Would be a nice addition if there would be an additional "no grouping" mode as well so the results are just shown in a list like in reglar TestRunner. 2. The old TestRunner had (after filtering the package) an additional useful context menu with "Select all" and "Select none", "Select inversion", .... which allowed easier focusing on the test classes I want to check. Would be nice if a similar one could be added. Thanks T.

Nov. 22, 2019

About dashed lines in Athens

by milton mamani

Hi to all I was playing with Athens and I found and error that you can reproduce with the next script in Pharo8x64 macOs ```Smalltalk AthensSurfaceExamples openViewOn: [ :can | can pathTransform restoreAfter: [ can pathTransform translateX: 30 Y: 30. can pathTransform rotateByDegrees: 35. can setPaint: Color red. can setStrokePaint: Color black. can setShape: (-20@ -20 corner: 20@ 20). can draw. ]. ]. AthensSurfaceExamples openViewOn: [ :can | can pathTransform restoreAfter: [ can pathTransform translateX: 30 Y: 30. can pathTransform rotateByDegrees: 35. can setPaint: Color red. (can setStrokePaint: Color black) width: 6; dashes: #(4) offset: 0. can setShape: (-20@ -20 corner: 20@ 20). can draw. ]. ]. AthensSurfaceExamples openViewOn: [ :can | can pathTransform restoreAfter: [ can pathTransform translateX: 30 Y: 30. can pathTransform rotateByDegrees: 35. can setPaint: Color red. can setStrokePaint: Color black. can setShape: (-20@ -20 corner: 20@ 20). can draw. ]. ]. ``` The previous examples opens 3 windows The first the line is normal The second the line is dashed The third one should be normal, but it is dashed Why because there is a cache for the color black in the methods `setStrokePaint:` I think that we need to fix this, Cheers, Milton

Nov. 21, 2019

[Pharo 8.0] Build #999: ProtoObject: #mustBeBooleanDeOptimize

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

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

Nov. 21, 2019

Re: [Pharo-dev] GildaVM - a Non-Blocking I/O Architecture for the Cog VM

by pmissech

Hi Ben It was accepted at IWST 2019, so there you go =] https://esug.github.io/2019-Conference/cfpIWST2019.html or direct download linkhttp://esug.github.io/2019-Conference/articles/2019-08-26-IWST19.zip Pierre On 21/11/2019 06:06, Ben Coman wrote: > I saw an interesting tweet on "GildaVM: a Non-Blocking I/O > Architecture for the Cog VM" [1] > which shows the VM running multiple interpreter-threads. > Where is the paper shown on page 23 available? > > Side thought, ifÂ "usually, 1% of objects survive their first > scavenge" [2] > as a "breadth-first traversal of objects from the remembered table (a > table holding all old objects referencing new objects) and the stack" > > that implies only a small percentage object mutations were in old > space (??) > > which makes wonder if each interpreter-thread had its "own" new-space, > then scavenging each new-space could run independently in > parallel-native-threads? > Thus a global lock may only(?) be needed to mutate a shared old-space > and minimizeÂ Â . > > This ignores the execution-engine needing to update method-lookup tables. > Could native-threads start with their own copy of a warmed up JIT and > then work independently? > > cheers -ben > > > [1] > https://www.slideshare.net/esug/gildavm-a-nonblocking-io-architecture-for-t… > > [2] > https://clementbera.wordpress.com/2017/03/12/tuning-the-pharo-garbage-colle… > >

Nov. 21, 2019

GildaVM - a Non-Blocking I/O Architecture for the Cog VM

by Ben Coman

I saw an interesting tweet on "GildaVM: a Non-Blocking I/O Architecture for the Cog VM" [1] which shows the VM running multiple interpreter-threads. Where is the paper shown on page 23 available? Side thought, if "usually, 1% of objects survive their first scavenge" [2] as a "breadth-first traversal of objects from the remembered table (a table holding all old objects referencing new objects) and the stack" that implies only a small percentage object mutations were in old space (??) which makes wonder if each interpreter-thread had its "own" new-space, then scavenging each new-space could run independently in parallel-native-threads? Thus a global lock may only(?) be needed to mutate a shared old-space and minimize . This ignores the execution-engine needing to update method-lookup tables. Could native-threads start with their own copy of a warmed up JIT and then work independently? cheers -ben [1] https://www.slideshare.net/esug/gildavm-a-nonblocking-io-architecture-for-t… [2] https://clementbera.wordpress.com/2017/03/12/tuning-the-pharo-garbage-colle…

Nov. 21, 2019

[Pharo 8.0] Build #992: 5085-Move-clap-into-BaselineOfBaseLibraries-2

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

There is a new Pharo build available! The status of the build #992 was: SUCCESS. The Pull Request #5175 was integrated: "5085-Move-clap-into-BaselineOfBaseLibraries-2" Pull request url: https://github.com/pharo-project/pharo/pull/5175 Issue Url: https://github.com/pharo-project/pharo/issues/5085 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 20, 2019

[Pharo 7.0] Build #174: Backport - Fix nextVersion for cases where an entry with basename only exists inâ¦

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

There is a new Pharo build available! The status of the build #174 was: SUCCESS. The Pull Request #5122 was integrated: "Backport - Fix nextVersion for cases where an entry with basename only exists inâ¦" Pull request url: https://github.com/pharo-project/pharo/pull/5122 Issue Url: https://pharo.fogbugz.com/f/cases/fix Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 20, 2019

[Pharo 8.0] Build #991: spellCheckAstCore

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

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

Nov. 20, 2019

[Pharo 8.0] Build #990: Replace-assert-equals-from-Morphic

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

There is a new Pharo build available! The status of the build #990 was: SUCCESS. The Pull Request #5171 was integrated: "Replace-assert-equals-from-Morphic" Pull request url: https://github.com/pharo-project/pharo/pull/5171 Issue Url: https://github.com/pharo-project/pharo/issues/Replace Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 19, 2019

[Pharo 8.0] Build #989: Replace-assert-equals-from-packages-starting-with-J-and-K

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

There is a new Pharo build available! The status of the build #989 was: SUCCESS. The Pull Request #5170 was integrated: "Replace-assert-equals-from-packages-starting-with-J-and-K" Pull request url: https://github.com/pharo-project/pharo/pull/5170 Issue Url: https://github.com/pharo-project/pharo/issues/Replace Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 19, 2019

Pharo Techtalk Nov 21

by Marcus Denker

Hi, Next techtalk will be *this* week (Nov 21): Topic: Discussion around Contributing to Pharo8 The idea is to discuss on Discord and may do some examples liveâ¦ Calendar entry: https://association.pharo.org/event-3419546 (sorry for the late announceâ¦ )

Nov. 19, 2019

[Pharo 8.0] Build #988: Replace-assert-equals-from-packages-starting-with-H

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

There is a new Pharo build available! The status of the build #988 was: FAILURE. The Pull Request #5169 was integrated: "Replace-assert-equals-from-packages-starting-with-H" Pull request url: https://github.com/pharo-project/pharo/pull/5169 Issue Url: https://github.com/pharo-project/pharo/issues/Replace Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 19, 2019

Re: [Pharo-dev] AbstractEnvironmentTestCase

by Sven Van Caekenberghe

> On 19 Nov 2019, at 12:27, ducasse <stepharo(a)netcourrier.com> wrote: > > > >> On 19 Nov 2019, at 11:57, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Hi, >> >> AbstractEnvironmentTestCase exists only in Pharo 8, tracking this with STON (from changes in Pharo 8) gives me tests that can no longer be loaded in Pharo 7 (or versions before that). >> >> At least AbstractEnvironmentTestCase should be back ported to Pharo 7. >> >> Apart from that, I don't think this is a good change (since it breaks backwards compatibility >> too much). > > I do not agree. Well, external code cannot write tests that confirms to the requirements of both versions. >> Why do all Smalltalk>>#at: references have to be removed ? The way I see it, Smalltalk>>#at: could be rewritten to dynamically use a different environment, if that is set up earlier, using a DynamicVariable. Similarly, #asClass could be implemented to follow the same path. > > Because if one day we want to have modules and environment better to have a system that does not point to > global variables. > We should not refer to global variables. But eventually, the reference has to be resolved and it has a name. I am familiar with packages in common lisp, is it like that ? Is there a document that describes these issues more clearly ? The plan going forward ? > Stef > > >> >> Or am I wrong ? >> >> Sven

Nov. 19, 2019

Re: [Pharo-dev] AbstractEnvironmentTestCase

by ducasse

> On 19 Nov 2019, at 11:57, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > AbstractEnvironmentTestCase exists only in Pharo 8, tracking this with STON (from changes in Pharo 8) gives me tests that can no longer be loaded in Pharo 7 (or versions before that). > > At least AbstractEnvironmentTestCase should be back ported to Pharo 7. > > Apart from that, I don't think this is a good change (since it breaks backwards compatibility > too much). I do not agree. > Why do all Smalltalk>>#at: references have to be removed ? The way I see it, Smalltalk>>#at: could be rewritten to dynamically use a different environment, if that is set up earlier, using a DynamicVariable. Similarly, #asClass could be implemented to follow the same path. Because if one day we want to have modules and environment better to have a system that does not point to global variables. We should not refer to global variables. Stef > > Or am I wrong ? > > Sven > > >

Nov. 19, 2019

AbstractEnvironmentTestCase

by Sven Van Caekenberghe

Hi, AbstractEnvironmentTestCase exists only in Pharo 8, tracking this with STON (from changes in Pharo 8) gives me tests that can no longer be loaded in Pharo 7 (or versions before that). At least AbstractEnvironmentTestCase should be back ported to Pharo 7. Apart from that, I don't think this is a good change (since it breaks backwards compatibility too much). Why do all Smalltalk>>#at: references have to be removed ? The way I see it, Smalltalk>>#at: could be rewritten to dynamically use a different environment, if that is set up earlier, using a DynamicVariable. Similarly, #asClass could be implemented to follow the same path. Or am I wrong ? Sven

Nov. 19, 2019

[Pharo 8.0] Build #987: Replace-assert-equals-from-packages-starting-with-F

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

There is a new Pharo build available! The status of the build #987 was: SUCCESS. The Pull Request #5160 was integrated: "Replace-assert-equals-from-packages-starting-with-F" Pull request url: https://github.com/pharo-project/pharo/pull/5160 Issue Url: https://github.com/pharo-project/pharo/issues/Replace Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 19, 2019

[Pharo 8.0] Build #986: CompilerNilCompiler

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

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

Nov. 19, 2019

[Pharo 8.0] Build #985: Replace-assert-equals-from-Epicea

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

There is a new Pharo build available! The status of the build #985 was: SUCCESS. The Pull Request #5159 was integrated: "Replace-assert-equals-from-Epicea" Pull request url: https://github.com/pharo-project/pharo/pull/5159 Issue Url: https://github.com/pharo-project/pharo/issues/Replace Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 18, 2019

[Pharo 8.0] Build #984: HandMorph cleanups required: remove three ivars

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

There is a new Pharo build available! The status of the build #984 was: SUCCESS. The Pull Request #5153 was integrated: "HandMorph cleanups required: remove three ivars" Pull request url: https://github.com/pharo-project/pharo/pull/5153 Issue Url: https://github.com/pharo-project/pharo/issues/HandMorph Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 18, 2019

[Pharo 8.0] Build #983: 5140-Browse-senders-crash-on-characters

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

There is a new Pharo build available! The status of the build #983 was: SUCCESS. The Pull Request #5141 was integrated: "5140-Browse-senders-crash-on-characters" Pull request url: https://github.com/pharo-project/pharo/pull/5141 Issue Url: https://github.com/pharo-project/pharo/issues/5140 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 18, 2019

endless loop when loading 4671 from my repo http://github.com/Ducasse/Pharo

by ducasse

Hi I got an endless loop when checkouting the issue 4671 from my repo http://github.com/Ducasse/Pharo <http://github.com/Ducasse/Pharo>. Apparently there are some old obsolete reference to number parser around and it breaks rub. would be nice to have a way to stop such infinite loops. Stef

Nov. 17, 2019

[Pharo 8.0] Build #982: Update bootstrap to pharo7

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

There is a new Pharo build available! The status of the build #982 was: SUCCESS. The Pull Request #4558 was integrated: "Update bootstrap to pharo7" Pull request url: https://github.com/pharo-project/pharo/pull/4558 Issue Url: https://github.com/pharo-project/pharo/issues/updateBootstrapToPharo7 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 15, 2019

[Pharo 8.0] Build #981: Cleanup: #copiedMethodsFromSuperclass

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

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

Nov. 15, 2019

[Pharo 8.0] Build #980: #parseTree needs to use compiler

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

There is a new Pharo build available! The status of the build #980 was: SUCCESS. The Pull Request #5150 was integrated: "#parseTree needs to use compiler" Pull request url: https://github.com/pharo-project/pharo/pull/5150 Issue Url: https://github.com/pharo-project/pharo/issues/parseTreeNeedsToUseCompiler Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 15, 2019

[Pharo 8.0] Build #979: Remove-some-unused-Beacon-methods-from-ZnLogEvent

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

There is a new Pharo build available! The status of the build #979 was: FAILURE. The Pull Request #5145 was integrated: "Remove-some-unused-Beacon-methods-from-ZnLogEvent" Pull request url: https://github.com/pharo-project/pharo/pull/5145 Issue Url: https://github.com/pharo-project/pharo/issues/Remove Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 15, 2019

[Pharo 8.0] Build #978: Compiler: small cleanup #parse

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

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

Nov. 15, 2019

[Pharo 8.0] Build #977: CompiledCode: #subclassResponsability

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

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

Nov. 15, 2019

[Pharo 8.0] Build #976: Completion: Move #commonSuperclass:

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

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

Nov. 15, 2019