- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Recommended production VM on latest macOS Sierra?

by Esteban Lorenzano

pharo 6 is very stable and should be used in production. every version has bugs, that will not change. Yes, that particular bug can be annoying but it does not happens always (for example, Iâm unable to reproduce it, which is in fact part of the reason why I cannot fix it). cheers, Esteban > On 5 Jul 2017, at 14:39, Tim Mackinnon <tim(a)testit.works> wrote: > > So does that mean we should use the Pharo5 vm for production then? It sounds like 6 is still a bit bleeding edge and for production applications we should wait for 6.1? > > At the moment it seems a little chaotic - we all like the new features, and 6 is definitely a breath of fresh air - however if you want to deploy something commercially then you need stability. > > > Tim > >> On 3 Jul 2017, at 19:28, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> Hi, >> >>> On 3 Jul 2017, at 20:08, Bernhard Pieber <bernhard(a)pieber.com> wrote: >>> >>> Hi, >>> >>> What VM would you recommend for a production app on macOS Sierra? >>> - Pharo 6, right? >> yes >> >>> - I assume 32-bit because 64-bit is still experimental, right? >> not particularly, you can download it and use it. >> some tests fails but people is already using it (iceberg will not work, but AFAIK, is the only thing that does not works). >> >>> - The one I get with âcurl get.pharo.org | bashâ has a reproducible crash when typing (https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/141) So it canât be the recommended one, right? >> nevertheless is the current recommended one, and that bug is annoying us all :) >> >> but we hope to be able to fix it eventually, of course :) >> >> cheers! >> Esteban >> >>> >>> I must admit I am quite confused. >>> >>> Cheers, >>> Bernhard >> >> > >

July 5, 2017

SmartTest

by Benoit Verhaeghe

Hi everyone, Iâm working on a new plugin for Nautilus/Calypso that will help us with the test. The goal is to provide us the selection of tests we should run after a modification. It would be great if you accept to try it or want to use it. Currently, by installing the plugin, when you select a method in Calypso or Nautilus, you will see a new critique that will offer you to run the test relative to the method youâve selected (or class ^^ ) Another goal is to calculate the efficient of this new tool and how we will use it. Itâs why Iâve also developed a plugin that will record how we will use the plugin. If you accept to help me. Please tell me ( so i will be able to estimate how many data I will obtain ). Now the commands. If youâd like to help me. The command is simple : Metacello new smalltalkhubUser: 'badetitou' project: 'TestsUsageAnalyser-CoraExtends'; configuration: 'TestsUsageAnalyser_CORAExtends'; version: #stable; get; load. If youâd like to use the plugin or just want to try it. Itâs also simple Metacello new smalltalkhubUser: 'badetitou' project: 'CORA'; configuration: 'CORA'; version: #stable; get; load. For the version with Calypso ( because itâs cool ). Metacello new smalltalkhubUser: 'badetitou' project: 'CORA'; configuration: 'CORA_Calypso'; version: #stable; get; load. So, if you want to help me and use calypso you should run the first and the third command. Options for the plugin are available in the settings of Pharo in the group : âTestRegressionâ. So you can extend the plugin with your own logic of testing strategy. To disable the spy (first package) in the option please uncheck âTest Usage Analyserâ Iâm going to write a blog post that will explain all the plugin and how to use it. If you find bugs ( But there are no bugs ;) ) please tell me and i will fix it as soon as possible. If youâd like that I add a feature, tell me too. Thanks a lot for your help. BenoÃ®t Verhaeghe

July 5, 2017

Re: [Pharo-dev] Recommended production VM on latest macOS Sierra?

by Tim Mackinnon

So does that mean we should use the Pharo5 vm for production then? It sounds like 6 is still a bit bleeding edge and for production applications we should wait for 6.1? At the moment it seems a little chaotic - we all like the new features, and 6 is definitely a breath of fresh air - however if you want to deploy something commercially then you need stability. Tim > On 3 Jul 2017, at 19:28, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > >> On 3 Jul 2017, at 20:08, Bernhard Pieber <bernhard(a)pieber.com> wrote: >> >> Hi, >> >> What VM would you recommend for a production app on macOS Sierra? >> - Pharo 6, right? > yes > >> - I assume 32-bit because 64-bit is still experimental, right? > not particularly, you can download it and use it. > some tests fails but people is already using it (iceberg will not work, but AFAIK, is the only thing that does not works). > >> - The one I get with âcurl get.pharo.org | bashâ has a reproducible crash when typing (https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/141) So it canât be the recommended one, right? > nevertheless is the current recommended one, and that bug is annoying us all :) > > but we hope to be able to fix it eventually, of course :) > > cheers! > Esteban > >> >> I must admit I am quite confused. >> >> Cheers, >> Bernhard > >

