December 2021 - Pharo-dev - lists.pharo.org

Sockets not working under heavy VM load?

by Pavel Krivanek

Hi, we have some performance issues with Glorp over P3 and, after some investigation, I have a theory that could explain it. And I would like to know your opinion if it is correct. To reproduce this issue, you can try something easy. Just create a process with normal or higher priority that will try to read something from a socket. And, in parallel, do in a separate thread an operation that takes all the processor time for several seconds. ```` [ 5 seconds wait. Time now traceCr. ZnClient new url: 'https://www.google.com'; get. Time now traceCr. ] forkAt: 60. [1000 timesRepeat: [ 10000 factorial ] ] timeToRun ```` (you may try a different safe server address) The processes run in parallel until the time when the first process tries to obtain data from the socket. Then it hangs and waits until finishing of the second process. My theory is that the VM socket plugin is able to receive incoming data from the connection and save it into the buffer. In the meantime, the reading process is waiting on the socket semaphore. But it looks like the plugin is not able to release the semaphore while the VM is actually doing something. It needs to wait until the VM has nothing useful to do, and then it is finally able to release the semaphores so Pharo processes are resumed and can start to read. Is my theory right? Cheers, -- Pavel

Dec. 29, 2021

Re: FileDoesNotExistException - FileBrowser opening on Mac M1

by stephane ducasse

