January 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] ZnClient issue: ZdcPlugin Missing

by Photon

Hey Cyril, thanks for your reply. I do not quite understand your instructions tho. I mean I get the anti virus part. I checked both folders, the zipped and unzipped one. They both do not hold any Zclient or Zdc plugin only a zlib1.dll The weird part is that the unzipped ffolder contains more items besides of my images. There were two particular wich I found in the unzipped folder but not in the zipped folder: stderr and stdout wich are just "files"... I do not understand what it means to sign the vm to windows tho. How do i do that? I want to give it a shot. Cheers -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Jan. 13, 2018

Re: [Pharo-dev] cannot write to the changes file

by Ben Coman

On 13 January 2018 at 12:43, Ben Coman <btc(a)openinworld.com> wrote: > Before creating an Issue, can someone confirm the following behaviour on > Windows 10 ? > Downloaded and unzipped into the same folder... > * http://files.pharo.org/image/70/Pharo-7.0.0-alpha. > build.425.sha.eb0a6fb.arch.32bit.zip > * http://files.pharo.org/vm/pharo-spur32/win/pharo-win- > i386-201711262336-8879e2e.zip > > The directory contains... > Pharo7.0-32bit-eb0a6fb.image > Pharo7.0-32bit-eb0a6fb.changes > Pharo.exe > > Double-clicking Pharo.exe produces notification... > Information > Pharo cannot write to the changes file named > C:\Users\....\pharo\Pharo7.0-32bit-eb0a6fb.changes. > Please check that you have write permission for this file. > You won't be able to save this image correctly until you fix this. > and btw, with notepad I can edit and and save the file no problem. cheers -ben > > However if I edit to AST-Tests-Core > NumberParserTest >> testFail > to add "My Comment" > then close all windows, Save&Quit the Image, > restart Pharo by double-clicking on Pharo.exe, > and open System Browser on testFail > I can see my comment. > > I'm not clear on exactly how it works but I presume that restarting the > Image would require "My Comment" to be read from the changes file, > but notepad shows its not in the changes file. > So perhaps the error notification is part of a transition in-Image sources > and > nothing to worry about? > > cheers -ben >

Jan. 13, 2018

Re: [Pharo-dev] cannot write to the changes file

by Alistair Grant

Hi Ben, I've seen this (on Windows 10), 32 bit. It wasn't happening last time I used Win10, some time in the last 4 months. Cheers, Alistair (From my phone) On 13 Jan. 2018 05:44, "Ben Coman" <btc(a)openinworld.com> wrote: > Before creating an Issue, can someone confirm the following behaviour on > Windows 10 ? > Downloaded and unzipped into the same folder... > * http://files.pharo.org/image/70/Pharo-7.0.0-alpha. > build.425.sha.eb0a6fb.arch.32bit.zip > * http://files.pharo.org/vm/pharo-spur32/win/pharo-win- > i386-201711262336-8879e2e.zip > > The directory contains... > Pharo7.0-32bit-eb0a6fb.image > Pharo7.0-32bit-eb0a6fb.changes > Pharo.exe > > Double-clicking Pharo.exe produces notification... > Information > Pharo cannot write to the changes file named > C:\Users\....\pharo\Pharo7.0-32bit-eb0a6fb.changes. > Please check that you have write permission for this file. > You won't be able to save this image correctly until you fix this. > > However if I edit to AST-Tests-Core > NumberParserTest >> testFail > to add "My Comment" > then close all windows, Save&Quit the Image, > restart Pharo by double-clicking on Pharo.exe, > and open System Browser on testFail > I can see my comment. > > I'm not clear on exactly how it works but I presume that restarting the > Image would require "My Comment" to be read from the changes file, > but notepad shows its not in the changes file. > So perhaps the error notification is part of a transition in-Image sources > and > nothing to worry about? > > cheers -ben >

Jan. 13, 2018

cannot write to the changes file

