- Pharo-dev - lists.pharo.org

Migrating XML support to github/PharoContributions/

by Stephane Ducasse

Hi I contacted the maintainer (but I'm not sure in fact who it is :) ) about the XML related packages in Pharo extras. XMLParser XMLParserHTML XMLParserStAX XMLSupport XMLWriter XPath I did not get any answer so may be I sent a mail to the wrong email address. Probably. Now the question still remains: who is planning to migrate the XML packages. I was planning to do it but I will not consider history because I do not know how to do it and I do not have the time to do it (sorry). And yes I work the weekends and this is bad and this is not even on Pharo. I was planning to spend some time on the baseline and making sure that we can load everything and run the tests. So let me know. Stef

Sept. 29, 2018

[ANN] Migrated Artefact to GitHub

by Stephane Ducasse

Hi guille I deeply appreciated that you spent your time to bring Artefact to Pharo 70 and in general all the positive energy you put around Pharo. I love Iceberg! and more! I quit these mailing-lists in the past because of these little aggressions, the "You should do that" I registered today again to this mailing list just to publicly talk to you, while I could come to your office (I will do it too). I did a port of Artefact to Pharo 60 a while ago and started to fix Artefact aspects I did not like and I would like to integrate my fixes to yours. Please let me know where it is. :) I do not care of the history because I prefer the future. If people care then this is their duties. Easy. If they are not happy. This is THEIR PROBLEM. You see people often tells me that I cannot control and that github is decentralised. It is! So enjoy but @People try to avoid to piss on good will of others. Now sorry Norbert your point that Guillemo would be rude because he spent his time to help Milton and made sure that Artefact in Pharo 70 is clearly out of context and misplaced. You see I did the same in github.com/olivierauverlot because I needed it. And this is like that. Period. You are not happy. This is ok. You do not like it. This is ok too. This is several times that I noticed that your are not nice with emails so do the same than me: think about the impact on others. You have no idea about what guille is doing and what it is paid for and this is certainly not to fix Artefact. And you may notice that we know what is to work on others unmaintained code because we do it all the time, we even create documentation on systems we do not understand because some people are too busy to write method and class comments so imagine documentation. So I would like to thanks again guille and I would like to have artefact on Pharo 70. Stef

Sept. 29, 2018

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

by Alexandre Bergel

Thanks Guille! Alexandre > On Sep 27, 2018, at 7:27 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > 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 > > Web: http://guillep.github.io > Phone: +33 06 52 70 66 13

Sept. 28, 2018

[Pharo 7.0-dev] Build #1276: 22482-AutoCompletion-preview-breaks-code-navigation

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

There is a new Pharo build available! The status of the build #1276 was: SUCCESS. The Pull Request #1831 was integrated: "22482-AutoCompletion-preview-breaks-code-navigation" Pull request url: https://github.com/pharo-project/pharo/pull/1831 Issue Url: https://pharo.fogbugz.com/f/cases/22482 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 28, 2018

[Pharo 7.0-dev] Build #1275: 22480-ClassTestCase--testClassComment-depends-on-the-environment-configuration

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

There is a new Pharo build available! The status of the build #1275 was: FAILURE. The Pull Request #1829 was integrated: "22480-ClassTestCase--testClassComment-depends-on-the-environment-configuration" Pull request url: https://github.com/pharo-project/pharo/pull/1829 Issue Url: https://pharo.fogbugz.com/f/cases/22480 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 28, 2018

[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