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

Re: [Pharo-users] Encoding Login information in your image (safely)

by Pierce Ng

On Wed, Aug 16, 2017 at 02:24:15PM -0300, Esteban A. Maringolo wrote: > My solution in the cases where I was worried about a config file leak > was to mitigate the risk, by using symmetric encryption algorithms, > where the shared secret is split in two different strings and > concatenated at runtime. The image, in turn holds the encryption key Take a look at SpsSplitPasswordStore, which is a simple secret splitter. http://ss3.gemtalksystems.com/ss/SpsSplitPasswordStore.html/ http://samadhiweb.com/blog/2013.08.11.splitpasswordstore.html Can be adapted to encrypt/decrypt the secret, with the cipher key also split, perhaps with one part stored in the image and another part fetched online from somewhere. I haven't touched the code in a while, but the Pharo 5 image that runs my blog is using this for the RFBServer passwords. Pierce

Aug. 18, 2017

Re: [Pharo-users] Problem compiling method source - genPushLiteral: out of range

by Henrik Sperre Johansen

The limitation is inherit in the object format/ instruction set, you can find some previous discussions at http://forum.world.st/Max-source-method-length-Max-string-length-Max-change… and http://forum.world.st/More-than-256-literals-referenced-td4676669.html#a467… One alternative is to change the compiler to create a literal array to hold all literals > 255 and rewrite accesses to indexes above 254 as something like genPushLiteral: 255 pushLiteral #at: pushConst: X messageSend , but as long as we're talking about a single digit number of cases, and not translating 200+ UI specs, it is probably a lot easier (albeit, maybe a little slower) to rewrite the code in a way which works in both dialects without using a large number of literals, say: MyClass class >> #initializeStaticVals dict := Dictionary new. initializerPairs := #( Key1 2 Key2 4 ). 1 to: initializerPairs size by: 2 do: [:ix | dict at: (initializerPairs at: ix) put: (initializerPairs at: ix +1)]. MyClassVar := dict. (Haven't seen a support layer package for VA, sorry) Cheers, Henry -- View this message in context: http://forum.world.st/Problem-compiling-method-source-genPushLiteral-out-of… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 18, 2017

ZnConstants class>>#httpStatusCodes and cloudflare

by Holger Freyther

Hi, I am currently using ZnClient to fetch data from a service behind "cloudflare" and sometimes the real/origin backend is unreachable/fails. Cloudflare has added additional[1] 5XX codes and ZnStatusLine>>#code: will signal an ZnUnknownHttpStatusCode because of that. I wonder how ZnClient should deal with these errors? IIRC the HTTP RFC specifies error classes and without knowing what "525" means one can know that the request was not successful and that the server is at "fault"? Should ZnStatusLine handle an unknown code gracefully? E.g. >>#reason: seems to do that already? have a nice weekend holger [1] https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#Cloudflare

Aug. 18, 2017

Problem compiling method source - genPushLiteral: out of range

by Patrick Scherer

Hello everyone, I'm trying to move some of our code from VA Smalltalk over to Pharo using a self-made importer and have encountered the following issue I need help with: A few of our methods are very large in size. For example, we have a method that creates a huge Dictionary with specific keys and values on startup and stores it in a class variable for immediate access. This method works fine in VA Smalltalk, but if I attempt to compile the same source code in Pharo (programmatically or via copy paste using the interface) I'm getting '*Error: genPushLiteral: index index 256 is out of range 0 to 255*' in OpalEncoderForV3PlusClosures. I'm getting the same error for some other methods. If I understand this correctly, the method simply exceeds the maximum number of literals, but it works fine in VA Smalltalk. Is there a way to increase this limit or bypass this issue without having to rework our implementation? Offtopic: Does anybody if there is a package which adds a support layer for imported VA Smalltalk code? I know there is one for Pharo->VA on VASTGoodies but I couldn't find one for the other way around. Kind regards, Patrick Scherer

Aug. 18, 2017

Re: [Pharo-users] Parser failure on FFI pragmas declaration in Pharo 5

by Denis Kudriashov

