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

Re: [Pharo-dev] Spec #subMenu is broken

by Pharo4Stef

Hi ben where? because I wanted to integrate it and I could not find the slice in the inbox. did you fix also the menu title rendering (when putting a title it was not used and rendered) because I was hacking a solution in the âMenuAdapterâ but I do not remember where I put the code. I will dig the code and publish it, if it is not fixed. Stef > I proposed a new update for Spec with this fix in it :) > > Ben > > On 04 Mar 2014, at 18:38, roberto.minelli(a)usi.ch wrote: > >> Cool Ben! >> >> P.s. Should I wait until the fix will be integrated in Pharo? >> >> Cheers, >> R >> >> On Mar 4, 2014, at 5:13 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> >>> Thanks for the report :) >>> >>> Fixed in commit df6e44a :) >>> >>> Ben >>> >>> On 04 Mar 2014, at 16:57, roberto.minelli(a)usi.ch wrote: >>> >>>> Hi, >>>> >>>> It seems that Specâs #subMenu functionality is broken. >>>> >>>> I opened an entry here: https://pharo.fogbugz.com/f/cases/13039/Spec-s-subMenu-is-broken >>>> >>>> Cheers, >>>> RM >>> >> >> >

March 5, 2014

files.pharo.org/platform - why empty

by Torsten Bergmann

The folder http://files.pharo.org/platform/ is empty for whatever reason. If this is by intention I dont think this is a good idea - as the URL is referred to in many posts, wesbites and blog entries to easy download a one click for platforms. Thx T.

March 5, 2014

Re: [Pharo-dev] Spec #subMenu is broken

by Benjamin

I proposed a new update for Spec with this fix in it :) Ben On 04 Mar 2014, at 18:38, roberto.minelli(a)usi.ch wrote: > Cool Ben! > > P.s. Should I wait until the fix will be integrated in Pharo? > > Cheers, > R > > On Mar 4, 2014, at 5:13 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >> Thanks for the report :) >> >> Fixed in commit df6e44a :) >> >> Ben >> >> On 04 Mar 2014, at 16:57, roberto.minelli(a)usi.ch wrote: >> >>> Hi, >>> >>> It seems that Specâs #subMenu functionality is broken. >>> >>> I opened an entry here: https://pharo.fogbugz.com/f/cases/13039/Spec-s-subMenu-is-broken >>> >>> Cheers, >>> RM >> > >

March 4, 2014

Re: [Pharo-dev] strange time / delay problems on pharo-contribution-linux64-4.ci.inria.fr

by Eliot Miranda

