- Pharo-dev - lists.pharo.org

Debugger hang when step throught
by Hilaire Feb. 7, 2017

Feb. 7, 2017

Hello, The faulty code bellow when debugged and 'step through' cause the debugger to hang: self inform: '1'. #(2 3 4) select: [:i| i] thenDo: [:n| self inform: n printString ]. self inform: '5'. It seems trapped in an infinite loop, you can more or less get control back with Alt+[.] When step in, the debugger properly report the error. Pharo #60362. I did not see similar bug report, shall I? -- Dr. Geo http://drgeo.eu

4 4

[pharo-project/pharo-core]
by GitHub Feb. 7, 2017

Feb. 7, 2017

Branch: refs/tags/60377 Home: https://github.com/pharo-project/pharo-core

1 0

[pharo-project/pharo-core] ab7ee8: 60377
by GitHub Feb. 7, 2017

Feb. 7, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: ab7ee87bf0bba53324987797b37402d486688cca https://github.com/pharo-project/pharo-core/commit/ab7ee87bf0bba53324987797… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-07 (Tue, 07 Feb 2017) Changed paths: M Polymorph-Widgets.package/Pharo3Theme.class/instance/fill-styles-buttons/buttonSelectedFillStyleFor_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60376.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60377.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60376.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60377.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A WriteBarrierTests.package/WriteBarrierStub.class/README.md A WriteBarrierTests.package/WriteBarrierStub.class/definition.st A WriteBarrierTests.package/WriteBarrierStub.class/instance/accessing/var1.st A WriteBarrierTests.package/WriteBarrierStub.class/instance/accessing/var10.st A WriteBarrierTests.package/WriteBarrierStub.class/instance/accessing/var10_.st A WriteBarrierTests.package/WriteBarrierStub.class/instance/accessing/var1_.st M WriteBarrierTests.package/WriteBarrierTest.class/instance/setup/expectedFailures.st A WriteBarrierTests.package/WriteBarrierTest.class/instance/tests - object/testMutateFirstInstVarOfObjectWithManyVars.st A WriteBarrierTests.package/WriteBarrierTest.class/instance/tests - object/testMutateInstVarShouldCatchRightFailure.st A WriteBarrierTests.package/WriteBarrierTest.class/instance/tests - object/testMutateLastInstVarOfObjectWithManyVars.st Log Message: ----------- 60377 19657 white theme color for button is not good https://pharo.fogbugz.com/f/cases/19657 19639 More tests for write barrier to cover that modification failure catch right parameters https://pharo.fogbugz.com/f/cases/19639 http://files.pharo.org/image/60/60377.zip

1 0

Esteban's ChangeLog week of 30 January 2017
by estebanlm＠gmail.com Feb. 7, 2017

Feb. 7, 2017

Hello! This is my weekly ChangeLog, from 30 January 2017 to 5 February 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=30/1/2017&to=5/2/2017 ChangeLog ========= 3 February 2017: ---------------- * Still on [iceberg](https://github.com/npasserini/iceberg), this time I addresed two issues: * [issue 269](https://github.com/npasserini/iceberg/issues/269), which is an improvement on the way we visualise trees (showing just those that have changes, this is very important in big repositories) * [issue 270](https://github.com/npasserini/iceberg/issues/270), which addreses a problem I left there when working on multi-remotes: it was showing incorrect data between the real outgoing commits and the ones shown in the browser. I made a couple of pull requests with them (yep, still using the plugin I developed yesterday :P) 2 February 2017: ---------------- * I spent last two days working on adapt [Iceberg](https://github.com/npasserini/iceberg) infrastructure to accept plugins. Well... not totally true. What in fact I made was to *start* to program a way to add plugins, which for now are just allowed in repositories pane on repositories browser. But well, the rudiments are there. What actually took most of my time was the development of the first plugin (you know, I do not believe too much on "developments in abstract", I need concrete cases to test my ideas): an Pull Request creator. With this, you can do from iceberg the same kind of work you do in github web page :) So, now you can have a beutiful pull request dialog, along with several validations... Now, you may wonder why I needed to develop such kind of tool (after all, you can always go to the web page and do the same). And the answer is that in the new process we are starting to create for Pharo, we need to be able to do things like: . create a fix . create a branch from pharo-core sources, named for example issue-12345 (something that would usually belong to a SLICE) . sends commits to that branch while working on the issue . send a Pull Request of the issue (what now is to commit the SLICE to inbox and changing status on the bug tracker) so, to make this process easy, we need to be able to complete the full cycle from Pharo, exactly as we do it now. Pull Requests are a necessary step to fulfill this requirement. 31 January 2017: ---------------- * Working on [iceberg](https://github.com/npasserini), I fixed a bug that happened when trying to clone a recently created repository (without branchs yet). cheers! Esteban

3 2

Pharo 60 needs help on shortcuts-are-wrongly-displayed
by Stephane Ducasse Feb. 7, 2017

Feb. 7, 2017

https://pharo.fogbugz.com/f/cases/19660/shortcuts-are-wrongly-displayed The system should display Ctrl + s and not Ctrl + S Because people are pressing Shift to get S and this is not working. We should distinguish between uppercase and lowercase. The reader cannot guess that S is not the same as s + shift. There is no way that a user can know that they should NOT press shift when looking at Ctrl + S (because there is no noshiftPressed). Ctrl + S means press Shift.

4 4

Pharo 60 need help white-theme-color-for-button-is-not-good
by Stephane Ducasse Feb. 7, 2017

Feb. 7, 2017

https://pharo.fogbugz.com/f/cases/19657/white-theme-color-for-button-is-not… If we compare the selection color for the dark theme, the blue is stronger and much better to see. This is particularly true for class/instance side button, I would be good to have a better white theme with stronger selection colors.

3 5

FileStreams and encoding ( opening a readStream on a FileRerefence)
by Nicolai Hess Feb. 7, 2017

Feb. 7, 2017

Hi How can I specify the character encoding when opening a readStream on a FileRerefence. I found this, that works: | readStream fileContent | readStream := (File named: aFileName) openForRead. fileContent := ZnCharacterReadStream on: readStream encoding: encoding. fileContent upToEnd asString. But if I try to do the same with a readStream from a FileReference | readStream fileContent | readStream := aFileName asFileReference readStream. fileContent := ZnCharacterReadStream on: readStream encoding: encoding. fileContent upToEnd asString. I get an error SmallInteger DNU #asciiValue, this is because, in the first method, we create a binary filestream, and if we use readStream from a FileReference, the stream is a MultibyteFileStream. How can I us ZnEncoder for a readstream from a FileReference? (and is it on purpose that both readStream method (openForRead/readStream) return different kinds of binary streams?) nicolai

5 13

[pharo-project/pharo-core] f197e6: 60376
by GitHub Feb. 7, 2017

Feb. 7, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: f197e65799a3ccc19b3e78e644e89e95b89e7e30 https://github.com/pharo-project/pharo-core/commit/f197e65799a3ccc19b3e78e6… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-07 (Tue, 07 Feb 2017) Changed paths: A OpalCompiler-Core.package/IRMethod.class/instance/mapping/sourceNodeExecuted.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60375.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60376.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60375.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60376.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60376 19661 When coding in the debugger I get an error sourceNodeExecuted https://pharo.fogbugz.com/f/cases/19661 http://files.pharo.org/image/60/60376.zip

1 0

[pharo-project/pharo-core]
by GitHub Feb. 7, 2017

Feb. 7, 2017

Branch: refs/tags/60376 Home: https://github.com/pharo-project/pharo-core

1 0

Segmentation fault while installing Scale
by Andrey Tykhonov Feb. 7, 2017

Feb. 7, 2017

Hi all! While executing the following command: $ wget -O- https://raw.githubusercontent.com/guillep/Scale/master/setupScale.sh | sudo bash > stderr.log I got the Segmentation fault error. You can see it in the contents of stderr.log which is attached to the email. Here you can see the output of the mentioned command: ``` --2017-02-03 19:35:16-- https://raw.githubusercontent.com/guillep/Scale/master/setupScale.sh Resolving raw.githubusercontent.com... 151.101.128.133, 151.101.192.133, 151.101.64.133, ... Connecting to raw.githubusercontent.com|151.101.128.133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 1021 [text/plain] Saving to: âSTDOUTâ - 100%[=============================================================>] 1021 --.-KB/s in 0s 2017-02-03 19:35:16 (274 MB/s) - written to stdout [1021/1021] Cloning into '/tmp/scale'... remote: Counting objects: 1457, done. remote: Total 1457 (delta 0), reused 0 (delta 0), pack-reused 1457 Receiving objects: 100% (1457/1457), 656.60 KiB | 714.00 KiB/s, done. Resolving deltas: 100% (799/799), done. Note: checking out 'f70fdb90cf66d443140b6fe84cad9848163bf32e'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> --2017-02-03 19:35:18-- http://get.pharo.org/50+vm Resolving get.pharo.org... 128.93.162.72 Connecting to get.pharo.org|128.93.162.72|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2901 (2.8K) [text/html] Saving to: âSTDOUTâ - 100%[=============================================================>] 2.83K --.-KB/s in 0.001s 2017-02-03 19:35:18 (3.56 MB/s) - written to stdout [2901/2901] Downloading the latest 50 Image: http://files.pharo.org/get-files/50/pharo.zip Downloading the latest pharoVM: http://files.pharo.org/get-files/50/pharo-linux-stable.zip Downloading PharoV50.sources: http://files.pharo.org/get-files/50/sources.zip Creating starter scripts pharo and pharo-ui Fetched -> BaselineOfScale-SantiagoBragagnolo.4 --- filetree:///tmp/scale/src [:] --- filetree:///tmp/scale/src./pharo: line 11: 19176 Aborted "$DIR"/"pharo-vm/pharo" --nodisplay "$@" Syntax Error on line 26: 'Unmatched '' in string literal. ->' ============================================================= 01: | scapeParentDirectory pharoParentDirectory scaleX scaleuiX | 02: 03: system stdout << 'Uninstalling scale' << String cr. 04: 05: system saveImageAs: #/ asFileReference / #tmp / #'uninstall.image'. 06: " The image must be stored elsewhere for deleting all the files " 07: 08: scaleX := '/usr/local/bin/scale' asFileReference. 09: scaleX exists ifTrue: [ system call: ' rm ', scaleX fullName ]. 10: system stdout << 'Uninstalling executable scale' << String cr ; flush. 11: 12: scaleuiX:='/usr/local/bin/scale-ui' asFileReference. 13: scaleuiX exists ifTrue: [ system call: ' rm ', scaleuiX fullName ]. 14: system stdout << 'Uninstalling executable scale-ui' << String cr ; flush. 15: 16: scapeParentDirectory := '/usr/local/scale' asFileReference. 17: pharoParentDirectory := '/usr/local/pharo' asFileReference. 18: 19: scapeParentDirectory exists ifTrue: [ system call: ' rm -rf ', scapeParentDirectory fullName ]. 20: system stdout << 'Removing scale folder' << String cr ; flush. 21: 22: pharoParentDirectory exists ifTrue: [ system call: ' rm -rf ', pharoParentDirectory fullName ]. 23: system stdout << 'Removing pharo folder' << String cr ; flush. 24: 25: 26: system stdout << 'Done _^_ Syntax Error on line 39: 'Unmatched '' in string literal. ->' ============================================================= 01: | scaleParentDirectory scaleFile scaleUIFile pharoParentDirectory| 02: 03: " DEPLOY " 04: system stdout << 'Deploying scale command';cr. 05: 06: scaleParentDirectory := '/usr/local/scale' asFileReference. 07: 08: scaleParentDirectory exists 09: ifTrue: [ 10: system stderr << 'There is already an installation. Please uninstall before' 11: ] ifFalse: [ 12: scaleParentDirectory ensureCreateDirectory. 13: scaleFile := scaleParentDirectory / 'scale'. 14: scaleUIFile := scaleParentDirectory / 'scale-ui'. 15: system workingDirectory / '..' / 'scale' copyTo: scaleFile. 16: system workingDirectory / '..' / 'scale-ui' copyTo: scaleUIFile. 17: system workingDirectory / '..' / #build / 'uninstall.st' copyTo: scaleParentDirectory / 'uninstall.st'. 18: system stdout << 'Deploying Pharo';cr. 19: 20: pharoParentDirectory := '/usr/local/pharo' asFileReference. 21: pharoParentDirectory ensureCreateDirectory. 22: #( 'pharo' 'pharo-vm' 'pharo-ui') 23: do: [ :file | system workingDirectory / file copyAllTo: pharoParentDirectory / file ]. 24: 25: #( 'Pharo.image' 'Pharo.changes') 26: do: [ :file | system workingDirectory / file copyAllTo: scaleParentDirectory / file ]. 27: 28: 29: system stdout << 'Giving permissions to run';cr. 30: 31: system call: 'chmod +x ', (pharoParentDirectory / 'pharo') fullName. 32: system call: 'chmod +x ', (pharoParentDirectory / 'pharo-ui') fullName. 33: system call: 'chmod +x ', (pharoParentDirectory / 'pharo-vm/pharo') fullName. 34: system call: 'chmod +x ', (scaleParentDirectory / 'uninstall.st') fullName. 35: system call: 'chmod +x ', scaleFile fullName. 36: system call: 'chmod +x ', scaleUIFile fullName. 37: system ln: scaleFile to: '/usr/local/bin/scale' asFileReference. 38: system ln: scaleUIFile to: '/usr/local/bin/scale-ui' asFileReference. 39: system stdout << 'Done _^_ ``` Could you please help me find a workaround in order to bypass this issue? Thank you in advance! -- Andriy

4 3