- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #588: 21386-Use-better-name-for-Literal-variable-binding-that-is-used-for-MetaLinks

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

There is a new Pharo build available! The status of the build #588 was: FAILURE. The Pull Request #927 was integrated: "21386-Use-better-name-for-Literal-variable-binding-that-is-used-for-MetaLinks" Pull request url: https://github.com/pharo-project/pharo/pull/927 Issue Url: https://pharo.fogbugz.com/f/cases/21386 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 21, 2018

Metacello/Iceberg Error: IceUndefinedRemote DNU #projectPath

by Sean P. DeNigris

I was loading a project via: Metacello new baseline: 'BabyPhexample'; repository: 'github://seandenigris/Baby-Phexample/repository'; onConflict: [ :ex | ex allow ]; load. into a Moose 6.1 image obtained from Launcher which already contained StateSpecs and got this: IceUndefinedRemote(Object)>>doesNotUnderstand: #projectPath IceMetacelloRepositoryAdapter>>projectPath IceMetacelloRepositoryAdapter>>hasNoLoadConflicts: MetacelloRepositorySpec>>hasNoLoadConflicts: MetacelloRepositoriesSpec>>hasNoLoadConflicts: MetacelloMCBaselineOfProjectSpec(MetacelloGenericProjectSpec)>>hasNoLoadConflicts: MetacelloMCBaselineOfProjectSpec(MetacelloMCProjectSpec)>>hasNoLoadConflicts: MetacelloMCBaselineOfProjectSpec(MetacelloProjectSpec)>>hasLoadConflicts: MetacelloMCBaselineOfProjectSpec(MetacelloMCProjectSpec)>>hasConflictWithBaselineSpec: MetacelloMCBaselineOfProjectSpec>>hasConflictWithProjectSpec: MetacelloProjectRegistration>>hasLoadConflicts: Ideas? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 21, 2018

[Pharo 7.0-dev] Build #587: 21384-Make-non-ensure-wrapped-after-the-default-for-message-sends

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

There is a new Pharo build available! The status of the build #587 was: SUCCESS. The Pull Request #925 was integrated: "21384-Make-non-ensure-wrapped-after-the-default-for-message-sends" Pull request url: https://github.com/pharo-project/pharo/pull/925 Issue Url: https://pharo.fogbugz.com/f/cases/21384 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 21, 2018

[Pharo 7.0-dev] Build #586: 21383-installed-metalinks-should-be-ordered

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

There is a new Pharo build available! The status of the build #586 was: SUCCESS. The Pull Request #924 was integrated: "21383-installed-metalinks-should-be-ordered" Pull request url: https://github.com/pharo-project/pharo/pull/924 Issue Url: https://pharo.fogbugz.com/f/cases/21383 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 21, 2018

Re: [Pharo-dev] CodeExporter doesn't

by Alistair Grant

On 21 February 2018 at 11:43, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Everyone, > > Attempting to file out changes from the Change Sorter results in an > 'Improper store into indexable object'. (To reproduce this, right click > on any change set and choose "File out"). > > I believe the root cause of the problem is: > > CodeExporter class>>writeSourceCodeFrom: aStream toFileReference: aFileReference > > aFileReference writeStreamDo: [ :outputStream | > (ZnCrPortableWriteStream on: (ZnCharacterWriteStream > on: outputStream > encoding: 'utf8')) nextPutAll: aStream contents. > ]. > > self inform: 'Filed out to: ', String cr, aFileReference basename > > > ZnCrPortableWriteStream expects a binary stream and is being given a > multi-byte file stream. > > The obvious solution is to add FileReference>>binaryWriteStreamDo: and > associated methods. > > Can someone who is more familiar with the Zinc package confirm that my > understanding is correct? > > Fogbugz: https://pharo.fogbugz.com/f/cases/21381/CodeExporter-triggers-errorImproper… And if I'd bothered to read the class comments before posting, I wouldn't have wasted everyone's time. Using a binary write stream is the answer, according to the class comments. Sorry, Alistair

Feb. 21, 2018

CodeExporter doesn't

by Alistair Grant

Hi Everyone, Attempting to file out changes from the Change Sorter results in an 'Improper store into indexable object'. (To reproduce this, right click on any change set and choose "File out"). I believe the root cause of the problem is: CodeExporter class>>writeSourceCodeFrom: aStream toFileReference: aFileReference aFileReference writeStreamDo: [ :outputStream | (ZnCrPortableWriteStream on: (ZnCharacterWriteStream on: outputStream encoding: 'utf8')) nextPutAll: aStream contents. ]. self inform: 'Filed out to: ', String cr, aFileReference basename ZnCrPortableWriteStream expects a binary stream and is being given a multi-byte file stream. The obvious solution is to add FileReference>>binaryWriteStreamDo: and associated methods. Can someone who is more familiar with the Zinc package confirm that my understanding is correct? Fogbugz: https://pharo.fogbugz.com/f/cases/21381/CodeExporter-triggers-errorImproper… Thanks! Alistair

Feb. 21, 2018

Re: [Pharo-dev] [ANN] Pharo Sprint Feb 23

by Marcus Denker

Hi, As a starting point, I put the sprint tag on some cases (which should be easy to do): https://pharo.fogbugz.com/f/filters/44/Sprint > On 20 Feb 2018, at 08:44, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Pharo Sprint Feb 23 > https://association.pharo.org/event-2789568 > > > For a list of all future Pharo Event, have a look at: https://association.pharo.org/events > (you can get iCal entries and subsribe to an event specific mailinglist bu registering) > > Marcus

Feb. 21, 2018

[Pharo 7.0-dev] Build #585: 21378-Distribute-Timeout-in-the-steps

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

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

Feb. 21, 2018

Re: [Pharo-dev] [Pharo 7.0-dev] Build #584: 19250-no-senders-of-ObjectmustBeBooleanIn

by Marcus Denker

> On 21 Feb 2018, at 08:16, ci-pharo-ci-jenkins2(a)inria.fr wrote: > > There is a new Pharo build available! > > The status of the build #584 was: FAILURE. > > The Pull Request #919 was integrated: "19250-no-senders-of-ObjectmustBeBooleanIn" > Pull request url: https://github.com/pharo-project/pharo/pull/919 > > Issue Url: https://pharo.fogbugz.com/f/cases/19250 > Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… "Resume after a restart not supported for non-blocking synchronous stepsâ No ideaâ¦ the build just before worked. Marcus

Feb. 21, 2018

[Pharo 7.0-dev] Build #584: 19250-no-senders-of-ObjectmustBeBooleanIn

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

There is a new Pharo build available! The status of the build #584 was: FAILURE. The Pull Request #919 was integrated: "19250-no-senders-of-ObjectmustBeBooleanIn" Pull request url: https://github.com/pharo-project/pharo/pull/919 Issue Url: https://pharo.fogbugz.com/f/cases/19250 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 21, 2018