- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Writeup: how to contribute to Pharo

by Esteban Lorenzano

no is ok. with the pharo version I know the iceberg version :) anyway your problem is that the remote for pharo is bad. you added git(a)github.com <mailto:git@github.com>:pharo/pharo.git and I do not think that exists. Correct one is: git(a)github.com <mailto:git@github.com>:pharo-project/pharo.git Esteban > On 17 Oct 2017, at 11:51, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > I don't see any easy way to find the Iceberg version. > > Should I update Iceberg using this script also in Pharo 7? > > "Restore defaults" > Iceberg enableMetacelloIntegration: false. > MetacelloPharo30Platform select. > > "Update metacello" > Metacello new > baseline: 'Metacello'; > repository: 'github://metacello/metacello:Pharo6.1/repository'; > onConflict: [:e | e useIncoming ]; > get; > load. > > "Update iceberg" > #( > 'Iceberg-UI' > 'Iceberg-Plugin-GitHub' > 'Iceberg-Plugin' > 'Iceberg-Metacello-Integration' > 'Iceberg-Libgit-Tonel' > 'Iceberg-Libgit-Filetree' > 'Iceberg-Libgit' > 'Iceberg' > 'LibGit-Core') > do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil: #removeFromSystem ]. > Metacello new > baseline: 'Iceberg'; > repository: 'github://pharo-vcs/iceberg:v0.6'; > load. > > 2017-10-17 6:46 GMT-03:00 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com>>: > Hi Esteban, > > This one: > > wget -O- get.pharo.org/70+vm <http://get.pharo.org/70+vm> | bash - > > 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > which Pharo version (and Iceberg version) do you have? > > Esteban > >> On 17 Oct 2017, at 04:36, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com>> wrote: >> >> Hi Guille, >> >> In https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to… <https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to…> >> >> This part is not working for me: "Go back to iceberg, right click on the pharo repository and go to the Pharo entry. You'll see the option Create new branch from Fogbugz issue." >> >> Because there is no such "Pharo" option in the menu. See the attached screenshot. >> >> Did I miss something? >> Any suggestion? >> >> >> 2017-08-10 12:17 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>>: >> Hi, >> >> I've made some write up for the pharo part (not metacello or external projects) >> >> https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to… <https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to…> >> >> Of course, expect bugs on it :) Not everything is smooth. If you have comments, they are welcome. >> >> Guille >> >> -- >> >> 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 >> >> <Clipboard01.png> > > >

Oct. 17, 2017

Re: [Pharo-dev] Writeup: how to contribute to Pharo

by HernÃ¡n Morales Durand

I don't see any easy way to find the Iceberg version. Should I update Iceberg using this script also in Pharo 7? "Restore defaults" Iceberg enableMetacelloIntegration: false. MetacelloPharo30Platform select. "Update metacello" Metacello new baseline: 'Metacello'; repository: 'github://metacello/metacello:Pharo6.1/repository'; onConflict: [:e | e useIncoming ]; get; load. "Update iceberg" #( 'Iceberg-UI' 'Iceberg-Plugin-GitHub' 'Iceberg-Plugin' 'Iceberg-Metacello-Integration' 'Iceberg-Libgit-Tonel' 'Iceberg-Libgit-Filetree' 'Iceberg-Libgit' 'Iceberg' 'LibGit-Core') do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil: #removeFromSystem ]. Metacello new baseline: 'Iceberg'; repository: 'github://pharo-vcs/iceberg:v0.6'; load. 2017-10-17 6:46 GMT-03:00 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: > Hi Esteban, > > This one: > > wget -O- get.pharo.org/70+vm | bash - > > 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> which Pharo version (and Iceberg version) do you have? >> >> Esteban >> >> On 17 Oct 2017, at 04:36, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> >> wrote: >> >> Hi Guille, >> >> In https://github.com/guillep/PharoIntegrationProcess/wiki/Cont >> ribute-a-fix-to-Pharo >> >> This part is not working for me: "Go back to iceberg, right click on the >> pharo repository and go to the *Pharo* entry. You'll see the option *Create >> new branch from Fogbugz issue*." >> >> Because there is no such "Pharo" option in the menu. See the attached >> screenshot. >> >> Did I miss something? >> Any suggestion? >> >> >> 2017-08-10 12:17 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com>: >> >>> Hi, >>> >>> I've made some write up for the pharo part (not metacello or external >>> projects) >>> >>> https://github.com/guillep/PharoIntegrationProcess/wiki/Cont >>> ribute-a-fix-to-Pharo >>> >>> Of course, expect bugs on it :) Not everything is smooth. If you have >>> comments, they are welcome. >>> >>> Guille >>> >>> -- >>> >>> 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 >>> >> >> <Clipboard01.png> >> >> >> >

