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

Re: [Pharo-dev] Never-ending computations and cmd-dot

by HernÃ¡n Morales Durand

Hi Tim, Yes, I am aware of such menu item. However I would like to know if someone is working in a more architectural solution. Because I guess this would imply to hook message sends into the main feedback loop. Cheers, HernÃ¡n 2017-09-25 20:08 GMT-03:00 Tim Mackinnon <tim(a)testit.works>: > Its not quite what you are asking for, but if you right click on one of those windows, someone has helpfully added a âclose all windows to rightâ option, which does let you rapidly get rid of them. > > Tim > >> On 25 Sep 2017, at 23:16, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >> >> Hi, >> >> Guys I have the situation you will recognize in the attached picture: >> A never-ending recursive computation which generate zillions of >> pre-debug windows when cmd-dot key is pressed. >> >> Is there any setting, or any way to put a monitor to detect that >> cmd-dot is creating too many windows so will pop-up just one or two? >> Maybe someone researched this issue, does it makes sense? >> >> Cheers, >> >> HernÃ¡n >> <rw.png> > >

Sept. 26, 2017

Re: [Pharo-dev] XPath chapter...

by Sean P. DeNigris

ghoetker wrote > Thank you, Stef, for providing this (and all else you do). As a very new > user, I agree completely with your comment about the importance of > documentation. +100!!! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 26, 2017

Re: [Pharo-dev] [Ann] Class meta annotations

by Sean P. DeNigris

Denis Kudriashov wrote > Also I would like to thank Marcus who helps me realize this concept in > Commander and Calypso which I start simplify with this library. Embarrassingly, I'm not quite clear on what this all means so I'll be eager to hear the results of the case study with Commander and Calypso! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 26, 2017

Re: [Pharo-dev] Never-ending computations and cmd-dot

by Tim Mackinnon

Its not quite what you are asking for, but if you right click on one of those windows, someone has helpfully added a âclose all windows to rightâ option, which does let you rapidly get rid of them. Tim > On 25 Sep 2017, at 23:16, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Hi, > > Guys I have the situation you will recognize in the attached picture: > A never-ending recursive computation which generate zillions of > pre-debug windows when cmd-dot key is pressed. > > Is there any setting, or any way to put a monitor to detect that > cmd-dot is creating too many windows so will pop-up just one or two? > Maybe someone researched this issue, does it makes sense? > > Cheers, > > HernÃ¡n > <rw.png>

Sept. 25, 2017

Re: [Pharo-dev] Never-ending computations and cmd-dot

by Esteban A. Maringolo

I think the problem doesn't come from a lot of Ctrl+., but for another unhandled exception. I've been bitten by that from time to time, usually in the context of a MessageNotUnderstood exception that gets recursive. Regards, Esteban A. Maringolo 2017-09-25 19:16 GMT-03:00 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: > Hi, > > Guys I have the situation you will recognize in the attached picture: > A never-ending recursive computation which generate zillions of > pre-debug windows when cmd-dot key is pressed. > > Is there any setting, or any way to put a monitor to detect that > cmd-dot is creating too many windows so will pop-up just one or two? > Maybe someone researched this issue, does it makes sense? > > Cheers, > > HernÃ¡n

Sept. 25, 2017

Never-ending computations and cmd-dot

by HernÃ¡n Morales Durand

Hi, Guys I have the situation you will recognize in the attached picture: A never-ending recursive computation which generate zillions of pre-debug windows when cmd-dot key is pressed. Is there any setting, or any way to put a monitor to detect that cmd-dot is creating too many windows so will pop-up just one or two? Maybe someone researched this issue, does it makes sense? Cheers, HernÃ¡n

Sept. 25, 2017

Re: [Pharo-dev] slow Pharo downloading and Travis

by Gabriel Cotelli

