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

Re: [Pharo-dev] PharoSpur32Vm

by Nicolas Cellier

2017-03-17 23:32 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > > > 2017-03-16 21:51 GMT+01:00 Nicolas Cellier <nicolas.cellier.aka.nice@ > gmail.com>: > >> >> >> 2017-03-15 18:14 GMT+01:00 Nicolas Cellier <nicolas.cellier.aka.nice@gmai >> l.com>: >> >>> >>> >>> 2017-03-15 15:03 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>>> sorry for coming late to this threadâ¦ hard week :) >>>> why we are trying to compile with cygwin? >>>> is there a problem with the mingw distro? >>>> >>>> I didnât have the time to update the README, sadly. But wellâ¦ following >>>> appveyor configuration should give you all you need to reproduce the build >>>> (thatâs what I did last time I built an environment). >>>> >>>> Esteban >>>> >>>> >>>> Hi Esteban, >>> How did you solve the directx problem? >>> >>> >> >> Hurrah, I succeeded in compiling Win32 Pharo VM from cygwin by using >> cross-compiler i686-w64-mingw32 >> (cygwin64 here but it could be cygwin32). >> >> This is good news, because it means that: >> - we don't have to rely anymore on non-redistributable legacy directx SDK >> - we can compile with clang if we want too (well, for all the 3rd party >> dependencies, that's a bit more work) >> - it opens the door to win64 version >> >> Some details remain: I have to pick the right libgcc and libwindpthread >> as weel as iconv.dll and copy them to the pharo build directory to satisfy >> the SDL2 dependencies. >> Maybe there's a better option for compiling SDL2 with more static stuff? >> -static-libgcc or something... >> >> cairo required another dirty hack, not the one of Igor which must be >> eliminated for cygwin compilation, but one for working around the files >> that are not truncated when overwritten... >> I wonder where this bug comes from? make? cygwin itself? VirtualBox >> (unlikely)? >> > > what hack from Igor ? I thought the pharo build just downloads a tar.gz > archive from cairo and starts the configure/build ? > > https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/f7d3c98eaa001d2d07…

March 17, 2017

Re: [Pharo-dev] PharoSpur32Vm

by Nicolai Hess

