- Pharo-dev - lists.pharo.org

Windows PharoLauncher cannot create "C:\Program Files (x86)\Pharo\Pharo.image"
by Ben Coman March 26, 2018

March 26, 2018

I popped over to Windows for a moment to try to make my CloudflareUn crossplatform, and installed PharoLauncher from the downloads page... http://files.pharo.org/pharo-launcher/1.1/pharo-launcher-installer-1.1-x86.… I logged in as an Admin to do this, but when I open it I get an error... "PrimitiveFailed: primitive #createDirectory: in WindowsStore failed" where... path ==> "Path / 'C:' / 'Program Files (x86)' / 'Pharo' / 'pharo-local'" encodedPath ==> C:\Program Files (x86)\Pharo\pharo-local (self isDirectory: parent) ==> true in... WindowsStore(DiskStore) >> createDirectory: path | parent encodedPathString pathString result | pathString := self stringFromPath: path. encodedPathString := Primitives encode: pathString. result := Primitives createDirectory: encodedPathString. result ifNil: [ parent := path parent. (self exists: path) ifTrue: [ (self isFile: path) ifTrue: [ self signalFileExists: path ] ifFalse: [ self signalDirectoryExists: path ] ]. (self isDirectory: parent) ifFalse: [ ^ self signalDirectoryDoesNotExist: parent ]. self primitiveFailed ]. ^ self A few calls down the stack is OmSessioNStore>>resetWithStoreNamed: Does this happen for anyone else? Version Info... OS ----- Windows 10 Image ----- C:\Program Files (x86)\Pharo\Pharo.image Pharo6.0 Latest update: #60528 Unnamed Virtual Machine --------------- C:\Program Files (x86)\Pharo\Pharo.exe CoInterpreter VMMaker.oscog-eem.2254 uuid: 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017 VM: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Thu Jul 20 12:42:21 2017 -0700 $ Plugins: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Win32 built on Jul 20 2017 20:21:26 GMT Compiler: 5.4.0 VMMaker versionString VM: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Thu Jul 20 12:42:21 2017 -0700 $ Plugins: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ CoInterpreter VMMaker.oscog-eem.2254 uuid: 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017 Also, I would expect trouble for Non-Admin users trying to use the Admin installed Pharo Launcher.trying to write to "pharo-local" under "Program Files". Does PharoLauncher have its own CI testing to ensure it can open okay and run an image? I'm glad to see it promoted in importance but with this it probably needs such CI testing of its own separate to the usual Pharo CI testing. On Windows such CI testing *should* run as a Non-Admin user. btw, requiring Administrative privileges to install PharoLauncher is going to lock out people who don't have administrative control over their PCs e.g. University student labs. Wanting to run a quick demo for someone in a corporate office. Why don't we make it the same as OSX and Linux and be usable without Admin privileges. That would lower a barrier to entry. cheers -ben

3 5

[Pharo 7.0-dev] Build #722: Fix Case #21647 - Slot Comments Should List Necessary Overrides
by ci-pharo-ci-jenkins2＠inria.fr March 26, 2018

March 26, 2018

There is a new Pharo build available! The status of the build #722 was: SUCCESS. The Pull Request #1150 was integrated: "Fix Case #21647 - Slot Comments Should List Necessary Overrides" Pull request url: https://github.com/pharo-project/pharo/pull/1150 Issue Url: https://pharo.fogbugz.com/f/cases/21647 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #721: 21623-Update-Jenkinsfile-to-use-staged-bootstrap
by ci-pharo-ci-jenkins2＠inria.fr March 26, 2018

March 26, 2018

There is a new Pharo build available! The status of the build #721 was: SUCCESS. The Pull Request #1135 was integrated: "21623-Update-Jenkinsfile-to-use-staged-bootstrap" Pull request url: https://github.com/pharo-project/pharo/pull/1135 Issue Url: https://pharo.fogbugz.com/f/cases/21623 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #720: 21471 AthensCairoMatrixTest and CairoUTF8ConverterTest should be in an own package Athens-Tests-Cairo
by ci-pharo-ci-jenkins2＠inria.fr March 26, 2018

March 26, 2018

There is a new Pharo build available! The status of the build #720 was: SUCCESS. The Pull Request #1006 was integrated: "21471 AthensCairoMatrixTest and CairoUTF8ConverterTest should be in an own package Athens-Tests-Cairo" Pull request url: https://github.com/pharo-project/pharo/pull/1006 Issue Url: https://pharo.fogbugz.com/f/cases/21471 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

DigitalSignatureAlgorithm and dsa.test.out
by Torsten Bergmann March 25, 2018

March 25, 2018

In DigitalSignatureAlgorithm>>testExamplesFromDisk uses a file called "dsa.test.out" Do we have it somewhere (to turn the method into a real test) or can we just delete the method ... Thx T.

1 1

Re: [Pharo-dev] Released versions in Pharo Bootstrap
by Stephan Eggermont March 25, 2018

March 25, 2018

Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > Le 19/03/2018 Ã 18:49, Stephan Eggermont a Ã©crit : >> Then why bother releasing? >> > > Hi, > > For people using Pharo 7 to not get the same bugs for more than 1 year, > to get the new functionalities and to be able to detect new bugs > introduced in releases. Forgive me for sounding like a broken record. How exactly is this style of releasing going to help with these points? Stephan

2 1

Re: [Pharo-dev] [pharo-project/pharo] 21646 AbstractFileReference should use "utilities" protocol name (#1149)
by Guillermo Polito March 25, 2018

March 25, 2018

Hi Torsten, I like all this cleanups and recategorizations. But I have two requests, tell me what you think: - first and more important. I'd like that we define a convention document in a wiki page or pillar document for protocols. What are the correct protocols to use and why? This is important for newcomers and for making tools. I see that you're doing a lot of recategorizations but I'd like if we set them up and discuss them in the mailing list. - second and more technological. Why are all categorizations splitted in mini pull requests, scoped to one class? Can we group them at least by package? otherwise this is killing our integration infrastructure (which is modest but for free :)). Also separating all this changes means that we cannot easily find them in the history later on, I'd prefer that we group related changes in related commits if possible. Marcus was telling me this may be because people have trouble reviewing them if they are too big? I can review if you put me ask me as reviewer. Tx, Guilel On Sun, Mar 25, 2018 at 8:54 PM, Astares <notifications(a)github.com> wrote: > https://pharo.fogbugz.com/f/cases/21646/AbstractFileReference-should- > use-utilities-protocol-name > ------------------------------ > You can view, comment on, or merge this pull request online at: > > https://github.com/pharo-project/pharo/pull/1149 > Commit Summary > > - 21646 AbstractFileReference should use "utilities" protocol name > > File Changes > > - *M* src/FileSystem-Core/AbstractFileReference.class.st > <https://github.com/pharo-project/pharo/pull/1149/files#diff-0> (2) > > Patch Links: > > - https://github.com/pharo-project/pharo/pull/1149.patch > - https://github.com/pharo-project/pharo/pull/1149.diff > > â > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/pharo-project/pharo/pull/1149>, or mute the thread > <https://github.com/notifications/unsubscribe-auth/AArO4g3P9uj62nQGbRG-T842H…> > . > -- 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

2 1

pharo64+load code=broken image
by Javier PimÃ¡s March 24, 2018

March 24, 2018

Hi folks, I take a fresh Pharo6.1 (spur64), load a git repository and save the image. When reopening I get a segmentation fault. OS is ubuntu 17.04/64 bits. I just cannot make it work, tried with all the vms I could (vmI61, vmT61, vmLatest70, vmTLatest70). I suspect it is related to using git but I'm not even sure. Below I put the involved code, crash dump at the end (seems to be the same with any vm). btw, the vmILatest70 script does not seem to work (curl https://get.pharo.org/64/vmILatest70 | bash). Any ideas? --- cli /CogNOS/image (master)$ ../vms/vmI61/pharo-ui Pharo.image ../scripts/loadSqueakNOSImage.st /CogNOS/image (master)$ ../vms/vmI61/pharo-ui SqueakNOS.image --- loadSqueaNOSImage.st Author useAuthor: 'LoadSqueakNOS' during: [ Metacello new baseline: #SqueakNOS; repository: 'github://nopsys/CogNOS/Image-src'; load ]. (Smalltalk saveAs: 'SqueakNOS') ifFalse: [ Smalltalk snapshot: false andQuit: true ]. /CogNOS/image (master)$ ../vms/vmI61/pharo-ui Pharo.image ../scripts/loadSqueakNOSImage.st /CogNOS/image (master)$ ../vms/vmI61/pharo-ui SqueakNOS.image ----- Segmentation fault Thu Mar 22 22:52:28 2018 /CogNOS/vms/vmI61/pharo-vm/lib/pharo/5.0-201708271955/pharo Pharo VM version: 5.0-201708271955 Sun Aug 27 20:00:28 UTC 2017 gcc 4.6.3 [Production Spur 64-bit ITHB VM] Built from: CoInterpreter VMMaker.oscog-eem.2265 uuid: 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 With: StackToRegisterMappingCogit VMMaker.oscog-eem.2262 uuid: 8b531242-de02-48aa-b418-8d2dde0bec6c Aug 27 2017 Revision: VM: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Sun Aug 27 21:55:26 2017 +0200 $ Plugins: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Build host: Linux testing-gce-643eb2a1-aa49-4136-af37-2965c12a9e8f 3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 16:47:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux plugin path: /CogNOS/vms/vmI61/pharo-vm/lib/pharo/5.0-201708271955 [default: /CogNOS/vms/vmI61/pharo-vm/lib/pharo/5.0-201708271955/] C stack backtrace & registers: rax 0xa6bdac40 rbx 0xa6bdaad0 rcx 0xa6bdacf8 rdx 0xa6bdab88 rdi 0xa6bda8a8 rsi 0xa6bda8a8 rbp 0xa6bdaa18 rsp 0xa6bdadb0 r8 0xa6bda2e8 r9 0xa6bda3a0 r10 0xa6bda458 r11 0xa6bda510 r12 0xa6bda5c8 r13 0xa6bda680 r14 0xa6bda738 r15 0xa6bda7f0 rip 0xa6bdae68 *[0x7ffea6bdae68] /CogNOS/vms/vmI61/pharo-vm/lib/pharo/5.0-201708271955/pharo[0x41cd91] /CogNOS/vms/vmI61/pharo-vm/lib/pharo/5.0-201708271955/pharo[0x41d11f] /lib/x86_64-linux-gnu/libc.so.6(+0x357f0)[0x7efdaadb67f0] /lib/x86_64-linux-gnu/libc.so.6(malloc_usable_size+0x12)[0x7efdaae08902] /usr/lib/nvidia-384/libGL.so.1(+0xba159)[0x7efdaa38b159] [0x7ffea6bd9116] Smalltalk stack dump: 0x7ffea6bea5e8 M ExternalAddress>finalize 0x64e4e90: a(n) ExternalAddress 0x7ffea6bea620 M WeakFinalizerItem>finalizeValues 0x64e37d8: a(n) WeakFinalizerItem 0x7ffea6bea658 M [] in WeakRegistry>finalizeValues 0x347fb18: a(n) WeakRegistry 0x7ffea6bea688 M BlockClosure>on:do: 0x2b643c0: a(n) BlockClosure 0x7ffea6bea6c8 M BlockClosure>on:fork: 0x2b643c0: a(n) BlockClosure 0x7ffea6bea708 M [] in WeakRegistry>finalizeValues 0x347fb18: a(n) WeakRegistry 0x7ffea6bea750 M OrderedCollection>do: 0x2b63b38: a(n) OrderedCollection 0x7ffea6bea7a0 M WeakRegistry>finalizeValues 0x347fb18: a(n) WeakRegistry 0x7ffea6bea7d8 M [] in WeakArray class>doOldFinalization 0x3498518: a(n) WeakArray class 0x7ffea6bea808 M BlockClosure>on:do: 0x2b63a00: a(n) BlockClosure 0x7ffea6bea848 M BlockClosure>on:fork: 0x2b63a00: a(n) BlockClosure 0x7ffea6bea888 M [] in WeakArray class>doOldFinalization 0x3498518: a(n) WeakArray class 0x7ffea6bea8d0 M WeakArray(SequenceableCollection)>do: 0x31fe7f0: a(n) WeakArray 0x7ffea6bea908 M [] in WeakArray class>doOldFinalization 0x3498518: a(n) WeakArray class 0x7ffea6bea948 M [] in Semaphore>critical: 0x6031ba0: a(n) Semaphore 0x7ffea6bea988 M BlockClosure>ensure: 0x2b5e260: a(n) BlockClosure 0x7ffea6bea9c8 M Semaphore>critical: 0x6031ba0: a(n) Semaphore 0x7ffea6beaa10 I WeakArray class>doOldFinalization 0x3498518: a(n) WeakArray class 0x7ffea6beaa60 I WeakArray class>finalizationProcess 0x3498518: a(n) WeakArray class 0x649cb58 s [] in WeakArray class>restartFinalizationProcess 0x6036d68 s [] in BlockClosure>newProcess Most recent primitives replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: at: stringHash:initialHash: stringHash:initialHash: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: stringHash:initialHash: replaceFrom:to:with:startingAt: stringHash:initialHash: replaceFrom:to:with:startingAt: stringHash:initialHash: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: at: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: tempAt: indexOfAscii:inString:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: findFirstInString:inSet:startingAt: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: primWrite:from:startingAt:count: findFirstInString:inSet:startingAt: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: primWrite:from:startingAt:count: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: stringHash:initialHash: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: primWrite:from:startingAt:count: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: stringHash:initialHash: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: primGetPosition: replaceFrom:to:with:startingAt: shallowCopy replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: instVarAt: class **StackOverflow** **StackOverflow** indexOfAscii:inString:startingAt: replaceFrom:to:with:startingAt: **StackOverflow** replaceFrom:to:with:startingAt: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: **StackOverflow** stringHash:initialHash: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: instVarAt: **StackOverflow** indexOfAscii:inString:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: **StackOverflow** stringHash:initialHash: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: instVarAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: **StackOverflow** stringHash:initialHash: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: instVarAt: **StackOverflow** basicNew \\ \\ replaceFrom:to:with:startingAt: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: **StackOverflow** stringHash:initialHash: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: primGetPosition: **IncrementalGC** wait value wait value at: at: basicAt: at: at: expire at: at: at: at: at: at: at: at: at: at: at: at: at: at: at: at: at: at: at: at: replaceFrom:to:with:startingAt: at: at: at: at: at: at: at: at: at: at: at: at: at: at: at: at: notNil notNil replaceFrom:to:with:startingAt: signal primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: wait primCloseNoError: signal wait signal wait signal wait signal wait replaceFrom:to:with:startingAt: signal size at: free stack page bytes 8192 available headroom 5576 minimum unused headroom 6032 (Segmentation fault) -- Javier PimÃ¡s Ciudad de Buenos Aires

3 8

[Pharo 7.0-dev] Build #718: 21641 Use "instance creation" protocol in Dependency Analyzer classes - Part2
by ci-pharo-ci-jenkins2＠inria.fr March 23, 2018

March 23, 2018

There is a new Pharo build available! The status of the build #718 was: SUCCESS. The Pull Request #1147 was integrated: "21641 Use "instance creation" protocol in Dependency Analyzer classes - Part2" Pull request url: https://github.com/pharo-project/pharo/pull/1147 Issue Url: https://pharo.fogbugz.com/f/cases/21641 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #717: 21640 Fix comment expressions in Number quo:
by ci-pharo-ci-jenkins2＠inria.fr March 23, 2018

March 23, 2018

There is a new Pharo build available! The status of the build #717 was: SUCCESS. The Pull Request #1146 was integrated: "21640 Fix comment expressions in Number quo:" Pull request url: https://github.com/pharo-project/pharo/pull/1146 Issue Url: https://pharo.fogbugz.com/f/cases/21640 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0