Still really slow from Argentina. In case it helps traceroute files.pharo.org traceroute to files.pharo.org (128.93.162.72), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 0.574 ms 0.968 ms 1.538 ms 2 192.168.0.1 (192.168.0.1) 2.048 ms 2.499 ms 2.847 ms 3 10.33.32.1 (10.33.32.1) 12.264 ms 14.160 ms 14.336 ms 4 10.242.2.161 (10.242.2.161) 14.522 ms 14.643 ms 16.497 ms 5 telecentro.baires3.bai.seabone.net (195.22.220.33) 18.936 ms 19.575 ms 18.843 ms 6 ae0.baires3.bai.seabone.net (195.22.220.32) 19.554 ms 10.675 ms 13.028 ms 7 et10-1-0.miami15.mia.seabone.net (89.221.41.175) 246.284 ms et9-3-0.miami15.mia.seabone.net (195.22.199.179) 246.214 ms et4-3-0.miami15.mia.seabone.net (195.22.199.177) 246.137 ms 8 gtt.miami15.mia.seabone.net (89.221.41.197) 245.909 ms 245.924 ms 245.870 ms 9 xe-3-1-2.cr0-par7.ip4.gtt.net (141.136.109.18) 251.632 ms 274.447 ms 250.097 ms 10 renater-gw-ix1.gtt.net (77.67.123.206) 281.025 ms 259.509 ms 261.717 ms 11 * * * 12 inria-rocquencourt-te1-4-inria-rtr-021.noc.renater.fr (193.51.184.177) 271.263 ms 307.011 ms 306.876 ms 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * httping -g http://files.pharo.org/get-files/61/pharo64.zip -c 20 PING files.pharo.org:80 (/get-files/61/pharo64.zip): connected to 128.93.162.72:80 (256 bytes), seq=0 time=625,90 ms connected to 128.93.162.72:80 (256 bytes), seq=1 time=842,02 ms connected to 128.93.162.72:80 (256 bytes), seq=2 time=638,83 ms connected to 128.93.162.72:80 (256 bytes), seq=3 time=637,63 ms connected to 128.93.162.72:80 (256 bytes), seq=4 time=637,85 ms connected to 128.93.162.72:80 (256 bytes), seq=5 time=580,27 ms connected to 128.93.162.72:80 (256 bytes), seq=6 time=1207,98 ms connected to 128.93.162.72:80 (256 bytes), seq=7 time=638,13 ms connected to 128.93.162.72:80 (256 bytes), seq=8 time=637,74 ms connected to 128.93.162.72:80 (256 bytes), seq=9 time=582,59 ms connected to 128.93.162.72:80 (256 bytes), seq=10 time=658,11 ms connected to 128.93.162.72:80 (256 bytes), seq=11 time=673,84 ms connected to 128.93.162.72:80 (256 bytes), seq=12 time=584,44 ms connected to 128.93.162.72:80 (256 bytes), seq=13 time=691,84 ms connected to 128.93.162.72:80 (256 bytes), seq=14 time=637,20 ms connected to 128.93.162.72:80 (256 bytes), seq=15 time=861,84 ms connected to 128.93.162.72:80 (256 bytes), seq=16 time=619,45 ms connected to 128.93.162.72:80 (256 bytes), seq=17 time=638,03 ms connected to 128.93.162.72:80 (256 bytes), seq=18 time=638,11 ms connected to 128.93.162.72:80 (256 bytes), seq=19 time=741,01 ms --- http://files.pharo.org/get-files/61/pharo64.zip ping statistics --- 20 connects, 20 ok, 0,00% failed, time 33781ms round-trip min/avg/max = 580,3/688,6/1208,0 ms On Thu, Sep 21, 2017 at 12:13 PM, Ben Coman <btc(a)openinworld.com> wrote: > Still seems a bit slow... > http://files.pharo.org/get-files/70/pharo64.zip > 16MB ==> 10 minutes (and actually it stalled after 3.4MB downloaded) > Local speed test: 40Mb/s down, 20Mb/s up > > but then I'm a long way across the internet, the cause could be anywhere... > $ traceroute files.pharo.org > traceroute to files.pharo.org (128.93.162.72), 30 hops max, 60 byte > packets > 1 192.168.43.1 (192.168.43.1) 2.040 ms 2.403 ms 4.222 ms > 2 * * * > 3 * * * > 4 Bundle-Ether14.wel-edge901.perth.telstra.net (139.130.16.49) 67.741 > ms 67.739 ms 67.730 ms > 5 bundle-ether6.wel-core3.perth.telstra.net (203.50.6.214) 67.696 ms > 67.697 ms 67.697 ms > 6 bundle-ether7.fli-core1.adelaide.telstra.net (203.50.11.18) 95.723 > ms 91.753 ms 100.574 ms > 7 bundle-ether9.win-core10.melbourne.telstra.net (203.50.11.91) > 106.550 ms 108.849 ms 108.851 ms > 8 bundle-ether12.ken-core10.sydney.telstra.net (203.50.11.122) 117.770 > ms 117.767 ms 117.751 ms > 9 bundle-ether1.pad-gw11.sydney.telstra.net (203.50.6.61) 117.720 ms > 103.603 ms 102.171 ms > 10 bundle-ether1.sydp-core04.sydney.reach.com (203.50.13.90) 93.276 ms > 95.822 ms 102.577 ms > 11 i-52.tlot-core02.bx.telstraglobal.net (202.84.137.101) 330.128 ms > 321.231 ms 322.522 ms > 12 i-0-4-0-10.tlot-core01.bi.telstraglobal.net (202.84.253.21) 321.187 > ms i-0-2-0-10.tlot-core01.bi.telstraglobal.net (202.40.149.181) 321.181 > ms i-0-2-0-9.tlot-core01.bi.telstraglobal.net (202.40.149.177) 308.786 ms > 13 gtt-peer.tlot02.pr.telstraglobal.net (134.159.63.182) 273.784 ms > 283.530 ms 281.079 ms > 14 xe-1-2-0.cr0-par7.ip4.gtt.net (89.149.185.53) 466.648 ms 479.910 ms > 481.254 ms > 15 renater-gw-ix1.gtt.net (77.67.123.206) 479.900 ms 479.882 ms > 478.641 ms > 16 * * * > 17 inria-rocquencourt-te1-4-inria-rtr-021.noc.renater.fr > (193.51.184.177) 436.776 ms 479.819 ms 478.907 ms > 18 * * * > 19 * * * > > $ httping -h files.pharo.org > PING files.pharo.org:80 (http://files.pharo.org:80/) > connected to 128.93.162.72:80 (169 bytes), seq=0 time=970.27 ms > connected to 128.93.162.72:80 (169 bytes), seq=1 time=928.26 ms > connected to 128.93.162.72:80 (169 bytes), seq=2 time=860.06 ms > connected to 128.93.162.72:80 (169 bytes), seq=3 time=976.04 ms > connected to 128.93.162.72:80 (169 bytes), seq=4 time=1238.72 ms > connected to 128.93.162.72:80 (169 bytes), seq=5 time=1239.65 ms > connected to 128.93.162.72:80 (169 bytes), seq=6 time=918.06 ms > > > cheers -ben > > On Thu, Sep 21, 2017 at 5:43 PM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >> >> > On 18 Sep 2017, at 08:37, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> > >> > >> >> On 16 Sep 2017, at 09:40, Stephane Ducasse <stepharo.self(a)gmail.com> >> wrote: >> >> >> >> Hi marcus >> >> >> >> I do not see why they could not find it. >> >> Can you tell me how you ask because we should reask? >> >> >> >> >> > >> > I spend a ticket and they wanted to close it last week. I have told >> them to not close it >> > >> The problems seems to be fixed now. >> >> If someone sees any slowness -> send me a mail. >> >> Marcus >> >> >> >