2017-03-16 21:51 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com>: > > > 2017-03-15 18:14 GMT+01:00 Nicolas Cellier <nicolas.cellier.aka.nice@ > gmail.com>: > >> >> >> 2017-03-15 15:03 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> sorry for coming late to this threadâ¦ hard week :) >>> why we are trying to compile with cygwin? >>> is there a problem with the mingw distro? >>> >>> I didnât have the time to update the README, sadly. But wellâ¦ following >>> appveyor configuration should give you all you need to reproduce the build >>> (thatâs what I did last time I built an environment). >>> >>> Esteban >>> >>> >>> Hi Esteban, >> How did you solve the directx problem? >> >> > > Hurrah, I succeeded in compiling Win32 Pharo VM from cygwin by using > cross-compiler i686-w64-mingw32 > (cygwin64 here but it could be cygwin32). > > This is good news, because it means that: > - we don't have to rely anymore on non-redistributable legacy directx SDK > - we can compile with clang if we want too (well, for all the 3rd party > dependencies, that's a bit more work) > - it opens the door to win64 version > > Some details remain: I have to pick the right libgcc and libwindpthread as > weel as iconv.dll and copy them to the pharo build directory to satisfy the > SDL2 dependencies. > Maybe there's a better option for compiling SDL2 with more static stuff? > -static-libgcc or something... > > cairo required another dirty hack, not the one of Igor which must be > eliminated for cygwin compilation, but one for working around the files > that are not truncated when overwritten... > I wonder where this bug comes from? make? cygwin itself? VirtualBox > (unlikely)? > what hack from Igor ? I thought the pharo build just downloads a tar.gz archive from cairo and starts the configure/build ? > > If I find the energy to rebase -i and clean a bit my non linear attempts > (squash/reorder/...) then I'll push the branch on opensmalltalk-vm and see > how appveyor like it. > > > > >> On 15 Mar 2017, at 10:11, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >>> >>> >>> >>> 2017-03-15 9:22 GMT+01:00 philippe.back(a)highoctane.be < >>> philippe.back(a)gmail.com>: >>> >>>> I made my own build here. >>>> Not up to date with latest stuff but should work for the build process. >>>> >>>> https://ci.appveyor.com/project/philippeback/pharo-vm >>>> >>>> It uses my forked repo and provided you set your own bintray env vars >>>> for API keys will publish there. >>>> >>>> Check all of the output of env vars and where/which in the appveyor >>>> console to see what gets used when when it comes to compilers and so on as >>>> there were various compiler versions involved at one point. >>>> >>>> Third party cache part is also worth checking. >>>> >>>> Still not able to build on my local box at the moment due to some tools >>>> discrepancies happening. >>>> >>>> My build artifacts are embarking too much at this point but allow you >>>> ro get the release, debug, and assert vms for windows. This helps when >>>> debugging as backtraces and so on are much more meaningful and one can use >>>> gdb more effectively to understand what is going on. >>>> >>>> Just keep the dlls and exes and you'll be fine. >>>> >>> >>> Ah good, thank you. >>> >>> >>> >>>> >>>> HTH >>>> >>>> Phil >>>> >>>> Le 15 mars 2017 08:58, "Nicolai Hess" <nicolaihess(a)gmail.com> a Ã©crit : >>>> >>>>> >>>>> >>>>> 2017-03-14 22:22 GMT+01:00 Nicolas Cellier <nicolas.cellier.aka.n >>>>> ice(a)gmail.com>: >>>>> >>>>>> >>>>>> >>>>>> 2017-03-14 9:30 GMT+01:00 Nicolas Cellier <nicolas.cellier.aka.n >>>>>> ice(a)gmail.com>: >>>>>> >>>>>>> >>>>>>> >>>>>>> 2017-03-14 8:58 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> 2017-03-11 10:01 GMT+01:00 Nicolas Cellier <nicolas.cellier.aka.n >>>>>>>> ice(a)gmail.com>: >>>>>>>> >>>>>>>>> Hi Nicolai, >>>>>>>>> >>>>>>>>> If you look at appveyor.yml configuration on >>>>>>>>> https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Co >>>>>>>>> g/.appveyor.yml, you will see that the pharo brand is not yet in >>>>>>>>> the matrix. >>>>>>>>> >>>>>>>>> It's because builds are based on cygwin, but as I understood, some >>>>>>>>> library used by some plugin required by pharo refuse to compile with >>>>>>>>> cygwin. They appear to work with mingw32. >>>>>>>>> Cygwin provides headers for legacy directx, some distribution of >>>>>>>>> mingw32 did in the past, but it does not seem the case anymore. >>>>>>>>> Using the directx headers from Microsoft SDK is a problem. They >>>>>>>>> are not redistributable and can't be found anymore on the net (too old). We >>>>>>>>> cannot seriously base the builds on something so fragile (both technically >>>>>>>>> and legally) in the long term. >>>>>>>>> >>>>>>>>> Also, the 64 bits VM does only work with clang, and we don't have >>>>>>>>> anything available as a 64bits Microsoft SDK... So pharo has to fix that >>>>>>>>> too. >>>>>>>>> >>>>>>>>> In the interim, you should look at https://github.com/pharo-pr >>>>>>>>> oject/pharo-vm/blob/master/.appveyor.yml and follow the scripts >>>>>>>>> there. >>>>>>>>> >>>>>>>> >>>>>>>> Ok, thank you. >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> I gave it a shot on sunday, because it was particularly rainy in >>>>>>> Nantes, and I almost succeeded in compiling all the dependencies with >>>>>>> cygwin. >>>>>>> Well, I mean with autotools cmake libtool pkg-config and I surely >>>>>>> forget a few other niceties that some not so well informed programmers >>>>>>> committed with the faith that it would make their life "easier". It >>>>>>> certainly does not make mine simpler... >>>>>>> Almost, because gcc 5.4.0 failed to compile cairo with ssize_t: it >>>>>>> seems that the workaround of Igor does not work anymore. >>>>>>> ssize_t, WTF??? >>>>>>> Maybe I'll be able to fix it tonight. Or tomorrow. In which case >>>>>>> I'll publish the branch to see how far appveyor goes. >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> So I solved the ssize_t problem by removing the hack from Igor which >>>>>> is not necessary anymore... >>>>>> But got another problem soon after while building the tests... >>>>>> There are trailing lines generated at end of >>>>>> tests/cairo-test-constructors.c that make the compilation fail: >>>>>> >>>>>> i686-w64-mingw32-gcc -DHAVE_CONFIG_H -I. -I.. -I. -I./pdiff >>>>>> -I../boilerplate -I../util/cairo-missing -I../util/cairo-script -I../src >>>>>> -I../src -D_REENTRANT -I/cygdrive/y/Smalltalk/opensm >>>>>> alltalk-vm/.thirdparty-cache/windows/i386/include/pixman-1 >>>>>> -I/cygdrive/y/Smalltalk/opensmalltalk-vm/.thirdparty-cach >>>>>> e/windows/i386/include/libpng16 -Wall -Wextra >>>>>> -Wmissing-declarations -Werror-implicit-function-declaration >>>>>> -Wpointer-arith -Wwrite-strings -Wsign-compare -Wpacked -Wswitch-enum >>>>>> -Wmissing-format-attribute -Wvolatile-register-var -Wstrict-aliasing=2 >>>>>> -Winit-self -Wunsafe-loop-optimizations -Wno-missing-field-initializers >>>>>> -Wno-unused-parameter -Wno-attributes -Wno-long-long -Winline >>>>>> -fno-strict-aliasing -fno-common -Wp,-D_FORTIFY_SOURCE=2 >>>>>> -Wno-unused-but-set-variable -D_REENTRANT -m32 >>>>>> -static-libgcc -static-libstdc++ -I/cygdrive/y/Smalltalk/opensm >>>>>> alltalk-vm/.thirdparty-cache/windows/i386/include -march=pentium4 -c >>>>>> -o cairo_test_suite-cairo-test-constructors.o `test -f >>>>>> 'cairo-test-constructors.c' || echo './'`cairo-test-constructors.c >>>>>> cairo-test-constructors.c:1118:1: attention : la dÃ©finition de >>>>>> donnÃ©es n'a pas de type ni de classe de stockage >>>>>> oning (); >>>>>> ^ >>>>>> cairo-test-constructors.c:1118:1: attention : type defaults to âintâ >>>>>> in declaration of âoningâ [-Wimplicit-int] >>>>>> cairo-test-constructors.c:1119:5: attention : la dÃ©finition de >>>>>> donnÃ©es n'a pas de type ni de classe de stockage >>>>>> _register_ft_show_glyphs_table (); >>>>>> ^ >>>>>> >>>>>> And the file looks like it has obviously been overwritten, but not >>>>>> truncated !!! >>>>>> >>>>>> ... >>>>>> extern void _register_multi_page (void); >>>>>> extern void _register_fallback_resolution (void); >>>>>> >>>>>> void >>>>>> _cairo_test_runner_register_tests (void) >>>>>> { >>>>>> _register_a1_bug (); >>>>>> _register_a1_clip_paint (); >>>>>> ... >>>>>> _register_multi_page (); >>>>>> _register_fallback_resolution (); >>>>>> } >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> *oning (); _register_ft_show_glyphs_table >>>>>> (); _register_ft_text_vertical_layout_type1 >>>>>> (); _register_ft_text_vertical_layout_type3 >>>>>> (); _register_ft_text_antialias_none (); _register_ps_eps >>>>>> (); _register_ps_features (); _register_ps_surface_source >>>>>> (); _register_svg_surface (); _register_svg_clip >>>>>> (); _register_svg_surface_source (); _register_multi_page >>>>>> (); _register_fallback_resolution ();}* >>>>>> >>>>>> This file is generated by a shell script >>>>>> test/make-cairo-test-constructors.sh >>>>>> I can't find any reference of the bug, and upgrade to version 1.14.8 >>>>>> does not solve the issue. >>>>>> So it will wait until tomorrow... >>>>>> >>>>> >>>>> >>>>> I got the build for windows with mingw nearly working. (it can not >>>>> build some plugins, like SqueakSSL for windows, because the used wincrypt.h >>>>> is different in the mingw distrubtion). >>>>> >>>>> I still have the problem, that there seems to be a preprocessing step >>>>> , that should put the vm-version (and source timestamp) in the >>>>> *sqSCCSVersion.h* >>>>> I got this working by running .travis_build.sh (with the options for >>>>> arch/flavor/platform) But how is this done normally when you build a vm >>>>> locally? >>>>> And how is this done for the pharo-vm we currently use? >>>>> >>>>> >>>>> >>>>>> >>>>>> Nicolas >>>>>> >>>>>> >>>>>>>>> I hope that Esteban will find time to resolve all these problems >>>>>>>>> and have pharo brand back on opensmalltalk-vm. I guess that any form of >>>>>>>>> help is welcome. >>>>>>>>> >>>>>>>>> Nicolas >>>>>>>>> >>>>>>>>> >>>>>>>>> 2017-03-11 8:33 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: >>>>>>>>> >>>>>>>>>> I still have problems building a vm on windows. >>>>>>>>>> can you give me some hints how to start ? >>>>>>>>>> I cloned the recent pharo-vm project, >>>>>>>>>> in opensmalltalk-vm\build.win32x86\pharo.cog.spur\ >>>>>>>>>> run >>>>>>>>>> mvm >>>>>>>>>> >>>>>>>>>> But I got a couple of problems (mingw-32 compiler commands not >>>>>>>>>> found, I had to adjust the include path for finding directx header, missing >>>>>>>>>> variable replacement for git-versions). >>>>>>>>>> So I may miss some important steps. >>>>>>>>>> Is there a repository where I can clone the mingw environment >>>>>>>>>> used to build the win32-pharo-vm, the environment used on the build-server ? >>>>>>>>>> >>>>>>>>>> Thanks >>>>>>>>>> Nicolai >>>>>>>>>> >>>>>>>>>> 2017-02-04 1:50 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> 2017-02-04 1:44 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> 2017-01-23 8:59 GMT+01:00 Esteban Lorenzano < >>>>>>>>>>>> estebanlm(a)gmail.com>: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On 22 Jan 2017, at 13:19, Nicolai Hess <nicolaihess(a)gmail.com> >>>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> 2017-01-22 10:21 GMT+01:00 ClÃ©ment Bera < >>>>>>>>>>>>> bera.clement(a)gmail.com>: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>> >>>>>>>>>>>>>> I believe they're built from* https://github.com/OpenSmalltalk/vm >>>>>>>>>>>>>> <https://github.com/OpenSmalltalk/vm>* using travis and >>>>>>>>>>>>>> appveyor. On the gitbhub readme there are relevant links. All built >>>>>>>>>>>>>> artifacts are also kept on bintray for history. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> Thank you! >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> no, they arenât :) >>>>>>>>>>>>> instead, they are built here: https://github.com/pharo >>>>>>>>>>>>> -project/pharo-vm >>>>>>>>>>>>> >>>>>>>>>>>>> (README still not updated) >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> what did changed ? I am not able to build the vm on windows >>>>>>>>>>>> anymore (something wrong with generating the generator.image, I'll now >>>>>>>>>>>> reset my local pharo-vm build directory and see if it works afterwards). >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> see attached the stderr log : >>>>>>>>>>> >>>>>>>>>>> 'Errors in script loaded from u:\github\pharo-vm\scripts\Loa >>>>>>>>>>> dVMMaker.st' >>>>>>>>>>> [31mMessageNotUnderstood: receiver of "default:" is nil >>>>>>>>>>> [0mUndefinedObject(Object)>>doesNotUnderstand: #default: >>>>>>>>>>> BaseSoundSystem class>>initialize >>>>>>>>>>> MCMethodDefinition>>postloadOver: >>>>>>>>>>> >>>>>>>>>>> .... >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> Are we still working with branch spur-64, or are we back on >>>>>>>>>>>> master ? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Esteban >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Sun, Jan 22, 2017 at 9:25 AM, Nicolai Hess < >>>>>>>>>>>>>> nicolaihess(a)gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Where are the latest Pharo-spur-vms (32bit) are built? >>>>>>>>>>>>>>> I don't see them on the build server, only the buildresults >>>>>>>>>>>>>>> at >>>>>>>>>>>>>>> http://files.pharo.org/vm/pharo-spur32/linux/ >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> The latest builds on the buildserver are from the last year >>>>>>>>>>>>>>> only. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> nicolai >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>> >> >