Hi Thanks for the report. Did you enter a bug report for the M1 case? Do you have a reproducible case? May be Apple changed some file info under our feet but probably that the tool should not be blindy trying to access files. S > On 23 Dec 2021, at 17:56, Stewart MacLean <stewmaclean(a)gmail.com> wrote: > > Hi All, > > This is my first post! Sadly it is to report an issue with the FileBrowser on the Mac M1. > > I am encountering this exception - FileDoesNotExistException. > > These are the culprits: > > <image.png> > > I have seen a similar error reported on Windows. Looks like Pharo can't access the attributes of these files? https://github.com/pharo-project/pharo/issues/3571 <https://github.com/pharo-project/pharo/issues/3571> > > I'm exploring Pharo with a view to migrating my VisualWorks project of many years, as support for M1 looks like it might be a way off, so not off to a good start! > > I managed to work around it, by deleting these two files (not from the disk!) in the debugger, before it tried to fetch the attributes. Interestingly, when in the debugger it showed N/A and 0 for the attributes, as these are system files I'm guessing. > > Thanks, > > Stewart > > ==================================================================== > Pharo 9.0.0 > Build information: Pharo-9.0.0+build.1573.sha.0e09d756fc99383cbb498565200d9e5e9841ce11 (64 Bit) > > Mac Mini M1 (2020) > Monterey 12.0.1 > > File class>>signalError:for: > File class>>primFileAttribute:number: > File class>>fileAttribute:number: > MacStore(DiskStore)>>sizeOf: > FileSystem>>sizeOf: > FileReference>>size > FileReference(AbstractFileReference)>>humanReadableSize > FileListGridNode>>fileSize > [:node :cont | node perform: self rowMorphGetSelector] in MorphTreeColumn>>rowMorphGetterBlock in Block: [:node :cont | node perform: self rowMorphGetSelec...etc... > MorphTreeColumn>>rowMorphFor: > [:col | | v | > v := col rowMorphFor: complexContents. > controls add: v. > col -> v] in MorphTreeNodeMorph>>buildRowMorph in Block: [:col | | v |... > OrderedCollection>>collect: > MorphTreeNodeMorph>>buildRowMorph > MorphTreeNodeMorph>>initRow > MorphTreeNodeMorph>>initWithContents:prior:forList:indentLevel: > [:item :idx | > priorMorph := self indentingItemClass new > initWithContents: item > prior: priorMorph > forList: self > indentLevel: newIndent. > firstAddition > ifNil: [firstAddition := priorMorph]. > morphList add: priorMorph. > "Was this row expanded ? if true -> expand it > again " > ((item hasEquivalentIn: expandedItems) > or: [priorMorph isExpanded]) > ifTrue: [priorMorph isExpanded: true. > priorMorph > addChildrenForList: self > addingTo: morphList > withExpandedItems: expandedItems]] in MorphTreeMorph>>addMorphsTo:from:withExpandedItems:atLevel: in Block: [:item :idx | ... > Array(SequenceableCollection)>>withIndexDo: > Array(Collection)>>doWithIndex: > MorphTreeMorph>>addMorphsTo:from:withExpandedItems:atLevel: > MorphTreeMorph>>addSubmorphsFromNodeList:previouslyExpanded: > MorphTreeMorph>>addSubmorphsFromNodeList > MorphTreeMorph>>buildContents > FileListGrid>>treeMorph > FileList>>morphicGrid > FileList>>grid > FileList>>updateFileList > FileList>>reference: > FileList>>directory: > FileList>>initialize > FileList class(Behavior)>>new > > On Thu, Dec 23, 2021 at 4:23 PM Stewart MacLean <stewart(a)xtra.co.nz <mailto:stewart@xtra.co.nz>> wrote: > Hi All, > > This is my first post! Sadly it is to enquire about an issue with the FileBrowser on the Mac M1. > > I am encountering this exception - FileDoesNotExistException. > > I appears to be opening on just two files: > > <image.png> > > I have seen a similar error reported on Windows. Looks like Pharo can't access the attributes of these files? https://github.com/pharo-project/pharo/issues/3571 <https://github.com/pharo-project/pharo/issues/3571> > > I'm exploring Pharo with a view to migrating my VisualWorks project of many years, as support for M1 looks like it might be a way off, so not a good start! > > Any help appreciated. > > Thanks, > > Stewart > > ==================================================================== > Pharo 9.0.0 > Build information: Pharo-9.0.0+build.1573.sha.0e09d756fc99383cbb498565200d9e5e9841ce11 (64 Bit) > > Mac Mini M1 (2020) > Monterey 12.0.1 > > File class>>signalError:for: > File class>>primFileAttribute:number: > File class>>fileAttribute:number: > MacStore(DiskStore)>>sizeOf: > FileSystem>>sizeOf: > FileReference>>size > FileReference(AbstractFileReference)>>humanReadableSize > FileListGridNode>>fileSize > [:node :cont | node perform: self rowMorphGetSelector] in MorphTreeColumn>>rowMorphGetterBlock in Block: [:node :cont | node perform: self rowMorphGetSelec...etc... > MorphTreeColumn>>rowMorphFor: > [:col | | v | > v := col rowMorphFor: complexContents. > controls add: v. > col -> v] in MorphTreeNodeMorph>>buildRowMorph in Block: [:col | | v |... > OrderedCollection>>collect: > MorphTreeNodeMorph>>buildRowMorph > MorphTreeNodeMorph>>initRow > MorphTreeNodeMorph>>initWithContents:prior:forList:indentLevel: > [:item :idx | > priorMorph := self indentingItemClass new > initWithContents: item > prior: priorMorph > forList: self > indentLevel: newIndent. > firstAddition > ifNil: [firstAddition := priorMorph]. > morphList add: priorMorph. > "Was this row expanded ? if true -> expand it > again " > ((item hasEquivalentIn: expandedItems) > or: [priorMorph isExpanded]) > ifTrue: [priorMorph isExpanded: true. > priorMorph > addChildrenForList: self > addingTo: morphList > withExpandedItems: expandedItems]] in MorphTreeMorph>>addMorphsTo:from:withExpandedItems:atLevel: in Block: [:item :idx | ... > Array(SequenceableCollection)>>withIndexDo: > Array(Collection)>>doWithIndex: > MorphTreeMorph>>addMorphsTo:from:withExpandedItems:atLevel: > MorphTreeMorph>>addSubmorphsFromNodeList:previouslyExpanded: > MorphTreeMorph>>addSubmorphsFromNodeList > MorphTreeMorph>>buildContents > FileListGrid>>treeMorph > FileList>>morphicGrid > FileList>>grid > FileList>>updateFileList > FileList>>reference: > FileList>>directory: > FileList>>initialize > FileList class(Behavior)>>new > >

Dec. 26, 2021

CLAP - how to get instance of command without executing it

by bajger＠gmail.com