July 5, 2017

Ideas wanted: "Patterns to sustain feedback loops"

by Marcus Denker

Hi, I want to do a third talk at ESUG as the âpart 3â of the feedback loop series.. The first parts where: 1. Nomads do not build Cathedrals: https://www.slideshare.net/MarcusDenker/2014-esugcathedral 2. Perfection and Feedback Loops: Why worse is better. https://www.slideshare.net/MarcusDenker/perfection-feedback-loops-or-why-wo… The idea for part 3 is to do something along the lines of âpatterns to enable feedback loopsâ, a more practical view on what one should be doing (or not be doing) to enable and sustain a project as a feedback loop. - both things we do and those we should - things that we do wrong / anti patterns - technical as well as social (communityâ¦) - examples you have seen in the real world The idea is not to follow a formal patterns language, it will be informalâ¦ so if you have any ideas, please send a private mail to me. Marcus

July 5, 2017

Re: [Pharo-dev] Pull requests reviews

by Esteban Lorenzano

donât need it. Iâm working on tool for that :) > On 5 Jul 2017, at 10:02, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > If you don't mind, I'll transform your script into a class and commit it somewhere :) > > On Wed, Jul 5, 2017 at 8:30 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: > So loading of the PR packages is very simple. Do at the end: > > diff := IceDiff from: headCommit to: bootstrapCommit. > diff changedPackages do: #reload. > > > > 2017-07-04 17:33 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>>: > I prepared a script that should help you with the reviews of the pull requests on Pharo 7. We will later convert it into a more fancy tool. It does next steps: > > - sets the basic information: pull request number, path to your pharo repository clone, name of your fork. > - registers the repository into Iceberg and sets pull and push target remotes > - switches branch to a particular commit from which the Pharo image was bootstrapped > - registers the repository into into Monticello packages to be able to do correct diffs > - gets basic information about the pull request from GitHub (original repository, branch name) > - registers the PR original repository into remotes if needed and fetches information from it > - creates a new local branch to merge the PR > - merges the PR branch > - displays a simple tool that shows differences in done in this merged branch > > -------- > > pullRequest := 73. > target := '/path/pharo' asFileReference. > myForkName := 'myFork'. > > repository := IceRepositoryCreator new location: target; subdirectory:'src'; createRepository. > repository register. > fork := repository remotes detect: [ :remote | remote remoteName = myForkName ]. > repository pushRemote: fork. > repository pullRemote: repository origin. > repository checkoutBranch: (SystemVersion current commitHash). > > fileTreeRepository := (MCFileTreeRepository new directory: target / #src; yourself). > repositoryGroup := MCRepositoryGroup withRepositories: { fileTreeRepository. MCCacheRepository uniqueInstance. }. > MCWorkingCopy allManagers > select: [ :wc | (wc repositoryGroup repositories reject: [ :repo | repo isCache ]) isEmpty ] > thenDo: [ :wc | wc repositoryGroup: repositoryGroup ]. > > stonString := (ZnEasy get: 'https://api.github.com/repos/pharo-project/pharo/pulls/ <https://api.github.com/repos/pharo-project/pharo/pulls/>', pullRequest asString) contents. > head := (STONJSON fromString: stonString) at: 'head'. > sshUrl := (head at: #repo) at: 'ssh_url'. > branchName := head at: #ref. > user := (sshUrl withoutPrefix: 'git(a)github.com:') withoutSuffix: '/pharo.git'. > > fork := repository remotes detect: [ :remote | remote remoteName = user ] ifNone: [ > | newFork | > newFork := (IceRemote name: user url: ('git@github.com:{1}/pharo.git' format: {user})). > repository addRemote: newFork. > newFork ]. > > repository fetchFrom: fork. > > prMergedBranchName := 'pr', pullRequest asString. > repository createBranch: prMergedBranchName. > repository checkoutBranch: prMergedBranchName. > > commit := repository revparse: user, '/', branchName. > bootstrapCommit := repository revparse: (SystemVersion current commitHash). > [ repository backend merge: commit id ] > on: IceMergeAborted > do: [ :error | repository mergeConflictsWith: commit ] . > headCommit := repository revparse: 'HEAD'. > > browser := GLMTabulator new. > browser row: [:row | row column: #commits span: 2; column: #changes span: 3]; row: #diff. > browser transmit to: #commits. > browser transmit to: #changes; from: #commits; andShow: [ :a :commitInfo | > (IceDiffChangeTreeBuilder new entity: commitInfo; diff: (IceDiff from: commitInfo to: bootstrapCommit); buildOn: a) title: 'Changes'. ]. > browser transmit from: #commits; from: #changes; to: #diff; andShow: [ :a | > a diff title: 'Left: working copy / Right: incoming updates'; display: [ :commitInfo :change | > { change theirVersion ifNil: ''. change myVersion ifNil: ''. }]]. > browser openOn: {headCommit}. > > -------- > > The merge operation only changes the Git working copy, no code is loaded into the image. If you want to test the PR code, currently you need to open Iceberg and reload all packages in the Pharo repository (Packages tab, Reload all) > > Expect troubles :-) > > Cheers, > -- Pavel > > > > > > > -- > > Guille Polito > > Research Engineer > French National Center for Scientific Research - http://www.cnrs.fr <http://www.cnrs.fr/> > > > Web: http://guillep.github.io <http://guillep.github.io/> > Phone: +33 06 52 70 66 13