March 17, 2017

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

by Alistair Grant

On 17 March 2017 at 12:40, Ben Coman <btc(a)openinworld.com> wrote: > > > On Fri, Mar 17, 2017 at 5:02 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> That list is multi-selection. On Mac, you can press Cmd while clicking and >> you get the collection to the right. >> >> > > I now see that Shift-click multi-selects and works just like I imagined it > would. > However Ctrl-click doesn't do anything, which was the only thing I tested > before. > I presume that is a bug? Can anyone confirm this on Linux? > > I'm... 32-bit Debian 8 Jessie. > Pharo 60447 & Unix VM built on Mar 3 2017 21:07:26 Compiler: 4.6.3 > VMMaker versionString VM: 201703031554 > https://github.com/pharo-project/pharo-vm.git $ Date: Fri Mar 3 16:54:16 > 2017 +0100 $ Plugins: 201703031554 > https://github.com/pharo-project/pharo-vm.git $ > CoInterpreter * VMMaker.oscog-eem.2143 uuid: > fe064b6b-e530-4766-837d-799ffe1e8dcd Mar 3 2017 > StackToRegisterMappingCogit * VMMaker.oscog-eem.2143 uuid: > fe064b6b-e530-4766-837d-799ffe1e8dcd Mar 3 2017 I have the same behaviour (can't multi-select using Ctrl-click on linux): Ubuntu 16.04 Pharo 6.0 Latest update: #60438 5.0-201702221539 Wed Feb 22 15:46:29 UTC 2017 gcc 4.6.3 [Production Spur ITHB VM] CoInterpreter * VMMaker.oscog-EstebanLorenzano.2136 uuid: 40534c32-ca6b-4e97-91ec-31d509e49b0c Feb 22 2017 StackToRegisterMappingCogit * VMMaker.oscog-EstebanLorenzano.2136 uuid: 40534c32-ca6b-4e97-91ec-31d509e49b0c Feb 22 2017 VM: 201702221539 https://github.com/pharo-project/pharo-vm.git $ Date: Wed Feb 22 16:39:40 2017 +0100 $ Plugins: 201702221539 https://github.com/pharo-project/pharo-vm.git $ Linux testing-docker-9b911eb3-3e93-4fc4-acb7-571482555639 4.8.12-040812-generic #201612020431 SMP Fri Dec 2 09:33:31 UTC 2016 i686 i686 i386 GNU/Linux plugin path: /snap/pharo/x1/usr/bin/pharo-vm/ [default: /snap/pharo/x1/usr/bin/pharo-vm/] Cheers, Alistair

