- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Survey] Forking Operating System Proces in Pharo

by Mariano Martinez Peck

Dear all, This is a simple reminder in case someone missed it. I also wanted to thank everybody that already took the time for filling it! Very much appreciated. On Sat, Jan 2, 2016 at 10:44 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Dear all, > > As I mentioned in the thread "Pharo Consortium Sponsored Development > Effort" [1] I built a survey about Forking Operating System Processes in > Pharo. > > The idea of the survey is simple: I want to understand what people needs > the most, which features would be useful, which ones would not, what is > missing, what is wrong, etc etc etc. As always, since we have limited > resources, we should optimize them as much as possible. > > I count with you so that we can make a roadmap together on this project. > Please, feel free to forward this survey anywhere where there could be an > interest. > > https://www.surveymonkey.com/r/DHR22TL > > Best regards, > > [1] > http://forum.world.st/ANN-Pharo-Consortium-Sponsored-Development-Effort-td4… > > -- > Mariano > http://marianopeck.wordpress.com > -- Mariano http://marianopeck.wordpress.com

Jan. 12, 2016

Re: [Pharo-dev] How to get launcher launching Spur images?

by Ben Coman

On Tue, Jan 12, 2016 at 10:03 PM, stepharo <stepharo(a)free.fr> wrote: > I loaded the stable version in Pharo 50 and I saw that it does not have the > Spur special Folder. > So I loaded the latest version of the packages from the repo and I could not > run the launcher anymore. > > So could you tell me how you did it? Err, umm... looking just now I see only one settable VM path. So it seems I did not load the latest, only the version from the Catalog. So I guess I can only run Spur images. cheers -ben > > Stef > > Le 11/1/16 16:48, stepharo a Ã©crit : > > Ok I will do the same then ;) > > > Le 11/1/16 13:09, Ben Coman a Ã©crit : > > > On Mon, Jan 11, 2016 at 1:49 AM, stepharo <stepharo(a)free.fr> wrote: >> >> Hi >> >> I changed the setting to be the following but I cannot get a spur image >> started on mac. >> Does anybody succeed? >> >> Stef >> > > I cheated and started with latest Pharo 5 Spur and installed PharoLauncher > from the Catalog Browser. > (I should soon try an image with old vm) > cheers -ben > > >

Jan. 12, 2016

Re: [Pharo-dev] Morphic Migrations gotchas, was Re: Better class comment version2

by Thierry Goubier

2016-01-12 11:02 GMT+01:00 David Allouche <david(a)allouche.net>: > I wonder whether it would be worth reversing this change, to remove an > unnecessary incompatibility with other dialects. > > But maybe there is no development activity outside of Pharo, that would > justify making any effort to maintain compatibility. I do not know. > > Practicality beats purity, if cleaning up existing APIs means cutting out > Pharo from a wider ecosystem, and introducing painful bitrot, it might not > be worth the cost. > Hum. That change induced a lot of pain because touching Rectangle is very invasive (tend to crash the GUI), but I can't avoid thinking that places creating those strange rectangles were in fact bugs. For LayoutFrame, a simple refactoring when importing Morphic code would do the trick. In practice, a significant amount of code in Pharo 5 still creates wrong rectangles. A specific package even added an API to Rectangle to be able to do so. Thierry > > > On 11 Jan 2016, at 22:25, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > > And it probably won't be integrated in Squeak, because it's not worth the > pain. > > The change was conducted without analyzing all the impacts, because it was > probably not possible to analyze the huge code base. > (though it would have been possible to instrument code and collect the > sender stacks producing degenerated rectangles) > > The only motto was to make code more "pure". > Generally, I tend to be wary... > > On the other hand, storing the offsets in a rectangle just because there > are 4 edges is sort of hackish usage, so while at cleaning... > > 2016-01-11 9:42 GMT+01:00 Stephan Eggermont <stephan(a)stack.nl>: > >> On 10-01-16 23:16, Thierry Goubier wrote: >> >>> Hi David, >>> >>> this is the bug with LayoutFrame>>#fractions:offsets: we were talking >>> about relative to that class comment. >>> >>> In Pharo, Rectangles are constrained to have the smallest vertical value >>> as the top, smallest horizontal value as the left, largest vertical >>> value as bottom and largest horizontal value as right. >>> >> >> Indeed. And there is no Morphic documentation at all that is aware of >> that, as nearly all of it was written before we changed the behavior of >> Rectangle in Pharo, and it is a change that is not done in Squeak. The >> result is that nearly no old Morphic code will run unmodified in Pharo. >> >> I would like to collect a list of these gotchas, preferably with >> solutions, to make it easier for people to update/migrate old morphic code. >> Post them here, or mail them to me. >> >> Stephan >> >> >> >> >> > >

Jan. 12, 2016

Re: [Pharo-dev] Morphic Migrations gotchas, was Re: Better class comment version2

by Ben Coman

On Tue, Jan 12, 2016 at 6:02 PM, David Allouche <david(a)allouche.net> wrote: > I wonder whether it would be worth reversing this change, to remove an > unnecessary incompatibility with other dialects. Of course we should not introduce *unnecessary* incompatibilities, but its be hard to judge the subtle dampening effect of compatibility on innovation & API cleaning, against the benefits obtained from these. So Pharo tends to favour the latter over the former. Equally, mistakes sometimes aren't apparent until later, so no "improvement" should be treated as golden goose. I'm not qualified to have an opinion in this case, but I remember several people being quite pleased with the change. You'd probably have to clearly identify other benefits of reverting. (Compatibility with existing Morphic examples noted.) > But maybe there is no development activity outside of Pharo, that would > justify making any effort to maintain compatibility. I do not know. > Practicality beats purity, if cleaning up existing APIs means cutting out > Pharo from a wider ecosystem, and introducing painful bitrot, it might not > be worth the cost. You may find interesting the first three chapters... https://gforge.inria.fr/frs/download.php/30434/PharoVision.pdf cheers -ben > On 11 Jan 2016, at 22:25, Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > And it probably won't be integrated in Squeak, because it's not worth the > pain. > > The change was conducted without analyzing all the impacts, because it was > probably not possible to analyze the huge code base. > (though it would have been possible to instrument code and collect the > sender stacks producing degenerated rectangles) > > The only motto was to make code more "pure". > Generally, I tend to be wary... > > On the other hand, storing the offsets in a rectangle just because there are > 4 edges is sort of hackish usage, so while at cleaning... > > 2016-01-11 9:42 GMT+01:00 Stephan Eggermont <stephan(a)stack.nl>: >> >> On 10-01-16 23:16, Thierry Goubier wrote: >>> >>> Hi David, >>> >>> this is the bug with LayoutFrame>>#fractions:offsets: we were talking >>> about relative to that class comment. >>> >>> In Pharo, Rectangles are constrained to have the smallest vertical value >>> as the top, smallest horizontal value as the left, largest vertical >>> value as bottom and largest horizontal value as right. >> >> >> Indeed. And there is no Morphic documentation at all that is aware of >> that, as nearly all of it was written before we changed the behavior of >> Rectangle in Pharo, and it is a change that is not done in Squeak. The >> result is that nearly no old Morphic code will run unmodified in Pharo. >> >> I would like to collect a list of these gotchas, preferably with >> solutions, to make it easier for people to update/migrate old morphic code. >> Post them here, or mail them to me. >> >> Stephan >> >> >> >> > >

Jan. 12, 2016

Re: [Pharo-dev] How to get launcher launching Spur images?

by stepharo

