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

Cargo
by Norbert Hartl June 22, 2018

June 22, 2018

Here comes my every-no-and-then-inquiry of the status of cargo. Is it in pharo7? Is it usable? Norbert

3 3

ESUG 2018 Innovation Technology Awards: Call for Submissions
by N. Bouraqadi June 21, 2018

June 21, 2018

Dear fellow Smalltalkers, The 15th edition of the ESUG Innovation Technology Awards is now officially open. As for every year, you can submit software based on any Smalltalk flavor, to attempt to win one of the three prizes. All you have to do is to provide a 3-5min video demo. More info and a link to the submission server is at: https://esug.github.io/2018-Conference/awardsCall2018.html On behalf of the ESUG board, Noury -- http://twitter.com/#!/NouryBouraqadi http://car.imt-lille-douai.fr/noury

1 0

Nice catchy video for covering Pharo capability
by Andrei Stebakov June 20, 2018

June 20, 2018

Could you suggest a nice video for a presentation to showcase Pharo as a nice language for data visualization? Thanks, Andrei

4 4

Voyage-UnQLite hangs on Windows
by Marco HÃ¶rning June 20, 2018

June 20, 2018

I started evaluating Voyage-UnQLite, current Pharo 6.1, Windows 10 installed: Metacello new repository: 'github://pharo-nosql/voyage/mc'; baseline: 'Voyage'; load: 'unqlite tests'. Using latest dll (Aug 10, 2016) https://github.com/pharo-nosql/PunQLite/commits/master/binary/win/unqlite.d… Basic test trying to store and reload a simple object containing a string instance variable Object subclass: #SomeTag instanceVariableNames: 'designation' SomeTag class>>isVoyageRoot ^ true Here's the Testcase code: VoyageTest>>setUp repository := VOUnQLiteRepository on: FileSystem workingDirectory / 'TestDatabase.db'. repository open VoyageTest>>tearDown repository close Running tests now: VoyageTest>>testVoyageUnQLiteStartup self assert: repository isOpen that works, db an be opened and closed. Now trying to store an object.... VoyageTest>>testVoyageUnQLiteWrite | aTag | self assert: SomeTag isVoyageRoot. aTag := SomeTag new designation:'aTag'. repository save: aTag works, if I open a Database (PunQLite) Browser it shows me the entries 'SomeTag' and 'SomeTag_0'. Trying to load the object.... VoyageTest>>testVoyageUnQLiteRead | fetchedTags | fetchedTags := repository selectAll:SomeTag that does not work. System hangs and I get a Testcase timeout with a "TestTookTooMuchTime" exception. the external call in UnQLilteFFI>>array: pArray walk: xWalk data: pUserData does not come back. Any comments or bright ideas what's wrong ? Anybody experience with Voyage-UnQLite on Windows ? Kind Regards from Germany Marco

2 1

How to contribute to Calypso when it relies on pharo-core editors?
by Tim Mackinnon June 20, 2018

June 20, 2018

Hi - so in trying to improve the sendersof/implementors of - I thought I had nailed it (and got working what I had done in Pharo 6 for Pharo 7) - but when I loaded my commit into a fresh image I realised that none of the (minor) changes I had made to Calypso had been committed. This is actually quite confusing - and its take me a while to realise that Calypso is a separate project and so when I picked commit on Pharo - this wonât pick up any of the changes in Calypsoâ¦. Arrrgggg So now Iâm guessing that I have to follow the same steps that I followed for loading a pharo repo - for Calypso? But then if I do this - and I propose some fixes to Calypso - how can it work, as it relies on some changes to older pharo core editors that its inserting from? My changes without Calypso will work (they did in V6) - but then how can someone test those in V7 as Calypso is then the default variable. Iâm in a bit of a twist - how can I proceed? Iâd really like to help improve the situation - as its bugged me for years that its a pain looking stuff up quickly (requiring you to highlight just the right stuff for very obvious things) Tim

3 4

Re: [Pharo-users] Pharo 7 proxy problem
by Vitor Medina Cruz June 19, 2018

June 19, 2018

