- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Processes, what are they doing?

by Benoit St-Jean

Or option #2.Â Issue a warning for now and deprecated #fork.Â This will give people some time to fix their code. Â ----------------- Benoit St-Jean Yahoo! Messenger: bstjean Blogue: endormitoire.wordpress.com A standpoint is an intellectual horizon of radius zero. (Albert Einstein) >________________________________ > From: Igor Stasenko <siguctua(a)gmail.com> >To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> >Sent: Tuesday, April 23, 2013 7:58:26 PM >Subject: [Pharo-project] Processes, what are they doing? > > >Have you ever seen the list of processes running under your OS? >There's many, isn't? >The operating systems may be different, but i'd like to tell, what is >common between all of them: >- by looking at list of processes you have no idea what each of them >there for, nor what are they doing. > >For instance, myÂ home windows machine has strange peaks of disk >activity (when it supposed to be idle, since it is not touched >more than a hour)... >now this is annoying that i cannot ask system in easy way, what is >going on and why such heavy disk activity is needed, >and disable such "very important feature".. >Today's systems grown too large and too clever, where user more and >more feels like a passenger (which request to stop the train can be >silently ignored), rather than driver of the train who can stop it at >any moment. > >Since i cannot tell, what each process doing on my machine.. i cannot >control them. >There's of course a solution: i should spend hours with google , read >docs & manuals >and in general, look for anywhere else, rather than simply ask a >process: what are you doing, what is your responsibility and who runs >you and why. > >Besides, if i cannot ask the process, my study of a system is more or >less just a waste of time, because even if i learn everything, >tomorrow it will be different OS version or different OS, where >everything will be completely different, and there we starting over >again: having a list of processes and no clue which is responsible for >what and do you need it or not. > >Sure thing, i am not proposing to change the world and fix today's >operating systems, but what i thought that at least in Pharo we have a >good >opportunity to fix that. > >I think it would be beneficial to establish a quality standard (or at >least make an attempt to move closer to it): >- each running process should have a description what its purpose and >who/what running it, as well as how to terminate it in non-abrupt way. > >In practice it means that one should not write: >[ ... ] fork > >but > >[ ... ] forkWithDescription: 'i doing this that and there' > >or even: > >[ ... ] forkWithDescription: 'i doing this that and there' >toTerminateDo: [.. block for graciously terminating this process >regardless in which state it currently is ] > >So, my question are you with me or not? :) >And how far? > >0 - keep things as they are >... >1 - deprecate all protocols which allow anonymous process creation, >and force developers to always put a description for every #fork in >their code. >(or simply refuse to #resume the process unless its description is not nil ;) > >There is already field in Process - name. But it is not enforced by >system that it should be never nil. I am not sure if we need both name >and description >or we need just one field (which will serve for both). What i am sure >about is that anonymous processes are BAD. > >-- >Best regards, >Igor Stasenko. > > > >

April 24, 2013

[Pharo-project] Processes, what are they doing?

by Igor Stasenko

Have you ever seen the list of processes running under your OS? There's many, isn't? The operating systems may be different, but i'd like to tell, what is common between all of them: - by looking at list of processes you have no idea what each of them there for, nor what are they doing. For instance, my home windows machine has strange peaks of disk activity (when it supposed to be idle, since it is not touched more than a hour)... now this is annoying that i cannot ask system in easy way, what is going on and why such heavy disk activity is needed, and disable such "very important feature".. Today's systems grown too large and too clever, where user more and more feels like a passenger (which request to stop the train can be silently ignored), rather than driver of the train who can stop it at any moment. Since i cannot tell, what each process doing on my machine.. i cannot control them. There's of course a solution: i should spend hours with google , read docs & manuals and in general, look for anywhere else, rather than simply ask a process: what are you doing, what is your responsibility and who runs you and why. Besides, if i cannot ask the process, my study of a system is more or less just a waste of time, because even if i learn everything, tomorrow it will be different OS version or different OS, where everything will be completely different, and there we starting over again: having a list of processes and no clue which is responsible for what and do you need it or not. Sure thing, i am not proposing to change the world and fix today's operating systems, but what i thought that at least in Pharo we have a good opportunity to fix that. I think it would be beneficial to establish a quality standard (or at least make an attempt to move closer to it): - each running process should have a description what its purpose and who/what running it, as well as how to terminate it in non-abrupt way. In practice it means that one should not write: [ ... ] fork but [ ... ] forkWithDescription: 'i doing this that and there' or even: [ ... ] forkWithDescription: 'i doing this that and there' toTerminateDo: [.. block for graciously terminating this process regardless in which state it currently is ] So, my question are you with me or not? :) And how far? 0 - keep things as they are ... 1 - deprecate all protocols which allow anonymous process creation, and force developers to always put a description for every #fork in their code. (or simply refuse to #resume the process unless its description is not nil ;) There is already field in Process - name. But it is not enforced by system that it should be never nil. I am not sure if we need both name and description or we need just one field (which will serve for both). What i am sure about is that anonymous processes are BAD. -- Best regards, Igor Stasenko.

April 23, 2013

