- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] 89d297: 60501
by GitHub June 14, 2017

June 14, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 89d297dce3beea42497ef1b7aea3d7460bc75a4b https://github.com/pharo-project/pharo-core/commit/89d297dce3beea42497ef1b7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-06-14 (Wed, 14 Jun 2017) Changed paths: M Kernel.package/Deprecation.class/class/class initialization/initialize.st M Kernel.package/Deprecation.class/class/logging/deprecationsWhile_.st M Kernel.package/Deprecation.class/class/settings/raiseWarning.st M Kernel.package/Deprecation.class/class/settings/showWarning.st M Kernel.package/Deprecation.class/instance/handling/transform.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60500.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60501.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60500.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60501.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Tools.package/VersionBrowser.class/instance/accessing/displayStringsFor_.st Log Message: ----------- 60501 20093 Missing source stamp makes changes hard to view https://pharo.fogbugz.com/f/cases/20093 20148 transforming deprecations should take #showWarning into account https://pharo.fogbugz.com/f/cases/20148 http://files.pharo.org/image/60/60501.zip

1 0

[pharo-project/pharo-core]
by GitHub June 14, 2017

June 14, 2017

Branch: refs/tags/60501 Home: https://github.com/pharo-project/pharo-core

1 0

Re: [Pharo-dev] [Vm-dev] BUG? A problem with callbacks that shows up in 64bits (but is on 32bits too)
by Eliot Miranda June 14, 2017

June 14, 2017