On Tue, Mar 4, 2014 at 2:37 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 04 Mar 2014, at 22:34, Max Leske <maxleske(a)gmail.com> wrote: > > > Phew! I already thought I was crazy :) > > > > In that case here are two more tidbits: > > - I tried to log 'DateAndTime now' in a different test simultaneously. > The timestamp produced there was different, suggesting that the clock does > move from time to time. > > - FileSystemTests>>testEntryAt exhibits that problem. But the tests run > on the main Pharo machines are fine (that's why I thought it might be the > system clock). > > - the same test only fails in the Pharo3 image, not in Pharo2, but both > use the stable PharoVM for building. > > There is a big difference in how DateAndTime class>>#now works in 2.0 vs > 3.0. The former uses #millisecondClockValue while the latter uses > #microsecondClockValue. Furthermore 2.0 does all kind of crazy stuff with a > loop and Delays to try to improve the accuracy, we threw all that out. > > Yeah, I guess the clock is just being updated slowly, maybe under heavy > load. The question is where that happens. I think in the virtualised OS. > That makes sense. In the VM the microsecond clock is updated on every heartbeat and the heartbeat should be running at about 500Hz. Can anyone with hardware confirm that in 3.0 the time on linux does indeed increase at about 500Hz? Note that even in 2.0 the time is being derived from the same basis. In Cog, the effective time basis is the 64-bit microsecond clock maintained by the heartbeat and even the secondClock and millisecondClock are derived from this. So its still confusing why there should be such a difference between 2.0 and 3.0. > > > Hope that helps. > > > > On 04.03.2014, at 22:10, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > >> Hey Max, > >> > >> Great catch, I saw some weird stuff too, and we had this conversation : > >> > >>> may be just = > >>> and time does not pass fast enough/ > >>> > >>>> On 03 Mar 2014, at 22:22, no-reply(a)ci.inria.fr wrote: > >>>> > >>>>> > https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation-A-L/labe… > >>>>> > >>>>> 1 regressions found. > >>>>> KernelTests.Chronology.DateAndTimeTest.testMonotonicity > >>>> > >>>> How the hell can this fail ? > >>>> The clock moving backwards ?? > >>>> > >>>> testMonotonicity > >>>> > >>>> | t1 t2 t3 t4 | > >>>> t1 := DateAndTime now. > >>>> t2 := DateAndTime now. > >>>> (Delay forMilliseconds: 1000) wait. > >>>> t3 := DateAndTime now. > >>>> t4 := DateAndTime now. > >>>> > >>>> self > >>>> assert: (t1 <= t2); > >>>> assert: (t2 < t3); > >>>> assert: (t3 <= t4). > >> > >> > >> So you proofed Stef's assumption of time standing still ;-) > >> > >> But there were earlier problems as well. > >> > >> Thx ! > >> > >> On 04 Mar 2014, at 21:43, Max Leske <maxleske(a)gmail.com> wrote: > >> > >>> There seems to be a problem on > pharo-contribution-linux64-4.ci.inria.fr AFAICT. I can reproduce the > following to phenomena: > >>> > >>> 1. '(Delay forSeconds: 10) wait' does not wait. > >>> 2. 'DateAndTime now' does not change for long intervals. > >>> > >>> For instance, the following code: > >>> > >>> (FileSystem disk workingDirectory / 'foo.log') writeStreamDo: [ > :stream | > >>> stream nextPutAll: DateAndTime now asString;crlf. > >>> stream nextPutAll: ([(Delay forSeconds: 10) wait] timeToRun / > 1000) asString; crlf. > >>> stream nextPutAll: DateAndTime now asString ]. > >>> > >>> produces this output: > >>> > >>> 2014-03-04T21:32:21.396669+01:00 > >>> 0:00:00:00 > >>> 2014-03-04T21:32:21.396669+01:00 > >>> > >>> Too me (and my untrained eye) this looks like a system clock problem. > Could somebode take a look at the server in question? > >>> > >>> Cheers, > >>> Max > >> > >> > > > > > > > -- best, Eliot

March 4, 2014

Re: [Pharo-dev] strange time / delay problems on pharo-contribution-linux64-4.ci.inria.fr

by Sven Van Caekenberghe

On 04 Mar 2014, at 22:34, Max Leske <maxleske(a)gmail.com> wrote: > Phew! I already thought I was crazy :) > > In that case here are two more tidbits: > - I tried to log âDateAndTime nowâ in a different test simultaneously. The timestamp produced there was different, suggesting that the clock does move from time to time. > - FileSystemTests>>testEntryAt exhibits that problem. But the tests run on the main Pharo machines are fine (thatâs why I thought it might be the system clock). > - the same test only fails in the Pharo3 image, not in Pharo2, but both use the stable PharoVM for building. There is a big difference in how DateAndTime class>>#now works in 2.0 vs 3.0. The former uses #millisecondClockValue while the latter uses #microsecondClockValue. Furthermore 2.0 does all kind of crazy stuff with a loop and Delays to try to improve the accuracy, we threw all that out. Yeah, I guess the clock is just being updated slowly, maybe under heavy load. The question is where that happens. I think in the virtualised OS. > Hope that helps. > > On 04.03.2014, at 22:10, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> Hey Max, >> >> Great catch, I saw some weird stuff too, and we had this conversation : >> >>> may be just = >>> and time does not pass fast enough/ >>> >>>> On 03 Mar 2014, at 22:22, no-reply(a)ci.inria.fr wrote: >>>> >>>>> https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation-A-L/labe… >>>>> >>>>> 1 regressions found. >>>>> KernelTests.Chronology.DateAndTimeTest.testMonotonicity >>>> >>>> How the hell can this fail ? >>>> The clock moving backwards ?? >>>> >>>> testMonotonicity >>>> >>>> | t1 t2 t3 t4 | >>>> t1 := DateAndTime now. >>>> t2 := DateAndTime now. >>>> (Delay forMilliseconds: 1000) wait. >>>> t3 := DateAndTime now. >>>> t4 := DateAndTime now. >>>> >>>> self >>>> assert: (t1 <= t2); >>>> assert: (t2 < t3); >>>> assert: (t3 <= t4). >> >> >> So you proofed Stef's assumption of time standing still ;-) >> >> But there were earlier problems as well. >> >> Thx ! >> >> On 04 Mar 2014, at 21:43, Max Leske <maxleske(a)gmail.com> wrote: >> >>> There seems to be a problem on pharo-contribution-linux64-4.ci.inria.fr AFAICT. I can reproduce the following to phenomena: >>> >>> 1. '(Delay forSeconds: 10) waitâ does not wait. >>> 2. âDateAndTime nowâ does not change for long intervals. >>> >>> For instance, the following code: >>> >>> (FileSystem disk workingDirectory / 'foo.log') writeStreamDo: [ :stream | >>> stream nextPutAll: DateAndTime now asString;crlf. >>> stream nextPutAll: ([(Delay forSeconds: 10) wait] timeToRun / 1000) asString; crlf. >>> stream nextPutAll: DateAndTime now asString ]. >>> >>> produces this output: >>> >>> 2014-03-04T21:32:21.396669+01:00 >>> 0:00:00:00 >>> 2014-03-04T21:32:21.396669+01:00 >>> >>> Too me (and my untrained eye) this looks like a system clock problem. Could somebode take a look at the server in question? >>> >>> Cheers, >>> Max >> >> > >

