- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #108: 2363 Add ProperManifestCategorizationTest as new release test
by ci-pharo-ci-jenkins2＠inria.fr March 1, 2019

March 1, 2019

There is a new Pharo build available! The status of the build #108 was: SUCCESS. The Pull Request #2364 was integrated: "2363 Add ProperManifestCategorizationTest as new release test" Pull request url: https://github.com/pharo-project/pharo/pull/2364 Issue Url: https://pharo.fogbugz.com/f/cases/2363 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Running Pharo under Ubuntu (Windows Subsystem for Linux)
by Christopher Fuhrman Feb. 28, 2019

Feb. 28, 2019

Thanks to Cyril who told me it was possible, I got Pharo 7 Unix running under the Ubuntu 18 that's part of Windows Subsystem for Linux (WSL) in Windows 10. It's not a VM VirtualBox. I documented the install steps on my new blog that uses Jekyll and github pages, which actually took longer to set up than the Pharo under WSL :) The Mesa install step on the blog might be useful for documenting how to get Pharo 7 to work in Ubuntu 18? https://fuhrmanator.github.io/Pharo-in-WSL/

3 3

Trying to load a stateful trait in a stateless version. in bootstrap when loading newSpec?
by ducasse Feb. 27, 2019

Feb. 27, 2019

2 2

AWS SDK for Pharo
by Stefan Krecher Feb. 27, 2019

Feb. 27, 2019

Hi, I'm aware that there is already an AWS SDK implementation for Smalltalk ( https://github.com/newapplesho/aws-sdk-smalltalk ) This implementation doesn't seem to be a complete implementation to access all AWS services. Using a live-programming environment like Pharo would be so cool, flexible, productive and intuitive to control/ manage AWS resources - but implementing the SDK by hand is probably not a good idea, since it would be so hard to keep it up-to-date, because AWS adds new features weekly ... I contacted the AWS enterprise support and they gave me some great hints. There are many 3rd party SDK's available that utilizes the json files provided in botocore to automatically generate SDKs: Botocore: https://github.com/boto/botocore <https://github.com/boto/botocore>Example service.json: <https://github.com/boto/botocore> https://github.com/boto/botocore/blob/develop/botocore/data/ecs/2014-11-13/… They can then automatically generate an SDK based off of these json definitions. One example of this is Rusoto, the AWS SDK for Rust: Rusoto: https://github.com/rusoto/rusoto Automatic generation portion: https://github.com/rusoto/rusoto/tree/master/service_crategen Would anyone interested in supporting this kind of project? What would be a good starting-point? Although I am (to be honest: I was) a Smalltalk-Programmer, I have too little experience with Pharo - but maybe others might find this useful. It would also be useful to "spread the word" - AWS scripting/ automation is so popular, there would be so many occasions to showcase Pharo + AWS or to create Products that are based on AWS services. Regards Stefan

5 6

Startup Metacello Error
by Sean P. DeNigris Feb. 26, 2019

Feb. 26, 2019

While loading a project from a class-side #startUp: method, I'm getting a DNU #ifTrue:ifFalse which seemed to come from somewhere deep inside Metacello [1]. On the Metacello ML, Dale suggested that the startup mechanism might be the cause: > MetacelloSkipDirtyPackageLoad is a subclass of Notification, so if some > piece of code is catching Notification or above and doing a simple resume, > then you've found your culprit ... sounds like something startup code > might do when the system isn't able to handle GUI interaction ... but it's > a pretty harsh solution ... This same code was not throwing an error on P6.1. Has something changed re startup in P7 that could account for this error? Thanks! [1] The top of the call chain is: DoItIn: arg1 ^ (MetacelloSkipDirtyPackageLoad signal: self) ifTrue: [ | tmp2 | tmp2 := Transcript. tmp2 cr; show: 'Skipping load of modified package: ' , self file. arg1 home return: self ] ifFalse: [ | tmp4 | tmp4 := Transcript. tmp4 cr; ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

1 1

Apparently Zodiac plugin can crash VM on Linux
by Max Leske Feb. 26, 2019

Feb. 26, 2019

Hi, I'm writing on behalf of Martin (eMBee) who's experiencing crashes when using SSL. You can find a VM crash stack trace here: http://ws.stfx.eu/AKVNLUPMPGLG. He says he hasn't updated openssl since December 15th but that the crashes started to happen only recently (within the last couple of days). I asked him to try HTTP only connections and those work. The VM crashes immediately when using SSL. To me it looks like the cuplrit is the Zodiac plugin, or at least the library it works with. His system: linux, fedora 29, and from the system reporter i get: Pharo/vms/70-x64/lib/pharo/5.0-201806281256/pharo CoInterpreter VMMaker.oscog-eem.2401 uuid: 29232e0e-c9e3-41d8-ae75-519db862e02c Jun 28 2018 StackToRegisterMappingCogit VMMaker.oscog-eem.2401 uuid: 29232e0e-c9e3-41d8-ae75-519db862e02c Jun 28 2018 VM: 201806281256 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Thu Jun 28 14:56:30 2018 CommitHash: a8a1dc1 Plugins: 201806281256 https://github.com/OpenSmalltalk/opensmalltalk-vm.git cheers, Max

2 4

[Pharo 8.0] Build #107: 2725-When-doing-a-FileOut-propose-to-open-the-folder-containing-the-fileout
by ci-pharo-ci-jenkins2＠inria.fr Feb. 25, 2019

Feb. 25, 2019

There is a new Pharo build available! The status of the build #107 was: FAILURE. The Pull Request #2726 was integrated: "2725-When-doing-a-FileOut-propose-to-open-the-folder-containing-the-fileout" Pull request url: https://github.com/pharo-project/pharo/pull/2726 Issue Url: https://pharo.fogbugz.com/f/cases/2725 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #106: 2718-Rubric-should-not-depend-on-TextEditor
by ci-pharo-ci-jenkins2＠inria.fr Feb. 25, 2019

Feb. 25, 2019

There is a new Pharo build available! The status of the build #106 was: SUCCESS. The Pull Request #2719 was integrated: "2718-Rubric-should-not-depend-on-TextEditor" Pull request url: https://github.com/pharo-project/pharo/pull/2719 Issue Url: https://pharo.fogbugz.com/f/cases/2718 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #149: 2699 - backport pharo-vcs/tonel bug fix
by ci-pharo-ci-jenkins2＠inria.fr Feb. 25, 2019

Feb. 25, 2019

There is a new Pharo build available! The status of the build #149 was: SUCCESS. The Pull Request #2700 was integrated: "2699 - backport pharo-vcs/tonel bug fix" Pull request url: https://github.com/pharo-project/pharo/pull/2700 Issue Url: https://pharo.fogbugz.com/f/cases/Pharo7.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Esteban's ChangeLog week of 18 February 2019
by estebanlm＠gmail.com Feb. 25, 2019

Feb. 25, 2019

Hello! This is my weekly ChangeLog, from 18 February 2019 to 24 February 2019. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=18/2/2019&to=24/2/2019 ChangeLog ========= 19 February 2019: ----------------- * Small-fix-a-day: [critiques icons are not managed correctly](https://github.com/pharo-project/pharo/pull/2655) cheers! Esteban

1 0