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

Recommendation for password encryption?
by Mariano Martinez Peck Sept. 30, 2022

Sept. 30, 2022

Hi guys. Some time ago I asked about the best way to encrypt a password. Some of the recommendations I got was: 1) Generally for passwords you do not write a decrypt method for security purposes (eg you do not want people to be able to reverse engineer the encrypted password easily) 2) put a little salt 3) There is http://www.squeaksource.com/Cryptography/PasswordHashingFFI 4) I should not decrypt password but instead I should compare both encrypted versions to see if they are equal. My scenario is the following. I need to store database passwords in text files. So I don't want to let them as plain text. And while I understand 4), I think it's a different scenario than mine. I know that some database driver may allow you to directly send the encrypted password. But still...I have another similar scenario in which I have to store a password and then send it (unencrypted)...so I kind of really need a bi-directional encryption. Now..I would try to avoid having an external library + FFI. Any ideas what is the best thing I can do? And how could I solve 1) if I want bidirectional like in my case? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

9 26

Re: [Pharo-project] Parsing and navigating Html
by Paul DeBruicker July 16, 2020

July 16, 2020

On 12/05/2010 06:02 AM, pharo-project-request(a)lists.gforge.inria.fr wrote: > From: St?phane Ducasse<stephane.ducasse(a)inria.fr> > Subject: [Pharo-project] Parsing and navigating Html > To:"Pharo-project(a)lists.gforge.inria.fr Development" > <Pharo-project(a)lists.gforge.inria.fr> > Message-ID:<1C53DFD8-3021-4233-BC83-CE8C1EA8D103(a)inria.fr> > Content-Type: text/plain; charset=us-ascii > > Hi > > I would like extract partial information from HTML pages. > So I started to play and fix HTMLParser. > > Now does anybody know alternatives? > > Second, does anybody develop a lib to query HTML structure as with the XMLSupport package? > > Stef The Soup package on SqueakSource.com works OK.

3 4

Re: [Pharo-dev] [Vm-dev] Image crashing on startup, apparently during GC
by Eliot Miranda June 3, 2019

June 3, 2019