Hi Pharoers! I have following problem in CLAP and would be glad to get your guidance: I have following method on command class (sub-class of ClapApplication):\ `PhLImageKillCliCommand>>osShellCmdString` `(arguments at: #all) value ` ` ifTrue: [ ^ (self killImageCmdStringFrom: nil) ]. ` `^ self killImageCmdStringFrom: self imageName` And I want to implement unit test, that would test expected output of this method. As you can see, implementation is dependent on arguments attribute #all. And here is a problem in unit test: `testOsShellCmdString`\ `| killCliCommand aMatch| aMatch := (context arguments: #('launcher' 'image' 'kill' '--all')) match. killCliCommand := PhLImageKillCliCommand new. killCliCommand setArguments: aMatch.` `self assert: killCliCommand osShellCmdString equals: ''.` This doesn't work, since `arguments at: #all` gives NotYetImplemented exception. So I don't know, how to "wire" toghether instance of command (without executing it) and needed arguments (a match). Any advice on this? ![ObrÃ¡zek](https://media.discordapp.net/attachments/819245127310114886/922498381358723123/unknown.png)

Dec. 25, 2021

Re: FileDoesNotExistException - FileBrowser opening on Mac M1

by Stewart MacLean

Hi All, This is my first post! Sadly it is to report an issue with the FileBrowser on the Mac M1. I am encountering this exception - FileDoesNotExistException. These are the culprits: [image: image.png] I have seen a similar error reported on Windows. Looks like Pharo can't access the attributes of these files? https://github.com/pharo-project/pharo/issues/3571 I'm exploring Pharo with a view to migrating my VisualWorks project of many years, as support for M1 looks like it might be a way off, so not off to a good start! I managed to work around it, by deleting these two files (not from the disk!) in the debugger, before it tried to fetch the attributes. Interestingly, when in the debugger it showed N/A and 0 for the attributes, as these are system files I'm guessing. Thanks, Stewart ==================================================================== Pharo 9.0.0 Build information: Pharo-9.0.0+build.1573.sha.0e09d756fc99383cbb498565200d9e5e9841ce11 (64 Bit) Mac Mini M1 (2020) Monterey 12.0.1 File class>>signalError:for: File class>>primFileAttribute:number: File class>>fileAttribute:number: MacStore(DiskStore)>>sizeOf: FileSystem>>sizeOf: FileReference>>size FileReference(AbstractFileReference)>>humanReadableSize FileListGridNode>>fileSize [:node :cont | node perform: self rowMorphGetSelector] in MorphTreeColumn>>rowMorphGetterBlock in Block: [:node :cont | node perform: self rowMorphGetSelec...etc... MorphTreeColumn>>rowMorphFor: [:col | | v | v := col rowMorphFor: complexContents. controls add: v. col -> v] in MorphTreeNodeMorph>>buildRowMorph in Block: [:col | | v |... OrderedCollection>>collect: MorphTreeNodeMorph>>buildRowMorph MorphTreeNodeMorph>>initRow MorphTreeNodeMorph>>initWithContents:prior:forList:indentLevel: [:item :idx | priorMorph := self indentingItemClass new initWithContents: item prior: priorMorph forList: self indentLevel: newIndent. firstAddition ifNil: [firstAddition := priorMorph]. morphList add: priorMorph. "Was this row expanded ? if true -> expand it again " ((item hasEquivalentIn: expandedItems) or: [priorMorph isExpanded]) ifTrue: [priorMorph isExpanded: true. priorMorph addChildrenForList: self addingTo: morphList withExpandedItems: expandedItems]] in MorphTreeMorph>>addMorphsTo:from:withExpandedItems:atLevel: in Block: [:item :idx | ... Array(SequenceableCollection)>>withIndexDo: Array(Collection)>>doWithIndex: MorphTreeMorph>>addMorphsTo:from:withExpandedItems:atLevel: MorphTreeMorph>>addSubmorphsFromNodeList:previouslyExpanded: MorphTreeMorph>>addSubmorphsFromNodeList MorphTreeMorph>>buildContents FileListGrid>>treeMorph FileList>>morphicGrid FileList>>grid FileList>>updateFileList FileList>>reference: FileList>>directory: FileList>>initialize FileList class(Behavior)>>new On Thu, Dec 23, 2021 at 4:23 PM Stewart MacLean <stewart(a)xtra.co.nz> wrote: > Hi All, > > This is my first post! Sadly it is to enquire about an issue with the > FileBrowser on the Mac M1. > > I am encountering this exception - FileDoesNotExistException. > > I appears to be opening on just two files: > > [image: image.png] > > I have seen a similar error reported on Windows. Looks like Pharo can't > access the attributes of these files? > https://github.com/pharo-project/pharo/issues/3571 > > I'm exploring Pharo with a view to migrating my VisualWorks project of > many years, as support for M1 looks like it might be a way off, so not a > good start! > > Any help appreciated. > > Thanks, > > Stewart > > ==================================================================== > Pharo 9.0.0 > Build information: > Pharo-9.0.0+build.1573.sha.0e09d756fc99383cbb498565200d9e5e9841ce11 (64 Bit) > > Mac Mini M1 (2020) > Monterey 12.0.1 > > File class>>signalError:for: > File class>>primFileAttribute:number: > File class>>fileAttribute:number: > MacStore(DiskStore)>>sizeOf: > FileSystem>>sizeOf: > FileReference>>size > FileReference(AbstractFileReference)>>humanReadableSize > FileListGridNode>>fileSize > [:node :cont | node perform: self rowMorphGetSelector] in > MorphTreeColumn>>rowMorphGetterBlock in Block: [:node :cont | node perform: > self rowMorphGetSelec...etc... > MorphTreeColumn>>rowMorphFor: > [:col | | v | > v := col rowMorphFor: complexContents. > controls add: v. > col -> v] in MorphTreeNodeMorph>>buildRowMorph in Block: [:col | | v |... > OrderedCollection>>collect: > MorphTreeNodeMorph>>buildRowMorph > MorphTreeNodeMorph>>initRow > MorphTreeNodeMorph>>initWithContents:prior:forList:indentLevel: > [:item :idx | > priorMorph := self indentingItemClass new > initWithContents: item > prior: priorMorph > forList: self > indentLevel: newIndent. > firstAddition > ifNil: [firstAddition := priorMorph]. > morphList add: priorMorph. > "Was this row expanded ? if true -> expand it > again " > ((item hasEquivalentIn: expandedItems) > or: [priorMorph isExpanded]) > ifTrue: [priorMorph isExpanded: true. > priorMorph > addChildrenForList: self > addingTo: morphList > withExpandedItems: expandedItems]] in > MorphTreeMorph>>addMorphsTo:from:withExpandedItems:atLevel: in Block: > [:item :idx | ... > Array(SequenceableCollection)>>withIndexDo: > Array(Collection)>>doWithIndex: > MorphTreeMorph>>addMorphsTo:from:withExpandedItems:atLevel: > MorphTreeMorph>>addSubmorphsFromNodeList:previouslyExpanded: > MorphTreeMorph>>addSubmorphsFromNodeList > MorphTreeMorph>>buildContents > FileListGrid>>treeMorph > FileList>>morphicGrid > FileList>>grid > FileList>>updateFileList > FileList>>reference: > FileList>>directory: > FileList>>initialize > FileList class(Behavior)>>new > > >

