September 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

Pharo Downloads are sluggish
by Esteban Maringolo March 13, 2019

March 13, 2019

Is there a reason why the latest version of the builds linked from the website are not hosted in some CDN, Amazon S3 or similar? Maybe in Europe the speed is fast, but where I am (Argentina) it is really slow, the screenshot shows 3.5KB/s, it averages 10KB/s, with peaks of 40KB/s. This is an pitiful boarding experience, that will make many cancel it even before getting to open the downloaded launcher. [image: node-pharo.png] The screenshot shows that is not a problem with my home connection, which isn't the fastest but is "normal" for my use cases. Regards, Esteban A. Maringolo ps: When I finished writing this email, this was the progress... [image: image.png]

4 15

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

Streams and FileDialog in Pharo 6 and 7
by Torsten Bergmann Nov. 11, 2018

Nov. 11, 2018

Hi, A question to those who worked on the new streams for Pharo 7: In PHARO 6 I used the following expression to open a file dialog and let the user choose a binary file: s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). This returned - either nil (when file dialog was canceled) - a "MultiByteFileStream" instance when a file was selected The MultiByteFileStream instance already had the name of the file (= full path) and I was able to query it for further use: s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). s name inspect (for instance to display which file is processed in a window by showing the full path) Now in PHARO 7 same expression returns an instance of ZnCharacterReadStream (as MultiByteFileStream is deprecated): s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). and ZnCharacterReadStream does not understand #name - and in fact the info about the name is totally lost/not available. To me this looks missing/broken. So what is the recommended way in Pharo 7 to open a file dialog, let the use choose a file and get a file stream but also the name? IMHO this is either broken or missing... Thanks T.

6 10

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

Fraction and ScaledDecimal should be not be serialized as Float in STON format
by Julien Oct. 10, 2018

Oct. 10, 2018

Hello, I realised that in the current implementation, when a number is serialised by STON it is either as an integer literal or as a float literal. There is a risk to loose precision, especially if what you serialise is a ScaledDecimal or a fraction. I propose a simple change to fix this: 1. Add STONWriter>>#isInJsonMode method which returns true if the STONWriter wants to write JSON 2. Add: Fraction>>#stonOn: stonWriter stonWriter isInJsonMode ifTrue: [ ^ super stonOn: stonWriter ]. stonWriter writeObject: self streamMap: [ :dictionary | dictionary at: #numerator put: numerator. dictionary at: #denominator put: denominator ] 3. Add: ScaledDecimal>>#stonOn: stonWriter stonWriter isInJsonMode ifTrue: [ ^ super stonOn: stonWriter ]. stonWriter writeObject: self streamMap: [ :dictionary | dictionary at: #numerator put: numerator. dictionary at: #denominator put: denominator. dictionary at: #scale put: scale ] This change has a main drawback, storing fractions and scaled decimal will result in a huge overhead. Maybe for ScaledDecimal we can use Pharoâs literal (e.g. 1.12s2). For fractions I donât know what literal could be used? Or maybe the overhead is fine? Cheers, 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

3 6

Migrating XML support to github/PharoContributions/
by Stephane Ducasse Oct. 7, 2018

Oct. 7, 2018

