April 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] RefsHunter

by Ben Coman

On Tue, Apr 19, 2016 at 10:08 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > > 2016-04-19 15:53 GMT+02:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> >> Hi Pavel, >> >> This would have helped us to track that evil object years ago (remember >> the name???) hahaha. > > > Dzindzik :-) > >> >> Anyway, do you think it's worth an integration of this to >> http://smalltalkhub.com/#!/~BenComan/PointerDetective ?? The last few commits of this are not stable. Unfortunately I got distracted in the middle of some re-factoring when I stumbled due to debugging circular references which locked the image [1] . I should look at reviving this for Pharo 5, maybe on Bloc... [1] https://pharo.fogbugz.com/default.asp?14827 - printString locks Image on circular references cheers -ben > > It should be pretty easy. it deserves an attempt. > > -- Pavel > >> >> >> Best, >> >> On Tue, Apr 19, 2016 at 10:44 AM, Pavel Krivanek >> <pavel.krivanek(a)gmail.com> wrote: >>> >>> Hi, >>> >>> when we were trying to fix memory leaks in the system in last weeks, it >>> was very handy to create a small tool that shows a shortest path of backward >>> references from one object to another one. Our tool is named RefsHunter and >>> you can find it in the Catalog of Pharo 5. >>> >>> You can use Gofer if you want to load it without tests to the minimal >>> Pharo: >>> >>> Gofer new >>> smalltalkhubUser: 'PavelKrivanek' project: 'RefsHunter'; >>> package: 'RefsHunter-Core'; >>> load. >>> >>> The RefsHunter creates a temporary snapshot of all objects in the image >>> and then collects information about all non-weak backward references. After >>> that you can ask on the shortest path from one object to another one. That >>> is useful for example when you still have got some leaking instance in the >>> image and you want to see how is it linked with the global space. >>> >>> Example: >>> >>> | rh | >>> rh := RefsHunter snapshot. >>> rh wayFrom: (Array>>#asArray) to: Smalltalk specialObjectsArray. >>> >>> Notice that this tool is very memory demanding and it is not good idea to >>> make a new RefsHunter snapshot when you still have some previous snapshot in >>> the object memory. >>> >>> Cheers, >>> -- Pavel >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com > >

April 19, 2016

[pharo-project/pharo-core] 6ec53f: 50701

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 6ec53f68a760b8265ff0d5a68df4f1542a00a415 https://github.com/pharo-project/pharo-core/commit/6ec53f68a760b8265ff0d5a6… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-04-19 (Tue, 19 Apr 2016) Changed paths: M ReleaseTests.package/ReleaseTest.class/instance/testing/testShouldFileLocatorBeBeforeSystemSettingsPersistenceInStartupList.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50700.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50701.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50700.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50701.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50701 16976 Invalid repo predefined in Monticello browser https://pharo.fogbugz.com/f/cases/16976 17965 Failing on CI: #testShouldFileLocatorBeBeforeSystemSettingsPersistenceInStartupList https://pharo.fogbugz.com/f/cases/17965 http://files.pharo.org/image/50/50701.zip

April 19, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50701 Home: https://github.com/pharo-project/pharo-core

April 19, 2016

Re: [Pharo-dev] [ANN] RefsHunter

by Mariano Martinez Peck

On Tue, Apr 19, 2016 at 11:08 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > > 2016-04-19 15:53 GMT+02:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > >> Hi Pavel, >> >> This would have helped us to track that evil object years ago (remember >> the name???) hahaha. >> > > Dzindzik :-) > That one!!!!! haahahha I checked my emails and ... uff.. that was in 2012 ;) we are getting older haha. > > >> Anyway, do you think it's worth an integration of this to >> http://smalltalkhub.com/#!/~BenComan/PointerDetective ?? >> > > It should be pretty easy. it deserves an attempt. > > Cool! Note that there are many efforts in this area. Please see https://github.com/dalehenrich/obex You can see the reference from there to http://www.smalltalkhub.com/#!/~PierreChanson/RPointerDetective Cheers, > -- Pavel > > >> >> Best, >> >> On Tue, Apr 19, 2016 at 10:44 AM, Pavel Krivanek < >> pavel.krivanek(a)gmail.com> wrote: >> >>> Hi, >>> >>> when we were trying to fix memory leaks in the system in last weeks, it >>> was very handy to create a small tool that shows a shortest path of >>> backward references from one object to another one. Our tool is named >>> RefsHunter and you can find it in the Catalog of Pharo 5. >>> >>> You can use Gofer if you want to load it without tests to the minimal >>> Pharo: >>> >>> Gofer new >>> smalltalkhubUser: 'PavelKrivanek' project: 'RefsHunter'; >>> package: 'RefsHunter-Core'; >>> load. >>> >>> The RefsHunter creates a temporary snapshot of all objects in the image >>> and then collects information about all non-weak backward references. After >>> that you can ask on the shortest path from one object to another one. That >>> is useful for example when you still have got some leaking instance in the >>> image and you want to see how is it linked with the global space. >>> >>> Example: >>> >>> | rh | >>> rh := RefsHunter snapshot. >>> rh wayFrom: (Array>>#asArray) to: Smalltalk specialObjectsArray. >>> >>> Notice that this tool is very memory demanding and it is not good idea >>> to make a new RefsHunter snapshot when you still have some previous >>> snapshot in the object memory. >>> >>> Cheers, >>> -- Pavel >>> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > -- Mariano http://marianopeck.wordpress.com