March 4, 2014

Re: [Pharo-dev] strange time / delay problems on pharo-contribution-linux64-4.ci.inria.fr

by Max Leske

Phew! I already thought I was crazy :) In that case here are two more tidbits: - I tried to log âDateAndTime nowâ in a different test simultaneously. The timestamp produced there was different, suggesting that the clock does move from time to time. - FileSystemTests>>testEntryAt exhibits that problem. But the tests run on the main Pharo machines are fine (thatâs why I thought it might be the system clock). - the same test only fails in the Pharo3 image, not in Pharo2, but both use the stable PharoVM for building. Hope that helps. On 04.03.2014, at 22:10, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hey Max, > > Great catch, I saw some weird stuff too, and we had this conversation : > >> may be just = >> and time does not pass fast enough/ >> >>> On 03 Mar 2014, at 22:22, no-reply(a)ci.inria.fr wrote: >>> >>>> https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation-A-L/labe… >>>> >>>> 1 regressions found. >>>> KernelTests.Chronology.DateAndTimeTest.testMonotonicity >>> >>> How the hell can this fail ? >>> The clock moving backwards ?? >>> >>> testMonotonicity >>> >>> | t1 t2 t3 t4 | >>> t1 := DateAndTime now. >>> t2 := DateAndTime now. >>> (Delay forMilliseconds: 1000) wait. >>> t3 := DateAndTime now. >>> t4 := DateAndTime now. >>> >>> self >>> assert: (t1 <= t2); >>> assert: (t2 < t3); >>> assert: (t3 <= t4). > > > So you proofed Stef's assumption of time standing still ;-) > > But there were earlier problems as well. > > Thx ! > > On 04 Mar 2014, at 21:43, Max Leske <maxleske(a)gmail.com> wrote: > >> There seems to be a problem on pharo-contribution-linux64-4.ci.inria.fr AFAICT. I can reproduce the following to phenomena: >> >> 1. '(Delay forSeconds: 10) waitâ does not wait. >> 2. âDateAndTime nowâ does not change for long intervals. >> >> For instance, the following code: >> >> (FileSystem disk workingDirectory / 'foo.log') writeStreamDo: [ :stream | >> stream nextPutAll: DateAndTime now asString;crlf. >> stream nextPutAll: ([(Delay forSeconds: 10) wait] timeToRun / 1000) asString; crlf. >> stream nextPutAll: DateAndTime now asString ]. >> >> produces this output: >> >> 2014-03-04T21:32:21.396669+01:00 >> 0:00:00:00 >> 2014-03-04T21:32:21.396669+01:00 >> >> Too me (and my untrained eye) this looks like a system clock problem. Could somebode take a look at the server in question? >> >> Cheers, >> Max > >

March 4, 2014

Re: [Pharo-dev] strange time / delay problems on pharo-contribution-linux64-4.ci.inria.fr

by Sven Van Caekenberghe