by Ben Coman

Before creating an Issue, can someone confirm the following behaviour on Windows 10 ? Downloaded and unzipped into the same folder... * http://files.pharo.org/image/70/Pharo-7.0.0-alpha.build.425.sha.eb0a6fb.arc… * http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201711262336-8879… The directory contains... Pharo7.0-32bit-eb0a6fb.image Pharo7.0-32bit-eb0a6fb.changes Pharo.exe Double-clicking Pharo.exe produces notification... Information Pharo cannot write to the changes file named C:\Users\....\pharo\Pharo7.0-32bit-eb0a6fb.changes. Please check that you have write permission for this file. You won't be able to save this image correctly until you fix this. However if I edit to AST-Tests-Core > NumberParserTest >> testFail to add "My Comment" then close all windows, Save&Quit the Image, restart Pharo by double-clicking on Pharo.exe, and open System Browser on testFail I can see my comment. I'm not clear on exactly how it works but I presume that restarting the Image would require "My Comment" to be read from the changes file, but notepad shows its not in the changes file. So perhaps the error notification is part of a transition in-Image sources and nothing to worry about? cheers -ben

Jan. 13, 2018

Re: [Pharo-dev] Blame support P7

by Eliot Miranda

Hi Stephane, On Fri, Jan 12, 2018 at 1:26 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi torsten > > we have a super long list of *important* fixes and enhancements to do. > Isn't it important to preserve the ability to exchange code between Pharo, Squeak and Cuis? Don't you care that the VM development is directly affected by this? Is the VM and plugin support not important to Pharo? > > Stef > > On Fri, Jan 12, 2018 at 1:09 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > > Not having timestamps/authors in Pharo 7 due to git and missing blame > support > > (see [1]) has other bad side effects: > > > > > > - it clobbers all method stamps in an MCZ package [1] if you use > Monticello > > which can lead easily to trouble/lamenting > > > > - it is not possible to fileout a changeset [2] in the ChangeSorter > > > > Was there any further discussion/decision for P7 on solving this > > or adding blame support? > > > > Thx > > T. > > > > > > [1] http://forum.world.st/Author-name-in-version-Iceberg-td4968472.html > > [2] http://lists.squeakfoundation.org/pipermail/vm-dev/2018- > January/026350.html > > [3] https://pharo.fogbugz.com/f/cases/20951/ > > > > -- _,,,^..^,,,_ best, Eliot

Jan. 13, 2018

Re: [Pharo-dev] Blame support P7

by Ben Coman

On 13 January 2018 at 04:50, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > 2018-01-12 21:23 GMT+01:00 Norbert Hartl <norbert(a)hartl.name>: > >> Donât you think having Author and timestamps is important? >> > > Glad to see Pharo Community waking up :) > I felt a bit alone since I complained about that in last November ('about > SortFunctions' thread) > I've recently started using Pharo 7 and found it disconcerting when troubleshooting not knowing how old a method is or have any hint who might be familiar with it. IIUC the loss of author/timestamps is a consequence of merge conflicts in version information. I don't have a good grasp of the background on this though. I can't remember seeing a reproducible use case presented to the community to solve. Probably I was too busy and missed the discussion. Could someone link to a past steps to reproduce? Or now we have new Tonel files, how we can reintroduce version info code into a branch so we can experiment with solutions? I had a vague idea where version-info was kept in a separate file to the Tonel file. Each time the Tonel file is updated, its associated version-info is written to a *new* file. The hash of the Tonel file would form part of the version-info filename so you can always find the version-info file for a given Tonel file if they become separated. This might avoid version conflicts since whole version-info files are never modified, only deleted and added. cheers -ben > >> > Am 12.01.2018 um 10:26 schrieb Stephane Ducasse < >> stepharo.self(a)gmail.com>: >> > >> > Hi torsten >> > >> > we have a super long list of *important* fixes and enhancements to do. >> > >> > Stef >> > >> >> On Fri, Jan 12, 2018 at 1:09 AM, Torsten Bergmann <astares(a)gmx.de> >> wrote: >> >> Not having timestamps/authors in Pharo 7 due to git and missing blame >> support >> >> (see [1]) has other bad side effects: >> >> >> >> >> >> - it clobbers all method stamps in an MCZ package [1] if you use >> Monticello >> >> which can lead easily to trouble/lamenting >> >> >> >> - it is not possible to fileout a changeset [2] in the ChangeSorter >> >> >> >> Was there any further discussion/decision for P7 on solving this >> >> or adding blame support? >> >> >> >> Thx >> >> T. >> >> >> >> >> >> [1] http://forum.world.st/Author-name-in-version-Iceberg-td49684 >> 72.html >> >> [2] http://lists.squeakfoundation.org/pipermail/vm-dev/2018-Janu >> ary/026350.html >> >> [3] https://pharo.fogbugz.com/f/cases/20951/ >> >> >> >> >