Hi Esteban, Hi Igor, Hi All, On Fri, Mar 10, 2017 at 7:35 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > Iâm tumbling into an error in Pharo, because we use callbacks intensively, > in Athens(cairo)-to-World conversion in particular, and people is sending > always their crash reportsâ¦ we made the whole conversion a lot more robust > since problems started to arise, but now I hit a wall I cannot solve: I > think problem is in something in callbacks. > > And problem is showing very easy on 64bits (while in 32bits it takes time > and is more random). > I responded in the "image not opening" thread, but it's the same problem. I really want to hear what y'all think because I'll happily implement a fix, but I want to know which one y'all think is a good idea. Here's my reply (edits between [ & ] to add information): On Mon, Mar 13, 2017 at 9:11 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: I'm pretty confident [I know] this is to do with bugs in the Athens surface code which assumes that callbacks can be made in the existing copyBits and warpBits primitive. They can't do this safely because a GC (scavenge) can happen during a callback, which then causes chaos when the copyBits primitive tries to access objects that have been moved under its feet. I've done work to fix callbacks so that when there is a failure it is the copyBits primitive that fails, instead of apparently the callback return primitive. One of the apparent effects of this fix is to stop the screen opening up too small; another is getting the background colour right, and yet another is eliminating bogus pixels in the VGTigerDemo demo. But more work is required to fix the copyBits and warpBits primitives. There are a few approaches one might take: a) fixing the primitive so that it saves and restores oops around the callbacks using the external oop table [InterpreterProxy>>addGCRoot: & removeGCRoot:]. That's a pain but possible. [It's a pain because all the derived pointers (the start of the destForm, sourceForm, halftoneForm and colorMapTable) must be recomputed also, and of course most of the time the objects don't move; we only scavenge about once every 2 seconds in normal running] b) fixing the primitive so that it pins the objects it needs before ever invoking a callback [this is a pain because pinning an object causes it to be tenured to old space if it is in new space; objects can't be pinned in new space, so instead the pin operation forwards the new space object to an old space copy if required and answers its location in old space, so a putative withPinnedObjectsDo: operation for the copyBits primitive looks like withPinnedFormsDo: aBlock <inline: #always> self cppIf: SPURVM & false ifTrue: [| bitBltOopWasPinned destWasPinned sourceWasPinned halftoneWasPinned | (bitBltOopWasPinned := interpreterProxy isPinned: bitBltOop) ifFalse: [bitBltOop := interpreterProxy pinObject: bitBltOop]. (destWasPinned := interpreterProxy isPinned: destForm) ifFalse: [destForm := interpreterProxy pinObject: destForm]. (sourceWasPinned := interpreterProxy isPinned: sourceForm) ifFalse: [sourceForm := interpreterProxy pinObject: sourceForm]. (halftoneWasPinned := interpreterProxy isPinned: halftoneForm) ifFalse: [halftoneForm := interpreterProxy pinObject: halftoneForm]. aBlock value. bitBltOopWasPinned ifFalse: [interpreterProxy unpinObject: bitBltOop]. destWasPinned ifFalse: [interpreterProxy unpinObject: destForm]. sourceWasPinned ifFalse: [interpreterProxy unpinObject: sourceForm]. halftoneWasPinned ifFalse: [interpreterProxy unpinObject: halftoneForm]] ifFalse: [aBlock value] and tenuring objects to old space is not ideal because they are only collected by a full GC, so doing this would at least tenure the bitBltOop which is very likely to be in new space] c) fixing the primitive so that it uses the scavenge and fullGC counters in the VM to detect if a GC occurred during one of the callbacks and would fail the primitive [if it detected that a GC had occurred in any of the surface functions]. The primitive would then simply be retried. d) ? I like c) as it's very lightweight, but it has issues. It is fine to use for callbacks *before* cop[yBits and warpBits move any bits (the lockSurface and querySurface functions). But it's potentially erroneous after the unlockSurface primitive. For example, a primitive which does an xor with the screen can't simply be retried as the first, falling pass, would have updated the destination bits but not displayed them via unlockSurface. But I think it could be arranged that no objects are accessed after unlockSurface, which should naturally be the last call in the primitive (or do I mean showSurface?). So the approach would be to check for GCs occurring during querySurface and lockSurface, failing if so, and then caching any and all state needed by unlockSurface and showSurface in local variables. This way no object state is accessed to make the unlockSurface and showSurface calls, and no bits are moved before the queryDurface and lockSurface calls. If we used a failure code such as #'object may move' then the primitives could answer this when a GC during callbacks is detected and then the primitive could be retried only when required. [Come on folks, please comment. I want to know which idea you like best. We could fix this quickly. But right now it feels like I'm talking to myself.] > Here is the easiest way to reproduce it (in mac): > > wget files.pharo.org/get-files/60/pharo64-mac-latest.zip > wget files.pharo.org/get-files/60/pharo64.zip > wget files.pharo.org/get-files/60/sources.zip > unzip pharo64-mac-latest.zip > unzip pharo64.zip > unzip sources.zip > ./Pharo.app/Contents/MacOS/Pharo ./Pharo64-60438.image eval "VGTigerDemo > runDemo" > > eventually (like 5-6 seconds after, if not immediately), you will have a > stack like this: > > SmallInteger(Object)>>primitiveFailed: > SmallInteger(Object)>>primitiveFailed > SmallInteger(VMCallbackContext64)>>primSignal:andReturnAs:fromContext: > GrafPort>>copyBits > GrafPort>>image:at:sourceRect:rule: > FormCanvas>>image:at:sourceRect:rule: > FormCanvas(Canvas)>>drawImage:at:sourceRect: > FormCanvas(Canvas)>>drawImage:at: > VGTigerDemo>>runDemo > VGTigerDemo class>>runDemo > UndefinedObject>>DoIt > OpalCompiler>>evaluate > OpalCompiler(AbstractCompiler)>>evaluate: > [ result := Smalltalk compiler evaluate: aStream. > self hasSessionChanged > ifFalse: [ self stdout > print: result; > lf ] ] in EvaluateCommandLineHandler>>evaluate: > in Block: [ result := Smalltalk compiler evaluate: aStream.... > BlockClosure>>on:do: > EvaluateCommandLineHandler>>evaluate: > EvaluateCommandLineHandler>>evaluateArguments > EvaluateCommandLineHandler>>activate > EvaluateCommandLineHandler class(CommandLineHandler class)>>activateWith: > [ aCommandLinehandler activateWith: commandLine ] in > PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in > Block: [ aCommandLinehandler activateWith: commandLine ] > BlockClosure>>on:do: > PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: > PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand > PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument: > [ self > handleArgument: > (self arguments > ifEmpty: [ '' ] > ifNotEmpty: [ :arguments | arguments first ]) ] in > PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: [ > self... > BlockClosure>>on:do: > PharoCommandLineHandler(BasicCommandLineHandler)>>activate > PharoCommandLineHandler>>activate > PharoCommandLineHandler class(CommandLineHandler class)>>activateWith: > [ super activateWith: aCommandLine ] in PharoCommandLineHandler > class>>activateWith: in Block: [ super activateWith: aCommandLine ] > > Any idea? > > thanks! > Esteban -- _,,,^..^,,,_ best, Eliot