Hi I contacted the maintainer (but I'm not sure in fact who it is :) ) about the XML related packages in Pharo extras. XMLParser XMLParserHTML XMLParserStAX XMLSupport XMLWriter XPath I did not get any answer so may be I sent a mail to the wrong email address. Probably. Now the question still remains: who is planning to migrate the XML packages. I was planning to do it but I will not consider history because I do not know how to do it and I do not have the time to do it (sorry). And yes I work the weekends and this is bad and this is not even on Pharo. I was planning to spend some time on the baseline and making sure that we can load everything and run the tests. So let me know. Stef

5 7

[ANN] Success story Mobility Map
by Norbert Hartl Oct. 2, 2018

Oct. 2, 2018

As presented on ESUG here is the brief description of one of our current projects. Mobility Map ââââââ Mobility Map is a broker for mobility services. It offers multi-modal routing search enabling users to find the best travel options between locations. Travel options include car sharing, bikes, trains, busses etc. Rented cars can be offered for ride sharing on booking time letting other people find it to participate in the ride. Single travel options are combined in travel plans that can be booked and managed in a very easy way. For this project main requirements were scalability to serve a large user base and flexibility to add more additional providers to the broker. The application has been realized using web technologies for the frontend and pharo for the backend. Using a microservice architecture combined with a broker it is easy to extend the platform with additional brokers. Deployment is done using docker swarm for distributing dozens of pharo images among multiple server machines connected by a message queue for the communication. Pharo supported that scenario very well enabling us the meet the requirements with less effort. Pharo turned out to be a perfect fit to develop the application in a agile way. Small development cycles with continuous integration and continuous delivery enables fast turnarounds for the customers to validate progress. This is a screenshot of the search page for multi-modal results:

6 11

Reach of Iceberg/git/tonel ?
by Sven Van Caekenberghe Oct. 2, 2018

Oct. 2, 2018

Hi, So the future for Pharo is Iceberg/git/tonel and that is fine. My question however is: if I convert my external libraries to this new format, what is the reach of this new technology ? Can people still load code in older versions of Pharo ? I think 6.x is no problem, but what about earlier versions ? What about other Smalltalk implementations ? What is the official answer here ? A second question: suppose a repo is converted, is then still possible to copy a version over to an old MC repo ? Just to keep it in sync. Thx, Sven

6 7

[ANN] Migrated Artefact to GitHub
by Stephane Ducasse Oct. 2, 2018

Oct. 2, 2018

Hi guille I deeply appreciated that you spent your time to bring Artefact to Pharo 70 and in general all the positive energy you put around Pharo. I love Iceberg! and more! I quit these mailing-lists in the past because of these little aggressions, the "You should do that" I registered today again to this mailing list just to publicly talk to you, while I could come to your office (I will do it too). I did a port of Artefact to Pharo 60 a while ago and started to fix Artefact aspects I did not like and I would like to integrate my fixes to yours. Please let me know where it is. :) I do not care of the history because I prefer the future. If people care then this is their duties. Easy. If they are not happy. This is THEIR PROBLEM. You see people often tells me that I cannot control and that github is decentralised. It is! So enjoy but @People try to avoid to piss on good will of others. Now sorry Norbert your point that Guillemo would be rude because he spent his time to help Milton and made sure that Artefact in Pharo 70 is clearly out of context and misplaced. You see I did the same in github.com/olivierauverlot because I needed it. And this is like that. Period. You are not happy. This is ok. You do not like it. This is ok too. This is several times that I noticed that your are not nice with emails so do the same than me: think about the impact on others. You have no idea about what guille is doing and what it is paid for and this is certainly not to fix Artefact. And you may notice that we know what is to work on others unmaintained code because we do it all the time, we even create documentation on systems we do not understand because some people are too busy to write method and class comments so imagine documentation. So I would like to thanks again guille and I would like to have artefact on Pharo 70. Stef

5 11

[Pharo 7.0-dev] Build #1281: 22433-Review-FloatTest-testCopySignTo-and-testSign
by ci-pharo-ci-jenkins2＠inria.fr Sept. 30, 2018

Sept. 30, 2018

There is a new Pharo build available! The status of the build #1281 was: SUCCESS. The Pull Request #1835 was integrated: "22433-Review-FloatTest-testCopySignTo-and-testSign" Pull request url: https://github.com/pharo-project/pharo/pull/1835 Issue Url: https://pharo.fogbugz.com/f/cases/22433 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1280: 22489-cleanup--CompilationContext-and-doSemanticAnalysis
by ci-pharo-ci-jenkins2＠inria.fr Sept. 30, 2018

