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

[Pharo 7.0-dev] Build #1178: 22345 Tag Manifests in IssueTracking and IssueTracking-Tests
by ci-pharo-ci-jenkins2＠inria.fr Aug. 20, 2018

Aug. 20, 2018

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

1 0

A new rule to implement in Pharo ?
by Lionel Akue Aug. 20, 2018

Aug. 20, 2018

Hello, Do you have a rule you would like to get implement in Pharo? I am reading about Renraku and I would like to exercise. Thanks, Lionel

4 3

[Pharo 7.0-dev] Build #1177: 22339 Cleanup canZapMethodDictionary
by ci-pharo-ci-jenkins2＠inria.fr Aug. 20, 2018

Aug. 20, 2018

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

1 0

Uncomitted changes in latest image
by Torsten Bergmann Aug. 19, 2018

Aug. 19, 2018

There are uncomitted changes in the latest Pharo image (Pharo-7.0+alpha.build.1176.sha.eedde11d2331266218204b1bb5c77a9037b7a706 (64 Bit)) for some packages. Got the image out of sync with the sources?

1 0

feenk log
by Tudor Girba Aug. 17, 2018

Aug. 17, 2018

Hi, We again got carried away and forgot to update the world about what is up in our corner. Here is a summary: -- Bloc & Brick -- - Text editor stability has been significantly improved - Improved support for selection in the text editor - Support for typical editing keybindings (copy, cut, paste) - Text editor debuggability: https://twitter.com/feenkcom/status/1024680215379959808 https://twitter.com/feenkcom/status/1020768298017992704 - The text editor can handle emojis: https://twitter.com/feenkcom/status/1021872214151507968 -- GT -- - Inspector We now have an initial version of a working inspector with resizable panes: https://twitter.com/feenkcom/status/1030091849795612672 https://twitter.com/feenkcom/status/1030314856736538624 It shows a display string for the current object: https://twitter.com/feenkcom/status/1024564065870512129 It can handle errors in the definition of views gracefully: https://twitter.com/feenkcom/status/1009174937217720320 We now have multiple extensions expressed in the new Inspector: https://twitter.com/feenkcom/status/1024321868566814720 https://twitter.com/feenkcom/status/1022393383850008576 - Documenter saw multiple enhancements. We can now resize various previews live: https://twitter.com/feenkcom/status/1002851190475026432 https://twitter.com/feenkcom/status/1001407762285375490 https://twitter.com/feenkcom/status/1001152789874167808 It now relies on the annotation mechanism from Pillar: https://twitter.com/feenkcom/status/1006508725409079298 We can now link classes and expand their definition: https://twitter.com/feenkcom/status/1014609460520775681 https://twitter.com/feenkcom/status/1029085603948843008 The preview of examples can handle errors gracefully: https://twitter.com/feenkcom/status/1022123808524836864 We can run examples in place, enabling a smoother tutorial experience: https://twitter.com/feenkcom/status/1028390957023223809 We have new documentation expressed in it: https://twitter.com/feenkcom/status/1007008814204444672 Have fun, The feenk team -- www.feenk.com "Presenting is storytelling."

4 4

Re: [Pharo-dev] Collection groupedBy: and groups order
by Damien Pollet Aug. 17, 2018

Aug. 17, 2018

The problem is, there isn't really an order to preserve in the first place, since even if the original collection is a sequencable one, the elements of each group would be interleaved in it. I could see the point of sorting the keys though. On Tue, 14 Aug 2018 at 18:32, Petr Fischer via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > Hello, I found a useful method in the collection - groupedBy: - the result > container is some PlugableDictionary (integer variant) and group order > (keys) is not preserved. > > Would not it be better to choose some other Dictionary variant, which > preserve the order of groups (like in source Collection)? > > pf > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

3 2

[Pharo 7.0-dev] Build #1176: 22335-Add-Spec-Demo
by ci-pharo-ci-jenkins2＠inria.fr Aug. 17, 2018

Aug. 17, 2018

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

1 0

[update 6.1] #60542
by Marcus Denker Aug. 17, 2018

Aug. 17, 2018

60542 ----- 22305 Backport to Pharo6: "Leave Variable Undeclared" https://pharo.fogbugz.com/f/cases/22305 <https://pharo.fogbugz.com/f/cases/22305> <https://pharo.fogbugz.com/f/cases/22305> 22298 Backport of the fix of Infinite Debugger https://pharo.fogbugz.com/f/cases/22298 <https://pharo.fogbugz.com/f/cases/22298>

2 2

[Pharo 7.0-dev] Build #1175: 22204 new value holder package should be split into new value holder core and new value holder tests packages
by ci-pharo-ci-jenkins2＠inria.fr Aug. 17, 2018

Aug. 17, 2018

