Serious problem with ConfigurationOfBootstrap - Error: Apparent loop in import expansion
Hello, The load of the 0.12.2 version gives a error. Quite annoying as Boostrap is quite needed for webdev :-( What changed? Loading 0.12.2 of ConfigurationOfBootstrap...'Errors in script loaded from /Users/philippeback/project/BuildBaseWorker.st' Error: Apparent loop in import expansion MetacelloVersionConstructor(Object)>>error: MetacelloVersionConstructor>>collectAllVersionsFromVersionImportPragmasInto:using:satisfiedPragmas: MetacelloVersionConstructor>>calculate:project: MetacelloVersionConstructor>>on:project: in Block: [ :cache | ... MetacelloPharo30Platform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: in Block: [ :dict | ... MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [ ^ aBlock value: dict ] BlockClosure>>on:do: MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: MetacelloPharo30Platform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: MetacelloPharo30Platform(MetacelloPlatform)>>stackCacheFor:at:doing: MetacelloVersionConstructor>>on:project: MetacelloVersionConstructor class>>on:project: ConfigurationOfSeaside3>>project MetacelloMCProjectSpec>>projectClassProject MetacelloMCProjectSpec>>version MetacelloMCProjectSpec(MetacelloProjectSpec)>>versionOrNil in Block: [ self version ] BlockClosure>>on:do: MetacelloMCProjectSpec(MetacelloProjectSpec)>>versionOrNil MetacelloMCProjectSpec>>loadPackageList MetacelloMCVersion>>packageAndProjectNamesToLoad:loader: in Block: [ :prj | ... OrderedCollection>>do: MetacelloMCVersion>>packageAndProjectNamesToLoad:loader: MetacelloMCVersion>>defaultPackageNamesToLoad: MetacelloMCVersion>>doLoadRequiredFromArray: in Block: [ ... BlockClosure>>ensure: MetacelloMCVersion>>doLoadRequiredFromArray: MetacelloMCVersion>>load GoferMetacelloLoad>>loadConfiguration GoferMetacelloLoad>>execute Gofer>>execute:do:
Hi Phil, Â nothing I can reproduce here. I tried with the latest/fresh Pharo 3.0 (build 30858) image. No problem to load from script or config browser. Also CI is green. Are you already using Pharo 4.0? Then it might be related that the prerequisite Seaside version may be not yet be ready/supported for Pharo 4.0. https://ci.inria.fr/pharo-contribution/job/Pharo4Seaside/ Bye T.
It turned out that the problem appeared randomly on various configurations and the cause is possibly a low memory condition. Also possible is an instable smalltalkhub. The problems were blocking us for a while with no clear cause. That is quite annoying. Phil Le 12 oct. 2014 21:35, "Torsten Bergmann" <astares@gmx.de> a écrit :
Hi Phil,
nothing I can reproduce here. I tried with the latest/fresh Pharo 3.0 (build 30858) image. No problem to load from script or config browser. Also CI is green.
Are you already using Pharo 4.0? Then it might be related that the prerequisite Seaside version may be not yet be ready/supported for Pharo 4.0. https://ci.inria.fr/pharo-contribution/job/Pharo4Seaside/
Bye T.
participants (2)
-
phil@highoctane.be -
Torsten Bergmann