Sept. 30, 2018

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

1 0

[Pharo 7.0-dev] Build #1279: 22498-TextEditorsaveContentsInFile-should-not-use-FileStream
by ci-pharo-ci-jenkins2＠inria.fr Sept. 30, 2018

Sept. 30, 2018

There is a new Pharo build available! The status of the build #1279 was: FAILURE. The Pull Request #1839 was integrated: "22498-TextEditorsaveContentsInFile-should-not-use-FileStream" Pull request url: https://github.com/pharo-project/pharo/pull/1839 Issue Url: https://pharo.fogbugz.com/f/cases/22498 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1278: 22397-Add-executable-comments-to-Date-classes
by ci-pharo-ci-jenkins2＠inria.fr Sept. 29, 2018

Sept. 29, 2018

There is a new Pharo build available! The status of the build #1278 was: SUCCESS. The Pull Request #1832 was integrated: "22397-Add-executable-comments-to-Date-classes" Pull request url: https://github.com/pharo-project/pharo/pull/1832 Issue Url: https://pharo.fogbugz.com/f/cases/22397 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1277: 22497-MIMEDocumentsaveToFile-should-not-use-FileStream
by ci-pharo-ci-jenkins2＠inria.fr Sept. 29, 2018

Sept. 29, 2018

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

1 0

Re: [Pharo-dev] Artifact and PDFExporter for Roassal
by milton mamani Sept. 28, 2018

Sept. 28, 2018

El jue., 13 sept. 2018 a las 14:06, milton mamani (<akevalion(a)gmail.com>) escribiÃ³: > Hi! > > I am Milton Mamani I work with Roassal2, and now I am in ESUG-Cagliari, > and I have tried to load Artefact with the next piece of code, in the last > Pharo7 image. > > Metacello new > configuration: 'Artefact'; > smalltalkhubUser: 'RMoD' project: 'Artefact'; > version: #stable; > load. > > "To load roassal and pdf roassal exporter" > > Metacello new > configuration: 'GraphQLBeta'; > smalltalkhubUser: 'ObjectProfile' project: 'GraphQL'; > version: #development; > load. > > Gofer new > smalltalkhubUser: 'azazael' project: 'RTPDFExporter'; > package: 'ConfigurationOfRTPDFExporter'; load. > (Smalltalk at: #ConfigurationOfRTPDFExporter) loadDevelopment > > I have a problem, when I tried to export my Roassal-Visualization to pdf > file with for example this piece of code: > > view := RTBoxPlotExample new exampleBoxPlot5 build view. > stream := 'foo.pdf' asFileReference writeStream. > > [RTPDFExporter new > stream: stream; > exportView: view ] ensure: [ stream close ] > > I get a lot of kind exceptions related with the class: PDFStreamPrinter > > In the method visitPDFDataXRefEntry: > And in the logic of the new Stream classes of Pharo7. > > Could you please review Artifact in Pharo7 with this roassal2 > implementation > > Cheers, > Milton > >

3 2

[Pharo 7.0-dev] Build #1276: 22482-AutoCompletion-preview-breaks-code-navigation
by ci-pharo-ci-jenkins2＠inria.fr Sept. 28, 2018

Sept. 28, 2018

There is a new Pharo build available! The status of the build #1276 was: SUCCESS. The Pull Request #1831 was integrated: "22482-AutoCompletion-preview-breaks-code-navigation" Pull request url: https://github.com/pharo-project/pharo/pull/1831 Issue Url: https://pharo.fogbugz.com/f/cases/22482 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1275: 22480-ClassTestCase--testClassComment-depends-on-the-environment-configuration
by ci-pharo-ci-jenkins2＠inria.fr Sept. 28, 2018

Sept. 28, 2018