I loaded the stable version in Pharo 50 and I saw that it does not have the Spur special Folder. So I loaded the latest version of the packages from the repo and I could not run the launcher anymore. So could you tell me how you did it? Stef Le 11/1/16 16:48, stepharo a Ã©crit : > Ok I will do the same then ;) > > > Le 11/1/16 13:09, Ben Coman a Ã©crit : >> >> On Mon, Jan 11, 2016 at 1:49 AM, stepharo <stepharo(a)free.fr >> <mailto:stepharo@free.fr>> wrote: >> >> Hi >> >> I changed the setting to be the following but I cannot get a spur >> image started on mac. >> Does anybody succeed? >> >> Stef >> >> >> I cheated and started with latest Pharo 5 Spur and installed >> PharoLauncher from the Catalog Browser. >> (I should soon try an image with old vm) >> cheers -ben >> >

Jan. 12, 2016

Re: [Pharo-dev] Test Runner: "Run Coverage" fails or hangs when multithreading is used in test.

by Jan Vrany

> Maybe it should only lock the threads that were _not_ started by the > âtest threadâ? Iâm not even sure that is possible, > just suggesting things. > Have a look at Niall Ross' XProc Patterns. They do the same by - AFAIK - intercepting process creation and checking whether the creating process is one of the "tests threads".Â HTH, Jan > > On Jan 12, 2016, at 11:11 AM, Sven Van Caekenberghe <sven(a)stfx.eu> > > wrote: > > > > The coverage seems to be implemented by 'locking' the current > > execution thread exclusively, which would mean no other threads can > > run, at all. So code depending on multi threading, like > > client/server code, like HTTP, cannot work. Yes that seems to be a > > limitation, but an understandable one. > > > > I am trying to help but I don't known anything about the coverage > > tool, so maybe I should shut up ;-) > > > > > On 12 Jan 2016, at 11:05, Skip Lentz <skip.lentz(a)inria.fr> wrote: > > > > > > You mean as in it can check the coverage effected by the code > > > running in the other thread? > > > Or is this not what you mean? > > > > > > Well I mean, at least it can show the coverage done by what was > > > run in the same thread.. > > > And it will at least not hang or fail. > > > > > > > On Jan 12, 2016, at 10:59 AM, Sven Van Caekenberghe <sven@stfx. > > > > eu> wrote: > > > > > > > > I never used that, but it seems coverage can only deal with > > > > single threaded code, which sounds logical. No ? > > > > > > > > > On 12 Jan 2016, at 10:53, Skip Lentz <skip.lentz(a)inria.fr> > > > > > wrote: > > > > > > > > > > Hi, > > > > > > > > > > When I want to run the coverage of for example Zincâs Client > > > > > and Server tests, > > > > > it will either hang (in the case of Zincâs test cases) or > > > > > fail because the coverage > > > > > uses BlockClosure>>valueUnpreemptively for running the tests. > > > > > The relevant method is TestRunner>>collectCoverageFor:. > > > > > > > > > > So when a test is run, it is not able to be preempted by > > > > > another process, like for > > > > > example a local server which is needed to run the actual test > > > > > in Zincâs case. > > > > > > > > > > When I use BlockClosure>>valueUninterruptably it works. Can > > > > > someone tell me > > > > > if it is wrong to use that instead? Is valueUnpreemptively > > > > > necessary in this case, > > > > > and if so, why? > > > > > > > > > > To reproduce: Load fresh image, select Zinc's ZnClientTests > > > > > and ZnServerTests, > > > > > click on âRun Coverageâ -> hanging image. > > > > > > > > > > Thanks, > > > > > > > > > > Skip > > > > > > > > > > > > > > > > > > > > >

Jan. 12, 2016

Re: [Pharo-dev] Pharo50 spur works on CentOS?

by Sven Van Caekenberghe

