- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] @lab at midday

by Norbert Hartl

Am 12.07.2013 um 14:00 schrieb Damien Cassou <damien.cassou(a)gmail.com>: > On Fri, Jul 12, 2013 at 12:52 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> Au repertoire, > > > ??? > Ok, that seems to only work for non-native french speakers :) Although it is stupid to explain jokes this should be a proof of my capabilities of speaking french. If I would know how to speak it I probably would have written "Au revoir" insteadâ¦ >> Norber' > t > :-) > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

July 12, 2013

Re: [Pharo-dev] Fwd: Build failed in Jenkins: Nand2Tetris Â» 30,bleedingEdge,vm #184

by Damien Cassou

On Fri, Jul 12, 2013 at 2:14 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > ClassBuilder problems most probably. > Should be resolved as of noon today :) works fine, thank you. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

July 12, 2013

Recommendation for password encryption?

by Mariano Martinez Peck

Hi guys. Some time ago I asked about the best way to encrypt a password. Some of the recommendations I got was: 1) Generally for passwords you do not write a decrypt method for security purposes (eg you do not want people to be able to reverse engineer the encrypted password easily) 2) put a little salt 3) There is http://www.squeaksource.com/Cryptography/PasswordHashingFFI 4) I should not decrypt password but instead I should compare both encrypted versions to see if they are equal. My scenario is the following. I need to store database passwords in text files. So I don't want to let them as plain text. And while I understand 4), I think it's a different scenario than mine. I know that some database driver may allow you to directly send the encrypted password. But still...I have another similar scenario in which I have to store a password and then send it (unencrypted)...so I kind of really need a bi-directional encryption. Now..I would try to avoid having an external library + FFI. Any ideas what is the best thing I can do? And how could I solve 1) if I want bidirectional like in my case? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

July 12, 2013

[update 3.0] #30269

by Marcus Denker

30269 ----- 11154 Update Opal to latest version https://pharo.fogbugz.com/f/cases/11154 This update includes all these fixes: 11035 VMMaker compiling error 10942 OCASTClosureAnalyzer should be referenced just in OCASTSemanticAnalyzer 10964 Temp vars shown multiple times in debugger context inspector 11122 Temp mapping not working sometimes 11134 Undeclared class not shown in Transcript 11137 add IRBuilder buildMethod: 11133 AdditionalMethodState only when needed We recompile the whole image in the postscript, mostly for 11133. Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Tests-MarcusDenk… http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Core-MarcusDenke…

July 12, 2013

Re: [Pharo-dev] Fwd: Build failed in Jenkins: Nand2Tetris Â» 30,bleedingEdge,vm #184

by Camillo Bruni

ClassBuilder problems most probably. Should be resolved as of noon today :) On 2013-07-12, at 13:58, Damien Cassou <damien.cassou(a)gmail.com> wrote: > Is it a VM problem? I didn't touch the source code for some time and > it was working until yesterday. > > > ---------- Forwarded message ---------- > From: <ci-pharo-contribution(a)inria.fr> > Date: Fri, Jul 12, 2013 at 12:16 PM > Subject: Build failed in Jenkins: Nand2Tetris Â» 30,bleedingEdge,vm #184 > To: Damien(a)inria.fr, Cassou(a)inria.fr, damien.cassou(a)gmail.com > > > See <https://ci.inria.fr/pharo-contribution/job/Nand2Tetris/PHARO=30,VERSION=ble…> > > ------------------------------------------ > [...truncated 237 lines...] > instVarAt:put: > instVarAt: > instVarAt:put: > instVarAt: > instVarAt:put: > instVarAt: > instVarAt:put: > instVarAt: > instVarAt:put: > instVarAt: > instVarAt:put: > instVarAt: > instVarAt:put: > at:put: > elementsForwardIdentityTo: > basicNew > new: > someInstance > nextInstance > at:put: > new: > replaceFrom:to:with:startingAt: > new: > shallowCopy > species > new: > species > new: > replaceFrom:to:with:startingAt: > species > new: > replaceFrom:to:with:startingAt: > replaceFrom:to:with:startingAt: > species > new: > replaceFrom:to:with:startingAt: > replaceFrom:to:with:startingAt: > species > new: > replaceFrom:to:with:startingAt: > species > new: > replaceFrom:to:with:startingAt: > species > new: > replaceFrom:to:with:startingAt: > species > new: > replaceFrom:to:with:startingAt: > species > new: > replaceFrom:to:with:startingAt: > replaceFrom:to:with:startingAt: > species > new: > replaceFrom:to:with:startingAt: > shallowCopy > species > new: > species > new: > replaceFrom:to:with:startingAt: > species > new: > replaceFrom:to:with:startingAt: > replaceFrom:to:with:startingAt: > species > new: > replaceFrom:to:with:startingAt: > replaceFrom:to:with:startingAt: > species > new: > replaceFrom:to:with:startingAt: > species > new: > replaceFrom:to:with:startingAt: > species > new: > replaceFrom:to:with:startingAt: > species > new: > replaceFrom:to:with:startingAt: > species > new: > replaceFrom:to:with:startingAt: > species > new: > replaceFrom:to:with:startingAt: > species > new: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > compare:with:collated: > at:put: > basicNew > instVarAt: > instVarAt:put: > instVarAt: > instVarAt:put: > instVarAt: > instVarAt:put: > instVarAt: > instVarAt:put: > instVarAt: > instVarAt:put: > instVarAt: > instVarAt:put: > instVarAt: > instVarAt:put: > instVarAt: > instVarAt:put: > instVarAt: > instVarAt:put: > instVarAt: > instVarAt:put: > instVarAt: > instVarAt:put: > instVarAt: > instVarAt:put: > instVarAt: > instVarAt:put: > instVarAt: > instVarAt:put: > at:put: > elementsForwardIdentityTo: > elementsForwardIdentityTo: > > stack page bytes 4096 available headroom 3300 minimum unused headroom 2228 > > (Segmentation fault) > ./pharo: line 11: 30688 Aborted (core dumped) > "$DIR"/"pharo-vm/pharo" -nodisplay "$@" > Build step 'Execute shell' marked build as failure > Archiving artifacts > Recording test results > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

July 12, 2013

Re: [Pharo-dev] @lab at midday

by Damien Cassou

On Fri, Jul 12, 2013 at 12:52 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > Au repertoire, ??? > Norber' :-) -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

July 12, 2013

Fwd: Build failed in Jenkins: Nand2Tetris Â» 30,bleedingEdge,vm #184

by Damien Cassou

Is it a VM problem? I didn't touch the source code for some time and it was working until yesterday. ---------- Forwarded message ---------- From: <ci-pharo-contribution(a)inria.fr> Date: Fri, Jul 12, 2013 at 12:16 PM Subject: Build failed in Jenkins: Nand2Tetris Â» 30,bleedingEdge,vm #184 To: Damien(a)inria.fr, Cassou(a)inria.fr, damien.cassou(a)gmail.com See <https://ci.inria.fr/pharo-contribution/job/Nand2Tetris/PHARO=30,VERSION=ble…> ------------------------------------------ [...truncated 237 lines...] instVarAt:put: instVarAt: instVarAt:put: instVarAt: instVarAt:put: instVarAt: instVarAt:put: instVarAt: instVarAt:put: instVarAt: instVarAt:put: instVarAt: instVarAt:put: at:put: elementsForwardIdentityTo: basicNew new: someInstance nextInstance at:put: new: replaceFrom:to:with:startingAt: new: shallowCopy species new: species new: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: shallowCopy species new: species new: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: species new: compare:with:collated: at:put: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: basicNew instVarAt: instVarAt:put: instVarAt: instVarAt:put: instVarAt: instVarAt:put: instVarAt: instVarAt:put: instVarAt: instVarAt:put: instVarAt: instVarAt:put: instVarAt: instVarAt:put: instVarAt: instVarAt:put: instVarAt: instVarAt:put: instVarAt: instVarAt:put: instVarAt: instVarAt:put: instVarAt: instVarAt:put: instVarAt: instVarAt:put: instVarAt: instVarAt:put: at:put: elementsForwardIdentityTo: elementsForwardIdentityTo: stack page bytes 4096 available headroom 3300 minimum unused headroom 2228 (Segmentation fault) ./pharo: line 11: 30688 Aborted (core dumped) "$DIR"/"pharo-vm/pharo" -nodisplay "$@" Build step 'Execute shell' marked build as failure Archiving artifacts Recording test results -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

July 12, 2013

Re: [Pharo-dev] OpenDBX problem with simultaneus connections

by Mariano Martinez Peck

No, GlorpOpenDBXDriver-MarianoMartinezPeck.16 in ' http://www.smalltalkhub.com/mc/DBXTalk/Glorp/main' On Thu, Jul 11, 2013 at 11:55 PM, Facundo Vozzi <facundov79(a)gmail.com>wrote: > Mariano, > is OpenDBXDriver-MarianoMartinezPeck.38 your last commit? > > Thanks > > > On Thu, Jul 11, 2013 at 5:21 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> I recommend to update to the last commit I did... >> Otherwise, if you were using different instances of Login for each >> session you should have several SelmaConnectionPool alive :) (rather than 1) >> >> >> On Sat, Jul 6, 2013 at 5:54 PM, Facundo Vozzi <facundov79(a)gmail.com>wrote: >> >>> Thanks Esteban. >>> >>> Now, I changed GlorpOpenDBXPoolingDriver for GlorpOpenDBXDriver and all >>> is working properly. I'll try to fix the problem because I think that will >>> be a problem the number of postgres.exe process running on the server this >>> way. >>> >>> >>> On Sat, Jul 6, 2013 at 5:36 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: >>> >>>> >>>> On Jul 6, 2013, at 7:15 PM, Facundo Vozzi <facundov79(a)gmail.com> wrote: >>>> >>>> Hi, >>>> I migrated my small app from Pharo 1.3 to Pharo 2.0. I'm using DBXTalk >>>> and GlorpDBX. >>>> >>>> It's working perfectly on my notebook (Windows 7 64 bits and postgreSql >>>> 9.1) but on my server (Windows 2003 32 bits server and postgreSql 9.0) I'm >>>> getting this error at OpenDBXWin32 level with 3 simultaneus connections: >>>> * 'FATAL: lo siento, ya tenemos demasiados clientes'*. >>>> >>>> It's strange (for me) because the version on Pharo 1.3 works properly >>>> in both machines but the version on Pharo 2.0 works perfect on my notebook >>>> and works properly for the first two connections on the server. >>>> >>>> I think that could be a problem with the OpenDBX library with the >>>> server and the implementation of FFI on Pharo 2.0 but I can't figure out it. >>>> >>>> Any suggestions? >>>> >>>> Thanks in advance, >>>> Facundo >>>> >>>> p.s.: where is hosted the DBXTalk project now? I can't find it on >>>> http://dbxtalk.smallworks.com.ar/ anymore >>>> >>>> >>>> sorry, I'm changing servers and the DNS is not well refreshed yet... >>>> however, you can find it here: >>>> >>>> http://dbxtalk.smallworks.eu >>>> >>>> >>>> <Error on the third connection attempt.txt> >>>> >>>> >>>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > -- Mariano http://marianopeck.wordpress.com

July 12, 2013

resignalAs:

by Camillo Bruni

Who uses Exception >> #resignalAs: ? Because I would like to change to from ------------------------------------------------------------------- resignalAs: replacementException "Signal an alternative exception in place of the receiver." self resumeUnchecked: replacementException signal ------------------------------------------------------------------- to ------------------------------------------------------------------- resignalAs: replacementException "Signal an alternative exception in place of the receiver." ^ replacementException signalIn: signalContext ------------------------------------------------------------------- In my opinion better of course ;). Facts: ------- 1) there are no users of #resignalAs: in the image 2) my change doesn't break the Exception tests

July 12, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/… 1 regressions found. Tests.CodeImport.ChunkImportTestCase.testImportAClassCategory

July 12, 2013