July 2019 - Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #588: 4152-Cleanups-in-UIManager
by ci-pharo-ci-jenkins2＠inria.fr July 31, 2019

July 31, 2019

There is a new Pharo build available! The status of the build #588 was: FAILURE. The Pull Request #4153 was integrated: "4152-Cleanups-in-UIManager" Pull request url: https://github.com/pharo-project/pharo/pull/4153 Issue Url: https://github.com/pharo-project/pharo/issues/4152 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #587: 4154-Hiedra-Merge-new-version-with-branch-coloring
by ci-pharo-ci-jenkins2＠inria.fr July 31, 2019

July 31, 2019

There is a new Pharo build available! The status of the build #587 was: FAILURE. The Pull Request #4155 was integrated: "4154-Hiedra-Merge-new-version-with-branch-coloring" Pull request url: https://github.com/pharo-project/pharo/pull/4155 Issue Url: https://github.com/pharo-project/pharo/issues/4154 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Pharo process scheduling
by Alistair Grant July 31, 2019

July 31, 2019

Hi Everyone, I'm trying to get a better grip on process scheduling in Pharo but don't understand the behaviour I'm seeing. My understanding is that the VM (which does the real work of scheduling the processes) is a pre-emptive co-operative model, meaning: - Higher priority processes are always scheduled ahead of lower priority processes. - Processes at the same priority get the CPU until something is done to explicitly stop processing, e.g.: -- terminate the process, wait on semaphore (I/O, timer, mutex, etc.), #yield the processor But given the following: | p x a index | p := 35. a := Array new: 20. index := 1. [ 1 to: 10 do: [ :i | [ a at: index put: i. index := index + 1. x := 0. 300000000 timesRepeat: [ x := x + 1 ]. a at: index put: i. index := index + 1. ] forkAt: p named: 'Proc', i asString ]. ] forkAt: p+1. a. The code above was written to be as simple as possible (it isn't going to be creating streams, have semaphores etc. called somewhere deep within). The 300000000 number was manually determined as something that will run for a few seconds on my laptop. Since the forking process is higher priority than the 10 worker processes, I expect that all 10 processes will be created before the first gets any CPU, and they will then be executed in order (since there is nothing obvious to cause a context switch), and the results to be: #(1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 8 9 9 10 10) But it appears that each process gets some time as soon as it is forked despite being a lower priority than the forking process, and then the order becomes non-deterministic: #(1 2 3 4 5 6 7 8 9 10 7 10 9 1 2 3 4 5 6 8) #(1 2 3 4 5 6 7 8 9 10 5 9 2 10 4 7 1 6 3 8) #(1 2 3 4 5 6 7 8 9 10 6 1 8 9 3 4 7 10 5 2) Changing p := 45 (so it is higher priority than the morphic UI process) doesn't have any effect. Can someone explain what I'm missing in my understanding? Thanks! Alistair

4 9

[ANN] OSWinSubprocess a library to spawn Windows System processes
by Christophe Demarey July 30, 2019

July 30, 2019

Hi, Pharo Launcher had stability problems to spawn new processes (launch Pharo images) on Windows as well as limitations (paths could only contain ASCII characters). To solve this problem, we developed a new library: OSWinSubprocess (https://github.com/pharo-contributions/OSWinSubprocess <https://github.com/pharo-contributions/OSWinSubprocess>) and decided to make it a standalone library so that people can use it if they need to. We tried to use the same API as OSSubprocess when possible. This library uses the Windows API to create process from both 32-bit and 64-bit Pharo images. It also supports Unicode characters. Here are some examples on how to use it: process := OSWSWinProcess new command: 'C:\Windows\notepad.exe'; run. ... process terminate. OSWSWinProcess new command: 'C:\Windows\notepad.exe'; arguments: #('notepad.exe' 'C:\foo.txt'); runAndWait. Important note: As of now, this library does not yet support standard streams (stdin, stdout and stderr). It could be done by setting the appropriate information in the STARTUPINFO structutre. You can check the README for more information. Regards, Christophe.

7 8

[Pharo 8.0] Build #586: Add-some-icons-to-commands
by ci-pharo-ci-jenkins2＠inria.fr July 30, 2019

July 30, 2019

There is a new Pharo build available! The status of the build #586 was: FAILURE. The Pull Request #4131 was integrated: "Add-some-icons-to-commands" Pull request url: https://github.com/pharo-project/pharo/pull/4131 Issue Url: https://github.com/pharo-project/pharo/issues/AddIconsToCommands Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #585: Separate Network-Tests-Mail into new package
by ci-pharo-ci-jenkins2＠inria.fr July 30, 2019

July 30, 2019

There is a new Pharo build available! The status of the build #585 was: SUCCESS. The Pull Request #4146 was integrated: "Separate Network-Tests-Mail into new package" Pull request url: https://github.com/pharo-project/pharo/pull/4146 Issue Url: https://github.com/pharo-project/pharo/issues/Network_Tests_Mail Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #584: Push-up-push-down-new-preview
by ci-pharo-ci-jenkins2＠inria.fr July 28, 2019

July 28, 2019

There is a new Pharo build available! The status of the build #584 was: FAILURE. The Pull Request #4132 was integrated: "Push-up-push-down-new-preview" Pull request url: https://github.com/pharo-project/pharo/pull/4132 Issue Url: https://github.com/pharo-project/pharo/issues/PushUpPushDownNewPreview Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #583: Deprecate-unused-cairo-method
by ci-pharo-ci-jenkins2＠inria.fr July 28, 2019

July 28, 2019

There is a new Pharo build available! The status of the build #583 was: SUCCESS. The Pull Request #4139 was integrated: "Deprecate-unused-cairo-method" Pull request url: https://github.com/pharo-project/pharo/pull/4139 Issue Url: https://github.com/pharo-project/pharo/issues/Deprecate Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Pharo Newsletter July 2019
by Marcus Denker July 27, 2019

July 27, 2019

The Pharo Newsletter July 2019 has been sent to subscribers one week ago. https://mailchi.mp/pharo/pharo-newsletter-july-2019 <https://mailchi.mp/pharo/pharo-newsletter-july-2019> To get it as soon as it is released, please subscribe here: http://eepurl.com/bykqWn <http://eepurl.com/bykqWn>

1 0

[Pharo 8.0] Build #582: add Dictionary>>#associationAt:ifPresent:ifAbsent:
by ci-pharo-ci-jenkins2＠inria.fr July 27, 2019

July 27, 2019

There is a new Pharo build available! The status of the build #582 was: FAILURE. The Pull Request #4122 was integrated: "add Dictionary>>#associationAt:ifPresent:ifAbsent:" Pull request url: https://github.com/pharo-project/pharo/pull/4122 Issue Url: https://github.com/pharo-project/pharo/issues/associationAtifPresentifAbsent Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0