Dec. 23, 2021

Re: pharo9 tools moldability

by Esteban Lorenzano

you have also this : https://github.com/pharo-spec/smalltodo-example/blob/master/SmallTODO-Tutor… Esteban On Dec 19 2021, at 8:37 pm, Danil Osipchuk <danil.osipchuk(a)gmail.com> wrote: > Sebastian, yes, this is exactly kind of writeups I was asking for -- thanks > > regards, > Danil > > > > Ð²Ñ, 19 Ð´ÐµÐº. 2021 Ð³. Ð² 20:19, Sebastian Jordan Montano <sebastian.jordan(a)inria.fr (mailto:sebastian.jordan@inria.fr)>: > > This may interest you: > > > > > > https://modularmoose.org/2021/05/04/how-to-build-a-new-moose-tool.html > > > > > De: "Danil Osipchuk" <danil.osipchuk(a)gmail.com (mailto:danil.osipchuk@gmail.com)> > > > Ã: "Pharo Development List" <pharo-dev(a)lists.pharo.org (mailto:pharo-dev@lists.pharo.org)> > > > EnvoyÃ©: Samedi 18 DÃ©cembre 2021 15:06:33 > > > Objet: [Pharo-dev] pharo9 tools moldability > > > > > > > Dear all, > > > > > > Being a long time smalltalk user (meaning I'm crafting tools for my own usage for domains I'm working with) I always relied upon the environment itself to interact with models to spare time creating user interfaces. Besides plain inspectors I used metafacilities where possible -- seaside, then omnibrowser and lately glamour toolkit in pharo8. > > > Now it seems the glamourous core is not part of pharo9 anymore. Meanwhile pharo9 looks increasingly neat and I would like to make a transition but having tools in pharo8 holds me back. > > > I would be grateful for any pointers to help me to get started with the moldable inspectors pharo9 - papers, talks, online discussions, etc. I can likely figure it out on my own, but having an overall understanding of the approach concept would save an effort and shorten the trial and error phase. > > > (maybe I'm overcomplicating it and just having browsed around inspector code pragmas is enough to get started) > > > > > > > > > > > > > > > regards, > > > Danil > > > > > > > > > > > > >

