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

Re: [Pharo-dev] changing pharo packaging in linux

by Ben Coman

On Fri, Mar 17, 2017 at 3:47 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 17 Mar 2017, at 04:46, Ben Coman <btc(a)openinworld.com> wrote: > > On Thu, Mar 16, 2017 at 6:11 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > > Hi, > > Last weeks I was fighting with library dependency problems on linux > distributions and at the end I came to the conclusion that the only way to > guarantee that our own dependencies will be found first than OS versions > (which can have problems for us when we choose to distribute a library by > our own) is to add library directory to LD_LIBRARY_PATH before the > execution. > > Now, I added that to zeroconf and thatâs working fine, but now we have > the problem of the ânon zeroconfâ distributions. > > I checked how to add this and well, turns out that âold wayâ of > distributions, from the standard builds of os-vm (we changed it like 5 > years ago) already have something like that. The osvm for linux has this > structure: > > ./pharo > ./lib > ./lib/5.0-201703221605 > ./lib/5.0-201703221605/* //All binaries and libraries here > ./bin > ./bin/pharo > > thing is: here ./pharo is an script who mades all we need. > > So, instead reinventing the wheel I want to go back to this structureâ¦ I > do not think it will imply anything to anyone, but I wanted to let you know > :) > > cheers, > Esteban > > > > Can you consider this for our startup script... > Generalise determination of LD_LIBRARY_PATH in squeak run script > https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/15 > > > this is already merged, isnât? > in osvm, yes. > then is already in âmy scriptâ (what I was proposing is to use the osvm > script) :) > cool, just checking. Not too long ago it was missing from the Squeak download. cheers -ben btw, I just checked Squeak again and actually its script is now completely different, not setting LD_LIBRARY_PATH at all. > > > Last time I downloaded Squeak this hadn't filtered through to their > packaging > and their startup script bombed on my 32-bit Debian 8 Jessie. > > cheers -ben > > > P.S if time permits, could you also action out this.. > Download PharoXXX.sources if its not found in the usual location. > https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/79 > > >

March 17, 2017

Re: [Pharo-dev] Pharo7 Inspector feature idea - cherry-pick collection items

by Tudor Girba

Yes, the order is given by the order in which I click on the items. Doru > On Mar 17, 2017, at 9:26 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > > 2017-03-17 10:18 GMT+01:00 Norbert Hartl <norbert(a)hartl.name>: > Is there a reason why the order is reversed? > > I think it related to FastTable. Selected indexes are in order from last selected to first selected. New selected row is always added as first. -- www.tudorgirba.com www.feenk.com "If you can't say why something is relevant, it probably isn't."

March 17, 2017

Re: [Pharo-dev] 60445, empty version info stamps

by Pavel Krivanek

Pharo 7 will be bootstrapped from the metadata-less filetree where timestamps are ignored completely. So the question is if we should put energy into this... -- Pavel 2017-03-17 11:57 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > > > On Fri, Mar 17, 2017 at 5:30 PM, Ben Coman <btc(a)openinworld.com> wrote: > >> >> >> On Fri, Mar 17, 2017 at 5:22 PM, Ben Coman <btc(a)openinworld.com> wrote: >> >>> In 60445, browse the implementors of #cacheAt:for:ifAbsentPut: >>> and the view the Versions of each. >>> Curiously some of them have a blank user/date. >>> >>> There are others... >>> errors := OrderedCollection new. >>> versions := (CompiledMethod allInstances) flatCollect: [:cm| >>> [VersionBrowser new setRGMethodFrom: cm asRingDefinition; >>> buildChangeList] >>> on: Error do:[:ex| errors add: (cm -> ex). #()] ]. >>> versions size. >>> "112131" >>> emptyStamps := versions select: [:rgm| rgm stamp = '']. >>> emptyStamps size. >>> "9264" >>> or 8% >>> >>> Maybe some are historic, but I'd guess this one at least is not so >>> old... >>> GLMFastListDataSource>>cacheAt:for:ifAbsentPut: >>> >>> What reasonable action do we need to take? >>> >>> cheers -ben >>> >> >> P.S. >> the errors were all "UTF8InvalidText: Invalid utf8 input detected" for >> these methods... >> QuotedPrintableMimeConverter >> #decode: >> StringTest >> #UTF8InvalidText: >> EpEnabledIntegrationTest >> #setUp >> SingleCodeCriticResultList >> #diffTextForChange: >> >> >> > Further analysis... > 60000 versions=93482 emptyStamps=8964 > 60050 versions=95654 (+2172) emptyStamps=9214 (+250) > 60100 versions=96112 (+458) emptyStamps=9212 (-2) > 60150 versions=97335 (+1223) emptyStamps=9211 (-1) > 60200 versions=98030 (+695) emptyStamps=9169 (-42) > 60250 versions=99779 (+1749) emptyStamps=9282 (113) > 60300 versions=109440 (+9661) emptyStamps=9153 (-129) > 60350 versions=109586 (+146) emptyStamps=9173 (+20) > 60400 versions=110278 (+692) emptyStamps=9185 (+12) > 60455 versions=112131 (+1853) emptyStamps=9264 (+79) > > cheers -ben >

March 17, 2017

Re: [Pharo-dev] 60445, empty version info stamps

by Ben Coman

On Fri, Mar 17, 2017 at 5:30 PM, Ben Coman <btc(a)openinworld.com> wrote: > > > On Fri, Mar 17, 2017 at 5:22 PM, Ben Coman <btc(a)openinworld.com> wrote: > >> In 60445, browse the implementors of #cacheAt:for:ifAbsentPut: >> and the view the Versions of each. >> Curiously some of them have a blank user/date. >> >> There are others... >> errors := OrderedCollection new. >> versions := (CompiledMethod allInstances) flatCollect: [:cm| >> [VersionBrowser new setRGMethodFrom: cm asRingDefinition; >> buildChangeList] >> on: Error do:[:ex| errors add: (cm -> ex). #()] ]. >> versions size. >> "112131" >> emptyStamps := versions select: [:rgm| rgm stamp = '']. >> emptyStamps size. >> "9264" >> or 8% >> >> Maybe some are historic, but I'd guess this one at least is not so old... >> GLMFastListDataSource>>cacheAt:for:ifAbsentPut: >> >> What reasonable action do we need to take? >> >> cheers -ben >> > > P.S. > the errors were all "UTF8InvalidText: Invalid utf8 input detected" for > these methods... > QuotedPrintableMimeConverter >> #decode: > StringTest >> #UTF8InvalidText: > EpEnabledIntegrationTest >> #setUp > SingleCodeCriticResultList >> #diffTextForChange: > > > Further analysis... 60000 versions=93482 emptyStamps=8964 60050 versions=95654 (+2172) emptyStamps=9214 (+250) 60100 versions=96112 (+458) emptyStamps=9212 (-2) 60150 versions=97335 (+1223) emptyStamps=9211 (-1) 60200 versions=98030 (+695) emptyStamps=9169 (-42) 60250 versions=99779 (+1749) emptyStamps=9282 (113) 60300 versions=109440 (+9661) emptyStamps=9153 (-129) 60350 versions=109586 (+146) emptyStamps=9173 (+20) 60400 versions=110278 (+692) emptyStamps=9185 (+12) 60455 versions=112131 (+1853) emptyStamps=9264 (+79) cheers -ben

March 17, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60447 Home: https://github.com/pharo-project/pharo-core

March 17, 2017

[pharo-project/pharo-core] 3cb2c0: 60447

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 3cb2c06250cbf8e5de24b9eeebbd30b0f0e4b2a8 https://github.com/pharo-project/pharo-core/commit/3cb2c06250cbf8e5de24b9ee… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-03-17 (Fri, 17 Mar 2017) Changed paths: M Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - before/testBeforeMethodPrimitive.st A Reflectivity-Tests.package/ReflectivityTest.class/README.md A Reflectivity-Tests.package/ReflectivityTest.class/definition.st A Reflectivity-Tests.package/ReflectivityTest.class/instance/running/tearDown.st A Reflectivity-Tests.package/ReflectivityTest.class/instance/tagging/increase.st A Reflectivity-Tests.package/ReflectivityTest.class/instance/tagging/tagExec.st A Reflectivity-Tests.package/ReflectivityTest.class/instance/tagging/tagExec_.st A Reflectivity-Tests.package/ReflectivityTest.class/instance/tests/testTwoLinksUnstallOne.st M Reflectivity.package/ReflectiveMethod.class/instance/invalidate/removeLink_.st M Reflectivity.package/extension/CompiledMethod/instance/installLink_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60446.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60447.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60446.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60447.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60447 19847 removeLink: needs to invalidate https://pharo.fogbugz.com/f/cases/19847 http://files.pharo.org/image/60/60447.zip

March 17, 2017

Re: [Pharo-dev] Fogbugz feedback - "Image Version"

by Eliot Miranda

Hi Ben, > On Mar 16, 2017, at 8:32 PM, Ben Coman <btc(a)openinworld.com> wrote: > > A niggle I've had for a while is that the "Image Version" field seems to me to be useless. > > It defaults to a particular major version. > (that even though only a small thing, is one more thing to maintain) > > It tends to be superseded by the Milestone field. > > The limited selection of major version is too broad to add any > useful info beyond Milestone to narrow down action. > > So I wonder Image Version if it might be replaced by a freeform field > "Image Version" to enter the value from System > About. > > ----- > As an extension, given the flux of the VMs with the move to 64 bit, > and ongoing support for both, it might also be good to have a "VM Version" field. > > Now actually I often find it awkward to report VM version. > The text under System > System Reporter > VM General > is quite bulky and its not clear what is the really useful parts for identification. > So I usually end up pasting the whole thing, but this is too much for > an issue tracker field. Also, there is no indication here of itimer versus threaded heartbeats which is sometimes pertinent. > Could suitable minimal VM version info be added to System > About > so the info required for the issue tracker is all in one simple place? Perhaps we should start by enumerating use cares. I originally wrote that bulky version info so that vm maintainers could identify the exact version of a VM. The use case here is to locate or obtain the build date, c compiler and exact C and VMMaker source for the vm in order to locate the exact vm, attach a debugger, recompile a matching debug vm, etc. At the time the version info was a) the commit to the subversion Cog repository of the vm sources b) the commit to the subversion squeakvm repository of the vm support files shared between Cog and squeakvm c) the VMMaker version of the StackInterpreter or CoInterpreter in the vm (including the "*" dirty mark if so) d) the VMMaker version of the Cogit in the vm (including the "*" dirty mark if so) With opensmalltalk-vm we can collapse a) and b), or rather, b) is no longer separate and hence obsolete, but the triad a), c) & d) are still most relevant to me. Condensing these to a summary means having to index (e.g. lookup the VMMaker info in opensmalltalk-vm by checking out a particular commit) and that's time consuming. So for me, while the info is poorly formatted and hard to read it is informative and saves me time. I'm happy to see it paired down by dropping b), and doing whatever we can to make it more readable but I'd still like to see people cite it in full when reporting a potential vm problem or reporting their vm version. What other use cases are there for this version info? (and that's not a rhetorical question). > > ----- > Finally, do we want these version fields to: > * remain static for the version initially reported on, or > * be refreshed as confirmed in a later version, or > * have separate fields "Confirmed in {Image/VM} Version" to track tests. > > cheers -ben > > cheers -ben >

March 17, 2017

Re: [Pharo-dev] 60445, empty version info stamps

by Ben Coman

On Fri, Mar 17, 2017 at 5:22 PM, Ben Coman <btc(a)openinworld.com> wrote: > In 60445, browse the implementors of #cacheAt:for:ifAbsentPut: > and the view the Versions of each. > Curiously some of them have a blank user/date. > > There are others... > errors := OrderedCollection new. > versions := (CompiledMethod allInstances) flatCollect: [:cm| > [VersionBrowser new setRGMethodFrom: cm asRingDefinition; buildChangeList] > on: Error do:[:ex| errors add: (cm -> ex). #()] ]. > versions size. > "112131" > emptyStamps := versions select: [:rgm| rgm stamp = '']. > emptyStamps size. > "9264" > or 8% > > Maybe some are historic, but I'd guess this one at least is not so old... > GLMFastListDataSource>>cacheAt:for:ifAbsentPut: > > What reasonable action do we need to take? > > cheers -ben > P.S. the errors were all "UTF8InvalidText: Invalid utf8 input detected" for these methods... QuotedPrintableMimeConverter >> #decode: StringTest >> #UTF8InvalidText: EpEnabledIntegrationTest >> #setUp SingleCodeCriticResultList >> #diffTextForChange:

March 17, 2017

Re: [Pharo-dev] Pharo7 Inspector feature idea - cherry-pick collection items

by Denis Kudriashov

2017-03-17 10:18 GMT+01:00 Norbert Hartl <norbert(a)hartl.name>: > Is there a reason why the order is reversed? I think it related to FastTable. Selected indexes are in order from last selected to first selected. New selected row is always added as first.

March 17, 2017

60445, empty version info stamps

by Ben Coman

In 60445, browse the implementors of #cacheAt:for:ifAbsentPut: and the view the Versions of each. Curiously some of them have a blank user/date. There are others... errors := OrderedCollection new. versions := (CompiledMethod allInstances) flatCollect: [:cm| [VersionBrowser new setRGMethodFrom: cm asRingDefinition; buildChangeList] on: Error do:[:ex| errors add: (cm -> ex). #()] ]. versions size. "112131" emptyStamps := versions select: [:rgm| rgm stamp = '']. emptyStamps size. "9264" or 8% Maybe some are historic, but I'd guess this one at least is not so old... GLMFastListDataSource>>cacheAt:for:ifAbsentPut: What reasonable action do we need to take? cheers -ben

March 17, 2017