Jan. 13, 2018

Re: [Pharo-dev] ZnClient issue: ZdcPlugin Missing

by Cyril Ferlicot D.

Le 12/01/2018 Ã 19:48, Photon a Ã©critÂ : > Hello, > > I was just following along this book: > and it told me to get some data via ZnClient like this, I tried them both > with a dot inbetween and independantly like in the picture below. Does > someone got an idea what`s wrong? > Hi, Are you on Windows? Sometimes the Windows's anti-virus delete this plugin... We need to sign the VM for windows to avoid this problem. Try to browse the zip without extracting it to see if it contains the plugin. > <http://forum.world.st/file/t371759/ZnClient_issue.png> > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Jan. 13, 2018

Re: [Pharo-dev] Blame support P7

by Norbert Hartl

> Am 12.01.2018 um 21:50 schrieb Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > > > > 2018-01-12 21:23 GMT+01:00 Norbert Hartl <norbert(a)hartl.name>: >> Donât you think having Author and timestamps is important? > > Glad to see Pharo Community waking up :) > I felt a bit alone since I complained about that in last November ('about SortFunctions' thread) > I donât think it slept. There are just too much important things to do. So a temporary sacrifice is sometimes necesssary. >> >> > Am 12.01.2018 um 10:26 schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: >> > >> > Hi torsten >> > >> > we have a super long list of *important* fixes and enhancements to do. >> > >> > Stef >> > >> >> On Fri, Jan 12, 2018 at 1:09 AM, Torsten Bergmann <astares(a)gmx.de> wrote: >> >> Not having timestamps/authors in Pharo 7 due to git and missing blame support >> >> (see [1]) has other bad side effects: >> >> >> >> >> >> - it clobbers all method stamps in an MCZ package [1] if you use Monticello >> >> which can lead easily to trouble/lamenting >> >> >> >> - it is not possible to fileout a changeset [2] in the ChangeSorter >> >> >> >> Was there any further discussion/decision for P7 on solving this >> >> or adding blame support? >> >> >> >> Thx >> >> T. >> >> >> >> >> >> [1] http://forum.world.st/Author-name-in-version-Iceberg-td4968472.html >> >> [2] http://lists.squeakfoundation.org/pipermail/vm-dev/2018-January/026350.html >> >> [3] https://pharo.fogbugz.com/f/cases/20951/ >> >> >> >

Jan. 12, 2018

[Pharo 7.0-dev] Build #425: SUCCESS

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #425 was: SUCCESS. Could not extract further issue information from commit message: https://pharo.fogbugz.com/f/cases/20961/ Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 12, 2018

[Pharo 7.0-dev] Build #424: SUCCESS

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #424 was: SUCCESS. Could not extract further issue information from commit message: https://pharo.fogbugz.com/f/cases/20960/Move-ExecutionDisplayPlugin-from-Re… Reviewed the code and the tests Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 12, 2018