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

[Pharo 7.0-dev] Build #845: 21846-basicAddSelectorwithMethod-has-unused-temp

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

There is a new Pharo build available! The status of the build #845 was: FAILURE. The Pull Request #1311 was integrated: "21846-basicAddSelectorwithMethod-has-unused-temp" Pull request url: https://github.com/pharo-project/pharo/pull/1311 Issue Url: https://pharo.fogbugz.com/f/cases/21846 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 7, 2018

[Pharo 7.0-dev] Build #844: 21847-RBSmallLintContext-has-unused-ivars

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

There is a new Pharo build available! The status of the build #844 was: FAILURE. The Pull Request #1312 was integrated: "21847-RBSmallLintContext-has-unused-ivars" Pull request url: https://github.com/pharo-project/pharo/pull/1312 Issue Url: https://pharo.fogbugz.com/f/cases/21847 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 7, 2018

[Pharo 7.0-dev] Build #843: 21841-Full-screen-margin-should-be-0-

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

There is a new Pharo build available! The status of the build #843 was: SUCCESS. The Pull Request #1308 was integrated: "21841-Full-screen-margin-should-be-0-" Pull request url: https://github.com/pharo-project/pharo/pull/1308 Issue Url: https://pharo.fogbugz.com/f/cases/21841 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 7, 2018

[Pharo 7.0-dev] Build #842: 21839 Improve FileSystem-Tests-Disk and FileSystem-Tests-Memory

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

There is a new Pharo build available! The status of the build #842 was: FAILURE. The Pull Request #1306 was integrated: "21839 Improve FileSystem-Tests-Disk and FileSystem-Tests-Memory" Pull request url: https://github.com/pharo-project/pharo/pull/1306 Issue Url: https://pharo.fogbugz.com/f/cases/21839 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 7, 2018

[Pharo 7.0-dev] Build #841: 21838 Improve FileSystem-Path

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

There is a new Pharo build available! The status of the build #841 was: FAILURE. The Pull Request #1305 was integrated: "21838 Improve FileSystem-Path" Pull request url: https://github.com/pharo-project/pharo/pull/1305 Issue Url: https://pharo.fogbugz.com/f/cases/21838 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 7, 2018

<Programming> 2019: Call for Papers & Call for Workshop Proposals

by Fabio Niephaus

<Programming> 2019 : The Art, Science, and Engineering of Programming April 1-4, 2019, Genova, Italy http://2019.programming-conference.org The International Conference on the Art, Science, and Engineering of Programming is a new conference focused on programming topics including the experience of programming. We have named it <Programming> for short. <Programming> seeks for papers that advance knowledge of programming on any relevant topic, including programming practice and experience. Paper submissions and publications are handled by the the Art, Science, and Engineering of Programming journal (http://programming-journal.org) Accepted papers must be presented at the conference. ******************************************************** CALL FOR PAPERS ******************************************************** <Programming> 2019 accepts scholarly papers that advance knowledge of programming. Almost anything about programming is in scope, but in each case there should be a clear relevance to the act and experience of programming. PAPER SUBMISSIONS: June 1, 2018 URL FOR SUBMISSIONS: http://programming-journal.org/submission/ Submissions covering several areas of expertise are accepted, including but not limited to: â¢ General-purpose programming â¢ Distributed systems programming â¢ Parallel and multi-core programming â¢ Graphics and GPU programming â¢ Security programming â¢ User interface programming â¢ Database programming â¢ Visual and live programming â¢ Data mining and machine learning programming â¢ Interpreters, virtual machines and compilers â¢ Modularity and separation of concerns â¢ Model-based development â¢ Metaprogramming and reflection â¢ Testing and debugging â¢ Program verification â¢ Programming education â¢ Programming environments â¢ Social coding ******************************************************** CALL FOR WORKSHOP PROPOSALS ******************************************************** To build a community and to foster an environment where participants can exchange ideas and experiences related to practical software development, <Programming> will host a number of workshops, during the days before the main conference. The workshops will provide a collaborative forum to exchange recent and/or preliminary results, to conduct intensive discussions on a particular topic, or to coordinate efforts between representatives of a technical community. They are intended as a forum for lively discussion of innovative ideas, recent progress, or practical experience on programming and applied software development in general for specific aspects, specific problems, or domain-specific needs. We also encourage practical, hands-on workshops in which participants actually experience one or several aspects of practical software development. WORKSHOP PROPOSAL SUBMISSIONS: First Deadline: July 1st, 2018 Second Deadline: September 1st, 2018 The duration of workshops is in general one day, but we encourage the submission of half-day workshop proposals on focused topics as well. In exceptional situations, e.g., for workshops that involve actual practice of programming-related activities, workshop organizers can request a 2 day workshop slot. If desired, the workshop proceedings can be published in the ACM Digital Library. ******************************************************** IMPORTANT DATES ******************************************************** Research paper submissions: June 1, 2019 Research paper first notifications: August 1, 2018 Research paper final notifications: September 7, 2018 Workshop proposals: July 1st, 2018 (first deadline) Workshop proposals: September 1st, 2018 (second deadline) ******************************************************** ORGANIZATION ******************************************************** General Chair: Davide Ancona, University of Genova Local Organizing Chair: Elena Zucca, University of Genova Program Chair: Matthew Flatt, University of Utah Organizing Committee: Walter Cazzola (Workshops Co-Chair), UniversitÃ degli Studi di Milano Stefan Marr (Workshops Co-Chair), University of Kent Fabio Niephaus (Publicity Co-Chair), Hasso Plattner Institute, University of Potsdam Tobias Pape (Web Technology Chair), Hasso Plattner Institute, University of Potsdam Program Committee: Mehdi Bagherzadeh, Oakland University Walter Cazzola, UniversitÃ degli Studi di Milano Ravi Chugh, University of Chicago Joeri De Koster, Vrije Universiteit Brussel Christos Dimoulas, Northwestern University Susan Eisenbach, Imperial College London Richard P. Gabriel, Dream Songs, Inc. & HPI Jeremy Gibbons, University of Oxford Michael Greenberg, Pomona College Philipp Haller, KTH Royal Institute of Technology Robert Hirschfeld, HPI, University of Potsdam Eunsuk Kang, Carnegie Mellon University Stephen Kell, University of Cambridge Stefan Marr, University of Kent Tamara Rezk, Inria Joshua Sunshine, Carnegie Mellon University Steffen Zschaler, King's College London ******************************************************** <Programming> 2019 is kindly supported by AOSA ******************************************************** For more information, visit http://2019.programming-conference.org