March 17, 2017

Re: [Pharo-dev] Script to download Pharo 4 vm for Mac os sierra

by stepharong

Nice to see on this list after all these years :) This is important for synectiquers to use the power of the open-source :) > Hello, > > We have a jenkins job, running on a linux machine, that is responsible > for building and outputing a Pharo 4 development image + vm ready to be > used on mac machines. > > We use this command line to download the VM and archived it as output > of the job: > > curl -O http://files.pharo.org/vm/pharo/mac/Pharo-VM-mac-latest.zip > > On my mac (10.12.1), when i open the pharo image with this vm , I am > facing what seem to be some known issues for Mac OS sierra: > > Pharo[13048:431565] *** -[NSPathStore2 stringByAppendingPathExtension:]: > cannot append extension 'bundle/Contents/MacOS/' to path ... > Now, when I try to download a Pharo 4 vm directly from my mac sierra > machine, > with a zeroconf script (get.pharo.org/vm40) > It works: I am able to open the pharo image with this vm. > > Is there a script that allows to download a pharo 4 vm working for mac > os sierra, from a linux machine ? > > --Cyrille Delaunay -- Using Opera's mail client: http://www.opera.com/mail/

March 17, 2017

xsd to pharo?

by stepharong

Hi we are looking for a xsd to pharo class generator? Stef -- Using Opera's mail client: http://www.opera.com/mail/

