- Pharo-dev - lists.pharo.org

[Mm10s] 2020-01-27
by tesonep＠gmail.com Jan. 27, 2020

Jan. 27, 2020

### Last week: - [Diffussion] Preparing Material for FOSDEM - [Doc] Adding type Table to uFFI booklet - [Pharo9] Running Bootstrap and tests in 64 bits - [Spotter] Add a setting to limit the number of results in Spotter - [Doc] Techtalk Iceberg - [VM] Documenting GC, participating in the GC code dojo. - [Large Images] Making Battle Plan with Esteban - [Large Images] 5562-Executing-All-Instances-in-the-startup-affects-loading-times - [Callbacks] Helping Schmidt to use TFFI Callbacks - [Callbacks] Detection of a deadlock when calling callbacks from a different thread while the VM is running. - [Pharo9] Fixing #5571 - Color settings should have default values ### This week (starting 2020-01-27): - [VM] Fixing Tests in Idle - [VM] Documenting GC, participating in the GC code dojo. - [VM] SDL Plugin for Idle - [VM] Improving Speed of TFFI - [VM] REPL example (?) - [VM] Writing tests for JIT generation - [Diffusion] FOSDEM preparation: material, trip organization, presentations - [Callbacks] Fixing Deadlock when a callback is executed from a different thread. - [Doc] Pass on VM booklet: Callback chapter / Preface - [LargeImages] Working on improving the speed and responsiveness of large images. -- Pablo Tesone. tesonep(a)gmail.com

1 0

Wrong behavior of receiveDataInto:fromHost:port:
by HilaireFernandes Jan. 26, 2020

Jan. 26, 2020

Hello, I would like to discuss one point regarding this method. In my opinion its parameter hostAddress is expected to be a SocketAdress, but the method interprets it as a ByteArray. So in the code bellow, the returned result is 0, although the host responds a datagram: server := NetNameResolver addressForName: 'localhost'. socket := Socket newUDP. socket sendUDPData: packet toHost: server port: 30000. socket waitForData. packet := ByteArray new: 200. result := socket receiveDataInto: packet fromHost: server port: 30000. The method receiveUDPData:toHost:port: should be amended as follow to make it symmetric with sendUDPData... : [ | datagram | datagram := self receiveUDPDataInto: aStringOrByteArray. ((datagram at: 2) *asSocketAddress* = hostAddress and: [ (datagram at: 3) = portNumber ]) ifTrue: [ ^ datagram at: 1 ] ifFalse: [ ^0 ] ] repeat What do you think? ----- http://drgeo.eu -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

4 10

[Pharo 9.0] Build #27: SUCCESS
by ci-pharo-ci-jenkins2＠inria.fr Jan. 25, 2020

Jan. 25, 2020

There is a new Pharo build available! The status of the build #27 was: SUCCESS. Could not extract further issue information from commit message: Merge branch 'Pharo9.0' of github.com:pharo-project/pharo into Pharo9.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #26: 5573-SpDropListPresenterselectedIndex-
by ci-pharo-ci-jenkins2＠inria.fr Jan. 25, 2020

Jan. 25, 2020

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

1 0

pharo9.x?
by ducasse Jan. 25, 2020

Jan. 25, 2020

Hi I would like to adapt some baselines to Pharo90 and Iâm wondering if we should not add pharo9.x to a list somewhere. S.

2 2

URGENT: Pharo 8 Needs Stable Version Update
by Sean P. DeNigris Jan. 25, 2020

Jan. 25, 2020

How do we update https://files.pharo.org/image/80/stable-64.zip? The "emergency evaluator on warning" issue [1] is fixed, but Launcher is still serving a pre-fix image under "Official distributions". This seems like a critical issue as new users may be immediately put off. FYI as a workaround select the latest snapshot from the "Pharo 8.0" build templates further down in the tree. 1. https://github.com/pharo-project/pharo/issues/5545 ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

3 5

[Pharo 9.0] Build #25: Renraku Rules Profiles for Beginners - fixes: #5536
by ci-pharo-ci-jenkins2＠inria.fr Jan. 24, 2020

Jan. 24, 2020

There is a new Pharo build available! The status of the build #25 was: SUCCESS. The Pull Request #5537 was integrated: "Renraku Rules Profiles for Beginners - fixes: #5536" Pull request url: https://github.com/pharo-project/pharo/pull/5537 Issue Url: https://github.com/pharo-project/pharo/issues/CreateRenrakuRulesProfiles Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #24: 5562-Executing-All-Instances-in-the-startup-affects-loading-times
by ci-pharo-ci-jenkins2＠inria.fr Jan. 24, 2020

Jan. 24, 2020

There is a new Pharo build available! The status of the build #24 was: SUCCESS. The Pull Request #5569 was integrated: "5562-Executing-All-Instances-in-the-startup-affects-loading-times" Pull request url: https://github.com/pharo-project/pharo/pull/5569 Issue Url: https://github.com/pharo-project/pharo/issues/5562 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #23: 5571-testDefaultImageDoesNotStoreAnySetting-failing-in-Pharo9-on-CI-all-plattforms
by ci-pharo-ci-jenkins2＠inria.fr Jan. 24, 2020

Jan. 24, 2020

There is a new Pharo build available! The status of the build #23 was: SUCCESS. The Pull Request #5572 was integrated: "5571-testDefaultImageDoesNotStoreAnySetting-failing-in-Pharo9-on-CI-all-plattforms" Pull request url: https://github.com/pharo-project/pharo/pull/5572 Issue Url: https://github.com/pharo-project/pharo/issues/5571 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] Short Survey about automatic deprecation rewrites
by ducasse Jan. 24, 2020

Jan. 24, 2020

Thanks! Martin milton juraj should do it too :) S. > On 21 Jan 2020, at 21:34, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > > From: Alexandre Bergel <alexandre.bergel(a)me.com> > Subject: Re: [Pharo-dev] Short Survey about automatic deprecation rewrites > Date: 21 January 2020 at 21:34:58 CET > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Cc: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > Just answered! > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On 21-01-2020, at 13:23, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> >> Hi all, >> >> We would like to share with you a short survey about the automatic deprecation rewrites that have been around since Pharo 6. >> It will be super useful for us to enhance the support for migrations. >> We estimate it will take ~< 3 minutes to fill. >> >> This survey is aimed at people both *using* Pharo, or writing libraries and frameworks for Pharo. >> If youâre a library/framework maintainer and you know people using your library, would you mind share it with them? >> >> Link to the survey: https://sondages.inria.fr/index.php/133442?lang=en >> >> Thanks a lot! >> Guille, in behalf of the Pharo consortium > > > >

3 2