Hi Damien, On Fri, Mar 23, 2018 at 12:38 PM, Damien Pollet <damien.pollet(a)gmail.com> wrote: > > Here are the files (image and various outputs). Running with --leakcheck > does mention a few object leaks (see output.txt); > Indeed the image is corrupt at start-up. See below. > I'm not sure where to get or how to build an assert VM. > When you build a phar. VM under build.macos64x64/pharo.cog.spur using the mvm script (mvm -A) you produce an assert VM in PharoAssert.app. > I also realized the VM I had was from this summer (the one that comes with > a 70 image with zeroconf). The output files I include were produced by the > VM at get.pharo.org/64/vmLatest70 > > https://www.dropbox.com/s/y8yqjuzd9nsvy1u/clap-broken.tar.gz?dl=0 > > On 20 March 2018 at 18:17, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > >> >> Hi Damien, >> >> On Tue, Mar 20, 2018 at 3:12 AM, Damien Pollet <damien.pollet(a)gmail.com> >> wrote: >> >>> >>> Hi, I have a Pharo image that crashes the VM on startup. The crash >>> report below seems to incriminate GC. Should I make it available somewhere >>> online? What's most convenient? >>> >> >> Don't care. Anywhere it can be downloaded from. Also, try running with >> -leakcheck 15, preferably in an assert VM and see if that gets you >> additional information. >> >> >>> >>> Process: Pharo [64892] >>> Path: /Users/USER/*/Pharo.app/Contents/MacOS/Pharo >>> Identifier: org.pharo.Pharo >>> Version: 5.0.201708271955 (5.0.201708271955) >>> >> Right. This VM is prior to the bug fixes in VMMaker.oscog-eem.2320: Spur: Fix a bad bug in SpurPlnningCompactor. unmarkObjectsFromFirstFreeObject, used when the compactor requires more than one pass due to insufficient savedFirstFieldsSpace, expects the corpse of a moved object to be unmarked, but copyAndUnmarkObject:to:bytes:firstField: only unmarked the target. Unmarking the corpse before the copy unmarks both. This fixes a crash with ReleaseBuilder class>>saveAsNewRelease when non-use of cacheDuring: creates lots of files, enough to push the system into the multi-pass regime. Pharo urgently needs to upgrade the VM to one more up to date than 2017 08 27 (in fact more up-to-date than opensmalltalk/vm commit 0fe1e1ea108e53501a0e728736048062c83a66ce, Fri Jan 19 13:17:57 2018 -0800). The bug that VMMaker.oscog-eem.2320 fixes can result in image corruption in large images, and can occur (as it has here) at start-up, causing one's work to be irretrievably lost. > Code Type: X86-64 (Native) >>> Parent Process: ??? [64888] >>> Responsible: Pharo [64892] >>> User ID: 501 >>> >>> Date/Time: 2018-03-19 20:27:03.906 +0100 >>> OS Version: Mac OS X 10.13.3 (17D102) >>> Report Version: 12 >>> Anonymous UUID: 6D022236-78DD-6676-117F-EADA56D5D1BE >>> >>> Sleep/Wake UUID: AC9E4E55-3CDB-4B4F-A6B4-51ACB1177154 >>> >>> Time Awake Since Boot: 28000 seconds >>> Time Since Wake: 6500 seconds >>> >>> System Integrity Protection: enabled >>> >>> Crashed Thread: 0 Dispatch queue: com.apple.main-thread >>> >>> Exception Type: EXC_BAD_ACCESS (SIGABRT) >>> Exception Codes: KERN_INVALID_ADDRESS at 0x000000012b67c0b0 >>> Exception Note: EXC_CORPSE_NOTIFY >>> >>> VM Regions Near 0x12b67c0b0: >>> VM_ALLOCATE 000000011adfc000-00000001259fc000 [172.0M] >>> rw-/rwx SM=PRV >>> --> >>> STACK GUARD 0000700005613000-0000700005614000 [ 4K] >>> ---/rwx SM=NUL stack guard for thread 1 >>> >>> Application Specific Information: >>> abort() called >>> >>> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread >>> 0 libsystem_kernel.dylib 0x00007fff53fbde3e __pthread_kill + 10 >>> 1 libsystem_pthread.dylib 0x00007fff540fc150 pthread_kill + 333 >>> 2 libsystem_c.dylib 0x00007fff53f1a312 abort + 127 >>> 3 org.pharo.Pharo 0x0000000104ed8997 sigsegv + 190 >>> 4 libsystem_platform.dylib 0x00007fff540eff5a _sigtramp + 26 >>> 5 ??? 000000000000000000 0 + 0 >>> 6 org.pharo.Pharo 0x0000000104e73558 markObjects + 464 >>> 7 org.pharo.Pharo 0x0000000104e72d40 fullGC + 72 >>> 8 org.pharo.Pharo 0x0000000104e92dea primitiveFullGC + >>> 45 >>> 9 org.pharo.Pharo 0x0000000104e52425 interpret + 26715 >>> 10 org.pharo.Pharo 0x0000000104e5c7f6 >>> enterSmalltalkExecutiveImplementation + 152 >>> 11 org.pharo.Pharo 0x0000000104e4be6c interpret + 674 >>> 12 org.pharo.Pharo 0x0000000104ed9cc1 >>> -[sqSqueakMainApplication runSqueak] + 394 >>> 13 com.apple.Foundation 0x00007fff2e6d696c >>> __NSFirePerformWithOrder + 360 >>> 14 com.apple.CoreFoundation 0x00007fff2c579127 >>> __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 >>> 15 com.apple.CoreFoundation 0x00007fff2c57904f >>> __CFRunLoopDoObservers + 527 >>> 16 com.apple.CoreFoundation 0x00007fff2c55b6a8 __CFRunLoopRun + >>> 1240 >>> 17 com.apple.CoreFoundation 0x00007fff2c55af43 >>> CFRunLoopRunSpecific + 483 >>> 18 com.apple.HIToolbox 0x00007fff2b872e26 >>> RunCurrentEventLoopInMode + 286 >>> 19 com.apple.HIToolbox 0x00007fff2b872a9f >>> ReceiveNextEventCommon + 366 >>> 20 com.apple.HIToolbox 0x00007fff2b872914 >>> _BlockUntilNextEventMatchingListInModeWithFilter + 64 >>> 21 com.apple.AppKit 0x00007fff29b3df5f _DPSNextEvent + >>> 2085 >>> 22 com.apple.AppKit 0x00007fff2a2d3b4c >>> -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] >>> + 3044 >>> 23 com.apple.AppKit 0x00007fff29b32d6d -[NSApplication >>> run] + 764 >>> 24 com.apple.AppKit 0x00007fff29b01f1a NSApplicationMain >>> + 804 >>> >>> -- >>> Damien Pollet >>> type less, do more [ | ] http://people.untyped.org/damien.pollet >>> >>> >> >> >> -- >> _,,,^..^,,,_ >> best, Eliot >> >> > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > > -- _,,,^..^,,,_ best, Eliot