[Pharo-project] Smart Suggestion Version 1

by Gisela Decuzzi

Hello! After some work I think that Smart Suggestions it's ready to have some real feedback to continue growing up :) What is it? The idea it's to have suggestions based in the text selected or the cursor position. Actually there are suggestions for: - Temporary/Instance/Class Variable - Class - Method (when you are in the selector) - Source (multiple lines) - Message How to install it? Gofer it smalltalkhubUser: 'gisela' project: 'SmartSuggestions'; package: 'SmartSuggestions'; load. Some screen shots: (to activate de menu the shortcut es Ctrl + t for windows or unix and Command + t for mac) [image: ImÃ¡genes integradas 1] [image: ImÃ¡genes integradas 2] [image: ImÃ¡genes integradas 3] How to define a new action? It's easy to define your own action only use the pragma in your custom method and make sure to retunr an instance of SugsSuggestion, examples in SugsSuggestionFactory are categorized by the selection. If you have some comments I will be very happy to heard about, I have removed the actions form nautilus menu, because it was to much visual noise (at least for me) if you want to add it, only uncoment the pragma in: #SugsMenuBuilder>>addSuggestionToSourceCodeMenu: ps: It could appear a DNU when fetching the suggestions for a class variable the description and solution are in https://pharo.fogbugz.com/default.asp?10380#75204

April 23, 2013

Re: [Pharo-project] NativeBoost label call

by Igor Stasenko

Hi, Guido, hmm... as far as i remember, there should be already support for that in asmjit. I remember we did something about it not long ago. But i will check. On 23 April 2013 22:02, Guido Chari <charig(a)gmail.com> wrote: > Hi Igor, > > I need support to call labels in Waterfall. I used to have a changeset with > this changes. > > But now i want to put Waterfall on Jenkins. So it would be easier if NB > already has the implementation. Otherwise i would need to load a changeset > after loading WF code through Metacello. > > I attach you my changes so you can check if you want to integrate them. If > you prefer not to integrate them just tell me so i check for the other > solution. > > Cheers, > Guido. > > -- Best regards, Igor Stasenko.

April 23, 2013

[Pharo-project] NativeBoost label call

by Guido Chari

Hi Igor, I need support to call labels in Waterfall. I used to have a changeset with this changes. But now i want to put Waterfall on Jenkins. So it would be easier if NB already has the implementation. Otherwise i would need to load a changeset after loading WF code through Metacello. I attach you my changes so you can check if you want to integrate them. If you prefer not to integrate them just tell me so i check for the other solution. Cheers, Guido.

April 23, 2013

[Pharo-project] the future of #stable in Metacello

by Dale Henrichs