Ah yes, that is better, thanks! > On 12 Jan 2016, at 11:54, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > Agree. > I open a bug: https://pharo.fogbugz.com/f/cases/17378/Improve-command-line-handler-docume… that improve the doc. > I propose: > Usage: [--no-preferences|--preference-file=<FILE>][--help|--list|--copyright|--version|--no-quit|<subcommand> <subcommand args>] > --help print this help message > --list list a description of all active command line handlers > --copyright print the copyrights > --version print the version for the image and the vm > --no-quit keep the image running without activating any other command line handler > <subcommand> a valid subcommand in --list > <subcommand> --help show subcommand help > > Vincent > >> -----Message d'origine----- >> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de >> Sven Van Caekenberghe >> EnvoyÃ© : mardi 12 janvier 2016 11:48 >> Ã : Pharo Development List >> Objet : Re: [Pharo-dev] Pharo50 spur works on CentOS? >> >> No, I don't think so, it has a function. >> >> Some people like to configure Pharo images so that they have a running >> server inside them. In that case, starting your app is a simple as starting the >> image, but you would probably need the --no-quit to prevent it from exiting >> immediately. >> >> (I personally don't like and never use that approach, but I know some people >> like it). >> >> The confusing aspect is that the same option is used in two places and the >> first one annihilates the second. But that is documented: >> >> prometheus:pharo5 sven$ ./pharo Pharo.image --help >> Usage: [--no-preferences|--preference-file=<FILE>][<subcommand>] [-- >> help] [--copyright] [--version] [--list] [ --no-quit ] >> --help print this help message >> --copyright print the copyrights >> --version print the version for the image and the vm >> --list list a description of all active command line handlers >> --no-quit keep the image running without activating any other >> command line handler >> <subcommand> a valid subcommand in --list >> >> Documentation: >> A BasicCommandLineHandler handles default command line arguments and >> options. >> >> It clearly says "without activating any other command line handler". So using >> --no-quit BEFORE the subcommand annihilates the subcommand (AFAIU). >> >>> On 12 Jan 2016, at 11:28, Blondeau Vincent >> <vincent.blondeau(a)worldline.com> wrote: >>> >>> So --no-quit should be removed from the default line handler? >>> >>> Vincent >>> >>>> -----Message d'origine----- >>>> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part >>>> de Esteban Lorenzano EnvoyÃ© : mardi 12 janvier 2016 11:18 Ã : Pharo >>>> Development List Objet : Re: [Pharo-dev] Pharo50 spur works on >>>> CentOS? >>>> >>>> But you cannot use it as a general command. >>>> If you use a subcommand (most likely) then you do not have it unless >>>> the subcommand defines it. >>>> >>>> Esteban >>>> >>>>> On 12 Jan 2016, at 11:12, Blondeau Vincent >>>> <vincent.blondeau(a)worldline.com> wrote: >>>>> >>>>> >>>>> >>>>>> -----Message d'origine----- >>>>>> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la >>>>>> part de Sven Van Caekenberghe EnvoyÃ© : mardi 12 janvier 2016 10:57 Ã >> : >>>>>> Pharo Development List Objet : Re: [Pharo-dev] Pharo50 spur works >>>>>> on CentOS? >>>>>> >>>>>> >>>>>>>> On 12 Jan 2016, at 10:50, Esteban Lorenzano >> <estebanlm(a)gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On 12 Jan 2016, at 10:34, Sven Van Caekenberghe <sven(a)stfx.eu> >>>> wrote: >>>>>>>> >>>>>>>> >>>>>>>>> On 12 Jan 2016, at 10:28, Blondeau Vincent >>>>>> <vincent.blondeau(a)worldline.com> wrote: >>>>>>>>> >>>>>>>>> Indeed, it works. Thanks! >>>>>>>>> >>>>>>>>> But the command line usage is not clear : >>>>>>>>> ./pharo Pharo.image >>>>>>>>> Usage: [--no-preferences|--preference- >> file=<FILE>][<subcommand>] >>>>>>>>> [--help] [--copyright] [--version] [--list] [ --no-quit ] >>>>>>>>> >>>>>>>>> Maybe, it can be : >>>>>>>>> Usage: [--no-preferences|--preference- >> file=<FILE>][<subcommand>] >>>>>>>>> [--help] [--copyright] [--version] [--list] [ --no-quit ] >>>>>>>>> [<subcommand args>] >>>>>>>>> >>>>>>>>> Moreover, an option can usually be placed anywhere on the >>>>>>>>> command >>>>>> line, shouldn't it? Or at least it should raise an error? >>>>>>>> >>>>>>>> Yes it is a bit confusion (but you could try to read/understand >>>>>>>> the Pharo code, it is not very difficult ;-) >>>>>>>> >>>>>>>> But the idea is that the sub-command controls its own options >>>>>>>> (like passing linker options via the compiler to the linker - git >>>>>>>> also has global and per sub command options, no ?) >>>>>>>> >>>>>>>> --no-quit probably also works for the default command ... (I >>>>>>>> haven't >>>>>> looked), so at that point, the option is consumed already. >>>>>>> >>>>>>> No, it doesn't :) >>>>>> >>>>>> prometheus:pharo5 sven$ ./pharo Pharo.image printVersion [version] >>>>>> 5.0 >>>>>> #50510 >>>>>> prometheus:pharo5 sven$ ./pharo Pharo.image --no-quit ^C >>>>>> >>>>>> The last command 'hangs' (i.e. the image keeps running, just as >>>> advertised). >>>>>> So the default (Pharo, subclass of BasicCommandHandler) interpreted >>>>>> the -- no-quit and acted upon it. No ? >>>>> >>>>> Yes! See: BasicCommandLineHandler>>handleArgument: >>>>>> >>>>>>>> >>>>>>>>> Vincent >>> >>> >>> >>> Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage >> exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret >> professionnel. Si vous recevez ce message par erreur, merci d'en avertir >> immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne >> pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra >> Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs >> efforts soient faits pour maintenir cette transmission exempte de tout virus, >> l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne >> saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. >>> >>> This e-mail and the documents attached are confidential and intended >> solely for the addressee; it may also be privileged. If you receive this e-mail >> in error, please notify the sender immediately and destroy it. As its integrity >> cannot be secured on the Internet, the Worldline liability cannot be triggered >> for the message content. Although the sender endeavours to maintain a >> computer virus-free network, the sender does not warrant that this >> transmission is virus-free and will not be liable for any damages resulting >> from any virus transmitted. >> > > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Jan. 12, 2016