9 26

Recent Pharo 6.1 OSX shows lots of "Error: unsupported compressor 8 on command line"
by Tim Mackinnon April 19, 2019

April 19, 2019

I noticed that recent Pharo 6.1 zero conf downloads show lots of these errors when you run the image in the terminal. Previous versions didnât do this - is this something to do with the latest vm upgrade? ./pharo-ui PagerDuty.image /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50: Error: unsupported compressor 8 /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist' /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50: Error: unsupported compressor 8 /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist' Tim

6 6

Minheadless trial
by Ben Coman Dec. 5, 2018

Dec. 5, 2018

wow time flies, its been 18 months since Ronie announced his Minheadless VM branch... [1] http://forum.world.st/Minheadless-VM-flavour-status-update-td4928091.html I've been meaning this whole time to try it out. Recently in my meandering thoughts on FreeRTOS port, I guessed Minheadless might make a good starting basis to experiment with. So a quick test on Ubuntu16.04.3(Windows10-WSL)... Long ago I'd already done... git clone git@github.com:OpenSmalltalk/opensmalltalk-vm.git so I now did... cd opensmalltalk-vm git remote add ronie git@github.com:ronsaldo/opensmalltalk-vm.git git fetch ronie git checkout MinimalisticHeadless ./scripts/updateSCCSVersions cd build.minheadless.cmake/x64/pharo.stack.spur/ ./mvm VM=`pwd`/release/dist/pharo ls $VM ==> confirmed it exists cd ~/pharo wget http://files.pharo.org/image/70/latest-minimal-64.zip unzip latest-minimal-64.zip sudo $VM Pharo7.0-metacello-64bit-65cff7b.image eval "19 + 23" ==> 42 yay Particularly interesting from [1] is "using the same CMake scripts for building on the three platforms: Windows, Linux and OS X." So I thought I'd also give it a try under Windows10-VisualStudio2017. I hardly used VS before, so I'll detail what I did as a reminder for myself (and also in case someone might be able to help if I get stuck). Under a windows cmd.exe prompt (having installed git and cloned opensmalltalk-vm a long time ago) cd opensmalltalk-vm git remote add ronie git@github.com:ronsaldo/opensmalltalk-vm.git git fetch ronie git checkout -b MinimalisticHeadless ronie/MinimalisticHeadless I watched video [2] about CMake integration with Visual Studio 10. and checked the VS workloads configuration specified [2@1:13] using [3]. There is a CMakeLists.txt file in the git root folder, so.. started VS > File > Open > Folder... C:\Repos\OpenSmalltalk\opensmalltalk-vm The CMake command run ([2]@2:13) was... C:\...\cmake.exe -G "Ninja" -DCMAKE_INSTALL_PREFIX:PATH="C:\Users\Ben\CMakeBuilds\...\x86-Debug" -DCMAKE_CXX_COMPILER="C:/.../MSVC/14.14.26428/bin/HostX86/x86/cl.exe" -DCMAKE_C_COMPILER="C:/.../MSVC/14.14.26428/bin/HostX86/x86/cl.exe" -DCMAKE_BUILD_TYPE="Debug" -DCMAKE_MAKE_PROGRAM="C:\...\CMAKE\Ninja\ninja.exe" "C:\Repos\OpenSmalltalk\opensmalltalk-vm" I changed the cmake configuration [2@2:27] to "x64-Debug". For debug target [2@3:00] I chose "pharo.exe" Hey, thats pretty cool [2@4:05] that switching between targets changes the highlighting of #ifdef code. I had a moment when I was missing the "Debug and Launch Settings" menu item [2@4:40-4:55] and mentioned at [4], but maybe there was some clash with previously experimenting with git cloning opensmalltalk-vm from inside VS. After closing VS and reopening my cmd.exe git'd opensmalltalk-vm it showed up, but I didn't change any settings there. Then (with x64-Debug & pharo.exe selected) I went Cmake > Build All ==> 10 Errors, 9 Warnings, which I'll discuss in a followup post. cheers -ben [2] https://blogs.msdn.microsoft.com/vcblog/2016/10/05/cmake-support-in-visual-… [3] https://docs.microsoft.com/en-us/visualstudio/install/modify-visual-studio [4] https://blogs.msdn.microsoft.com/vcblog/2016/12/20/cmake-support-in-visual-… [5] https://developercommunity.visualstudio.com/content/problem/234808/cmake-de…

6 22

PharoLauncher : Image version determination error
by Julien Nov. 9, 2018

Nov. 9, 2018

Hello, Is there something wrong with the latest Pharo 7.0 32bits image? I got this error from Pharo Launcher: Cannot determine image version: image version file not found! Try to run this command in a shell to get more information on the problem: cd "/Users/julien/Documents/Pharo/vms/private/6521/Pharo.app/Contents/MacOS" && "/Users/julien/Documents/Pharo/vms/private/6521/Pharo.app/Contents/MacOS/Pharo" --headless "/Users/julien/Documents/Pharo/images/RTFExperiment-Iceberg/RTFExperiment-Iceberg.image" eval "(Smalltalk imagePath asFileReference parent) / 'pharo.version' writeStreamDo: [ :stream | |major minor| major := SystemVersion current major. minor := SystemVersion current minor. (major = 6 and: [ SystemVersion current highestUpdate >= 60509 ]) ifTrue: [ minor := 1 ]. stream << major asString; << minor asString ]" When trying to start it. If I run this script in the terminal, nothing is print but the process crashes returning 1 as exit code. Can someone relate this issue as well? 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

9 20

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

Promote new Pharo 7 VM (d952580)
by Alistair Grant Sept. 2, 2018

Sept. 2, 2018

Hi Esteban and Everyone, I would like to request we start the process for promoting a new Pharo 7 VM. d952580 (vmLatest as I write this) has two changes that I'm looking forward to: - Fix path encoding / decoding on OSX Hopefully this will finally allow me to submit the File Attributes changes (fogbugz 18279[1] & 21368[2]). - Add primitiveChangeMode(), primitiveChangeOwner() and primitiveSymlinkChangeOwner() This will allow Pharo to set file owner & group IDs and posix permissions on Unix platforms (Linux & OSX). Other changes include: - stdio is flagged correctly on Windows - Windows 64 bit work - fflush added to sqFileTruncate() - Eliot's work on Cog - Everything else I've missed :-) (sorry to those authors) Running the automated test suite on Linux 32 bit, Linux 64 bit and Windows 32 bit produces basically the same set of failures with the current stable VM and the proposed VM. [1] https://pharo.fogbugz.com/f/cases/18279/isSymlink-seems-to-be-broken-on-Lin… [2] https://pharo.fogbugz.com/f/cases/21368/Integrate-FileAttributesPlugin Thanks, Alistair

2 2

[Pharo 7.0-dev] Build #1208: 22381-asCommaString-deserves-a-executable-comment
by ci-pharo-ci-jenkins2＠inria.fr Aug. 31, 2018

Aug. 31, 2018

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

1 0

[Pharo 7.0-dev] Build #1207: turned example expressions in comments into the form of executable exâ¦
by ci-pharo-ci-jenkins2＠inria.fr Aug. 31, 2018

Aug. 31, 2018

There is a new Pharo build available! The status of the build #1207 was: FAILURE. The Pull Request #1753 was integrated: "turned example expressions in comments into the form of executable exâ¦" Pull request url: https://github.com/pharo-project/pharo/pull/1753 Issue Url: https://pharo.fogbugz.com/f/cases/22323 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1206: 20638-Cleaning-left-over-from-NativeBoost
by ci-pharo-ci-jenkins2＠inria.fr Aug. 31, 2018

Aug. 31, 2018

There is a new Pharo build available! The status of the build #1206 was: FAILURE. The Pull Request #1734 was integrated: "20638-Cleaning-left-over-from-NativeBoost" Pull request url: https://github.com/pharo-project/pharo/pull/1734 Issue Url: https://pharo.fogbugz.com/f/cases/20638 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1205: 22378-rename-NECSymbols---NECSymbolCache
by ci-pharo-ci-jenkins2＠inria.fr Aug. 31, 2018

Aug. 31, 2018

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

1 0

[Pharo 7.0-dev] Build #1204: 22186-eCompletion smart quotes is missing other common Smalltalk characters like | and <
by ci-pharo-ci-jenkins2＠inria.fr Aug. 31, 2018

Aug. 31, 2018

There is a new Pharo build available! The status of the build #1204 was: FAILURE. The Pull Request #1583 was integrated: "22186-eCompletion smart quotes is missing other common Smalltalk characters like | and <" Pull request url: https://github.com/pharo-project/pharo/pull/1583 Issue Url: https://pharo.fogbugz.com/f/cases/22186 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1203: 22379-ecompletion-clean-up-toggleExpand
by ci-pharo-ci-jenkins2＠inria.fr Aug. 31, 2018

Aug. 31, 2018

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

1 0

[Pharo 7.0-dev] Build #1202: 22300-returning-enumeration-does-not-search-elements-from-the-enumeration
by ci-pharo-ci-jenkins2＠inria.fr Aug. 31, 2018

Aug. 31, 2018

There is a new Pharo build available! The status of the build #1202 was: SUCCESS. The Pull Request #1673 was integrated: "22300-returning-enumeration-does-not-search-elements-from-the-enumeration" Pull request url: https://github.com/pharo-project/pharo/pull/1673 Issue Url: https://pharo.fogbugz.com/f/cases/22300 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

IndexedSlots in combination with StatefulTraits
by Torsten Bergmann Aug. 31, 2018

Aug. 31, 2018

I guess I found a bug in accessing Slots using #slots in combination with IndexedSlots and traits. To reproduce use latest Pharo 7 (Build 1126) First create a class with a slot, note that the slot needs to be : Object subclass: #ClassA slots: { IndexedSlot named: #upper } classVariables: { } package: 'Slot-Bugs' As it is the first slot it internally receives an index 1 as you can check with "ClassA slots first". Now define a stateful trait with another indexed slot: Trait named: #StatefulTrait uses: {} slots: { IndexedSlot named: #slotFromTrait } category: 'Slot-Bugs' And create a new subclass using the new Trait ClassA subclass: #ClassB uses: StatefulTrait instanceVariableNames: '' classVariableNames: '' package: 'Slot-Bugs' 1. when you evaluate "ClassA slots" it returns {#FirstSlot => Slot} which is correct 2. when you evaluate "StatefulTrait slots" it returns {#slotFromTrait => Slot} which is correct 3. when you evaluate "ClassB allSlots" returns "an OrderedCollection(#upper => InstanceVariableSlot #slotFromTrait => InstanceVariableSlot)" which is OK but 4. when you evaluate "ClassB slots" it returns {#slotFromTrait => InstanceVariableSlot} which is NOT correct as class B does not define the slot, it is defined in the trait So I think 4. is wrong and reasons is the implementation of #slot: slots "I remove the slots comming from a traitComposition" ^ super slots reject:[ :e | self traitComposition slots includes:e ] If you debug you will notice that super slots returns our #slotFromTrait with an index of 2 while self traitComposition slots returns our #slotFromTrait with an index of 1 while which is the same #slotFromTrait but a different index - therefore it does not get removed. Dont know what is the best way to fix this without any side effects. Commenst and help appreciated. Thanks T.

5 8

[Pharo 7.0-dev] Build #1201: 22374 create button in debugger doesnt work for classes like it does for methods
by ci-pharo-ci-jenkins2＠inria.fr Aug. 31, 2018

Aug. 31, 2018

There is a new Pharo build available! The status of the build #1201 was: SUCCESS. The Pull Request #1726 was integrated: "22374 create button in debugger doesnt work for classes like it does for methods" Pull request url: https://github.com/pharo-project/pharo/pull/1726 Issue Url: https://pharo.fogbugz.com/f/cases/22374 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1200: 22377-simplify-NEContextcreateModel
by ci-pharo-ci-jenkins2＠inria.fr Aug. 31, 2018

Aug. 31, 2018

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

1 0

[Pharo 7.0-dev] Build #1199: 22373-LinkedListreject-is-slow
by ci-pharo-ci-jenkins2＠inria.fr Aug. 30, 2018

Aug. 30, 2018

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

1 0

[Pharo 7.0-dev] Build #1198: 22366-TabMorph-should-use-displayScaleFactor
by ci-pharo-ci-jenkins2＠inria.fr Aug. 29, 2018