Oct. 17, 2017

Re: [Pharo-dev] Writeup: how to contribute to Pharo

by HernÃ¡n Morales Durand

Hi Esteban, This one: wget -O- get.pharo.org/70+vm | bash - 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > which Pharo version (and Iceberg version) do you have? > > Esteban > > On 17 Oct 2017, at 04:36, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> > wrote: > > Hi Guille, > > In https://github.com/guillep/PharoIntegrationProcess/wiki/ > Contribute-a-fix-to-Pharo > > This part is not working for me: "Go back to iceberg, right click on the > pharo repository and go to the *Pharo* entry. You'll see the option *Create > new branch from Fogbugz issue*." > > Because there is no such "Pharo" option in the menu. See the attached > screenshot. > > Did I miss something? > Any suggestion? > > > 2017-08-10 12:17 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com>: > >> Hi, >> >> I've made some write up for the pharo part (not metacello or external >> projects) >> >> https://github.com/guillep/PharoIntegrationProcess/wiki/Cont >> ribute-a-fix-to-Pharo >> >> Of course, expect bugs on it :) Not everything is smooth. If you have >> comments, they are welcome. >> >> Guille >> >> -- >> >> 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 >> > > <Clipboard01.png> > > >

Oct. 17, 2017

Re: [Pharo-dev] VM specific mailing list

by Esteban Lorenzano

> On 17 Oct 2017, at 10:55, Raffaello Giulietti <raffaello.giulietti(a)lifeware.ch> wrote: > > Hi, > > is there a specific mailing list to discuss about Pharo's VM? vm-dev(a)lists.squeakfoundation.org not âpharoâ specific but vm specific (the pharo vm is a flavour of opensmalltalk-vm) Esteban > > Greetings > Raffaello >

Oct. 17, 2017

VM specific mailing list

by Raffaello Giulietti

Hi, is there a specific mailing list to discuss about Pharo's VM? Greetings Raffaello

Oct. 17, 2017

Re: [Pharo-dev] Writeup: how to contribute to Pharo

by Esteban Lorenzano

which Pharo version (and Iceberg version) do you have? Esteban > On 17 Oct 2017, at 04:36, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Hi Guille, > > In https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to… <https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to…> > > This part is not working for me: "Go back to iceberg, right click on the pharo repository and go to the Pharo entry. You'll see the option Create new branch from Fogbugz issue." > > Because there is no such "Pharo" option in the menu. See the attached screenshot. > > Did I miss something? > Any suggestion? > > > 2017-08-10 12:17 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>>: > Hi, > > I've made some write up for the pharo part (not metacello or external projects) > > https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to… <https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to…> > > Of course, expect bugs on it :) Not everything is smooth. If you have comments, they are welcome. > > Guille > > -- > > 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 > > <Clipboard01.png>

Oct. 17, 2017

Re: [Pharo-dev] Writeup: how to contribute to Pharo

by HernÃ¡n Morales Durand

Hi Guille, In https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to… This part is not working for me: "Go back to iceberg, right click on the pharo repository and go to the *Pharo* entry. You'll see the option *Create new branch from Fogbugz issue*." Because there is no such "Pharo" option in the menu. See the attached screenshot. Did I miss something? Any suggestion? 2017-08-10 12:17 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com>: > Hi, > > I've made some write up for the pharo part (not metacello or external > projects) > > https://github.com/guillep/PharoIntegrationProcess/wiki/Cont > ribute-a-fix-to-Pharo > > Of course, expect bugs on it :) Not everything is smooth. If you have > comments, they are welcome. > > Guille > > -- > > > > 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 >

Oct. 17, 2017

Re: [Pharo-dev] Writeup: how to contribute to Pharo

by HernÃ¡n Morales Durand

