- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] SSL error on windows 7

by webwarrior

ZnClient new url: 'https://github.com'; get Windows 7 64-bit: Error (Error: SSL Exception: connect failed [code:-5]) both in Pharo6 and Pharo7 Windows 10 64-bit: Works fine in both Pharo6 and Pharo7 -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

April 3, 2018

[Pharo 7.0-dev] Build #751: 20151-new-halt-messages

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

There is a new Pharo build available! The status of the build #751 was: SUCCESS. The Pull Request #1177 was integrated: "20151-new-halt-messages" Pull request url: https://github.com/pharo-project/pharo/pull/1177 Issue Url: https://pharo.fogbugz.com/f/cases/20151 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 3, 2018

Re: [Pharo-dev] Loading code with iceberg

by Guillermo Polito

Hi Javier, you should register your repository, otherwise it will be just garbage collected: [[[ myRepository register. ]]] On Sun, Apr 1, 2018 at 4:57 PM, Javier PimÃ¡s <elpochodelagente(a)gmail.com> wrote: > We are loading some code using Iceberg API in pharo6.1. That works fine, > the problem we have is that when I open Iceberg browser no repo is shown > up. Maybe you can help me find what we are doing wrong. We first update > iceberg, then load our repo, code is below. > > Cheers, > Pocho. > > ---- > > Author useAuthor: 'LoadSqueakNOS' during: [ > "First update Iceberg" > > MetacelloPharoPlatform select. > #( > 'BaselineOfTonel' > 'BaselineOfLibGit' > 'BaselineOfIceberg' > 'Iceberg-UI' > 'Iceberg-Plugin-GitHub' > 'Iceberg-Plugin' > 'Iceberg-Metacello-Integration' > 'Iceberg-Libgit-Tonel' > 'Iceberg-Libgit-Filetree' > 'Iceberg-Libgit' > 'Iceberg' > 'Iceberg-Pharo6' > 'LibGit-Core' > 'MonticelloTonel-Tests' > 'MonticelloTonel-Core' > 'MonticelloTonel-FileSystem' ) > do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil: > #removeFromSystem ]. > > Metacello new > baseline: 'Iceberg'; > repository: 'github://pharo-vcs/iceberg:v0.6.8'; > load. > ] > > "Based on the same file from the pharo-vm project" > > myRepository := IceRepositoryCreator new > url: 'git@github.com:nopsys/CogNOS.git'; > subdirectory: 'Image-src'; > createRepository. > (myRepository addPackageNamed: 'SqueakNOS') loadLatest. > > > -- > Javier PimÃ¡s > Ciudad de Buenos Aires > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

April 3, 2018

Re: [Pharo-dev] [Vm-dev] VM git commit hash (was: Image crashing on startup, apparently during GC)

by Alistair Grant

On 3 April 2018 at 01:02, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Alistair, Hi Ben, > > >> On Apr 2, 2018, at 9:28 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> >> >> Hi Ben, >> >> >>> On 2 April 2018 at 15:42, Ben Coman <btc(a)openinworld.com> wrote: >>> >>> >>> >>>> On 2 April 2018 at 20:26, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>>> >>>> >>>>> On Sun, Apr 01, 2018 at 10:46:14AM -0700, Eliot Miranda wrote: >>>>> Hi Alistair, >>>>> >>>>> _,,,^..^,,,_ (phone) >>>>> >>>>>> On Mar 31, 2018, at 1:42 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>>>>> >>>>>> git doesn't provide a substitution mechanism like sccs, but the script >>>>>> we have that embeds the date can just as easily embed the hash. In >>>>>> .git_filters/RevDateURL.smudge there's a line that retrieves the >>>>>> commit date from git: >>>>>> >>>>>> $date = `git log --format=%ad -1`; >>>>>> >>>>>> to get the (short) hash we can simply add: >>>>>> >>>>>> $shorthash = `git log --format=%h -1`; >>>>>> >>>>>> The string substitution can then proceed as for the date. >>>>>> >>>>>> I think it would be worthwhile having both the date and hash in the >>>>>> --version info. >>>>>> >>>>>> I'm happy to add this in and update the --version output if there's >>>>>> general agreement. >>>>> >>>>> Yes please!!! The conventional alternative is to invoke git log from >>>>> the makefiles and lass in the commit hash as a compiler-line default >>>>> me. But this is messy and slows down compilation (unless there is a >>>>> special rule for just one file, and that's fragile). I much prefer >>>>> having the commit somewhere in source. >>>> >>>> Done: >>>> >>>> $ git log --oneline | head >>>> 5a5b1c7 vm version string: add commit short hash >>>> 4c4686e Skip SUnit testing in Sista builds >>>> 79c0809 Merge pull request #230 from smalltalking/Cog >>>> 804ed5c Fixed typo in the download URL >>>> >>>> >>>> $ products/cogspur64linuxht/pharo --version >>>> 5.0-201804012008-version_hash Sun Apr 1 22:15:07 CEST 2018 gcc 5.4.0 [Production Spur 64-bit VM] >>>> CoInterpreter VMMaker.oscog-eem.2361 uuid: 7ca2f89a-de70-422f-b92b-54f91ac4e47b Apr 1 2018 >>>> StackToRegisterMappingCogit VMMaker.oscog-eem.2361 uuid: 7ca2f89a-de70-422f-b92b-54f91ac4e47b Apr 1 2018 >>>> VM: 201804012008-version_hash alistair@4c0a4b2bdb79:vmmaker/opensmalltalk-vm $ >>>> Date: Sun Apr 1 22:08:11 2018 +0200 $ Hash: 5a5b1c7 $ >>> >>> >>> Maybe rather than just "Hash:" could it be more explicit as "GitHash:" or even "GitSHA1:" >>> One day the algorithm is likely to change... "Moving Git past SHA-1" (https://lwn.net/Articles/715716/) >>> and it may be useful later to be able to distinguish. >> >> I like "GitHash" as it may not be obvious what the hash refers to for >> a newcomer. Even if/when git moves away from sha1, from a cli/ui >> perspective presumably it will still just be "the hash". > > Commit Hash? > Commit Hash (git)? > C Commit Hash? > Repository Commit Hash? > > We've already moved from one sccs to another for the C code and may move again if anyone improves on git, which is not inconceivable. Makes sense, CommitHash it is. I've updated the PR. But since Nicolas and Fabio are busy working on getting the build and deploy pipe-line working I'll wait a bit before merging rather than potentially derailing their work (thanks, guys!). Cheers, Alistair >>>> Plugins: 201804012008-version_hash alistair@4c0a4b2bdb79:vmmaker/opensmalltalk-vm $ >>>> Linux 4c0a4b2bdb79 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux >>>> plugin path: products/cogspur64linuxht/lib/pharo/5.0-201804012008-version_hash [default: /home/alistair/vmmaker/opensmalltalk-vm/products/cogspur64linuxht/lib/pharo/5.0-201804012008-version_hash/] >>>> >>>> >>>> As expected, the hash is also included in: >>>> >>>> - the VirtualMachine object (in Pharo, and the equivalent in squeak) >>> >>> >>> I presume this is what shows up under System > System Reporter ? >> >> Yes. >> >> >>>> - crash.dmp >>>> - kill -USR1 output >>>> >>>> >>>> https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/233 >>>> if anyone wants to take a look. >>> >>> >>> >>> An interesting insight for me into how the version info is generated. thx. >> >> Glad it was useful. :-) >> >> Thanks for your feedback. I'll update the PR (probably tomorrow). >> >> Cheers, >> Alistair

April 3, 2018

[Pharo 7.0-dev] Build #750: 21670-FileReference-GT-Contents-Inspector-causes-DNU-binary

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

There is a new Pharo build available! The status of the build #750 was: SUCCESS. The Pull Request #1176 was integrated: "21670-FileReference-GT-Contents-Inspector-causes-DNU-binary" Pull request url: https://github.com/pharo-project/pharo/pull/1176 Issue Url: https://pharo.fogbugz.com/f/cases/21670 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 3, 2018

Re: [Pharo-dev] [Pharo7] halt inside and outside tests

by Tudor Girba

+1 Doru > On Apr 3, 2018, at 9:09 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 3 Apr 2018, at 00:19, Ben Coman <btc(a)openinworld.com> wrote: >> >> >> >> On 3 April 2018 at 03:12, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> Hi, >> >> As we can not very easily decide if we are inside a test execution or not there was the idea to have special #halt messages >> >> https://pharo.fogbugz.com/f/cases/20151/new-halt-messages >> >> This PR implements them: >> >> https://github.com/pharo-project/pharo/pull/1177 >> >> There is now #haltIfInsideTest and #haltfOutsideTest. I >> >> Should the standard #halt default to one of these? Or left as is? (I've no clue, just the question arises). >> > I would keep it for now as is.. it is the simplest to have one âhaltâ that always halts and then variants (there > is halt once, too, which makes often more sense than #halt). > > Marcus -- www.tudorgirba.com www.feenk.com "Reasonable is what we are accustomed with."

April 3, 2018

Re: [Pharo-dev] [Pharo7] halt inside and outside tests

by Marcus Denker

> On 3 Apr 2018, at 00:19, Ben Coman <btc(a)openinworld.com> wrote: > > > > On 3 April 2018 at 03:12, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > Hi, > > As we can not very easily decide if we are inside a test execution or not there was the idea to have special #halt messages > > https://pharo.fogbugz.com/f/cases/20151/new-halt-messages <https://pharo.fogbugz.com/f/cases/20151/new-halt-messages> > > This PR implements them: > > https://github.com/pharo-project/pharo/pull/1177 <https://github.com/pharo-project/pharo/pull/1177> > > There is now #haltIfInsideTest and #haltfOutsideTest. I > > Should the standard #halt default to one of these? Or left as is? (I've no clue, just the question arises). > I would keep it for now as is.. it is the simplest to have one âhaltâ that always halts and then variants (there is halt once, too, which makes often more sense than #halt). Marcus

April 3, 2018

Re: [Pharo-dev] [Vm-dev] VM git commit hash (was: Image crashing on startup, apparently during GC)

by Eliot Miranda

Hi Alistair, Hi Ben, > On Apr 2, 2018, at 9:28 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > Hi Ben, > > >> On 2 April 2018 at 15:42, Ben Coman <btc(a)openinworld.com> wrote: >> >> >> >>> On 2 April 2018 at 20:26, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>> >>> >>>> On Sun, Apr 01, 2018 at 10:46:14AM -0700, Eliot Miranda wrote: >>>> Hi Alistair, >>>> >>>> _,,,^..^,,,_ (phone) >>>> >>>>> On Mar 31, 2018, at 1:42 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>>>> >>>>> git doesn't provide a substitution mechanism like sccs, but the script >>>>> we have that embeds the date can just as easily embed the hash. In >>>>> .git_filters/RevDateURL.smudge there's a line that retrieves the >>>>> commit date from git: >>>>> >>>>> $date = `git log --format=%ad -1`; >>>>> >>>>> to get the (short) hash we can simply add: >>>>> >>>>> $shorthash = `git log --format=%h -1`; >>>>> >>>>> The string substitution can then proceed as for the date. >>>>> >>>>> I think it would be worthwhile having both the date and hash in the >>>>> --version info. >>>>> >>>>> I'm happy to add this in and update the --version output if there's >>>>> general agreement. >>>> >>>> Yes please!!! The conventional alternative is to invoke git log from >>>> the makefiles and lass in the commit hash as a compiler-line default >>>> me. But this is messy and slows down compilation (unless there is a >>>> special rule for just one file, and that's fragile). I much prefer >>>> having the commit somewhere in source. >>> >>> Done: >>> >>> $ git log --oneline | head >>> 5a5b1c7 vm version string: add commit short hash >>> 4c4686e Skip SUnit testing in Sista builds >>> 79c0809 Merge pull request #230 from smalltalking/Cog >>> 804ed5c Fixed typo in the download URL >>> >>> >>> $ products/cogspur64linuxht/pharo --version >>> 5.0-201804012008-version_hash Sun Apr 1 22:15:07 CEST 2018 gcc 5.4.0 [Production Spur 64-bit VM] >>> CoInterpreter VMMaker.oscog-eem.2361 uuid: 7ca2f89a-de70-422f-b92b-54f91ac4e47b Apr 1 2018 >>> StackToRegisterMappingCogit VMMaker.oscog-eem.2361 uuid: 7ca2f89a-de70-422f-b92b-54f91ac4e47b Apr 1 2018 >>> VM: 201804012008-version_hash alistair@4c0a4b2bdb79:vmmaker/opensmalltalk-vm $ >>> Date: Sun Apr 1 22:08:11 2018 +0200 $ Hash: 5a5b1c7 $ >> >> >> Maybe rather than just "Hash:" could it be more explicit as "GitHash:" or even "GitSHA1:" >> One day the algorithm is likely to change... "Moving Git past SHA-1" (https://lwn.net/Articles/715716/) >> and it may be useful later to be able to distinguish. > > I like "GitHash" as it may not be obvious what the hash refers to for > a newcomer. Even if/when git moves away from sha1, from a cli/ui > perspective presumably it will still just be "the hash". Commit Hash? Commit Hash (git)? C Commit Hash? Repository Commit Hash? We've already moved from one sccs to another for the C code and may move again if anyone improves on git, which is not inconceivable. >>> Plugins: 201804012008-version_hash alistair@4c0a4b2bdb79:vmmaker/opensmalltalk-vm $ >>> Linux 4c0a4b2bdb79 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux >>> plugin path: products/cogspur64linuxht/lib/pharo/5.0-201804012008-version_hash [default: /home/alistair/vmmaker/opensmalltalk-vm/products/cogspur64linuxht/lib/pharo/5.0-201804012008-version_hash/] >>> >>> >>> As expected, the hash is also included in: >>> >>> - the VirtualMachine object (in Pharo, and the equivalent in squeak) >> >> >> I presume this is what shows up under System > System Reporter ? > > Yes. > > >>> - crash.dmp >>> - kill -USR1 output >>> >>> >>> https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/233 >>> if anyone wants to take a look. >> >> >> >> An interesting insight for me into how the version info is generated. thx. > > Glad it was useful. :-) > > Thanks for your feedback. I'll update the PR (probably tomorrow). > > Cheers, > Alistair

April 2, 2018

Re: [Pharo-dev] SSL error on windows 7

by Ben Coman

On 3 April 2018 at 04:13, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > Hi! > > I have some trouble with SSL in Pharo 7. > > If I execute this code: > > ZnClient new url: 'https://google.com'; get. > > I get a result. > > If I execute this code: > > ZnClient new url: 'https://github.com'; get. > This works for me on Microsoft Windows [Version 10.0.16299.309] (`ver` from cmd.exe) with 60539 run from PharoLauncher. <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <link rel="dns-prefetch" href="https://assets-cdn.github.com"> <link rel="dns-prefetch" href="https://avatars0.githubusercontent.com"> <link rel="dns-prefetch" href="https://avatars1.githubusercontent.com"> etc... cheers -ben > > I get this error: Error: SSL Exception: connect failed [code:-5] > > I tried with both stable and latest vm. > > This is very troublesome because I cannot load some projects on this > computer :( > > I am on windows 7. > > Here are the details and the stack: > > Image > ----- > E:\Pharo\images\Pharo 7.0 (development version)-22\Pharo 7.0 > (development version)-22.image > Pharo7.0alpha > Build information: > Pharo-7.0+alpha.build.749.sha.039a4b6f0d61ba99778349c4cff2c4e8d5ff9227 > (32 Bit) > Unnamed > > Virtual Machine > --------------- > C:\Users\JeCisC\Documents\Pharo\vms\70-x86\Pharo.exe > CoInterpreter VMMaker.oscog-eem.2359 uuid: > b3273e3e-dd9d-4819-a928-7034e1cf412c Mar 16 2018 > StackToRegisterMappingCogit VMMaker.oscog-eem.2359 uuid: > b3273e3e-dd9d-4819-a928-7034e1cf412c Mar 16 2018 > VM: 201803161038 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > Date: Fri Mar 16 11:38:09 2018 +0100 $ Plugins: 201803161038 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > > Win32 built on Mar 16 2018 11:02:19 GMT Compiler: 6.4.0 > VMMaker versionString VM: 201803161038 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Fri Mar 16 > 11:38:09 2018 +0100 $ Plugins: 201803161038 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > CoInterpreter VMMaker.oscog-eem.2359 uuid: > b3273e3e-dd9d-4819-a928-7034e1cf412c Mar 16 2018 > StackToRegisterMappingCogit VMMaker.oscog-eem.2359 uuid: > b3273e3e-dd9d-4819-a928-7034e1cf412c Mar 16 2018 > > Operating System/Hardware > ------------------------- > Win32 6.1 IX86 > > Operating System Details > ------------------------ > Operating System: Windows 7 Professional N (Build 7601 Service Pack 1) > SP major version: 1 > SP minor version: 0 > Suite mask: 100 > Product type: 1 > > > ============================================================== > > ZdcSecureSocketStream(Object)>>error: > ZdcSecureSocketStream>>sslException:code: > ZdcSecureSocketStream>>connect > ZnClient>>setupTLSTo: > ZnClient>>newConnectionTo: > ZnClient>>getConnectionAndExecute > ZnClient>>executeWithRedirectsRemaining: > [ self executeWithRedirectsRemaining: self maxNumberOfRedirects ] in > ZnClient>>executeWithRetriesRemaining: in Block: [ self > executeWithRedirectsRemaining: self maxNumb...etc... > BlockClosure>>on:do: > ZnClient>>executeWithRetriesRemaining: > [ self executeWithRetriesRemaining: self numberOfRetries ] in [ [ self > executeWithRetriesRemaining: self numberOfRetries ] > on: Error > do: self ifFailBlock ] in ZnClient>>executeWithTimeout in Block: [ > self > executeWithRetriesRemaining: self numberOfR...etc... > BlockClosure>>on:do: > [ [ self executeWithRetriesRemaining: self numberOfRetries ] > on: Error > do: self ifFailBlock ] in ZnClient>>executeWithTimeout in Block: [ > [ > self executeWithRetriesRemaining: self numberO...etc... > [ ^ block value ] in ZnClient>>withTimeoutDo: in Block: [ ^ block value ] > [ activeProcess psValueAt: index put: anObject. > aBlock value ] in ZnConnectionTimeout(DynamicVariable)>>value:during: in > Block: [ activeProcess psValueAt: index put: anObject.... > BlockClosure>>ensure: > ZnConnectionTimeout(DynamicVariable)>>value:during: > ZnConnectionTimeout class(DynamicVariable class)>>value:during: > ZnClient>>withTimeoutDo: > ZnClient>>executeWithTimeout > [ result := self executeWithTimeout ] in ZnClient>>execute in Block: [ > result := self executeWithTimeout ] > [ ^ block value ] in ZnClient>>withProgressDo: in Block: [ ^ block value ] > [ activeProcess psValueAt: index put: anObject. > aBlock value ] in ZnSignalProgress(DynamicVariable)>>value:during: in > Block: [ activeProcess psValueAt: index put: anObject.... > BlockClosure>>ensure: > ZnSignalProgress(DynamicVariable)>>value:during: > ZnSignalProgress class(DynamicVariable class)>>value:during: > ZnClient>>withProgressDo: > ZnClient>>execute > ZnClient>>get > UndefinedObject>>DoIt > > > > -- > Cyril Ferlicot > https://ferlicot.fr > >

April 2, 2018

Re: [Pharo-dev] [Pharo7] halt inside and outside tests

by Ben Coman

On 3 April 2018 at 03:12, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > As we can not very easily decide if we are inside a test execution or not > there was the idea to have special #halt messages > > https://pharo.fogbugz.com/f/cases/20151/new-halt-messages > > This PR implements them: > > https://github.com/pharo-project/pharo/pull/1177 > > There is now #haltIfInsideTest and #haltfOutsideTest. I > Should the standard #halt default to one of these? Or left as is? (I've no clue, just the question arises). cheers -ben

April 2, 2018