- Pharo-dev - lists.pharo.org

[ Pharo 70 ] build 27 - 20009 Recompilation of trait methods creates changes recoâ¦

by Guillermo Polito

https://github.com/pharo-project/pharo/pull/103 https://pharo.fogbugz.com/f/cases/20009/ -- 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

Aug. 11, 2017

[ Pharo 70 ] build 26 - 13217 FS #basename with compound path string

by Guillermo Polito

https://github.com/pharo-project/pharo/pull/192 https://pharo.fogbugz.com/f/cases/13217/ -- 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

Aug. 11, 2017

Re: [Pharo-dev] Launcher Error w Pharo 7

by Tim Mackinnon

Hi Sean - I know that the vm was upgraded due to new feature requirements of libgit so I'm guessing you don't have the latest vm? I think the one in 6.1 should work currently. But maybe someone else will kick in. Tim Sent from my iPhone > On 10 Aug 2017, at 23:51, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > I just downloaded Launcher for Mac via the CI. I created a Pharo 7 image and > launched it. The following error came up: "Error: External module not found" > from libgit2_init. I assume it's because libgit2 is not installed on my > system. If that's right, how do I set it up e.g. What's the best way to get > it? Does it have to be in a certain location? etc, etc. > > Thanks > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Launcher-Error-w-Pharo-7-tp4959777.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Aug. 11, 2017

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

by Guillermo Polito

I extended the document with some windows specific instructions also. On Fri, Aug 11, 2017 at 9:31 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > > > On Fri, Aug 11, 2017 at 12:34 AM, Nicolai Hess <nicolaihess(a)gmail.com> > wrote: > >> >> >> 2017-08-10 17:17 GMT+02: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. >>> >> >> >> >> [image: Inline-Bild 1] >> >> >> In option 2, I think this should be "Click on the Edit button", >> > > Thanks, fixed! > >> >> >> >> >>> >>> 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 <+33%206%2052%2070%2066%2013> >>> >> >> > > > -- > > > > 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 <+33%206%2052%2070%2066%2013> > -- 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

Aug. 11, 2017

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

by Guillermo Polito

On Fri, Aug 11, 2017 at 12:34 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > 2017-08-10 17:17 GMT+02: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. >> > > > > [image: Inline-Bild 1] > > > In option 2, I think this should be "Click on the Edit button", > Thanks, fixed! > > > > >> >> 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 <+33%206%2052%2070%2066%2013> >> > > -- 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

Aug. 11, 2017

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

by Guillermo Polito

On Thu, Aug 10, 2017 at 11:58 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > Am 10.08.2017 11:21 nachm. schrieb "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" > > > What does "clone using sourcetree" mean? > Yeap, sorry. I meant https://www.sourcetreeapp.com/ It is a free graphical git client from atlassian. In windows I default to graphical tools :). I assume not most of the people will install a msys environment on their machines (but maybe I'm wrong...). > > > 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... > > >> - that #development branch is used instead of master >> > > I'll make another writeup about the entire process. > > >> - how one can keep his own fork up to date >> > > And about this one too > > >> >> Also it would be good to have the AboutBox in Pharo with the build number >> again. >> > >> Because the ZeroCnnf just gives you a Pharo.image and nobody knows what >> the build number >> or sha was to reproduce how old or new this is. >> > > Well, actually right now > > SystemVersion current > > has the hash of the commit the image was generated from if you check the > inspector. It's then a UI problem and easy to fix. Maybe somebody could use > this to try making a pull request? > > Then, we could add a build number in SystemVersion of course. > > Guille > >> >> Thanks >> T. >> >> >> *Gesendet:* Donnerstag, 10. August 2017 um 17:17 Uhr >> *Von:* "Guillermo Polito" <guillermopolito(a)gmail.com> >> *An:* "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org> >> *Betreff:* [Pharo-dev] Writeup: how to contribute to Pharo >> 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 <+33%206%2052%2070%2066%2013> >> > > > > -- > > > > 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 <+33%206%2052%2070%2066%2013> > > > -- 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

Aug. 11, 2017

Re: [Pharo-dev] Impediment to contributing

by Stephan Eggermont

On 10/08/17 17:16, Guillermo Polito wrote: > 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… > > Of course, expect bugs on it :) Not everything is smooth. If you have > comments, they are welcome. Thanks Guille. Stephan

Aug. 11, 2017

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

by Pavel Krivanek

2017-08-11 0:53 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: > > > 2017-08-10 17:17 GMT+02: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 >> > > Maybe I mixed something up, but following the other (pavel)howto I > thought that I would > clone the origin repository, (and edit iceberg to use the local clone as > the origin) > and later define my (github)-fork as another remote. > > But in your screenshots, it looks like you cloned your pharo fork, and set > the original pharo git project as another remote. > Are both options equal and just differe in which remote is called "pharo" > and which is called "origin" ? > To have pharo-project/pharo as the origin is a scheme that Esteban is using and in past Iceberg had troubles to enable Pharo pluggin correctly for repositories that were not set like that. Now it does not matter, however if you will use your local repository clone more, you will have forks of other people as remotes too and then it is quite natural to have your own fork as only one of them. -- 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 <+33%206%2052%2070%2066%2013> >> > >

