August 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] including Pillar in Pharo image by default

by Stephane Ducasse

Hi tim I personally do not care much about the syntax but I care about what I can do with it (ref, cite, ... ) I cannot write books in markdown because reference to figures!!!!!! were missing. And of course a parser because markdown is not really nice to parse and I will not write a parser because I have something else to do. I want to make pillar smaller, simpler, nicer. Now if someone come up with a parser that parse for REAL a markdown that can be extended with decent behavior (figure reference, section reference, cite) and can be extended because there are many things that can be nice to have (for example I want to be able to write the example below) and emit a PillarModel (AST) we can talk to have another syntax for Pillar but not before. [[[test 2+3 >>> 5 ]]] and being able to verify that the doc is in sync. Stef On Sat, Aug 12, 2017 at 12:37 AM, Tim Mackinnon <tim(a)testit.works> wrote: > Of course, I/we recognise and appreciate all the work that's gone into docs in pillar - but I think it should be reasonably straightforward to write a converter as it is pretty closely related from what I have seen. > > So I don't make the suggestion flippantly, and would want to help write a converter and get us to a common ground where we can differentiate on the aspects where we can excel. > > Tim > > Sent from my iPhone > >> On 11 Aug 2017, at 23:21, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >> >> A long time issue with Markdown was that there was no standardization (and when I used Pillar's MD export ~2 years ago it didn't work well). >> >> However CommonMark ( http://spec.commonmark.org/0.28/ ) has become the de-facto standard, so it would make sense to support it bidirectionally with Pillar. >> >>> The readme.md that Peter is talking about is gfm markdown >> >> Well, technically it is just a CommonMark, as I am not using any github extensions. >> (Github uses CommonMarks and adds just couple small extensions.) >> >> Peter >> > >

Aug. 13, 2017

Re: [Pharo-users] pharo config problem

by Johannes Brauer

Hi Stef, the connection from a Monticello Browser in a local image with same username and password works fine. Johannes > Am 13.08.2017 um 20:34 schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: > > Hi johannes > > I do not know how to help you but this is strange. > We managed our synectique private code on STHub and it works. > Now STHub is getting stranger and stranger. So may be your passwrd got desync. > Esteban? if you read this mail. Can you check when you are back from vacation? > > Stef > > On Sun, Aug 13, 2017 at 7:20 PM, jb <brauer(a)nordakademie.de> wrote: >> Hi, >> >> I have a problem with connection to a private smalltalkhub rep from the >> command line with pharo config. >> I think I set the --username and --password options correctly, but I always >> get: >> ZnHttpUnsuccessful: 403 Forbidded >> >> If I make the rep public then there is no access problem. >> >> Any hints what is going wrong? >> >> Johannes >> >> >> >> -- >> View this message in context: http://forum.world.st/pharo-config-problem-tp4960715.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >

Aug. 13, 2017

Re: [Pharo-users] Probably a bug in Garage SQLite

by Herby VojÄÃk

Stephane Ducasse wrote: > Do you have the same bug in 5.0? > Because I do not know if garage was really tested on 60. Don't know (don't have it), but last commit in Garage-SQLite GuillermoPolito.26 from 2016. The mentioned #nbBindingOf: is sent at no place at all in the image (except supersend in the lone method itself), so it definitely looks like it need to rename to ffiBindingOf: for 60. Herby > > Stef > > On Sun, Aug 13, 2017 at 8:41 PM, Herby VojÄÃk<herby(a)mailbox.sk> wrote: >> Stephane Ducasse wrote: >>> Hi Herby >>> >>> On which version of Pharo are you trying? Because lot of changes >>> happened on Pharo 60 FFI. >>> >>> Stef >>> >>> On Sun, Aug 13, 2017 at 6:11 PM, Herby VojÄÃk<herby(a)mailbox.sk> wrote: >>>> Hello! >>>> >>>> This testing code: >>>> >>>> | databaseFile login accessor sqlString | >>>> databaseFile := Smalltalk imageDirectory asFileReference / >>>> 'play.sqlite'. >>>> login := Login new >>>> database: SQLite3Platform new; >>>> host: ''; >>>> port: ''; >>>> username: ''; >>>> password: ''; >>>> databaseName: databaseFile fullPath asZnUrl >>>> asString; >>>> yourself. >>>> accessor := DatabaseAccessor forLogin: login. >>>> accessor login. >>>> sqlString := 'SELECT * FROM AGENT'. >>>> (accessor basicExecuteSQLString: sqlString) contents inspect. >>>> >>>> fails (Pharo 6.1, GarageGlorp #stable loaded a week ago as a project >> >> As I wrote here, Pharo 6.1. >> >> >>>> dependency) with: >>>> >>>> Error: Unable to resolve external type: sqlite3 >>>> >>>> FFICallout(Object)>>error: >>>> FFICallout>>resolveType: >>>> FFICallout>>typeName:pointerArity: >>>> FFICallout>>argName:indirectIndex:type:ptrArity: >>>> FFIFunctionParser>>parseArgument >>>> FFIFunctionParser>>parseArguments >>>> FFIFunctionParser>>parseNamedFunction: >>>> FFICalloutMethodBuilder>>parseSignature: >>>> FFICalloutMethodBuilder>>generate >>>> FFICalloutMethodBuilder>>build: >>>> FFICalloutAPI>>function:module: >>>> GASqlite3FFI(Object)>>ffiCall:module: >>>> GASqlite3FFI>>apiErrorMessage: >>>> GASqlite3FFI>>signal:with:on: >>>> GASqlite3FFI>>checkForOk:on: >>>> GASqlite3FFI>>prepare:on:with: >>>> GASqlite3Statement>>prepare >>>> GASqlite3Driver>>prepare: >>>> GASqlite3ResultSet>>prepareStatement: >>>> GASqlite3ResultSet>>execute:withCollection: >>>> GASqlite3ResultSet>>execute:with:on: >>>> GASqlite3Driver>>execute:with: >>>> GASqlite3Driver>>execute: >>>> GAGlorpDriver>>basicExecuteSQLString: >>>> PharoDatabaseAccessor>>basicExecuteSQLString: >>>> UndefinedObject>>DoIt >>>> OpalCompiler>>evaluate >>>> [..snip..] >>>> >>>> Problem seems to be that in FFICallout>> resolveType:, the line >>>> >>>> binding := resolver ffiBindingOf: name asSymbol. >>>> >>>> actually produces nil, resolver being GASqlite3FFI class. If looking at >>>> the >>>> class side of GaSqlite3FFI, there is no ffiBindingOf: at all; there is >>>> >>>> nbBindingOf: aTypeName >>>> ^ TypeMap at: aTypeName ifAbsent: [ super nbBindingOf: aTypeName >>>> ] >>>> >>>> though. If I copy near-mindlessly and add: >>>> >>>> ffiBindingOf: aTypeName >>>> ^ TypeMap at: aTypeName ifAbsent: [ super ffiBindingOf: >>>> aTypeName ] >>>> >>>> then the code above fails correctly with: 'no such table: AGENT'. >>>> >>>> Am I missing some nb<->ffi bridge? Or is there a bug in Garage SQLite >>>> driver? >>>> >>>> Herby >> >

