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

Re: [Pharo-users] ZnClient 403 but 200 in Firefox

by Sven Van Caekenberghe

Because they don't like Pharo or Zinc ;-) ZnClient new systemPolicy; beOneShot; url: 'http://ifconfig.me/ip'; accept: ZnMimeType textPlain; headerAt: 'User-Agent' put: 'curl/7.54.0'; get. Changing the User-Agent (effectively lying) works. > On 10 Oct 2018, at 22:02, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > When I visit this site http://ifconfig.me/ip using the web browser I > get the expected text output. However if I try to do it from Pharo 6.1 > (Windows 8.1) I get a 403 forbidden response using this code: > > ZnClient new > systemPolicy; > beOneShot; > accept: ZnMimeType textPlain; > timeout: 6000; > url: 'http://ifconfig.me/ip'; > get. > > 2018-09-16 03:06:18 011 Retrying ConnectionTimedOut: Cannot connect to > 153.121.72.212:80 > 2018-09-16 03:06:19 012 Connection Established ifconfig.me:80 > 153.121.72.212 288ms > 2018-09-16 03:06:19 013 Request Written a ZnRequest(GET /all.xml) 1ms > 2018-09-16 03:06:19 014 Response Read a ZnResponse(403 Forbidden > text/html;charset=iso-8859-1 209B) 318ms > 2018-09-16 03:06:19 015 GET /all.xml 403 209B 319ms > 2018-09-16 03:06:19 016 Connection Closed 153.121.72.212:80 > > In Firefox this is the output > > Request Headers Firefox: > > Host: ifconfig.me > User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:62.0) > Gecko/20100101 Firefox/62.0 > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 > Accept-Language: en-US > Accept-Encoding: gzip, deflate > DNT: 1 > Connection: keep-alive > Upgrade-Insecure-Requests: 1 > > Response Headers Firefox: > > HTTP/1.1 200 OK > Date: Sun, 16 Sep 2018 16:47:02 GMT > Server: Apache > Vary: Accept-Encoding > Content-Encoding: gzip > Content-Length: 32 > Connection: close > Content-Type: text/plain > > > Any idea? > > Cheers, > > HernÃ¡n >

Oct. 10, 2018

ZnClient 403 but 200 in Firefox

by HernÃ¡n Morales Durand

When I visit this site http://ifconfig.me/ip using the web browser I get the expected text output. However if I try to do it from Pharo 6.1 (Windows 8.1) I get a 403 forbidden response using this code: ZnClient new systemPolicy; beOneShot; accept: ZnMimeType textPlain; timeout: 6000; url: 'http://ifconfig.me/ip'; get. 2018-09-16 03:06:18 011 Retrying ConnectionTimedOut: Cannot connect to 153.121.72.212:80 2018-09-16 03:06:19 012 Connection Established ifconfig.me:80 153.121.72.212 288ms 2018-09-16 03:06:19 013 Request Written a ZnRequest(GET /all.xml) 1ms 2018-09-16 03:06:19 014 Response Read a ZnResponse(403 Forbidden text/html;charset=iso-8859-1 209B) 318ms 2018-09-16 03:06:19 015 GET /all.xml 403 209B 319ms 2018-09-16 03:06:19 016 Connection Closed 153.121.72.212:80 In Firefox this is the output Request Headers Firefox: Host: ifconfig.me User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-US Accept-Encoding: gzip, deflate DNT: 1 Connection: keep-alive Upgrade-Insecure-Requests: 1 Response Headers Firefox: HTTP/1.1 200 OK Date: Sun, 16 Sep 2018 16:47:02 GMT Server: Apache Vary: Accept-Encoding Content-Encoding: gzip Content-Length: 32 Connection: close Content-Type: text/plain Any idea? Cheers, HernÃ¡n

Oct. 10, 2018

Re: [Pharo-users] [ANN] Cryptography moved to pharo-contributions

by Norbert Hartl

No, that you cannot > Am 10.10.2018 um 16:36 schrieb Sean P. DeNigris <sean(a)clipperadams.com>: > > NorbertHartl wrote >> The rest is provided by github as long as you do not create a new >> repository with the same name. > > Can you still fork the transferred repo in your personal account? I wasn't > sure, which is why I didn't handle Artefact this way. > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Oct. 10, 2018

Re: [Pharo-users] [ANN] Migrated Artefact to GitHub

by Cyril Ferlicot