Oh! on 32 bits version worked \o/, just tested it now. On Tue, Jun 19, 2018 at 3:43 PM, Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > I just download it using Pharo Launcher > > > > > Out of curiosity, how do I deserialize it into an image? :) > > > On Tue, Jun 19, 2018 at 3:36 PM, <Vincent.Blondeau(a)lamresearch.com> wrote: > >> Hi, >> >> >> >> Could you send the serialized stack of your primitive failure? >> >> And the version of Pharo you are using? >> >> >> >> Thanks, >> >> >> >> Vincent Blondeau >> >> >> >> *From:* Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] *On >> Behalf Of *Vitor Medina Cruz >> *Sent:* Tuesday, June 19, 2018 11:30 >> *To:* Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >> *Subject:* Re: [Pharo-users] Pharo 7 proxy problem >> >> >> >> Yes, it can resolve. >> >> >> >> On Tue, Jun 19, 2018 at 1:30 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >> have you tested your windows can resolve localhost? >> Iâm not a regular windows user, but I remember time ago this was not >> evident on windows systems. >> >> Esteban >> >> >> > On 19 Jun 2018, at 18:23, Vitor Medina Cruz <vitormcruz(a)gmail.com> >> wrote: >> > >> > Hello, >> > >> > I decided to give a try on Pharo 7 and see how iceberg is doing.... on >> windows :) >> > >> > Pharo launcher is working fine by the way â I had some problems with it >> in the past, but it seems more stable now. >> > >> > Well, if using windows isn't bad enought I am behind a proxy, so I use >> cntlm and my configuration in Pharo 6.1 for cntlm proxy on localhost works >> fine, but in 7 don't. First it seems to not recognize localhost as >> 127.0.0.1, it prompts the message: NameLookupFailure: cannot resolve >> 'localhost' >> > >> > Using 127.0.0.1 I got a PrimitiveFailure (Ick!): >> > >> > PrimitiveFailed: primitive #primSocketCreateNetwork:type: >> receiveBufferSize:sendBufSize:semaIndex:readSemaIndex:writeSemaIndex: in >> Socket failed' >> > >> > Since it is a primitive problem, I figure there is no workaround >> possible here... right? >> > >> > >> > ------------------------------------------------ >> > >> > >> > Socket(ProtoObject)>>primitiveFailed: >> > Socket(ProtoObject)>>primitiveFailed >> > Socket>>primSocketCreateNetwork:type:receiveBufferSize: >> sendBufSize:semaIndex:readSemaIndex:writeSemaIndex: >> > Socket>>initialize: >> > [ super new initialize: TCPSocketType ] in Socket class>>newTCP in >> Block: [ super new initialize: TCPSocketType ] >> > BlockClosure>>repeatWithGCIf: >> > Socket class>>newTCP >> > ZdcSocketStream class(ZdcSimpleSocketStream >> class)>>openConnectionToHost:port:timeout: >> > ZnNetworkingUtils>>socketStreamToUrlDirectly: >> > ZnNetworkingUtils>>socketStreamToProxy >> > ZnNetworkingUtils>>socketStreamToUrl: >> > ZnNetworkingUtils class>>socketStreamToUrl: >> > ZnClient>>newConnectionTo: >> > ZnClient>>getConnectionAndExecute >> > ZnClient>>executeWithRedirectsRemaining: >> > [ self executeWithRedirectsRemaining: self maxNumberOfRedirects ] in >> ZnClient>>executeWithRetriesRemaining: in Block: [ self >> executeWithRedirectsRemaining: self maxNumb...etc... >> > BlockClosure>>on:do: >> > ZnClient>>executeWithRetriesRemaining: >> > [ self executeWithRetriesRemaining: self numberOfRetries ] in [ [ self >> executeWithRetriesRemaining: self numberOfRetries ] >> > on: Error >> > do: self ifFailBlock ] in ZnClient>>executeWithTimeout in Block: [ >> self executeWithRetriesRemaining: self numberOfR...etc... >> > BlockClosure>>on:do: >> > [ [ self executeWithRetriesRemaining: self numberOfRetries ] >> > on: Error >> > do: self ifFailBlock ] in ZnClient>>executeWithTimeout in Block: [ >> [ self executeWithRetriesRemaining: self numberO...etc... >> > [ ^ block value ] in ZnClient>>withTimeoutDo: in Block: [ ^ block value >> ] >> > [ activeProcess psValueAt: index put: anObject. >> > aBlock value ] in ZnConnectionTimeout(DynamicVariable)>>value:during: >> in Block: [ activeProcess psValueAt: index put: anObject.... >> > BlockClosure>>ensure: >> > ZnConnectionTimeout(DynamicVariable)>>value:during: >> > ZnConnectionTimeout class(DynamicVariable class)>>value:during: >> > ZnClient>>withTimeoutDo: >> > ZnClient>>executeWithTimeout >> > [ result := self executeWithTimeout ] in ZnClient>>execute in Block: [ >> result := self executeWithTimeout ] >> > [ ^ block value ] in ZnClient>>withProgressDo: in Block: [ ^ block >> value ] >> > >> > Regards, >> > Vitor >> >> >> > >

