July 2018 - Pharo-users - lists.pharo.org

Pharo7, consistent image freeze/deadlock on snapshotAndQuit
by Johan Brichau Oct. 7, 2018

Oct. 7, 2018

Hi, I ran into a freeze issue when trying to save and/or quit an image after loading Seaside3 and Zinc (not an infrequent combination :) The cause seems to be that terminating processes in a `shutDown` handler (called on image shutdown / snapshot) leads to a deadlock (somewhere). Both Comet and Zinc will send #terminate to a process when an image is quit or saved. If I disable one of those, the deadlock does not occur. I managed to reconstruct the issue with a simple example, attached. The attached Freeze class creates two processes (that loop with a Delay>>wait inside) in the `startUp` method (on image start). These processes are terminated by the shutdown method (called on image quit/save). However, when you try to quit and/or save the image, you will experience an image freeze. Iâm not familiar with the process scheduler, or anything else in this contextâ¦ so help would be appreciated while I try to dive further into it :) To reproduce: just file in the attached file in a Pharo7 image and try to quit. For reference, System Reporter output for my configuration. Any ideas? Cheers Johan Image ----- /Users/jbrichau/Pharo/images/Pharo 7.0 - 64bit (development version)/Pharo 7.0 - 64bit (development version).image Pharo7.0alpha Build information: Pharo-7.0+alpha.build.1131.sha.a46bfaef44ba209888c92fa0e3bd3a5e04a38c5d (64 Bit) Unnamed Virtual Machine --------------- /Users/jbrichau/Pharo/vms/70-x64/Pharo.app/Contents/MacOS/Pharo CoInterpreter VMMaker.oscog-eem.2401 uuid: 29232e0e-c9e3-41d8-ae75-519db862e02c Jun 28 2018 StackToRegisterMappingCogit VMMaker.oscog-eem.2401 uuid: 29232e0e-c9e3-41d8-ae75-519db862e02c Jun 28 2018 VM: 201806281256 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Thu Jun 28 14:56:30 2018 CommitHash: a8a1dc1 Plugins: 201806281256 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Mac OS X built on Jun 28 2018 13:07:33 UTC Compiler: 4.2.1 Compatible Apple LLVM 7.3.0 (clang-703.0.31) VMMaker versionString VM: 201806281256 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Thu Jun 28 14:56:30 2018 CommitHash: a8a1dc1 Plugins: 201806281256 https://github.com/OpenSmalltalk/opensmalltalk-vm.git CoInterpreter VMMaker.oscog-eem.2401 uuid: 29232e0e-c9e3-41d8-ae75-519db862e02c Jun 28 2018 StackToRegisterMappingCogit VMMaker.oscog-eem.2401 uuid: 29232e0e-c9e3-41d8-ae75-519db862e02c Jun 28 2018

2 2

Pharo 6 snap package
by Alistair Grant Sept. 20, 2018

Sept. 20, 2018

Hi Everyone, I've updated the Pharo 6 snap package for Ubuntu. The major advantages of using the snap package are: - No need to install all the 32 bit dependencies on a 64 bit system, they're all contained and isolated within the snap package. - Automagically distinguish between 32 bit and 64 bit images and run the appropriate VM (as with the ZeroConf package, the 64 bit VM still needs more testing). To get Pharo up and running on Ubuntu 16.04 or later: # Install Pharo $ sudo snap install --candidate pharo --classic # If your system isn't configured for threaded heartbeat: $ sudo pharo.config # Download the latest Pharo 6 image $ pharo.getimage # Go... $ pharo.ui Pharo.image # or: $ pharo Pharo.image eval 4+3 To get a list of available commands: $ snap info pharo If you're on Debian or Ubuntu 14.04 you'll need to install snapd, see https://snapcraft.io/docs/core/install The VM is the threaded heartbeat, dated 201705310241. The installation flags are: --candidate - The edge and beta channels are for development versions. It progresses to candidate and then stable. --classic - Snap packages are normally sandboxed for security reasons. Since Pharo is a development environment in which we want to be able to run any executable, or load any library, it is installed with access to the entire system (as the running user). Why use snap packages? - They include all dependencies. In particular, for the 32 bit versions, this means that it isn't necessary to install all the 32 bit architecture and associated dependencies. - Including dependencies means that there shouldn't be any problems with incompatible library versions when upgrading. Why not use snap packages? - It's a relatively new technology, with a number of rough edges. - There may still be issues with its sandboxing that I haven't discovered yet. - Because the package uses classic confinement, it isn't cross-distribution in practice (unfortunately). Please let me know of any other advantages or disadvantages you think should be listed here. If you don't trust me to configure your system correctly (which requires sudo): - All the scripts that make up the sub-commands are visible, e.g. pharo.config can be viewed at /snap/pharo/current/usr/bin/CONFIG The packaging code is at: https://github.com/akgrant43/pharo-snap Cheers, Alistair

7 12

Retina support in Pharo
by markm Sept. 20, 2018

Sept. 20, 2018

Hi Is it possible to get Pharo (4 or 5) to run with retina support on OS X? I have tried searching for some answers, but alas could only find a handful of posts from a few years back. Any help much appreciated! Mark -- View this message in context: http://forum.world.st/Retina-support-in-Pharo-tp4895245.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

10 14

Yet another Pharo in docker
by Herby VojÄÃk Sept. 18, 2018

Sept. 18, 2018

https://hub.docker.com/r/herbysk/pharo/

8 16

Tracing Method Calls
by Arturo Zambrano Aug. 29, 2018

Aug. 29, 2018

Hi all, I have a piece of undocumented software that I need understand ... One thing I would like to do is to have a complete trace of method calls (receivers, parameters) for certain scenarios. As an "aspects"guy, my first idea was to use Phantom, but it seems not active anymore. Could someone please point me to some tools that I could use for this? (using Pharo 6, 6.1 or 7) Thanks in advance Cheers Arturo

3 4

Jupyter notebooks / Dynabook / JupyterTalk
by H. Hirzel Aug. 29, 2018

Aug. 29, 2018

Hello What is the status of this project? https://github.com/jmari/JupyterTalk Hannes

9 48

separate native window of same Pharo image
by Peter UhnÃ¡k Aug. 17, 2018

Aug. 17, 2018

Hi, did anyone play around with launching a separate native window for Pharo? E.g. I have normal window in which Pharo is, and then I open a separate native window that shows just e.g. Transcript. I know that there are some projects like OSWindow-SDL and OSWindows-UI (using WinAPI), but both of them are aimed at opening windows with non-pharo content, which is not what I want. Any pointers? Thanks, Peter

4 7

Pharo 7 file streams guideline
by Pavel Krivanek Aug. 11, 2018

Aug. 11, 2018

Hello, I've prepared a draft of a short document that should help you with the transition to the "new" file streams API in Pharo 7. https://github.com/pavel-krivanek/pharoMaterials/blob/master/Filestreams.MD Pull requests are welcome. Cheers, -- Pavel

11 25

Morph reacting to Window being closed
by Peter UhnÃ¡k Aug. 7, 2018

Aug. 7, 2018

Hi, how can a Morph react to its parent window being closed? E.g. Morph subclass: #MyMorph. MyMorph new openInWindow how can MyMorph cleanup itself on window close? I thought Morph>>delete would do the trick, but it is not being called. Thanks, Peter

3 3

Pillar Book Tester
by Quentin DUCASSE (CI_2020) Aug. 5, 2018

Aug. 5, 2018

Hello everyone! I am currently in an internship within the RMoD team and would like to present my work. My internship subject was the following: âHow to test documents (books, slides) written in Pillar?â. Let me first introduce Pillar then what I managed to implement and what is left to do. -What is Pillar? Pillar is a markup syntax and associated tools to write and generate documentation, books, slide-based presentations or websites. Pillar syntax is similar to Markdownâs one but its emphasis is stressed on publishing to different formats/languages (Markdown, html, LateX, pdf). -What does it mean to âtest a bookâ? -- Display code within the book Pillar syntax allows you to write codeblocks, showing a part of code. The inside of a codeblock allows one to display any part of code you might want to. For example: [[[ YourClass >> yourMethod ^ âblaâ ]]] This codeblock presents a method definition, the other two possible codeblocks are the following: Class definition [[[ Object subclass: #YourClass instanceVariableNames: '' classVariableNames: '' package: YourPackage' ]]] Example [[[ 1+1 >>> 2 ]]] -- How to test it? The use of â>>>â and parameters in the codeblock will help us to test the code within it. The BookTester will turn examples into tests. Testing examples: [[[testcase=true 3+4 becomes self assert: (3+4) equals: 7 >>>7 ]]] Testing methodDefinitions and classDefinitions: Testing method or class definitions resumes is the same as testing if the compilation of the method does not raise any error. It can help make sure your book is up to date with the latest Pharo version. Those tests are done the same way as testing an example: stating methodDefinition=true or classDefinition=true as code block parameters will make them elible for tests. Now, we are adding more features to code block or Pillar to help book writers. -Additional Features In Pillar, several annotations can be used for different purposes like including columns/tables/citations/figures/linksâ¦ -- Loading code: loader ${loader:account=QDucasse|project=TestBook|tag=Chapter1}$ allows you to load the github project as it was in the commit tagged Chapter1. This will help you test every chapter of your code with its current progression and also allow you to test the objects you are defining in your book. - Executing Tests: run ${run:testClass=YourClassTest}$ runs the test defined in the class testClass. And of course this testClass can be Other annotations have been added to help you write your book: - Display a class definition: showClass: ${showClass:className=YourClass}$ displays a codeblock with the class definition within it This helps you quickly include a class definition you want to display in your book. Combined with the loader it means that the code can be the source of your book. - Display a method definition: showMethod: ${showMethod:className=YourClass|methodName=yourMethod}$ will display a codeblock with the method definition within it This helps you quickly include a method definition you want to display in your book. - Screenshot: ${showMethod:packageName=yourPackage|className=YourClass|methodName=yourMethod|caption|width|label}$ saves a screenshot of a Calypso browser open at the selected package, class and method and includes it in both your book (using the designated Pillar figure reference) and the figures subfolder in the pillar book folder (saved as PNG). -Future objectives One of the future improvements would be to make everyone able to write examples and test them in the comments of method definitions. It is already partially possible â3+4 >>> 7â will be highlighted differently and if printed will display â7->7â. However, an automation or UI improvement would be nice. I hope this gave you the will to write something you had in mind. Are there any books you want to try the tools on? Feel free to ask ! Quentin Ducasse

2 1