April 19, 2016

Re: [Pharo-dev] unzip:to:

by Tudor Girba

The way I see it is that pathString can be anything that understands asFileReference. This means: - FileReference - Path - String Doru > On Apr 19, 2016, at 2:54 PM, stepharo <stepharo(a)free.fr> wrote: > > unzip: fullFileName to: pathString > "Unzip the contents of the file specified by the full path name fullFileName to the location given by pathString." > > so we would expect to pass a string in the second argument? > > the unique sender of it in the system > > unzip: fullFileName > "Unzip the contents of a gzipped file specified by its full file name to the current working directory" > > ^ self unzip: fullFileName to: FileSystem disk workingDirectory > > > but the implementation seems to indicate that fullFileName is should be a string as well as pathString > > unzip: fullFileName to: pathString > "Unzip the contents of the file specified by the full path name fullFileName to the location given by pathString." > > | zipped buffer unzipped newName | > newName := fullFileName copyUpToLast: FileSystem disk extensionDelimiter. > pathString asFileReference ensureCreateDirectory. > unzipped := FileStream newFileNamed: (pathString asFileReference / newName) fullName. > unzipped ifNil: [self error: pathString, ' looks incorrect']. > [ unzipped binary. > zipped := self on: (FileStream readOnlyFileNamed: fullFileName). > buffer := ByteArray new: 50000. > [zipped atEnd] whileFalse: [unzipped nextPutAll: (zipped nextInto: buffer)]] > ensure: [ > zipped close. > unzipped close]. > ^ newName > > Am I correct to think that the comments are not really good enough? > > Stef > > > -- www.tudorgirba.com www.feenk.com "We can create beautiful models in a vacuum. But, to get them effective we have to deal with the inconvenience of reality."

April 19, 2016

Re: [Pharo-dev] [ANN] RefsHunter

by Pavel Krivanek

2016-04-19 15:53 GMT+02:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi Pavel, > > This would have helped us to track that evil object years ago (remember > the name???) hahaha. > Dzindzik :-) > Anyway, do you think it's worth an integration of this to > http://smalltalkhub.com/#!/~BenComan/PointerDetective ?? > It should be pretty easy. it deserves an attempt. -- Pavel > > Best, > > On Tue, Apr 19, 2016 at 10:44 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com > > wrote: > >> Hi, >> >> when we were trying to fix memory leaks in the system in last weeks, it >> was very handy to create a small tool that shows a shortest path of >> backward references from one object to another one. Our tool is named >> RefsHunter and you can find it in the Catalog of Pharo 5. >> >> You can use Gofer if you want to load it without tests to the minimal >> Pharo: >> >> Gofer new >> smalltalkhubUser: 'PavelKrivanek' project: 'RefsHunter'; >> package: 'RefsHunter-Core'; >> load. >> >> The RefsHunter creates a temporary snapshot of all objects in the image >> and then collects information about all non-weak backward references. After >> that you can ask on the shortest path from one object to another one. That >> is useful for example when you still have got some leaking instance in the >> image and you want to see how is it linked with the global space. >> >> Example: >> >> | rh | >> rh := RefsHunter snapshot. >> rh wayFrom: (Array>>#asArray) to: Smalltalk specialObjectsArray. >> >> Notice that this tool is very memory demanding and it is not good idea to >> make a new RefsHunter snapshot when you still have some previous snapshot >> in the object memory. >> >> Cheers, >> -- Pavel >> > > > > -- > Mariano > http://marianopeck.wordpress.com >