May 7, 2018

Re: [Pharo-dev] Esteban's ChangeLog week of 30 April 2018

by Stephan Eggermont

<estebanlm(a)gmail.com> wrote: > > This should provide backward compatibility on baselines (who can > still be declared with +github://+ etc. protocol) and > makes tonel format available up to Pharo 3.0 versions (since it does > not depends on iceberg presence anymore). That is great! Thanks! Stephan

May 7, 2018

Esteban's ChangeLog week of 30 April 2018

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 30 April 2018 to 6 May 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=30/4/2018&to=6/5/2018 ChangeLog ========= 3 May 2018: ----------- * I took some time to polish a long time waiting PR: [https://github.com/pharo-project/pharo/pull/1202](https://github.com/pharo-…, which finally closed [case: 20878](https://pharo.fogbugz.com/f/cases/20878)... and incidentally cleaned up some dependencies with old Compiler we no longer need. Not bad :) * I spent last 5 working days working on a change on metacello that I thought it was going to be just a morning. Considering murphy's law of estimations, I'm still 5 days early ;) ... but I'm not done (even if PR is working, you can see it [here](https://github.com/Metacello/metacello/pull/490)) I'm waiting for some feedback from Dale (there are some problems on gemstone side and I need help for it). Anyway. this PR basically makes tonel format available even when declaring +filetree://+ repositories (+filetree://+ now is just a declaration of "smalltalk format", not binded to +cypress+ as before). This should provide backward compatibility on baselines (who can still be declared with +github://+ etc. protocol) and makes tonel format available up to Pharo 3.0 versions (since it does not depends on iceberg presence anymore). cheers! Esteban

May 7, 2018

[Pharo 7.0-dev] Build #840: 21833 Deprecate #isTranslucentColor in Color (and small package cleanups)

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

There is a new Pharo build available! The status of the build #840 was: SUCCESS. The Pull Request #1300 was integrated: "21833 Deprecate #isTranslucentColor in Color (and small package cleanups)" Pull request url: https://github.com/pharo-project/pharo/pull/1300 Issue Url: https://pharo.fogbugz.com/f/cases/21833 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 6, 2018

Re: [Pharo-dev] Curious context change latency experiment results (wrt DelayScheduler)

by Eliot Miranda

Hi Ben, > On May 5, 2018, at 7:25 AM, Ben Coman <btc(a)openinworld.com> wrote: > > > >> On 5 May 2018 at 22:10, Ben Coman <btc(a)openinworld.com> wrote: >> One of the key parts of Delay scheduling is setting the resumption time. >> There are two places this could be done. >> a. In Delay>>#schedule, running (for example) at userSchedulingPriority=40 >> b. In DelayMicrosecondScheduler>>#handleTImerEvent:, running at timingPriority=80 >> >> When we were using the millisecond clock for delay scheduling, >> it made sense to use (b.) since the clock might(?) roll over >> between when resumption time was set, and when #handleTImerEvent: expires delays. >> >> This should not be a problem now that we are using the microsecond clock, >> so I wondered what the latency penalty might be between (a.) and (b.). >> I ran a little experiment that indicates the cost/latency of switching threads, >> and was curious if anyone can comment on the validity of the experiment >> and interpretation of results. >> >> I made the following three changes... >> >> DelayScheduler subclass: #DelayMicrosecondScheduler >> instanceVariableNames: 'latencyStart countSinceLastZero' >> classVariableNames: 'LatencyCounts' >> poolDictionaries: '' >> category: 'Kernel-Processes' >> >> >> DelayMicrosecondScheduler>>#schedule: aDelay >> latencyStart:= Time primUTCMicrosecondsClock. "This is position (a.)" >> aDelay schedulerBeingWaitedOn ifTrue: [^self error: 'This Delay has already been scheduled.']. >> accessProtect critical: [ >> scheduledDelay := aDelay. >> timingSemaphore signal. "#handleTimerEvent: sets scheduledDelay:=nil" >> ]. >> >> >> DelayMicrosecondScheduler>>#handleTimerEvent: microsecondNowTick >> | microsecondNextTick | >> "Process any schedule requests" "This is position (b.)" >> scheduledDelay ifNotNil: [ >> |latency| >> latency := Time primUTCMicrosecondsClock - latencyStart. >> LatencyCounts ifNil: [ LatencyCounts := Bag new ]. >> LatencyCounts add: latency. >> latency = 0 >> ifTrue: [ countSinceLastZero := 1 + (countSinceLastZero ifNil: [0])] >> ifFalse: [Transcript >> crShow: 'zero latency count ' , countSinceLastZero printString ; >> show: ' before latency ', latency printString. >> countSinceLastZero := 0]. >> "Schedule the given delay." >> scheduledDelay scheduler: self resumptionTime: microsecondNowTick + (1000 * scheduledDelay millisecondDelayDuration). >> self scheduleDelay: scheduledDelay. >> scheduledDelay := nil ]. >> <snip> >> rest of method unchanged >> >> >> Then opened the Transcript and in Playground evaluated... >> Delay delaySchedulerClass: DelayMicrosecondScheduler. >> >> >> The Transcript results are shown below with some comments inserted. >> >> Now I guess the latency is affected by garbage collection. >> But one thing I was curious about is why the latency's were quantised in 1000s. >> >> Another interesting thing is that vast majority of the latency's were zero, >> which was a nice surprise, but can it be true? Or is it a consequence >> of the quantitisation rounding down? >> >> It seems that the idle-ness of the image affected how often a non-zero latency occurred. >> After I left the house for a while, the count of zero latency was very high, but a few still occurred. It would make sense there was less GC while idle. What is a good snippet of code to stress GC. I presume the latency might increase. >> >> >> zero latency count 2273 before latency 1000 >> zero latency count 943 before latency 1000 >> zero latency count 3666 before latency 1000 >> zero latency count 1643 before latency 1000 >> zero latency count 27 before latency 1000 >> "Left house for 20 minutes" >> zero latency count 12022 before latency 1000 >> zero latency count 15195 before latency 1000 >> zero latency count 41998 before latency 1000 >> "Returned from outing" >> zero latency count 128 before latency 1000 >> zero latency count 116 before latency 1000 >> zero latency count 555 before latency 1000 >> zero latency count 2377 before latency 1000 >> zero latency count 5423 before latency 1000 >> zero latency count 3178 before latency 1000 >> zero latency count 47 before latency 1000 >> zero latency count 2276 before latency 1000 >> "Left house to go shopping" >> zero latency count 6708 before latency 3000 >> zero latency count 4896 before latency 1000 >> zero latency count 433 before latency 1000 >> zero latency count 7106 before latency 1000 >> zero latency count 2195 before latency 1000 >> zero latency count 12397 before latency 1000 >> zero latency count 4815 before latency 2000 >> zero latency count 3480 before latency 1000 >> zero latency count 5690 before latency 1000 >> zero latency count 1670 before latency 1000 >> zero latency count 320 before latency 1000 >> zero latency count 1641 before latency 2000 >> zero latency count 290 before latency 1000 >> zero latency count 3835 before latency 1000 >> zero latency count 3818 before latency 1000 >> zero latency count 1132 before latency 1000 >> "Returned from shopping." >> zero latency count 2045 before latency 1000 >> zero latency count 671 before latency 1000 >> zero latency count 167 before latency 1000 >> zero latency count 147 before latency 1000 >> >> From the System Browser, inspecting the class variable LatencyCounts showed... >> 0 171329 >> 3000 1 >> 2000 3 >> 1000 49 > > P.S. after running a few more hours, LatencyCounts shows... > 0 1102691 > 1000 219 > 2000 12 > 3000 29 > 4000 21 > 5000 5 > 49000 1 > 75000 1 It's likely that the vm code is using the cheap microsecond click which is updated by the heartbeat, not the expensive one that interrogates the OS at the instant. If not, it's the OS. I'll check soon.

May 5, 2018