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

[Pharo 7.0-dev] Build #1274: 22458-lastFileFor-baseFileName-extension-extension-randomly-sorts-files

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

There is a new Pharo build available! The status of the build #1274 was: FAILURE. The Pull Request #1806 was integrated: "22458-lastFileFor-baseFileName-extension-extension-randomly-sorts-files" Pull request url: https://github.com/pharo-project/pharo/pull/1806 Issue Url: https://pharo.fogbugz.com/f/cases/22458 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 28, 2018

Re: [Pharo-dev] PharoLauncher based test resporting centre

by Ben Coman

On Fri, 28 Sep 2018 at 10:23, Ben Coman <btc(a)openinworld.com> wrote: > Just a random idea... > when running Testrunner locally and a random test causes the image to > freeze, its a bit of an effort to identify which test was being run. You > need to restart and then start bisecting the tests and perhaps it is > intermittent so the bisect doesn't work... > > but now that PharoLauncher has been mainstreamed > maybe it could provide a centralised Reporting Centre > i.e. open a port for launched images to report the test about-to-commence > as well as the run time. Then it would be simple to see which test froze > the system. Also it could keep a record individual test runtimes, to > alleviate fears when the system is not frozen but just a long running test. > > Extending the idea, while CI testing is very useful, we get these sporadic > errors that are hard to replicate locally. A local PharoLauncher driven > system for repetitively launching an image auto-running tests might be good > to gather statistics on sporadic failures to then drill down on the > troublemakers. > > Plus with the goal of having an object based logging system, a viewer is > needed and perhaps PharoLauncher would be a logical place to provide a > logging service to gather and especially to view log-objects reporting by > launched images. > side thought, such a system might be good for watching test progress on headless IoT devices. > > of course, resources required to do it, > but just thought I share the idea. > > cheers -ben >

Sept. 28, 2018

PharoLauncher based test resporting centre

by Ben Coman

Just a random idea... when running Testrunner locally and a random test causes the image to freeze, its a bit of an effort to identify which test was being run. You need to restart and then start bisecting the tests and perhaps it is intermittent so the bisect doesn't work... but now that PharoLauncher has been mainstreamed maybe it could provide a centralised Reporting Centre i.e. open a port for launched images to report the test about-to-commence as well as the run time. Then it would be simple to see which test froze the system. Also it could keep a record individual test runtimes, to alleviate fears when the system is not frozen but just a long running test. Extending the idea, while CI testing is very useful, we get these sporadic errors that are hard to replicate locally. A local PharoLauncher driven system for repetitively launching an image auto-running tests might be good to gather statistics on sporadic failures to then drill down on the troublemakers. Plus with the goal of having an object based logging system, a viewer is needed and perhaps PharoLauncher would be a logical place to provide a logging service to gather and especially to view log-objects reporting by launched images. of course, resources required to do it, but just thought I share the idea. cheers -ben

Sept. 28, 2018

[Pharo 7.0-dev] Build #1273: 22477-DelayScheduler-cleanup-and-refactoring

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

There is a new Pharo build available! The status of the build #1273 was: FAILURE. The Pull Request #1819 was integrated: "22477-DelayScheduler-cleanup-and-refactoring" Pull request url: https://github.com/pharo-project/pharo/pull/1819 Issue Url: https://pharo.fogbugz.com/f/cases/22477 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 27, 2018

Re: [Pharo-dev] [Pharo-users] [ANN] Migrated Artefact to GitHub

by Alistair Grant

