Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Re: [Pharo-dev] Re: Segmentation fault on Moose 6.1 Build

by Tudor Girba

Hmm, it looks like something changed and the build is now yellow. Does anyone have the time to check this mysterious behavior? Cheers, Doru > On Mar 2, 2017, at 1:24 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > I will try to make some easier way to reproduce it and open an issue > > -- Pavel > > 2017-03-02 11:58 GMT+01:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > Hm, I haven't check the time of the failing build... Yes, it will be related... > > 2017-03-02 11:51 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > Except for tiny changes in Athens in 60419 :) > > Doru > > > > On Mar 2, 2017, at 11:33 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > > > On image side nothing relevant happened in 60418 where it started to fail. > > > > -- Pavel > > > > 2017-03-02 11:31 GMT+01:00 Blondeau Vincent <vincent.blondeau(a)worldline.com>: > > I heard that the gc compactor have changed. > > > > Cheers, > > Vincent > > > > > -----Message d'origine----- > > > De : Moose-dev [mailto:moose-dev-bounces@list.inf.unibe.ch] De la part de > > > Tudor Girba > > > Envoyé : jeudi 2 mars 2017 11:29 > > > À : Pharo Development List > > > Cc : Moose-related development > > > Objet : [Moose-dev] Re: [Pharo-dev] Segmentation fault on Moose 6.1 Build > > > > > > Hi, > > > > > > Was there a change related to the stable VM? > > > > > > Cheers, > > > Doru > > > > > > > > > > On Mar 2, 2017, at 11:23 AM, Blondeau Vincent > > > <vincent.blondeau(a)worldline.com> wrote: > > > > > > > > Hi, > > > > > > > > The latest builds of the Moose6.1 image are failing due to a segmentation > > > fault. > > > > Here is the link to the last build: > > > > https://ci.inria.fr/moose/job/moose-6.1/550/console > > > > > > > > How can we fix this? > > > > > > > > Thanks in advance, > > > > > > > > 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.!!!" > > > > <dump.txt> > > > > > > -- > > > www.tudorgirba.com > > > www.feenk.com > > > > > > “Live like you mean it." > > > > > > _______________________________________________ > > > Moose-dev mailing list > > > Moose-dev(a)list.inf.unibe.ch > > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > > > !!!************************************************************************************* > > "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.!!!" > > > > -- > www.tudorgirba.com > www.feenk.com > > "Yesterday is a fact. > Tomorrow is a possibility. > Today is a challenge." > > > > > > > -- www.tudorgirba.com www.feenk.com "Beauty is where we see it."

8 years, 1 month

Google Summer of Code 2017: Call for students for Pharo Consortium

by Serge Stinckwich