July 5, 2017

Re: [Pharo-dev] Pull requests reviews

by Guillermo Polito

If you don't mind, I'll transform your script into a class and commit it somewhere :) On Wed, Jul 5, 2017 at 8:30 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > So loading of the PR packages is very simple. Do at the end: > > diff := IceDiff from: headCommit to: bootstrapCommit. > diff changedPackages do: #reload. > > > > 2017-07-04 17:33 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > >> I prepared a script that should help you with the reviews of the pull >> requests on Pharo 7. We will later convert it into a more fancy tool. It >> does next steps: >> >> - sets the basic information: pull request number, path to your pharo >> repository clone, name of your fork. >> - registers the repository into Iceberg and sets pull and push target >> remotes >> - switches branch to a particular commit from which the Pharo image was >> bootstrapped >> - registers the repository into into Monticello packages to be able to do >> correct diffs >> - gets basic information about the pull request from GitHub (original >> repository, branch name) >> - registers the PR original repository into remotes if needed and fetches >> information from it >> - creates a new local branch to merge the PR >> - merges the PR branch >> - displays a simple tool that shows differences in done in this merged >> branch >> >> -------- >> >> pullRequest := 73. >> target := '/path/pharo' asFileReference. >> myForkName := 'myFork'. >> >> repository := IceRepositoryCreator new location: target; >> subdirectory:'src'; createRepository. >> repository register. >> fork := repository remotes detect: [ :remote | remote remoteName = >> myForkName ]. >> repository pushRemote: fork. >> repository pullRemote: repository origin. >> repository checkoutBranch: (SystemVersion current commitHash). >> >> fileTreeRepository := (MCFileTreeRepository new directory: target / >> #src; yourself). >> repositoryGroup := MCRepositoryGroup withRepositories: { >> fileTreeRepository. MCCacheRepository uniqueInstance. }. >> MCWorkingCopy allManagers >> select: [ :wc | (wc repositoryGroup repositories reject: [ :repo | repo >> isCache ]) isEmpty ] >> thenDo: [ :wc | wc repositoryGroup: repositoryGroup ]. >> >> stonString := (ZnEasy get: 'https://api.github.com/repos/ >> pharo-project/pharo/pulls/', pullRequest asString) contents. >> head := (STONJSON fromString: stonString) at: 'head'. >> sshUrl := (head at: #repo) at: 'ssh_url'. >> branchName := head at: #ref. >> user := (sshUrl withoutPrefix: 'git(a)github.com:') withoutSuffix: >> '/pharo.git'. >> >> fork := repository remotes detect: [ :remote | remote remoteName = user ] >> ifNone: [ >> | newFork | >> newFork := (IceRemote name: user url: ('git@github.com:{1}/pharo.git' >> format: {user})). >> repository addRemote: newFork. >> newFork ]. >> >> repository fetchFrom: fork. >> >> prMergedBranchName := 'pr', pullRequest asString. >> repository createBranch: prMergedBranchName. >> repository checkoutBranch: prMergedBranchName. >> >> commit := repository revparse: user, '/', branchName. >> bootstrapCommit := repository revparse: (SystemVersion current >> commitHash). >> [ repository backend merge: commit id ] >> on: IceMergeAborted >> do: [ :error | repository mergeConflictsWith: commit ] . >> headCommit := repository revparse: 'HEAD'. >> >> browser := GLMTabulator new. >> browser row: [:row | row column: #commits span: 2; column: #changes span: >> 3]; row: #diff. >> browser transmit to: #commits. >> browser transmit to: #changes; from: #commits; andShow: [ :a :commitInfo >> | >> (IceDiffChangeTreeBuilder new entity: commitInfo; diff: (IceDiff from: >> commitInfo to: bootstrapCommit); buildOn: a) title: 'Changes'. ]. >> browser transmit from: #commits; from: #changes; to: #diff; andShow: [ >> :a | >> a diff title: 'Left: working copy / Right: incoming updates'; display: [ >> :commitInfo :change | >> { change theirVersion ifNil: ''. change myVersion ifNil: ''. }]]. >> browser openOn: {headCommit}. >> >> -------- >> >> The merge operation only changes the Git working copy, no code is loaded >> into the image. If you want to test the PR code, currently you need to open >> Iceberg and reload all packages in the Pharo repository (Packages tab, >> Reload all) >> >> Expect troubles :-) >> >> Cheers, >> -- Pavel >> >> >> > -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

