- Moose-dev - INF Mailman

Jenkins build became unstable: moose-latest-dev-4.8 #1165

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1165/>

11 years, 9 months

1
0
0 0

Confused by ConfigurationOfGrease

by Stéphane Ducasse

Hi in my project I defined on Pharo2.0 I did project: 'Grease Core' with: [ spec className: 'ConfigurationOfGrease'; loads: #('Core' ); file: 'ConfigurationOfGrease'; repository: 'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main' ]; Now it loads Grease-Core.pmm.76 and not Name: Grease-Core-MattSpr.77 which correctly handles trim extension.. I tried (ConfigurationOfGrease project version: #stable) record a MetacelloNullRecordingMCSpecLoader(linear load : linear load : 1.0.8 [ConfigurationOfGrease] load : ConfigurationOfRefactoringBrowser linear load : 1.0.8 [ConfigurationOfGrease] load : Grease-Core-pmm.72 load : Grease-Pharo20-Core-pmm.1 load : Grease-Slime-topa.15) So I thought that it woudl be better. I tried so change my configuration to load the "stable" version project: 'Grease Core' with: [ spec className: 'ConfigurationOfGrease'; loads: #('Core' ); versionString: #stable; file: 'ConfigurationOfGrease'; repository: 'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main' ]; and it crashed on me. Grease-Pharo20-Core.pmm.1 GRDelegatingStream is not there. So is there a version loading well (without dirty packages) in Pharo2.0? I tried to use the development version and I still dirty packages……. Thanks Stef

11 years, 9 months

1
0
0 0

Testing moose (roassal)

by Diego Lont

Hi all, We are checking the build server for failed tests, checking what the problem is: I found problems in Glamour. It used a wrong symbol in its configuration, that caused CollectionExtensions not to load. It caused test fails in GToolkit. I found problems with method categories. There are some tests, that are more or less roassal tests, or at least use roassal, so do not belong in Moose-Algos. I think some methods should be moved to *roassal-paintings … or maybe *roassal-moose-algos and the tests should move along with them. I cannot write in roassal, if someone gives me a good method category and write access to roassal, I will move these methods. I found failed tests in Orion, but it looks like we caused them with our change in moose entity, so I will take a closer look and fix it, or write another mail. Cheers, Stephan and Diego

11 years, 9 months

4
9
0 0

Jenkins build became unstable: moose-latest-dev-4.8 #1153

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1153/>

11 years, 9 months

1
1
0 0

Jenkins build became unstable: moose-latest-dev-4.8 #1151

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1151/>

11 years, 9 months

1
1
0 0

Initial size of MooseGroupRuntimeStorage?

by Stephan Eggermont

MooseGroupRuntimeStorage >initialize: capacity byType := Dictionary new: 24. byName := IdentityDictionary new: 10000. elements := OrderedCollection new: capacity byName seems a bit excessive/inflexible. Stephan

11 years, 9 months

2
1
0 0

Re: Testing moose (roassal)

by Stephan Eggermont

Alexandre wrote: > Problem: Some packages related to the Algorithm have wrongly packaged dependencies. This create problem when these algos are loaded and not Roassal. > > A solution to this problem: > 1 - I've open a Moose panel, imported all the packages that match *Algo* and *Roassal-* > 2 - Open a Roassal easel on the model packages and do it the following visualization: Beautiful! I've learned something today. Stephan

11 years, 9 months

1
0
0 0

Jenkins build became unstable: moose-latest-dev-4.8 #1145

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1145/>

11 years, 9 months

1
1
0 0

GraphET x-axis label - bug?

by Usman Bhatti

Hello, I am starting to use GraphET and looks really nice. While learning to script with it, I stumbled upon this script that does not place x-axis label in the correct place. In fact the x-axis label is superimposed on y-axis one. Here's how you can reproduce it: tmpBrowser := GLMDashboard new. tmpBrowser addPaneNamed: #first. tmpBrowser transmit to: #first; andShow: [:a | a graphET title: 'First Chart with ET'; chart: [:chart :mooseModel| chart verticalBarDiagram models: (1 to: 3); xAxisLabel: 'Test label'; yAxisLabel: 'Another'; regularAxis. ]. ]. tmpBrowser openOn: 1

11 years, 9 months

2
4
0 0

Duplicate packages

by Diego Lont

Hi All, I found a stray package "collectionextensions" version 32 in the moose repository, while the most recent (and referenced in the configuration) package is version 34 in the folder Moose/CollectionExtensions. Any objections if I remove this package? Cheers, Diego

11 years, 9 months

1
0
0 0

Jenkins build is back to stable : moose-latest-dev-4.8 #1140

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1140/>

11 years, 9 months

1
0
0 0

Re: flushGroups called too often?

by Stephan Eggermont

Isn't it possible to update the cache instead of flushing it? Or is it only supposed to be a very local (in time) cache? Stephan

11 years, 9 months

1
0
0 0

Build failed in Jenkins: moose-latest-dev-4.8 #1138

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1138/> ------------------------------------------ [URLTrigger] A change within the response URL invocation (log) Building remotely on moose-ubuntu1204-dualproc-i386 in workspace <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/> Deleting project workspace... done [moose-latest-dev-4.8] $ /bin/sh -xe /tmp/hudson3019283886616803656.sh + + bash wget --quiet -O - http://get.pharo.org/20+vmLatest Downloading the latest 20 Image: http://files.pharo.org/image/20/latest.zip Pharo.image Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/latest.zip pharo-vm/pharo Downloading PharoV10.sources: http://files.pharo.org/sources//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/sources//PharoV20.sources.zip Creating starter scripts pharo and pharo-ui + ./pharo Pharo.image save moose-latest-dev-4.8 + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main + ./pharo moose-latest-dev-4.8.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development [31m[33m =============================================================================== Notice: Installing ConfigurationOfMoose development =============================================================================== [0m[0m[31m==== Startup Error: Error: Name not found: Core [0mMetacelloMCVersionSpec(Object)>>error: MetacelloMCVersionSpec>>resolveToLoadableSpec:forMap:packages: in Block: [^ self error: 'Name not found: ' , aString] MetacelloMCVersionSpec>>packageNamed:forMap:ifAbsent: MetacelloMCVersionSpec>>resolveToLoadableSpec:forMap:packages: MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: in Block: [:req | (self... Set>>do: MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: MetacelloMCVersionSpecLoader>>resolveToLoadableSpecs MetacelloMCVersionSpecLoader>>load MetacelloMCVersion>>executeLoadFromArray: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [:dict | ^ self executeLoadFromArray: anArray] MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] BlockClosure>>on:do: MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [self versionSpec loader: newLoader.... BlockClosure>>ensure: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [[self versionSpec loader: newLoader.... MetacelloPharoPlatform>>do:displaying: in Block: [aBlock value] BlockClosure>>ensure: RPackageSet class>>withCacheDo: MetacelloPharoPlatform>>do:displaying: in Block: [:bar | ... BlockClosure>>cull: Job>>run in Block: [result := block cull: self] BlockClosure>>on:do: Job>>run in Block: [self prepareForRunning.... BlockClosure>>ensure: Job>>run NonInteractiveUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressFrom:to:during: MetacelloPharoPlatform>>do:displaying: [0m[31mGot startup errors: [0m[31m Error: Name not found: Core [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

11 years, 9 months

1
0
0 0

flushGroups called too often?

by Stephan Eggermont

MooseAbstractGroup>add: anItem self entityStorage add: anItem. self privateState flushGroups. ^ anItem Why is the privateState not updated? Stephan

11 years, 9 months

2
1
0 0

Jenkins build became unstable: moose-latest-dev-4.8 #1136

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1136/>

11 years, 9 months

1
0
0 0

Changes to Famix-Core, Moose-Core & Moose-MonticelloImporter safe?

by Stephan Eggermont

When trying to walk smalltalkhub and import latest versions to find invocations, we needed to make the following changes to make it work: FAMIXAccess>variable: aStructuralEntity (aStructuralEntity isKindOf: FAMIXAnnotationInstanceAttribute) ifFalse: [ variable := FMMultivalueLink on: self update: #incomingAccesses from: self variable to: aStructuralEntity] Add MooseMonticelloVisitor>visitScriptDefinition: aMCPostscriptDefinition "TODO" MooseMonticelloHTTPImporter>setRepositoryCache: aCache. repositoryCache := aCache MooseMonticelloMethodPopulator>ensureAnnotationType: aRBPragmaNode ^self importer ensureAnnotationType: aRBPragmaNode. And change for performance: MooseGroupRuntimeStorage>add: anElement | key group | key := anElement class. group := byType at: key ifAbsentPut: [ OrderedCollection new ]. group add: anElement. elements add: anElement. byName at: anElement mooseName asSymbol put: anElement. ^ anElement MooseGroupRuntimeStorage >at: uniqueName ifAbsent: exceptionBlock | entity na | na := uniqueName asSymbol. "look first by name and if not found" entity := byName at: na ifAbsent: [nil]. entity notNil ifTrue: [ entity mooseName asSymbol = na ifTrue: [ ^entity] ifFalse: [ byName at: na put: nil. byName at: entity mooseName asSymbol put: entity. self halt. "Should this be happening?" ]]. ^ exceptionBlock value Would they be safe to commit?

11 years, 9 months

3
4
0 0

Namespace tree calculation for java

by Stephan Eggermont

This looks like a rather slow way to calculate a namespace tree. I'm pretty sure it can be done in such a way that a Task is not needed. MooseModel>inferNamespaceParentsBasedOnNames <menuItem: 'Infer Namespace Parents Based on Names' category: 'Utilities'> | parent parentNameSize currentPosition parentName namespaces | namespaces := self allNamespaces. MooseCustomTask new with: [:task | namespaces do: [ :each | currentPosition := 1. each name: (each name copyReplaceAll: '.' with: '::'). [ currentPosition := each name indexOf: $: startingAt: currentPosition. currentPosition isZero not ] whileTrue: [ parentName := (each name copyFrom: 1 to: currentPosition - 1) asSymbol. namespaces detect: [ :x | parentName = x mooseName ] ifNone: [ | newNamespace | newNamespace := FAMIXNamespace new name: parentName. namespaces add: newNamespace. self add: newNamespace ]. currentPosition := currentPosition + 2 ]. task increment]. namespaces do: [ :each | each belongsTo isNil ifTrue: [ parentNameSize := (each name lastIndexOf: $:) - 2. parentNameSize > 0 ifTrue: [ parent := namespaces detect: [ :x | (each name copyFrom: 1 to: parentNameSize) asSymbol = x mooseName ] ifNone: [ nil ]. parent isNil ifFalse: [ each name: (each name copyFrom: parentNameSize + 3 to: each name size) asSymbol. each parentScope: parent ] ] ]. task increment] ] description: 'Infer namespace parents based on names' length: (namespaces size * 2); runWithProgress. ^ self allNamespaces

11 years, 9 months

2
1
0 0

Jenkins build is back to stable : moose-latest-dev-4.8 #1129

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1129/>

11 years, 9 months

1
0
0 0

Jenkins build became unstable: moose-latest-dev-4.8 #1127

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1127/>

11 years, 9 months

2
1
0 0

Re: Changes to Famix-Core, Moose-Core & Moose-MonticelloImporter safe?

by Stephan Eggermont

I wrote: >FAMIXAccess>variable: aStructuralEntity > (aStructuralEntity isKindOf: FAMIXAnnotationInstanceAttribute) ifFalse: [ > variable := FMMultivalueLink on: self > update: #incomingAccesses > from: self variable > to: aStructuralEntity] Dory wrote: >This is strange. Why do you need that? We tried to do findDeprecationsFor: aVersion in: aProject | mooseModel | mooseModel := (MooseMonticelloHTTPImporter new setRepositoryCache: aProject monticelloRepository; importFileNamed: (aVersion at: #filename)). mooseModel allInvocations do: [ :each| aProject addInvocation: each inVersion: aVersion ]

11 years, 9 months

1
0
0 0

Snapshot Release

by Diego Lont

Hi all, I like moose a lot, but I have a problem with the way the moose configurations are used. So I would like to discuss this on the developers list. I would like to know if more people experience these problems. First of all, I like the way the development works out. All development configurations simply do not use any version numbers, and therefor return the latest version. Maybe we should create an actual development version, that is empty, except for the packages we want to be a fixed version. But this is a minor point. But once moose is released, a snapshot is taken, it is no longer a proper configuration. Main drawback is that all groups and such are removed. But also referred configurations are no longer used. I believe it should be possible to upgrade to the stable version of a configuration in the place where a development version was used. Especially when the development version is released. Taking snapshots prevents this, since it no longer contains groups. Also I think that bug fixes of used configurations should be imported automatically. Taking snapshots prevents this, since they do not use used configurations. Finally there is a scenario that actually breaks configurations downstream. When I load version 1.6-baseline of PetitParser and sub sequentially ask for the current version, it returns 1.7-snapshot. But since I try to load the 'Core' group of PetitParser, I can no longer use my configuration. It simply halts on the error that the group 'Core' could not be found. I have two suggestions to improve the process: > We either choose to stick to snapshots for the releases, since this is a very reliable way to reproduce a build (with all known bugs). But for this we create a class SnapshotOf<projectname>, for each project, with all the methods needed, to indicate it is not a configuration. We could add previous releases to this class. > We create a proper stable version, in the way configurations are meant to be. We bless these methods with release and only update versions if it is a bug fix. We also create a new development version at the moment we make the release, so we can continue development, without breaking the release For the last suggestion I have updated my Metaceller tool (part of GToolkit). It is still beta, but it produces proper release version for a single configuration, based on the current state of the image. Regards, Diego

11 years, 9 months

1
0
0 0

Make edges not clickable in Roassal visualization from within a Glamour browser

by Damien Cassou

Please answer at: http://stackoverflow.com/questions/18829093/make-edges-not-clickable-in-roa… -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

11 years, 9 months

4
5
0 0

MooseGroupRuntimeStorage implementation

by Stephan Eggermont

While trying to import some monticello packages from smalltalkhub with a MooseMonticelloHTTPImporter, we noticed some less nice behavior from the MooseGroupRuntimeStorage. at: ifAbsent is really slow when byName contains 128 elements and elements 64K. What is the usecase for putting the elements in an OrderedCollection? Doing byName at: anElement mooseName asSymbol put: anElement. in add: makes it perform a lot better. Is there a usecase where you don't want byName to be filled immediately? Diego & Stephan

11 years, 9 months

1
0
0 0

MooseDay - any news?

by Andrei Vasile Chis

Hi, Will the moose day still take place? If yes is the date fixed? Cheers, Andrei

11 years, 9 months

6
7
0 0

Roassal 3D

by Usman Bhatti

Hi Alex, I would like to play a bit with Roassal 3D, I'm looking for a link to load and run my first examples ;). tx. Usman

11 years, 9 months

2
3
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev