January 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

by Denis Kudriashov

Hi 2018-01-17 7:15 GMT+01:00 Max Leske <maxleske(a)gmail.com>: > Hi Martin, > > What I do is > 1. update local pharo repository on branch 'development' > 2. add repository to Iceberg > 3. create branch for phogbugz issue > 4. make changes (e.g. load stuff from your project) > 5. Note that you will have to handle addition and removal of packages > separately: > 5.1 addition: click 'add package' > 5.2 removal: click 'remove package'. You will have to commit the removal > from the command line, as Iceberg does not currently recognize removals as > staged changes. > I usually just make a second commit with the removal before I push > everything. > 6. Now the changes may not show up. But you can right click on the > repository in Iceberg and select 'Synchronize full repository' > 7. Select the changes you want to commit > I think the 4-th step is the question. Epicea in image is managed by Iceberg and hosted in github. How to load new version from external monticello repo? Also there is no ConfigurationOfEpicea in the image. > > The rest you know, I guess ;) > > Cheers, > Max > > > > On 16 January 2018 at 20:16:22, Martin Dias (tinchodias(a)gmail.com) wrote: > > Hi, I followed the guide and everything is good. What I don't know is how > to upgrade an external project already integrated in Pharo 7 (Epicea). I > have new version 8.2.6. > > Cheers, MartÃn. > > On Tue, Jan 9, 2018 at 11:01 AM, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > >> EstebanLM wrote >> >> Mmm. I think this is because your local clone is outdated. >> >> It should be fixed with a fetchâ¦ from pharo-project, I mean :) >> >> That worked. Thanks. Next problem: Iceberg is showing a massive number of >> changes when syncing with pharo fork on the dev branch at the same commit >> as >> the image. There doesn't seem to be a way to collapse the whole tree >> making >> it impossible to find the real changes. I assume it's that known bug where >> the first commit will sync the list, but not very user friendly! >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >> >> >

Jan. 17, 2018

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

by Esteban Lorenzano

> On 17 Jan 2018, at 07:15, Max Leske <maxleske(a)gmail.com> wrote: > > Hi Martin, > > What I do is > 1. update local pharo repository on branch 'development' > 2. add repository to Iceberg > 3. create branch for phogbugz issue > 4. make changes (e.g. load stuff from your project) > 5. Note that you will have to handle addition and removal of packages separately: > 5.1 addition: click 'add package' > 5.2 removal: click 'remove package'. You will have to commit the removal from the command line, as Iceberg does not currently recognize removals as staged changes. > I usually just make a second commit with the removal before I push everything. > 6. Now the changes may not show up. But you can right click on the repository in Iceberg and select 'Synchronize full repository' > 7. Select the changes you want to commit yep, thatâs pretty much the process in that case :) > > The rest you know, I guess ;) > > Cheers, > Max > > > > On 16 January 2018 at 20:16:22, Martin Dias (tinchodias(a)gmail.com <mailto:tinchodias@gmail.com>) wrote: > >> Hi, I followed the guide and everything is good. What I don't know is how to upgrade an external project already integrated in Pharo 7 (Epicea). I have new version 8.2.6. >> >> Cheers, MartÃn. >> >> On Tue, Jan 9, 2018 at 11:01 AM, Sean P. DeNigris <sean(a)clipperadams.com <mailto:sean@clipperadams.com>> wrote: >> EstebanLM wrote >> >> Mmm. I think this is because your local clone is outdated. >> >> It should be fixed with a fetchâ¦ from pharo-project, I mean :) >> >> That worked. Thanks. Next problem: Iceberg is showing a massive number of >> changes when syncing with pharo fork on the dev branch at the same commit as >> the image. There doesn't seem to be a way to collapse the whole tree making >> it impossible to find the real changes. I assume it's that known bug where >> the first commit will sync the list, but not very user friendly! >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html>

Jan. 17, 2018

Re: [Pharo-dev] [Pharo-users] Google Summer of Code 2018 with Pharo Consortium

by Serge Stinckwich

