March 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Pharo by example 5.0 is officially released and available

by Dimitris Chloupis

Awesome ;) On Fri, 10 Mar 2017 at 21:55, stepharong <stepharong(a)free.fr> wrote: > Hi > > After several iterations and some month of efforts, the new version of > Pharo by Example is finally available in print form and pdf. > > http://books.pharo.org > > > Tx all the contributors. > > -- > >

March 10, 2017

Re: [Pharo-users] New Version of Pillar on Windows

by mldavis＠chaparralwest.com

Thank you for the quick response. From what you told me and what I have seen so far, it will most likely work. I will have it tested and get back to you by Monday. I'm rather swamped today. I would like to add a comment about this, that ties into another thread with a comment by Peter: "I would argue that its simply easier to find Mac/Linux low-level experts and contributors than Windows as the developer culture (including OSS and contributions) is different." I agree with Peter that the Windows developer culture, even at the low-level is different. I believe that is twofold: First, use of the Windows command line and even the Microsoft endorsed PowerShell is seldom used to perform development work. Although PowerShell is commonly used for server administration. ALSO, and more importantly, the "C" / ADT based language culture is very, very strong in the U.S. I believe this was an unfortunate branch in software development here. This requires such a strong behavioral change to switch to a dynamic, object messaging environment like SmallTalk, that it is typically ignored. I'm personally pursuing an effort to motivate local interest in Pharo, in a local open source group to which I belong, for all the reasons you know well. In this particular case, for example, rather than adapting the Linux style scripts to Windows command line, my first reaction was to attempt to do the same thing within the Playground after which I would add an appropriate method or subclass to the Pillar package etc. Is this too far afield from where you are going with Pharo? At any rate, I will get the Windows command line version tested and also a Windows command line batch file (.bat) which could be circulated along with the .sh scripts, if you like. Cheers, mike -----Original Message----- From: stepharong [mailto:stepharong@free.fr] Sent: Thursday, March 9, 2017 1:20 PM To: pharo-users(a)lists.pharo.org; mldavis(a)chaparralwest.com Subject: Re: [Pharo-users] New Version of Pillar on Windows Hi mike I just checked - ./download.sh and it took the 50 stable version - make this created the html Now on windows you do not have make probably :) so you should $(OUTPUTDIRECTORY)/%.html: $(OUTPUTDIRECTORY)/%.html.json ./mustache --data=$< --template=${HTMLTEMPLATE} > $@ invoke ./mustache --data=output.html.json --template==yourhtmltemplate Tell me if this is working. > I am trying out the new version of Pillar (build 1940 or 1941) on > Windows on Pharo 50770, following the Pillar tutorial in Enterprise > Pharo book: > > I created the new file first.pillar containing: ! Hello World > > I ran: C:\Users\mldavis\Desktop\mldPillarWorking>Pharo.exe > Pillar.image pillar export --to=html first.pillar > > It created a file named: output.html.json containing: > {"content":"<section>\r\n<h1>1. Hello World</h1>\r\n</section>"} > > It was supposed to be an HTML document as shown in Enterprise Pharo > para > 14.2 page 213 "5 Minutes Tutorial". > > Any suggestions what I missed or should do? > > mike > > > -- Using Opera's mail client: http://www.opera.com/mail/

March 10, 2017

Pharo by example 5.0 is officially released and available

by stepharong

Hi After several iterations and some month of efforts, the new version of Pharo by Example is finally available in print form and pdf. http://books.pharo.org Tx all the contributors. --

March 10, 2017

Pharo Association event listing updated

by Marcus Denker

Hi, I added all events (tech talks, sprints, pharodays) that will happen till June here: https://association.pharo.org/events Marcus

March 10, 2017

Re: [Pharo-users] What is the craziest bug you ever face

by werner kassens

and occasionally memory leaks werner On 03/10/2017 04:02 PM, werner kassens wrote: > Hi Stephane, > bugs i found difficult to debug are eg (1) red cross of death bugs in > morphs, (2) bugs that are not visible any more because they are caught > and dealt with in the wrong place and then produce wrong results > instead of errors, and (3) bugs in iterative algos that work eg with > #while and that pop up eg in the 1000th iteration, where i first have > to add a counter to know that it happens in the 1000th iteration and > then have to add a #halt if counter=999 to see what happens then in > the debugger. > werner > > On 03/09/2017 12:36 PM, Stephane Ducasse wrote: >> Hi guys >> >> During the DSU workshop we were brainstorming about what are the most >> difficult bugs we faced and what are the conceptual tools that would >> have helped you. >> >> Stef > > > >

March 10, 2017

Re: [Pharo-users] What is the craziest bug you ever face

by werner kassens

Hi Stephane, bugs i found difficult to debug are eg (1) red cross of death bugs in morphs, (2) bugs that are not visible any more because they are caught and dealt with in the wrong place and then produce wrong results instead of errors, and (3) bugs in iterative algos that work eg with #while and that pop up eg in the 1000th iteration, where i first have to add a counter to know that it happens in the 1000th iteration and then have to add a #halt if counter=999 to see what happens then in the debugger. werner On 03/09/2017 12:36 PM, Stephane Ducasse wrote: > Hi guys > > During the DSU workshop we were brainstorming about what are the most > difficult bugs we faced and what are the conceptual tools that would > have helped you. > > Stef