*** Please forward this message to students that might be interested *** Heartiest Congratulations ! Pharo Consortium has been selected as a mentor organisation for Google Summer of Code 2017. Google Summer of Code is a global program focused on introducing students to open source software development. Students work on a 3 month programming project with an open source organisation during their break from university. Read more at https://summerofcode.withgoogle.com/ Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback (think IDE and OS rolled into one). Everything in Pharo is an object. The entire syntax of Pharo fits on a postcard coding can be done directly in the debugger. Pharo has super cool tools that empower you and make you super efficient. Pharo's goal is to deliver a clean, innovative, free and open-source immersive environment. By providing a stable and small core system, excellent developing tools, and maintained releases, Pharo is an attractive platform to build and deploy mission critical applications. Pharo fosters a healthy ecosystem of both private and commercial contributors who advance and maintain the core system and its external packages. More information about Pharo is available here: http://www.pharo.org/ We invite all the prospective eligible students to code their summer away with Pharo Consortium. Student Responsibilities ...to your Mentor - Submit quality work - Regularly communicate work completed, what you intend to do next, and blockers - Ask for help when something is preventing you from achieving a goal - Give indication that you are alive and working daily (GSoC) - Re-evaluate work scope when significantly ahead of expectations (GSoC) - Communicate with your mentor AND the broader community - Inform when work capacity will be reduced, as early as possible (e.g., family, health, other work) (GSoC) - Listen and respond to feedback ...to the Org Admin Let them know when there are - Interaction issues with any mentor or community member - Significant disagreements involving your work or changes to your work plan Read more about responsibilities here: https://developers.google.com/open-source/gsoc/help/responsibilities Hence, we invite enthusiastic student developers contributors to work with Pharo Consortium for GSoC 2017. 1. A first list of projects are available here : http://gsoc.pharo.org/ but more can be found by interacting with mentors from the Pharo community. 2. Join dedicated channels, #gsoc-students for general interactions with students on Pharo slack. In order to get an invitation for pharoproject.slack.com visit the URL here: http://slackinvites.pharo.org/ Discuss with mentors about the complexity and skills required for the different projects. 3. Please help fix bugs, open relevant issues, suggest changes, additional features, help build a roadmap, and interact with mentors on mailing list and/or slack to get a better insight into projects. Better the contributions, Better are the chances of selection. Before applying: * Knowledge about OOP * Basic idea about Pharo & Smalltalk syntax and ongoing projects * Past experience with Pharo & Smalltalk * Interaction with organisation You can start with the Pharo MOOC : http://files.pharo.org/mooc/ Guidelines for Proposal: * Introduction: Clearly defined problem. Current state of things. Issues you wish to solve and why. Conclude with solution. * Project goals: Format it like a list. Propose a clear list of deliverables, explaining exactly what you promise to do and what you do not plan to do. “Future developments” can be mentioned. It is better to promise less and deliver more than to promise a lot and then fall short. * Implementation: Longer and more detailed. Provide technical details, show that you understand the technology and illustrate key technical elements of your proposed solution. * Timeline: Make it weekly. Set goals for each week. Be upfront about other commitments, including exams, classes, travel, internships, jobs, etc. * Benefits to Community: Make your case a benefit to the organization. * Related Work: Research and write how the project fits into the target organization. Explain related works, similarities & differences. * About me: Provide full contact information, email addresses, websites, IRC nick, postal address and telephone. Write a few sentences about yourself, previous experiences and why you think you’re the best for this job. Submit your proposal early. Keep it short. Include necessary information. Get it reviewed in the mailing list or Slack channel before submitting it. The deadline for submitting your proposal is March 20th to April 3rd on https://summerofcode.withgoogle.com/ Looking forward to great talent joining our organisation this summer. Warm Regards Pharo Organisation Admins (Alexandre Bergel, Jigyasa Grover, Serge Stinckwich & Yuriy Tymchuk)

8 years, 1 month

Roassal examples browser - too many items

by Ben Coman

Just some quick feedback... in the "Moose Suite 6.0 (beta)" image from PharoLauncher I opened World > Roassal > Roasasal Examples Nice interface, but for the category "Grapher - Overall" I find there are too many items, such that even the text labels are too small to read. It might be better to split this out to a few more categories. cheers -ben

8 years, 1 month

ElasticBoxZoom

by Ben Coman

I loaded Roassal into Pharo 60411 and tried #exampleElasticBoxZoom. I select a major portion of the graph, but it zooms down onto one of the tiny axis tick-marks. Is there an issue tracker that is a better place to report this? cheers -ben P.S. I was trying to run Moose 6.0 (beta) from Pharo Launcher on top of a recent VM Feb 22 2017. It was locking up and crashing and I wasn't sure how the versions aligned, so switching to loading Roassal from catalog into 60411 has been running fine.

8 years, 1 month

GTInspector duplicates overriden extensions

by Peter Uhnak

Hi, when I override a method with a GTInspector (because I need to change it), then inspector contains the extension twice. It seems Inspector scans the whole hierarchy of the inspected object for methods, but doesn't deduplicate them. Peter

8 years, 1 month

CK metrics from Moose? (was Re: Publications of projects using Moose?)

by Cris Fuhrman