Just a reminder that we need your subject idea ! The deadline to apply is January 23, 2018. Thank you ! On Wed, Jan 10, 2018 at 6:10 AM, Jigyasa Grover <grover.jigyasa1(a)gmail.com> wrote: > Hello Pharo-ers ! > > On behalf of the community, I would like to thank each one of you for their > significant contribution in the previously concluded *Google Summer of Code > 2017* with *Pharo Consortium*. We aspire to take-off on a long flight after > this successful stint by applying to participate in the upcoming *Google > Summer of Code 2018*. > > As many of you might know, Google Summer of Code is a global program > focused > on bringing more student developers into open source software development. > Students work with an open source organization on a 3 month programming > project during their break from school. Read more about the program here: > https://summerofcode.withgoogle.com/ > > The deadline for organisations to apply is January 23, 2018 which is fast > approaching. As an open source evangelist and a Pharo developer, I would > like to invite all the experienced members to be a part of the "GSoC 2018 > with Pharo Consortium" Team and mentor students. Propose fresh ideas for > projects which shall help improve Pharo or volunteer to mentor any of the > existing one (Listed here: http://gsoc.pharo.org/) To add your own > project > idea to the list, visit http://gsoc.pharo.org/#adding-a-proposal > > Looking forward to an appreciable representation from the Pharo community. > > Best regards > Jigyasa Grover > Pharo Consortium Org Admin, Google Summer of Code 2017 [hidden email] > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC/UY1) "Programs must be written for people to read, and only incidentally for machines to execute."http://www.doesnotunderstand.org/

Jan. 17, 2018

Re: [Pharo-dev] [Pharo-users] [ANN] PharoLauncher v1.1 released!

by Serge Stinckwich

Thank you Christophe for this wonderful work ! On Tue, Jan 16, 2018 at 9:46 PM, Christophe Demarey < christophe.demarey(a)inria.fr> wrote: > Hi all, > > I just released *PharoLauncher 1.1*. There are now 64-bits versions for > Mac and Linux. Jenkins build is now managed through a Jenkins file. > > Here is the changelog (details on https://github.com/pharo- > project/pharo-launcher/issues): > New features: > #66 new command: import an image into the launcher default image folder > #65 new command: remove a template from "Downloaded templates" > #64 new command: create a local template from an image and remove the image > #57 new option: run an image from a login shell to inherit from shell > startup scripts to set up environment variables. > #54 It is now possible to run an image anywhere on your file system if you > click "launch" and no image is selected > #23 Pharo Launcher now has an "about" box giving its description, version > and a link to the bug tracker. > Improvements: > #62 Pharo Launcher should not load default Pharo settings > #51 Pharo Launcher now sets the current directory to the directory > containing the image (was the VM directory). Avoid confusions in Pharo 7 > images. > Bux fixes: > #60 hardReset option causes troubles to PharoLauncher > #56 #, was sent to nil > #55 Display name of Pharo 7 images unusable > #52 Cannot open a Pharo 2 image > #47 Cannot run pharo 50 pre-Spur images > > You can get platform bundles from files.pharo.org: > http://files.pharo.org/pharo-launcher/1.1/ > > Regards, > Christophe. > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC/UY1) "Programs must be written for people to read, and only incidentally for machines to execute."http://www.doesnotunderstand.org/

Jan. 17, 2018

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

by Max Leske

Hi Martin, What I do is 1. update local pharo repository on branch 'development' 2. add repository to Iceberg 3. create branch for phogbugz issue 4. make changes (e.g. load stuff from your project) 5. Note that you will have to handle addition and removal of packages separately: 5.1 addition: click 'add package' 5.2 removal: click 'remove package'. You will have to commit the removal from the command line, as Iceberg does not currently recognize removals as staged changes. I usually just make a second commit with the removal before I push everything. 6. Now the changes may not show up. But you can right click on the repository in Iceberg and select 'Synchronize full repository' 7. Select the changes you want to commit The rest you know, I guess ;) Cheers, Max On 16 January 2018 at 20:16:22, Martin Dias (tinchodias(a)gmail.com) wrote: Hi, I followed the guide and everything is good. What I don't know is how to upgrade an external project already integrated in Pharo 7 (Epicea). I have new version 8.2.6. Cheers, MartÃn. On Tue, Jan 9, 2018 at 11:01 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > EstebanLM wrote > >> Mmm. I think this is because your local clone is outdated. > >> It should be fixed with a fetchâ¦ from pharo-project, I mean :) > > That worked. Thanks. Next problem: Iceberg is showing a massive number of > changes when syncing with pharo fork on the dev branch at the same commit > as > the image. There doesn't seem to be a way to collapse the whole tree making > it impossible to find the real changes. I assume it's that known bug where > the first commit will sync the list, but not very user friendly! > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > >

Jan. 17, 2018

Re: [Pharo-dev] [ANN] PharoLauncher v1.1 released!

by Julien

Jan. 16, 2018

[ANN] PharoLauncher v1.1 released!

by Christophe Demarey

Hi all, I just released PharoLauncher 1.1. There are now 64-bits versions for Mac and Linux. Jenkins build is now managed through a Jenkins file. Here is the changelog (details on https://github.com/pharo-project/pharo-launcher/issues) New features: #66 new command: import an image into the launcher default image folder #65 new command: remove a template from "Downloaded templates" #64 new command: create a local template from an image and remove the image #57 new option: run an image from a login shell to inherit from shell startup scripts to set up environment variables. #54 It is now possible to run an image anywhere on your file system if you click "launch" and no image is selected #23 Pharo Launcher now has an "about" box giving its description, version and a link to the bug tracker. Improvements: #62 Pharo Launcher should not load default Pharo settings #51 Pharo Launcher now sets the current directory to the directory containing the image (was the VM directory). Avoid confusions in Pharo 7 images. Bux fixes: #60 hardReset option causes troubles to PharoLauncher #56 #, was sent to nil #55 Display name of Pharo 7 images unusable #52 Cannot open a Pharo 2 image #47 Cannot run pharo 50 pre-Spur images You can get platform bundles from files.pharo.org <http://files.pharo.org/>: http://files.pharo.org/pharo-launcher/1.1/ Regards, Christophe.

Jan. 16, 2018

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

by Martin Dias

Hi, I followed the guide and everything is good. What I don't know is how to upgrade an external project already integrated in Pharo 7 (Epicea). I have new version 8.2.6. Cheers, MartÃn. On Tue, Jan 9, 2018 at 11:01 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > EstebanLM wrote > >> Mmm. I think this is because your local clone is outdated. > >> It should be fixed with a fetchâ¦ from pharo-project, I mean :) > > That worked. Thanks. Next problem: Iceberg is showing a massive number of > changes when syncing with pharo fork on the dev branch at the same commit > as > the image. There doesn't seem to be a way to collapse the whole tree making > it impossible to find the real changes. I assume it's that known bug where > the first commit will sync the list, but not very user friendly! > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > >

Jan. 16, 2018

Re: [Pharo-dev] Anyone recognize this data?

by Eliot Miranda

Thanks Tobias! _,,,^..^,,,_ (phone) > On Jan 16, 2018, at 12:39 AM, Tobias Pape <Das.Linux(a)gmx.de> wrote: > > Hi Eliot, > >> On 16.01.2018, at 08:29, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >> Hi All, >> >> this data appears to have overwritten some of the object pointers in a key buffer in the VM's compaction algorithm, leading to a crash. I don't recognize it. Perhaps someone here does. That would help in tracking down where the overwrite originates. >> >> nonStandyo 5/3/2closeCamjm 11/11frameExtjm 8/31/cameraIsjm 9/9/2getFramejm 5/13/camera: jm 11/6/openCamejm 9/5/2videoTeskfr 10/1packedFrjm 8/31/declareCjm 4/29/cameraNajm 9/1/2cameraIskfr 10/1waitForCdmoc 5/2addCustodgd 8/30defaultCdgd 2/14toggleStsw 11/7/closeEdisw 9/30/sortPagesw 9/30/initialidgd 2/14saveAsCusw 8/12/invokePasw 12/11openEditsw 9/30/setLabelsw 9/29/wantsExpsw 6/5/2book: aBRAA 12/2adjustBosw 9/29/extent: sw 10/8/includeIRAA 8/8/initialisw 3/17/assureDasw 3/17/descriptsw 1/25/additionsw 1/25/type: aSar 5/23/paneForBdgd 8/31paneForBdgd 8/31makeTargkfr 3/8/tgt2ndGrRAA 3/8/paneForSdgd 8/31makeTargRAA 3/8/initialikfr 3/8/adjustTaRAA 3/8/paneForSdgd 8/31adjustTaRAA 3/8/adjustTaRAA 3/8/borderPrsd 11/13toggleBoar 8/25/paneForRdgd 8/31tgt2ndGrkfr 5/3/paneForMkfr 3/8/targetHaRAA 3/8/adjustTaRAA 3/8/defaultBdgd 3/7/defaultCdgd 3/7/paneForDdgd 8/31toggleTaRAA 2/20paneForSdgd 8/31paneForBdgd 8/31doEnablesw 5/3/2rebuildOwiz 9/21targetHaRAA 3/8/toggleTaRAA 2/20numberOnRAA 3/8/toggleTaRAA 3/8/toggleSikfr 3/8/paneForSRAA 3/8/targetRaRAA 3/8/targetBoar 11/26targetBoar 8/25/paneFor2dgd 8/31numberOngm 2/16/paneForLcmm 11/1paneForGdgd 8/31paneForCdgd 8/31paneForGdgd 8/31paneForGdgd 8/31updateBoyo 1/15/window: tak 10/2sortedPryo 1/10/intoWorlyo 1/10/wantsToBtak 10/1directoryo 1/10/onEnterWdtl 11/1sortedAlyo 1tak 10/2buildPanyo 1/10/initialiyo 1/10/buildButyo 1/15/projectFtak 10/1setupBooyo 1/22/fullPathtak 10/1openProjtak 10/2thumbnaitak 10/1showGallyo 1/10/updatePatak 10/2trackedEyo 9/22/clearEvayo 1/13/setRewriyo 1/13/includeIdi 6/22/setDefauyo 9/1/2writingUtk 1/31/generatesw 6/10/initialitfel 8/3trackedEyo 9/22/writingUtk 1/31/launchAlsw 1/30/descripttak 7/25defaultNKR 5/23/asm 4/11registerKR 8/12/allScripsw 6/12/initialiasm 4/11morphToDfbs 11/2addCustosw 4/13/acceptDrsw 6/9/2isColorCar 8/16/handlesMar 2/8/2lastTilesw 6/6/2restoreDul 12/12mouseLeasw 6/19/prin^ sw 10/3/isTilePaar 1/3/2isOutsidtk 8/3/1parseNodyo 4/12/canAccepsw 5/1/2setType:sw 9/17/prepareTdgd 2/22mouseEntsw 6/14/basicWidsw 9/17/storeCodjm 5/28/setToBeasw 10/6/wrapInFusw 6/5/2la"rls 1/25/getRepliyo 9/14/printSesasm 11/2layoutPrsw 9/14/controlAjm 2/20/cardDeckdjp yo 4/25/bePossessw 9/8/2includeIdi 5/3/1addToForls 7/4/1currentVsw 6/4/2initPinSdi 5/1/1defaultNKR 5/2"olot 11sound 3/7/coords > > This looks a lot like (overlapping) method time stamps. > > Here, I tried to disentangle them: > > Most looks like 8 byte method name and 8 byte stamp. > Some are differently broken, tho (see empty areas) > Also, the method part seems to come from source code, it includes ^ and ". > > Hope that helps. > > Best regards > -Tobias > > nonStand yo 5/3/2 > closeCam jm 11/11 > frameExt jm 8/31/ > cameraIs jm 9/9/2 > getFrame jm 5/13/ > camera: jm 11/6/ > openCame jm 9/5/2 > videoTes kfr 10/1 > packedFr jm 8/31/ > declareC jm 4/29/ > cameraNa jm 9/1/2 > cameraIs kfr 10/1 > waitForC dmoc 5/2 > addCusto dgd 8/30 > defaultC dgd 2/14 > toggleSt sw 11/7/ > closeEdi sw 9/30/ > sortPage sw 9/30/ > initiali dgd 2/14 > saveAsCu sw 8/12/ > invokePa sw 12/11 > openEdit sw 9/30/ > setLabel sw 9/29/ > wantsExp sw 6/5/2 > book: aB RAA 12/2 > adjustBo sw 9/29/ > extent: sw 10/8/ > includeI RAA 8/8/ > initiali sw 3/17/ > assureDa sw 3/17/ > descript sw 1/25/ > addition sw 1/25/ > type: aS ar 5/23/ > paneForB dgd 8/31 > paneForB dgd 8/31 > makeTarg kfr 3/8/ > tgt2ndGr RAA 3/8/ > paneForS dgd 8/31 > makeTarg RAA 3/8/ > initiali kfr 3/8/ > adjustTa RAA 3/8/ > paneForS dgd 8/31 > adjustTa RAA 3/8/ > adjustTa RAA 3/8/ > borderPr sd 11/13 > toggleBo ar 8/25/ > paneForR dgd 8/31 > tgt2ndGr kfr 5/3/ > paneForM kfr 3/8/ > targetHa RAA 3/8/ > adjustTa RAA 3/8/ > defaultB dgd 3/7/ > defaultC dgd 3/7/ > paneForD dgd 8/31 > toggleTa RAA 2/20 > paneForS dgd 8/31 > paneForB dgd 8/31 > doEnable sw 5/3/2 > rebuildO wiz 9/21 > targetHa RAA 3/8/ > toggleTa RAA 2/20 > numberOn RAA 3/8/ > toggleTa RAA 3/8/ > toggleSi kfr 3/8/ > paneForS RAA 3/8/ > targetRa RAA 3/8/ > targetBo ar 11/26 > targetBo ar 8/25/ > paneFor2 dgd 8/31 > numberOn gm 2/16/ > paneForL cmm 11/1 > paneForG dgd 8/31 > paneForC dgd 8/31 > paneForG dgd 8/31 > paneForG dgd 8/31 > updateBo yo 1/15/ > window: tak 10/2 > sortedPr yo 1/10/ > intoWorl yo 1/10/ > wantsToB tak 10/1 > director yo 1/10/ > onEnterW dtl 11/1 > sortedAl yo 1 > tak 10/2 > buildPan yo 1/10/ > initiali yo 1/10/ > buildBut yo 1/15/ > projectF tak 10/1 > setupBoo yo 1/22/ > fullPath tak 10/1 > openProj tak 10/2 > thumbnai tak 10/1 > showGall yo 1/10/ > updatePa tak 10/2 > trackedE yo 9/22/ > clearEva yo 1/13/ > setRewri yo 1/13/ > includeI di 6/22/ > setDefau yo 9/1/2 > writingU tk 1/31/ > generate sw 6/10/ > initiali tfel 8/3 > trackedE yo 9/22/ > writingU tk 1/31/ > launchAl sw 1/30/ > descript tak 7/25 > defaultN KR 5/23/ > asm 4/11 > register KR 8/12/ > allScrip sw 6/12/ > initiali asm 4/11 > morphToD fbs 11/2 > addCusto sw 4/13/ > acceptDr sw 6/9/2 > isColorC ar 8/16/ > handlesM ar 2/8/2 > lastTile sw 6/6/2 > restoreD ul 12/12 > mouseLea sw 6/19/ > prin^ sw 10/3/ > isTilePa ar 1/3/2 > isOutsid tk 8/3/1 > parseNod yo 4/12/ > canAccep sw 5/1/2 > setType: sw 9/17/ > prepareT dgd 2/22 > mouseEnt sw 6/14/ > basicWid sw 9/17/ > storeCod jm 5/28/ > setToBea sw 10/6/ > wrapInFu sw 6/5/2 > la"r ls 1/25/ > getRepli yo 9/14/ > printSes asm 11/2 > layoutPr sw 9/14/ > controlA jm 2/20/ > cardDeck djp > yo 4/25/ > bePosses sw 9/8/2 > includeI di 5/3/1 > addToFor ls 7/4/1 > currentV sw 6/4/2 > initPinS di 5/1/1 > defaultN KR 5/2 > " olot 11 > sound 3/7/ > coords > > >

Jan. 16, 2018

[Pharo 7.0-dev] Build #432: 20936-64bit-primitiveFailure-for-10-largeIdentityHash

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

There is a new Pharo build available! The status of the build #432 was: SUCCESS. The Pull Request #653 was integrated: "20936-64bit-primitiveFailure-for-10-largeIdentityHash" Pull request url: https://github.com/pharo-project/pharo/pull/653 Issue Url: https://pharo.fogbugz.com/f/cases/20936 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 16, 2018