There is a new Pharo build available! The status of the build #1275 was: FAILURE. The Pull Request #1829 was integrated: "22480-ClassTestCase--testClassComment-depends-on-the-environment-configuration" Pull request url: https://github.com/pharo-project/pharo/pull/1829 Issue Url: https://pharo.fogbugz.com/f/cases/22480 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1274: 22458-lastFileFor-baseFileName-extension-extension-randomly-sorts-files
by ci-pharo-ci-jenkins2＠inria.fr Sept. 28, 2018

Sept. 28, 2018

There is a new Pharo build available! The status of the build #1274 was: FAILURE. The Pull Request #1806 was integrated: "22458-lastFileFor-baseFileName-extension-extension-randomly-sorts-files" Pull request url: https://github.com/pharo-project/pharo/pull/1806 Issue Url: https://pharo.fogbugz.com/f/cases/22458 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

PharoLauncher based test resporting centre
by Ben Coman Sept. 28, 2018

Sept. 28, 2018

Just a random idea... when running Testrunner locally and a random test causes the image to freeze, its a bit of an effort to identify which test was being run. You need to restart and then start bisecting the tests and perhaps it is intermittent so the bisect doesn't work... but now that PharoLauncher has been mainstreamed maybe it could provide a centralised Reporting Centre i.e. open a port for launched images to report the test about-to-commence as well as the run time. Then it would be simple to see which test froze the system. Also it could keep a record individual test runtimes, to alleviate fears when the system is not frozen but just a long running test. Extending the idea, while CI testing is very useful, we get these sporadic errors that are hard to replicate locally. A local PharoLauncher driven system for repetitively launching an image auto-running tests might be good to gather statistics on sporadic failures to then drill down on the troublemakers. Plus with the goal of having an object based logging system, a viewer is needed and perhaps PharoLauncher would be a logical place to provide a logging service to gather and especially to view log-objects reporting by launched images. of course, resources required to do it, but just thought I share the idea. cheers -ben

1 1

[Pharo 7.0-dev] Build #1273: 22477-DelayScheduler-cleanup-and-refactoring
by ci-pharo-ci-jenkins2＠inria.fr Sept. 27, 2018

Sept. 27, 2018

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

1 0

[ANN] Migrated Artefact to GitHub
by Guillermo Polito Sept. 27, 2018

Sept. 27, 2018

Hi all, I've moved the Artefact library to GitHub ( https://github.com/pharo-contributions/Artefact) I've also made some changes to it in the way and made a 1.7.0 version with: - support for Pharo7 streams - a baseline So, people using Artifact, you can contribute through pull requests ^^, Guille -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 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

3 2

Esteban's ChangeLog week of 17 September 2018
by estebanlm＠gmail.com Sept. 27, 2018

Sept. 27, 2018