Hello! I'm wondering if it's in the scope of Moose to get to the standard CK metrics for a model? It seems it's been done experimentally ( https://pdfs.semanticscholar.org/0eb2/14ec7c6288dc13564580beafc2609b09118b.…) and I also found the momfe paper from 2002 ( http://scg.unibe.ch/archive/projects/Bute02a.pdf) but appeared not to have all the CK metrics. I also found the right-click on a Moose Model -> Export -> Export model to MSE, but there was nothing that looked like standard CK metrics in the exported file. We are particularly trying to generate CBO (for a research comparison) for a few classes and would like to be able to do all our work in Moose if possible (especially with the visualizations in a RTView). Cheers, C. Fuhrman On Wed, Oct 5, 2016 at 11:58 AM, Hernán Morales Durand < hernan.morales(a)gmail.com> wrote: > Hi guys, > > Do you have good reference links to publications (yours or from other > people) which uses Moose metrics for example in a "Material and Methods" > section? > > I mean *not* Moose projects publications (projects derived from Moose), > but those projects which uses Moose analysis to report Cyclomatic > Complexity, Halstead Length, WMC, DIT, CBO, etc . I want to see what and > how people reports metrics for a software project using Moose. If > publication is in a Journal outside of the field of Software Engineering > field that would be better. > > Cheers, > > Hernán > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > >

8 years, 1 month

Position of #numberOfLinesOfCode in hierarchy

by Cyril Ferlicot D.

Hello everyone, I found something I find odd today. The method #numberOfLinesOfCodes is defined on the Behavioral entities. I would have expected it on the Sourced entities because if an entity has sources it should have a number of lines of code. What do you think? -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France

8 years, 1 month

How ready is Bloc for a simple use-case?

by Peter Uhnak

Hi, I wanted to ask about Bloc: 1) how stable is the API? e.g. if some overhaul changes to unify/whatever are planned 2) I saw in the techtalk that you can align elements (to center, bottom, ...), however is that possible with lines? Lines have to rotate, morph shape, etc. 3) Are non-straight lines possible? (e.g. bezier, arc) The idea for me is to make a simple mindmap - elements with some text, icons, math symbols inside - connectors (non-straight lines) between elements To me (apart from the lines) it seems like it should be already doable. Also either my (Morphic) Pharo is really slow, or Bloc (in the video) is superfast (everything is happening instantly). Thanks, Peter

8 years, 1 month

Cannot inspect Hashtable anymore

by Blondeau Vincent

Hello, I am currently working with Hashtable which is loaded by default in the Moose image. With the latest image, I tried to do: (HashTable new at: #a put:1;yourself) inspect. And I got an inspector with the red square of death... It seems that the visualization wants to get the item at the position 1 in the Hashtable but it cannot succeed because there is no item at 1 (obviously, it is an hashtable). Can someone with GtTools knowledge take a look at that? Thanks in advance, 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.!!!"

8 years, 1 month

RTForceBasedLayout without overlapping arbitrary shapes

by Cris Fuhrman

Hello, Here's an example code using RTForceBasedLayout (from an example on this list a while back): ------------ view := RTView new. objects := RTObject withAllSubclasses. elements := (RTBox new size: #numberOfMethods; color: (Color blue alpha: 0.5)) elementsOn: objects. elements @ RTPopup new. view addAll: elements. RTForceBasedLayout on: elements. view @ RTDraggableView . view open ------------ It produces: [image: Inline image 1] Is it possible to have the RTForceBasedLayout such that the result has no overlapping boxes (or rectangles)? I realize setting force: to some large negative number will help, but it's not ideal because it creates a lot of empty space. In d3 (with SVG) there are a couple of examples of what I'd like to achieve (although they don't show edges): https://bl.ocks.org/mbostock/1062383 (arbitrary shapes) https://bl.ocks.org/mbostock/3231298 (arbitrary circles that stick to each other) The animation isn't important in my case. I wasn't sure where/how to apply the transform operation after a layout has been done in RTForceBasedLayout. Any hints? Here's what my graph looks like: [image: Inline image 2] The code I have to produce this is too much to post, so I used the example at the top. My code also uses RTForceBasedLayout new charge: -1000; on: b elements. Cheers!

8 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev