May 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] [TODO] Bug Tracker Status (429)

by Marcus Denker

Hello! The weekly bug tracker status report. Open Issues: 429 http://code.google.com/p/pharo/issues/list For starters, looking at the ones tagged "1.3" is best: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.3 These should contain only things -> that are real show stoppers for a release -> We *really* *really* want them -> failing tests -> things that look good that only need to be integrated Another good starting point are issues tagged "easy": http://code.google.com/p/pharo/issues/list?can=2&q=difficulty=Easy -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 16, 2011

Re: [Pharo-project] Zinc in PharoDev (was Re: XML maintainer???)

by Mariano Martinez Peck

On Mon, May 16, 2011 at 8:21 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > On May 16, 2011, at 3:03 AM, GermÃ¡n Arduino wrote: > > > Hi: > > > > I saw in your image that Zinc is already loaded. > > > > It will be at this way in the images from now? I'm asking because I > > must decide what path take with XMLRPC. If Zinc will be the default to > > use, I will adapt xmlrpc to work with Zn. > > yes zinc will be in core. > It is already, you did it ;) > > Stef > > > > > I know that xmlrpc is not heavily used but still I think is cool > > having the tools in the image to expose an easy and straightforward > > API. > > > > I wait comments. > > > > Cheers. > > GermÃ¡n. > > > > > > 2011/5/15 Mariano Martinez Peck <marianopeck(a)gmail.com>: > >> So...we added XML to PharoDev. Where are the maintaners? Could you > please > >> check these issues? > >> > >> Thanks! > >> > >> mariano > >> > >> ---------- Forwarded message ---------- > >> From: <pharo(a)googlecode.com> > >> Date: Sun, May 15, 2011 at 8:50 PM > >> Subject: [Pharo-bugtracker] Issue 4232 in pharo: Failing Tests in Full: > XML > >> To: pharo-bugtracker(a)lists.gforge.inria.fr > >> > >> > >> Status: Accepted > >> Owner: marcus.d...(a)gmail.com > >> Labels: Milestone-1.3-DevImage > >> > >> New issue 4232 by marcus.d...(a)gmail.com: Failing Tests in Full: XML > >> http://code.google.com/p/pharo/issues/detail?id=4232 > >> > >>>>> > >>>>> > XML.Tests.Parser.Nodes.XMLObservableListTest.testReplaceFromToWithStartingAt > >>>>> 0.0 1 > >>>>> > >>>>> > XML.Tests.Parser.Nodes.XMLOrderedListTest.testReplaceFromToWithStartingAt > >> > >> > >> _______________________________________________ > >> Pharo-bugtracker mailing list > >> Pharo-bugtracker(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker > >> > >> > >> > >> -- > >> Mariano > >> http://marianopeck.wordpress.com > >> > >> > > > > > -- Mariano http://marianopeck.wordpress.com

May 16, 2011

[Pharo-project] [TODO] 1.3

by Marcus Denker

Core ==== Open Issues: 20 http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3 Failing Tests: 1 https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/lastCompleted… Full === Open Issues: 8 http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3-DevImage Failing Tests: 3 https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/lastCompletedBuild/t… => Most important next Issue to tackle: Get all tests green. It would be nice to get both Core and Full green. Than the idea is that in the spirit of Continuous Delivery, we just keep it green. No degeneration of trivial problems (undeclards), fast roll-back of problematic changes... The idea is to keep it in a state that we could, at a minumum, always say "We could release next Friday". And the best would be: "We could release today". -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 16, 2011

[Pharo-project] [TODO] 1.2.2

by Marcus Denker

Core ----- -> All Tests Green -> No known Bugs reported -> Version number set to 1.2.2 -> New pre-build uploaded, will be linked as current stable core soon. >From now on, 1.2 will stay in "release" mode, we will just fix bugs that happen, but there will be no dedicted "1.2.3" release. (For 1.3, we will do the same: no point release, just an eternal stream of bug fixes in 1.3 Release The version number is just 1.3 plus the update number, that's enough) Full ---- Failing Tests: 4 Open Bugs: 1 http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2.2-DevImage Issue 4166: Failing Tests: OBFakeBrowserTest (ConfigurationOfOmniBrowser needs update) So somone needs to take the current 1.3 of OB Metacello and sync the 1.2 config to load the same packaged. Should not be hard to do. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 16, 2011

Re: [Pharo-project] Zinc in PharoDev (was Re: XML maintainer???)

by StÃ©phane Ducasse

On May 16, 2011, at 3:03 AM, GermÃ¡n Arduino wrote: > Hi: > > I saw in your image that Zinc is already loaded. > > It will be at this way in the images from now? I'm asking because I > must decide what path take with XMLRPC. If Zinc will be the default to > use, I will adapt xmlrpc to work with Zn. yes zinc will be in core. Stef > > I know that xmlrpc is not heavily used but still I think is cool > having the tools in the image to expose an easy and straightforward > API. > > I wait comments. > > Cheers. > GermÃ¡n. > > > 2011/5/15 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> So...we added XML to PharoDev. Where are the maintaners? Could you please >> check these issues? >> >> Thanks! >> >> mariano >> >> ---------- Forwarded message ---------- >> From: <pharo(a)googlecode.com> >> Date: Sun, May 15, 2011 at 8:50 PM >> Subject: [Pharo-bugtracker] Issue 4232 in pharo: Failing Tests in Full: XML >> To: pharo-bugtracker(a)lists.gforge.inria.fr >> >> >> Status: Accepted >> Owner: marcus.d...(a)gmail.com >> Labels: Milestone-1.3-DevImage >> >> New issue 4232 by marcus.d...(a)gmail.com: Failing Tests in Full: XML >> http://code.google.com/p/pharo/issues/detail?id=4232 >> >>>>> >>>>> XML.Tests.Parser.Nodes.XMLObservableListTest.testReplaceFromToWithStartingAt >>>>> 0.0 1 >>>>> >>>>> XML.Tests.Parser.Nodes.XMLOrderedListTest.testReplaceFromToWithStartingAt >> >> >> _______________________________________________ >> Pharo-bugtracker mailing list >> Pharo-bugtracker(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> >

May 16, 2011

[Pharo-project] ***HIGHLY IMPORTANT*** call for Configuration of Browsers and infrastructure

by StÃ©phane Ducasse

Miguel, torsten, alexandre, mariano, dale and others This is *****REALLY***** important that we put in place an infrastructure and process + browser (already done) to publish configurations for each projects. We nearly have everything. Alexandre could we have a menu to freeze a configuration in a particular distribution repository? Guys could you take action on this point? Stef

May 16, 2011

Re: [Pharo-project] SSL/HTTPS -SecureSocketStream/SSLSessionforPharo/Squeak and otherSmalltalk implementations

by Rob Withers

StÃ©phane, Sven and friends, I created a fork project called CryptoPharo on squeaksource.com. I added StÃ©phane and Sven as admins. So, connect to: MCHttpRepository location: 'http://www.squeaksource.com/CryptoPharo' user: '' password: '' I pulled the base Cryptography package, and made a few fixes...the SSL package, and tried to get it running...and copied the CryptoPlugins without loading it. The mouse clicks were real jumpy and it automatically copied some versions to PharoInbox, I believe, totally out of my control. I don't have a lot of time to offer, unfortunately, as I am quite busy with other things in my life like rebuilding a 240z. I will see if I can take another look at it later this week, but it would be best if you guys can take the initiative and own it. Below are a few notes I took. Regards, Rob ------------------------------------------ Crypto: Ported the crypto code over. All tests seem to pass except #raisedTo:modulo: is god awful slow and so I bailed on the DiffieHellman and ElGamal tests after a few minutes of thought. The RSA test is a little slow, but ends up passing within 10s of seconds. The chain of calls which end up calling #raisedTo:modulo: is --- PrimesFinder>>primeOfSize: MillerRabin>>isProbablyPrime: LargePositiveInteger>>raisedto:modulo: -------------------------------------------- SSL: HTTPSocket class>>httpGetDocument:args:accept:request: has a problem with: '' asNumber with this line of code: port := (serverName copyFrom: index+1 to: serverName size) asNumber. where serverName = 'https:' and index = 6 Note: this is using HTTPSocket rather than HttpsSocket due to the string conversion to a Url subclass resolving to HttpUrl, rather than HttpsUrl. Initial port of SSL to CryptoPharo. Fixed hex issue with CipherSuite. Problems remain, with testCertStore (setting up private key is referencing RSAKey, which is gone and is using a call: #exponent:modulo: that is a RSAPublicKey thing and not a RSAPrivateKey thing) and with sending and getting data, but the Socket is reaching a connected state, so the handshake seems to be working. Not sure how given the perf issues with DiffieHellman. Actually, I did get a BAD REQUEST response, so data is flowing over the connection. Try: SSLSocket newConnection: 'www.cacert.org' port: 443 and check for connected (isConnected), then send: a command and receive a response.

May 16, 2011

[Pharo-project] Zinc in PharoDev (was Re: XML maintainer???)

by GermÃ¡n Arduino

Hi: I saw in your image that Zinc is already loaded. It will be at this way in the images from now? I'm asking because I must decide what path take with XMLRPC. If Zinc will be the default to use, I will adapt xmlrpc to work with Zn. I know that xmlrpc is not heavily used but still I think is cool having the tools in the image to expose an easy and straightforward API. I wait comments. Cheers. GermÃ¡n. 2011/5/15 Mariano Martinez Peck <marianopeck(a)gmail.com>: > So...we added XML to PharoDev. Where are the maintaners?Â Could you please > check these issues? > > Thanks! > > mariano > > ---------- Forwarded message ---------- > From: <pharo(a)googlecode.com> > Date: Sun, May 15, 2011 at 8:50 PM > Subject: [Pharo-bugtracker] Issue 4232 in pharo: Failing Tests in Full: XML > To: pharo-bugtracker(a)lists.gforge.inria.fr > > > Status: Accepted > Owner: marcus.d...(a)gmail.com > Labels: Milestone-1.3-DevImage > > New issue 4232 by marcus.d...(a)gmail.com: Failing Tests in Full: Â XML > http://code.google.com/p/pharo/issues/detail?id=4232 > >>>> >>>> XML.Tests.Parser.Nodes.XMLObservableListTest.testReplaceFromToWithStartingAt >>>> Â Â 0.0 Â Â 1 >>>> >>>> XML.Tests.Parser.Nodes.XMLOrderedListTest.testReplaceFromToWithStartingAt > > > _______________________________________________ > Pharo-bugtracker mailing list > Pharo-bugtracker(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker > > > > -- > Mariano > http://marianopeck.wordpress.com > >

May 16, 2011

Re: [Pharo-project] SSL/HTTPS - SecureSocketStream/SSLSessionforPharo/Squeak and other Smalltalk implementations

by David T. Lewis

On Sat, May 14, 2011 at 01:13:29PM +0200, Nicolas Cellier wrote: > 2011/5/14 St?phane Ducasse <stephane.ducasse(a)inria.fr>: > >>> > >> > >> I accelerated raisedTo:modulo: a bit with a primitive > >> (http://bugs.squeak.org/view.php?id=7120) but that's not enough > > Nicolas > > > > do you know why it was not integrated? > > It is a good candidate to check the build system of the VM and their evolution. > > Igor (I gave the windows distribution) to the arnaud so I hope that soon we will get a new windows slave for jenkins. > > > > Stef > > > > Don't know. Nicolas, I added your LargeIntegersPlugin>>primMontgomeryTimes:modulo:mInvModB: in SqS/VMMaker/VMMaker-dtl.233 (interpreter VM only, not Cog), and added some notes to http://bugs.squeak.org/view.php?id=7120. It compiles and runs correctly on both 32 and 64 bit platforms, but I cannot confirm the performance gain, so examples or tests would be helpful. On my system I built 32 and 64-bit versions, and I can confirm that the primitive runs and that the results are as expected: 12345678907 raisedTo: 3 modulo: 12345678917 ==> 12345677917 12345678907 montgomeryRaisedTo: 3 modulo: 12345678917 ==> 12345677917 But performance is not good in the example I came up with. On an interpreter VM (not Cog): Time millisecondsToRun: [100000 timesRepeat: [12345678907 raisedTo: 3 modulo: 12345678917]] ==> 633 Time millisecondsToRun: [100000 timesRepeat: [12345678907 montgomeryRaisedTo: 3 modulo: 12345678917]] ==> 1415 > > Don't know. I also have my modest bitShift: improvments pending > (http://bugs.squeak.org/view.php?id=7109) > Maybe I haven't performed enough tests to assert the performance gain. > The changes are reliable, I run a VM with both improvments without > crash for months. I have not looked at http://bugs.squeak.org/view.php?id=7109 yet but will do so. Dave

May 15, 2011

[Pharo-project] XML maintainer??? Fwd: [Pharo-bugtracker] Issue 4232 in pharo: Failing Tests in Full: XML

by Mariano Martinez Peck

So...we added XML to PharoDev. Where are the maintaners? Could you please check these issues? Thanks! mariano ---------- Forwarded message ---------- From: <pharo(a)googlecode.com> Date: Sun, May 15, 2011 at 8:50 PM Subject: [Pharo-bugtracker] Issue 4232 in pharo: Failing Tests in Full: XML To: pharo-bugtracker(a)lists.gforge.inria.fr Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3-DevImage New issue 4232 by marcus.d...(a)gmail.com: Failing Tests in Full: XML http://code.google.com/p/pharo/issues/detail?id=4232 XML.Tests.Parser.Nodes.XMLObservableListTest.testReplaceFromToWithStartingAt >>> 0.0 1 >>> XML.Tests.Parser.Nodes.XMLOrderedListTest.testReplaceFromToWithStartingAt >>> >> _______________________________________________ Pharo-bugtracker mailing list Pharo-bugtracker(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker -- Mariano http://marianopeck.wordpress.com

May 15, 2011