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

[Pharo 8.0] Build #616: Go back to version Iceberg 1.6.1
by ci-pharo-ci-jenkins2＠inria.fr Aug. 12, 2019

Aug. 12, 2019

There is a new Pharo build available! The status of the build #616 was: FAILURE. The Pull Request #4284 was integrated: "Go back to version Iceberg 1.6.1" Pull request url: https://github.com/pharo-project/pharo/pull/4284 Issue Url: https://github.com/pharo-project/pharo/issues/fix/reverting Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #615: 4017-tryning-to-add-an-ivar-to-UndefinedObject-crashes-the-VM
by ci-pharo-ci-jenkins2＠inria.fr Aug. 12, 2019

Aug. 12, 2019

There is a new Pharo build available! The status of the build #615 was: SUCCESS. The Pull Request #4279 was integrated: "4017-tryning-to-add-an-ivar-to-UndefinedObject-crashes-the-VM" Pull request url: https://github.com/pharo-project/pharo/pull/4279 Issue Url: https://github.com/pharo-project/pharo/issues/4017 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #614: 4223-Lint-clean-RubCharacterBlockScanner-cr
by ci-pharo-ci-jenkins2＠inria.fr Aug. 12, 2019

Aug. 12, 2019

There is a new Pharo build available! The status of the build #614 was: SUCCESS. The Pull Request #4224 was integrated: "4223-Lint-clean-RubCharacterBlockScanner-cr" Pull request url: https://github.com/pharo-project/pharo/pull/4224 Issue Url: https://github.com/pharo-project/pharo/issues/4223 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #613: Simplify Socket>>waitForAcceptFor:
by ci-pharo-ci-jenkins2＠inria.fr Aug. 12, 2019

Aug. 12, 2019

There is a new Pharo build available! The status of the build #613 was: FAILURE. The Pull Request #4190 was integrated: "Simplify Socket>>waitForAcceptFor: " Pull request url: https://github.com/pharo-project/pharo/pull/4190 Issue Url: https://github.com/pharo-project/pharo/issues/Socket_waitForAcceptFor_ Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #612: 4229-Lint-clean-BehaviorallInstVarNames
by ci-pharo-ci-jenkins2＠inria.fr Aug. 12, 2019

Aug. 12, 2019

There is a new Pharo build available! The status of the build #612 was: SUCCESS. The Pull Request #4231 was integrated: "4229-Lint-clean-BehaviorallInstVarNames" Pull request url: https://github.com/pharo-project/pharo/pull/4231 Issue Url: https://github.com/pharo-project/pharo/issues/4229 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

An old but insightful critique of Eric Raymondâs The Cathedral and the Bazaar by Nikolai Bezroukov
by Eliot Miranda Aug. 10, 2019

Aug. 10, 2019

This may be old news. It was news to me and apart from being an excellent critique of tCatB it also includes many truths about large software systems and if open source communities in general. If you havenât read it already may I suggest it is well worth your time reading. https://firstmonday.org/article/view/708/618/ _,,,^..^,,,_ (phone)

1 0

(7.0.3) writing a large(?) string to stdout is mangled
by Dale Henrichs Aug. 10, 2019

Aug. 10, 2019

I've run into an issue with pharo 7.0.3 where writing a string that contains embedded crs or lfs to stdout causes the output to be corrupted in odd ways. I have provided the details and a reproducible test case up on github[1]. Stef suggested I post the issue here as well ... Dale [1] https://github.com/pharo-project/pharo/issues/4266

1 0

[Pharo 8.0] Build #611: Zinc-Character-Encoding-test-cases-should-end-with-Test
by ci-pharo-ci-jenkins2＠inria.fr Aug. 10, 2019

Aug. 10, 2019

There is a new Pharo build available! The status of the build #611 was: FAILURE. The Pull Request #4267 was integrated: "Zinc-Character-Encoding-test-cases-should-end-with-Test" Pull request url: https://github.com/pharo-project/pharo/pull/4267 Issue Url: https://github.com/pharo-project/pharo/issues/Zinc Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #610: Remove-duplicated-method-in-TraitedClass
by ci-pharo-ci-jenkins2＠inria.fr Aug. 9, 2019

Aug. 9, 2019