6 11

[pharo-project/pharo-core]
by GitHub June 14, 2017

June 14, 2017

Branch: refs/tags/60500 Home: https://github.com/pharo-project/pharo-core

1 0

[pharo-project/pharo-core] e59a47: 60500
by GitHub June 14, 2017

June 14, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: e59a4769ea6b401295c17ddf67cfb58757f8909d https://github.com/pharo-project/pharo-core/commit/e59a4769ea6b401295c17ddf… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-06-14 (Wed, 14 Jun 2017) Changed paths: R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60499.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60500.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60499.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60500.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Zinc-Zodiac.package/ZnHTTPSTests.class/instance/testing/testGetPharoVersion.st Log Message: ----------- 60500 20146 ZnHTTPSTests>>#testGetPharoVersion started to fail https://pharo.fogbugz.com/f/cases/20146 http://files.pharo.org/image/60/60500.zip

1 0

[ANN] Pharo 6.0 released!
by Esteban Lorenzano June 13, 2017

June 13, 2017

Dear World, The time has come for Pharo 6.0! Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. This is our most significant release yet. Here are some highlights: - Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability (beware, 64bits version is a new technology and a small amount of tests is still failing) - A new code changes management system named Epicea for easier reviewing and recovering of your code easily - Integrated support for Git through an easy-to-use tool for repositories and commits management named Iceberg (as a preview for Pharo 6, it will be the default in Pharo 7) - The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved - The PharoVM is now part of OpenSmalltalk initiative - Introduction of object immutability, alternative bytecode sets and block closures independent of outer context - Pharo can now be bootstrapped from source code managed by Git - Pharo modularity is improved - Pharo is faster - The Dark Theme was improved and set as default color theme of Pharo These are just the more prominent highlights, but the details are just as important. We have closed 1474 issues in Pharo 6.0 (a more complete changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo60Change…) While the technical improvements are significant (starting the transition to 64bits is a remarkable achievement), still the most impressive fact is that the new code that got in the main Pharo 6.0 image was contributed by more than 80 people. Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release: Alberto Bacchelli, Alejandro Infante, Alexandre Bergel, Aliaksei Syrel, Alistair Grant, Andrei Chis, Ben Coman, Bernardo Contreras, Bernhard Pieber, Boris Spasojevic, Christophe Demarey, Clement Bera, Cyril Ferlicot, Dale Henrichs, Damien Cassou, Damien Pollet, Dave Lewis, Denis Kudriashov, Dirk Roeleveld, Eliot Miranda, Esteban Lorenzano, Esteban Maringolo, Evan Donahue, Federico Balaguer, Franck Warlouzet, Glenn Cavarle, Guillermo Polito, Gustavo Santos, Henrik Johansen, Henrik Nergaard, Hilaire Fernandes, Holger Hans, Jan Kurs, Jan van de Sandt, Johan Fabry, Juraj Kubelka, K. K. Subramaniam, Ken Causey, Kris Gybels, Lionel Akue, Luc Fabresse, Lucas Godoy, Marcus Denker, Mariano Martinez Peck, Marion Noirbent, Martin Dias, Max Leske, Maxime Roelandt, Merwan Ouddane, Matteo Bellotto, Miguel Campusano, Milton Mamani, Myroslava Romaniuk, Nicolai Hess, Nicolas Cellier, Nicolas Passerini, Norbert Hartl, Offray Luna, Pablo Tesone, Paul De Bruicker, Pavel Krivanek, Peter Uhnak, Philippe Back, Roger Stebler, Ronie Salgado, Sean DeNigris, Serge Stinckwich, Skip Lentz, Sophie Kaleba, Stefan Reichhart, Stephan Eggermont, Stephane Ducasse, Sven Van Caekenberghe, Thibault Arloing, Thibault Arloing, Thibault Raffaillac, Thierry Goubier, Thomas Heniart, Tommaso Dal Sasso, Torsten Bergmann, Tudor Girba, Udo Schneider, Valentin Ryckewaert, Vincent Blondeau, Werner Kassens, Yuriy Tymchuk (If you contributed with Pharo 6.0 development in any way and we missed your name, please send us a mail and we will add you). Enjoy! The Pharo Team Try Pharo: http://pharo.org/download Learn Pharo: http://pharo.org/documentation