> > @Esteban: Would you accept a change to the FFI-Pharo5Compat to not use the > currentScope variable/reduce error checking? Or would you accept it in a > FFI-Pharo6Compat package? > I think it would help to be able to load the Nacl code in Pharo6 and then > fix it? But you can just switch default compiler. Is not works for you? 2017-08-18 10:20 GMT+02:00 Holger Freyther <holger(a)freyther.de>: > > > On 17. Aug 2017, at 19:37, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > > > Hey! > > > Yes. > > > > Also simple solution can be to override compiler of problem classes to > return old compiler. > > > > I know it is better to rewrite code but it can be not simple task when > there are a lot of ffi-methods. > > > I ran into this problem with the wonderful (as it had a SHA256 > implementation) NaCl bindings. > > > Pharo5: > * RBParser still has the currentScope variable and can import it > * Syntax highlighting ends in an exception (which I disabled) > > Pharo6: > * RBParser doesn't have currentScope anymore so I patched it out > * Syntax highlighting seems to work fine > > > @Esteban: Would you accept a change to the FFI-Pharo5Compat to not use the > currentScope variable/reduce error checking? Or would you accept it in a > FFI-Pharo6Compat package? > > I think it would help to be able to load the Nacl code in Pharo6 and then > fix it? > > > what do you think? > > holger >

Aug. 18, 2017

Re: [Pharo-users] YAML parser (2017)

by Peter Uhnak

Hi, Phil Back has kindly fixed the PetitYAML so it mostly works now. The only problem I've encountered was some weird misparsing of strings containing slashes, e.g. "5/". In any case: Install PetitParser (from Catalog or somewhere), load PetitYAML package (this is already loaded when loading PP from catalog). And then parse your string ``` PPYAMLGrammar parse: ' language: c sudo: false cache: directories: - opensmalltalk-vm/.thirdparty-cache git: depth: "5"'. ``` "Dictionary( 'cache'->a Dictionary( 'directories'->#('opensmalltalk-vm/.thirdparty-cache') ) 'git'->a Dictionary( 'depth'->'5' ) 'language'->'c' 'sudo'->'false' )" Take a look at PPYAMLGrammarTest>>testTravisYml too. Peter On Fri, Aug 18, 2017 at 09:45:00AM +0200, H. Hirzel wrote: > I am not looking for a complete implementation which is quite an effort > > but rather for a subset which does simple things such as parsing > - a list of hashes (dictionaries), > - a dictionary of dictionaries (nested to arbitrary depths), > - multi-line comments > > > --Hannes > > On 8/16/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > > Are there any news about a YAML parser for Pharo 5 / 6.1? > > > > --Hannes > > > > On 5/29/17, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > >> Hi, > >> > >> do we have a working parser for YAML? > >> > >> There's PPYAMLGrammar (in PetitParser), however it doesn't seem to work > >> in > >> Pharo 6 at all (not even tests pass). > >> In Pharo 5 the tests are green, but using it on YAML content still > >> fails... > >> with small fix I managed it to "pass", however the output seems to be a > >> very > >> fine-grained AST decomposition and not the expected output > >> (dictionaries/arrays). > >> > >> So do we have some else/working? > >> > >> YAML specs have BNF descriptions, so maybe SmaCC can generate it? (I > >> don't > >> know SmaCC, so maybe this is not how it works.) > >> > >> Thanks, > >> Peter > >> > >> > > >

Aug. 18, 2017

Re: [Pharo-users] Parser failure on FFI pragmas declaration in Pharo 5

by Holger Freyther

> On 17. Aug 2017, at 19:37, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: Hey! > Yes. > > Also simple solution can be to override compiler of problem classes to return old compiler. > > I know it is better to rewrite code but it can be not simple task when there are a lot of ffi-methods. I ran into this problem with the wonderful (as it had a SHA256 implementation) NaCl bindings. Pharo5: * RBParser still has the currentScope variable and can import it * Syntax highlighting ends in an exception (which I disabled) Pharo6: * RBParser doesn't have currentScope anymore so I patched it out * Syntax highlighting seems to work fine @Esteban: Would you accept a change to the FFI-Pharo5Compat to not use the currentScope variable/reduce error checking? Or would you accept it in a FFI-Pharo6Compat package? I think it would help to be able to load the Nacl code in Pharo6 and then fix it? what do you think? holger

Aug. 18, 2017

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo 6.1 (summer) released!

by Marcus Denker