On Wed, Oct 10, 2018 at 4:37 PM Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Sean P. DeNigris wrote > > I migrated the > > repo with the hopes that someone in the pharo-contributions organization > > will copy it. > > [snip] > > https://github.com/seandenigris/Artefact > > Bump. Anyone? I will do it if you add me to pharo-contributionsâ¦ > Hi Sean, Apparently we both moved Artefact to github at the same time. This repo contains the project: https://github.com/pharo-contributions/Artefact It has: - Migrated sources - A new Baseline - I also moved Stylesheet to github - I updated the dependency to Units to point to the one of Zweidenker - Guille fixed the streams problem Now we have only one Pharo 7 test failing. I wanted to correct it before releasing. > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > -- Cyril Ferlicot https://ferlicot.fr

Oct. 10, 2018

Re: [Pharo-users] [Seaside] [ANN] MaterialDesignLite for Seaside v1.3.0

by Cyril Ferlicot

On Wed, Oct 10, 2018 at 10:46 AM Pierce Ng <pierce(a)samadhiweb.com> wrote: > > > Hi Cyril, > > In a Pharo 60541 image with Seaside already loaded, loading MDL resulted > in dependency mismatch error. I resolved (ahem) it the expedient way, by > commenting out the Seaside dependency in BaselineOfMaterialDesignLite. > It is now running and looks very nice! > > Is there a way to specify the dependency more flexibly? > > Seaside was loaded thusly: > > Metacello new > repository: 'github://SeasideSt/Seaside:master/repository'; > baseline: 'Seaside3'; > load. > > MDL: > > Metacello new > githubUser: 'DuneSt' project: 'MaterialDesignLite' commitish: 'v1.3.0' path: 'src'; > baseline: 'MaterialDesignLite'; > onWarningLog; > load. > Hi Pierce, I tried to execute this on my image: Metacello new repository: 'github://SeasideSt/Seaside:master/repository'; baseline: 'Seaside3'; load. Metacello new githubUser: 'DuneSt' project: 'MaterialDesignLite' commitish: 'v1.3.0' path: 'src'; baseline: 'MaterialDesignLite'; onWarningLog; load. It worked for me. I tried in the latest Pharo 7 and also in Pharo 6.1. We should have a missmatch only if there is a version of Seaside from StHub loaded in the image. Can someone else try it? > Pierce > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside -- Cyril Ferlicot https://ferlicot.fr

Oct. 10, 2018

Re: [Pharo-users] [ANN] Cryptography moved to pharo-contributions

by Sean P. DeNigris

NorbertHartl wrote > The rest is provided by github as long as you do not create a new > repository with the same name. Can you still fork the transferred repo in your personal account? I wasn't sure, which is why I didn't handle Artefact this way. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 10, 2018

Re: [Pharo-users] [ANN] Migrated Artefact to GitHub

by Sean P. DeNigris

Sean P. DeNigris wrote > I migrated the > repo with the hopes that someone in the pharo-contributions organization > will copy it. > [snip] > https://github.com/seandenigris/Artefact Bump. Anyone? I will do it if you add me to pharo-contributionsâ¦ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 10, 2018

Re: [Pharo-users] Why is the root class of tests named TestAsserter?

by James Foster

Hi Abdelghani, I donât have immediate access to earlier versions of SUnit (oh, that it were on GitHub!), but my recollection is that TestCase was originally a root class but duplicate code with TestResource inspired a refactoring that called for a common superclass. The name TestAsserter was chosen to reflect the common behavior. James > On Oct 9, 2018, at 8:12 AM, Alidra Abdelghani via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Alidra Abdelghani <alidrandco(a)yahoo.fr> > Subject: Why is the root class of tests named TestAsserter? > Date: October 9, 2018 at 8:12:11 AM PDT > To: pharo-users(a)lists.pharo.org > > > Hi, > > I am trying to understand how classes in smalltalk projects are named. > Something I can hardly understand is why the root class of the Test hierarchy is named TestAsserter? > What is the intention behind the term Asserter? > Wouldnât it be more appropriate to name it AbstractTest since most classes of this hierarchy are Tests? > > Many thanks in advance > Abdelghani > > >

Oct. 10, 2018

Re: [Pharo-users] Glorp with P3

by Sven Van Caekenberghe