12 13

Github package management beta
by Eliot Miranda June 13, 2017

June 13, 2017

Hi All, I've been invited to participate in github's Bera test of their new package management support. I don't know much, if anything, about the software except that it supports RubyGems (Ruby), Maven (Java) and npm (JavaScript) formats. My contact at github has asked me to supply a list of email addresses of those who would like to test the software. My contact will provide documentation. If you would like to participate please reply to me using this same subject line and including in the body of the message the email you'd like used. Please do top post. Maybe we could get github to directly support Monticello. Maybe this could achieve some simplifications and ease some tensions. I don't know. But I'm intrigued. Cheers! _,,,^..^,,,_ (phone)

5 4

CPU and RAM usage of Pharo3 vs. Pharo6
by Holger Freyther June 12, 2017

June 12, 2017

Hey! my current major deployment is still with Pharo3 and due some bigger changes I start to migrate to Pharo6 and today I finally managed to update the test deployment (and be happy with it). The test is not scientific but maybe an early indicator that there is something to look at? The image is idle and not handling any application payload so it might be a fair comparison because of that. RSS + ~16 MiB RAM (~53 Mib vs. ~69 Mib) CPU + ~0.005s per real second passed (think of Amazon AWS why that could matter) (In ~1400s wall clock 57.8s vs. 50.86s cpu time was used) Does anyone else see this increased usage? Has anyone explored the source of it? Does anyone of you share the concern I have? :) holger Outline of the setup: * Take a Pharo3 or Pharo6 base image * Load my code (and its dependencies, big difference is version of Voyage) * Start the images on the test system * Opens a TCP connection, initialize VoyageMongo * Wait for work Look at top for RSS and CPU time used.

3 4

CFP - IWST 2017 - International Workshop on Smalltalk Technologies - deadline extension
by Anne Etien June 12, 2017

June 12, 2017

