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

Re: [Pharo-dev] iceberg PrimitiveFailed allocateExecutablePage
by Alistair Grant Sept. 23, 2018

Sept. 23, 2018

Hi Petr, On Sun, 23 Sep 2018 at 19:52, Petr Fischer via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > Hello, I want to propose some small fixes to Pharo, it took me hours just to run Pharo with Iceberg on CentOS 7 (I don't care about Ubuntu)... > > Now I am stuck with this Iceberg error: > https://app.box.com/file/321243070589 I was presented with a login box when I tried to view this. > I am using 64bit Pharo VM + latest Pharo7 image from zeroconf (and latest CentOS7) - is Iceberg OK on 64bits? Yes, I use it all the time (on Ubuntu 16.04 64 bit). Cheers, Alistair

2 1

iceberg PrimitiveFailed allocateExecutablePage
by Petr Fischer Sept. 23, 2018

Sept. 23, 2018

Hello, I want to propose some small fixes to Pharo, it took me hours just to run Pharo with Iceberg on CentOS 7 (I don't care about Ubuntu)... Now I am stuck with this Iceberg error: https://app.box.com/file/321243070589 I am using 64bit Pharo VM + latest Pharo7 image from zeroconf (and latest CentOS7) - is Iceberg OK on 64bits? Thanks! pf

1 0

update linux info page again, please [CentOS/RHEL]
by Petr Fischer Sept. 23, 2018

Sept. 23, 2018

Hello, please, edit CentOS7 installation page: https://pharo.org/gnu-linux-installation-64 and add workaround for CentOS7 section, wihout this symlink, iceberg is broken: (do as root) cd /usr/lib64 ln -s libcurl.so.4 libcurl-gnutls.so.4 Best solution is to put this in the RPM post installation step (I mean RPM from official Pharo CentOS repository) - but we will wait for this fix for months, maybe years, so, workaround info on that page is necessary and easy to manage. More details here: http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2018-July/272624… Thanks! pf

1 0

Float should not implement #to:, #to:by:, etc...
by Julien Sept. 23, 2018

Sept. 23, 2018

Hello, I realised that it is possible to create an interval of floats. I think this is bad because, since intervals are computed by successively adding a number, it might result in precision errors. (0.0 to: 1.0 by: 0.1) asArray >>> #(0.0 0.1 0.2 0.30000000000000004 0.4 0.5 0.6000000000000001 0.7000000000000001 0.8 0.9 1.0) The correct (precise) way to do it would be to use ScaledDecimal: (0.0s1 to: 1.0s1 by: 0.1s1) asArray >>> #(0.0s1 0.1s1 0.2s1 0.3s1 0.4s1 0.5s1 0.6s1 0.7s1 0.8s1 0.9s1 1.0s1) I opened an issue about it: https://pharo.fogbugz.com/f/cases/22467/Float-should-not-implement-to-to-by… <https://pharo.fogbugz.com/f/cases/22467/Float-should-not-implement-to-to-by…> And Iâd like to discuss this with you. What do you think? Cheers, Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40

7 11

[Pharo 7.0-dev] Build #1261: Bug fix for bindings to inherited pool dictionaries (issue 22470)
by ci-pharo-ci-jenkins2＠inria.fr Sept. 22, 2018

Sept. 22, 2018

There is a new Pharo build available! The status of the build #1261 was: FAILURE. The Pull Request #1816 was integrated: "Bug fix for bindings to inherited pool dictionaries (issue 22470)" Pull request url: https://github.com/pharo-project/pharo/pull/1816 Issue Url: https://pharo.fogbugz.com/f/cases/22470 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1260: 22432 New Release test: NoUnusedTemporaryVariablesLeftTest
by ci-pharo-ci-jenkins2＠inria.fr Sept. 21, 2018

Sept. 21, 2018

There is a new Pharo build available! The status of the build #1260 was: FAILURE. The Pull Request #1782 was integrated: "22432 New Release test: NoUnusedTemporaryVariablesLeftTest" Pull request url: https://github.com/pharo-project/pharo/pull/1782 Issue Url: https://pharo.fogbugz.com/f/cases/22432 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Mailing list Archive - Bandwidth Limit Exceeded
by Torsten Bergmann Sept. 21, 2018

Sept. 21, 2018

Hi Marcus, I receive a "Bandwidth Limit Exceeded - The server is temporarily unable to service your request due to the site owner reaching his/her bandwidth limit. Please try again later." message on http://lists.pharo.org If I remember correctly we already had this one or two years ago. Thanks T.

2 2

Deprecation guide for methods, classes and packages
by Torsten Bergmann Sept. 21, 2018

Sept. 21, 2018

Hi, >From Bug #20900/ PR 1818 it looked like it is not really clear on how to "deprecate" correctly. Therefore I summarized and wrote a short guide following what we contributors used as best practice so far. Also read [1], [2] and [3] and check some of the deprecation settings in the Pharo settings browser. Just open SettingsBrowser and search for "Depre". I write this mail to "pharo-dev" with CC: "pharo-users" list - because of common interest. But comments and replies should please go to "pharo-dev" so we do not disrupt the thread too much. Thanks! Please review what I wrote and ideally we can put the text or a link to it as "Deprecation guide" into the documentation / wiki / ... on GitHub afterwards. Hope this helps a little bit. Thanks T. [1] https://en.wikipedia.org/wiki/Deprecation [2] https://www.peteruhnak.com/blog/2015/08/06/transforming-deprecated-code-wit… [3] https://pharoweekly.wordpress.com/2016/06/17/automatic-deprecation-refactor… ------------------------------------------------------------------------------------------------------------------------------ In any Pharo version we have a special package hosting deprecated methods and classes. This allows smooth migration for Pharo users as code should still load and runs to some extent - but deprecation warnings and possibly a helping hand (in form of automatic code transformations) could be given to support migration. As we currently work on Pharo7 there is a "Deprecated70" package in the image hosting deprecated methods and classes intended to be removed for Pharo 8. When Pharo 7 is released the users can easily spot the deprecations - also because they are striked through (more on this below). When Pharo 8 iteration starts the "Deprecated70" will be replaced with an empty "Deprecated80" package. DEPRECATING METHODS =================== If you deprecate a METHOD use #deprecated: message and switch it to be an extension method in *Deprecated70*. If the method could be replaced by calling another method then dispatch the call to the new method and ideally provide a transformation so next time the old method is called the sender method is automagically rewritten and could be adopted/migrated: oldMethod "An old method we do not use anymore. But luckily there is a replacement." self deprecated: 'Please use #newMethod instead' transformWith: '`@receiver oldMethod' -> '`@receiver newMethod'. ^ self newMethod So if there is a method like foo self oldMethod sending the old deprecated method it will be migrated to foo self newMethod as soon as foo, the oldMethod and the transformation is called. If the automatically migrated method is under version control (Monticello or git) you will easily see that #foo was modified. In case there is no replacement for a method you would like to deprecate then it is best to throw an error when it is used: veryOldMethod "A very old method hopefully nobody uses. So we do no provide a replacement." self deprecated: 'The method #veryOldMethod is deprecated without any replacement'. ^ self error: 'Do not use #veryOldMethod anymore' Note that the method is striked through in the Pharo system browser in both cases to show that it should not be used anymore. In the standard image calling a deprecated method is logged on the Transcript and flagged with a warning dialog. This should help users and maintainers of external packages to easily spot when they still use deprecated code. You can change these settings in Pharo Settings Browser under Tools -> Debugging -> Deprecation Handling. DEPRECATING CLASSES =================== If you deprecate a CLASS implement #isDeprecated on class side to return true and move it to package "Deprecated70" Ideally write in the class comment why it is deprecated and if there is a replacement class what to use instead Object subclass: #OldClass instanceVariableNames: '' classVariableNames: '' package: 'Deprecated70-OldTag' and comment to explain the reasons: OldClass comment: 'Use NewClass instead'. and implement in class side method category 'testing' isDeprecated "We do not need this class anymore" ^true Note that the class is striked through in the system browser. DEPRECATING PACKAGES ==================== If you deprecate a PACKAGE then rename it with "Deprecated" in the name. Let the class side of the package manifest (typically a subclass of PackageManifest within the package) als return #isDeprecated with true. In the class comment of the package manifest (which also serves as package comment) explain why the package is deprecated and if there is a replacement or not. Example: your package name is "OldPackage-Core", so the new name is "OldPackage-Deprecated-Core". Create a manifest or use the existing one. A Manifest should be a subclass of PackageManifest and should be categorized within a 'Manifest' tag. PackageManifest subclass: #ManifestOldPackageCore instanceVariableNames: '' classVariableNames: '' package: 'OldPackage-Deprecated-Core-Manifest' and comment to explain the reasons: ManifestOldPackageCore comment: 'This package is not useful anymore. Check NewPackage for replacement'. and implement in class side method category 'testing' isDeprecated "We do not need this package anymore" ^true Note that the manifest class and the package is striked through in the system browser. Be aware that a deprecated package might be removed completely already in the next Pharo major version iteration.

1 0

Debugger should step silently over #halt
by Ben Coman Sept. 20, 2018

Sept. 20, 2018

I'll often put several breakpoints in code like this... ``` debug := true. "Somewhere else in application code..." debug ifTrue: [ self halt ]. 1 + 1. "Representing some longer bit of application code" debug ifTrue: [ self halt ]. 2 + 2. "Representing some longer bit of application code" debug ifTrue: [ self halt ]. 3 + 3. "Representing some longer bit of application code" ``` While stepping <Over> code after hitting the first halt, I am used to subsequent halts being silently stepped over. I just confirmed this with http://files.pharo.org/platform/Pharo6.0-win.zip and also build 60541 started from PharoLauncher. However build 71231 and build 60542 do not silently step over a #halt. Each produces slightly different results (pics attached). [image: P01-Double-Halt-Pharo7.png] [image: P02-Double-Halt-Pharo60542.png] I've logged an issue... https://pharo.fogbugz.com/f/cases/22474/Debugger-should-step-silently-over-… cheers -ben

2 2

Platform file encoding for FFI
by Alistair Grant Sept. 19, 2018

Sept. 19, 2018

Hi Esteban, Guille and Everyone, I haven't looked at using FFI much, however it is easy to imagine that different file encoding rules on different platforms will make writing FFI calls more difficult, i.e. some of the different formats are: - OSX uses Mac specific decomposed UTF8 encoding - Windows uses Wide Strings (16 bit Unicode characters) - Linux allows pretty much anything, but precomposed UTF8 is common Believe it or not, I'm still working on getting the FileAttributesPlugin working (file name encoding on Windows being the latest issue - the tests in Pharo need to be extended). Would it be useful for future FFI work to have primitives available which convert file names to and from the various platform specific formats? (Linux is basically a no-op, and Windows could be written in-image, but OSX requires the platform routines to be called). Cheers, Alistair

5 10

[Pharo 7.0-dev] Build #1259: 21660-Changing-the-superclass-of-a-Class-using-superclass-method-does-not-update-instSize-correctly
by ci-pharo-ci-jenkins2＠inria.fr Sept. 19, 2018

Sept. 19, 2018

There is a new Pharo build available! The status of the build #1259 was: FAILURE. The Pull Request #1618 was integrated: "21660-Changing-the-superclass-of-a-Class-using-superclass-method-does-not-update-instSize-correctly" Pull request url: https://github.com/pharo-project/pharo/pull/1618 Issue Url: https://pharo.fogbugz.com/f/cases/21660 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1258: 22457-Provide-a-CalendarPresenter-fully-written-in-Spec
by ci-pharo-ci-jenkins2＠inria.fr Sept. 19, 2018

Sept. 19, 2018

There is a new Pharo build available! The status of the build #1258 was: SUCCESS. The Pull Request #1804 was integrated: "22457-Provide-a-CalendarPresenter-fully-written-in-Spec" Pull request url: https://github.com/pharo-project/pharo/pull/1804 Issue Url: https://pharo.fogbugz.com/f/cases/22457 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1257: 22469-Small-cleanup-in-NEC-Model-classes
by ci-pharo-ci-jenkins2＠inria.fr Sept. 19, 2018

Sept. 19, 2018

There is a new Pharo build available! The status of the build #1257 was: FAILURE. The Pull Request #1815 was integrated: "22469-Small-cleanup-in-NEC-Model-classes" Pull request url: https://github.com/pharo-project/pharo/pull/1815 Issue Url: https://pharo.fogbugz.com/f/cases/22469 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1256: 22448 Cleanup ManifestSystemModel and related package
by ci-pharo-ci-jenkins2＠inria.fr Sept. 19, 2018

Sept. 19, 2018

There is a new Pharo build available! The status of the build #1256 was: FAILURE. The Pull Request #1796 was integrated: "22448 Cleanup ManifestSystemModel and related package" Pull request url: https://github.com/pharo-project/pharo/pull/1796 Issue Url: https://pharo.fogbugz.com/f/cases/22448 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1255: 20111-Some-Collection-tests-fail-on-64-bit-because-they-assume-Floats-are-non-immediate
by ci-pharo-ci-jenkins2＠inria.fr Sept. 19, 2018

Sept. 19, 2018

There is a new Pharo build available! The status of the build #1255 was: SUCCESS. The Pull Request #1624 was integrated: "20111-Some-Collection-tests-fail-on-64-bit-because-they-assume-Floats-are-non-immediate" Pull request url: https://github.com/pharo-project/pharo/pull/1624 Issue Url: https://pharo.fogbugz.com/f/cases/20111 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Roassal2 crashing when drawing TRLabelShape
by Oleksandr Zaytsev Sept. 18, 2018

Sept. 18, 2018

Hello, Roassal2 has recently been crashing on my image on every example that includes text. Peter Uhnak helped me discover that it crashes when drawing a TRLabelShape and maybe Cairo doesn't like the new FT plugin. Some experiments: 1. Inspecting an empty view (RTView new inspect) doesn't crash. 2. Everything works well on Pharo 7. My image and crash.dmp can be found in this folder: https://drive.google.com/drive/folders/1lypWVL6VwYfHCqRuXZfnAcA4qZGulDal?us… Oleks

1 0

Re: [Pharo-dev] [squeak-dev] _: in selectors
by Eliot Miranda Sept. 18, 2018

Sept. 18, 2018

On Tue, Sep 18, 2018 at 10:38 AM Levente Uzonyi <leves(a)caesar.elte.hu> wrote: > Hi Eliot, > > That's clearly a bug as the compiler accepts this: > > method: p __: q __: r > ^'cool' > ROTFL > > Levente > > On Tue, 18 Sep 2018, Eliot Miranda wrote: > > > Hi All, > > Pharo accepts > > > > method: p _: q _: r > > ^'cool' > > > > Squeak does not. I have an urgent compelling use case in VMMaker. > Would there be any strong objections to me modifying the Squeak compiler to > accept the above when the allowUnderscoresInSelectors > > preference is in effect? > > _,,,^..^,,,_ > > best, Eliot > > > > > -- _,,,^..^,,,_ best, Eliot

1 0

_: in selectors
by Eliot Miranda Sept. 18, 2018

Sept. 18, 2018

Hi All, Pharo accepts method: p _: q _: r ^'cool' Squeak does not. I have an urgent compelling use case in VMMaker. Would there be any strong objections to me modifying the Squeak compiler to accept the above when the allowUnderscoresInSelectors preference is in effect? _,,,^..^,,,_ best, Eliot

1 0

[Pharo 7.0-dev] Build #1254: 22463 Tag ManifestTextCore and classes in package Text-Core-Manifest
by ci-pharo-ci-jenkins2＠inria.fr Sept. 18, 2018

Sept. 18, 2018

There is a new Pharo build available! The status of the build #1254 was: SUCCESS. The Pull Request #1811 was integrated: "22463 Tag ManifestTextCore and classes in package Text-Core-Manifest" Pull request url: https://github.com/pharo-project/pharo/pull/1811 Issue Url: https://pharo.fogbugz.com/f/cases/22463 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1253: 22456 dynamic left to right columns layout generates an additional unneeded row with null presenters
by ci-pharo-ci-jenkins2＠inria.fr Sept. 18, 2018

Sept. 18, 2018

There is a new Pharo build available! The status of the build #1253 was: SUCCESS. The Pull Request #1803 was integrated: "22456 dynamic left to right columns layout generates an additional unneeded row with null presenters" Pull request url: https://github.com/pharo-project/pharo/pull/1803 Issue Url: https://pharo.fogbugz.com/f/cases/22456 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

UndefinedClasses as first class entities for P7
by Torsten Bergmann Sept. 18, 2018

Sept. 18, 2018

At ESUG 207 there was a presentation about UndefinedClasses as first class entities. According to the slides: https://de.slideshare.net/esug/firstclass-undefined-classes-for-pharo-from-… this was planned for inclusion into Pharo 7. Is this still on the plate? Any status? Thanks T.

4 4

Confused about FileReference read/write streams
by Sven Van Caekenberghe Sept. 18, 2018

Sept. 18, 2018

Hi, Since ever (or as far as I can remember), FileReference made a distinction between read and write streams, see #readStream[Do:] and #writeStream[Do:] - these return a ZnCharacterReadStream and ZnCharacterWriteStream in Pharo 7. Along the same lines, #binaryReadStream and #binaryWriteStream where introduced. However, the first returns a ZnBufferedReadStream (OK) while the latter returns a ZnBufferedReadWriteStream. Why ? I think it would be generally better if a standard ZnBufferedWriteStream where returned. ZnBufferedReadWriteStream is not a very pretty class to say the least, it also strikes me as confusing. What would break if we changed this ? If necessary there could be something like #readWriteStream[Do:] I guess. Sven

2 2

Standardized nomenclature for feature requests
by Esteban A. Maringolo Sept. 17, 2018

Sept. 17, 2018

Hi there, Q: Is there a reason why Pharo (as a project) doesn't follow a standardized nomenclature for features/request as other communities does? So for instance something like PFR-005 (Pharo Feature Request) could be "Truly headless images", PFR-006 "Pharo Bootstrapping", etc. I can't really tell whether this would improve to the overall process, but I wanted to know if this was already debated by the board and dismissed, if it is something that wasn't considered at all, of if we have something equivalent and what it is. Regards, Language examples: JSR (Java Specification Requests) https://www.jcp.org/en/jsr/all PEP (Python Enhancement Proposals) https://www.python.org/dev/peps/ RFC (Rust, Request for Comments) https://github.com/rust-lang/rfcs Technologies: BIP (Bitcoin Improvement Proposal) https://github.com/bitcoin/bips EIP (Ethereum Improvement Proposal) https://eips.ethereum.org/ -- Esteban A. Maringolo

1 0

ZnMimePart Disposition-Content spaces
by Ben Coman Sept. 17, 2018

Sept. 17, 2018

Hi Sven, We encountered a ZnMimePart Content-Disposition header problem with a server expecting a space following the "form-data;" string. The diff here... https://www.diffchecker.com/ETIfCUzx * on the left shows the working request from the default command-line tool * on the right shows the non-working request from Pharo. The specifications are really unclear about the requirement or not for a space, so it may be reasonable to consider the fault lies with the server not being permissive enough, but I notice these examples all have space after semi colons... * https://tools.ietf.org/html/rfc7578 * https://www.ietf.org/rfc/rfc2388.txt so I wonder if this scenario might be widespread (and endemic to Rails apps which this was) and maybe its pragmatic to include the extra spaces to cut off potential issues (it took quite a while to isolate with the live service being HTTPS only.) Steps to reproduce are here... https://github.com/exercism/pharo/issues/96#issuecomment-421224203 In the meantime, once isolated it was simple to work around, but it was almost a show stopper, so I'm interested in your thoughts. cheers -ben

1 0

[Pharo 7.0-dev] Build #1252: 22417 Decide about DateAndTimeDosEpochTest>>testToByDo
by ci-pharo-ci-jenkins2＠inria.fr Sept. 17, 2018

Sept. 17, 2018

There is a new Pharo build available! The status of the build #1252 was: FAILURE. The Pull Request #1810 was integrated: "22417 Decide about DateAndTimeDosEpochTest>>testToByDo" Pull request url: https://github.com/pharo-project/pharo/pull/1810 Issue Url: https://pharo.fogbugz.com/f/cases/22417 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1251: 22459-FileReferencecopyTo-deserves-a-much-better-comment
by ci-pharo-ci-jenkins2＠inria.fr Sept. 17, 2018

Sept. 17, 2018

There is a new Pharo build available! The status of the build #1251 was: SUCCESS. The Pull Request #1807 was integrated: "22459-FileReferencecopyTo-deserves-a-much-better-comment" Pull request url: https://github.com/pharo-project/pharo/pull/1807 Issue Url: https://pharo.fogbugz.com/f/cases/22459 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] New Pharo 6.1 stable VM
by Esteban Lorenzano Sept. 17, 2018

Sept. 17, 2018

Hi, Following what I had in my todo list for when coming back from ESUG, I promoted a new stable VM for Pharo 6.1. This is the VM that has been tested during almost two months for Pharo 7.0, so it should be fine, but let me know if there is any problem. Esteban

1 0

[Pharo 7.0-dev] Build #1249: 22452 Added #labelHeight method.
by ci-pharo-ci-jenkins2＠inria.fr Sept. 16, 2018

Sept. 16, 2018

There is a new Pharo build available! The status of the build #1249 was: FAILURE. The Pull Request #1800 was integrated: "22452 Added #labelHeight method." Pull request url: https://github.com/pharo-project/pharo/pull/1800 Issue Url: https://pharo.fogbugz.com/f/cases/22452 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

2 1

[Pharo 7.0-dev] Build #1250: 22451 Unselecting example from SpecDemo's left list raises an exception
by ci-pharo-ci-jenkins2＠inria.fr Sept. 16, 2018

Sept. 16, 2018

There is a new Pharo build available! The status of the build #1250 was: SUCCESS. The Pull Request #1802 was integrated: "22451 Unselecting example from SpecDemo's left list raises an exception" Pull request url: https://github.com/pharo-project/pharo/pull/1802 Issue Url: https://pharo.fogbugz.com/f/cases/22451 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1248: 22454 Add comments to #presenter:configuredAs: and #presenterProvidedBy:configuredAs: methods of DynamicPresentersListBuilder
by ci-pharo-ci-jenkins2＠inria.fr Sept. 16, 2018

Sept. 16, 2018

There is a new Pharo build available! The status of the build #1248 was: FAILURE. The Pull Request #1801 was integrated: "22454 Add comments to #presenter:configuredAs: and #presenterProvidedBy:configuredAs: methods of DynamicPresentersListBuilder" Pull request url: https://github.com/pharo-project/pharo/pull/1801 Issue Url: https://pharo.fogbugz.com/f/cases/22454 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1247: 22443 Tag and comment ManifestSystemAnnouncements
by ci-pharo-ci-jenkins2＠inria.fr Sept. 14, 2018

Sept. 14, 2018

There is a new Pharo build available! The status of the build #1247 was: FAILURE. The Pull Request #1790 was integrated: "22443 Tag and comment ManifestSystemAnnouncements" Pull request url: https://github.com/pharo-project/pharo/pull/1790 Issue Url: https://pharo.fogbugz.com/f/cases/22443 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1246: 22446 Comment ManifestSpecInspector and ManifestSpecMorphicAdapters
by ci-pharo-ci-jenkins2＠inria.fr Sept. 13, 2018

Sept. 13, 2018

There is a new Pharo build available! The status of the build #1246 was: SUCCESS. The Pull Request #1794 was integrated: "22446 Comment ManifestSpecInspector and ManifestSpecMorphicAdapters" Pull request url: https://github.com/pharo-project/pharo/pull/1794 Issue Url: https://pharo.fogbugz.com/f/cases/22446 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1245: 22449-Port-back-old-OSWindow-changes
by ci-pharo-ci-jenkins2＠inria.fr Sept. 13, 2018

Sept. 13, 2018

There is a new Pharo build available! The status of the build #1245 was: SUCCESS. The Pull Request #1797 was integrated: "22449-Port-back-old-OSWindow-changes" Pull request url: https://github.com/pharo-project/pharo/pull/1797 Issue Url: https://pharo.fogbugz.com/f/cases/22449 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1244: 22444 Cleanup manifest in system basic command line handler utilities
by ci-pharo-ci-jenkins2＠inria.fr Sept. 13, 2018

Sept. 13, 2018

There is a new Pharo build available! The status of the build #1244 was: SUCCESS. The Pull Request #1791 was integrated: "22444 Cleanup manifest in system basic command line handler utilities" Pull request url: https://github.com/pharo-project/pharo/pull/1791 Issue Url: https://pharo.fogbugz.com/f/cases/22444 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1243: 22442 Tag and comment Manifests in all Spec related packages
by ci-pharo-ci-jenkins2＠inria.fr Sept. 13, 2018

Sept. 13, 2018

There is a new Pharo build available! The status of the build #1243 was: SUCCESS. The Pull Request #1789 was integrated: "22442 Tag and comment Manifests in all Spec related packages" Pull request url: https://github.com/pharo-project/pharo/pull/1789 Issue Url: https://pharo.fogbugz.com/f/cases/22442 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1242: 22439 Cleanup Manifest in RandomCore package
by ci-pharo-ci-jenkins2＠inria.fr Sept. 13, 2018

Sept. 13, 2018

There is a new Pharo build available! The status of the build #1242 was: SUCCESS. The Pull Request #1787 was integrated: "22439 Cleanup Manifest in RandomCore package" Pull request url: https://github.com/pharo-project/pharo/pull/1787 Issue Url: https://pharo.fogbugz.com/f/cases/22439 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1241: 22376 Add a quick setup to the welcome page
by ci-pharo-ci-jenkins2＠inria.fr Sept. 13, 2018

Sept. 13, 2018

There is a new Pharo build available! The status of the build #1241 was: SUCCESS. The Pull Request #1727 was integrated: "22376 Add a quick setup to the welcome page" Pull request url: https://github.com/pharo-project/pharo/pull/1727 Issue Url: https://pharo.fogbugz.com/f/cases/22376 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1240: 22435-delete-method-tesOptionAt
by ci-pharo-ci-jenkins2＠inria.fr Sept. 11, 2018

Sept. 11, 2018

There is a new Pharo build available! The status of the build #1240 was: FAILURE. The Pull Request #1793 was integrated: "22435-delete-method-tesOptionAt" Pull request url: https://github.com/pharo-project/pharo/pull/1793 Issue Url: https://pharo.fogbugz.com/f/cases/22435 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Sept. 11, 2018

Hello We would like to have a BOF around Pharo. Since there are many topics to talk about. Tuesday after the show us your project? We can have one at the beach before the social event aroun 17h? Stef -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / 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

Call for Papers: <Programming> 2019
by Fabio Niephaus Sept. 10, 2018

Sept. 10, 2018

<Programming> 2019 : The Art, Science, and Engineering of Programming April 1-4, 2019, Genova, Italy http://2019.programming-conference.org The International Conference on the Art, Science, and Engineering of Programming is a new conference focused on programming topics including the experience of programming. We have named it <Programming> for short. <Programming> seeks for papers that advance knowledge of programming on any relevant topic, including programming practice and experience. Paper submissions and publications are handled by the the Art, Science, and Engineering of Programming journal (http://programming-journal.org) Accepted papers must be presented at the conference. ******************************************************** CALL FOR PAPERS ******************************************************** <Programming> 2019 accepts scholarly papers that advance knowledge of programming. Almost anything about programming is in scope, but in each case there should be a clear relevance to the act and experience of programming. PAPER SUBMISSIONS: October 1, 2018 URL FOR SUBMISSIONS: http://programming-journal.org/submission/ Submissions covering several areas of expertise are accepted, including but not limited to: â¢ General-purpose programming â¢ Distributed systems programming â¢ Parallel and multi-core programming â¢ Graphics and GPU programming â¢ Security programming â¢ User interface programming â¢ Database programming â¢ Visual and live programming â¢ Data mining and machine learning programming â¢ Interpreters, virtual machines and compilers â¢ Modularity and separation of concerns â¢ Model-based development â¢ Metaprogramming and reflection â¢ Testing and debugging â¢ Program verification â¢ Programming education â¢ Programming environments â¢ Social coding ******************************************************** IMPORTANT DATES ******************************************************** Research paper submissions: October 1, 2018 Research paper first notifications: December 1, 2018 Research paper final notifications: January 7, 2019 ******************************************************** ORGANIZATION ******************************************************** General Chair: Davide Ancona, University of Genova Local Organizing Chair: Elena Zucca, University of Genova Program Chair: Matthew Flatt, University of Utah Organizing Committee: Walter Cazzola (Workshops Co-Chair), UniversitÃ degli Studi di Milano Stefan Marr (Workshops Co-Chair), University of Kent Fabio Niephaus (Publicity Co-Chair), Hasso Plattner Institute, University of Potsdam Guido Salvaneschi (Publicity Co-Chair), Darmstadt University of Technology Tobias Pape (Web Technology Chair), Hasso Plattner Institute, University of Potsdam Program Committee: Anya Helene Bagge, University of Bergen Mehdi Bagherzadeh, Oakland University Walter Cazzola, UniversitÃ degli Studi di Milano Ravi Chugh, University of Chicago Joeri De Koster, Vrije Universiteit Brussel Christos Dimoulas, Northwestern University Susan Eisenbach, Imperial College London Richard P. Gabriel, Dream Songs, Inc. & HPI Jeremy Gibbons, University of Oxford Michael Greenberg, Pomona College Philipp Haller, KTH Royal Institute of Technology Robert Hirschfeld, HPI, University of Potsdam Eunsuk Kang, Carnegie Mellon University Stephen Kell, University of Cambridge Stefan Marr, University of Kent Tamara Rezk, Inria Joshua Sunshine, Carnegie Mellon University Steffen Zschaler, King's College London ******************************************************** <Programming> 2019 is kindly supported by AOSA ******************************************************** For more information, visit http://2019.programming-conference.org

1 0

Iceberg goodness plus ideas
by Ben Coman Sept. 10, 2018

Sept. 10, 2018

First, kudos to Iceberg team for detecting the mistake I made messing around at the command line under the feet of an Iceberg managed repo. I'm interested in some general discussion of a few ideas before logging any issues. I had an Iceberg managed repo branch "ready-multiple-commands" as shown at [A] in the attached pic. (note that this is "exercism/pharo" not "pharo-project/pharo") I wanted to compare "git log --graph" between a few branches so I jumped into a command prompt and did so. Along the way I changed branch to "master" from the command line [B]. Then friends arrived and it was six hours until I got back to it and was presented with "Detached Working Copy" [C], and I'd forgotten what I'd done. Repair repository [D] didn't make this immediately obvious although given the two commits after a while I managed to work it out and simply `git checkout ready-multiple-commands` at the command line fixed things, returning the display to [A]. So the discussion points I'm interested in are: a. An extra column "Image Branch" with the existing column renamed "Disk Branch" would have made my mistake immediately obvious. b. Such under the covers command line operation may be a corner case(??), so if not an extra column, a red Status message "Image Branch ready-multiple-commands" or similar would have helped. c. In the first paragraph of [D] it was not apparent what "working copy" and "repository commit" referred to (although after a while I worked it out from the given commit hashes -- the former was in-Image and the latter on-disk. But the files on disk are a "working copy" in all other git documentation and it invites confusion not to refer to it like that. It seems to me we deal with two working copies: an "image working copy" and a "disk working copy". That terminology would have eased discovery of my mistake. d. Instead of the commit hashes [D], is it feasible to match those to branches/tags and display those. That would have made my mistake more obvious. d. In [D], its not clear the difference between: "Discard local changes" "Discard image changes" cheers -ben

2 5

Esteban's ChangeLog week of 3 September 2018
by estebanlm＠gmail.com Sept. 10, 2018

Sept. 10, 2018

Hello! This is my weekly ChangeLog, from 3 September 2018 to 9 September 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=3/9/2018&to=9/9/2018 ChangeLog ========= 4 September 2018: ----------------- * While I'm back from my holidays, this week will be slow and full of admin work. Nothing very relevant to inform :) Also, I'm preparing my presentation for ESUG :) cheers! Esteban

1 0

Pharo and Docker (some steps)
by Torsten Bergmann Sept. 9, 2018

Sept. 9, 2018

For those interested in Docker: I recently played with Pharo and Docker and summarized some of my steps in a small tutorial in my Pharo wiki: http://wiki.astares.com/pharo/613 There is also a page following Mike Filonovs suggestions on the Pharo docker file: http://wiki.astares.com/pharo/615 Maybe this is useful for others too. Bye T.

3 2

Added Pharo8 milestone to issue tracker
by Marcus Denker Sept. 9, 2018

Sept. 9, 2018

Hi, As part of getting ready for the release, we should check all issue tracker entries tagged for pharo7 and decide if they are real show stoppers. I added a Pharo8 Milestone (but when removing the pharo7 milestone, it is in most cases better to just put it on âLaterâ). Marcus

1 0

[Pharo 7.0-dev] Build #1239: 22434 Cleanup FloatTest
by ci-pharo-ci-jenkins2＠inria.fr Sept. 8, 2018

Sept. 8, 2018

There is a new Pharo build available! The status of the build #1239 was: SUCCESS. The Pull Request #1783 was integrated: "22434 Cleanup FloatTest" Pull request url: https://github.com/pharo-project/pharo/pull/1783 Issue Url: https://pharo.fogbugz.com/f/cases/22434 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1238: 22404-NECSymbolCache-is-not-needed-anymore
by ci-pharo-ci-jenkins2＠inria.fr Sept. 8, 2018

Sept. 8, 2018

There is a new Pharo build available! The status of the build #1238 was: SUCCESS. The Pull Request #1769 was integrated: "22404-NECSymbolCache-is-not-needed-anymore" Pull request url: https://github.com/pharo-project/pharo/pull/1769 Issue Url: https://pharo.fogbugz.com/f/cases/22404 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1237: 22422 Correctly deprecate Ring- Core-Kernel and Ring Tests Kernel
by ci-pharo-ci-jenkins2＠inria.fr Sept. 7, 2018

Sept. 7, 2018

There is a new Pharo build available! The status of the build #1237 was: SUCCESS. The Pull Request #1773 was integrated: "22422 Correctly deprecate Ring- Core-Kernel and Ring Tests Kernel" Pull request url: https://github.com/pharo-project/pharo/pull/1773 Issue Url: https://pharo.fogbugz.com/f/cases/22422 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] [Pharo-users] [Moose-dev] Pharo eye-candy: Domain-Specific Modeling and Simulation
by Nick Papoylias Sept. 7, 2018

Sept. 7, 2018

Thanx Alex :) Looking forward to the Roassal talk on Thursday ! On Fri, Sep 7, 2018 at 5:22 PM Alexandre Bergel via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Wow!!!!! > You guys rock! > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Sep 6, 2018, at 2:17 PM, Nick Papoylias <npapoylias(a)gmail.com> wrote: > > A nice example of how Pharo can be used for > domain-specific modeling and simulation. Short > session from one of our projects at Rochelle: > > https://www.youtube.com/watch?v=Z7wJNhAIaVQ > > Some additional info here: https://goo.gl/jS4NjB > > Currently investigating how to incorporate the new Bloc based > widgets of @feenkcom into the workflow. > > Cheers, > > Nick > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > > >

1 0

Release test for unused temps and other
by Torsten Bergmann Sept. 7, 2018

Sept. 7, 2018

Hi, the very nice contribution on GIFReadWriter/animated images (see https://pharo.manuscript.com/f/cases/22137) unfortunately introduced some methods that had no sender, were uncategorized and had unused temporary variables, etc. Something that is meanwhile shown by our tools and easy to fix. I guess it was some overseen leftover. Unfortunately this also slipped through the integration process as it was merged without an approval from a community reviewer. I dont want to lament too much on this specifc case (especially as I now fixed it in https://pharo.fogbugz.com/f/cases/22426) But after I cleaned the P7 image this spring to not have unused temporaries anymore I was suprised to find such glitches again now. So to me it shows that we need to write more tests to detect violations and keep our achieved quality standards up and also should not solely rely on the review process. Otherwise we need to invest our time in cleaning up our own stuff afterwards again and again. To be specific one can evaluate: CompiledMethod allInstances select: [:m | m ast temporaries anySatisfy: [:x | x binding isUnused ]]. to find unused temps - which would be easy to package up into one of the release test to ensure no unused temp vars are left (the tearDown would require an "ASTCache reset"). The problem is that this simple test would take around 20-30 seconds depending on machine and I do not know if it would be a good idea/good solution to integrate. Especially I'm not sure if it is worth the issue or will kill the CI again and again. What do you think about it? Comments appreciated? Thanks T.

5 6

Pharo eye-candy: Domain-Specific Modeling and Simulation
by Nick Papoylias Sept. 7, 2018

Sept. 7, 2018

A nice example of how Pharo can be used for domain-specific modeling and simulation. Short session from one of our projects at Rochelle: https://www.youtube.com/watch?v=Z7wJNhAIaVQ Some additional info here: https://goo.gl/jS4NjB Currently investigating how to incorporate the new Bloc based widgets of @feenkcom into the workflow. Cheers, Nick

6 9