March 10, 2017

Re: [Pharo-users] What is the craziest bug you ever face

by Offray Vladimir Luna CÃ¡rdenas

Hi, On the issue of developers log/notebook, I also have mine about Grafoscopio and other ideas (which is, of course, an interactive notebook, made in Grafoscopio). That allows me to take notes and trying to reproduce stuff that is not yet into the system as part of a package or create a story and different contextual information about my dev process to communicate it to another people. Here is an screenshot of how it looks: I have attached the notebook in ston format also :-). Cheers, Offray On 09/03/17 14:34, Dale Henrichs wrote: > > Stef, > > One of the things that I do all of the time when trying to debug > particularly difficult problems is to keep a "bug notebook". My "bug > notebook" is a text file where I record information gleaned from an > inspector intermixed with comments, code and observations... > > I've attached an example from a couple of days ago (bug_notebook.txt). > > The particular problem I am working on involves btree nodes being > improperly updated during index object updates. Each btree node is > basically a 2000+ element Array ... so there is a lot of data to deal > with . > > In the notebook, I extract the interesting entries from the btree node > and record the original set of values and then record the updated set > of values and in this particular case I was able to "see" that after > the update I had 4 entries that were not properly deleted ... > > In addition to recording the interesting chunks of large data > structures, I often end up with chunks of stacks from the debugger, > copies of a inspector panes in my "bug notebooks" and chunks of code ... > > Over the last several weeks I have been tackling different sets of > bugs in this same area and I have been keeping a time-stamped log of > the work that I've done along the way (analysis_notebook.txt) ... in > this notebook I've bee recording test results and branch/SHA > information so that I can easily reference different versions of > methods as I work through fixing bugs and managing regressions ... > There's a section in the notebook where I've record performance > information, so that when I have finished work on this set of bugs, I > can evaluate how I've impacted performance ... Finally at the very > bottom of the notebook, I've recorded a simple todo-list ... > > The notebooks are on a shared disk so that I can access and update > the "bug notebook" when I am working from home on a mac or at work > from a linux box ... > > I rely on the fact that I am working with text and not images ... > since I like to copy and paste as well as search for particular > strings in the data from the inspector ... in the bug_notebook I > searched for the `victim` string in the text output from an inspector ... > > I have come to really depend upon bug notebooks when addressing > difficult bugs and I think that support for creating and maintaining > bug notebooks would be a valuable addition the the debugging arsenal... > > Dale > > On 03/09/2017 10:50 AM, stepharong wrote: >> Thanks you all. >> >> The idea is that we want to see how we cn improve our debugging arsenal. >> So it is important that your scenario give use some hints. >> It is difficult to convey what we are really looking for :) >> >> >> >> Hi guys >> >> During the DSU workshop we were brainstorming about what are the >> most difficult bugs we faced and what are the conceptual tools >> that would have helped you. >> >> Stef >> >> >> >> >> -- >> Using Opera's mail client: http://www.opera.com/mail/ >

March 10, 2017

Re: [Pharo-users] What is the craziest bug you ever face

by Evan Donahue

Yeah, that sounds right. The debugger needed to be able to step through lines of code like normal (to debug the logic framework) as well as to step through search steps (to debug programs written in the framework) defined in terms of the system semantics (since bugs could be in either program or framework at this point). It also needed to recognize the semantics not only of the framework, but of the debugging interaction, because I needed it to step through the search space until it arrived at a particular leaf of the search frontier. The framework itself basically does a breadth-first-search, and it doesn't care when a particular frontier node will be visited again, but if I am tracing the search in one particular part of the space for the very specific purposes of debugging, only then do I need the debugger to recognize the semantics of when we are expanding a child of a given frontier node. I also played with the idea of actually changing the search order while debugging, which would change the semantics of the actual running program to make it turn out a certain way so that I could observe rare behavior. The analogy would be manually setting a random number in the debugger, except that it might take more than a single instance variable assignment to change the structure of a search tree. Evan -- View this message in context: http://forum.world.st/What-is-the-craziest-bug-you-ever-face-tp4937984p4938… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 9, 2017

Re: [Pharo-users] What is the craziest bug you ever face

by stepharong