There is a new Pharo build available! The status of the build #610 was: FAILURE. The Pull Request #4245 was integrated: "Remove-duplicated-method-in-TraitedClass" Pull request url: https://github.com/pharo-project/pharo/pull/4245 Issue Url: https://github.com/pharo-project/pharo/issues/Remove Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #609: ReTestClassNameShouldEndWithTest-should-also-accept-TestCase
by ci-pharo-ci-jenkins2＠inria.fr Aug. 9, 2019

Aug. 9, 2019

There is a new Pharo build available! The status of the build #609 was: FAILURE. The Pull Request #4218 was integrated: "ReTestClassNameShouldEndWithTest-should-also-accept-TestCase" Pull request url: https://github.com/pharo-project/pharo/pull/4218 Issue Url: https://github.com/pharo-project/pharo/issues/ReTestClassNameShouldEndWithT… Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #608: Repackage PositionableStream class >> with:do:
by ci-pharo-ci-jenkins2＠inria.fr Aug. 9, 2019

Aug. 9, 2019

There is a new Pharo build available! The status of the build #608 was: SUCCESS. The Pull Request #4247 was integrated: "Repackage PositionableStream class >> with:do: " Pull request url: https://github.com/pharo-project/pharo/pull/4247 Issue Url: https://github.com/pharo-project/pharo/issues/PositionableStream_class_with… Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #607: Exposing icon from the worldState with a form as argument.
by ci-pharo-ci-jenkins2＠inria.fr Aug. 9, 2019

Aug. 9, 2019

There is a new Pharo build available! The status of the build #607 was: FAILURE. The Pull Request #4249 was integrated: "Exposing icon from the worldState with a form as argument." Pull request url: https://github.com/pharo-project/pharo/pull/4249 Issue Url: https://github.com/pharo-project/pharo/issues/fix/icontests Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #606: Repackage PositionableStream class >> with:do:
by ci-pharo-ci-jenkins2＠inria.fr Aug. 9, 2019

Aug. 9, 2019

There is a new Pharo build available! The status of the build #606 was: FAILURE. The Pull Request #4247 was integrated: "Repackage PositionableStream class >> with:do: " Pull request url: https://github.com/pharo-project/pharo/pull/4247 Issue Url: https://github.com/pharo-project/pharo/issues/PositionableStream_class_with… Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #605: Cleaning class names, comments, method formatting of Spec2-PolyWidgets
by ci-pharo-ci-jenkins2＠inria.fr Aug. 9, 2019

Aug. 9, 2019

There is a new Pharo build available! The status of the build #605 was: FAILURE. The Pull Request #4257 was integrated: "Cleaning class names, comments, method formatting of Spec2-PolyWidgets" Pull request url: https://github.com/pharo-project/pharo/pull/4257 Issue Url: https://github.com/pharo-project/pharo/issues/4250 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Call for Papers, The Programming Journal, Volume 4, Issue 3
by Fabio Niephaus Aug. 8, 2019

Aug. 8, 2019

======================================================================== The Programming Journal The Art, Science, and Engineering of Programming Call for Papers for Volume 4, Issue 3 http://programming-journal.org/cfp/ Follow us on Twitter: @programmingconf ======================================================================== The Art, Science, and Engineering of Programming was created with the goal of placing the wonderful art of programming on the map of scholarly works. Many academic journals and conferences exist that publish research related to programming, starting with programming languages, software engineering, and expanding to the whole Computer Science field. Yet, many of us feel that, as the field of Computer Science expanded, programming, in itself, has been neglected to a secondary role not worthy of scholarly attention. That is a serious gap, as much of the progress in Computer Science lies on the basis of computer programs, the people who write them, and the concepts and tools available to them to express computational tasks. The Art, Science, and Engineering of Programming aims at closing this gap by focusing primarily on programming: the art itself (programming styles, pearls, models, languages), the emerging science of understanding what works and what doesnât work in general and in specific contexts, as well as more established engineering and mathematical perspectives. We solicit papers describing work from one of the following perspectives: Art: knowledge and technical skills acquired through practice and personal experiences. Examples include libraries, frameworks, languages, APIs, programming models and styles, programming pearls, and essays about programming. Science (Theoretical): knowledge and technical skills acquired through mathematical formalisms. Examples include formal programming models and proofs. Science (Empirical): knowledge and technical skills acquired through experiments and systematic observations. Examples include user studies and programming-related data mining. Engineering: knowledge and technical skills acquired through designing and building large systems and through calculated application of principles in building those systems. Examples include measurements of artifactsâ properties, development processes and tools, and quality assurance methods. Independent of the type of work, the journal accepts submissions covering several areas of expertise, including but not limited to: - General-purpose programming - Data mining and machine learning programming, and for programming - Database programming - Distributed systems programming - Graphics and GPU programming - Interpreters, virtual machines, and compilers - Metaprogramming and reflection - Model-based development - Modularity and separation of concerns - Parallel and multi-core programming - Program verification - Programming education - Programming environments - Security programming - Social coding - Testing and debugging - User interface programming - Visual and live programming All details, including the selection process are described on http://programming-journal.org/cfp/ Details on the submission processed are available at http://programming-journal.org/submission/ Authors of accepted papers will be invited to present at the <Programming>â20 conference in Porto, Portugal from March 23-26: https://2020.programming-conference.org/ ## Upcoming Deadlines We solicit submissions for the following upcoming deadlines: Submission: October 1 First notification: December 1 Revised submission: January 1 Final notification: January 7 Camera-ready: January 15 ## Standing Review Committee Volume 4 Christophe Scholliers, Ghent University Coen De Roover, Vrije Universiteit Brussel Craig Anslow, Victoria University of Wellington, New Zealand Didier Verna, EPITA / LRDE, France Diego Garbervetsky, University of Buenos Aires Edd Barrett, King's College London Erik Ernst, Google Felienne Hermans, Leiden University Francisco Sant'Anna, Rio de Janeiro State University Friedrich Steimann, University of Hagen Gordana Rakic, University of Novi Sad Guido Salvaneschi, TU Darmstadt Hidehiko Masuhara, Tokyo Institute of Technology Jeremy Gibbons, University of Oxford Jonathan Edwards, US Jun Kato, AIST, Japan Luke Church, University of Cambridge Matthew Flatt, University of Utah Michael L. Van De Vanter, Cal Poly San Luis Obispo NicolÃ¡s Cardozo, Universidad de los Andes, Colombia Stephen Kell, University of Kent ## Editors Stefan Marr (Editor Volume 4), University of Kent Cristina V. Lopes (Editor-in-Chief), University of California, Irvine

1 0

[Pharo 8.0] Build #604: Fix allocation tests
by ci-pharo-ci-jenkins2＠inria.fr Aug. 8, 2019

Aug. 8, 2019

There is a new Pharo build available! The status of the build #604 was: SUCCESS. The Pull Request #4230 was integrated: "Fix allocation tests" Pull request url: https://github.com/pharo-project/pharo/pull/4230 Issue Url: https://github.com/pharo-project/pharo/issues/fix/allocationTests Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #603: Fix word layouts and friends
by ci-pharo-ci-jenkins2＠inria.fr Aug. 8, 2019

Aug. 8, 2019

There is a new Pharo build available! The status of the build #603 was: SUCCESS. The Pull Request #4243 was integrated: "Fix word layouts and friends" Pull request url: https://github.com/pharo-project/pharo/pull/4243 Issue Url: https://github.com/pharo-project/pharo/issues/fix/wordlayouts Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #601: 4214-Code-Completion-DNU-on-visitAssignmentNode
by ci-pharo-ci-jenkins2＠inria.fr Aug. 6, 2019

Aug. 6, 2019

There is a new Pharo build available! The status of the build #601 was: FAILURE. The Pull Request #4215 was integrated: "4214-Code-Completion-DNU-on-visitAssignmentNode" Pull request url: https://github.com/pharo-project/pharo/pull/4215 Issue Url: https://github.com/pharo-project/pharo/issues/4214 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Iceberg and package renamings
by Torsten Bergmann Aug. 6, 2019

Aug. 6, 2019

Hi, usually when contributing I download a fresh Pharo 8 image (built by CI) using either Launcher or ZeroConf and use the Iceberg "repair" functionality to connect to / checkout the existing local clone of the repo with the Pharo 8 branch. This way I usually easily come easily to the "up to date" state and can start own modifications. But this time I used an older Pharo 8 image. So I pulled from upstream, pushed to my origin (forked git repo) and updated an already existing image also using the "repair" functionality. The changes where assembled and loaded. This way I also got into the "up to date" state for this image. But as one of the last changes done was a package renaming of "ReleaseTest" into "Release-Tests" this was reflected on the "src" folder on disk but not in the image itself. So unfortunately - the git repo was already having a "Release-Tests" folder in synch with the upstream - the local "up to date" image stayed with the old "ReleaseTests" package name as it was updated and not freshly bootstrapped from Baselines and with this out of synch. See attached screenshot. So I guess Iceberg's updating can not yet properly handle package renamings, maybe this is a known bug / not yet implemented feature - or something that is not easy to fix due to the renaming. Is this known? Could it be handled in the future? Just want to mention this as this could be a source of further problems when contributors update their image instead of using a new CI built one as they may hit such a renamed package. Bye T.

1 0

[Pharo 8.0] Build #600: Remove-shadow-variables
by ci-pharo-ci-jenkins2＠inria.fr Aug. 6, 2019

Aug. 6, 2019

There is a new Pharo build available! The status of the build #600 was: FAILURE. The Pull Request #4193 was integrated: "Remove-shadow-variables" Pull request url: https://github.com/pharo-project/pharo/pull/4193 Issue Url: https://github.com/pharo-project/pharo/issues/Remove Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #599: 4206-Cleaning-arcTan-comment-and-adding-executable-comments
by ci-pharo-ci-jenkins2＠inria.fr Aug. 6, 2019

Aug. 6, 2019

There is a new Pharo build available! The status of the build #599 was: SUCCESS. The Pull Request #4207 was integrated: "4206-Cleaning-arcTan-comment-and-adding-executable-comments" Pull request url: https://github.com/pharo-project/pharo/pull/4207 Issue Url: https://github.com/pharo-project/pharo/issues/4206 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #598: Move method to make it work
by ci-pharo-ci-jenkins2＠inria.fr Aug. 6, 2019

Aug. 6, 2019

There is a new Pharo build available! The status of the build #598 was: FAILURE. The Pull Request #4202 was integrated: "Move method to make it work" Pull request url: https://github.com/pharo-project/pharo/pull/4202 Issue Url: https://github.com/pharo-project/pharo/issues/fix/udptest Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #597: Fixing the dependency analysis of BaselineOfIDE
by ci-pharo-ci-jenkins2＠inria.fr Aug. 6, 2019

Aug. 6, 2019

There is a new Pharo build available! The status of the build #597 was: SUCCESS. The Pull Request #4200 was integrated: "Fixing the dependency analysis of BaselineOfIDE" Pull request url: https://github.com/pharo-project/pharo/pull/4200 Issue Url: https://github.com/pharo-project/pharo/issues/fixing Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[FileReference] why this class don't provide a method isAHiddenFile ?
by ClÃ©ment Dutriez Aug. 6, 2019

Aug. 6, 2019

-- Dutriez ClÃ©ment dutriezcle(a)gmail.com 0605199489 [image: www.linkedin.com/in/clÃ©ment-dutriez-407275173] <http://www.linkedin.com/in/clÃ©ment-dutriez-407275173>

4 9

[ANN] Pharo Launcher 1.9.1 released
by Christophe Demarey Aug. 6, 2019

Aug. 6, 2019

Hi all, We are pleased to announce Pharo Launcher 1.9.1 release! The goal of this release is to have a better Windows support. Indeed Pharo Launcher now uses a new library OSWinSubprocess (https://github.com/pharo-contributions/OSWinSubprocess <https://github.com/pharo-contributions/OSWinSubprocess>) created for Pharo Launcher needs. This library allows to create Windows processes through ffi calls to the Windows API. It uses the unicode api, allowing paths with non-ascii characters. In the same time, we switched from OSProcess to OSSubprocess (Linux and OS X) that is now the preferred library to use to fork processes on Linux-based systems. This release is not yet the default download of Pharo Launcher on Pharo web site because we want more feedback before promoting it. Please use this link to install it: https://files.pharo.org/pharo-launcher/1.9 <https://files.pharo.org/pharo-launcher/1.9> and let us know if this version works fine/better for you. ps: For now, the binary is not signed but it will come soon. ps2: Thanks to Keldon Alleyne for his PR on Pharo Launcher offering the first FFI binding to Windows process API Regards, The Pharo team.

4 9

Two Surprising and Scary FS Behaviors
by Sean P. DeNigris Aug. 6, 2019

Aug. 6, 2019

I may be ignorant of some key principle in the filesystem world, but IMHO conceptually, `location / somethingElse` should always return either location or something inside of it, unless the request explicitly requests otherwise (e.g. location / '..'). To do otherwise could be disastrous. Behavior #1 rootDataFolder := FileLocator home / 'a' / 'b' / . subfolderName := self accidentallyReturnAnEmptyString. assumedToBeInRootData := rootDataFolder / subfolderName. assumedToBeInRootData deleteAll. "I hope I have a recent machine backup, because..." assumedToBeInRootData resolve = FileLocator root resolve. "WTH?!" Behavior 2 (similar) Path * 'a' / 'b' / '/' = Path root. "WTH?!" ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 1

[Pharo 8.0] Build #596: 4137-Code-completion-error
by ci-pharo-ci-jenkins2＠inria.fr Aug. 5, 2019

Aug. 5, 2019

There is a new Pharo build available! The status of the build #596 was: FAILURE. The Pull Request #4175 was integrated: "4137-Code-completion-error" Pull request url: https://github.com/pharo-project/pharo/pull/4175 Issue Url: https://github.com/pharo-project/pharo/issues/4137 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #595: Refactor a few tests to new classes
by ci-pharo-ci-jenkins2＠inria.fr Aug. 5, 2019

Aug. 5, 2019

There is a new Pharo build available! The status of the build #595 was: FAILURE. The Pull Request #4189 was integrated: "Refactor a few tests to new classes" Pull request url: https://github.com/pharo-project/pharo/pull/4189 Issue Url: https://github.com/pharo-project/pharo/issues/refactor_tests Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Some new bindings for native emulation stuff
by Guillermo Polito Aug. 5, 2019

Aug. 5, 2019

Hi everybody, Iâve been playing around with machine code simulation this last week and Iâve made bindings for the unicorn library and the llvm disassembler: https://github.com/guillep/pharo-unicorn <https://github.com/guillep/pharo-unicorn> https://github.com/guillep/pharo-llvmDisassembler <https://github.com/guillep/pharo-llvmDisassembler> Funny thing: both support lots of platforms (x86 and arm both 32 and 64 bits and moreâ¦). So out of the box we can simulate and disassemble lots of platforms. And in one afternoon Iâve played with them to do a native debugger with Spec2 just for fun. Hope this evolves a bit more soon, and that it helps somebody. Guille

4 5

Aug. 5, 2019

Hello, I'm looking for a project using the Pharo System-History (class HistoryNode, HistoryLeaf). I want to use it in the fileDialog can someone send me a link to his project? Thank you in advance. -- Dutriez ClÃ©ment dutriezcle(a)gmail.com 0605199489 [image: www.linkedin.com/in/clÃ©ment-dutriez-407275173] <http://www.linkedin.com/in/clÃ©ment-dutriez-407275173>

1 0

Breakpoint restart error
by Ben Coman Aug. 5, 2019

Aug. 5, 2019

I trying to set a breakpoint programatically so that users can be dropped into the custom script they can add to a system. I try... Object compile: 'myTest |a b c| a := 1. b := 2. c := 3'. Breakpoint new node: (Object>>#myTest) ast; install. Object new myTest. "click <over> <over> <restart> <over>" but the following error appears and the debugger gets confused... [image: image.png] What am I doing wrong? cheers -ben

2 1

[Pharo 8.0] Build #594: UFFI-test-cases-should-end-with-Test
by ci-pharo-ci-jenkins2＠inria.fr Aug. 4, 2019

Aug. 4, 2019

There is a new Pharo build available! The status of the build #594 was: FAILURE. The Pull Request #4176 was integrated: "UFFI-test-cases-should-end-with-Test" Pull request url: https://github.com/pharo-project/pharo/pull/4176 Issue Url: https://github.com/pharo-project/pharo/issues/UFFI Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #593: Test-cases-should-end-with-Test-instead-of-Tests
by ci-pharo-ci-jenkins2＠inria.fr Aug. 4, 2019

Aug. 4, 2019

There is a new Pharo build available! The status of the build #593 was: FAILURE. The Pull Request #4187 was integrated: "Test-cases-should-end-with-Test-instead-of-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/4187 Issue Url: https://github.com/pharo-project/pharo/issues/Test Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #592: Add option to rename parameters when extract a method
by ci-pharo-ci-jenkins2＠inria.fr Aug. 3, 2019

Aug. 3, 2019

There is a new Pharo build available! The status of the build #592 was: FAILURE. The Pull Request #4168 was integrated: "Add option to rename parameters when extract a method" Pull request url: https://github.com/pharo-project/pharo/pull/4168 Issue Url: https://github.com/pharo-project/pharo/issues/RenameParametersVersion2 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #591: Add submenu, and new shortcuts
by ci-pharo-ci-jenkins2＠inria.fr Aug. 3, 2019

Aug. 3, 2019

There is a new Pharo build available! The status of the build #591 was: SUCCESS. The Pull Request #4167 was integrated: "Add submenu, and new shortcuts" Pull request url: https://github.com/pharo-project/pharo/pull/4167 Issue Url: https://github.com/pharo-project/pharo/issues/AddSubmenu Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Pharo Harbour
by Torsten Bergmann Aug. 2, 2019

Aug. 2, 2019

Hi, I experimented with Spec on P8 to build a simple file browser. Metacello new repository: 'github://astares/Pharo-Harbour/src'; baseline: 'Harbour'; load Not much and not complete - unfortunately I had no time to test or verify it yet and time to continue on it is limited next weeks. But I opened the repo to be public already so others can have a look. Use at your own risk and if you have improvements or fixes feel free to send PR's. Maybe we can build something better to replace the old file tool... Bye T.

5 7

Pharo Launcher 1.9.2 Crash
by Sean P. DeNigris Aug. 2, 2019

Aug. 2, 2019

PharoLauncher-1.9.2-x64.dmg does not open on Mac OS 10.14.1. Crash dump shows Freetype related: Segmentation fault Fri Jul 26 09:07:17 2019 VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git C stack backtrace & registers: rax 0x0000000111ae3be0 rbx 0x00000001121a1878 rcx 0x0000000000000000 rdx 0x000000000000018c rdi 0x0000000111ae3be0 rsi 0x0000000111ae3be0 rbp 0x00007ffee922c1b0 rsp 0x00007ffee922c1b0 r8 0x0000000000000000 r9 0x0000000000000000 r10 0x0000000106a935a0 r11 0x0000000111ae3be0 r12 0x0000000000000000 r13 0x0000000000000010 r14 0x0000000000000000 r15 0x0000000000000000 rip 0x00007fff67353dd0 0 libsystem_platform.dylib 0x00007fff67353dd0 _platform_memmove$VARIANT$Haswell + 240 1 Pharo 0x0000000106a25642 reportStackState + 952 2 Pharo 0x0000000106a25987 sigsegv + 174 3 libsystem_platform.dylib 0x00007fff67356b3d _sigtramp + 29 4 ??? 0x0000000000000000 0x0 + 0 5 Pharo 0x0000000106a5e5aa primitiveCalloutWithArgs + 164 Smalltalk stack dump: 0x7ffee923a2d0 M LibC>memCopy:to:size: 0x10ec722d8: a(n) LibC 0x7ffee923a318 M LibC class>memCopy:to:size: 0x10e4c65e0: a(n) LibC class 0x7ffee923a380 I ExternalAddress>copyFrom:to: 0x111bab200: a(n) ExternalAddress 0x111baea18 s FreeTypeFace(FT2Face)>renderGlyphIntoForm:pixelMode: 0x111bbc5b8 s FreeTypeFace(FT2Face)>renderGlyphIntoForm: 0x111bc2db0 s FreeTypeSubPixelAntiAliasedGlyphRenderer>renderStretchedGlyph:depth:subpixelPosition:font: 0x111bc6a70 s FreeTypeSubPixelAntiAliasedGlyphRenderer>subGlyphOf:colorValue:mono:subpixelPosition:font: ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 2

P8 voyage not installing, error probably in magritte
by Sanjay Minni Aug. 2, 2019

Aug. 2, 2019

hi, in Pharo 8-win64bit Voyage is not installing, failure is probably in magritte incidentally where should such things be pointed out ... this forum / elsewhere at ... / not at all regards Sanjay ----- cheers, Sanjay -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

3 3

[Pharo 8.0] Build #590: 4157-glmSubscriptions-is-deprecated-and-its-three-users-can-be-rewritten-as-subscriptions
by ci-pharo-ci-jenkins2＠inria.fr Aug. 1, 2019

Aug. 1, 2019

There is a new Pharo build available! The status of the build #590 was: FAILURE. The Pull Request #4159 was integrated: "4157-glmSubscriptions-is-deprecated-and-its-three-users-can-be-rewritten-as-subscriptions" Pull request url: https://github.com/pharo-project/pharo/pull/4159 Issue Url: https://github.com/pharo-project/pharo/issues/4157 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0