- Pharo-dev - lists.pharo.org

Directory structure on files.pharo.org
by stephan Sept. 14, 2017

Sept. 14, 2017

This looks like it is missing directories. On the other hand, perhaps exposing the build steps as directories might not be the best idea, as that is unlikely to remain stable. http://files.pharo.org/image/70/ Stephan

2 3

Bintray for Pharo7 images?
by Holger Freyther Sept. 14, 2017

Sept. 14, 2017

Hey, I keep on clicking on the "bintray" badges to get to a recent Pharo7 image but after looking at the Jenkinsfile I don't see the script being invoked and given the timestamp of "201706...." it seems no images were uploaded for a while? Should we remove the bintray badge or upload them again? Would there be any objection to link to http://files.pharo.org/get-files/70/pharo.zip from the README.md to get the latest image/sources/changes? cheers holger

2 1

Tricky Metaclass>>binding
by Denis Kudriashov Sept. 13, 2017

Sept. 13, 2017

I found interesting trick in system: the way how class side perform #binding message: Metaclass>>binding "return an association that can be used as the binding To share it between methods, reuse an existing one if possible" ^self methodDict ifEmpty: [nil -> self] ifNotEmpty: [:dict | dict anyOne classBinding] It leads to interesting behaviour of class without class side methods: NewClass class binding == NewClass class binding "==> false" Generally I discovered in the logic which decode class of method in last literal. Interesting that for instance side methods it is always represented by GlobalVariable. And for class side methods it is always general Association. Can we make this behaviour more consistent? And will it improve the system? (I thing about possible complications to bootstrap). As solution I would introduce new kind of LiteralVariable: ClassBinding with two subclasses InstanceSideBinding and ClassSideBinding. They will take place in last method literal. InstanceSideBinding will be used in Smalltalk dictionary for classes instead of GlobalVariable. And it will keep variable with class side binding. So the trick will be not needed anymore. So what do you think?

4 8

About Git support for windows
by Stephane Ducasse Sept. 13, 2017

Sept. 13, 2017

Hi all At ESUG we discussed with Esteban, martin mcClure, Dale and (many many others :), esteban designed a nice class file format. So that we will not have 2Gb of space on harddisc, problems with long method names and sluggish commits. He is waiting at Wien and is probably checking everything right now. It is a nice format because we will be able to use it to communicate by emails using it. So readable, compact and I like it :) Stef

12 28

Build #111
by Guillermo Polito Sept. 13, 2017

Sept. 13, 2017

Hi all, since the build #111 there is a new version of iceberg. I'll let Esteban get into the details of that. From what respects to me, this build fixes 9 failing tests: https://github.com/pharo-project/pharo/pull/267 The build has however one failing test that fails randomly: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… Kernel.Tests.Processes.SemaphoreTest.testMutualExclusion <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> Denis has proposed a solution for that, so we will have a green build back soon :) -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

6 7

argh, tests are failing!
by Guillermo Polito Sept. 13, 2017

Sept. 13, 2017

Hi all, Since a couple of builds we have consistently failing the following tests: - GT.EventRecorder.Tests.Core.GTEventRecorderTest.testDeliverNow2 <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> - GT.EventRecorder.Tests.Core.GTEventRecorderTest.testNotDeliveredDataShouldBeResent <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> - Kernel.Tests.Processes.MutexTest.testFailedCriticalSectionShouldUnblockWaitingOne <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> - ReleaseTests.Categorization.ProperMethodCategorizationTest.testHashMethodNeedsToBeInComparingProtocol <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> - ReleaseTests.Categorization.ProperMethodCategorizationTest.testHashMethodNeedsToBeInComparingProtocol <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> - ReleaseTests.Categorization.ProperMethodCategorizationTest.testHashMethodNeedsToBeInComparingProtocol <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> - ReleaseTests.Categorization.ProperMethodCategorizationTest.testHashMethodNeedsToBeInComparingProtocol <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> - ReleaseTests.Categorization.ProperMethodCategorizationTest.testHashMethodNeedsToBeInComparingProtocol <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> - ReleaseTests.Categorization.ProperMethodCategorizationTest.testHashMethodNeedsToBeInComparingProtocol <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> - ReleaseTests.Categorization.ProperMethodCategorizationTest.testHashMethodNeedsToBeInComparingProtocol <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> Green builds are the only hard metric to say if the build is healthy or not. - We should not integrate anything until the build is green again... Also, we spent with Pablo a lot of time to have a green build in all platforms... I'd like to spend my time in other fun stuff than the CI :/ -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

7 21

[OOPS @ SAC 2018] Extended submission deadline: Sept. 25
by Nick Papoylias Sept. 12, 2017

Sept. 12, 2017

************************************************** OOPS 2018 Call for Papers Object-Oriented Programming Languages and Systems http://oops.disi.unige.it/OOPS18 ************************************************** Technical Track at the 33rd ACM Symposium on Applied Computing, SAC 2018 https://www.sigapp.org/sac/sac2018/index.html April 9 - 13, 2018 Pau, France - Important Dates Submission of regular papers and SRC abstracts *September 25, 2017 (extended deadline)* Paper and SRC notifications November 10, 2017 Paper and SRC camera-ready copies November 25, 2017 Author registration December 10, 2017 SAC 2018 April 9 - 13, 2018 - Track Chair Davide Ancona (davide.ancona(a)unige.it) DIBRIS, University of Genova, Italy - SAC 2018 For the past thirty two years, the ACM Symposium on Applied Computing (SAC) has been a primary gathering forum for applied computer scientists, computer engineers, software engineers, and application developers from around the world. SAC 2018 is sponsored by the ACM Special Interest Group on Applied Computing (SIGAPP) and is hosted by hosted by UniversitÃ© de Pau et des Pays de l'Adour (UPPA), Pau, France. - Call For Student Research Abstracts Graduate students seeking feedback from the scientific community on their research ideas are invited to submit original abstracts of their research work in areas of experimental computing and application development related to SAC 2018 Tracks. The Student Research Competition (SRC) Program is designed to provide graduate students the opportunity to meet and exchange ideas with researchers and practitioners in their areas of interest. - OOPS Track: Aims and Topics Object-oriented programming (OOP) has become the mainstream programming paradigm for developing complex software systems in most application domains. However, existing OO languages and platforms need to evolve to meet the continuous demand for new abstractions, features, and tools able to reduce the time, effort, and cost of creating object-oriented software systems, and improving their performance, quality and usability. To this aim, OOPS is seeking for research advances bringing benefits in all those typical aspects of software development, such as modeling, prototyping, design, implementation, concurrency and distribution, code generation, analysis, verification, testing, debugging, evaluation, deployment, maintenance, reuse, and software evolution and adaptation. The specific topics of interest for the OOPS track include, but are not limited to, the following: * Aspects and components * Code generation, and optimization, just-in-time compilation * Context-oriented programming * Databases and persistence * Distribution and concurrency * Dynamic and scripting languages * Evaluation * Feature Oriented Software Development and Programming * Formal verification * Internet of Things technology and programming * Integration with other paradigms * Interoperability, versioning and software evolution and adaptation * Language design and implementation * Modular and generic programming * Reflection, meta-programming * Runtime verification and monitoring * Safe, secure and dependable software * Static analysis * Testing and debugging * Type systems and type inference * Virtual machines OOPS offers a great opportunity to the OOP community to gain visibility, and to exploit the inter-disciplinary nature of SAC. - Submission Instructions 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 2018 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 2018 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 (http://www.acm.org/sigs/publications/proceedings-templates) 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 2 pages, in camera-ready format, included in the registration fee. No extra pages are allowed. Papers that fall short the above requirements are subjected to rejection. All papers must be submitted by September 15, 2017. For more information please visit the SAC 2018 home page. - Proceedings Accepted papers will be published by ACM in the annual conference proceedings. Accepted posters will be published as extended abstracts in the same proceedings. Paper registration is required, allowing the inclusion of the papers and posters in the conference proceedings. An author or a proxy attending SAC MUST present the paper. This is a requirement for all accepted papers, posters, and invited SRC submissions to be included in the ACM digital library. No-show of scheduled papers, posters, and student research abstracts will result in excluding them from the ACM digital library. Student registration is only intended to encourage student attendance and does not cover inclusion of papers/posters in the conference proceedings. Finally, following the tradition of the past OOPS editions (http://oops.disi.unige.it/special-issues) depending on the quality and the overall number of accepted papers, authors of selected papers will be invited to submit an extended version for a journal special issue ( http://oops.disi.unige.it/special-issues) after the conference.

1 0

Iceberg causes 64 bit VM core dump on Ubuntu
by Alistair Grant Sept. 11, 2017

Sept. 11, 2017

Hi Everyone, I thought I'd have another go at moving to 64 bits after Esteban commented that he's regularly using it now. However the following sequence reliably crashses the 64 bit VM (Ubuntu 16.04): 1. Execute: Iceberg enableMetacelloIntegration: true. Metacello new repository: 'github://akgrant43/FileAttributes/src'; baseline: 'FileAttributes'; load. 2. Open Iceberg 3. Select the FileAttributes repository 4. Show History... 5. Select master 6. Click on the top commit $ ../vm64/pharo-ui Pharo7.0-64bit-f65af60.image pharo: malloc.c:2394: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed. ../vm64/pharo-ui: line 11: 13199 Aborted (core dumped) "$DIR"/"pharo-vm/pharo" "$@" I also get crashes from other operations, e.g. iceRepository pull. The result is that for me 64 bits isn't usable yet. If this isn't already known I'll open a fogbugz issue. Build info: Pharo 7.0 Build information: alpha.build.109.sha.f65af6011ac4ff31af37c8d8567bf8a5fdad8dca but has happened with other builds as well. $ ../vm64/pharo --version 5.0-201708271955 Sun Aug 27 20:00:58 UTC 2017 gcc 4.6.3 [Production Spur 64-bit VM] CoInterpreter VMMaker.oscog-eem.2265 uuid: 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2262 uuid: 8b531242-de02-48aa-b418-8d2dde0bec6c Aug 27 2017 VM: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Sun Aug 27 21:55:26 2017 +0200 $ Plugins: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Linux testing-gce-7a972a8a-3d5e-4b8d-94e0-6252bfe9a477 3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 16:47:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux plugin path: /home/alistair/pharo7/vm64/pharo-vm/lib/pharo/5.0-201708271955 [default: /home/alistair/pharo7/vm64/pharo-vm/lib/pharo/5.0-201708271955/] Thanks very much, Alistair

4 13

Can Realm (DB) and Pharo play together (or can we have a Pharo Realm Object Server to ROS) ?
by CÃ©drick BÃ©ler Sept. 11, 2017

Sept. 11, 2017

Hello all, Iâve spent some time in the summer in what I call my quest to the ultimate and easy and fun architecture to prototype some personal administration apps and have fun :-) Iâll share some experience and wonder if there are alternative in Pharo. I want app that are mobile firsts, then manageable with a computer (for more complex administrative tasks). I want them reactive (I especially like reactive data driven application like meteor.js), ubiquitous around my devices and not always connected (offline-first - this is very important if not the first objective). Ok, so I was lurking around looking for server and mobile distributed databases and I finally found Realm (https://realm.io/products/realm-mobile-platform/ <https://realm.io/products/realm-mobile-platform/>) which is a cool architecture plenty of promises, well documented, lots of tutorials... The architecture is composed of 2 products: - Realm DB [1] that runs on mobile device - multiplatform - fully open-source - performant - an object DB with some limitation though - Realm Object Server (ROS) [2] - provide two-way data sync simple and easy - BUT proprietary even if free for developers â¦ the entry point for serious developments (in particular access programmatically to the server) is very expensive ! 1500$mo ! The developer edition with is free is already quite outstanding to me. Looks at this demo page on GitHub [3] ! Butâ¦ without any control to the ROS, I find ROS quite limited finally. I may then use the DB part, ROS free for what really need sync reactivity between devices or between group of people (like a black board), but store all less transient information to WhateverNoSQLDB probably in REST. Anyway I want to share that with you because it rings a smalltalk bell in my headâ¦ itâs about object data, live feeling, and I want to use Pharo on the server :) Maybe some people here have thought of an alternative ROS in Pharo or Gemstone ? Any ideas or remarks ? I was aware of sebastian Flow living full-stack framework attempt but donât know more. TIA CÃ©drick NB: Pharo looks more and more great ! Congratulations guys for you job ! I hope ESUG was nice. Iâve just tried Telepharo on Pharo 6 (64 bit). Really great work too... It works like a charm, out of the box on low cost dedicated ubuntu servers [4] => 10â¬mo Pharo 64 tinyBenchmarks is 2,75 times slower than on my Mac mini Core i5 2,5GHz from 2012 with SSD (I guess itâs not that bad and usable for personal applications servers). I think itâ about 3 times faster than on a raspberry Pi. Mac mini (32 bit version): '1329870129 bytecodes/sec; 108576799 sends/secâ Dedibox Low Cost server (64 bit version)â '595695171 bytecodes/sec; 39441333 sends/sec' NB2: to download/install Pharo from command line, on the web site instructions, it seems it lacks the trailing slash. I had to add it. curl get.pharo.org/64/ | bash [1] https://realm.io/products/realm-mobile-database/ <https://realm.io/products/realm-mobile-database/> [2] https://realm.io/products/realm-mobile-platform/ <https://realm.io/products/realm-mobile-platform/> [3] https://github.com/realm-demos <https://github.com/realm-demos> [4] https://www.online.net/fr/serveur-dedie/dedibox-sc <https://www.online.net/fr/serveur-dedie/dedibox-sc>

5 5

poor state of fuel
by Norbert Hartl Sept. 11, 2017

Sept. 11, 2017

I'm migrating most of my projects to pharo 6.1 at the moment. I come from pharo 4, I skipped pharo 5. I use 64 bit which removes a lot of stuff that does not need to be installed and makes deployment better. That really feels much better. I use jenkins and there if a test fails a fuel dump is written to disk. The jenkins server is ubuntu linux with the vm of the opensuse build. My laptop has Mac OS and cannot read back those fuel dumps. I use the same image version on jenkins and my laptop. Both are 64bit. I asked that on discord and there was a mentioning that not only the 64 bit fuel has problems. So I wanted to ask what is the state of fuel right now. I consider fuel one of the core technologies in pharo and it is sad if it just stops working. Any feedback is highly appreciated, Norbert

6 14