Hello! This is my weekly ChangeLog, from 17 September 2018 to 23 September 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=17/9/2018&to=23/9/2018 ChangeLog ========= 19 September 2018: ------------------ * I migrated all [pharo-ide](https://github.com/pharo-ide) projects to tonel format. Harder than it seems, it took me a good bunch of hours. But now is working. This will enhance work/fixes on Calypso. 18 September 2018: ------------------ * I just [fixed the CI for Calypso](https://github.com/pharo-ide/Calypso/issues/319) (it was failing for Pharo 7.0 because of problems when updating). Now I can start fixing real issues of it :) 17 September 2018: ------------------ * I backported/promoted a new stable vm for Pharo 6.1. This is the one that has been tested for Pharo 7.0alpha already for some time, so things should be fine. Current stable VM is from 2018-07-04 (yeah, eventually we will have a decent semver numbering, but for now this will have to be enough :P) cheers! Esteban

3 3

Top MenuBar does not auto follow font changes
by Sven Van Caekenberghe Sept. 27, 2018

Sept. 27, 2018

Hi, The Top MenuBar does not seem to auto follow font changes, although it picks them uppitiest when you hide/show the menu bar from the Settings. Sven

1 0

[Pharo 7.0-dev] Build #1272: 22490-It-seems-that-openFileStreamwritable-is-dead-code
by ci-pharo-ci-jenkins2＠inria.fr Sept. 27, 2018

Sept. 27, 2018

There is a new Pharo build available! The status of the build #1272 was: SUCCESS. The Pull Request #1827 was integrated: "22490-It-seems-that-openFileStreamwritable-is-dead-code" Pull request url: https://github.com/pharo-project/pharo/pull/1827 Issue Url: https://pharo.fogbugz.com/f/cases/22490 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] [Pharo 7.0-dev] Build #1271: 22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary
by Esteban Lorenzano Sept. 26, 2018

Sept. 26, 2018

> On 26 Sep 2018, at 15:24, Petr Fischer via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Petr Fischer <petr.fischer(a)me.com> > Subject: Re: [Pharo-dev] [Pharo 7.0-dev] Build #1271: 22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary > Date: 26 September 2018 at 15:24:49 CEST > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > Hello, why is test status of this pull request: FAILURE? > > Thanks for clarification, Petr Fischer Is a misleading message. It means merge was done, but for some reason (usually network problems), some tests failed to run. We are working on fix that (but you knowâ¦ time :P). Esteban > > >> There is a new Pharo build available! >> >> The status of the build #1271 was: FAILURE. >> >> The Pull Request #1823 was integrated: "22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary" >> Pull request url: https://github.com/pharo-project/pharo/pull/1823 >> >> Issue Url: https://pharo.fogbugz.com/f/cases/22483 >> Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… > > > >

1 0

Re: [Pharo-dev] [Pharo 7.0-dev] Build #1271: 22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary
by Marcus Denker Sept. 26, 2018

Sept. 26, 2018

Hi, It means that the build for this one merge failedâ¦ build got much more stable over the last weeks, but we still sometimes have crashes (here it seems to be the text render bug) But this is undefended of the merge: the next build then will take this into account. > On 26 Sep 2018, at 15:24, Petr Fischer via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Petr Fischer <petr.fischer(a)me.com> > Subject: Re: [Pharo-dev] [Pharo 7.0-dev] Build #1271: 22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary > Date: 26 September 2018 at 15:24:49 CEST > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > Hello, why is test status of this pull request: FAILURE? > > Thanks for clarification, Petr Fischer > > >> There is a new Pharo build available! >> >> The status of the build #1271 was: FAILURE. >> >> The Pull Request #1823 was integrated: "22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary" >> Pull request url: https://github.com/pharo-project/pharo/pull/1823 >> >> Issue Url: https://pharo.fogbugz.com/f/cases/22483 >> Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… > > > >

1 0

[Pharo 7.0-dev] Build #1271: 22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2018

Sept. 26, 2018

There is a new Pharo build available! The status of the build #1271 was: FAILURE. The Pull Request #1823 was integrated: "22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary" Pull request url: https://github.com/pharo-project/pharo/pull/1823 Issue Url: https://pharo.fogbugz.com/f/cases/22483 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

2 1

[Pharo 7.0-dev] Build #1270: 22221-Jump-to-next-keyword
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2018

Sept. 26, 2018

There is a new Pharo build available! The status of the build #1270 was: SUCCESS. The Pull Request #1722 was integrated: "22221-Jump-to-next-keyword" Pull request url: https://github.com/pharo-project/pharo/pull/1722 Issue Url: https://pharo.fogbugz.com/f/cases/jump Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1269: 22481-NetNameResolver-classlocalHostAddress---error-check-with-default
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2018

Sept. 26, 2018

There is a new Pharo build available! The status of the build #1269 was: FAILURE. The Pull Request #1822 was integrated: "22481-NetNameResolver-classlocalHostAddress---error-check-with-default" Pull request url: https://github.com/pharo-project/pharo/pull/1822 Issue Url: https://pharo.fogbugz.com/f/cases/22481 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

IoT hackathon @zweidenker
by Norbert Hartl Sept. 26, 2018

Sept. 26, 2018

Hi, we (ZWEIDENKER) and RModD organized an IoT Hackathon in cologne at 19th of october 2018. The plan will be: - Allex Oliviera will present the tutorial he made on PharoThings [1]. The audience will try it in a hands-on-session and give feedback to improve it. Zweidenker is sponsoring the hardware so nobody has to bring anything to the session - We are collecting ideas at the moment what we want to do with the learnings from Allex, meaning what hardware to build - If you have ideas about what to build with real life things that should be connected from pharo, please tell us. We will compile a list of ideas and for the first two or three we will buy the necessary hardware so we can build it at that day The Hackathon will take place at ZWEIDENKER GmbH Luxemburger Str. 72 50674 KÃ¶ln germany As we have a limited amount of seats you need to register if you are interested. Go to http://zweidenker.de/en/iot-hackathon-2018 <http://zweidenker.de/en/iot-hackathon-2018> to register your seat on the session. If there are more participants than seats we will have to do selection by dice rolling. Registration period ends on 5th of october so you will know in advance if you can come. See you there, Norbert on behalf of ZWEIDENKER [1] https://github.com/pharo-iot/PharoThings <https://github.com/pharo-iot/PharoThings>

1 0

[Pharo 7.0-dev] Build #1268: 22488-Bootstrapping-from-outside-of-the-repository-broken
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2018

Sept. 26, 2018

There is a new Pharo build available! The status of the build #1268 was: SUCCESS. The Pull Request #1826 was integrated: "22488-Bootstrapping-from-outside-of-the-repository-broken" Pull request url: https://github.com/pharo-project/pharo/pull/1826 Issue Url: https://pharo.fogbugz.com/f/cases/22488 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1267: 22478 button presenter does not take into account its color
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2018

Sept. 26, 2018

There is a new Pharo build available! The status of the build #1267 was: SUCCESS. The Pull Request #1820 was integrated: "22478 button presenter does not take into account its color" Pull request url: https://github.com/pharo-project/pharo/pull/1820 Issue Url: https://pharo.fogbugz.com/f/cases/22478 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1266: 22440-Compiler-parseExpression-does-not-set-up-compilation-context-for-method-node
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2018

Sept. 26, 2018

There is a new Pharo build available! The status of the build #1266 was: SUCCESS. The Pull Request #1825 was integrated: "22440-Compiler-parseExpression-does-not-set-up-compilation-context-for-method-node" Pull request url: https://github.com/pharo-project/pharo/pull/1825 Issue Url: https://pharo.fogbugz.com/f/cases/22440 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] iceberg PrimitiveFailed allocateExecutablePage - PharoDebug.log
by Eliot Miranda Sept. 26, 2018

Sept. 26, 2018

Hi Petr, along with Estebanâs request for the error code from allocateExecutablePage can you also see whether use of iceberg is successful the second time you launch Pharo? So start up your virtualbox, try and interact with iceberg, quit if it fails, relaunch and try again? Also in your steps what do you do to prepare? eg do you boot in virtualbox, return from sleep, or...? FYI, allocateExecutablePage uses valloc (IIRC) to get a page from the OS and then uses mprotect to add executable permission to the page before answering the pageâs address as the result of the primitive. The callback machinery then uses the page to provide the executable blue code used in implementing callbacks. The address of a code sequence in the page is what is actually handed out to C code as a fu croon pointer. When external code calls this function pointer the code in the sequence invokes a callback into the vm before returning back to C. Consequently it is key that allocateExecutablePage works correctly. If it doesnât then no callbacks. _,,,^..^,,,_ (phone) > On Sep 24, 2018, at 11:11 AM, Petr Fischer via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > <mime-attachment>

2 1

[Pharo 7.0-dev] Build #1265: 22479-Imporove-kernel-testing
by ci-pharo-ci-jenkins2＠inria.fr Sept. 25, 2018

Sept. 25, 2018

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

1 0

[ANN] Pharo Consortium upgrade to Platinum: ZWEIDENKER
by Marcus Denker Sept. 25, 2018

Sept. 25, 2018

The Pharo Consortium is very happy to announce that ZWEIDENKER has ugraded to be a Platinum member. About - ZWEIDENKER: http://zweidenker.de - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: - http://association.pharo.org

2 1

[Pharo 7.0-dev] Build #1264: 22471 prepare pharo7.0.0 rc1 release
by ci-pharo-ci-jenkins2＠inria.fr Sept. 25, 2018

Sept. 25, 2018

There is a new Pharo build available! The status of the build #1264 was: SUCCESS. The Pull Request #1817 was integrated: "22471 prepare pharo7.0.0 rc1 release" Pull request url: https://github.com/pharo-project/pharo/pull/1817 Issue Url: https://pharo.fogbugz.com/f/cases/22471 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1263: Avoid race conditions between tests by removing parallel runs
by ci-pharo-ci-jenkins2＠inria.fr Sept. 25, 2018

Sept. 25, 2018

There is a new Pharo build available! The status of the build #1263 was: SUCCESS. The Pull Request #1824 was integrated: "Avoid race conditions between tests by removing parallel runs" Pull request url: https://github.com/pharo-project/pharo/pull/1824 Issue Url: https://pharo.fogbugz.com/f/cases/22485 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Files-Core and Zinc-Character-Encoding-Core package load sequence
by Alistair Grant Sept. 25, 2018

Sept. 25, 2018

Hi Guille, Sven, Esteban and Everyone, Can someone (dis)confirm that the Zinc-Character-Encoding-Core package is considered part of the pharo "core" image? The reason I ask is that I'd like to know whether the File class (which is part of the Files-Core package) can count on ZnUTF8Encoder (which is part of the Zinc-Character-Encoding-Core package) being present in the image. If File can count on ZnUTF8Encoder being present then for FileAttributes I will make UTF8 encoding / decoding available from File, and thus UTF8 file names will be supported. If it can't count on ZnUTF8Encoder being present then File will only be able to handle ascii file names (unless the names are somehow already UTF8 encoded) and support for UTF8 file names will effectively be restricted to FileSystem. Thanks, Alistair

3 3

Re: [Pharo-dev] update linux info page again, please [CentOS/RHEL]
by Marcus Denker Sept. 25, 2018

Sept. 25, 2018

Hello, I have added it. https://pharo.org/gnu-linux-installation-64 > On 23 Sep 2018, at 18:32, Petr Fischer via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Petr Fischer <petr.fischer(a)me.com> > Subject: update linux info page again, please [CentOS/RHEL] > Date: 23 September 2018 at 18:32:00 CEST > To: pharo-dev(a)lists.pharo.org > > > Hello, > > please, edit CentOS7 installation page: > https://pharo.org/gnu-linux-installation-64 > > and add workaround for CentOS7 section, wihout this symlink, iceberg is broken: > > (do as root) > cd /usr/lib64 > ln -s libcurl.so.4 libcurl-gnutls.so.4 > > Best solution is to put this in the RPM post installation step (I mean RPM from official Pharo CentOS repository) - but we will wait for this fix for months, maybe years, so, workaround info on that page is necessary and easy to manage. > > More details here: > http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2018-July/272624… > > Thanks! pf > > >

1 0

[ANN] Pharo Consortium New Bronze Member: Spesenfuchs
by Marcus Denker Sept. 25, 2018

Sept. 25, 2018

The Pharo Consortium is very happy to announce that Spesenfuchs has joined the Consortium as a Bronze Member. About - Spesenfuchs: http://spesenfuchs.de - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: - http://association.pharo.org

1 0

Re: [Pharo-dev] iceberg PrimitiveFailed allocateExecutablePage - PharoDebug.log
by Esteban Lorenzano Sept. 24, 2018

Sept. 24, 2018

That means primAllocateExecutablePage failed. There should be an errorCode value there, that can help us understand better the problem. Can you check at it? Thanks! Esteban > On 24 Sep 2018, at 17:49, Petr Fischer via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > >

2 1

Re: [Pharo-dev] iceberg PrimitiveFailed allocateExecutablePage - corrected screenshot link
by Guillermo Polito Sept. 24, 2018

Sept. 24, 2018

This looks like an FFI error... Can you try running uFFI tests in your system and sen us the results? Tx, Guille On Sun, Sep 23, 2018 at 9:54 PM Petr Fischer via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > Ohh sorry - better screenshot link: > > > > https://app.box.com/s/isd7tdyv8lgr8aj5449xqkrxt4y4uxqy > > > > pf > > > > Hi Petr, > > > > On Sun, 23 Sep 2018 at 19:52, Petr Fischer via Pharo-dev > > <pharo-dev(a)lists.pharo.org> wrote: > > > > > > Hello, I want to propose some small fixes to Pharo, it took me hours > just to run Pharo with Iceberg on CentOS 7 (I don't care about Ubuntu)... > > > > > > Now I am stuck with this Iceberg error: > > > https://app.box.com/file/321243070589 > > > > I was presented with a login box when I tried to view this. > > > > > > > I am using 64bit Pharo VM + latest Pharo7 image from zeroconf (and > latest CentOS7) - is Iceberg OK on 64bits? > > > > Yes, I use it all the time (on Ubuntu 16.04 64 bit). > > > > Cheers, > > Alistair > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 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

2 1

Re: [Pharo-dev] iceberg PrimitiveFailed allocateExecutablePage - PharoDebug.log
by Petr Fischer Sept. 24, 2018

Sept. 24, 2018

PharoDebug.log attached pf > Ohh sorry - better screenshot link: > > https://app.box.com/s/isd7tdyv8lgr8aj5449xqkrxt4y4uxqy > > pf > > > > Hi Petr, > > > > On Sun, 23 Sep 2018 at 19:52, Petr Fischer via Pharo-dev > > <pharo-dev(a)lists.pharo.org> wrote: > > > > > > Hello, I want to propose some small fixes to Pharo, it took me hours just to run Pharo with Iceberg on CentOS 7 (I don't care about Ubuntu)... > > > > > > Now I am stuck with this Iceberg error: > > > https://app.box.com/file/321243070589 > > > > I was presented with a login box when I tried to view this. > > > > > > > I am using 64bit Pharo VM + latest Pharo7 image from zeroconf (and latest CentOS7) - is Iceberg OK on 64bits? > > > > Yes, I use it all the time (on Ubuntu 16.04 64 bit). > > > > Cheers, > > Alistair >

1 0

[Pharo 7.0-dev] Build #1262: 22465 Examples in Number>>#printShowingDecimalPlaces: should be runnable
by ci-pharo-ci-jenkins2＠inria.fr Sept. 24, 2018

Sept. 24, 2018

There is a new Pharo build available! The status of the build #1262 was: FAILURE. The Pull Request #1813 was integrated: "22465 Examples in Number>>#printShowingDecimalPlaces: should be runnable" Pull request url: https://github.com/pharo-project/pharo/pull/1813 Issue Url: https://pharo.fogbugz.com/f/cases/22465 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Next Pharo Sprint: Sept 28
by Marcus Denker Sept. 24, 2018

Sept. 24, 2018

We will organize a Pharo sprint / Moose dojo Sept 28, starting at 10:00am. (Local Time Paris). Goals of this sprint: â¢ Pharo 7 issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events Known Local Sprint meetings Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come https://association.pharo.org/event-2973620

1 0