April 19, 2016

Re: [Pharo-dev] What the state of unifying Beacon with SystemLogger?

by Tudor Girba

Hi, I even reviewed this post :). Of course, you can just use plain Announcements, but I still need to nuance your too strong statement. A framework is worthwhile when there is a recurrent need that it can serve. And when it comes to logging there are several such needs. For example: - reusing typical events (e.g., logging an exception) - reusing storage possibilities - having a timestamp for events I think it is worthwhile to have support out of the box for handling these. Cheers, Doru > On Apr 19, 2016, at 3:44 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > You might want to read > > https://medium.com/concerning-pharo/lampsort-revisited-visualised-6652055ef… > > that discusses object logging and what you can do with it. > > My take on this is that if you write your code to produce log events (as Announcements), you can do whatever you want in the end. There is no real need to depend on some framework. > >> On 19 Apr 2016, at 15:34, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> Beacon is being used systematically. We even said we will integrate it in the image for Pharo 5 at the end of last year, but after the agitated start of the year, I did not push it anymore to not increase the level of agitation. >> >> The only class name that encountered some opposition was BoundedBeacon. >> >> We also agreed that the only things we want from SystemLogger were the concrete connections to external storage. This was not done, but the idea was that we should first integrate them and then allow people to extend it with bindings to external storage. >> >> I use Beacon on a regular basis, and I extended it recently with a couple of more Signal types that can capture exceptions and stack information. You now also have a better integration in the inspector to be able to start/pause an in-memory log stream. In the process I also added the possibility to remove Announcements from an AnnouncementSet and I would like to push this in Pharo 6.0. One thing I would work on is to add to Annoucements the possibility of filtering announcements based on instances not just types. This is a longer term plan. >> >> Another thing to do is to ensure that the log signals are not expensive to create. For example, the ExceptionSignal, ContextStackSignal and MethodStackSignal manipulate thisContext right at creation time, while this should happen only when we actually capture it in a BoundedBeacon to manipulate/store it in a specific way. This part should be refined. >> >> @Dennis: it would be great to join efforts. The two frameworks look similar, but there are 2 significant differences: >> 1. SystemLogger has its own log events propagation mechanism, Beacon uses Announcements. >> 2. SystemLogger relies on levels of filtering, Beacon uses the mechanisms from Announcements to pick and choose at a fine grain level which log signals should be logged. >> >> For reference: >> - description: http://www.humane-assessment.com/blog/beacon/ >> - repository: http://www.smalltalkhub.com/#!/~Pharo/Beacon >> >> Cheers, >> Doru >> >> >>> On Apr 19, 2016, at 2:59 PM, stepharo <stepharo(a)free.fr> wrote: >>> >>> >>> >>> Le 18/4/16 18:28, Denis Kudriashov a Ã©crit : >>>> Hello. >>>> >>>> Year ago Beacon and SystemLogger were announced. There was big discussion about them. And there were plans to provide single solution. What was done around that? >>> >>> Nothing. We should have done it at Cambridge and we just discussed. >>> I did not like some Beacon class names because they are totally confusing. >>>> >>>> What exactly should be merged between this libraries? Was Beacon or SystemLogger planned to be end solution? >>> We planned to merge SystemLogger into Beacon to use announcements >>>> We definitely need legacy logging tool for Pharo. And I am going to work on this direction. >>>> Personally I prefer metaphor and names from Beacon. But both libraries implement similar idea. >>> Remember that you want to have them short especially for the main one. This is why in SystemLogger >>> we have Log instead of what it is LogObject if I remember correctly. >>>> >>>> Best regards, >>>> Denis >>> >>> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> âLive like you mean it." >> >> > > -- www.tudorgirba.com www.feenk.com "Problem solving efficiency grows with the abstractness level of problem understanding."

April 19, 2016

Re: [Pharo-dev] unzip:to:

by Valentin Ryckewaert

