- Pharo-dev - lists.pharo.org

OSPlatform currentVersion
by Norbert Hartl July 6, 2017

July 6, 2017

Does anyone know when the output for OSPlatform currentVersion changed? In Pharo 4 I get '1095' and in pharo6 I get '10.12.5'. The determination if it is a OSX system or older is done by currentVersion asNumber >= 1000 which changes behaviour because the currentVersion string has been changed. Is the output the one supposed to be? Norbert

2 3

Simply Happy
by Stephane Ducasse July 6, 2017

July 6, 2017

Hi pharoing people Just a little word to tell you that I'm super happy about the future of Pharo. The consortium is growing and will probably be able to pay esteban and clement. The roadmap for Pharo 70 is really exciting. The bootstrap, git and the new project in the pipe will boost us. So I wanted to thanks you all for all this super great energy. We (you and us) are building a super cool future. Stef

7 6

tar sec files for windows Pharo VM build
by Eliot Miranda July 6, 2017

July 6, 2017

Hi All, if I'm reading the build.winMNxOP/third-party/Makefile.libXXX files correctly there should be a libXXX.spec.win file for each library in build.winMNxOP/third-party. There are no such files in the Cog or master branches. Can anybody point me to these files? _,,,^..^,,,_ best, Eliot

1 1

Recommended production VM on latest macOS Sierra?
by Bernhard Pieber July 5, 2017

July 5, 2017

Hi, What VM would you recommend for a production app on macOS Sierra? - Pharo 6, right? - I assume 32-bit because 64-bit is still experimental, right? - 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? I must admit I am quite confused. Cheers, Bernhard

4 5

SmartTest
by Benoit Verhaeghe July 5, 2017

July 5, 2017

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

1 0

Pull requests reviews
by Pavel Krivanek July 5, 2017

July 5, 2017

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

3 3

P6 crashed image
by Hilaire July 5, 2017

July 5, 2017

