Hi,
I just wanted to know why the today Moose 6.1 jenkins jobs are failing : https://ci.inria.fr/moose/job/moose-6.1
It seems that someone changed the configuration to load iceberg :
./pharo $JOB_NAME.image eval "Metacello new \
baseline: 'Iceberg'; \
repository: 'github://npasserini/iceberg'; \
load. \
IceRepository defaultBackendType: IceLibgitLocalRepository. \
Smalltalk snapshot: true andQuit: true."
What is the status ?
Cheers,
Vincent
!!!*************************************************************************************
"Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"
Hi,
has anybody done anything with bug analysis in Pharo? I know that the most common approach is to see in which version an issue was closed and what code was changed and when was that code introduced and as the result you have lifespans of bugs.
Other suggestions are also welcome :)
Uko
----- Forwarded message -----
Hi,
Is it possible to configure the position of the GTDebugger panes to the previous version:
( http://humane-assessment.com/pierfiles/9e/kmq3rz0d783ks2m12lot6qg34ow8kd/gt… )
With the variables pane being a bit taller.
I remember that some people didn’t like this layout, that’s why I am asking whether it can be configured (for people that want to use this layout).
Thanks,
Peter
Hi,
Indeed, I forgot about this one. I would like to add this in Moose because it looks quite handy.
Cheers,
Doru
> On Nov 7, 2016, at 2:35 PM, stepharo <stepharo(a)free.fr> wrote:
>
> Thanks!
>
>
>
> Le 7/11/16 à 12:37, Sven Van Caekenberghe a écrit :
>> This is very nice:
>>
>> http://smalltalkhub.com/#!/~emaringolo/SortFunctions
>>
>>> On 7 Nov 2016, at 12:25, stepharo <stepharo(a)free.fr> wrote:
>>>
>>> Hi
>>>
>>> I know that "steffen" did a nice library to sort objects and I know that this is a nice extension.
>>>
>>> But I cannot find it.
>>>
>>> Stef
>>>
>>>
>>
>>
>
>
--
www.tudorgirba.comwww.feenk.com
"Every thing has its own flow."
Hi,
I am playing a bit with RTMondrian and I cannot seem to be able to connect nested nodes. I am trying this:
view := RTMondrian new.
view nodes: (1 to: 2) forEach: [ :each |
view node: each * 10 ].
view edges source: {10->20} connectFrom: #key to: #value.
view
Given the advanced time, it might well be that I am missing something obvious. Or is it a regression?
Cheers,
Doru
--
www.tudorgirba.comwww.feenk.com
"We are all great at making mistakes."
Hello everyone,
We modified FAMIXImplicitVariable>>#parentBehaviouralEntity to add the pragma <container> (which declares that the parent entity contains this kind of entity).
We also modified FAMIXLocalVariable>>#parentBehaviouralEntity the same way.
However, some tests are now failing: https://ci.inria.fr/moose/job/moose-6.1/. But, we think that it is a correct change.
It appears that the problem can be summarized as:
Should #queryAllIncomingAssociations applied on a class give the internal associations?
If, yes: we just need to change the tests by adding; #withoutSelfLoops.
Else, we have to change FamixQuery.
What do you think about it?
Thanks in advance,
Cheers,
Vincent & Julien
!!!*************************************************************************************
"Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"
What to use for labeling a pie chart by a block:
| b |
b := RTPieBuilder new.
b objects: (1 to: 10).
b slice: [ :nr | nr squared ].
b normalizer distinctColor.
b labelled:[:i | i asWords].
b build.
b view
this will raise a deprecation warning, with the info I should use
#labelled: instead of #labelled:
:)
There is no method expecting a single block ?
Only labeledIf:withBlock: ?
nicolai
> Hi all, especially Luc, Stéphane and Damien,
>
> the Pharo MOOC course was fantastic and I use the archived material for
> reference quite a lot. It is here:
>
> https://www.fun-mooc.fr/courses/inria/41010/session01/b116d12e24ec484c98483…
>
> But - the English table of contents is in French, and the attached ZIP files
> need to be downloaded before they can be browsed. It gets quite messy. Would
> anyone with the required permissions be OK to:
>
> - translate the TOC to English
> - split the ZIP files into separate elements under their respective
> headlines that can be viewed in the browser
>
> or
>
> - grant me the permissions to do this work for the community?
Sure.
Let me know how I can help.
I will forward your mail to christelle that manages the mooc for us
Siemen
did you see the web portal
http://rmod-pharo-mooc.lille.inria.fr/MOOC/WebPortal/co/pharo.html (we
should add a pointer from http://mooc.pharo.org to it)
and also the http://mooc.pharo.org page? because we have the full
control on this one.
And this is on my todo to make sure that people can get an archive with
the complete mooc nicely packaged.
Now if you want to help it would be great.
Stef
>
> best,
> Siemen
>
>
>
> --
> View this message in context: http://forum.world.st/MOOC-TOC-cleanup-tp4921304.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>
>
