- Pharo-dev - lists.pharo.org

MCMczWriter>>#flush breaks
by Sven Van Caekenberghe March 14, 2018

March 14, 2018

Hi, I was trying to merge in Zinc changes from the latest Pharo 7 back to the MC Zinc repos. It seems like MCMczWriter>>#flush breaks [1]. I can save to the package cache but not to an Http repo, nor copy to it. Guile, has this been tested, or do you no longer use the old MC ? Sven [1] ByteString(Object)>>error: ByteString(Object)>>errorImproperStore ByteString>>at:put: ZipWriteStream(WriteStream)>>nextPut: [ :ch | self nextPut: ch ] in ZipWriteStream(DeflateStream)>>next:putAll:startingAt: in Block: [ :ch | self nextPut: ch ] ByteArray(SequenceableCollection)>>do: ZipWriteStream(DeflateStream)>>next:putAll:startingAt: ZipWriteStream(DeflateStream)>>nextPutAll: ZipStringMember(ZipArchiveMember)>>compressDataTo: ZipStringMember(ZipArchiveMember)>>writeDataTo: ZipStringMember(ZipArchiveMember)>>writeTo: [ :member | member writeTo: stream. member endRead ] in ZipArchive>>writeTo: in Block: [ :member | ... OrderedCollection>>do: ZipArchive>>writeTo: MCMczWriter>>flush MCMczWriter class>>fileOut:on: MCVersion>>fileOutOn: [ :s | aVersion fileOutOn: s ] in MCHttpRepository(MCFileBasedRepository)>>basicStoreVersion: in Block: [ :s | aVersion fileOutOn: s ] MCHttpRepository>>entityStreamContents: MCHttpRepository>>writeStreamForFileNamed:replace:do: MCHttpRepository(MCFileBasedRepository)>>writeStreamForFileNamed:do: MCHttpRepository(MCFileBasedRepository)>>basicStoreVersion: MCHttpRepository(MCRepository)>>storeVersion: MCHttpRepository(MCFileBasedRepository)>>storeVersion: [ super storeVersion: aVersion ] in MCHttpRepository>>storeVersion: in Block: [ super storeVersion: aVersion ] BlockClosure>>on:do: MCHttpRepository>>retryOnCredentialRequest: MCHttpRepository>>storeVersion: MCWorkingCopyBrowser>>storeVersion:in: [ self storeVersion: newVersion in: aRepository; storeDependencies: newVersion in: aRepository ] in [ [ self storeVersion: newVersion in: aRepository; storeDependencies: newVersion in: aRepository ] ensure: [ (MCVersionInspector new version: newVersion) show ] ] in MCWorkingCopyBrowser>>basicSaveVersionIn: in Block: [ self...

2 4

cannot write to the changes file
by Ben Coman March 13, 2018

March 13, 2018

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

5 9

Family contact book ?
by Sven Van Caekenberghe March 13, 2018

March 13, 2018

There is (probably an example) called 'Family contact book' in the World menu ... weird.

3 3

[Pharo 7.0-dev] Build #694: 21528-Improving-the-Quality-of-the-Bootstrap-process
by ci-pharo-ci-jenkins2＠inria.fr March 13, 2018

March 13, 2018

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

1 0

Error opening Zinc MC repository in latest Pharo 7
by Sven Van Caekenberghe March 13, 2018

March 13, 2018