Sept. 25, 2017

Re: [Pharo-dev] Class side method is missing in obsolete class after the class is removed from system

by NicolÃ¡s Papagna Maldonado

Thanks Stef! I tried creating classes using SystemAnnouncer uniqueInstance suspendAllWhile: but this skips all subscribers, not only ChangeSet. That means that, say, RPackageTag instances won't contain the new class. Will use a workaround for now, as this is not the core of the thing im working on. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 25, 2017

Re: [Pharo-dev] [Ann] Class meta annotations

by Denis Kudriashov

I also realized that this library automatically adds annotations to packages because we are now able annotate manifest classes 2017-09-25 17:01 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > Hi. > > I glad to present one class package which introduces reusable mechanism > for first class annotations. > > The project can be found on github https://github.com/ > dionisiydk/ClassMetaAnnotation. > And I tried to describe why it is needed in my blog > http://dionisiydk.blogspot.fr/2017/09/class-meta-annotations.html. > > And here is overview: > > Every annotation should be subclass of ClassMetaAnnotation. To attach it > to class you create new class side method which will return an instance of > the annotation. Method should be marked with pragma #classMetaAnnotation: > > > MyClass class>>specialAnnotation > > <classMetaAnnotation> > > ^MySpecialAnnotation new > > > To query annotations from system there are two methods: > > 1) You can ask concrete annotation class for all declared instances: > > MySpecialAnnotation declaredInstances > > 2) You can ask given class for all attached annotations: > > MyClass metaAnnotations > > Every annotation includes information about annotated class and the > selector of declaring method. > All annotations are cached. So it is cheap to query them. There are extra > messages to enumerate annotations using block. > > Now let's discuss it. I think it can be good addition for the Pharo 7. > Especially that it is very small code. > > Also I would like to thank Marcus who helps me realize this concept in > Commander and Calypso which I start simplify with this library. > > Best regards, > Denis >

Sept. 25, 2017

Re: [Pharo-dev] [Ann] Class meta annotations

by Marcus Denker

> On 25 Sep 2017, at 17:38, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > I agree with guille. We should just called them class annotations. > The problem that I see is that people will confuse them with per class properties (and pragmas, should we add them). If I hear âclass annotationâ I think that this is something visible in the class definition pane. But I have no strong opinion, that is, if everyone else thinks the name is good I am ok with it. Marcus

Sept. 25, 2017