Aug. 13, 2017

Re: [Pharo-users] Probably a bug in Garage SQLite

by Stephane Ducasse

Do you have the same bug in 5.0? Because I do not know if garage was really tested on 60. Stef On Sun, Aug 13, 2017 at 8:41 PM, Herby VojÄÃk <herby(a)mailbox.sk> wrote: > Stephane Ducasse wrote: >> >> Hi Herby >> >> On which version of Pharo are you trying? Because lot of changes >> happened on Pharo 60 FFI. >> >> Stef >> >> On Sun, Aug 13, 2017 at 6:11 PM, Herby VojÄÃk<herby(a)mailbox.sk> wrote: >>> >>> Hello! >>> >>> This testing code: >>> >>> | databaseFile login accessor sqlString | >>> databaseFile := Smalltalk imageDirectory asFileReference / >>> 'play.sqlite'. >>> login := Login new >>> database: SQLite3Platform new; >>> host: ''; >>> port: ''; >>> username: ''; >>> password: ''; >>> databaseName: databaseFile fullPath asZnUrl >>> asString; >>> yourself. >>> accessor := DatabaseAccessor forLogin: login. >>> accessor login. >>> sqlString := 'SELECT * FROM AGENT'. >>> (accessor basicExecuteSQLString: sqlString) contents inspect. >>> >>> fails (Pharo 6.1, GarageGlorp #stable loaded a week ago as a project > > > As I wrote here, Pharo 6.1. > > >>> dependency) with: >>> >>> Error: Unable to resolve external type: sqlite3 >>> >>> FFICallout(Object)>>error: >>> FFICallout>>resolveType: >>> FFICallout>>typeName:pointerArity: >>> FFICallout>>argName:indirectIndex:type:ptrArity: >>> FFIFunctionParser>>parseArgument >>> FFIFunctionParser>>parseArguments >>> FFIFunctionParser>>parseNamedFunction: >>> FFICalloutMethodBuilder>>parseSignature: >>> FFICalloutMethodBuilder>>generate >>> FFICalloutMethodBuilder>>build: >>> FFICalloutAPI>>function:module: >>> GASqlite3FFI(Object)>>ffiCall:module: >>> GASqlite3FFI>>apiErrorMessage: >>> GASqlite3FFI>>signal:with:on: >>> GASqlite3FFI>>checkForOk:on: >>> GASqlite3FFI>>prepare:on:with: >>> GASqlite3Statement>>prepare >>> GASqlite3Driver>>prepare: >>> GASqlite3ResultSet>>prepareStatement: >>> GASqlite3ResultSet>>execute:withCollection: >>> GASqlite3ResultSet>>execute:with:on: >>> GASqlite3Driver>>execute:with: >>> GASqlite3Driver>>execute: >>> GAGlorpDriver>>basicExecuteSQLString: >>> PharoDatabaseAccessor>>basicExecuteSQLString: >>> UndefinedObject>>DoIt >>> OpalCompiler>>evaluate >>> [..snip..] >>> >>> Problem seems to be that in FFICallout>> resolveType:, the line >>> >>> binding := resolver ffiBindingOf: name asSymbol. >>> >>> actually produces nil, resolver being GASqlite3FFI class. If looking at >>> the >>> class side of GaSqlite3FFI, there is no ffiBindingOf: at all; there is >>> >>> nbBindingOf: aTypeName >>> ^ TypeMap at: aTypeName ifAbsent: [ super nbBindingOf: aTypeName >>> ] >>> >>> though. If I copy near-mindlessly and add: >>> >>> ffiBindingOf: aTypeName >>> ^ TypeMap at: aTypeName ifAbsent: [ super ffiBindingOf: >>> aTypeName ] >>> >>> then the code above fails correctly with: 'no such table: AGENT'. >>> >>> Am I missing some nb<->ffi bridge? Or is there a bug in Garage SQLite >>> driver? >>> >>> Herby > >

Aug. 13, 2017

Re: [Pharo-users] Probably a bug in Garage SQLite

by Herby VojÄÃk

Stephane Ducasse wrote: > Hi Herby > > On which version of Pharo are you trying? Because lot of changes > happened on Pharo 60 FFI. > > Stef > > On Sun, Aug 13, 2017 at 6:11 PM, Herby VojÄÃk<herby(a)mailbox.sk> wrote: >> Hello! >> >> This testing code: >> >> | databaseFile login accessor sqlString | >> databaseFile := Smalltalk imageDirectory asFileReference / >> 'play.sqlite'. >> login := Login new >> database: SQLite3Platform new; >> host: ''; >> port: ''; >> username: ''; >> password: ''; >> databaseName: databaseFile fullPath asZnUrl >> asString; >> yourself. >> accessor := DatabaseAccessor forLogin: login. >> accessor login. >> sqlString := 'SELECT * FROM AGENT'. >> (accessor basicExecuteSQLString: sqlString) contents inspect. >> >> fails (Pharo 6.1, GarageGlorp #stable loaded a week ago as a project As I wrote here, Pharo 6.1. >> dependency) with: >> >> Error: Unable to resolve external type: sqlite3 >> >> FFICallout(Object)>>error: >> FFICallout>>resolveType: >> FFICallout>>typeName:pointerArity: >> FFICallout>>argName:indirectIndex:type:ptrArity: >> FFIFunctionParser>>parseArgument >> FFIFunctionParser>>parseArguments >> FFIFunctionParser>>parseNamedFunction: >> FFICalloutMethodBuilder>>parseSignature: >> FFICalloutMethodBuilder>>generate >> FFICalloutMethodBuilder>>build: >> FFICalloutAPI>>function:module: >> GASqlite3FFI(Object)>>ffiCall:module: >> GASqlite3FFI>>apiErrorMessage: >> GASqlite3FFI>>signal:with:on: >> GASqlite3FFI>>checkForOk:on: >> GASqlite3FFI>>prepare:on:with: >> GASqlite3Statement>>prepare >> GASqlite3Driver>>prepare: >> GASqlite3ResultSet>>prepareStatement: >> GASqlite3ResultSet>>execute:withCollection: >> GASqlite3ResultSet>>execute:with:on: >> GASqlite3Driver>>execute:with: >> GASqlite3Driver>>execute: >> GAGlorpDriver>>basicExecuteSQLString: >> PharoDatabaseAccessor>>basicExecuteSQLString: >> UndefinedObject>>DoIt >> OpalCompiler>>evaluate >> [..snip..] >> >> Problem seems to be that in FFICallout>> resolveType:, the line >> >> binding := resolver ffiBindingOf: name asSymbol. >> >> actually produces nil, resolver being GASqlite3FFI class. If looking at the >> class side of GaSqlite3FFI, there is no ffiBindingOf: at all; there is >> >> nbBindingOf: aTypeName >> ^ TypeMap at: aTypeName ifAbsent: [ super nbBindingOf: aTypeName ] >> >> though. If I copy near-mindlessly and add: >> >> ffiBindingOf: aTypeName >> ^ TypeMap at: aTypeName ifAbsent: [ super ffiBindingOf: aTypeName ] >> >> then the code above fails correctly with: 'no such table: AGENT'. >> >> Am I missing some nb<->ffi bridge? Or is there a bug in Garage SQLite >> driver? >> >> Herby

Aug. 13, 2017

Re: [Pharo-users] (no subject)

by Stephane Ducasse

Christophe did a pass because he faced the same problem and he improved the situation. Now he left on vacation (and was stopped because of a huge jenkins crash because he left) and I do not know the status. (because we are also annoyed and sorry than you by the situation). Stef On Sun, Aug 13, 2017 at 10:31 AM, Vityou . <zlee314(a)gmail.com> wrote: > I recently discovered the pharo launcher. However, it only gives me options > to use outdated images, and I'm not sure about the vm. Is there any way to > change this?

Aug. 13, 2017

Re: [Pharo-users] Probably a bug in Garage SQLite

by Stephane Ducasse

Hi Herby On which version of Pharo are you trying? Because lot of changes happened on Pharo 60 FFI. Stef On Sun, Aug 13, 2017 at 6:11 PM, Herby VojÄÃk <herby(a)mailbox.sk> wrote: > Hello! > > This testing code: > > | databaseFile login accessor sqlString | > databaseFile := Smalltalk imageDirectory asFileReference / > 'play.sqlite'. > login := Login new > database: SQLite3Platform new; > host: ''; > port: ''; > username: ''; > password: ''; > databaseName: databaseFile fullPath asZnUrl > asString; > yourself. > accessor := DatabaseAccessor forLogin: login. > accessor login. > sqlString := 'SELECT * FROM AGENT'. > (accessor basicExecuteSQLString: sqlString) contents inspect. > > fails (Pharo 6.1, GarageGlorp #stable loaded a week ago as a project > dependency) with: > > Error: Unable to resolve external type: sqlite3 > > FFICallout(Object)>>error: > FFICallout>>resolveType: > FFICallout>>typeName:pointerArity: > FFICallout>>argName:indirectIndex:type:ptrArity: > FFIFunctionParser>>parseArgument > FFIFunctionParser>>parseArguments > FFIFunctionParser>>parseNamedFunction: > FFICalloutMethodBuilder>>parseSignature: > FFICalloutMethodBuilder>>generate > FFICalloutMethodBuilder>>build: > FFICalloutAPI>>function:module: > GASqlite3FFI(Object)>>ffiCall:module: > GASqlite3FFI>>apiErrorMessage: > GASqlite3FFI>>signal:with:on: > GASqlite3FFI>>checkForOk:on: > GASqlite3FFI>>prepare:on:with: > GASqlite3Statement>>prepare > GASqlite3Driver>>prepare: > GASqlite3ResultSet>>prepareStatement: > GASqlite3ResultSet>>execute:withCollection: > GASqlite3ResultSet>>execute:with:on: > GASqlite3Driver>>execute:with: > GASqlite3Driver>>execute: > GAGlorpDriver>>basicExecuteSQLString: > PharoDatabaseAccessor>>basicExecuteSQLString: > UndefinedObject>>DoIt > OpalCompiler>>evaluate > [..snip..] > > Problem seems to be that in FFICallout >> resolveType:, the line > > binding := resolver ffiBindingOf: name asSymbol. > > actually produces nil, resolver being GASqlite3FFI class. If looking at the > class side of GaSqlite3FFI, there is no ffiBindingOf: at all; there is > > nbBindingOf: aTypeName > ^ TypeMap at: aTypeName ifAbsent: [ super nbBindingOf: aTypeName ] > > though. If I copy near-mindlessly and add: > > ffiBindingOf: aTypeName > ^ TypeMap at: aTypeName ifAbsent: [ super ffiBindingOf: aTypeName ] > > then the code above fails correctly with: 'no such table: AGENT'. > > Am I missing some nb<->ffi bridge? Or is there a bug in Garage SQLite > driver? > > Herby >

Aug. 13, 2017

Re: [Pharo-users] pharo config problem

by Stephane Ducasse

Hi johannes I do not know how to help you but this is strange. We managed our synectique private code on STHub and it works. Now STHub is getting stranger and stranger. So may be your passwrd got desync. Esteban? if you read this mail. Can you check when you are back from vacation? Stef On Sun, Aug 13, 2017 at 7:20 PM, jb <brauer(a)nordakademie.de> wrote: > Hi, > > I have a problem with connection to a private smalltalkhub rep from the > command line with pharo config. > I think I set the --username and --password options correctly, but I always > get: > ZnHttpUnsuccessful: 403 Forbidded > > If I make the rep public then there is no access problem. > > Any hints what is going wrong? > > Johannes > > > > -- > View this message in context: http://forum.world.st/pharo-config-problem-tp4960715.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Aug. 13, 2017

pharo config problem

by jb

Hi, I have a problem with connection to a private smalltalkhub rep from the command line with pharo config. I think I set the --username and --password options correctly, but I always get: ZnHttpUnsuccessful: 403 Forbidded If I make the rep public then there is no access problem. Any hints what is going wrong? Johannes -- View this message in context: http://forum.world.st/pharo-config-problem-tp4960715.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 13, 2017

Probably a bug in Garage SQLite

by Herby VojÄÃk

Hello! This testing code: | databaseFile login accessor sqlString | databaseFile := Smalltalk imageDirectory asFileReference / 'play.sqlite'. login := Login new database: SQLite3Platform new; host: ''; port: ''; username: ''; password: ''; databaseName: databaseFile fullPath asZnUrl asString; yourself. accessor := DatabaseAccessor forLogin: login. accessor login. sqlString := 'SELECT * FROM AGENT'. (accessor basicExecuteSQLString: sqlString) contents inspect. fails (Pharo 6.1, GarageGlorp #stable loaded a week ago as a project dependency) with: Error: Unable to resolve external type: sqlite3 FFICallout(Object)>>error: FFICallout>>resolveType: FFICallout>>typeName:pointerArity: FFICallout>>argName:indirectIndex:type:ptrArity: FFIFunctionParser>>parseArgument FFIFunctionParser>>parseArguments FFIFunctionParser>>parseNamedFunction: FFICalloutMethodBuilder>>parseSignature: FFICalloutMethodBuilder>>generate FFICalloutMethodBuilder>>build: FFICalloutAPI>>function:module: GASqlite3FFI(Object)>>ffiCall:module: GASqlite3FFI>>apiErrorMessage: GASqlite3FFI>>signal:with:on: GASqlite3FFI>>checkForOk:on: GASqlite3FFI>>prepare:on:with: GASqlite3Statement>>prepare GASqlite3Driver>>prepare: GASqlite3ResultSet>>prepareStatement: GASqlite3ResultSet>>execute:withCollection: GASqlite3ResultSet>>execute:with:on: GASqlite3Driver>>execute:with: GASqlite3Driver>>execute: GAGlorpDriver>>basicExecuteSQLString: PharoDatabaseAccessor>>basicExecuteSQLString: UndefinedObject>>DoIt OpalCompiler>>evaluate [..snip..] Problem seems to be that in FFICallout >> resolveType:, the line binding := resolver ffiBindingOf: name asSymbol. actually produces nil, resolver being GASqlite3FFI class. If looking at the class side of GaSqlite3FFI, there is no ffiBindingOf: at all; there is nbBindingOf: aTypeName ^ TypeMap at: aTypeName ifAbsent: [ super nbBindingOf: aTypeName ] though. If I copy near-mindlessly and add: ffiBindingOf: aTypeName ^ TypeMap at: aTypeName ifAbsent: [ super ffiBindingOf: aTypeName ] then the code above fails correctly with: 'no such table: AGENT'. Am I missing some nb<->ffi bridge? Or is there a bug in Garage SQLite driver? Herby

Aug. 13, 2017