July 5, 2017

Re: [Pharo-dev] P6 crashed image

by Hilaire

Hi David, Removing did not make the image to start, althought it produces a different output. But never mind. Stephane, the image crash is not such a big deal. Now I really want to use Glamour because it can help to produce more friendly user interface for kids and scripting. Hilaire Le 05/07/2017 Ã 07:51, Stephane Ducasse a Ã©crit : > Hi hilaire > > We should throw away this plugin it is a bug nest. > Sorry because it does not solve your problem and this is super annoying for us. > > Stef -- Dr. Geo http://drgeo.eu

July 5, 2017

[ANN] association.pharo.org now on AWS

by Marcus Denker

Hi, I just changed the DNS entry for https://association.pharo.org It now runs on Amazon AWS, this should make it faster and more reliable than in the past. Marcus

July 5, 2017

Re: [Pharo-dev] [ANN] Iceberg 0.5 released

by Norbert Hartl

Great! All I wanted to hear! Thanks, Norbert > Am 05.07.2017 um 07:56 schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: > > Yes there will be a nice 6.1 because we care of people. > > Stef > > On Mon, Jul 3, 2017 at 4:39 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> Am 03.07.2017 um 14:45 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> >> On 3 Jul 2017, at 13:32, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> So it is decided there won't be an official pharo6 supporting iceberg? >> >> >> not today :) >> I will release Pharo 6.1 with updated icebergâ¦ because it requires a new VM >> and I donât want to break current downloaded version. >> Problem is: once we jump to 6.1, 6.0 will not be maintained anymoreâ¦ not >> cool, maybe. But inevitable due the amount of effort we can put there. >> >> Ok, understood! And glad we will have 6.1. Great! >> >> Norbert >> >> Esteban >> >> >> Norbert >> >> Am 03.07.2017 um 13:28 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> >> On 3 Jul 2017, at 13:18, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> Hi all, >> Iâm releasing 0.5 version of iceberg. >> This is the changelog: >> >> Major changes: >> ---- >> - works on 64bits >> - adds cheery-pick >> >> Other: >> ---- >> This version also includes a list of fixes, most important one is this: >> >> - branchs are kept inline with local working copy (so if you change a branch >> in command line or in another image it will indicate it correctly) >> >> But there are many others, next version will have a full list, I promise :) >> >> Now, to actually use it you will need to accomplish several steps (until I >> update the image) >> >> 1) You need to download the new stable VM for P7 (it does not matters if you >> are on P6). >> Zeroconf: >> >> 64bits: >> wget -O- get.pharo.org/64/vm70 | bash >> wget -O- get.pharo.org/64/vmT70 | bash #If you are on linux >> >> 32bits: >> wget -O- get.pharo.org/vm70 | bash >> wget -O- get.pharo.org/vmT70 | bash #If you are on linux >> >> then, to update, execute this (sorry, this is like that because we have >> still an older Metacello version): >> >> #('Iceberg-UI' 'Iceberg-Plugin' 'Iceberg-Metacello-Integration' >> 'Iceberg-Libgit' 'Iceberg' 'BaselineOfIceberg' 'LibGit-Core' >> 'BaselineOfLibGitâ) >> do: [ :each | each asPackage removeFromSystem ]. >> >> Metacello new >> baseline: 'Iceberg'; >> repository: 'github://pharo-vcs/iceberg'; >> load. >> >> >> Maybe I was not clearâ¦ this script works also for P6 (*if * you have the new >> VM) :) >> >> >> cheers! >> Esteban >> >> >> >>

July 5, 2017

Re: [Pharo-dev] [ANN] for P7, default VM for linux moved to threaded

by Esteban Lorenzano

usually, you will not notice a problem. but threaded is needed for Iceberg and OSSubprocess to work :( Esteban > On 5 Jul 2017, at 07:54, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > What are the implications? > > Stef > > On Mon, Jul 3, 2017 at 2:39 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Hi, >> >> I made default vm for linux (for P7) the default VM. >> >> I also updated zeroconf to add a new type of download for linux: the explicit iTimer heartbeat download. >> >> >> So, for P7, if you download the default stable VMâ¦ it will be a threaded VM. Take that into account :) >> >> Esteban >> >> >

July 5, 2017