April 2020 - Pharo-dev - lists.pharo.org

Recommendation for password encryption?
by Mariano Martinez Peck Sept. 30, 2022

Sept. 30, 2022

Hi guys. Some time ago I asked about the best way to encrypt a password. Some of the recommendations I got was: 1) Generally for passwords you do not write a decrypt method for security purposes (eg you do not want people to be able to reverse engineer the encrypted password easily) 2) put a little salt 3) There is http://www.squeaksource.com/Cryptography/PasswordHashingFFI 4) I should not decrypt password but instead I should compare both encrypted versions to see if they are equal. My scenario is the following. I need to store database passwords in text files. So I don't want to let them as plain text. And while I understand 4), I think it's a different scenario than mine. I know that some database driver may allow you to directly send the encrypted password. But still...I have another similar scenario in which I have to store a password and then send it (unencrypted)...so I kind of really need a bi-directional encryption. Now..I would try to avoid having an external library + FFI. Any ideas what is the best thing I can do? And how could I solve 1) if I want bidirectional like in my case? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

9 26

[ANN] Pharo Launcher 2.0 released!
by Christophe Demarey July 20, 2020

July 20, 2020

Hi all, Pharo Launcher 2.0 has just been released! It is available from http://pharo.org/download <http://pharo.org/download>. This new version introduces major changes: The UI has been fully rewritten using the new Spec2 framework <https://github.com/pharo-spec/Spec> and the Commander2 library <https://github.com/pharo-spec/Commander2>. UI has been revamped to increase usability, especially for newcomers. The main window is now composed of a toolbar and the list of images. The template list is now available when clicking on the new image button. Documentation web site : All Pharo Launcher features are now explained in the new documentation available at https://pharo-project.github.io/pharo-launcher. You can contribute easily by clicking the *edit on GitHub* button. You can now have many launch configurations for an image (VM to use, vm and image arguments). It means you can use headless Pharo VM from Pharo Launcher. When creating a new image, you can specify an initialisation script that will be run once at the first image launch. It is useful to load your project code in a stock Pharo image for example. See https://pharo-project.github.io/pharo-launcher/create-images/#image-initial… You can now define your own template sources in addition to official sources (see https://pharo-project.github.io/pharo-launcher/templates/#create-your-own-l…) including authenticated sources. Improved image metadata. Pharo Launcher now manages all image metadata in a single STON file (including description, Pharo version). Big thanks to all contributors, including issue reports. It is also the opportunity to thanks Damien Cassou, the original author of Pharo Launcher. Here is the changelog: Pharo Launcher v2.0 <https://github.com/pharo-project/pharo-launcher/releases/tag/2.0> The list of closed issue is too long (68) to be listed but you can browse it here: https://github.com/pharo-project/pharo-launcher/issues?q=is%3Aissue+is%3Acl… Here are some highlights: New features: Documentation web site Image initialisation script Launch configurations, headless VM support User template file in addition to the official template file Jenkins server template now support pipeline projects Support of private Jenkins server Support of authenticated HTTP server Improvements: Monitoring of image launch failures to give back the error message (if any) Newly created image is automatically selected in the image list Allow to set image description at creation time Better error management (you will have the choice to ignore them or debug them) Add a poor version column in image list Speedup (especially when image repository has a lot of images) Bug fixes: Fix use of system unzip on Windows Regards, The Pharo team.

6 8

Re: [Pharo-project] Parsing and navigating Html
by Paul DeBruicker July 16, 2020

July 16, 2020

On 12/05/2010 06:02 AM, pharo-project-request(a)lists.gforge.inria.fr wrote: > From: St?phane Ducasse<stephane.ducasse(a)inria.fr> > Subject: [Pharo-project] Parsing and navigating Html > To:"Pharo-project(a)lists.gforge.inria.fr Development" > <Pharo-project(a)lists.gforge.inria.fr> > Message-ID:<1C53DFD8-3021-4233-BC83-CE8C1EA8D103(a)inria.fr> > Content-Type: text/plain; charset=us-ascii > > Hi > > I would like extract partial information from HTML pages. > So I started to play and fix HTMLParser. > > Now does anybody know alternatives? > > Second, does anybody develop a lib to query HTML structure as with the XMLSupport package? > > Stef The Soup package on SqueakSource.com works OK.

3 4

[Pharo 9.0] Build #274: Removing classes from ChangeSorter throws DNU
by ci-pharo-ci-jenkins2＠inria.fr April 30, 2020

April 30, 2020

There is a new Pharo build available! The status of the build #274 was: FAILURE. The Pull Request #6261 was integrated: "Removing classes from ChangeSorter throws DNU" Pull request url: https://github.com/pharo-project/pharo/pull/6261 Issue Url: https://github.com/pharo-project/pharo/issues/6260 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #273: Lint cleanup #isZipArchive:
by ci-pharo-ci-jenkins2＠inria.fr April 30, 2020

April 30, 2020

There is a new Pharo build available! The status of the build #273 was: FAILURE. The Pull Request #6263 was integrated: "Lint cleanup #isZipArchive:" Pull request url: https://github.com/pharo-project/pharo/pull/6263 Issue Url: https://github.com/pharo-project/pharo/issues/6262 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #272: Cleanup InspectDebuggerDebugAction
by ci-pharo-ci-jenkins2＠inria.fr April 30, 2020

April 30, 2020

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

1 0

[Pharo 9.0] Build #271: Fix typo
by ci-pharo-ci-jenkins2＠inria.fr April 30, 2020

April 30, 2020

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

1 0

[Pharo 9.0] Build #270: SemanticAnalysis-PrimitiveErrorInvisitPragmaNode
by ci-pharo-ci-jenkins2＠inria.fr April 28, 2020

April 28, 2020

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

1 0

[Pharo 9.0] Build #269: NameAnalysis-Test-Cleanup
by ci-pharo-ci-jenkins2＠inria.fr April 28, 2020

April 28, 2020

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

1 0

[Pharo 9.0] Build #268: Revert "refactor-spanNewSessionFrom"
by ci-pharo-ci-jenkins2＠inria.fr April 28, 2020

April 28, 2020

There is a new Pharo build available! The status of the build #268 was: FAILURE. The Pull Request #6253 was integrated: "Revert "refactor-spanNewSessionFrom"" Pull request url: https://github.com/pharo-project/pharo/pull/6253 Issue Url: https://github.com/pharo-project/pharo/issues/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Fwd: [Vm-dev] why GT forked the VM and how to kill our fork
by Eliot Miranda April 28, 2020

April 28, 2020

_,,,^..^,,,_ (phone) Begin forwarded message: > From: Eliot Miranda <eliot.miranda(a)gmail.com> > Date: April 26, 2020 at 10:39:35 AM PDT > To: Open Smalltalk Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> > Subject: Re: [Vm-dev] why GT forked the VM and how to kill our fork > > ï»¿Hi Doru, > > >> On Apr 26, 2020, at 12:57 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> ï»¿ >> Hi, >> >> Currently, at feenk we have feenkcom/opensmalltalk-vm: >> https://github.com/feenkcom/opensmalltalk-vm >> >> This is a small fork of the headless branch from pharo-project/opensmalltalk-vm that appeared out of practical necessities, but that we would like to avoid having. This post briefly describes the changes in the feenkcom/opensmalltalk-vm repo and the functionality those changes provide for Glamorous Toolkit. >> >> For Glamorous Toolkit we aimed for the following functionality: >> â¢ Open the GUI natively and have native display quality (GUI opened through FFI calls) >> â¢ Have a Glamorous Toolkit app for Mac OS that works as any other apps for Mac OS >> â¢ Create end-user applications that are fully customisable (executable name, menus, etc) >> â¢ Use Github actions for doing all compilations of external libraries and the vm instead of Travis CI. >> â¢ Have Iceberg running in native windows (which requires nested FFI callbacks) >> >> There has been work on these issues in both OpenSmalltalk/opensmalltalk-vm and pharo-project/opensmalltalk-vm but they were not entirely addressed. We needed to have something reliable a few months ago, and forking and doing some quick changes made that possible. >> >> Ideally we want to be able to run Glamorous Toolkit on both OpenSmalltalk/opensmalltalk-vm and pharo-project/opensmalltalk-vm. >> >> To have native GUIs we relied on Ronie Salgadoâs work on the headless vm and started with pharo-project/opensmalltalk-vm - headless branch: >> https://github.com/pharo-project/opensmalltalk-vm/tree/headless >> That provided a solution for opening the GUI from the image through FFI calls. Currently we use Glutin (a library for OpenGL context creation, written in pure Rust) and this made it possible to run the entire Glamorous Toolkit inside a callback. >> >> On macOS when running an app, even a notarized one, the OS warns the user that the app is downloaded from the internet, and the user needs to confirm that they agree. Once the user agrees the app should automatically start. This is not currently possible with Pharo apps (for example PharoLaunched.app) and users have to again run the app manually after giving permission. Also Gatekeeper in macOS runs applications downloaded from zips in a randomized read-only DMG. We do not want this behaviour as users not copying Glamorous Toolkit to the Applications folder on macOS would then experience incorrect application behaviour. >> >> To create end-user applications we also need to fully customize the executable name (what the user sees in the Task Runner/Activity monitor), icons, native menus. Part of this work is already integrated in the pharo-project/opensmalltalk-vm - headless branch (Customizing the OS X icons, Brand the VM executable and package). >> >> Since last year Github offers Github Actions similar to Travis. We found it much easier to use than Travis for external libraries and the vm. Also we get to manage the code and the builds in the same place. This work is already integrated in the pharo-project/opensmalltalk-vm - headless branch (Build the VM under GitHub actions: https://github.com/pharo-project/opensmalltalk-vm/pull/56) >> >> The issues related to running Iceberg is a bit more technical. By moving to the headless vm we are running the entire image computation inside a callback from Glutin (https://github.com/rust-windowing/glutin/) When using Iceberg we get nested callbacks which we could not get to work using Alien. Instead we are using the ThreadedFFI Plugin and running all callback from Iceberg and Glutin using the Threaded FFI plugin (https://github.com/pharo-project/threadedFFI-Plugin) Currently we have a small fork of this plugin (feenkcom/threadedFFI-Plugin) and we also ship a custom plugin with the VM to fix a race condition due to having two copies of the callback stack (a pull request is here: https://github.com/pharo-project/threadedFFI-Plugin/pull/17) > > One detail here is that Alien provides the callback machinery used alongside ThreadedFFIPlugin. The Alien call-out machinery is an old hack used only by Newspeak, that could be eliminated in non-Newspeak builds. But AFAIA Alienâs callback machinery is *the* callback machinery everywhere for the OpenSmalltalk vm. > >> While not specific to our environment, openssl1.0 is no longer supported, and we are seeing users who are unable to run Pharo due to version conflicts, as reported in https://github.com/pharo-project/opensmalltalk-vm/issues/62. >> >> >> To sum up, a fork was the easiest way to get all this running. Now some changes are already in the pharo-project/opensmalltalk-vm - headless branch. What we are still missing are the changes that get the VM to work nicely with Mac OS and a bug fix in ThreadedFFI. >> >> We would also love it to have all these changes integrated in OpenSmalltalk/opensmalltalk-vm in the headless vm. This requires additional coordination as the required changes are somewhat deeper. > > Can it be done with pull requests? Should we try and firm a team of volunteers, eg one from feenk and one from OpenSmalltalk to try and merge in the feenk code? > > I would volunteer but I am way too busy getting the Terf system working. TFir e able, the ARMv8 JIT has been working for months but Iâve had no time to release it because of Terf and other payed work (got to pay the bills). > >> Please let us know you would prefer to coordinate. > > Any volunteers? > >> Cheers, >> Tudor, on behalf of the feenk team >> >> -- >> feenk.com >> >> "The coherence of a trip is given by the clearness of the goal." >> >> >> >> >> >> >>

2 1

[Pharo 9.0] Build #267: refactor-spanNewSessionFrom
by ci-pharo-ci-jenkins2＠inria.fr April 28, 2020

April 28, 2020

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

1 0

[Pharo 9.0] Build #266: Improve Tests OCBytecodeToASTCache
by ci-pharo-ci-jenkins2＠inria.fr April 28, 2020

April 28, 2020

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

1 0

Statement about the VM
by StÃ©phane Ducasse April 27, 2020

April 27, 2020

As promised the consortium engineering team composed of G. Polito, P. Tesone, E. Lorenzano, M. Denker, C. Demarey and S. Ducasse produced a statement about the Pharo VM. This statement was reviewed by the Pharo board and follows decisions taken during the 2019 consortium general assembly held during PharoDays. S. Ducasse on the behalf of the consortium -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

1 0

[Pharo 9.0] Build #265: 6186-System-end-up-in-a-bad-state-when-adding-a-class-in-a-trait-composition-instead-of-a-trait
by ci-pharo-ci-jenkins2＠inria.fr April 27, 2020

April 27, 2020

There is a new Pharo build available! The status of the build #265 was: FAILURE. The Pull Request #6214 was integrated: "6186-System-end-up-in-a-bad-state-when-adding-a-class-in-a-trait-composition-instead-of-a-trait" Pull request url: https://github.com/pharo-project/pharo/pull/6214 Issue Url: https://github.com/pharo-project/pharo/issues/6186 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

_ and precedence
by StÃ©phane Ducasse April 27, 2020

April 27, 2020

Hi Doig the XP for magic literals I found Symbol >> precedence "Answer the receiver's precedence, assuming it is a valid Smalltalk message selector or 0 otherwise. The numbers are 1 for unary, 2 for binary and 3 for keyword selectors." self size = 0 ifTrue: [^ 0]. (self first isLetter or: [ self first = $_ ]) ifFalse: [^ 2]. self last = $: ifTrue: [^ 3]. ^ 1 #'_foo' precedence. "1" #'_+' precedence. "1" #'+' precedence. "2" #'foo' precedence. "1" #'foo:' precedence. "3" #'_foo:' precedence. â3" And I wonder why we are concerned with _ S. -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

3 2

[Pharo 9.0] Build #264: FixBlockBytecodePrinting
by ci-pharo-ci-jenkins2＠inria.fr April 27, 2020

April 27, 2020

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

1 0

[Pharo 9.0] Build #263: 6171-Enhance-Collection-with-rollingAvegra
by ci-pharo-ci-jenkins2＠inria.fr April 27, 2020

April 27, 2020

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

1 0

why GT forked the VM and how to kill our fork
by Tudor Girba April 26, 2020

April 26, 2020

Hi, Currently, at feenk we have feenkcom/opensmalltalk-vm: https://github.com/feenkcom/opensmalltalk-vm This is a small fork of the headless branch from pharo-project/opensmalltalk-vm that appeared out of practical necessities, but that we would like to avoid having. This post briefly describes the changes in the feenkcom/opensmalltalk-vm repo and the functionality those changes provide for Glamorous Toolkit. For Glamorous Toolkit we aimed for the following functionality: â¢ Open the GUI natively and have native display quality (GUI opened through FFI calls) â¢ Have a Glamorous Toolkit app for Mac OS that works as any other apps for Mac OS â¢ Create end-user applications that are fully customisable (executable name, menus, etc) â¢ Use Github actions for doing all compilations of external libraries and the vm instead of Travis CI. â¢ Have Iceberg running in native windows (which requires nested FFI callbacks) There has been work on these issues in both OpenSmalltalk/opensmalltalk-vm and pharo-project/opensmalltalk-vm but they were not entirely addressed. We needed to have something reliable a few months ago, and forking and doing some quick changes made that possible. Ideally we want to be able to run Glamorous Toolkit on both OpenSmalltalk/opensmalltalk-vm and pharo-project/opensmalltalk-vm. To have native GUIs we relied on Ronie Salgadoâs work on the headless vm and started with pharo-project/opensmalltalk-vm - headless branch: https://github.com/pharo-project/opensmalltalk-vm/tree/headless That provided a solution for opening the GUI from the image through FFI calls. Currently we use Glutin (a library for OpenGL context creation, written in pure Rust) and this made it possible to run the entire Glamorous Toolkit inside a callback. On macOS when running an app, even a notarized one, the OS warns the user that the app is downloaded from the internet, and the user needs to confirm that they agree. Once the user agrees the app should automatically start. This is not currently possible with Pharo apps (for example PharoLaunched.app) and users have to again run the app manually after giving permission. Also Gatekeeper in macOS runs applications downloaded from zips in a randomized read-only DMG. We do not want this behaviour as users not copying Glamorous Toolkit to the Applications folder on macOS would then experience incorrect application behaviour. To create end-user applications we also need to fully customize the executable name (what the user sees in the Task Runner/Activity monitor), icons, native menus. Part of this work is already integrated in the pharo-project/opensmalltalk-vm - headless branch (Customizing the OS X icons, Brand the VM executable and package). Since last year Github offers Github Actions similar to Travis. We found it much easier to use than Travis for external libraries and the vm. Also we get to manage the code and the builds in the same place. This work is already integrated in the pharo-project/opensmalltalk-vm - headless branch (Build the VM under GitHub actions: https://github.com/pharo-project/opensmalltalk-vm/pull/56) The issues related to running Iceberg is a bit more technical. By moving to the headless vm we are running the entire image computation inside a callback from Glutin (https://github.com/rust-windowing/glutin/) When using Iceberg we get nested callbacks which we could not get to work using Alien. Instead we are using the ThreadedFFI Plugin and running all callback from Iceberg and Glutin using the Threaded FFI plugin (https://github.com/pharo-project/threadedFFI-Plugin) Currently we have a small fork of this plugin (feenkcom/threadedFFI-Plugin) and we also ship a custom plugin with the VM to fix a race condition due to having two copies of the callback stack (a pull request is here: https://github.com/pharo-project/threadedFFI-Plugin/pull/17) While not specific to our environment, openssl1.0 is no longer supported, and we are seeing users who are unable to run Pharo due to version conflicts, as reported in https://github.com/pharo-project/opensmalltalk-vm/issues/62. To sum up, a fork was the easiest way to get all this running. Now some changes are already in the pharo-project/opensmalltalk-vm - headless branch. What we are still missing are the changes that get the VM to work nicely with Mac OS and a bug fix in ThreadedFFI. We would also love it to have all these changes integrated in OpenSmalltalk/opensmalltalk-vm in the headless vm. This requires additional coordination as the required changes are somewhat deeper. Please let us know you would prefer to coordinate. Cheers, Tudor, on behalf of the feenk team -- feenk.com "The coherence of a trip is given by the clearness of the goal."

2 1

[Pharo 9.0] Build #262: simplify-ifNil-conditions
by ci-pharo-ci-jenkins2＠inria.fr April 25, 2020

April 25, 2020

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

1 0

[Pharo 9.0] Build #261: 5494-Rename-rules-to-end-up-with-Rule
by ci-pharo-ci-jenkins2＠inria.fr April 25, 2020

April 25, 2020

There is a new Pharo build available! The status of the build #261 was: SUCCESS. The Pull Request #6228 was integrated: "5494-Rename-rules-to-end-up-with-Rule" Pull request url: https://github.com/pharo-project/pharo/pull/6228 Issue Url: https://github.com/pharo-project/pharo/issues/5494 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #260: ifErrorDo: should be onErrorDo: and deprecate with transform
by ci-pharo-ci-jenkins2＠inria.fr April 25, 2020

April 25, 2020

There is a new Pharo build available! The status of the build #260 was: FAILURE. The Pull Request #6158 was integrated: "ifErrorDo: should be onErrorDo: and deprecate with transform" Pull request url: https://github.com/pharo-project/pharo/pull/6158 Issue Url: https://github.com/pharo-project/pharo/issues/6157 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #259: #5952-PharoEnvironmentHelp-outdated
by ci-pharo-ci-jenkins2＠inria.fr April 24, 2020

April 24, 2020

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

1 0

[Pharo 9.0] Build #258: 6165-Spotter-stopped-to-react-on-full-method-name
by ci-pharo-ci-jenkins2＠inria.fr April 24, 2020

April 24, 2020

There is a new Pharo build available! The status of the build #258 was: FAILURE. The Pull Request #6226 was integrated: "6165-Spotter-stopped-to-react-on-full-method-name" Pull request url: https://github.com/pharo-project/pharo/pull/6226 Issue Url: https://github.com/pharo-project/pharo/issues/6165 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #257: ReBasicTreeRule-Cleanup
by ci-pharo-ci-jenkins2＠inria.fr April 24, 2020

April 24, 2020

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

1 0