Hi Guille, I wasn't aware this existed - thanks for letting us know! Cheers, Alistair On Thu, 27 Sep 2018 at 15:41, Norbert Hartl <norbert(a)hartl.name> wrote: > > Super! Thanks > > Norbert > > Am 27.09.2018 um 11:26 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > Hi all, > > I've moved the Artefact library to GitHub (https://github.com/pharo-contributions/Artefact) > > I've also made some changes to it in the way and made a 1.7.0 version with: > - support for Pharo7 streams > - a baseline > > So, people using Artifact, you can contribute through pull requests ^^, > Guille > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - http://www.cnrs.fr > > > Web: http://guillep.github.io > > Phone: +33 06 52 70 66 13

Sept. 27, 2018

Re: [Pharo-dev] Esteban's ChangeLog week of 17 September 2018

by Sven Van Caekenberghe

> On 24 Sep 2018, at 10:01, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > >> On 24 Sep 2018, at 09:11, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Esteban, >> >>> On 24 Sep 2018, at 08:00, estebanlm(a)gmail.com wrote: >>> >>> * I migrated all [pharo-ide](https://github.com/pharo-ide) projects to tonel format. >>> >>> Harder than it seems, it took me a good bunch of hours. But now is working. >>> >>> This will enhance work/fixes on Calypso. >> >> If it was hard for you, how are we supposed to do it ? >> Is there a guide/description somewhere ? > > For what? > Migration? > There is an option on iceberg (repository/extrasâ¦) that does that and it will work 99% of the cases (there is a known bug with a fix waiting on the iceberg repo who prevents seaside migration). > This will migrate without history. Or better: history will be there, just in filetree but since there is no match between one format and another and that will give problems to see the history. I managed to convert https://github.com/svenvc/P3 to Tonel and all went well (as far as I can see). I must say that Iceberg matured a lot lately, it works super nice. Thx! > The problem here was that I needed to migrate all pharo-ide repositories, and update baselines and make all tests pass and in the middle I exceeding travis ârightâ to see tags (if you are not authenticated, it can happen), etc. > So a lot of small problems not directly related with the migration itself :) > > Esteban > >> >> Sven

Sept. 27, 2018

Top MenuBar does not auto follow font changes

by Sven Van Caekenberghe

Hi, The Top MenuBar does not seem to auto follow font changes, although it picks them uppitiest when you hide/show the menu bar from the Settings. Sven

Sept. 27, 2018

Re: [Pharo-dev] [Pharo-users] [ANN] Migrated Artefact to GitHub

by Norbert Hartl

Super! Thanks Norbert > Am 27.09.2018 um 11:26 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > Hi all, > > I've moved the Artefact library to GitHub (https://github.com/pharo-contributions/Artefact) > > I've also made some changes to it in the way and made a 1.7.0 version with: > - support for Pharo7 streams > - a baseline > > So, people using Artifact, you can contribute through pull requests ^^, > Guille > > -- > > Guille Polito > Research Engineer > Centre de Recherche en Informatique, Signal et Automatique de Lille > CRIStAL - UMR 9189 > French National Center for Scientific Research - http://www.cnrs.fr > > Web: http://guillep.github.io > Phone: +33 06 52 70 66 13

Sept. 27, 2018

Re: [Pharo-dev] Artifact and PDFExporter for Roassal

by Guillermo Polito

Hi Milton, I've taken 1 hour to migrate Artefact to Github, create a baseline, fix your issue and make a new release. Can you test? https://github.com/pharo-contributions/Artefact Guille On Thu, Sep 13, 2018 at 4:40 PM milton mamani <akevalion(a)gmail.com> wrote: > > > El jue., 13 sept. 2018 a las 14:06, milton mamani (<akevalion(a)gmail.com>) > escribiÃ³: > >> Hi! >> >> I am Milton Mamani I work with Roassal2, and now I am in ESUG-Cagliari, >> and I have tried to load Artefact with the next piece of code, in the last >> Pharo7 image. >> >> Metacello new >> configuration: 'Artefact'; >> smalltalkhubUser: 'RMoD' project: 'Artefact'; >> version: #stable; >> load. >> >> "To load roassal and pdf roassal exporter" >> >> Metacello new >> configuration: 'GraphQLBeta'; >> smalltalkhubUser: 'ObjectProfile' project: 'GraphQL'; >> version: #development; >> load. >> >> Gofer new >> smalltalkhubUser: 'azazael' project: 'RTPDFExporter'; >> package: 'ConfigurationOfRTPDFExporter'; load. >> (Smalltalk at: #ConfigurationOfRTPDFExporter) loadDevelopment >> >> I have a problem, when I tried to export my Roassal-Visualization to pdf >> file with for example this piece of code: >> >> view := RTBoxPlotExample new exampleBoxPlot5 build view. >> stream := 'foo.pdf' asFileReference writeStream. >> >> [RTPDFExporter new >> stream: stream; >> exportView: view ] ensure: [ stream close ] >> >> I get a lot of kind exceptions related with the class: PDFStreamPrinter >> >> In the method visitPDFDataXRefEntry: >> And in the logic of the new Stream classes of Pharo7. >> >> Could you please review Artifact in Pharo7 with this roassal2 >> implementation >> >> Cheers, >> Milton >> >> -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Sept. 27, 2018

[ANN] Migrated Artefact to GitHub

by Guillermo Polito

Hi all, I've moved the Artefact library to GitHub ( https://github.com/pharo-contributions/Artefact) I've also made some changes to it in the way and made a 1.7.0 version with: - support for Pharo7 streams - a baseline So, people using Artifact, you can contribute through pull requests ^^, Guille -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Sept. 27, 2018