There is a new Pharo build available! The status of the build #1175 was: SUCCESS. The Pull Request #1596 was integrated: "22204 new value holder package should be split into new value holder core and new value holder tests packages" Pull request url: https://github.com/pharo-project/pharo/pull/1596 Issue Url: https://pharo.fogbugz.com/f/cases/22204 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] Collection groupedBy: and groups order
by StÃ©phane Ducasse Aug. 16, 2018

Aug. 16, 2018

Hi Petr do you have a test illustrating what behavior you think should be good? 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

2 1

[Pharo 7.0-dev] Build #1174: 22315-remove-implicit-requirement-from-traits
by ci-pharo-ci-jenkins2＠inria.fr Aug. 16, 2018

Aug. 16, 2018

There is a new Pharo build available! The status of the build #1174 was: SUCCESS. The Pull Request #1686 was integrated: "22315-remove-implicit-requirement-from-traits" Pull request url: https://github.com/pharo-project/pharo/pull/1686 Issue Url: https://pharo.fogbugz.com/f/cases/22315 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1173: 22314-Stdio-doesnt-handle-cygwin-terminals-correctly
by ci-pharo-ci-jenkins2＠inria.fr Aug. 16, 2018

Aug. 16, 2018

There is a new Pharo build available! The status of the build #1173 was: FAILURE. The Pull Request #1684 was integrated: "22314-Stdio-doesnt-handle-cygwin-terminals-correctly" Pull request url: https://github.com/pharo-project/pharo/pull/1684 Issue Url: https://pharo.fogbugz.com/f/cases/22314 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Association hash vs equality
by Jan BlizniÄenko Aug. 16, 2018

Aug. 16, 2018

Hello, I've been looking at implementation of Associtation and LookupKey (its superclass). In LookupKey, there is LookupKey>>#= and LookupKey>>#hash both implemented to use key (compare keys and use hash of key), but in Association, Association>>#= compares both key and value, but hash is not changed there, so only hash of key is used, therefore it does not correspond to implementation of method = ... shouldn't it? To demonstrate: (1 -> #a) = (1 -> #b). is false but (1 -> #a) hash = (1 -> #b) hash. is true I also noticed similar discussion for Doplhin smalltalk http://forum.world.st/Association-gt-gt-hash-td3368868.html where guys state it is all right, but I still do not see why. Jan -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 1

[Pharo 7.0-dev] Build #1172: 22307-Refactoring-doesnt-work-in-debugger---Walkback-dnu-contentSelection
by ci-pharo-ci-jenkins2＠inria.fr Aug. 16, 2018

Aug. 16, 2018

There is a new Pharo build available! The status of the build #1172 was: FAILURE. The Pull Request #1680 was integrated: "22307-Refactoring-doesnt-work-in-debugger---Walkback-dnu-contentSelection" Pull request url: https://github.com/pharo-project/pharo/pull/1680 Issue Url: https://pharo.fogbugz.com/f/cases/22307 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1171: 22312-Integrate-Iceberg-v122
by ci-pharo-ci-jenkins2＠inria.fr Aug. 16, 2018

Aug. 16, 2018

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

1 0

[Pharo 7.0-dev] Build #1170: 22137-gif-read-writer-refactoring-and-animated-images
by ci-pharo-ci-jenkins2＠inria.fr Aug. 15, 2018

Aug. 15, 2018

There is a new Pharo build available! The status of the build #1170 was: FAILURE. The Pull Request #1666 was integrated: "22137-gif-read-writer-refactoring-and-animated-images" Pull request url: https://github.com/pharo-project/pharo/pull/1666 Issue Url: https://pharo.fogbugz.com/f/cases/22137 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1169: Revert "Disabling OSX tests until the slave resucitates"
by ci-pharo-ci-jenkins2＠inria.fr Aug. 14, 2018

Aug. 14, 2018

There is a new Pharo build available! The status of the build #1169 was: SUCCESS. The Pull Request #1688 was integrated: "Revert "Disabling OSX tests until the slave resucitates"" Pull request url: https://github.com/pharo-project/pharo/pull/1688 Issue Url: https://pharo.fogbugz.com/f/cases/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

ZnHeaders should allow custom or empty Server info
by Torsten Bergmann Aug. 14, 2018

Aug. 14, 2018

Hi Sven, when running a Zinc Server ZnServer startDefaultOn: 8080. the server currently reveals the framework, the framework version and the Pharo version the server is running on as part of the HTTP communication. For instance (ZnEasy get: 'http://localhost:8080') headers at: 'Server' would give Zinc HTTP Components 1.0 (Pharo/7.0) in the Server Header. While this is nice for debugging and during development this can be a problem in more secured/pentested environments where usually specific headers are turned off to not give specific informations to an attacker (to allow him to find vulnerabilities of specific versions or servers). While headers could be changed rewritten in front-ends or load balancing servers we can not assume that Pharo images work as backend server always. Webservers like Nginx, Apache, IIS, Express in JS, PHP and other allow to disable/modify these headers. Using the attached changeset it is possible to modify the Server header and customize it: ZnHeaders serverString: 'MoreSecureServer' If the server string is not customized the default server string is used as before. We should make sure this is integrated into Pharo 7 but also into the Zinc framework. I opened a bug https://pharo.fogbugz.com/f/cases/22317/ZnHeaders-should-allow-custom-or-em… As Zinc is also managed externally how should we proceed? Thx T.

1 0

Collection groupedBy: and groups order
by Petr Fischer Aug. 14, 2018

Aug. 14, 2018

Hello, I found a useful method in the collection - groupedBy: - the result container is some PlugableDictionary (integer variant) and group order (keys) is not preserved. Would not it be better to choose some other Dictionary variant, which preserve the order of groups (like in source Collection)? pf

1 0

ZnHTTPSTests and more CI trouble
by Torsten Bergmann Aug. 14, 2018

Aug. 14, 2018

Latest build fails with #testGetPharoVersion when run manually because this Test is calling https://ci.inria.fr/pharo/job/Pharo-6.0/lastSuccessfulBuild/api/xml?xpath=/… currently returning an error.

1 0

[Pharo 7.0-dev] Build #1168: Disabling OSX tests until the slave resucitates
by ci-pharo-ci-jenkins2＠inria.fr Aug. 14, 2018

Aug. 14, 2018

There is a new Pharo build available! The status of the build #1168 was: FAILURE. The Pull Request #1687 was integrated: "Disabling OSX tests until the slave resucitates" Pull request url: https://github.com/pharo-project/pharo/pull/1687 Issue Url: https://pharo.fogbugz.com/f/cases/Disabling Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Is Jenkins OK?
by Alistair Grant Aug. 14, 2018

Aug. 14, 2018

I have a PR that has been running for over 13 hours... https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen… (if there's something I can do about this myself instead of annoying the list, please let me know) Thanks, Alistair

4 5

Aug. 14, 2018

Hi In pillar we needed variable lookup with Mustache so we used a https://github.com/Ducasse/Containers-PropertyEnvironment <https://github.com/Ducasse/Containers-PropertyEnvironment> instead of a simple dictionary. Notice that https://github.com/Ducasse/Containers-PropertyEnvironment <https://github.com/Ducasse/Containers-PropertyEnvironment> has 100% test coverage. 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

2 2

CfP: Next Generation Programming Paradigms and Systems (NGPS at SAC 2019)
by Nick Papoylias Aug. 13, 2018

Aug. 13, 2018

------------------------------------------------------------------------------- Next Generation Programming Paradigms and Systems (NGPS 2019) Track of the 34th ACM/SIGAPP Symposium On Applied Computing Limassol, Cyprus https://ngps2019.github.io/ ------------------------------------------------------------------------------- AIMS AND TOPICS The complexity of modern software systems is continuously growing together with the communication capabilities and computational power of pervasive technology, embodied by a wide range of interacting heterogeneous smart devices. This new scenario is posing serious challenges to software development, which hardly keeps pace with this technological evolution. Sophisticated frameworks exposed through application programming interfaces, or directly integrated with mainstream programming languages provide partial solutions to support big data streaming and complex analytic; dynamic, autonomous, and collective coordination and adaptation capabilities; emergent behavior in cooperating systems; Internet of Things (IoT) systems development and maintenance; and employment of cloud platforms and parallel architectures, in particular heterogeneous ones. This calls for new abstractions, features, middlewares and tools able to reduce the time, effort, and cost of designing and developing the next generation software systems, improving performance, and ensuring reliability and security. To this aim, NGPS is seeking to advance the state-of-the-art and the state-of-the-practice of computational models and paradigms, formal techniques and software methods for easing software development and verification, and improving efficiency of complex modern systems. The specific topics of interest for the NGPS track include, but are not limited to, the following: - Integration of computational paradigms - Runtime verification and monitoring - Platforms for the Cloud - IoT systems - Secure and dependable software - Formal models and verification - Testing and debugging - System evaluation - Design, implementation and optimization of high-level programming languages - Middleware platforms - Scenarios, case studies and experience reports on innovative applications - High-level parallel programming - Distributed systems and concurrency - Development tools - Coordination models, specification, and technologies - Multi-agent systems, mobile agents, intelligent agents, and agent-based simulations - Models, frameworks and tools for Collective Adaptive Systems - Internet, Web, and pervasive computing systems - Self-organizing, self-adaptive, context-aware and nature-inspired systems - Security, trust and privacy management SUBMISSIONS Prospective papers should be submitted to the track in pdf format using the START submission system for regular and SRC papers available through the SAC 2019 home page. Submission of the same paper to multiple tracks is not allowed; all papers should represent original and previously unpublished works that are currently not under review in any conference or journal. Both basic and applied research papers are welcome. SAC 2019 will use double-blind reviewing; to facilitate this, author name(s) and institution(s) must be omitted, and references to authorsâ own related work should be in the third person. The format of the paper must adhere to the sig-alternate style. Full papers are limited to 8 pages, in camera-ready format, included in the registration fee. Authors have the option to include up to two (2) extra pages at additional fee of US$80 per page. Papers accepted as posters are limited to 3 pages, in camera-ready format, included in the registration fee. Authors have the option to include only one (1) extra page at additional fee of US$80. SRC abstracts are limited to 4 pages, in camera-ready format, included in the registration fee. No extra pages are allowed. Accepted papers will be published by ACM in the annual conference proceedings. Accepted posters will be published as extended abstracts in the same proceedings. Papers that fall short the above requirements are subjected to rejection. All papers must be submitted by September 10, 2018. For more information please visit the SAC 2019 home page. Paper registration is required, allowing the inclusion of the paper/poster in the conference proceedings. An author or a proxy attending SAC MUST present the paper: This is a requirement for the paper/poster to be included in the ACM/IEEE digital library. No-show of scheduled papers and posters will result in excluding them from the ACM/IEEE digital library. DEADLINES Sept 10, 2018 Submission of regular papers and SRC research abstracts Nov 10, 2018 Notification of paper acceptance/rejection Nov 10, 2018 Notification of SRC acceptance/rejection Nov 25, 2018 Camera-ready copies of accepted papers/SRC Dec 10, 2018 Author registration due date April 8-12, 2019 ACM SAC Conference TRACK CO-CHAIRS Davide Ancona, DIBRIS, University of Genova, IT Frederic Loulergue, SICCS, Northern Arizona University, USA Danilo Pianini, DISI, University of Bologna, IT Mirko Viroli, DISI, University of Bologna, IT PROGRAM COMMITTEE (to be completed) Mohamad Al Hajj Hassan, Huawei, DE Lorenzo Bettini, DISIA, University of Florence, IT HÃ©lÃ¨ne Coullon, IMT Atlantique, Inria, FR Ferruccio Damiani, DI, University of Torino, IT Simon Dobson, CS, University of St Andrews, UK Kento Emoto, IPL-Lab, Kyushu Institute of Technology, JP Erik Ernst, Google Inc., USA Lukas Esterle, ALICE, Aston University, UK FrÃ©dÃ©ric Gava, LACL, UniversitÃ© Paris-Est CrÃ©teil, FR Robert Hirschfeld, HPI, University of Potsdam, DE Jaakko JÃ¤rvi, II, University of Bergen, NO Einar Broch Johnsen, UiO, University of Oslo, NO Khaled Hamidouche AMD Research, USA Geoff Hamilton, School of Computing, Dublin City University, IE Hideya Iwasaki, The University of Electro-Communications, JP Doug Lea, CS, University of New York at Oswego Michele Loreti, DI, University of Camerino, IT Alberto Lluch Lafuente, DTU COMPUTE, Technical University of Denmark, DK Hidehiko Masuhara, PRG, Tokyo Institute of Technology, JP Virginia Niculescu, CS, Babes-Bolyai University of Cluj-Napoca, RO Nick Papoulias, University of La Rochelle, UMR LIENSs, CNRS, FR AntÃ³nio Ravara, DI FCT, New University of Lisbon, PT Barbara Re, SST, University of Camerino, IT Sophie Robert, LIFO, University of OrlÃ©ans Stefan Rudolph, OC, Augsburg University, DE Maurice ter Beek, FMT-ISTI, CNR, IT Martin Wirsing, SoSy-Lab, LMU Munich, D

1 0

Esteban's ChangeLog week of 6 August 2018
by estebanlm＠gmail.com Aug. 13, 2018

Aug. 13, 2018

Hello! This is my weekly ChangeLog, from 6 August 2018 to 12 August 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=6/8/2018&to=12/8/2018 ChangeLog ========= 7 August 2018: -------------- * I've been working on a new ODBC driver for Pharo, made on UFFI and Garage. Sadly, I cannot take the existing older ODBC driver as base because it was depending too much on old FFI structure. Also, it didn't have any test or example so it was hard to take as inspiration (too many differences to tacle). Anyway, the new ODBC driver will come soon(tm), in the mean time I needed to fix some issues on UnifiedFFI: * [case: 22287](https://pharo.fogbugz.com/f/cases/22287) * [case: 22300](https://pharo.fogbugz.com/f/cases/22300) This fixes some missing/incorrect parts on UFFI: first one adds a special handling for +size_t+ types (needed because they behave differently in different platforms/architectures). And the second fixes a problem when returning +enum+ values. cheers! Esteban

1 0