2 3

Help contributing a fix to pharo - docs seem out of date again?
by Tim Mackinnon June 19, 2018

June 19, 2018

Hi - a few weeks ago, I contributed a tiny fix to Pharo 7 -and the instructions seemed to work really well. Iâve since come back to try and do some more over lunch (I was thinking Iâd like to dig out the changes I worked out for using the AST and cursor to make senders/implements work properly and not just use the selected text). My first problem was that my fork of Pharo from many months ago was out of date - I think the instructions on https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo <https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo> should probably mention this subtlety. It took me ages to figure out what to do - this was the clue (https://help.github.com/articles/syncing-a-fork/ <https://help.github.com/articles/syncing-a-fork/>) - and of particular note the the tiny bit at the bottom to ensure you Push your changes back to your GitHub fork (I slightly complicated myself by using IntelliJ to do this - doable but you need to be aware of whats going on). I did this in a separate non-pharo directory (I think thats what you would recommend right? Then you can keep updating it from time to time?) Having got my GitHub fork caught up with pharo/development - I then have the Local Repo Missing error (expected) - and now when I go to repair it I can either clone again (which is the instructions online) - or âLocate this repository in your file systemâ. As Iâve had to already check everything out to catch up to pharo/dev I chose to locate. I then get a Fetch require msg (expected) I then choose to use Fetch (Iâm not sure what the Repair repository picture is now about?) - the text does mention I will become detached, so Iâve stuck to that Iâm not sure why the âsolving a detached working copyâ is further down the page - but Iâve jumped to that It says I need to synchronise both (image and repo) - but then says its easier to do a branch - and then says a nice alternative is to create a temp branch like temp/synch - however I canât see how to do that as there is only Crete new Branch from Issue now (the picture shows that plus New Branch). Am I on the right track here? If I want try something out - do I just create myself a new issue (or is there a temp issue anyway?) Tim

3 8

Pharo 7 proxy problem
by Vitor Medina Cruz June 19, 2018

June 19, 2018

Hello, I decided to give a try on Pharo 7 and see how iceberg is doing.... on windows :) Pharo launcher is working fine by the way â I had some problems with it in the past, but it seems more stable now. Well, if using windows isn't bad enought I am behind a proxy, so I use cntlm and my configuration in Pharo 6.1 for cntlm proxy on localhost works fine, but in 7 don't. First it seems to not recognize localhost as 127.0.0.1, it prompts the message: NameLookupFailure: cannot resolve 'localhost' Using 127.0.0.1 I got a PrimitiveFailure (Ick!): PrimitiveFailed: primitive #primSocketCreateNetwork:type:receiveBufferSize:sendBufSize:semaIndex:readSemaIndex:writeSemaIndex: in Socket failed' Since it is a primitive problem, I figure there is no workaround possible here... right? ------------------------------------------------ Socket(ProtoObject)>>primitiveFailed: Socket(ProtoObject)>>primitiveFailed Socket>>primSocketCreateNetwork:type:receiveBufferSize:sendBufSize:semaIndex:readSemaIndex:writeSemaIndex: Socket>>initialize: [ super new initialize: TCPSocketType ] in Socket class>>newTCP in Block: [ super new initialize: TCPSocketType ] BlockClosure>>repeatWithGCIf: Socket class>>newTCP ZdcSocketStream class(ZdcSimpleSocketStream class)>>openConnectionToHost:port:timeout: ZnNetworkingUtils>>socketStreamToUrlDirectly: ZnNetworkingUtils>>socketStreamToProxy ZnNetworkingUtils>>socketStreamToUrl: ZnNetworkingUtils class>>socketStreamToUrl: ZnClient>>newConnectionTo: ZnClient>>getConnectionAndExecute ZnClient>>executeWithRedirectsRemaining: [ self executeWithRedirectsRemaining: self maxNumberOfRedirects ] in ZnClient>>executeWithRetriesRemaining: in Block: [ self executeWithRedirectsRemaining: self maxNumb...etc... BlockClosure>>on:do: ZnClient>>executeWithRetriesRemaining: [ self executeWithRetriesRemaining: self numberOfRetries ] in [ [ self executeWithRetriesRemaining: self numberOfRetries ] on: Error do: self ifFailBlock ] in ZnClient>>executeWithTimeout in Block: [ self executeWithRetriesRemaining: self numberOfR...etc... BlockClosure>>on:do: [ [ self executeWithRetriesRemaining: self numberOfRetries ] on: Error do: self ifFailBlock ] in ZnClient>>executeWithTimeout in Block: [ [ self executeWithRetriesRemaining: self numberO...etc... [ ^ block value ] in ZnClient>>withTimeoutDo: in Block: [ ^ block value ] [ activeProcess psValueAt: index put: anObject. aBlock value ] in ZnConnectionTimeout(DynamicVariable)>>value:during: in Block: [ activeProcess psValueAt: index put: anObject.... BlockClosure>>ensure: ZnConnectionTimeout(DynamicVariable)>>value:during: ZnConnectionTimeout class(DynamicVariable class)>>value:during: ZnClient>>withTimeoutDo: ZnClient>>executeWithTimeout [ result := self executeWithTimeout ] in ZnClient>>execute in Block: [ result := self executeWithTimeout ] [ ^ block value ] in ZnClient>>withProgressDo: in Block: [ ^ block value ] Regards, Vitor