> > What I think would have been good is to list all the updates that where done between > releasing 6.0 and 6.1 *as part of the changelog* of 6.1 (even though they were already > in the image that you got a minute before Pharo6.1 was released, as they where released as > hot fixes before). > The changelog of things done between releasing 6.0 and the release of 6.1: 20262 Update Iceberg to 0.5.4 https://pharo.fogbugz.com/f/cases/20262 20268 update iceberg v0.5.5 https://pharo.fogbugz.com/f/cases/20268 20226 TabMorph should use stepping mechanism for animating background building https://pharo.fogbugz.com/f/cases/20226 20238 Run out of memory the image hangs without out of memory warning https://pharo.fogbugz.com/f/cases/20238 20218 Master branch (Pharo 6) needs to be safely merged into development branch (Pharo 7). https://pharo.fogbugz.com/f/cases/20218 20187 Request use of block in certain methods https://pharo.fogbugz.com/f/cases/20187 20188 Request representation of integer literal without float exponent https://pharo.fogbugz.com/f/cases/20188 20182 Extra dot in literal array https://pharo.fogbugz.com/f/cases/20182 18760 Failing test: WeakAnnouncerTest>>#testNoDeadWeakSubscriptions https://pharo.fogbugz.com/f/cases/18760 20186 Request removal of extra statement separators (dot) https://pharo.fogbugz.com/f/cases/20186 20185 Request pipe after block argments https://pharo.fogbugz.com/f/cases/20185 20183 TraitDescription>>fileOutLocalMethodsInCategory:on: method temp var name overlap https://pharo.fogbugz.com/f/cases/20183 20184 Request space between argument and selector in StdioStream>>next: https://pharo.fogbugz.com/f/cases/20184 20167 Regression with PNGReaderWriter in P6 https://pharo.fogbugz.com/f/cases/20167 20198 inner structure access does not work on multiple architecture https://pharo.fogbugz.com/f/cases/20198 20110 AllocationTest>>#testOutOfMemorySignal not well suited to 64-bit https://pharo.fogbugz.com/f/cases/20110 20096 Add script pragma to SpaceTally>>printSpaceAnalysis https://pharo.fogbugz.com/f/cases/20096 20174 In the debug halo of a morph: clicking on "inspect morph" and "explore morph" bring up the same window. https://pharo.fogbugz.com/f/cases/20174 20093 Missing source stamp makes changes hard to view https://pharo.fogbugz.com/f/cases/20093 20148 transforming deprecations should take #showWarning into account https://pharo.fogbugz.com/f/cases/20148 20146 ZnHTTPSTests>>#testGetPharoVersion started to fail https://pharo.fogbugz.com/f/cases/20146

Aug. 18, 2017

Re: [Pharo-users] YAML parser (2017)

by H. Hirzel

I am not looking for a complete implementation which is quite an effort but rather for a subset which does simple things such as parsing - a list of hashes (dictionaries), - a dictionary of dictionaries (nested to arbitrary depths), - multi-line comments --Hannes On 8/16/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Are there any news about a YAML parser for Pharo 5 / 6.1? > > --Hannes > > On 5/29/17, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >> Hi, >> >> do we have a working parser for YAML? >> >> There's PPYAMLGrammar (in PetitParser), however it doesn't seem to work >> in >> Pharo 6 at all (not even tests pass). >> In Pharo 5 the tests are green, but using it on YAML content still >> fails... >> with small fix I managed it to "pass", however the output seems to be a >> very >> fine-grained AST decomposition and not the expected output >> (dictionaries/arrays). >> >> So do we have some else/working? >> >> YAML specs have BNF descriptions, so maybe SmaCC can generate it? (I >> don't >> know SmaCC, so maybe this is not how it works.) >> >> Thanks, >> Peter >> >> >

Aug. 18, 2017

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo 6.1 (summer) released!

by Marcus Denker

> On 24 Jul 2017, at 15:11, Hilaire <hilaire(a)drgeo.eu> wrote: > > Thanks guys. > > I hope it includes the fixes for the bugs impacting Dr. Geo. > Hello, I think there is a bit of a confusion of how we do fixed for Pharo6. I will explain: -> if people find bugs, they end up on the issue tracker -> Some of these get fixed. If a fix is ready, we will integrate it very quickly. This means that only the update number changes, not the main version number (these are bug fixes, they do not change APIs). A good name for these updates is âhot fixesâ. They are announced to the dev list only with the automatic lists that are send for each update. We integrated already quite some into Pharo6 like that. The release was I think around #60500, while 6.1 was done around #60510 Then there are cases that are more grave: 6.1 was done because it contains bigger changes. What I think would have been good is to list all the updates that where done between releasing 6.0 and 6.1 *as part of the changelog* of 6.1 (even though they were already in the image that you got a minute before Pharo6.1 was released, as they where released as hot fixes before). Now if the image includes all fixes needed for DrGeo depends on a) has that issue been fixed and b) if yes was all massaging done to have the update actually integrated. (what does not help is that it is holiday time, e.g. I did not read emails and did *nothing* from end of Juli to yesterday, this does not help but was really, really needed). Marcus

Aug. 18, 2017