Re: [Pharo-dev] Pharo50 spur works on CentOS?

by Blondeau Vincent

Agree. I open a bug: https://pharo.fogbugz.com/f/cases/17378/Improve-command-line-handler-docume… that improve the doc. I propose: Usage: [--no-preferences|--preference-file=<FILE>][--help|--list|--copyright|--version|--no-quit|<subcommand> <subcommand args>] --help print this help message --list list a description of all active command line handlers --copyright print the copyrights --version print the version for the image and the vm --no-quit keep the image running without activating any other command line handler <subcommand> a valid subcommand in --list <subcommand> --help show subcommand help Vincent > -----Message d'origine----- > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de > Sven Van Caekenberghe > EnvoyÃ© : mardi 12 janvier 2016 11:48 > Ã : Pharo Development List > Objet : Re: [Pharo-dev] Pharo50 spur works on CentOS? > > No, I don't think so, it has a function. > > Some people like to configure Pharo images so that they have a running > server inside them. In that case, starting your app is a simple as starting the > image, but you would probably need the --no-quit to prevent it from exiting > immediately. > > (I personally don't like and never use that approach, but I know some people > like it). > > The confusing aspect is that the same option is used in two places and the > first one annihilates the second. But that is documented: > > prometheus:pharo5 sven$ ./pharo Pharo.image --help > Usage: [--no-preferences|--preference-file=<FILE>][<subcommand>] [-- > help] [--copyright] [--version] [--list] [ --no-quit ] > --help print this help message > --copyright print the copyrights > --version print the version for the image and the vm > --list list a description of all active command line handlers > --no-quit keep the image running without activating any other > command line handler > <subcommand> a valid subcommand in --list > > Documentation: > A BasicCommandLineHandler handles default command line arguments and > options. > > It clearly says "without activating any other command line handler". So using > --no-quit BEFORE the subcommand annihilates the subcommand (AFAIU). > > > On 12 Jan 2016, at 11:28, Blondeau Vincent > <vincent.blondeau(a)worldline.com> wrote: > > > > So --no-quit should be removed from the default line handler? > > > > Vincent > > > >> -----Message d'origine----- > >> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part > >> de Esteban Lorenzano EnvoyÃ© : mardi 12 janvier 2016 11:18 Ã : Pharo > >> Development List Objet : Re: [Pharo-dev] Pharo50 spur works on > >> CentOS? > >> > >> But you cannot use it as a general command. > >> If you use a subcommand (most likely) then you do not have it unless > >> the subcommand defines it. > >> > >> Esteban > >> > >>> On 12 Jan 2016, at 11:12, Blondeau Vincent > >> <vincent.blondeau(a)worldline.com> wrote: > >>> > >>> > >>> > >>>> -----Message d'origine----- > >>>> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la > >>>> part de Sven Van Caekenberghe EnvoyÃ© : mardi 12 janvier 2016 10:57 Ã > : > >>>> Pharo Development List Objet : Re: [Pharo-dev] Pharo50 spur works > >>>> on CentOS? > >>>> > >>>> > >>>>>> On 12 Jan 2016, at 10:50, Esteban Lorenzano > <estebanlm(a)gmail.com> > >>>>> wrote: > >>>>> > >>>>> > >>>>> > >>>>>> On 12 Jan 2016, at 10:34, Sven Van Caekenberghe <sven(a)stfx.eu> > >> wrote: > >>>>>> > >>>>>> > >>>>>>> On 12 Jan 2016, at 10:28, Blondeau Vincent > >>>> <vincent.blondeau(a)worldline.com> wrote: > >>>>>>> > >>>>>>> Indeed, it works. Thanks! > >>>>>>> > >>>>>>> But the command line usage is not clear : > >>>>>>> ./pharo Pharo.image > >>>>>>> Usage: [--no-preferences|--preference- > file=<FILE>][<subcommand>] > >>>>>>> [--help] [--copyright] [--version] [--list] [ --no-quit ] > >>>>>>> > >>>>>>> Maybe, it can be : > >>>>>>> Usage: [--no-preferences|--preference- > file=<FILE>][<subcommand>] > >>>>>>> [--help] [--copyright] [--version] [--list] [ --no-quit ] > >>>>>>> [<subcommand args>] > >>>>>>> > >>>>>>> Moreover, an option can usually be placed anywhere on the > >>>>>>> command > >>>> line, shouldn't it? Or at least it should raise an error? > >>>>>> > >>>>>> Yes it is a bit confusion (but you could try to read/understand > >>>>>> the Pharo code, it is not very difficult ;-) > >>>>>> > >>>>>> But the idea is that the sub-command controls its own options > >>>>>> (like passing linker options via the compiler to the linker - git > >>>>>> also has global and per sub command options, no ?) > >>>>>> > >>>>>> --no-quit probably also works for the default command ... (I > >>>>>> haven't > >>>> looked), so at that point, the option is consumed already. > >>>>> > >>>>> No, it doesn't :) > >>>> > >>>> prometheus:pharo5 sven$ ./pharo Pharo.image printVersion [version] > >>>> 5.0 > >>>> #50510 > >>>> prometheus:pharo5 sven$ ./pharo Pharo.image --no-quit ^C > >>>> > >>>> The last command 'hangs' (i.e. the image keeps running, just as > >> advertised). > >>>> So the default (Pharo, subclass of BasicCommandHandler) interpreted > >>>> the -- no-quit and acted upon it. No ? > >>> > >>> Yes! See: BasicCommandLineHandler>>handleArgument: > >>>> > >>>>>> > >>>>>>> Vincent > > > > > > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage > exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne > pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs > efforts soient faits pour maintenir cette transmission exempte de tout virus, > l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne > saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this e-mail > in error, please notify the sender immediately and destroy it. As its integrity > cannot be secured on the Internet, the Worldline liability cannot be triggered > for the message content. Although the sender endeavours to maintain a > computer virus-free network, the sender does not warrant that this > transmission is virus-free and will not be liable for any damages resulting > from any virus transmitted. > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Jan. 12, 2016

