October 2014 - Pharo-dev - lists.pharo.org

Super fast delay

by Norbert Hartl

I just recognized that Delay is working in a strange way on my linux box $ time pharo-vm-nox ./Pharo.image eval "(Delay forSeconds: 5) wait" a Delay(5000 msecs) real 0m0.158s user 0m0.136s sys 0m0.020s I use the vm from the ppa. What do you get when you execute it? Norbert

Oct. 28, 2014

Re: [Pharo-dev] AioPlugin is back in linux VMs

by Esteban Lorenzano

so you can pipe outputs when executing OSProcess commands. something like that. > On 28 Oct 2014, at 17:53, kilon alios <kilon.alios(a)gmail.com> wrote: > > whats the purpose of the plugin ? How we can test it ? > > On Tue, Oct 28, 2014 at 6:51 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > Hi, > > I reintroduced AioPlugin into the linux VM. > In Mac it is there since always. > In windows is irrelevant. > > So well, if you use linux and download the latest vm, you can play with it and check that everything is ok (or the contrary) :) > > Esteban >

Oct. 28, 2014

Re: [Pharo-dev] ShoreLine Reporter - A tool to collect stack traces

by Tommaso Dal Sasso

On Mon, Oct 27, 2014 at 1:18 PM, Stephan Eggermont <stephan(a)stack.nl <mailto:stephan@stack.nl>> wrote: > > Marcus wrote > > I was thinking... would it make sense to have this in the image > by default? > > Not all my work is open source. How do I make sure I don't > inadvertently > leak information? > > Stephan > > This is an interesting problem, and I would love to hear your opinion given your experience. The status of ShoreLine Reporter is that it stores the name of the class and the name of the method, no parameter is involved. I indeed understand that the name of the method and the trace of calls may reveal information that a user may want to keep private. As Markus said, we could filter the classes included in the stock Pharo image, but this would discard classes of projects like Voyage or Seaside. Another option could be to provide the user with a way to filter some classes, for example by matching the class name prefix. I am the first one to dislike "Big Brother" systems, so I am particularly sensible on the matter. What do you think? Thanks, Tommaso On 27/10/14 13:22, Marcus Denker wrote: > It would need to filter and only send those traces that are part of > the image. > > In a later step, it would be interesting to give people the same > infrastructure for their > own code, private to them. > > (like those error stack trace collecting tools that are used for > mobile apps) > > > >

Oct. 28, 2014

Re: [Pharo-dev] AioPlugin is back in linux VMs

by kilon alios

whats the purpose of the plugin ? How we can test it ? On Tue, Oct 28, 2014 at 6:51 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > I reintroduced AioPlugin into the linux VM. > In Mac it is there since always. > In windows is irrelevant. > > So well, if you use linux and download the latest vm, you can play with it > and check that everything is ok (or the contrary) :) > > Esteban >

Oct. 28, 2014

Re: [Pharo-dev] AioPlugin is back in linux VMs

by Esteban Lorenzano

ah yesâ¦ this was important for OSProcess and derivates :) Esteban > On 28 Oct 2014, at 17:51, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > I reintroduced AioPlugin into the linux VM. > In Mac it is there since always. > In windows is irrelevant. > > So well, if you use linux and download the latest vm, you can play with it and check that everything is ok (or the contrary) :) > > Esteban

Oct. 28, 2014

AioPlugin is back in linux VMs

by Esteban Lorenzano

Hi, I reintroduced AioPlugin into the linux VM. In Mac it is there since always. In windows is irrelevant. So well, if you use linux and download the latest vm, you can play with it and check that everything is ok (or the contrary) :) Esteban

Oct. 28, 2014

Re: [Pharo-dev] ShoreLine Reporter - A tool to collect stack traces

by Tommaso Dal Sasso