I understand well your point :) On Thu, 09 Mar 2017 21:30:21 +0100, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > > The attached screnshot illustrates why I like having text instead of > pngs ... being able to highlight the association value (-5.00->5.00) is > very useful when identifying the entries >in a btree associated with the > association (the entries at 13, 16,19, and 22)... > > On 03/09/2017 11:34 AM, Dale Henrichs wrote: >> >> Stef, >> >> One of the things that I do all of the time when trying to debug >> particularly difficult problems is to keep a "bug notebook". My "bug >> notebook" is a text file where I >>record information gleaned from an >> inspector intermixed with comments, code and observations... >> >> I've attached an example from a couple of days ago (bug_notebook.txt). >> The particular problem I am working on involves btree nodes being >> improperly updated during index object updates. Each btree node is >> basically a 2000+ >>element Array ... so there is a lot of data to deal >> with . >> In the notebook, I extract the interesting entries from the btree node >> and record the original set of values and then record the updated set >> of values and in this >>particular case I was able to "see" that after >> the update I had 4 entries that were not properly deleted ... >> In addition to recording the interesting chunks of large data >> structures, I often end up with chunks of stacks from the debugger, >> copies of a inspector panes in my >>"bug notebooks" and chunks of code >> ... >> >> Over the last several weeks I have been tackling different sets of bugs >> in this same area and I have been keeping a time-stamped log of the >> work that I've done >>along the way (analysis_notebook.txt) ... in this >> notebook I've bee recording test results and branch/SHA information so >> that I can easily reference different >>versions of methods as I work >> through fixing bugs and managing regressions ... There's a section in >> the notebook where I've record performance information, so >>that when >> I have finished work on this set of bugs, I can evaluate how I've >> impacted performance ... Finally at the very bottom of the notebook, >> I've recorded a >>simple todo-list ... >> The notebooks are on a shared disk so that I can access and update the >> "bug notebook" when I am working from home on a mac or at work from a >> linux box ... >> I rely on the fact that I am working with text and not images ... since >> I like to copy and paste as well as search for particular strings in >> the data from the inspector ... >>in the bug_notebook I searched for >> the `victim` string in the text output from an inspector ... >> >> I have come to really depend upon bug notebooks when addressing >> difficult bugs and I think that support for creating and maintaining >> bug notebooks would be a >>valuable addition the the debugging >> arsenal... >> >> Dale >> >> On 03/09/2017 10:50 AM, stepharong wrote: >>> Thanks you all. >>> >>> The idea is that we want to see how we cn improve our debugging >>> arsenal.So it is important that your scenario give use some hints.It >>> is difficult to convey what we are really looking for :) >>> >>> >>> >>>> Hi guys >>>> During the DSU workshop we were brainstorming about what are the most >>>> difficult bugs we faced and what are the conceptual tools that would >>>> >>>>have helped you. >>>> >>>> Stef >>> >>> >>> >>> --Using Opera's mail client: http://www.opera.com/mail/ >> > -- Using Opera's mail client: http://www.opera.com/mail/

March 9, 2017

Re: [Pharo-users] What is the craziest bug you ever face

by Dale Henrichs

The attached screnshot illustrates why I like having text instead of pngs ... being able to highlight the association value (-5.00->5.00) is very useful when identifying the entries in a btree associated with the association (the entries at 13, 16,19, and 22)... On 03/09/2017 11:34 AM, Dale Henrichs wrote: > > Stef, > > One of the things that I do all of the time when trying to debug > particularly difficult problems is to keep a "bug notebook". My "bug > notebook" is a text file where I record information gleaned from an > inspector intermixed with comments, code and observations... > > I've attached an example from a couple of days ago (bug_notebook.txt). > > The particular problem I am working on involves btree nodes being > improperly updated during index object updates. Each btree node is > basically a 2000+ element Array ... so there is a lot of data to deal > with . > > In the notebook, I extract the interesting entries from the btree node > and record the original set of values and then record the updated set > of values and in this particular case I was able to "see" that after > the update I had 4 entries that were not properly deleted ... > > In addition to recording the interesting chunks of large data > structures, I often end up with chunks of stacks from the debugger, > copies of a inspector panes in my "bug notebooks" and chunks of code ... > > Over the last several weeks I have been tackling different sets of > bugs in this same area and I have been keeping a time-stamped log of > the work that I've done along the way (analysis_notebook.txt) ... in > this notebook I've bee recording test results and branch/SHA > information so that I can easily reference different versions of > methods as I work through fixing bugs and managing regressions ... > There's a section in the notebook where I've record performance > information, so that when I have finished work on this set of bugs, I > can evaluate how I've impacted performance ... Finally at the very > bottom of the notebook, I've recorded a simple todo-list ... > > The notebooks are on a shared disk so that I can access and update > the "bug notebook" when I am working from home on a mac or at work > from a linux box ... > > I rely on the fact that I am working with text and not images ... > since I like to copy and paste as well as search for particular > strings in the data from the inspector ... in the bug_notebook I > searched for the `victim` string in the text output from an inspector ... > > I have come to really depend upon bug notebooks when addressing > difficult bugs and I think that support for creating and maintaining > bug notebooks would be a valuable addition the the debugging arsenal... > > Dale > > On 03/09/2017 10:50 AM, stepharong wrote: >> Thanks you all. >> >> The idea is that we want to see how we cn improve our debugging arsenal. >> So it is important that your scenario give use some hints. >> It is difficult to convey what we are really looking for :) >> >> >> >> Hi guys >> >> During the DSU workshop we were brainstorming about what are the >> most difficult bugs we faced and what are the conceptual tools >> that would have helped you. >> >> Stef >> >> >> >> >> -- >> Using Opera's mail client: http://www.opera.com/mail/ >

March 9, 2017