Dec. 20, 2021

Re: pharo9 tools moldability

by Danil Osipchuk

Sebastian, yes, this is exactly kind of writeups I was asking for -- thanks regards, Danil Ð²Ñ, 19 Ð´ÐµÐº. 2021 Ð³. Ð² 20:19, Sebastian Jordan Montano < sebastian.jordan(a)inria.fr>: > This may interest you: > > https://modularmoose.org/2021/05/04/how-to-build-a-new-moose-tool.html > > ------------------------------ > > *De: *"Danil Osipchuk" <danil.osipchuk(a)gmail.com> > *Ã: *"Pharo Development List" <pharo-dev(a)lists.pharo.org> > *EnvoyÃ©: *Samedi 18 DÃ©cembre 2021 15:06:33 > *Objet: *[Pharo-dev] pharo9 tools moldability > > Dear all, > > Being a long time smalltalk user (meaning I'm crafting tools for my own > usage for domains I'm working with) I always relied upon the environment > itself to interact with models to spare time creating user interfaces. > Besides plain inspectors I used metafacilities where possible -- seaside, > then omnibrowser and lately glamour toolkit in pharo8. > > Now it seems the glamourous core is not part of pharo9 anymore. Meanwhile > pharo9 looks increasingly neat and I would like to make a transition but > having tools in pharo8 holds me back. > > I would be grateful for any pointers to help me to get started with the > moldable inspectors pharo9 - papers, talks, online discussions, etc. I can > likely figure it out on my own, but having an overall understanding of the > approach concept would save an effort and shorten the trial and error > phase. > (maybe I'm overcomplicating it and just having browsed around inspector > code pragmas is enough to get started) > > > > regards, > Danil > >

Dec. 19, 2021

Re: pharo9 tools moldability

by Danil Osipchuk

Stephane, yes the AbstractFileReference extensions is definitely a very illustrative example. >From a quick glance it all seems to be pretty straightforward. Also I'd like to use this opportunity to congratulate all who worked hard to make the Pharo9 release possible. It is impressive how clean the code and even UI are now, I would say on par with Dolphin which is a high bar. Obviously a lot of care went into this. Also the books and infrastructure around the project - it is amazing. regards, Danil Ð²Ñ, 19 Ð´ÐµÐº. 2021 Ð³. Ð² 00:07, stephane ducasse <stephane.ducasse(a)inria.fr>: > Hi danil > > Have a look at the extension in FileReference for example. > You will see how you can extend the default inspector. > > What you should see is that you can use any Spec20 UI within the panes. > So we get the extensibility without the glamour and we gain the uniformity > of > using Spec20. > > For us the moldability is important. If you have scenario that do not work > we will study because > the current version may need some adjustments. > But what I can garantee is that we want to make sure that we can all build > our own tools. > > Here are the extensions we are using for a new compiler we are building > > > On 18 Dec 2021, at 16:06, Danil Osipchuk <danil.osipchuk(a)gmail.com> wrote: > > Dear all, > > Being a long time smalltalk user (meaning I'm crafting tools for my own > usage for domains I'm working with) I always relied upon the environment > itself to interact with models to spare time creating user interfaces. > Besides plain inspectors I used metafacilities where possible -- seaside, > then omnibrowser and lately glamour toolkit in pharo8. > > Now it seems the glamourous core is not part of pharo9 anymore. Meanwhile > pharo9 looks increasingly neat and I would like to make a transition but > having tools in pharo8 holds me back. > > I would be grateful for any pointers to help me to get started with the > moldable inspectors pharo9 - papers, talks, online discussions, etc. I can > likely figure it out on my own, but having an overall understanding of the > approach concept would save an effort and shorten the trial and error > phase. > (maybe I'm overcomplicating it and just having browsed around inspector > code pragmas is enough to get started) > > > > regards, > Danil > > >