3 3

[ANN] TechTalk Dates second half 2018
by Marcus Denker June 19, 2018

June 19, 2018

Here are the next dates for the Pharo Techtalks. 12 Jul 2018: Pharo TechTalk: Machine Learning with TensorFlow and Pharo https://association.pharo.org/event-2973748 For the others we have no topic yet, but dates are pre-fixed to: 23 Aug 2018: Pharo TechTalk https://association.pharo.org/event-2973753 11 Oct 2018: Pharo TechTalk https://association.pharo.org/event-2973754 15 Nov 2018: Pharo TechTalk https://association.pharo.org/event-2973755 13 Dec 2018: Pharo TechTalk https://association.pharo.org/event-2973756 We are looking for topics! â¢ If you have ideas for topics, please tell us! â¢ With no topic, we will use this slot for a general free discussion. â¢ If you want to do a TechTalk about a topic but no date is good, we can change the date! For recording of the past ones, see: http://pharo.org/TechTalk

1 0

[Ann] Iceberg v1.1.1
by Guillermo Polito June 19, 2018

June 19, 2018

Hi everybody, This week we have a small patch release of Iceberg, version v1.1.1. This version will be available in the next Pharo build. In summary, this release fixes two issues with the new credentials manager, and introduces a couple of other enhancements/bugfixes. Below you will find the detailed changes log. Enjoy, Guille Integrate Iceberg 1.1.1 https://pharo.fogbugz.com/f/cases/22168/Integrate-Iceberg-1-1-1 https://github.com/pharo-vcs/iceberg/releases/tag/v1.1.1 #864 <https://github.com/pharo-project/pharo/pull/864> Repairing Missing repositories lead to wrong source directory #861 <https://github.com/pharo-project/pharo/pull/861> update tonel to v1.0.9 #836 <https://github.com/pharo-project/pharo/pull/836> DefaultBackendType class variable is unused #862 <https://github.com/pharo-project/pharo/pull/862> Iceberg tests are not running in Pharo 7 #852 <https://github.com/pharo-project/pharo/pull/852> Make error dialogs copy-pastable #858 <https://github.com/pharo-project/pharo/pull/858> IceTipReadOnlyTextMorph does not allow select and copy anymore #850 <https://github.com/pharo-project/pharo/pull/850> Change Detached head status from error to warning if we are on a tag #853 <https://github.com/pharo-project/pharo/pull/853> Clone dialog "username" is confusing #860 <https://github.com/pharo-project/pharo/pull/860> CredentialStore API #854 <https://github.com/pharo-project/pharo/pull/854> Error in History window -- 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

5 8