- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Automatic Refactoring Disranging Seaside Rest Methods

by Stephane Ducasse

Lionel when the system does find a source, it decompiles the method and this is why you get the code changed. Stef On Tue, Jul 18, 2017 at 7:22 AM, Max Leske <maxleske(a)gmail.com> wrote: > As Gabriel notes, it looks like your missing the .sources file. I don't know > what pharocloud supports, but you could try packaging your image and your > .sources file into the same ZIP archive. > > Cheers, > Max > > > > On 18 July 2017 at 02:21:54, lionelakue (lionelakue(a)gmail.com) wrote: > > Now I can remember reading about this somewhere(wrongly remembered it as > automatic refactoring)... > > I have this problem when I have to copy my image to pharocloud by example. > > You need to zip your .image file and load it to the cloud. > > what I am doing now is to replace my in-uri string parameters with the > excepted arg1, arg2 etc. > > So is this the only solution? since the behavior is not voluntary. > > > gcotelli wrote >> I saw this happening only when the image cannot find the sources file, so >> it has to decompile the methods. >> >> On Mon, Jul 17, 2017 at 7:34 PM, lionelakue < > >> lionelakue@ > >> > wrote: >> >>> Hello everyone, >>> >>> When you copy an image or sometimes when you make a Metacello commit, >>> your >>> methods are automatically refactored. >>> >>> This uncleanse the code (replacing context meaningfull variable names >>> with >>> gereric identifiers) and prevents seaside request parameters . Which are >>> mapped to method parameters by uri strings: >>> >>> ToDoHandler>>searchFor: aString >>> >> <get> >>> >> <path: '/search?query={aString}'> >>> >>> ^ String streamContents: [ :stream | >>> ToDoList default items do: [ :each | >>> (each title includesSubString: aString) >>> ifTrue: [ stream nextPutAll: each title; crlf ] ] ] >>> >>> >>> will become: >>> >>> >>> ToDoHandler>>searchFor: arg1 >>> >> <get> >>> >> <path: '/search?query={aString}'> >>> ^ String streamContents: [ :arg2| >>> ToDoList default items do: [ :arg3| >>> (each title includesSubString: aString) >>> ifTrue: [ arg2 nextPutAll: arg3 title; crlf ] ] ] >>> >>> >>> So will end having a Parameter not found exception because arg1 and >>> aString >>> mismatche. >>> >>> >>> Is there a way to disable automatic refactoring? >>> >>> Lionel >>> >>> >>> >>> -- >>> View this message in context: >>> http://forum.world.st/Automatic-Refactoring- >>> Disranging-Seaside-Rest-Methods-tp4955422.html >>> Sent from the Pharo Smalltalk Developers mailing list archive at >>> Nabble.com. >>> >>> > > > > > > -- > View this message in context: > http://forum.world.st/Automatic-Refactoring-Disranging-Seaside-Rest-Methods… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

July 18, 2017

Re: [Pharo-dev] Epicea applying multiple changes

by Tim Mackinnon

I thought I had the same problem at Pharo Days, but actually I think it's just the UI is a bit confusing. Stephane E and I had a look and it seemed to be fine for the case I thought I had. Possibly it was that , it's easy to load in more than you think you should which gives weird outcomes. Tim Sent from my iPhone > On 18 Jul 2017, at 22:21, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi andrei > > this is strange because I recovered multiple time recently due to some > hidden bugs and I did not face the one you report. > > Stef > > On Tue, Jul 18, 2017 at 10:48 AM, Andrei Chis > <chisvasileandrei(a)gmail.com> wrote: >> Hi, >> >> Is there some known bug in Epicea when applying multiple changes at once in >> Pharo 6? >> >> I had a few crashes lately and each time when recovering the changes by >> selecting multiple changes at once some changes are skipped. If I apply >> manually each change it works. >> >> Cheers, >> Andrei >

July 18, 2017

Re: [Pharo-dev] Epicea applying multiple changes

by Stephane Ducasse

Hi andrei this is strange because I recovered multiple time recently due to some hidden bugs and I did not face the one you report. Stef On Tue, Jul 18, 2017 at 10:48 AM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Hi, > > Is there some known bug in Epicea when applying multiple changes at once in > Pharo 6? > > I had a few crashes lately and each time when recovering the changes by > selecting multiple changes at once some changes are skipped. If I apply > manually each change it works. > > Cheers, > Andrei

July 18, 2017

Re: [Pharo-dev] [Ann] Keccak hashing algorithm

by Esteban A. Maringolo

2017-07-18 17:33 GMT-03:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > 2017-07-18 17:26 GMT-03:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >> imply moving to github? The Cryptography package has Squeak contributors >> too and moving to github implies a fork. > Last commit to Squeaksource repo is 4 years old. I overlooked this, last commit is recent. My bad.

July 18, 2017

Re: [Pharo-dev] [Ann] Keccak hashing algorithm

by Esteban A. Maringolo

2017-07-18 17:26 GMT-03:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > Norbert, > > On Tue, Jul 18, 2017 at 11:05 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> Really great! I think we should move the Cryptography package from >> smalltalkhub to github, refactor it and add goodies like this. We need a >> strong crypto foundation. > > > I agree that refactoring and adding goodies is great. But why does that > imply moving to github? The Cryptography package has Squeak contributors > too and moving to github implies a fork. The fork, soft or hard, already happened since Pharo incorporated in "core" packages methods that belonged to the Cryptography package, so loading this one overrides core methods. Last commit to Squeaksource repo is 4 years old. As per my last year announcement in http://forum.world.st/Cryptography-packages-tp4915041p4915764.html "I just adapted the latest version of the Cryptography package in SqueakSource (Cryptography-rww.49) and removed everything that was already in the Pharo 5.0 image and modified what was necessary to have all the tests passing. There is still a pending organization of the Cryptography classes and packages per se, but this should be the reference implementation in Pharo. http://smalltalkhub.com/#!/~Cryptography/Cryptography/" Regards, Esteban A. Maringolo

July 18, 2017

Re: [Pharo-dev] [Ann] Keccak hashing algorithm

by Eliot Miranda

Norbert, On Tue, Jul 18, 2017 at 11:05 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > Really great! I think we should move the Cryptography package from > smalltalkhub to github, refactor it and add goodies like this. We need a > strong crypto foundation. > I agree that refactoring and adding goodies is great. But why does that imply moving to github? The Cryptography package has Squeak contributors too and moving to github implies a fork. > > Norbert > > > Am 18.07.2017 um 19:10 schrieb Esteban A. Maringolo < > emaringolo(a)gmail.com>: > > > > Great! > > > > I see you continue doing Ethereum related stuff ;-) > > > > Regards! > > Esteban A. Maringolo > > > > > > 2017-07-18 13:32 GMT-03:00 Santiago Bragagnolo < > santiagobragagnolo(a)gmail.com>: > >> Hi there! > >> > >> I am just releasing the first version of the Keccak-256 hashing > algorithm. > >> https://en.wikipedia.org/wiki/SHA-3 > >> > >> You can find it at: https://github.com/sbragagnolo/Keccak > >> > >> This version is based on a javascript implementation: > >> https://github.com/emn178/js-sha3 > >> > >> This implementation supports as message: bytearray and ascii and utf-8 > >> strings. > >> > >> > >> Soon i will be adding support to the rest of the Keccak family of > hashing > >> functions, since the implementations is quite configurable, is just > need to > >> add some constructors with specific configurations and tests for this > other > >> cases of usage. > >> > >> > >> Here a onliner for building an image with the version v0.1: > >> > >> wget -O- https://raw.githubusercontent.com/sbragagnolo/Keccak/v0.1/ > build.sh > >> | bash > >> > >> Hope you find it useful :) > >> > >> > >> Santiago > >> > >> > > -- _,,,^..^,,,_ best, Eliot

July 18, 2017

Re: [Pharo-dev] [Pharo-users] [Ann] Keccak hashing algorithm

by Santiago Bragagnolo

Hahahaha, Thanks for the feedback. Sven, I am quite new in this domain. I'll study your questions and come with solutions tomorrow :). Thanks, i really need this interaction. On Tue, 18 Jul 2017 at 20:28 Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Great work. I love libraries like these. > > I am a bit confused though, in your #updateString: you seem to be > implementing UTF-8 encoding, something we already have. Normally, hashing > algorithms are defined on bytes and result in bytes (yours returns a plain > Array, which is also strange). > > It seems > > (Keccak hashMessage: 'foo bar') = (Keccak hashMessage: 'foo bar' > asByteArray). > > is true, but > > (Keccak hashMessage: 'Les Ã©lÃ¨ves FranÃ§aises') = (Keccak hashMessage: 'Les > Ã©lÃ¨ves FranÃ§aises' utf8Encoded). > > is false. How come ? > > Is this UTF-8 encoding really part of the algorithm ? > > Do your tests cover it ? > > Another question, how would you compute the invariants given here ? > > https://en.wikipedia.org/wiki/SHA-3#Examples_of_SHA-3_variants > > SHAKE128("The quick brown fox jumps over the lazy dog", 256) > > f4202e3c5852f9182a0430fd8144f0a74b95e7417ecae17db0f8cfeed0e3e66e > > SHAKE128("The quick brown fox jumps over the lazy dof", 256) > > 853f4538be0db9621a6cea659a06c1107b1f83f02b13d18297bd39d7411cf10c > > > On 18 Jul 2017, at 18:32, Santiago Bragagnolo < > santiagobragagnolo(a)gmail.com> wrote: > > > > Hi there! > > > > I am just releasing the first version of the Keccak-256 hashing > algorithm. https://en.wikipedia.org/wiki/SHA-3 > > > > You can find it at: https://github.com/sbragagnolo/Keccak > > > > This version is based on a javascript implementation: > https://github.com/emn178/js-sha3 > > > > This implementation supports as message: bytearray and ascii and utf-8 > strings. > > > > > > Soon i will be adding support to the rest of the Keccak family of > hashing functions, since the implementations is quite configurable, is just > need to add some constructors with specific configurations and tests for > this other cases of usage. > > > > > > Here a onliner for building an image with the version v0.1: > > > > wget -O- > https://raw.githubusercontent.com/sbragagnolo/Keccak/v0.1/build.sh | bash > > > > Hope you find it useful :) > > > > > > Santiago > > > > > > >

July 18, 2017

Re: [Pharo-dev] [Ann] Keccak hashing algorithm

by Sven Van Caekenberghe

Great work. I love libraries like these. I am a bit confused though, in your #updateString: you seem to be implementing UTF-8 encoding, something we already have. Normally, hashing algorithms are defined on bytes and result in bytes (yours returns a plain Array, which is also strange). It seems (Keccak hashMessage: 'foo bar') = (Keccak hashMessage: 'foo bar' asByteArray). is true, but (Keccak hashMessage: 'Les Ã©lÃ¨ves FranÃ§aises') = (Keccak hashMessage: 'Les Ã©lÃ¨ves FranÃ§aises' utf8Encoded). is false. How come ? Is this UTF-8 encoding really part of the algorithm ? Do your tests cover it ? Another question, how would you compute the invariants given here ? https://en.wikipedia.org/wiki/SHA-3#Examples_of_SHA-3_variants SHAKE128("The quick brown fox jumps over the lazy dog", 256) f4202e3c5852f9182a0430fd8144f0a74b95e7417ecae17db0f8cfeed0e3e66e SHAKE128("The quick brown fox jumps over the lazy dof", 256) 853f4538be0db9621a6cea659a06c1107b1f83f02b13d18297bd39d7411cf10c > On 18 Jul 2017, at 18:32, Santiago Bragagnolo <santiagobragagnolo(a)gmail.com> wrote: > > Hi there! > > I am just releasing the first version of the Keccak-256 hashing algorithm. https://en.wikipedia.org/wiki/SHA-3 > > You can find it at: https://github.com/sbragagnolo/Keccak > > This version is based on a javascript implementation: https://github.com/emn178/js-sha3 > > This implementation supports as message: bytearray and ascii and utf-8 strings. > > > Soon i will be adding support to the rest of the Keccak family of hashing functions, since the implementations is quite configurable, is just need to add some constructors with specific configurations and tests for this other cases of usage. > > > Here a onliner for building an image with the version v0.1: > > wget -O- https://raw.githubusercontent.com/sbragagnolo/Keccak/v0.1/build.sh | bash > > Hope you find it useful :) > > > Santiago > >

July 18, 2017

Re: [Pharo-dev] [Ann] Keccak hashing algorithm

by Norbert Hartl

Really great! I think we should move the Cryptography package from smalltalkhub to github, refactor it and add goodies like this. We need a strong crypto foundation. Norbert > Am 18.07.2017 um 19:10 schrieb Esteban A. Maringolo <emaringolo(a)gmail.com>: > > Great! > > I see you continue doing Ethereum related stuff ;-) > > Regards! > Esteban A. Maringolo > > > 2017-07-18 13:32 GMT-03:00 Santiago Bragagnolo <santiagobragagnolo(a)gmail.com>: >> Hi there! >> >> I am just releasing the first version of the Keccak-256 hashing algorithm. >> https://en.wikipedia.org/wiki/SHA-3 >> >> You can find it at: https://github.com/sbragagnolo/Keccak >> >> This version is based on a javascript implementation: >> https://github.com/emn178/js-sha3 >> >> This implementation supports as message: bytearray and ascii and utf-8 >> strings. >> >> >> Soon i will be adding support to the rest of the Keccak family of hashing >> functions, since the implementations is quite configurable, is just need to >> add some constructors with specific configurations and tests for this other >> cases of usage. >> >> >> Here a onliner for building an image with the version v0.1: >> >> wget -O- https://raw.githubusercontent.com/sbragagnolo/Keccak/v0.1/build.sh >> | bash >> >> Hope you find it useful :) >> >> >> Santiago >> >>

July 18, 2017

Re: [Pharo-dev] [Ann] Keccak hashing algorithm

by Esteban A. Maringolo

Great! I see you continue doing Ethereum related stuff ;-) Regards! Esteban A. Maringolo 2017-07-18 13:32 GMT-03:00 Santiago Bragagnolo <santiagobragagnolo(a)gmail.com>: > Hi there! > > I am just releasing the first version of the Keccak-256 hashing algorithm. > https://en.wikipedia.org/wiki/SHA-3 > > You can find it at: https://github.com/sbragagnolo/Keccak > > This version is based on a javascript implementation: > https://github.com/emn178/js-sha3 > > This implementation supports as message: bytearray and ascii and utf-8 > strings. > > > Soon i will be adding support to the rest of the Keccak family of hashing > functions, since the implementations is quite configurable, is just need to > add some constructors with specific configurations and tests for this other > cases of usage. > > > Here a onliner for building an image with the version v0.1: > > wget -O- https://raw.githubusercontent.com/sbragagnolo/Keccak/v0.1/build.sh > | bash > > Hope you find it useful :) > > > Santiago > >

July 18, 2017