> On 10 Oct 2018, at 14:33, Craig <craig(a)hivemind.net> wrote: > > Sven, > > I just ported everything to Pharo 7.0 and the problem disappeared. > > Craig OK, good to know, but 6.1 should be compatible AFAIK. > -----Original Message----- > From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Sven Van Caekenberghe > Sent: Wednesday, 10 October 2018 11:13 > To: Any question about pharo is welcome > Subject: Re: [Pharo-users] Glorp with P3 > > Craig, > > I tried in a clean Pharo-7.0.0+alpha.build.1276.sha.6c09bd43bb0d76c18958c720649aaf6834870bb5 (64 Bit). > > Load expression (as per https://github.com/svenvc/P3) which also loads Glorp itself: > > Metacello new > baseline: 'P3'; > repository: 'github://svenvc/P3'; > load: 'glorp'. > > Transcript log: > > Fetched -> BaselineOfP3-CompatibleUserName.1539011881 --- git@github.com:svenvc/P3.git[master] --- git@github.com:svenvc/P3.git[master] > Loaded -> BaselineOfP3-CompatibleUserName.1539011881 --- git@github.com:svenvc/P3.git[master] --- git@github.com:svenvc/P3.git[master] > Loading baseline of BaselineOfP3... > Fetched -> BaselineOfZTimestamp-CompatibleUserName.1538577426 --- git@github.com:svenvc/ztimestamp.git[master] --- git@github.com:svenvc/ztimestamp.git[master] > Loaded -> BaselineOfZTimestamp-CompatibleUserName.1538577426 --- git@github.com:svenvc/ztimestamp.git[master] --- git@github.com:svenvc/ztimestamp.git[master] > Fetched -> BaselineOfNeoJSON-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- git@github.com:svenvc/NeoJSON.git[master] > Loaded -> BaselineOfNeoJSON-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- git@github.com:svenvc/NeoJSON.git[master] > ...RETRY->ConfigurationOfGlorp > Fetched -> ConfigurationOfGlorp-StephanEggermont.62 --- http://smalltalkhub.com/mc/DBXTalk/Configurations/main/ --- http://smalltalkhub.com/mc/DBXTalk/Configurations/main/ > Loaded -> ConfigurationOfGlorp-StephanEggermont.62 --- http://smalltalkhub.com/mc/DBXTalk/Configurations/main/ --- http://smalltalkhub.com/mc/DBXTalk/Configurations/main/ > Project: NeoJSON baseline > Fetched -> Neo-JSON-Core-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- git@github.com:svenvc/NeoJSON.git[master] > Fetched -> Neo-JSON-Tests-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- git@github.com:svenvc/NeoJSON.git[master] > Fetched -> Neo-JSON-Pharo-Core-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- git@github.com:svenvc/NeoJSON.git[master] > Fetched -> Neo-JSON-Pharo-Tests-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- git@github.com:svenvc/NeoJSON.git[master] > Project: ZTimestamp baseline > Fetched -> ZTimestamp-CompatibleUserName.1538577426 --- git@github.com:svenvc/ztimestamp.git[master] --- git@github.com:svenvc/ztimestamp.git[master] > Project: Glorp stable [2.0.1] > Fetched -> Glorp-HerbyVojcik.127 --- http://smalltalkhub.com/mc/DBXTalk/Glorp/main/ --- http://smalltalkhub.com/mc/DBXTalk/Glorp/main/ > Fetched -> Glorp-Tests-PierceNg.21 --- http://smalltalkhub.com/mc/DBXTalk/Glorp/main/ --- http://smalltalkhub.com/mc/DBXTalk/Glorp/main/ > Fetched -> P3-CompatibleUserName.1539011881 --- git@github.com:svenvc/P3.git[master] --- git@github.com:svenvc/P3.git[master] > Fetched -> P3-Glorp-CompatibleUserName.1539011881 --- git@github.com:svenvc/P3.git[master] --- git@github.com:svenvc/P3.git[master] > Loaded -> Neo-JSON-Core-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- cache > Loaded -> Neo-JSON-Tests-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- cache > Loaded -> Neo-JSON-Pharo-Core-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- cache > Loaded -> Neo-JSON-Pharo-Tests-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- cache > Loaded -> ZTimestamp-CompatibleUserName.1538577426 --- git@github.com:svenvc/ztimestamp.git[master] --- cache > Starting atomic load > MessageArchiver class>>inspectorClass (EyeProtoInspector is Undeclared) > > Dialect class>>reset (identitySetClass is Undeclared) > > DB2Sequence>>name: (DB2Platform is Undeclared) > > Loaded -> Glorp-HerbyVojcik.127 --- http://smalltalkhub.com/mc/DBXTalk/Glorp/main/ --- cache > Loaded -> Glorp-Tests-PierceNg.21 --- http://smalltalkhub.com/mc/DBXTalk/Glorp/main/ --- cache > Finished atomic load > Evaluated -> 2.0.1 [ConfigurationOfGlorp] >> resetDialect > Loaded -> P3-CompatibleUserName.1539011881 --- git@github.com:svenvc/P3.git[master] --- cache > Loaded -> P3-Glorp-CompatibleUserName.1539011881 --- git@github.com:svenvc/P3.git[master] --- cache > ...finished baseline > > Then set the driver using: > > PharoDatabaseAccessor DefaultDriver: P3DatabaseDriver. > > Next configure the unit tests (login resource) via: > > GlorpDatabaseLoginResource defaultLogin: (Login new > database: PostgreSQLPlatform new; > username: 'sven'; > password: ''; > connectString: 'localhost:5432_sven'; > encodingStrategy: #utf8; > yourself). > > I now have green tests, for example GlorpTableTest, GlorpDatabaseLoginTest, GlorpDatabaseBasicTest. I know that the actual PSQL DB that I am using has all the Glorp test tables in it, I forgot whether that happened automatically or not. > > As for the full test suite, if I exclude GlorpReadingTest I get > > 804 run, 788 passes, 4 skipped, 0 expected failures, 0 failures, 16 errors, 0 unexpected passes > > Which is not too bad for such a complex package. > > HTH, > > Sven > >> On 10 Oct 2018, at 09:36, Craig <craig(a)hivemind.net> wrote: >> >> Hi Sven, >> >> Thanks for the support. >> >> I'm using Pharo 6.1 - 32bit stable. >> >> Craig >> >> -----Original Message----- >> From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Sven Van Caekenberghe >> Sent: Wednesday, 10 October 2018 08:56 >> To: Any question about pharo is welcome >> Subject: Re: [Pharo-users] Glorp with P3 >> >> Hi Craig, >> >> Last time I checked, this worked fine. I'll try again later today, what version of Pharo are you using ? >> >> Sven >> >>> On 9 Oct 2018, at 15:43, Craig <craig(a)hivemind.net> wrote: >>> >>> Hi All, >>> >>> I installed Glorp with P3 using the snippet on the P3 Github page. >>> >>> P3 seems to be working fine. The tests are Ok. While working through the Glorp book, I got as far as âsession createTablesâ and then got a debugger window. >>> >>> It seems that the SQL is being sent to a variable in the PharoDatabaseAccessor class - âdatabaseDriverâ which is never initialised. >>> >>> Anybody able to assist with this? >>> >>> Craig >> >> >> >> > > > >

Oct. 10, 2018

Re: [Pharo-users] Glorp with P3

by Craig

Sven, I just ported everything to Pharo 7.0 and the problem disappeared. Craig -----Original Message----- From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Sven Van Caekenberghe Sent: Wednesday, 10 October 2018 11:13 To: Any question about pharo is welcome Subject: Re: [Pharo-users] Glorp with P3 Craig, I tried in a clean Pharo-7.0.0+alpha.build.1276.sha.6c09bd43bb0d76c18958c720649aaf6834870bb5 (64 Bit). Load expression (as per https://github.com/svenvc/P3) which also loads Glorp itself: Metacello new baseline: 'P3'; repository: 'github://svenvc/P3'; load: 'glorp'. Transcript log: Fetched -> BaselineOfP3-CompatibleUserName.1539011881 --- git@github.com:svenvc/P3.git[master] --- git@github.com:svenvc/P3.git[master] Loaded -> BaselineOfP3-CompatibleUserName.1539011881 --- git@github.com:svenvc/P3.git[master] --- git@github.com:svenvc/P3.git[master] Loading baseline of BaselineOfP3... Fetched -> BaselineOfZTimestamp-CompatibleUserName.1538577426 --- git@github.com:svenvc/ztimestamp.git[master] --- git@github.com:svenvc/ztimestamp.git[master] Loaded -> BaselineOfZTimestamp-CompatibleUserName.1538577426 --- git@github.com:svenvc/ztimestamp.git[master] --- git@github.com:svenvc/ztimestamp.git[master] Fetched -> BaselineOfNeoJSON-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- git@github.com:svenvc/NeoJSON.git[master] Loaded -> BaselineOfNeoJSON-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- git@github.com:svenvc/NeoJSON.git[master] ...RETRY->ConfigurationOfGlorp Fetched -> ConfigurationOfGlorp-StephanEggermont.62 --- http://smalltalkhub.com/mc/DBXTalk/Configurations/main/ --- http://smalltalkhub.com/mc/DBXTalk/Configurations/main/ Loaded -> ConfigurationOfGlorp-StephanEggermont.62 --- http://smalltalkhub.com/mc/DBXTalk/Configurations/main/ --- http://smalltalkhub.com/mc/DBXTalk/Configurations/main/ Project: NeoJSON baseline Fetched -> Neo-JSON-Core-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- git@github.com:svenvc/NeoJSON.git[master] Fetched -> Neo-JSON-Tests-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- git@github.com:svenvc/NeoJSON.git[master] Fetched -> Neo-JSON-Pharo-Core-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- git@github.com:svenvc/NeoJSON.git[master] Fetched -> Neo-JSON-Pharo-Tests-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- git@github.com:svenvc/NeoJSON.git[master] Project: ZTimestamp baseline Fetched -> ZTimestamp-CompatibleUserName.1538577426 --- git@github.com:svenvc/ztimestamp.git[master] --- git@github.com:svenvc/ztimestamp.git[master] Project: Glorp stable [2.0.1] Fetched -> Glorp-HerbyVojcik.127 --- http://smalltalkhub.com/mc/DBXTalk/Glorp/main/ --- http://smalltalkhub.com/mc/DBXTalk/Glorp/main/ Fetched -> Glorp-Tests-PierceNg.21 --- http://smalltalkhub.com/mc/DBXTalk/Glorp/main/ --- http://smalltalkhub.com/mc/DBXTalk/Glorp/main/ Fetched -> P3-CompatibleUserName.1539011881 --- git@github.com:svenvc/P3.git[master] --- git@github.com:svenvc/P3.git[master] Fetched -> P3-Glorp-CompatibleUserName.1539011881 --- git@github.com:svenvc/P3.git[master] --- git@github.com:svenvc/P3.git[master] Loaded -> Neo-JSON-Core-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- cache Loaded -> Neo-JSON-Tests-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- cache Loaded -> Neo-JSON-Pharo-Core-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- cache Loaded -> Neo-JSON-Pharo-Tests-CompatibleUserName.1538429427 --- git@github.com:svenvc/NeoJSON.git[master] --- cache Loaded -> ZTimestamp-CompatibleUserName.1538577426 --- git@github.com:svenvc/ztimestamp.git[master] --- cache Starting atomic load MessageArchiver class>>inspectorClass (EyeProtoInspector is Undeclared) Dialect class>>reset (identitySetClass is Undeclared) DB2Sequence>>name: (DB2Platform is Undeclared) Loaded -> Glorp-HerbyVojcik.127 --- http://smalltalkhub.com/mc/DBXTalk/Glorp/main/ --- cache Loaded -> Glorp-Tests-PierceNg.21 --- http://smalltalkhub.com/mc/DBXTalk/Glorp/main/ --- cache Finished atomic load Evaluated -> 2.0.1 [ConfigurationOfGlorp] >> resetDialect Loaded -> P3-CompatibleUserName.1539011881 --- git@github.com:svenvc/P3.git[master] --- cache Loaded -> P3-Glorp-CompatibleUserName.1539011881 --- git@github.com:svenvc/P3.git[master] --- cache ...finished baseline Then set the driver using: PharoDatabaseAccessor DefaultDriver: P3DatabaseDriver. Next configure the unit tests (login resource) via: GlorpDatabaseLoginResource defaultLogin: (Login new database: PostgreSQLPlatform new; username: 'sven'; password: ''; connectString: 'localhost:5432_sven'; encodingStrategy: #utf8; yourself). I now have green tests, for example GlorpTableTest, GlorpDatabaseLoginTest, GlorpDatabaseBasicTest. I know that the actual PSQL DB that I am using has all the Glorp test tables in it, I forgot whether that happened automatically or not. As for the full test suite, if I exclude GlorpReadingTest I get 804 run, 788 passes, 4 skipped, 0 expected failures, 0 failures, 16 errors, 0 unexpected passes Which is not too bad for such a complex package. HTH, Sven > On 10 Oct 2018, at 09:36, Craig <craig(a)hivemind.net> wrote: > > Hi Sven, > > Thanks for the support. > > I'm using Pharo 6.1 - 32bit stable. > > Craig > > -----Original Message----- > From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Sven Van Caekenberghe > Sent: Wednesday, 10 October 2018 08:56 > To: Any question about pharo is welcome > Subject: Re: [Pharo-users] Glorp with P3 > > Hi Craig, > > Last time I checked, this worked fine. I'll try again later today, what version of Pharo are you using ? > > Sven > >> On 9 Oct 2018, at 15:43, Craig <craig(a)hivemind.net> wrote: >> >> Hi All, >> >> I installed Glorp with P3 using the snippet on the P3 Github page. >> >> P3 seems to be working fine. The tests are Ok. While working through the Glorp book, I got as far as âsession createTablesâ and then got a debugger window. >> >> It seems that the SQL is being sent to a variable in the PharoDatabaseAccessor class - âdatabaseDriverâ which is never initialised. >> >> Anybody able to assist with this? >> >> Craig > > > >

Oct. 10, 2018