Re: [Pharo-dev] Pharo50 spur works on CentOS?

by Sven Van Caekenberghe

No, I don't think so, it has a function. Some people like to configure Pharo images so that they have a running server inside them. In that case, starting your app is a simple as starting the image, but you would probably need the --no-quit to prevent it from exiting immediately. (I personally don't like and never use that approach, but I know some people like it). The confusing aspect is that the same option is used in two places and the first one annihilates the second. But that is documented: prometheus:pharo5 sven$ ./pharo Pharo.image --help Usage: [--no-preferences|--preference-file=<FILE>][<subcommand>] [--help] [--copyright] [--version] [--list] [ --no-quit ] --help print this help message --copyright print the copyrights --version print the version for the image and the vm --list list a description of all active command line handlers --no-quit keep the image running without activating any other command line handler <subcommand> a valid subcommand in --list Documentation: A BasicCommandLineHandler handles default command line arguments and options. It clearly says "without activating any other command line handler". So using --no-quit BEFORE the subcommand annihilates the subcommand (AFAIU). > On 12 Jan 2016, at 11:28, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > So --no-quit should be removed from the default line handler? > > Vincent > >> -----Message d'origine----- >> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de >> Esteban Lorenzano >> EnvoyÃ© : mardi 12 janvier 2016 11:18 >> Ã : Pharo Development List >> Objet : Re: [Pharo-dev] Pharo50 spur works on CentOS? >> >> But you cannot use it as a general command. >> If you use a subcommand (most likely) then you do not have it unless the >> subcommand defines it. >> >> Esteban >> >>> On 12 Jan 2016, at 11:12, Blondeau Vincent >> <vincent.blondeau(a)worldline.com> wrote: >>> >>> >>> >>>> -----Message d'origine----- >>>> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part >>>> de Sven Van Caekenberghe EnvoyÃ© : mardi 12 janvier 2016 10:57 Ã : >>>> Pharo Development List Objet : Re: [Pharo-dev] Pharo50 spur works on >>>> CentOS? >>>> >>>> >>>>>> On 12 Jan 2016, at 10:50, Esteban Lorenzano <estebanlm(a)gmail.com> >>>>> wrote: >>>>> >>>>> >>>>> >>>>>> On 12 Jan 2016, at 10:34, Sven Van Caekenberghe <sven(a)stfx.eu> >> wrote: >>>>>> >>>>>> >>>>>>> On 12 Jan 2016, at 10:28, Blondeau Vincent >>>> <vincent.blondeau(a)worldline.com> wrote: >>>>>>> >>>>>>> Indeed, it works. Thanks! >>>>>>> >>>>>>> But the command line usage is not clear : >>>>>>> ./pharo Pharo.image >>>>>>> Usage: [--no-preferences|--preference-file=<FILE>][<subcommand>] >>>>>>> [--help] [--copyright] [--version] [--list] [ --no-quit ] >>>>>>> >>>>>>> Maybe, it can be : >>>>>>> Usage: [--no-preferences|--preference-file=<FILE>][<subcommand>] >>>>>>> [--help] [--copyright] [--version] [--list] [ --no-quit ] >>>>>>> [<subcommand args>] >>>>>>> >>>>>>> Moreover, an option can usually be placed anywhere on the command >>>> line, shouldn't it? Or at least it should raise an error? >>>>>> >>>>>> Yes it is a bit confusion (but you could try to read/understand the >>>>>> Pharo code, it is not very difficult ;-) >>>>>> >>>>>> But the idea is that the sub-command controls its own options (like >>>>>> passing linker options via the compiler to the linker - git also >>>>>> has global and per sub command options, no ?) >>>>>> >>>>>> --no-quit probably also works for the default command ... (I >>>>>> haven't >>>> looked), so at that point, the option is consumed already. >>>>> >>>>> No, it doesn't :) >>>> >>>> prometheus:pharo5 sven$ ./pharo Pharo.image printVersion [version] >>>> 5.0 >>>> #50510 >>>> prometheus:pharo5 sven$ ./pharo Pharo.image --no-quit ^C >>>> >>>> The last command 'hangs' (i.e. the image keeps running, just as >> advertised). >>>> So the default (Pharo, subclass of BasicCommandHandler) interpreted >>>> the -- no-quit and acted upon it. No ? >>> >>> Yes! See: BasicCommandLineHandler>>handleArgument: >>>> >>>>>> >>>>>>> Vincent > > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Jan. 12, 2016