I've cross-posted to pharo and metacello mailing list ... I'd prefer that the ongoing (possibly gory discussion:) take place on the metacello list, but since symbolic versions have been discussed on the pharo list it might make sense to keep the discussion in the pharo list ... First a bit of background. Symbolic versions were introduced because we were facing a situation where developers were breaking projects that were working fine in Pharo1.3 while porting them to Pharo1.4 and breaking Pharo1.4 behavior while fixing bugs in Pharo1.3 ... Metacello was pretty new then and an attempt was being made to have folks use Pharo1.4 while it was still in development and there were enough changes in Pharo1.4 that some code would break in Pharo1.4 while working in Pharo1.3 ... The real problem though was that project dependencies became difficult to manage in a number of different dimensions: - projects would change existing versions to work on the new platform version and break the old platform version - projects would create a new version that would run on both platforms, so dependent projects would to depend pon a new version - projects would create a new version that would run on only one platform, so dependent projects would have to depend upon 2 different versions based on platform version These types of things in isolation would be manageable, but the rate of change was high and changes propogated faster than configuration managers could keep up with. Oh and don't forget the projects where the maintainers were not even using Metacello at all and a third party developer had to translate the projects changes to a configuration to keep things working... Symbolic versions were introduced as a stopgap measure that made it possible for folks to easily declare which versions of the project were intended to be used on a particular platform. Dependent projects could depend upon the #stable version and the whole dependency management universe became simpler. Symbolic versions made it practical to port code to Pharo1.4 without impacting Pharo1.3 and so on. Which brings us to the present and a slightly different situation, but first let's step back a bit and look at what we have in Metacello today. In Metacello, a version is a label applied to a specific collection of mcz files. The collection of mcz files may be different depending upon which platform you happen to be loading the project into, but in the end, the same version on different platforms should give one the same set of functionality. Once a version has been released (indicated by a #release blessing) the contents of that collection of mcz files should never change ... If a change _is_ made, once should create a new version of the project to reflect that something has changed. In Metacello there are platform attributes (i.e., #'pharo1.x', #'pharo1.4.x', #'pharo1.4.1.x', #'pharo2.x', etc.). The platform attributes can provide very fine-grained control over which mcz files need to be loaded into a particular version of a platform, but the mechanism only works if the underlying platform is consistently naming versions ... In Metacello symbolic versions are simply a tagging mechanism. Versions and symbolic versions can be used interchangeably. Any name/platform/version combination can be created. We have been using the #stable convention for several years and it is definitely time to revisit it's use. However, we cannot drop the #stable convention without replacing it with another convention... otherwise we risk chaos, again:) In Metacello one can specify dependencies in terms of specific version numbers (tight coupling) or a tag (very loose coupling). Allowing one to specify dependencies based on version ranges would provide an intermediate coupling that avoids the tight coupling of specific version numbers while avoiding the ambiguity of a convention based on the name of a tag (symbolic version). If we introduce version range dependencies then individual projects can use a variety symbolic version names to properly represent their desired semantics. If we introduce version range dependencies then we must adopt a convention for how versions are named and that convention must be used pretty consistently within the community otherwise we may just have to return to the world of using #stable in self defense again ... As an alternative to a version numbering convention like Semantic Versioning[1], we could adopt a convention defining the semantics of a collection of symbolic version names .... I am a fan of Semantic Versioning, but it has some pretty specific rules that "must" be followed and all projects including the Smalltalk platforms (GemStone, Pharo and Squeak). Scan through the discussions surrounding Semantic Versions[2] to see what I'm talking about... In the grand scheme of things I don't want Metacello to be locked into any one convention. I am willing to have Metacello to support multiple conventions if called for. I have support for the Semantic Versioning version numbering scheme in Metacello, but other schemes can be added. I have anticipated the need to support version number ranges and have already built in a certain level of support and am willing to expand the capabilities in this area as needed ... Whatever the convention is, it has to be ADOPTED and SUPPORTED by the community. Metacello cannot enforce conventions, it can only support conventions ... So in closing, I would say that the future of #stable is in your hands... Dale [1] http://semver.org/ [2] https://github.com/mojombo/semver/issues

April 23, 2013

Re: [Pharo-project] User account on Jenkins

by Camillo Bruni

On 2013-04-23, at 20:15, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > You can register there by yourself, then there is a list of projects, pick the one you are interested in, Admins will then get a mail to add you you can do that here: https://ci.inria.fr/users/new > On Apr 23, 2013, at 7:45 PM, Guido Chari <charig(a)gmail.com> wrote: > >> Who can add me to Jenkins server so i can add a project to the infrastructure? >

April 23, 2013

Re: [Pharo-project] Your earlier problems accessing Monticello

by Sven Van Caekenberghe

OK, thx. On 23 Apr 2013, at 19:42, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > If a slice is proposed, you should "resolve" the case which flags the issue as Fix Review Needed > > :) > > Ben > > On Apr 23, 2013, at 7:40 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> >> On 23 Apr 2013, at 19:18, Guido Chari <charig(a)gmail.com> wrote: >> >>> Sorry for the delay, but yes i confirm this solves my issue. >> >> Thanks, that is good to know ! >> >>> What i see is that it is not yet integrated into 3.0 >> >> Yeah, it is ready for inclusion, maybe I gave it the wrong status. >> >> https://pharo.fogbugz.com/default.asp?10102 >> https://pharo.fogbugz.com/f/cases/10102/SocketStream-next-should-not-signal… >> >>> Cheers, >>> Guido. >>> >>> >>> 2013/3/23 Guido Chari <charig(a)gmail.com> >>> Yes, i'm sure this will do the fix. Nevertheless, as soon as i come back home i will send you the confirmation. >>> >>> Thanks >>> >>> >>> 2013/3/23 Camillo Bruni <camillobruni(a)gmail.com> >>> Guido is right now in Lille :P so you have to wait for a week. >>> From what I recall it was exactly that bug we had over in Argentina :) >>> >>> On 2013-03-23, at 11:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> Hi Guido, >>>> >>>> Some time ago you were unable to access Monticello from inside your particular network situation. >>>> >>>> http://forum.world.st/Unable-to-use-Monticello-in-last-images-from-Jenkins-… >>>> >>>> We just were able to solve a similar case. >>>> >>>> http://forum.world.st/Problem-downloading-packages-with-Monticello-from-Sma… >>>> >>>> Would it be possible to verify, first that your old problem still exists, and then try again with the following patch. >>>> >>>> SocketStream>>next: count >>>> "Read count elements and return them in a collection. >>>> If the receiver is #atEnd before count elements were read, return a smaller collection." >>>> >>>> ^ self nextInto: (self streamBuffer: count) >>>> >>>> That would be most helpful. >>>> >>>> Thx, >>>> >>>> Sven >>>> >>>> -- >>>> Sven Van Caekenberghe >>>> http://stfx.eu >>>> Smalltalk is the Red Pill >>>> >>>> >>> >>> >>> >>> >> >> >

April 23, 2013

Re: [Pharo-project] User account on Jenkins

by Benjamin

You can register there by yourself, then there is a list of projects, pick the one you are interested in, Admins will then get a mail to add you Ben On Apr 23, 2013, at 7:45 PM, Guido Chari <charig(a)gmail.com> wrote: > Who can add me to Jenkins server so i can add a project to the infrastructure?

April 23, 2013

[Pharo-project] User account on Jenkins

by Guido Chari

Who can add me to Jenkins server so i can add a project to the infrastructure?

April 23, 2013