2017-08-10 18:20 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com>: > > > On Thu, Aug 10, 2017 at 9:39 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > >> Hi Guille, >> >> nice writeup and definitely needed. Thanks a lot! >> >> If possible you should complete it with: >> - how Windows users could contribute >> > > Hard topic. I'm taking benefit of my gf's windows computer right now to > test. Basically, windows has problems with long paths but there are > workarounds. Icerberg works by default without any changes (same bugs as in > linux and osx at least :)). Here are my notes to make it work: > > * Download latest pharo: > - http://files.pharo.org/image/70/latest-32.zip > - http://files.pharo.org/vm/pharo-spur32/win/stable-20170720.zip > > * Clone using sourcetree > This is very slow and failed to checkout (not clone) because of the > "Filename too long errors" > > I found for this the following workaround: http://pingec.si/blog/ > articles/msysgit-longpath/ > > Once I did that, sourcetree worked nicely, and I could commit and change > branches using iceberg. > > Warning: I did not test making changes on the "long files" to see what > happens... > I tested it on Windows with msysgit. First you have to make the git clone $ git clone https://github.com/hernanmd/pharo.git You have to ***let it fail*** ... "fatal: unable to checkout working tree" ... Then $ cd pharo/ $ git config core.longpaths true $ git checkout -f HEAD Checking out files: 100% (107983/107983), done. Your branch is up-to-date with 'origin/development'.

Oct. 17, 2017

[Pharo 7.0-dev] Build #203: 05723-Default-Working-Directory

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #203 was: SUCCESS. The Pull Request #92 was integrated: "05723-Default-Working-Directory" Pull request url: https://github.com/pharo-project/pharo/pull/92 Issue Url: https://pharo.fogbugz.com/f/cases/05723 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 16, 2017

Re: [Pharo-dev] Test Runner: Walkback when storing result as progress reference

by Marcus Denker

Hello, That feature is implemented in a way that it compiles code. Now if the amount of information it wants to store is large, it tries to compile code that is beyond the limits of the current byte code set (too many literals). Two things to try: -> enable the new bytecode set, it has larger limits. -> rewrite the feature to store the information differently (e.g. in nested arrays) -> maybe we should even remove the feature as it is not used a lot. Marcus > On 14 Oct 2017, at 19:55, Bernhard Pieber <bernhard(a)pieber.com> wrote: > > I just tripped over a walkback when clicking on the menu item âStore result as progress referenceâ in the Test Runner after having run all tests in a Pharo 6.1 (stable) image created by PharoLauncher 1.0.1 on macOS Sierra 10.12.6. Has anyone seen this before? > > Cheers, > Bernhard > > OpalEncoderForV3PlusClosures(Object)>>error: > OpalEncoderForV3PlusClosures(OpalBytecodeEncoder)>>outOfRangeError:index:range:to: > OpalEncoderForV3PlusClosures(OpalEncoderForV3)>>genPushLiteral: > IRBytecodeGenerator>>pushLiteral: > IRTranslatorV2>>visitPushLiteral: > IRPushLiteral>>accept: > IRTranslatorV2(IRVisitor)>>visitNode: > IRTranslatorV2>>visitInstruction: > [ :instr | self visitInstruction: instr ] in IRTranslatorV2(IRVisitor)>>visitSequence: in Block: [ :instr | self visitInstruction: instr ] > OrderedCollection>>do: > IRSequence>>do: > IRTranslatorV2(IRVisitor)>>visitSequence: > IRTranslatorV2>>visitSequence: > IRSequence>>accept: > IRTranslatorV2(IRVisitor)>>visitNode: > [ :each | self visitNode: each ] in IRTranslatorV2(IRVisitor)>>visitNodes: in Block: [ :each | self visitNode: each ] > SortedCollection(OrderedCollection)>>do: > IRTranslatorV2(IRVisitor)>>visitNodes: > IRTranslatorV2>>visitSequences: > IRTranslatorV2>>visitMethod: > IRMethod>>accept: > IRTranslatorV2(IRVisitor)>>visitNode: > IRMethod>>generate: > IRMethod>>compiledMethodWith: > RBMethodNode>>generate: > [ [ ast := self parse. > self doSemanticAnalysis. > self callPlugins ] > on: OCSourceCodeChanged > do: [ :notification | > self source: notification newSourceCode. > notification retry ]. > cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ [ ast := self parse.... > BlockClosure>>on:do: > OpalCompiler>>compile > Metaclass(ClassDescription)>>compile:classified:withStamp:notifying:logSource: > Metaclass(ClassDescription)>>compile:classified:withStamp:notifying: > >

Oct. 16, 2017