Dear Smalltakers, Deadline of IWST has been postponed to June 21th AoE. However, we ask you to submit at least an abstract for June 16th. Only papers submitted before this date could be modified until June 21th. Thanks in advance, Cheers, Jannik and Anne > DÃ©but du message rÃ©expÃ©diÃ© : > > De: <jannik.laval(a)gmail.com> > Objet: [Moose-dev] CFP - IWST 2017 - International Workshop on Smalltalk Technologies > Date: 13 avril 2017 10:59:00 UTC+2 > Ã: "'Moose-related development'" <moose-dev(a)list.inf.unibe.ch> > RÃ©pondre Ã : Moose-related development <moose-dev(a)list.inf.unibe.ch> > > CFP - IWST 2017 - International Workshop on Smalltalk Technologies > > [Please accept our apologies if you receive multiple copies of this call] > [Please send to interested colleagues / mailing-lists] > ************************************************************************************************************ > CALL FOR PAPERS > > IWST 2017 â International Workshop on Smalltalk Technologies > http://www.esug.org/wiki/pier/Conferences/2017/International-Workshop-IWST_… <http://www.esug.org/wiki/pier/Conferences/2017/International-Workshop-IWST_…> > > Maribor, Slovenia; Between September 4th to 8th, 2017 > ************************************************************************************************************ > > ------------------- > Goals and scopes > ------------------- > The goals of the workshop is to create a forum around advances or experience in Smalltalk and to trigger discussions and exchanges of ideas. The topics of your paper can be on all aspect of Smalltalk, theoretical as well as practical. Participants are invited to submit research articles or industrial papers. This year we want to open two different tracks: one research track and one industrial track with less scientific constraints. > > We expect papers of three kinds: > > Short position papers describing emerging ideas > Long research papers with deeper description of experiments and of research results. > Industrial papers with presentation of real and innovative Smalltalk applications; this kind of paper should enlighten why Smalltalk is really appropriate for your application. > We will not enforce any length restriction. > > -------------------- > Important Dates > -------------------- > Submission deadline: June 16th, 2017 > Notification deadline: July 21th, 2017 > Workshop : between September 4th and 8th, 2017 > All accepted papers will be published in ACM DL (To be confirmed) > > ------------------- > Topics > ------------------- > We welcome contributions on all aspects, theoretical as well as practical, of Smalltalk related topics such as: > > -Aspect-oriented programming, > -Design patterns, > -Experience reports, > -Frameworks, > -Implementation, new dialects or languages implemented in Smalltalk, > -Interaction with other languages, > -Meta-programming and Meta-modeling, > -Tools > > ------------------- > Best Paper Award > ------------------- > To encourage the submission of high-quality papers, the IWST organizing committee is very proud to announce a Best Paper Award for this edition of IWST. > > We thank the Lam Research Corporation for its financial contribution which makes it possible for prizes for the three best papers: 1000 USD for first place, 600 USD for second place and 400 USD for third place. > > The ranking will be decided by the program committee during the review process. The awards will be given during the ESUG conference social event. > > The Best Paper Award will take place only with a minimum of six submissions. Notice also that to be illegible, a paper must be presented at the workshop by one of the author and that the presenting author must be registered at the ESUG conference. > > ------------------- > Publication > ------------------- > Both submissions and final papers must be prepared using the ACM SIGPLAN 10 point format. Templates for Word and LaTeX are available at http://www.acm.org/sigs/sigplan/authorInformation.htm <http://www.acm.org/sigs/sigplan/authorInformation.htm>. This site also contains links to useful informations on how to write effective submissions. > > ------------------- > Submission > ------------------- > All submissions must be sent via easychair: https://easychair.org/conferences/?conf=iwst2017 <https://easychair.org/conferences/?conf=iwst2017> > > ------------------- > Program chairs > ------------------- > Anne Etien (UniversitÃ© de Lille 1, France) > Jannik Laval (UniversitÃ© Lyon 2 LumiÃ¨re, France) > > > -- > ~~Jannik Laval~~ > Enseignant-chercheur > Responsable PÃ©dagogique Licence Coordonnateur de Projet en SystÃ¨me d'Information > IUT LumiÃ¨re <http://iut.univ-lyon2.fr/>, UniversitÃ© LumiÃ¨re Lyon 2 <http://www.univ-lyon2.fr/> > laboratoire DISP <http://disp-lab.fr/> > +33 4 78 77 43 06 > http://www.jannik-laval.eu <http://www.jannik-laval.eu/> > http://www.phratch.com <http://www.phratch.com/> > http://www.approchealpes.info <http://www.approchealpes.info/> > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Garanti sans virus. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <x-msg://222/#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>_______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch> > https://www.list.inf.unibe.ch/listinfo/moose-dev <https://www.list.inf.unibe.ch/listinfo/moose-dev>

1 0

Esteban's ChangeLog week of 5 June 2017
by estebanlm＠gmail.com June 12, 2017

June 12, 2017

Hello! This is my weekly ChangeLog, from 5 June 2017 to 11 June 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=5/6/2017&to=11/6/2017 ChangeLog ========= 6 June 2017: ------------ * Well... we finally [released version 6.0](http://pharo.org/news/pharo6.0-released) ! And yes, I've been working the full day on that :) cheers! Esteban

1 0