Aug. 29, 2018

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

1 0

[Pharo 7.0-dev] Build #1197: 21989-TPrintOnSequencedTesttestStoreOn-contains-commented-code
by ci-pharo-ci-jenkins2＠inria.fr Aug. 29, 2018

Aug. 29, 2018

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

1 0

[Pharo 7.0-dev] Build #1196: 22370-RF-tests-related-to-level
by ci-pharo-ci-jenkins2＠inria.fr Aug. 29, 2018

Aug. 29, 2018

There is a new Pharo build available! The status of the build #1196 was: SUCCESS. The Pull Request #1723 was integrated: "22370-RF-tests-related-to-level" Pull request url: https://github.com/pharo-project/pharo/pull/1723 Issue Url: https://pharo.fogbugz.com/f/cases/22370 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1195: 21504-StringromanNumber-should-be-symmetric-to-IntegerprintStringRoman
by ci-pharo-ci-jenkins2＠inria.fr Aug. 29, 2018

Aug. 29, 2018

There is a new Pharo build available! The status of the build #1195 was: SUCCESS. The Pull Request #1619 was integrated: "21504-StringromanNumber-should-be-symmetric-to-IntegerprintStringRoman" Pull request url: https://github.com/pharo-project/pharo/pull/1619 Issue Url: https://pharo.fogbugz.com/f/cases/21504 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

ZnCharacterEncoder default instances
by Alistair Grant Aug. 28, 2018

Aug. 28, 2018

Hi Sven and Everyone, Instantiation of character encoders is relatively expensive, as can be seen by the following code snippet: | count str ba enc new old | count := 10000. str := 'test-Ã¤Ã¶Ã¼'. new := [ count timesRepeat: [ (ZnCharacterEncoder newForEncoding: 'utf8') encodeString: str ] ] timeToRunWithoutGC. enc := ZnCharacterEncoder newForEncoding: 'utf8'. old := [ count timesRepeat: [ enc encodeString: str ] ] timeToRunWithoutGC. { old. new. } " #(14 122)" What do you think of the idea of caching default instances of encoders? My idea was to have a dictionary in ZnCharacterEncoder and add a class method #forEncoding:. This would lazily create an instance, store it in the dictionary, and then re-use the instance whenever that encoder is requested. If people really want their own instance (not sure why, there aren't any instance variables, and so there's no state), they can use the existing #newForEncoding:. For example, sending #exists to a file reference currently instantiates two encoders. This was actually previously fixed by #20273[1], but seems to have been lost with the refactoring of FilePluginPrims to File. From memory, Cyril's application saved 12 seconds by caching the encoder. But in that case the instance was private to the file plugin primitives. This would be a more general solution. [1] https://pharo.fogbugz.com/f/cases/20273/FilePluginPrims-could-save-an-encod… Thanks, Alistair

2 3

Debugging FFI Calls
by Eliot Miranda Aug. 27, 2018

Aug. 27, 2018

Hi All, the latest VMs support a new facility which catches and reports exceptions during FFI calls as primitive failures. That means that if you have the relevant support code loaded (described below) and depending on dialect, you write your FFI interface method to contain an error code, or you're using the UnifiedFFI which uses invokeWithArguments:, then any exception that occurs during the FFI call will be caught and reported to use with the error code bound to an instance of ExceptionInFFICall, which contains a platform-specific error code and the pc at which it occurred. To use this facility you'll need to download a VM built yesterday or later (it should be derived from VMMaker.oscog-eem.2435 or later), or build your own from the tip of the Cog branch in opensmalltalk/vm. You'll then need to update the image code to install ExceptionInFFICall appropriately: in Pharo6 load SLICE 22367 in Squeak load the latest FFI code from source.squeak.org/FFI and update your image from trunk in Cuis, you'll need to adapt these changes to Cuis (sorry!!) There are two command-line flags to override the default behavior. [-]-failonffiexception causes the handling to be applied to all FFI calls, so if a method doesn't contain an error, you'll just see a primitive failure, and if ExceptionInFFICall is not installed you'll see only an error number in the call's error code. [-]-nofailonffiexception ignores exceptions during FFI calls, hence defaulting to the old behavior of crashing the VM (which may be useful if one is using a low-level debugger to debug the VM and/or external code). HTH _,,,^..^,,,_ best, Eliot

1 0