Hey Max, Great catch, I saw some weird stuff too, and we had this conversation : > may be just = > and time does not pass fast enough/ > >> On 03 Mar 2014, at 22:22, no-reply(a)ci.inria.fr wrote: >> >>> https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation-A-L/labe… >>> >>> 1 regressions found. >>> KernelTests.Chronology.DateAndTimeTest.testMonotonicity >> >> How the hell can this fail ? >> The clock moving backwards ?? >> >> testMonotonicity >> >> | t1 t2 t3 t4 | >> t1 := DateAndTime now. >> t2 := DateAndTime now. >> (Delay forMilliseconds: 1000) wait. >> t3 := DateAndTime now. >> t4 := DateAndTime now. >> >> self >> assert: (t1 <= t2); >> assert: (t2 < t3); >> assert: (t3 <= t4). So you proofed Stef's assumption of time standing still ;-) But there were earlier problems as well. Thx ! On 04 Mar 2014, at 21:43, Max Leske <maxleske(a)gmail.com> wrote: > There seems to be a problem on pharo-contribution-linux64-4.ci.inria.fr AFAICT. I can reproduce the following to phenomena: > > 1. '(Delay forSeconds: 10) waitâ does not wait. > 2. âDateAndTime nowâ does not change for long intervals. > > For instance, the following code: > > (FileSystem disk workingDirectory / 'foo.log') writeStreamDo: [ :stream | > stream nextPutAll: DateAndTime now asString;crlf. > stream nextPutAll: ([(Delay forSeconds: 10) wait] timeToRun / 1000) asString; crlf. > stream nextPutAll: DateAndTime now asString ]. > > produces this output: > > 2014-03-04T21:32:21.396669+01:00 > 0:00:00:00 > 2014-03-04T21:32:21.396669+01:00 > > Too me (and my untrained eye) this looks like a system clock problem. Could somebode take a look at the server in question? > > Cheers, > Max

March 4, 2014

strange time / delay problems on pharo-contribution-linux64-4.ci.inria.fr

by Max Leske

There seems to be a problem on pharo-contribution-linux64-4.ci.inria.fr AFAICT. I can reproduce the following to phenomena: 1. '(Delay forSeconds: 10) waitâ does not wait. 2. âDateAndTime nowâ does not change for long intervals. For instance, the following code: (FileSystem disk workingDirectory / 'foo.log') writeStreamDo: [ :stream | stream nextPutAll: DateAndTime now asString;crlf. stream nextPutAll: ([(Delay forSeconds: 10) wait] timeToRun / 1000) asString; crlf. stream nextPutAll: DateAndTime now asString ]. produces this output: 2014-03-04T21:32:21.396669+01:00 0:00:00:00 2014-03-04T21:32:21.396669+01:00 Too me (and my untrained eye) this looks like a system clock problem. Could somebode take a look at the server in question? Cheers, Max

March 4, 2014

Re: [Pharo-dev] ConfigurationOf and github

by Sebastian Sastre