March 17, 2017

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

by Ben Coman

On Fri, Mar 17, 2017 at 7:47 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I understand why it is useful to you, but it is a PIA for all the rest of > us. > > Consider: > > $ java -version > java version "1.8.0_60" > Java(TM) SE Runtime Environment (build 1.8.0_60-b27) > Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode) > > $ python --version > Python 2.7.10 > > $ ruby --version > ruby 2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin16] > > At the image level Pharo has: > > $ pharo Pharo.image printVersion > [version] 4.0 #40620 > > Clean, simple, precise. > > And then when the rest of the world wants to communicate about the VM > version they are using, you get: > > $ ../bin/pharo --version > 3.9-7 #1 Thu Apr 2 00:51:45 CEST 2015 gcc 4.6.3 [Production ITHB VM] > NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: > 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Apr 2 2015 > NBCogit NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: > 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Apr 2 2015 > https://github.com/pharo-project/pharo-vm.git Commit: > 32d18ba0f2db9bee7f3bdbf16bdb24fe4801cfc5 Date: 2015-03-24 11:08:14 +0100 > By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14904 > Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 > UTC 2012 i686 i686 i386 GNU/Linux > plugin path: /home/audio359/pharo/bin/pharo-vm/ [default: > /home/audio359/pharo/bin/pharo-vm/] > > This is way too technical. > This just needs to be --versionVerbose or --versionAll. cheers -ben > On the other hand, I understand that this is also a vetting problem: who > builds the VM, validates it, assigns it version/build numbers. > > BTW, is there no open source convention of using xx-config to return all > this detailed (build) info ? > > > On 17 Mar 2017, at 11:36, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > 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 Pavel Krivanek