Dec. 19, 2021

Re: pharo9 tools moldability

by Sebastian Jordan Montano

This may interest you: https://modularmoose.org/2021/05/04/how-to-build-a-new-moose-tool.html > De: "Danil Osipchuk" <danil.osipchuk(a)gmail.com> > Ã: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > EnvoyÃ©: Samedi 18 DÃ©cembre 2021 15:06:33 > Objet: [Pharo-dev] pharo9 tools moldability > Dear all, > Being a long time smalltalk user (meaning I'm crafting tools for my own usage > for domains I'm working with) I always relied upon the environment itself to > interact with models to spare time creating user interfaces. Besides plain > inspectors I used metafacilities where possible -- seaside, then omnibrowser > and lately glamour toolkit in pharo8. > Now it seems the glamourous core is not part of pharo9 anymore. Meanwhile pharo9 > looks increasingly neat and I would like to make a transition but having tools > in pharo8 holds me back. > I would be grateful for any pointers to help me to get started with the moldable > inspectors pharo9 - papers, talks, online discussions, etc. I can likely figure > it out on my own, but having an overall understanding of the approach concept > would save an effort and shorten the trial and error phase. > (maybe I'm overcomplicating it and just having browsed around inspector code > pragmas is enough to get started) > regards, > Danil

Dec. 19, 2021

Re: pharo9 tools moldability

by stephane ducasse

Hi danil Have a look at the extension in FileReference for example. You will see how you can extend the default inspector. What you should see is that you can use any Spec20 UI within the panes. So we get the extensibility without the glamour and we gain the uniformity of using Spec20. For us the moldability is important. If you have scenario that do not work we will study because the current version may need some adjustments. But what I can garantee is that we want to make sure that we can all build our own tools. Here are the extensions we are using for a new compiler we are building > On 18 Dec 2021, at 16:06, Danil Osipchuk <danil.osipchuk(a)gmail.com> wrote: > > Dear all, > > Being a long time smalltalk user (meaning I'm crafting tools for my own usage for domains I'm working with) I always relied upon the environment itself to interact with models to spare time creating user interfaces. Besides plain inspectors I used metafacilities where possible -- seaside, then omnibrowser and lately glamour toolkit in pharo8. > > Now it seems the glamourous core is not part of pharo9 anymore. Meanwhile pharo9 looks increasingly neat and I would like to make a transition but having tools in pharo8 holds me back. > > I would be grateful for any pointers to help me to get started with the moldable inspectors pharo9 - papers, talks, online discussions, etc. I can likely figure it out on my own, but having an overall understanding of the approach concept would save an effort and shorten the trial and error phase. > (maybe I'm overcomplicating it and just having browsed around inspector code pragmas is enough to get started) > > > > regards, > Danil

Dec. 18, 2021

pharo9 tools moldability

by Danil Osipchuk

Dear all, Being a long time smalltalk user (meaning I'm crafting tools for my own usage for domains I'm working with) I always relied upon the environment itself to interact with models to spare time creating user interfaces. Besides plain inspectors I used metafacilities where possible -- seaside, then omnibrowser and lately glamour toolkit in pharo8. Now it seems the glamourous core is not part of pharo9 anymore. Meanwhile pharo9 looks increasingly neat and I would like to make a transition but having tools in pharo8 holds me back. I would be grateful for any pointers to help me to get started with the moldable inspectors pharo9 - papers, talks, online discussions, etc. I can likely figure it out on my own, but having an overall understanding of the approach concept would save an effort and shorten the trial and error phase. (maybe I'm overcomplicating it and just having browsed around inspector code pragmas is enough to get started) regards, Danil

Dec. 18, 2021