Hi Mircea, Yes, we encountered this before. The problem is due to a bug introduced in the RB traversal of VW 7.6. I will try to dig up the solution (it was in the VW mailing list and in this one just after 7.6 was introduced last year). Cheers, Doru On 20 May 2009, at 15:00, Mircea Lungu wrote: > Hi guys, > > I am using the last MooseConfig 1.28 from the bern Store on Visual > Works. > > I am trying to import moose and a few other systems in moose. The > parser fails when parsing some test methods in the (DynaMooseTests, > MooseUIExtensions, MetaTests). What all these methods have in > common is definitions of arrays like in the following example method: > > > ------------- > modelSpec > ^ > #(Moose.Model (entity > (FAMIX.Package (id: 1) (name P1)) > (FAMIX.Package (id: 2) (name P2) (packagedIn (idref: 1))) > (FAMIX.Class (id: 5) (name C5) (packagedIn (idref: 2))) > (FAMIX.Class (id: 6) (name C6) (packagedIn (idref: 2))) > (FAMIX.Class (id: 7) (name C7) (packagedIn (idref: 2))) > (FAMIX.Package (id: 3) (name P3) (packagedIn (idref: 1))) > (FAMIX.Class (id: 8) (name C8) (packagedIn (idref: 3))) > (FAMIX.Class (id: 9) (name C9) (packagedIn (idref: 3))) > (FAMIX.Class (id: 4) (name C4) (packagedIn (idref: 1))) > )) > > ------------- > > Did anybody encounter anything like this? If so, is there a patch > for it? > > Thanks, > Mircea. > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "It's not what we do that matters most, it's how we do it." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Thanks Doru, you're a wizard :) m. On May 20, 2009, at 8:20 PM, Tudor Girba wrote: > Hi Mircea, > > Ok, I found the problem report (if want to search for it look for > RBParser in the subject of mails, either on this on the vwnc mailing > list). > > I packaged the fix in the PatchForRBParserInVW76 package. It contains > one override of the offending method. > > Cheers, > Doru > > > On 20 May 2009, at 16:02, Tudor Girba wrote: > >> Hi Mircea, >> >> Yes, we encountered this before. The problem is due to a bug >> introduced in the RB traversal of VW 7.6. I will try to dig up the >> solution (it was in the VW mailing list and in this one just after >> 7.6 was introduced last year). >> >> Cheers, >> Doru >> >> >> On 20 May 2009, at 15:00, Mircea Lungu wrote: >> >>> Hi guys, >>> >>> I am using the last MooseConfig 1.28 from the bern Store on Visual >>> Works. >>> >>> I am trying to import moose and a few other systems in moose. The >>> parser fails when parsing some test methods in the (DynaMooseTests, >>> MooseUIExtensions, MetaTests). What all these methods have in >>> common is definitions of arrays like in the following example >>> method: >>> >>> >>> ------------- >>> modelSpec >>> ^ >>> #(Moose.Model (entity >>> (FAMIX.Package (id: 1) (name P1)) >>> (FAMIX.Package (id: 2) (name P2) (packagedIn (idref: 1))) >>> (FAMIX.Class (id: 5) (name C5) (packagedIn (idref: 2))) >>> (FAMIX.Class (id: 6) (name C6) (packagedIn (idref: 2))) >>> (FAMIX.Class (id: 7) (name C7) (packagedIn (idref: 2))) >>> (FAMIX.Package (id: 3) (name P3) (packagedIn (idref: 1))) >>> (FAMIX.Class (id: 8) (name C8) (packagedIn (idref: 3))) >>> (FAMIX.Class (id: 9) (name C9) (packagedIn (idref: 3))) >>> (FAMIX.Class (id: 4) (name C4) (packagedIn (idref: 1))) >>> )) >>> >>> ------------- >>> >>> Did anybody encounter anything like this? If so, is there a patch >>> for it? >>> >>> Thanks, >>> Mircea. >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> -- >> www.tudorgirba.com >> >> "It's not what we do that matters most, it's how we do it." >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > www.tudorgirba.com > > "Relationships are of two kinds: those we choose and those that > happen. They both matter." > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Indeed. But I guess we would have to wait until we get a new release to get the fix. Cheers, Doru On 21 May 2009, at 09:47, Stéphane Ducasse wrote: > I saw that the AR for 7.7 to fix this bug was done. > > Stef > > On May 20, 2009, at 10:34 PM, Mircea Lungu wrote: > >> Thanks Doru, >> you're a wizard :) >> >> m. >> >> On May 20, 2009, at 8:20 PM, Tudor Girba wrote: >> >>> Hi Mircea, >>> >>> Ok, I found the problem report (if want to search for it look for >>> RBParser in the subject of mails, either on this on the vwnc >>> mailing >>> list). >>> >>> I packaged the fix in the PatchForRBParserInVW76 package. It >>> contains >>> one override of the offending method. >>> >>> Cheers, >>> Doru >>> >>> >>> On 20 May 2009, at 16:02, Tudor Girba wrote: >>> >>>> Hi Mircea, >>>> >>>> Yes, we encountered this before. The problem is due to a bug >>>> introduced in the RB traversal of VW 7.6. I will try to dig up the >>>> solution (it was in the VW mailing list and in this one just after >>>> 7.6 was introduced last year). >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> On 20 May 2009, at 15:00, Mircea Lungu wrote: >>>> >>>>> Hi guys, >>>>> >>>>> I am using the last MooseConfig 1.28 from the bern Store on >>>>> Visual >>>>> Works. >>>>> >>>>> I am trying to import moose and a few other systems in moose. The >>>>> parser fails when parsing some test methods in the >>>>> (DynaMooseTests, >>>>> MooseUIExtensions, MetaTests). What all these methods have in >>>>> common is definitions of arrays like in the following example >>>>> method: >>>>> >>>>> >>>>> ------------- >>>>> modelSpec >>>>> ^ >>>>> #(Moose.Model (entity >>>>> (FAMIX.Package (id: 1) (name P1)) >>>>> (FAMIX.Package (id: 2) (name P2) (packagedIn (idref: 1))) >>>>> (FAMIX.Class (id: 5) (name C5) (packagedIn (idref: 2))) >>>>> (FAMIX.Class (id: 6) (name C6) (packagedIn (idref: 2))) >>>>> (FAMIX.Class (id: 7) (name C7) (packagedIn (idref: 2))) >>>>> (FAMIX.Package (id: 3) (name P3) (packagedIn (idref: 1))) >>>>> (FAMIX.Class (id: 8) (name C8) (packagedIn (idref: 3))) >>>>> (FAMIX.Class (id: 9) (name C9) (packagedIn (idref: 3))) >>>>> (FAMIX.Class (id: 4) (name C4) (packagedIn (idref: 1))) >>>>> )) >>>>> >>>>> ------------- >>>>> >>>>> Did anybody encounter anything like this? If so, is there a patch >>>>> for it? >>>>> >>>>> Thanks, >>>>> Mircea. >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> Moose-dev(a)iam.unibe.ch >>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "It's not what we do that matters most, it's how we do it." >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)iam.unibe.ch >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> -- >>> www.tudorgirba.com >>> >>> "Relationships are of two kinds: those we choose and those that >>> happen. They both matter." >>> >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "Sometimes the best solution is not the best solution." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Hi Guys (in Bern), How are you? I hope everything is ok. With Diego (cc in this email) we are trying to download the package Moose-Development from the UniBeStore. Unfortunately our 15000 km far from Bern :) are not an advantage for us (we tried from different connections: univ, private from our home, but we are stuck when we tried to load the package). Two solutions come to my mind: 1) How different is the moose version published in the distribution of VW NC from the version in developement in Bern? If no big differences, we can work with that one 2) Second option: we need a caritative soul :) that loads moose-development in a clean image and upload the image (with moose-development) temporarily in a website where we can download it ... Anyway, we are open to suggestions to our nice problem ... :) thanks for any tip or information ... Cheers, Gabi _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Mircea: there's a different problem in Argentina: latency. Does VW really make connections for each file it tries to download? The network over there goes at around 50kb/s but even then I do remember Moose to take about 3 hours to install on an empty image. And then I was told to reinstall it every day ... No to make it workable they should have their own synced version over there I think; or like you said, through image sharing rather than by using the repo. On (21/05/09 23:05), Mircea Lungu wrote: > From: Mircea Lungu <mircea.lungu(a)lu.unisi.ch&gt; > To: &quot;arevalo(a)iam.unibe.ch&quot; <arevalo(a)iam.unibe.ch&gt;, > Related to the development of Moose and other related tools > <moose-dev(a)iam.unibe.ch&gt; > Cc: Diego Kogan <diegokogan(a)gmail.com&gt; > Subject: [Moose-dev] Re: Help to access to Moose-Development > Date: Thu, 21 May 2009 23:05:24 +0200 > > Ciao Gabriela, > > Did you try to load Moose Config? I remember that at one point I > tried > to load MooseDevelopment itself and it seemed to take a very long > time. > > Alternatively, you can download the latest image of Softwarenaut, you > will have also the latest version of Moose Development included (as > it > they are loaded by Moose Config 1.28). You find it at > http://www.inf.unisi.ch/phd/lungu/softwarenaut/download/resources/snaut-3... > > Cheers, > Mircea. > > > On May 21, 2009, at 4:25 PM, Gabriela Arevalo wrote: > >> Hi Guys (in Bern), >> >> How are you? I hope everything is ok. >> With Diego (cc in this email) we are trying to download the package >> Moose-Development from the UniBeStore. >> Unfortunately our 15000 km far from Bern :) are not an advantage for >> us >> (we tried from different connections: univ, private from our home, >> but >> we are stuck when we tried to load the package). >> Two solutions come to my mind: >> 1) How different is the moose version published in the >> distribution of >> VW NC from the version in developement in Bern? >> If no big differences, we can work with that one >> >> 2) Second option: we need a caritative soul :) that loads >> moose-development in a clean image and upload the image (with >> moose-development) temporarily in a website where we can download it >> ... >> >> Anyway, we are open to suggestions to our nice problem ... :) >> >> thanks for any tip or information ... >> >> Cheers, >> >> Gabi >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev