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

[Pharo 8.0] Build #800: 4734-Add a rule to warn when referencing Smalltalk

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #800 was: FAILURE. The Pull Request #4761 was integrated: "4734-Add a rule to warn when referencing Smalltalk" Pull request url: https://github.com/pharo-project/pharo/pull/4761 Issue Url: https://github.com/pharo-project/pharo/issues/4734 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 29, 2019

Re: [Pharo-dev] Cannot extract stable VM on Window

by Cyril Ferlicot D.

Le 29/09/2019 Ã 16:35, Brainstorms a Ã©critÂ : > Hi Cyril, > > I downloaded it and tried it on Win7 Pro 64bit (running in Virtualbox), and > was able to open as expected. > > However, looking in the zip file itself, I noticed about two dozen > "*_Zone.Identifier" files that I was not expecting to see. They likely > should not be there; they have something to do with IT security inspections > on downloaded files, and I delete them as a matter of course whenever I see > them (as part of a download). I'm not sure why the Pharo build process > would have these. > > I tried launching Pharo from this zip file before and after I removed these > files... It worked in both cases; no corruption reported. However, since > your error dialog was reporting one of these 'zone' files, I would trying > removing them and see if that helps. > Thanks! With your comment I succeeded to launch my image. What I needed to do was to open the zip file without extracting it, delete all the .Identifier files and extract it once done. I wonder how the vm zip files end up with those files in them. > -Ted > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > -- Cyril Ferlicot https://ferlicot.fr

Sept. 29, 2019

Re: [Pharo-dev] Cannot extract stable VM on Window

by Cyril Ferlicot D.

Le 29/09/2019 Ã 18:32, Christopher Fuhrman a Ã©critÂ : > I reported an intermittent problem with pharo-launcher transferring > images that are detected as corrupted on my Windows 10. What happens > when you retry?Â > > See https://github.com/pharo-project/pharo-launcher/issues/359 > I already saw this issue but retrying was not working. I can reproduce it. -- Cyril Ferlicot https://ferlicot.fr

Sept. 29, 2019

Re: [Pharo-dev] Cannot extract stable VM on Window

by Christopher Fuhrman

I reported an intermittent problem with pharo-launcher transferring images that are detected as corrupted on my Windows 10. What happens when you retry? See https://github.com/pharo-project/pharo-launcher/issues/359 On Sun, Sep 29, 2019, 11:03 Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > Hi, > > Today I tried to extract the stable windows VM for Pharo 8 64bits on > Windows 7 but I get an error saying the file is corrupted. > > Link: http://files.pharo.org/vm/pharo-spur64/win/stable-20190916.zip > > Can someone reproduce it? > -- > Cyril Ferlicot > https://ferlicot.fr >

Sept. 29, 2019

Re: [Pharo-dev] Cannot extract stable VM on Window

by Brainstorms

Hi Cyril, I downloaded it and tried it on Win7 Pro 64bit (running in Virtualbox), and was able to open as expected. However, looking in the zip file itself, I noticed about two dozen "*_Zone.Identifier" files that I was not expecting to see. They likely should not be there; they have something to do with IT security inspections on downloaded files, and I delete them as a matter of course whenever I see them (as part of a download). I'm not sure why the Pharo build process would have these. I tried launching Pharo from this zip file before and after I removed these files... It worked in both cases; no corruption reported. However, since your error dialog was reporting one of these 'zone' files, I would trying removing them and see if that helps. -Ted -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 29, 2019

Re: [Pharo-dev] Cannot extract stable VM on Window

by Cyril Ferlicot D.

Le 29/09/2019 Ã 15:53, Cyril Ferlicot D. a Ã©critÂ : > Hi, > > Today I tried to extract the stable windows VM for Pharo 8 64bits on > Windows 7 but I get an error saying the file is corrupted. > > Link: http://files.pharo.org/vm/pharo-spur64/win/stable-20190916.zip > > Can someone reproduce it? > Also, I tried to take the latest VM but when I launch an image, no UI is opening. (And I took the pharo64-win-latest, not the pharo64-win-headless-latest) -- Cyril Ferlicot https://ferlicot.fr

Sept. 29, 2019

Cannot extract stable VM on Window

by Cyril Ferlicot D.

Hi, Today I tried to extract the stable windows VM for Pharo 8 64bits on Windows 7 but I get an error saying the file is corrupted. Link: http://files.pharo.org/vm/pharo-spur64/win/stable-20190916.zip Can someone reproduce it? -- Cyril Ferlicot https://ferlicot.fr

Sept. 29, 2019

[Pharo 8.0] Build #799: 4765-Add-executable-comments-to-truncateTo

by ci-pharo-ci-jenkins2＠inria.fr

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

Sept. 29, 2019

Re: [Pharo-dev] Pumping FFI documentation

by Brainstorms

Hi Guillermo, I forked the uFFI booklet repo, branched your "version2", and revised & expanded the introduction section of the first chapter... I decided that before I got too far, I should submit a pull request for just that much and get some feedback in case I need trajectory tuning. Your prose is easy to edit. :^) And it looks like my submission promptly broke Travis... Oops. -Ted Guillermo Polito wrote > Hi Ted, > > I split this in a separate thread to avoid noise :) > >> El 23 sept 2019, a las 23:14, Brainstorms < > wild.ideas@ > > escribiÃ³: >> >> Guillermo, >> >> I'm interested in helping, but at this point, I think I'd be most helpful >> working at improving documentation (mainly editing) rather than working >> on >> Pharo code itself. (I'd like to work toward that, though.) > > Iâve been doing a pass on the structure, and I was thinking on a rough > structure as follows: > 1) Intro to FFI (callouts, function and library lookup, intro to value > marshalling) > 2) Marshalling (sending arguments, literal arguments, more on > marshalling, basic C types: ints, floats, pointers and how they are > transformed to pharo objects and vice-versaâ¦) > 3) Complex types: strings, unions, arrays, opaque types > 4) Derived types on the Pharo side: How to design nice classes with all > this > 5) Callbacks > 6) Memory management > > I did already a pass on 1), and I got blocked in 2), though I want to > release a version of it this week. > > If youâre up for it, there are several things we can do: > - review the english :) > - give feedback on what is missing, what is not understandable, what can > be explained better > - testing the examples? > >> >> I'm still a newbie with Pharo, but I am a good writer/editor. And I >> expect >> that working with Pharo documentation would be another means of >> increasing >> my knowledge of the Pharo ecosystem -- so that's additional incentive for >> me. > > Cool :) > >> I gather that the PDF books are written using Pillar, which I know >> nothing >> about. Are there resources & guides for this tool/format that would help >> me >> learn how to make & edit these kinds of documents? > > Pillar is a markup syntax (from Pierâs CMS, if you know it). > https://github.com/pillar-markup/pillar > <https://github.com/pillar-markup/pillar> > > Pillar comes with a document model, parser and generators to html, pdf > (through latex), and othersâ¦ > In Pillarâs readme there are the installation instructions + usage. > > If you check the travis file in the ffi booklet repository > > https://github.com/SquareBracketAssociates/Booklet-uFFI/blob/version2/.trav… > <https://github.com/SquareBracketAssociates/Booklet-uFFI/blob/version2/.travis.yml> > > Youâll see it is built with pillar 7.4.1. In other words > > # install pillar > $ git clone https://github.com/pillar-markup/pillar.git -b v7.4.1 > $ cd pillar && ./scripts/build.sh && cd .. > > # go into the booklet repository and build the pdf > $ ./pillar/build/pillar build pdf > > Although youâll need a mostly up-to-date latex version (latexmk required, > plus several other packages, check Pillarâs readme) > >> Also, I've never contributed to an open source project; Pharo seems to be >> a >> good place to start doing so. I see that most of the documentation, web >> pages, booklets, etc. are in English so there's the advantage that >> English >> is my first language (and I actually paid attention in school :^). I'm >> also aware, from experience, that Documentation is rarely the first >> choice >> for developers to apply their time & enthusiasmâ¦ > > And itâs super important nevertheless ^^. > > Guille -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 29, 2019

Re: [Pharo-dev] ZincHTTPComponents SSO breaks ZnBufferedReadWriteStream

by Alistair Grant

Just for reference, some of the PRs associated with the issue: - https://github.com/pharo-project/pharo/pull/4726 - https://github.com/pharo-project/pharo/pull/4739 - https://github.com/pharo-project/pharo/pull/4752 On Sat, 28 Sep 2019 at 09:45, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Sven, > > Executing: > > Metacello new > baseline: 'ZincHTTPComponents'; > repository: 'github://svenvc/zinc/repository'; > load: #(SSO) > > In recent Pharo 8 images breaks ZnBufferedReadWriteStream by > redefining the class to remove many of the instance variables. > > I guess this is due to changes to ZnBufferedReadWriteStream made in > the last few days, but the result is that the image is unusable (all > access to the changes file cause exceptions). > > Where should an issue be raised? > > Thanks, > Alistair > > Pharo8.0.0 > Build information: > Pharo-8.0.0+build.798.sha.ae566532ed60b60d669aff37d4d38b86241a7c9e (64 > Bit) > Ubuntu 16.04

Sept. 28, 2019