For some reason I can no longer open Zinc's old school MC repository in Pharo-7.0+alpha.build.690.sha.ffd58dcc88a0698be21b52b565a86316799cb25d (32 Bit) MCHttpRepository location: 'http://mc.stfx.eu/ZincHTTPComponents' user: '' password: ''. > Open repository (browser UI) gives me a DNU see [1] I just don't see what is wrong, maybe it has to do with the latest commit in the repo, (it took a git version number from the image as ancestor), but this code is hard to look at. Now I am stuck trying to fix a problem with Zinc. Any help would be appreciated, Sven [1] UndefinedObject(Object)>>doesNotUnderstand: #< [ :ancestor | (ancestor versionNumber < aVersionArray third or: [ ancestor versionNumber = aVersionArray third and: [ ancestor author ~= aVersionArray second ] ]) ifTrue: [ newer add: ancestor name ] ] in [ :aVersionArray | workingCopy ancestors do: [ :ancestor | (ancestor versionNumber < aVersionArray third or: [ ancestor versionNumber = aVersionArray third and: [ ancestor author ~= aVersionArray second ] ]) ifTrue: [ newer add: ancestor name ] ] ] in [ :workingCopy | | versionsForPackage | workingCopy ancestors do: [ :ancestor | loaded add: ancestor name ]. versionsForPackage := versions select: [ :v | v first = workingCopy package name ]. versionsForPackage do: [ :aVersionArray | workingCopy ancestors do: [ :ancestor | (ancestor versionNumber < aVersionArray third or: [ ancestor versionNumber = aVersionArray third and: [ ancestor author ~= aVersionArray second ] ]) ifTrue: [ newer add: ancestor name ] ] ] ] in MCFileRepositoryInspector>>refresh in Block: [ :ancestor | ... Array(SequenceableCollection)>>do: [ :aVersionArray | workingCopy ancestors do: [ :ancestor | (ancestor versionNumber < aVersionArray third or: [ ancestor versionNumber = aVersionArray third and: [ ancestor author ~= aVersionArray second ] ]) ifTrue: [ newer add: ancestor name ] ] ] in [ :workingCopy | | versionsForPackage | workingCopy ancestors do: [ :ancestor | loaded add: ancestor name ]. versionsForPackage := versions select: [ :v | v first = workingCopy package name ]. versionsForPackage do: [ :aVersionArray | workingCopy ancestors do: [ :ancestor | (ancestor versionNumber < aVersionArray third or: [ ancestor versionNumber = aVersionArray third and: [ ancestor author ~= aVersionArray second ] ]) ifTrue: [ newer add: ancestor name ] ] ] ] in MCFileRepositoryInspector>>refresh in Block: [ :aVersionArray | ... Array(SequenceableCollection)>>do: [ :workingCopy | | versionsForPackage | workingCopy ancestors do: [ :ancestor | loaded add: ancestor name ]. versionsForPackage := versions select: [ :v | v first = workingCopy package name ]. versionsForPackage do: [ :aVersionArray | workingCopy ancestors do: [ :ancestor | (ancestor versionNumber < aVersionArray third or: [ ancestor versionNumber = aVersionArray third and: [ ancestor author ~= aVersionArray second ] ]) ifTrue: [ newer add: ancestor name ] ] ] ] in MCFileRepositoryInspector>>refresh in Block: [ :workingCopy | ... Array(SequenceableCollection)>>do: MCFileRepositoryInspector>>refresh [ self refresh. MCWorkingCopy addDependent: self ] in MCFileRepositoryInspector>>setRepository:workingCopy: in Block: [ self refresh.... [ self value. Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value....

3 7

[Pharo 7.0-dev] Build #693: 21522-Better-support-for-write-barrier-in-MirrorPrimitives
by ci-pharo-ci-jenkins2＠inria.fr March 13, 2018

March 13, 2018

There is a new Pharo build available! The status of the build #693 was: SUCCESS. The Pull Request #1050 was integrated: "21522-Better-support-for-write-barrier-in-MirrorPrimitives" Pull request url: https://github.com/pharo-project/pharo/pull/1050 Issue Url: https://pharo.fogbugz.com/f/cases/21522 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #692: By default a class should not be abstract
by ci-pharo-ci-jenkins2＠inria.fr March 13, 2018

March 13, 2018

There is a new Pharo build available! The status of the build #692 was: FAILURE. The Pull Request #1090 was integrated: "By default a class should not be abstract" Pull request url: https://github.com/pharo-project/pharo/pull/1090 Issue Url: https://pharo.fogbugz.com/f/cases/21570 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

DNS change for lists.pharo.org
by Marcus Denker March 13, 2018

March 13, 2018

Hi, Our provider moved the mailinlists (lists.pharo.org <http://lists.pharo.org/>) to a new server (some new cloud based solution). I did the DNS change just now, but it should not have any impact other than some mails are delivered via the old system until the change propagates everywhere (and I guess in some case we could have some not show up in the archive). Marcus

1 0

Re: [Pharo-dev] Evaluate command handler broken because of AnObsoleteZnCrPortableWriteStream
by Cyril Ferlicot March 13, 2018

March 13, 2018

On Tue, Mar 13, 2018 at 2:30 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I found it, but it is very recent code, pff, now I have to check everything all over > > And yes, now I mistakenly changed an older version, shit > > Errors happen. :) I'll wait the new version to test it and report if the problem of WebSocket is corrected. Thank you! -- Cyril Ferlicot https://ferlicot.fr

1 0

[Pharo 7.0-dev] Build #690: 18414 change usages of standard file stream and multi byte file stream to file decorators
by ci-pharo-ci-jenkins2＠inria.fr March 13, 2018

March 13, 2018

There is a new Pharo build available! The status of the build #690 was: SUCCESS. The Pull Request #1031 was integrated: "18414 change usages of standard file stream and multi byte file stream to file decorators" Pull request url: https://github.com/pharo-project/pharo/pull/1031 Issue Url: https://pharo.fogbugz.com/f/cases/18414 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0