I mean, fileRef basename is myZip.zip and workingDirectory is the place files will go after being unziped but how does we find the file named fileRef basename ? 2016-04-19 15:46 GMT+02:00 stepharo <stepharo(a)free.fr>: > > > Le 19/4/16 15:41, Valentin Ryckewaert a Ã©crit : > > How does unzip:to: access to the file ? > > I do not get your question? > > It must be in the workingDirectory? > > > Read the code luke.... > > > unzip: fullFileName to: pathString > "Unzip the contents of the file specified by the full path name > fullFileName to the location given by pathString." > > | zipped buffer unzipped newName | > newName := fullFileName copyUpToLast: FileSystem disk > extensionDelimiter. > pathString asFileReference ensureCreateDirectory. > unzipped := FileStream newFileNamed: (pathString asFileReference / > newName) fullName. > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > unzipped ifNil: [self error: pathString, ' looks incorrect']. > [ unzipped binary. > zipped := self on: (FileStream readOnlyFileNamed: fullFileName). > buffer := ByteArray new: 50000. > [zipped atEnd] whileFalse: [unzipped nextPutAll: (zipped nextInto: > buffer)]] > ensure: [ > zipped close. > unzipped close]. > ^ newName > > > > > > 2016-04-19 15:06 GMT+02:00 HernÃ¡n Morales Durand < > <hernan.morales(a)gmail.com>hernan.morales(a)gmail.com>: > >> I use it a lot to uncompress external resources like this: >> >> fileRef := .... >> GZipReadStream unzip: fileRef basename to: FileSystem workingDirectory. >> >> but it could be used to pass a directory as String I guess. >> Comment should be corrected. >> >> >> 2016-04-19 9:54 GMT-03:00 stepharo < <stepharo(a)free.fr>stepharo(a)free.fr>: >> >>> unzip: fullFileName to: pathString >>> "Unzip the contents of the file specified by the full path name >>> fullFileName to the location given by pathString." >>> >>> so we would expect to pass a string in the second argument? >>> >>> the unique sender of it in the system >>> >>> unzip: fullFileName >>> "Unzip the contents of a gzipped file specified by its full file >>> name to the current working directory" >>> >>> ^ self unzip: fullFileName to: FileSystem disk workingDirectory >>> >>> >>> but the implementation seems to indicate that fullFileName is should be >>> a string as well as pathString >>> >>> unzip: fullFileName to: pathString >>> "Unzip the contents of the file specified by the full path name >>> fullFileName to the location given by pathString." >>> >>> | zipped buffer unzipped newName | >>> newName := fullFileName copyUpToLast: FileSystem disk >>> extensionDelimiter. >>> pathString asFileReference ensureCreateDirectory. >>> unzipped := FileStream newFileNamed: (pathString asFileReference / >>> newName) fullName. >>> unzipped ifNil: [self error: pathString, ' looks incorrect']. >>> [ unzipped binary. >>> zipped := self on: (FileStream readOnlyFileNamed: fullFileName). >>> buffer := ByteArray new: 50000. >>> [zipped atEnd] whileFalse: [unzipped nextPutAll: (zipped nextInto: >>> buffer)]] >>> ensure: [ >>> zipped close. >>> unzipped close]. >>> ^ newName >>> >>> Am I correct to think that the comments are not really good enough? >>> >>> Stef >>> >>> >>> >>> >> > >

April 19, 2016

Re: [Pharo-dev] [ANN] RefsHunter

by Mariano Martinez Peck

Hi Pavel, This would have helped us to track that evil object years ago (remember the name???) hahaha. Anyway, do you think it's worth an integration of this to http://smalltalkhub.com/#!/~BenComan/PointerDetective ?? Best, On Tue, Apr 19, 2016 at 10:44 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi, > > when we were trying to fix memory leaks in the system in last weeks, it > was very handy to create a small tool that shows a shortest path of > backward references from one object to another one. Our tool is named > RefsHunter and you can find it in the Catalog of Pharo 5. > > You can use Gofer if you want to load it without tests to the minimal > Pharo: > > Gofer new > smalltalkhubUser: 'PavelKrivanek' project: 'RefsHunter'; > package: 'RefsHunter-Core'; > load. > > The RefsHunter creates a temporary snapshot of all objects in the image > and then collects information about all non-weak backward references. After > that you can ask on the shortest path from one object to another one. That > is useful for example when you still have got some leaking instance in the > image and you want to see how is it linked with the global space. > > Example: > > | rh | > rh := RefsHunter snapshot. > rh wayFrom: (Array>>#asArray) to: Smalltalk specialObjectsArray. > > Notice that this tool is very memory demanding and it is not good idea to > make a new RefsHunter snapshot when you still have some previous snapshot > in the object memory. > > Cheers, > -- Pavel > -- Mariano http://marianopeck.wordpress.com