that clarified all thanks Thierry! On Mar 4, 2014, at 3:54 PM, GOUBIER Thierry <thierry.goubier(a)cea.fr> wrote: > With gitfiletree, version numbers are linked with the git history (they are extracted from the git log). > > So, when you ask a read-only gitfiletree remote, it will clone with a depth of 1, and so version numbers are well ... all .1 :) > > When you see other version numbers, then it is either a normal clone, or a mistake of mine. In the AltBrowser configuration, you'll see that the development will do a full clone, and hence give you version numbers in the 200 range. > > Thierry > > De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de Sebastian Sastre [sebastian(a)flowingconcept.com] > EnvoyÃ© : mardi 4 mars 2014 18:53 > Ã : Pharo Development List > Objet : Re: [Pharo-dev] ConfigurationOf and github > > fantastic Thierry. > > gitfiletree did it. > > One thing I didnât get straight yet is version numbers. > > The ConfigurationOfAltBrowser seems to be able to specify the package version and I always see/get SebastianSastre.1 > > sounds familiar? > > > > > On Mar 4, 2014, at 12:28 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > >> Le 04/03/2014 16:14, Sebastian Sastre a Ã©crit : >>> gitfiletree sounds great >> >> Thanks :) >> >>> Questionâ¦ >>> >>> The filetree code /has/ to be in the repoâs root or can I specify a subdir? >> >> No, you can put it anywhere you like. That's part of my professional requirements for using Pharo and git. >> >>> I ask because I use to put some other stuff beside filetree and I use to >>> put the filetree code in a src/ subdir >>> >>> For example now Iâm working on the new ConfigurationOfOmniBase here: >>> >>> https://github.com/sebastianconcept/OmniBase/tree/Pharo3.0 >> >> There is a dir parameter in the url: >> >> Try: >> >> 'gitfiletree://github.com/sebastianconcept/OmniBase.git?protocol=git&readOnl…' >> >> In short, your git ssh clone url, the branch, and the directory inside. >> >> Thierry >> >>> Iâve tried with this but it doesnât go: >>> >>> spec >>> blessing: #release; >>> author: 'sebastianconcept'; >>> repository: >>> 'gitfiletree://github.com/sebastianconcept/OmniBase.git/tree/Pharo3.0/src?pr…'; >>> >>> >>> also this: >>> >>> spec >>> blessing: #release; >>> author: 'sebastianconcept'; >>> repository: >>> 'gitfiletree://github.com/sebastianconcept/OmniBase.git/src?protocol=git&rea…'; >>> >>> >>> help? :) >>> >>> >>> >>> On Mar 3, 2014, at 12:43 PM, Goubier Thierry <thierry.goubier(a)cea.fr >>> <mailto:thierry.goubier@cea.fr>> wrote: >>> >>>> There are two ways: >>>> >>>> Read-only, no dependencies, no registering to github, 3.0 only: >>>> >>>> spec repository: >>>> 'github://dalehenrich/MetacelloRepository:master/monticello/repos/itory/path' >>>> >>>> Not in use in any configuration that I know off. I intend to use it :) >>>> Perfect for stable stuff. >>>> >>>> Read-write, requires Monticello-GitFileTree, requires git ssh access >>>> to github, works with any git remote service, suppose git installed on >>>> the target, no windows support, works on 3.0 and 2.0 : >>>> >>>> spec repository: >>>> 'gitfiletree://github.com/ThierryGoubier/AltBrowser.git?protocol=git&branch=…'; >>>> >>>> Two examples: ConfigurationOfAltBrowser, ConfigurationOfSmaCC >>>> >>>> Thierry >>>> >>>> Le 03/03/2014 16:23, Sebastian Sastre a Ã©crit : >>>>> Is it possible to make a ConfigurationOfXXXX that takes code from github? >>>>> >>>>> If so, is it there any example so I can take a look? >>>>> >>>>> thanks! >>>>> >>>>> sebastian <https://about.me/sebastianconcept> >>>>> >>>>> o/ >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> -- >>>> Thierry Goubier >>>> CEA list >>>> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >>>> 91191 Gif sur Yvette Cedex >>>> France >>>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>>> >>> >> >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

March 4, 2014

Re: [Pharo-dev] [ANN] Creativity - a Smalltalk usability experiment on browsing code and productivity

by Alexandre Bergel

>> I usually never switch between Log and other packages / classes, except if those packages are related (i.e., from the same application). When I need to see other classes that have nothing to do with my application, I usually open a new browser. > > Ok, then another question: > - When working on one application, would you prefer all searches and refactorings be: > a) scoped to your application > b) system wide > c) both (:)) I would like the system to give me what I expect: Searching for something that is not contained in my application, should give me the broad result. Searching for something that is part of the application, should result from the rest of the system should be made optional. Alexandre > > I implemented a) for classes and packages, but I'm wondering if this is the right balance: a) is very convenient, but at times I want b), which means c). > > I also have a problem of a good GUI representation of the fact the browser is scoped, and which scope exactly it is. Why? > > Because, when scoping is easy, then you can drill down through code by scoping over scoping: first a package / then a class / then a group of methods... And then explaining what the scope is at that point is... not easy. > > Thierry > >> Alexandre >> >> >> On Mar 4, 2014, at 9:29 AM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >> >>>> Now in Nautilus I often type Log to only the Log package so what display >>>> your search bar >>> >>> Hi Stef, >>> >>> when you do that, do you usually: >>> - work only with Log in that Nautilus instance (i.e. your package search entry is staying with Log all the time) >>> - Or switch between Log and other packages / classes (i.e. you write Log multiple times in the search bar) >> > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 4, 2014