Hi, I got problem with my Pharo6 image when I save it, after some Glamour try out, don't know if it is related. When I saved the image, it grows to 292MB then stalled, with the mouse writing pointer. Then Pharo display became garbage. I have to kill the process. The image does not start anymore, get segmentation fault with Smalltalk stack dump, Freetype seems to be involved: Segmentation fault Sun Jul 2 17:52:39 2017 /home/hilaire/Travaux/Developpement/Pharo/vm/pharo64-linux-threaded-stable/lib/pharo/5.0-201705310241/pharo Pharo VM version: 5.0-201705310241 Wed May 31 04:43:29 UTC 2017 gcc 4.6.3 [Production Spur 64-bit VM] Built from: CoInterpreter VMMaker.oscog-eem.2231 uuid: de62947a-7f40-4977-a232-e06a3a80c939 May 31 2017 With: StackToRegisterMappingCogit VMMaker.oscog-eem.2227 uuid: 7ea146b4-39ce-4de7-afa3-a76ed1d1da35 May 31 2017 Revision: VM: 201705310241 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Tue May 30 19:41:27 2017 -0700 $ Plugins: 201705310241 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Build host: Linux testing-gce-7baaea33-cad4-44b6-b0e5-7ad5f93c3335 3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 16:47:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux plugin path: /home/hilaire/Travaux/Developpement/Pharo/vm/pharo64-linux-threaded-stable/bin/../lib/pharo/5.0-201705310241 [default: /home/hilaire/Travaux/Developpement/Pharo/vm/pharo64-linux-threaded-stable/lib/pharo/5.0-201705310241/] C stack backtrace & registers: rax 0x49063940 rbx 0x490637d0 rcx 0x490639f8 rdx 0x49063888 rdi 0x490635a8 rsi 0x490635a8 rbp 0x49063718 rsp 0x49063ab0 r8 0x49062fe8 r9 0x490630a0 r10 0x49063158 r11 0x49063210 r12 0x490632c8 r13 0x49063380 r14 0x49063438 r15 0x490634f0 rip 0x49063b68 *[0x7fff49063b68] /home/hilaire/Travaux/Developpement/Pharo/vm/pharo64-linux-threaded-stable/bin/../lib/pharo/5.0-201705310241/pharo[0x41cac1] /home/hilaire/Travaux/Developpement/Pharo/vm/pharo64-linux-threaded-stable/bin/../lib/pharo/5.0-201705310241/pharo[0x41ce4f] /lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7f4e70d53330] /usr/lib/x86_64-linux-gnu/libfreetype.so.6(FT_Stream_ReadULong+0x78)[0x7f4e6cc9c168] /usr/lib/x86_64-linux-gnu/libfreetype.so.6(+0x52116)[0x7f4e6ccdb116] /usr/lib/x86_64-linux-gnu/libfreetype.so.6(+0x26742)[0x7f4e6ccaf742] /usr/lib/x86_64-linux-gnu/libfreetype.so.6(+0x152e3)[0x7f4e6cc9e2e3] /usr/lib/x86_64-linux-gnu/libfreetype.so.6(FT_Open_Face+0x2a0)[0x7f4e6cca0070] /usr/lib/x86_64-linux-gnu/libfreetype.so.6(FT_New_Memory_Face+0x39)[0x7f4e6cca0669] /home/hilaire/Travaux/Developpement/Pharo/vm/pharo64-linux-threaded-stable/bin/../lib/pharo/5.0-201705310241/FT2Plugin.so(primitiveNewMemoryFaceFromExternalMemoryAndIndex+0xea)[0x7f4e6cf309aa] /home/hilaire/Travaux/Developpement/Pharo/vm/pharo64-linux-threaded-stable/bin/../lib/pharo/5.0-201705310241/pharo[0x4572a7] /home/hilaire/Travaux/Developpement/Pharo/vm/pharo64-linux-threaded-stable/bin/../lib/pharo/5.0-201705310241/pharo(interpret+0xbd80)[0x467d80] /home/hilaire/Travaux/Developpement/Pharo/vm/pharo64-linux-threaded-stable/bin/../lib/pharo/5.0-201705310241/pharo[0x468651] /home/hilaire/Travaux/Developpement/Pharo/vm/pharo64-linux-threaded-stable/bin/../lib/pharo/5.0-201705310241/pharo(interpret+0x268)[0x45c268] /home/hilaire/Travaux/Developpement/Pharo/vm/pharo64-linux-threaded-stable/bin/../lib/pharo/5.0-201705310241/pharo(main+0x2ab)[0x419d6b] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f4e70695f45] /home/hilaire/Travaux/Developpement/Pharo/vm/pharo64-linux-threaded-stable/bin/../lib/pharo/5.0-201705310241/pharo[0x41a055] [0x7fff49061d60] Smalltalk stack dump: 0x7fff490695d8 I FreeTypeFace(FT2Face)>newFaceFromExternalMemory:index: 0x4a83478: a(n) FreeTypeFace 0x7fff49069628 I FreeTypeFace>create 0x4a83478: a(n) FreeTypeFace 0x7fff49069668 I FreeTypeFace>validate 0x4a83478: a(n) FreeTypeFace 0x7fff490696a8 I FreeTypeFont>face 0x13c41758: a(n) FreeTypeFont 0x7fff490696e8 I FreeTypeFont>validate 0x13c41758: a(n) FreeTypeFont 0x7fff49069728 I LogicalFont>realFont 0x3015870: a(n) LogicalFont 0x7fff49069768 I LogicalFont>descent 0x3015870: a(n) LogicalFont -- Dr. Geo http://drgeo.eu

3 3

[ANN] association.pharo.org now on AWS
by Marcus Denker July 5, 2017

July 5, 2017

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

1 0

[ANN] Iceberg 0.5 released
by Esteban Lorenzano July 5, 2017

July 5, 2017

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 <http://get.pharo.org/vm70> | bash wget -O- get.pharo.org/ <http://get.pharo.org/vm70>64/ <http://get.pharo.org/vm70>vmT70 <http://get.pharo.org/vm70> | bash #If you are on linux 32bits: wget -O- get.pharo.org/vm70 <http://get.pharo.org/vm70> | bash wget -O- get.pharo.org/vmT70 <http://get.pharo.org/vm70> | 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. cheers! Esteban

3 6

[ANN] for P7, default VM for linux moved to threaded
by Esteban Lorenzano July 5, 2017

July 5, 2017

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

2 2