April 19, 2016

Re: [Pharo-dev] [Pharo-users] GTDebugger shortcuts usability

by stepharo

This F keys suck! Stef Le 17/4/16 18:00, Ben Coman a Ã©crit : > Interesting. A search turned up... Quick Tip Debugger Shortcut Key Reference > http://www.mularien.com/blog/category/eclipse/ > > cheers -ben > > On Sun, Apr 17, 2016 at 11:15 PM, philippe.back(a)highoctane.be > <philippe.back(a)gmail.com> wrote: >> Most of the world IDE use function keys for debugging. >> >> Additional benefit: easier for newcomers to use it. >> >> Having the buttons on the top is a pain as the code pane is at the bottom >> and requires travels all the time. >> >> Phil >> >> On Apr 17, 2016 4:57 PM, "Peter UhnÃ¡k" <i.uhnak(a)gmail.com> wrote: >>> Well, I've added a startup script for myself... but it would be nice to >>> have it everywhere by default in some variant... >>> >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> StartupPreferencesLoader default executeAtomicItems: { >>> StartupAction >>> name: 'Change debugger labels & shortcuts' >>> code: [ >>> GLMMorphicActionRenderer compile: ( >>> (GLMMorphicActionRenderer>>#render:) sourceCode >>> copyReplaceAll: 'setBalloonText: (anAction title' >>> with: 'setBalloonText: (anAction title asString' >>> ). >>> RestartDebugAction compile: 'defaultKeyText >>> ^ ''R'''. >>> RestartDebugAction compile: 'defaultLabel >>> ^ ''Restart'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. >>> ResumeDebugAction compile: 'defaultKeyText >>> ^ ''P'''. >>> ResumeDebugAction compile: 'defaultLabel >>> ^ ''Proceed'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. >>> StepIntoDebugAction compile: 'defaultKeyText >>> ^ ''I'''. >>> StepIntoDebugAction compile: 'defaultLabel >>> ^ ''Into'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. >>> StepOverDebugAction compile: 'defaultLabel >>> ^ ''Over'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. >>> StepThroughDebugAction compile: 'defaultLabel >>> ^ ''Through'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. >>> ] >>> runOnce: true. >>> } >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> >>> >>> >>> On Sat, Apr 16, 2016 at 11:39 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>>>> Letâs turn this energy into something positive. Please propose a >>>>> concrete set of default keybindings that you think would work better. In >>>>> this process, please take into account all keybindings that are already >>>>> defined in the code editor (it might not be so easy as it appears). >>>> >>>> As I've said: >>>> >>>> 1. can we unify the shift vs ctrl+shift nonsense? (I'm using linux btw) >>>> 2. can we use the default shortcuts pattern where one of the letters is >>>> underlined? >>>> >>>> as for the shortcuts themselves, problem is proceed, restart & into >>>> >>>> proceed: ctrl+shift+p is not taken, so I don't see why it has shortcut >>>> confusing with restart >>>> restart: ctrl+shift+r indents, but I'd argue that uniformity is more >>>> important here... indent is just convenience >>>> into: ctrl+shift+i is taken (I've never used it, but it maybe it's >>>> important), but we can still use ctrl+shift+n and underline n (point 2) >>>> >>>> If points 1 & 2 are implemented, then the letter is not as important, >>>> although first letter is always preferable. >>>> >>>> Peter >>>> >>>>> Cheers, >>>>> Doru >>>>> >>>>> >>>>>> On Apr 16, 2016, at 8:37 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> I'm getting fed-up with GTDebugger shortcuts since they are completely >>>>>> random. >>>>>> >>>>>> Can we have them more meaningful and/or somehow visible? >>>>>> >>>>>> For now I ended up overriding the labels so I can at least see them... >>>>>> but doing this is also stupid, because I still have to look at them since I >>>>>> cannot remember random shortcuts. >>>>>> >>>>>> <debugger.png> >>>>>> >>>>>> 1. can we unify the shift vs ctrl+shift nonsense? (I'm using linux >>>>>> btw) >>>>>> 2. can we use the default shortcuts pattern where one of the letters >>>>>> is underlined? >>>>>> >>>>>> Peter >>>>> -- >>>>> www.tudorgirba.com >>>>> www.feenk.com >>>>> >>>>> "Value is always contextual." >>>>> >>>>> >>>>> >>>>> >>>>> >

April 19, 2016