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

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

Evaluate command handler broken because of AnObsoleteZnCrPortableWriteStream
by Cyril Ferlicot D. March 13, 2018

March 13, 2018

Hello! I have a Jenkins build for MaterialDesignLite and the Pharo 7 build never end. I load the code via the command line "eval" with the "--save" parameter and a Metacello command. While adding some log I found the problem. It comes from this method: EvaluateCommandLineHandler>>evaluate: aStream | result | [ result := Smalltalk compiler evaluate: aStream. self hasSessionChanged ifFalse: [ self stdout print: result; lf ] ] on: Error do: [ :error | self handleError: error ] In Pharo 6 it ends perfectly. In Pharo 7 there is an error and we end up in the catch. Here is the stack I could isolate: MessageNotUnderstood(Exception)>>signal UndefinedObject(Object)>>doesNotUnderstand: #'>=' AnObsoleteZnCrPortableWriteStream(WriteStream)>>nextPut: [ :v | self nextPut: v ] in AnObsoleteZnCrPortableWriteStream(Stream)>>nextPutAll: ByteSymbol(SequenceableCollection)>>do: AnObsoleteZnCrPortableWriteStream(Stream)>>nextPutAll: AnObsoleteZnCrPortableWriteStream(WriteStream)>>nextPutAll: MultiByteFileStream(StandardFileStream)>>printOn: AnObsoleteZnCrPortableWriteStream(Stream)>>print: VTermOutputDriver>>print: I have no idea how to correct this and it's pretty late now. Maybe someone will know :) https://pharo.fogbugz.com/f/cases/21566/EvaluateCommandLineHandler-is-broke… -- Cyril Ferlicot https://ferlicot.fr

4 7

March 13, 2018

Hi, I am trying to write a Metacello configuration loading code from git in the tonel format. I checked all the configurations present in the default Pharo image looking for examples, but it seems most of them load code with Monticello. I found ConfigurationOfPharoMetacello which loads code from github, however, it loads code using the file tree format and not tonel format. Can someone point me to a configuration loading code from git using tonel so I can use it as an example? Thanks -- ClÃ©ment BÃ©ra https://clementbera.github.io/ https://clementbera.wordpress.com/ BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

3 2

Loading configuration of spur
by Javier PimÃ¡s March 12, 2018

March 12, 2018

Ok, now I moved forward but cannot load vmmaker sources into a pharo 61 image, is that supported? I have this snippet that doesn't work: Metacello new filetreeDirectory: '../VMMaker/mc'; baseline: 'Spur'; load where ../VMMaker/mc is a clone of the official pharo repo at github. Cheers, pocho -- Javier PimÃ¡s Ciudad de Buenos Aires

5 10

feenk log
by Tudor Girba March 12, 2018

March 12, 2018

Hi, Here is an update of the work on Bloc, Brick and GT. As always, please do let us know what you think. Bloc: - Improved the deletion in the text editor and covered the scenarios with examples - Worked on the text selection. Still work needed for selection to be production ready: https://twitter.com/feenkcom/status/969183393547259905 - Balanced rope structure for even better performance of the editor. Overall, the performance of the text editor improved 2x. https://twitter.com/feenkcom/status/971009488789516288 - Selectable curves: https://twitter.com/feenkcom/status/967690664589910016 Brick: - Resizer overlay. The tweet below also shows how we can now easily script dragging behavior in examples: https://twitter.com/feenkcom/status/971990195011690496 GToolkit: - Diagrammer is a new engine for drawing diagrams based on Bloc. This is the first version, and we will continue working on it in the following weeks, so stay tuned for more news. This is also one of the first Bloc applications: https://twitter.com/feenkcom/status/972243179599794180 - Andrei put together a beautiful description of a scenario in which an application is molded interactively in the Playground & Inspector. The subject is face recognition, and the resulting code is both functional and explainable. This is intended as a tutorial material that shows what moldable development means and how it changes the way we program: https://twitter.com/feenkcom/status/972907051448979458 Have fun, The feenk team www.feenk.com -- www.tudorgirba.com www.feenk.com "To utilize feedback, you first have to acquire it."

2 1