Not sure with the date but we will store a hash of the commit from which the image will be bootstrapped. -- Pavel 2017-03-17 12:43 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > btw, will same user/date for multiple revisions remain available in > a Versions window? > > cheers -ben > > > On Fri, Mar 17, 2017 at 7:02 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > >> 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] Fogbugz feedback - "Image Version"

by Sven Van Caekenberghe

I understand why it is useful to you, but it is a PIA for all the rest of us. Consider: $ java -version java version "1.8.0_60" Java(TM) SE Runtime Environment (build 1.8.0_60-b27) Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode) $ python --version Python 2.7.10 $ ruby --version ruby 2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin16] At the image level Pharo has: $ pharo Pharo.image printVersion [version] 4.0 #40620 Clean, simple, precise. And then when the rest of the world wants to communicate about the VM version they are using, you get: $ ../bin/pharo --version 3.9-7 #1 Thu Apr 2 00:51:45 CEST 2015 gcc 4.6.3 [Production ITHB VM] NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Apr 2 2015 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Apr 2 2015 https://github.com/pharo-project/pharo-vm.git Commit: 32d18ba0f2db9bee7f3bdbf16bdb24fe4801cfc5 Date: 2015-03-24 11:08:14 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14904 Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux plugin path: /home/audio359/pharo/bin/pharo-vm/ [default: /home/audio359/pharo/bin/pharo-vm/] This is way too technical. On the other hand, I understand that this is also a vetting problem: who builds the VM, validates it, assigns it version/build numbers. BTW, is there no open source convention of using xx-config to return all this detailed (build) info ? > On 17 Mar 2017, at 11:36, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > 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

btw, will same user/date for multiple revisions remain available in a Versions window? cheers -ben On Fri, Mar 17, 2017 at 7:02 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > 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] Pharo7 Inspector feature idea - cherry-pick collection items

by Ben Coman

On Fri, Mar 17, 2017 at 5:02 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > That list is multi-selection. On Mac, you can press Cmd while clicking and > you get the collection to the right. > > > I now see that Shift-click multi-selects and works just like I imagined it would. However Ctrl-click doesn't do anything, which was the only thing I tested before. I presume that is a bug? Can anyone confirm this on Linux? I'm... 32-bit Debian 8 Jessie. Pharo 60447 & Unix VM built on Mar 3 2017 21:07:26 Compiler: 4.6.3 VMMaker versionString VM: 201703031554 https://github.com/pharo-project/pharo-vm.git $ Date: Fri Mar 3 16:54:16 2017 +0100 $ Plugins: 201703031554 https://github.com/pharo-project/pharo-vm.git $ CoInterpreter * VMMaker.oscog-eem.2143 uuid: fe064b6b-e530-4766-837d-799ffe1e8dcd Mar 3 2017 StackToRegisterMappingCogit * VMMaker.oscog-eem.2143 uuid: fe064b6b-e530-4766-837d-799ffe1e8dcd Mar 3 2017 cheers -ben > Cheers, > Doru > > > On Mar 17, 2017, at 8:14 AM, Ben Coman <btc(a)openInWorld.com > <btc(a)openinworld.com>> wrote: > > Sometimes when exploring a large data set in inspector, > I'd like to cherry pick a few items to act on as a collection. > > This would need to be valdiated/tested, but It could be useful to be > able to multi-select items and have the next pane to the right be the > collection containing the list of picked items. > > For the moment I can get by with... "self first: 5". > > cheers -ben > . > > > -- > www.tudorgirba.com > www.feenk.com > > "What we can governs what we wish." > > > > >

March 17, 2017