Re: [Pharo-dev] Test Runner: "Run Coverage" fails or hangs when multithreading is used in test.

by Skip Lentz

Haha, donât worry. You donât have to shut up, in fact I thank you for replying. I donât know exactly how it has been implemented, I had a look see and it seems to be like this: It seems to collect all methods that will be checked for coverage, and then instantiate a wrapper around each one, and replace the method with the wrapper in the method dictionary of the class (and restore it afterwards, obviously). Maybe it should only lock the threads that were _not_ started by the âtest threadâ? Iâm not even sure that is possible, just suggesting things. > On Jan 12, 2016, at 11:11 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > The coverage seems to be implemented by 'locking' the current execution thread exclusively, which would mean no other threads can run, at all. So code depending on multi threading, like client/server code, like HTTP, cannot work. Yes that seems to be a limitation, but an understandable one. > > I am trying to help but I don't known anything about the coverage tool, so maybe I should shut up ;-) > >> On 12 Jan 2016, at 11:05, Skip Lentz <skip.lentz(a)inria.fr> wrote: >> >> You mean as in it can check the coverage effected by the code running in the other thread? >> Or is this not what you mean? >> >> Well I mean, at least it can show the coverage done by what was run in the same thread.. >> And it will at least not hang or fail. >> >>> On Jan 12, 2016, at 10:59 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> I never used that, but it seems coverage can only deal with single threaded code, which sounds logical. No ? >>> >>>> On 12 Jan 2016, at 10:53, Skip Lentz <skip.lentz(a)inria.fr> wrote: >>>> >>>> Hi, >>>> >>>> When I want to run the coverage of for example Zincâs Client and Server tests, >>>> it will either hang (in the case of Zincâs test cases) or fail because the coverage >>>> uses BlockClosure>>valueUnpreemptively for running the tests. >>>> The relevant method is TestRunner>>collectCoverageFor:. >>>> >>>> So when a test is run, it is not able to be preempted by another process, like for >>>> example a local server which is needed to run the actual test in Zincâs case. >>>> >>>> When I use BlockClosure>>valueUninterruptably it works. Can someone tell me >>>> if it is wrong to use that instead? Is valueUnpreemptively necessary in this case, >>>> and if so, why? >>>> >>>> To reproduce: Load fresh image, select Zinc's ZnClientTests and ZnServerTests, >>>> click on âRun Coverageâ -> hanging image. >>>> >>>> Thanks, >>>> >>>> Skip >>> >>> >> >> > >

Jan. 12, 2016