On 27/10/14 13:05, stepharo wrote: > tommaso > send us a working script > not something that we should browse and understand. > > Stef You are right, the loading script is in the project page, but it is indeed another step of unneeded indirection. Thanks, Tommaso P.s.: for the sake of completeness, this is the script to load ShoreLine Reporter and configure it to automatically submit the stack traces without bothering the user ;-) StartupLoader default executeAtomicItems: { StartupAction name: 'ShoreLine-Reporter Installer' code: [ [ Gofer it smalltalkhubUser: 'dalsat' project: 'ShoreLine-Reporter'; configuration; load. #ConfigurationOfShoreLineReporter asClass load. "Setting Reporter configuration" #SlReporter asClass enabled: true. #SlReporter asClass autoSubmit: true. #SlReporter asClass showSummary: false. #SlReporter asClass showNotification: true. ] asJob run ] runOnce: true. }. > > On 7/10/14 11:23, Tommaso Dal Sasso wrote: >> Hello everybody, >> >> for those of you who were not at ESUG, I present ShoreLine Reporter. >> >> ShoreLine Reporter is a Pharo plugin to collect stack traces from >> exceptions and send them to a central repository. >> You can give feedback to the community by breaking things: how cool >> is that? >> >> >> * Why? >> >> We are collecting stack traces for research purposes and to identify >> the Pharo components that can be improved or optimized. >> We are also working on a web platform where users can access the >> submitted data and use them during the debugging process. More on >> that soon! >> >> >> * How? >> >> You can install ShoreLine Reporter by visiting the project page on >> SmalltalkHub: >> http://www.smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter/ >> >> Installing ShoreLine Reporter requires only a couple of seconds, and >> you can configure it with the level of feedback that you prefer. On >> the SmalltalkHub page you can find a script to automatically install >> ShoreLine Reporter with every new Pharo image. Just drop it in your >> Pharo preferences directory and forget about it. >> >> Once ShoreLine Report is installed, you can decide to configure if >> you want to be prompted to submit a stack trace, or to automatically >> submit each exception without any bother. >> >> >> * What? >> >> We try to collect as few data as possible: the execution stacktrace, >> the name of the author and the Pharo build. We do *not* any collect >> personal data, such as passwords or repositories. The data is >> currently stored on our server, at the University of Lugano. >> >> >> * Compatibility >> >> ShoreLine Reporter is developed for the Pharo debugger. We are >> improving ShoreLine Reporter to work with GTInspector, we will push >> an update in the following days. >> >> >> For any problem, contact me! >> >> Thanks, hope to see a lot of your exceptions ;-) >> Tommaso Dal Sasso @ REVEAL >> >> > >

Oct. 28, 2014

Re: [Pharo-dev] ShoreLine Reporter - A tool to collect stack traces

by Tommaso Dal Sasso

Hello everybody, thanks for your feedback. > On 27/10/14 07:01, Marcus Denker wrote: >> I was thinking... would it make sense to have this in the image by >> default? On 27/10/14 13:07, stepharo wrote: > It depends: > - is it overriding? > - is it well packaged? > - is it cross cutting a lot? > I have been extremely careful to be as clean as possible. The stack trace catching is implemented with a PreDebuggingAction without overriding any of the existing code. It was one of my first design goals, especially because the purpose of the tool is to be completely pluggable and unpluggable without influencing the system. Also, we tested it for three months in daily development activities, so it is reasonably stable. We are analyzing the stack traces we collected so far to see if what useful information a developer can obtain from that. I would love to see ShoreLine Reporter used to help the development of the Pharo ecosystem and I would be glad to help if you think that such a tool could be useful if integrated into Pharo. Tommaso >> >> >> On Tue, Oct 7, 2014 at 6:23 PM, Tommaso Dal Sasso >> <tommaso.dalsasso(a)gmail.com <mailto:tommaso.dalsasso@gmail.com>> wrote: >> >> Hello everybody, >> >> for those of you who were not at ESUG, I present ShoreLine Reporter. >> >> ShoreLine Reporter is a Pharo plugin to collect stack traces from >> exceptions and send them to a central repository. >> You can give feedback to the community by breaking things: how >> cool is that? >> >> >> * Why? >> >> We are collecting stack traces for research purposes and to >> identify the Pharo components that can be improved or optimized. >> We are also working on a web platform where users can access the >> submitted data and use them during the debugging process. More on >> that soon! >> >> >> * How? >> >> You can install ShoreLine Reporter by visiting the project page >> on SmalltalkHub: >> http://www.smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter/ >> <http://www.smalltalkhub.com/#%21/%7Edalsat/ShoreLine-Reporter/> >> >> Installing ShoreLine Reporter requires only a couple of seconds, >> and you can configure it with the level of feedback that you >> prefer. On the SmalltalkHub page you can find a script to >> automatically install ShoreLine Reporter with every new Pharo >> image. Just drop it in your Pharo preferences directory and >> forget about it. >> >> Once ShoreLine Report is installed, you can decide to configure >> if you want to be prompted to submit a stack trace, or to >> automatically submit each exception without any bother. >> >> >> * What? >> >> We try to collect as few data as possible: the execution >> stacktrace, the name of the author and the Pharo build. We do >> *not* any collect personal data, such as passwords or >> repositories. The data is currently stored on our server, at the >> University of Lugano. >> >> >> * Compatibility >> >> ShoreLine Reporter is developed for the Pharo debugger. We are >> improving ShoreLine Reporter to work with GTInspector, we will >> push an update in the following days. >> >> >> For any problem, contact me! >> >> Thanks, hope to see a lot of your exceptions ;-) >> Tommaso Dal Sasso @ REVEAL >> >> >> >> >> -- >> -- >> Marcus Denker -- denker(a)acm.org <mailto:denker@acm.org> >> http://www.marcusdenker.de >

Oct. 28, 2014

Re: [Pharo-dev] [pharo-dev] image size, Ubuntu

by Pierre CHANSON

good ! I take a look, Andrei is in my office right now. Thanks, Pierre 2014-10-28 11:48 GMT-03:00 Max Leske <maxleske(a)gmail.com>: > > On 28.10.2014, at 15:13, Pierre CHANSON <chans.pierre(a)gmail.com> wrote: > > Sure, I would like to load more than a 100 moose model of Roassal2 package > in one hismo meta model. > > > You should DEFINITELY check out pangea if you havenât already: > http://scg.unibe.ch/research/pangea > Pangeaâs goal is to address exactly that problem. > > > Pierre > > 2014-10-28 10:34 GMT-03:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > >> May I ask why do you need such "big" size of memory? >> >> Regards, >> >> Esteban A. Maringolo >> >> 2014-10-28 10:26 GMT-03:00 Pierre CHANSON <chans.pierre(a)gmail.com>: >> >> all right... :( >>> thank you very much >>> >>> Pierre >>> >>> 2014-10-28 10:23 GMT-03:00 Max Leske <maxleske(a)gmail.com>: >>> >>> >>>> On 28.10.2014, at 13:57, Pierre CHANSON <chans.pierre(a)gmail.com> wrote: >>>> >>>> Thank you for your answer Max. >>>> >>>> But when I want to use more than 2000m memory for an image, it gave me >>>> an error saying "Insufficient memory for this image"... I thought >>>> "--memory" was some disk space I would allow the image to useâ¦ >>>> >>>> >>>> nope. ââmemoryâ is memory. And the VM canât allocat more than 2GB >>>> (usually). The image resides in memory during runtime and the disk has >>>> nothing to do with it. >>>> >>>> Max >>>> >>>> >>>> Pierre >>>> >>>> >>>> >>>> 2014-10-27 19:42 GMT-03:00 Max Leske <maxleske(a)gmail.com>: >>>> >>>>> >>>>> > On 27.10.2014, at 23:11, Pierre CHANSON <chans.pierre(a)gmail.com> >>>>> wrote: >>>>> > >>>>> > Hi ! >>>>> > >>>>> > anyone knows how to increase the disk allocation size for an image >>>>> on Ubuntu ? I can't find the command line for that. >>>>> >>>>> What do you mean by âdisk allocationâ? >>>>> >>>>> Hereâs the --help: >>>>> >>>>> ./pharo --help >>>>> Usage: [<option>...] [<imageName> [<argument>...]] >>>>> [<option>...] -- [<argument>...] >>>>> >>>>> Common <option>s: >>>>> --help print this help message, then exit >>>>> --memory <size>[mk] use fixed heap size (added to image size) >>>>> --headless run in headless (no window) mode (default: >>>>> false) >>>>> --nohandlers disable sigsegv & sigusr1 handlers >>>>> >>>>> Notes: >>>>> <imageName> defaults to `Pharo.image'. >>>>> If `--memory' is not specified then the heap will grow dynamically. >>>>> <argument>s are ignored, but are processed by the Squeak image. >>>>> The first <argument> normally names a Squeak `script' to execute. >>>>> Precede <arguments> by `--' to use default image. >>>>> >>>>> >>>>> You can set the memory for the VM with "--memory 2048mâ for instance. >>>>> >>>>> Cheers, >>>>> Max >>>>> >>>>> > >>>>> > Thanks !! >>>>> > >>>>> > Pierre Chanson >>>>> >>>>> >>>>> >>>> >>>> >>> >> > >

Oct. 28, 2014

Re: [Pharo-dev] [pharo-dev] image size, Ubuntu

by Max Leske

> On 28.10.2014, at 15:13, Pierre CHANSON <chans.pierre(a)gmail.com> wrote: > > Sure, I would like to load more than a 100 moose model of Roassal2 package in one hismo meta model. You should DEFINITELY check out pangea if you havenât already: http://scg.unibe.ch/research/pangea <http://scg.unibe.ch/research/pangea> Pangeaâs goal is to address exactly that problem. > > Pierre > > 2014-10-28 10:34 GMT-03:00 Esteban A. Maringolo <emaringolo(a)gmail.com <mailto:emaringolo@gmail.com>>: > May I ask why do you need such "big" size of memory? > > Regards, > > Esteban A. Maringolo > > 2014-10-28 10:26 GMT-03:00 Pierre CHANSON <chans.pierre(a)gmail.com <mailto:chans.pierre@gmail.com>>: > > all right... :( > thank you very much > > Pierre > > 2014-10-28 10:23 GMT-03:00 Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>>: > > >> On 28.10.2014, at 13:57, Pierre CHANSON <chans.pierre(a)gmail.com <mailto:chans.pierre@gmail.com>> wrote: >> >> Thank you for your answer Max. >> >> But when I want to use more than 2000m memory for an image, it gave me an error saying "Insufficient memory for this image"... I thought "--memory" was some disk space I would allow the image to useâ¦ > > nope. ââmemoryâ is memory. And the VM canât allocat more than 2GB (usually). The image resides in memory during runtime and the disk has nothing to do with it. > > Max > >> >> Pierre >> >> >> >> 2014-10-27 19:42 GMT-03:00 Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>>: >> >> > On 27.10.2014, at 23:11, Pierre CHANSON <chans.pierre(a)gmail.com <mailto:chans.pierre@gmail.com>> wrote: >> > >> > Hi ! >> > >> > anyone knows how to increase the disk allocation size for an image on Ubuntu ? I can't find the command line for that. >> >> What do you mean by âdisk allocationâ? >> >> Hereâs the --help: >> >> ./pharo --help >> Usage: [<option>...] [<imageName> [<argument>...]] >> [<option>...] -- [<argument>...] >> >> Common <option>s: >> --help print this help message, then exit >> --memory <size>[mk] use fixed heap size (added to image size) >> --headless run in headless (no window) mode (default: false) >> --nohandlers disable sigsegv & sigusr1 handlers >> >> Notes: >> <imageName> defaults to `Pharo.image'. >> If `--memory' is not specified then the heap will grow dynamically. >> <argument>s are ignored, but are processed by the Squeak image. >> The first <argument> normally names a Squeak `script' to execute. >> Precede <arguments> by `--' to use default image. >> >> >> You can set the memory for the VM with "--memory 2048mâ for instance. >> >> Cheers, >> Max >> >> > >> > Thanks !! >> > >> > Pierre Chanson >> >> >> > > > >

Oct. 28, 2014