Aug. 11, 2017

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

by Guillermo Polito

Le ven. 11 aoÃ»t 2017 Ã 00:53, Nicolai Hess <nicolaihess(a)gmail.com> a Ã©crit : > 2017-08-10 17:17 GMT+02: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/Contribute-a-fix-to… >> >> Of course, expect bugs on it :) Not everything is smooth. If you have >> comments, they are welcome. >> >> Guille >> > > Maybe I mixed something up, but following the other (pavel)howto I > thought that I would > clone the origin repository, (and edit iceberg to use the local clone as > the origin) > and later define my (github)-fork as another remote. > > But in your screenshots, it looks like you cloned your pharo fork, and set > the original pharo git project as another remote. > Are both options equal and just differe in which remote is called "pharo" > and which is called "origin" ? > Bord are similar. If you clone pharo, you set your fork as push remote. If you clone ur fork you set pharo as pull remote. I don't remember if iceberg lets u rename a remote, but I think the remote name is not important but the URL. In any case you need both remotes. If you don't have pharo as remote you wont see the pharo plugin. > > > >> >> -- >> >> >> >> 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 <+33%206%2052%2070%2066%2013> >> > -- 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

Aug. 10, 2017

Re: [Pharo-dev] [Vm-dev] vm crash when using rairedTo: with fractions

by Eliot Miranda

Hi Andrei, On Thu, Aug 10, 2017 at 3:02 AM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Hi, > > I was executing this code '(2009/2000) ** (3958333/100000)' with the > Pharo6.1 distribution and the vm crashed with she stack attached below. > Tried it on both mac and windows 10. > Seems that #raisedTo: has a special case for fractions that ends up > calling #nthRoot: like '2009 nthRoot: 100000' leading to the crash. > The plugin is now fixed; see VMMaker.oscog-eem.2262. I'll generate code soon (am debugging something you're familiar with that takes several hours to run and don't want to generate sources while it's running). But I'm glad you've found a better way! This case creates 600k byte large integers and takes forever to run :-) > Cheers, > Andrei > > > 0xaddeac M LargePositiveInteger(Integer)>quo: 0x314093e8: a(n) > LargePositiveInteger > 0xaddec8 M LargePositiveInteger(LargeInteger)>quo: 0x314093e8: a(n) > LargePositiveInteger > 0xaddee8 M LargePositiveInteger(Integer)>// 0x314093e8: a(n) > LargePositiveInteger > 0xaddf04 M LargePositiveInteger(LargeInteger)>// 0x314093e8: a(n) > LargePositiveInteger > 0xaddf34 I LargePositiveInteger(Integer)>nthRootTruncated: 0x30cc8350: > a(n) LargePositiveInteger > 0xaddf5c I LargePositiveInteger(Integer)>nthRootRounded: 0x30cc8350: a(n) > LargePositiveInteger > 0xaddf88 I SmallInteger(Integer)>nthRoot: 0xfb3=2009 > 0xaddfb4 I Fraction>nthRoot: 0x4f9a940: a(n) Fraction > 0xaddfd8 I Fraction(Number)>raisedTo: 0x4f9a940: a(n) Fraction > 0xaddffc I Fraction(Number)>** 0x4f9a940: a(n) Fraction > 0xade018 M UndefinedObject>DoIt 0x5fe5d00: a(n) UndefinedObject > 0xade048 I OpalCompiler>evaluate 0x4f9a998: a(n) OpalCompiler > 0xade074 I RubSmalltalkEditor>evaluate:andDo: 0x305e5878: a(n) > RubSmalltalkEditor > 0xade09c I RubSmalltalkEditor>highlightEvaluateAndDo: 0x305e5878: a(n) > RubSmalltalkEditor > 0xade0b8 M GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>popupPrint > 0x3062fdc8: a(n) GLMMorphicPharoScri > enderer > 0xade0d8 I MorphicAlarm(MessageSend)>value 0x4f9ab20: a(n) MorphicAlarm > 0xade0f4 M MorphicAlarm>value: 0x4f9ab20: a(n) MorphicAlarm > 0xade114 M WorldState>triggerAlarmsBefore: 0x71bb5e0: a(n) WorldState > 0xade140 M WorldState>runLocalStepMethodsIn: 0x71bb5e0: a(n) WorldState > 0xade164 M WorldState>runStepMethodsIn: 0x71bb5e0: a(n) WorldState > 0xade180 M WorldMorph>runStepMethods 0x6ab7778: a(n) WorldMorph > 0xade198 M WorldState>doOneCycleNowFor: 0x71bb5e0: a(n) WorldState > 0xade1b4 M WorldState>doOneCycleFor: 0x71bb5e0: a(n) WorldState > 0xade1d0 M WorldMorph>doOneCycle 0x6ab7778: a(n) WorldMorph > 0xade1e8 M WorldMorph class>doOneCycle 0x6a9f960: a(n) WorldMorph class > 0xade200 M [] in MorphicUIManager>spawnNewProcess 0x2cc88718: a(n) > MorphicUIManager > 0xade220 I [] in BlockClosure>newProcess 0x2f178150: a(n) BlockClosure > > -- _,,,^..^,,,_ best, Eliot

Aug. 10, 2017