- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Amazon AWS S3 Monticello Mirror
by Marcus Denker May 16, 2011

May 16, 2011

On May 15, 2011, at 11:12 PM, StÃ©phane Ducasse wrote: > thanks this is an excellent initiative. > Marcus will love that. > Yes! We should get that setup... very nice! Whose Amazon Account do we use? Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] XML maintainer??? Fwd: [Pharo-bugtracker] Issue 4232 in pharo: Failing Tests in Full: XML
by Mariano Martinez Peck May 16, 2011

May 16, 2011

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

1 1

[Pharo-project] [TODO] Bug Tracker Status (429)
by Marcus Denker May 16, 2011

May 16, 2011

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.

1 0

[Pharo-project] SSL/HTTPS - SecureSocketStream/SSLSession for Pharo/Squeak and other Smalltalk implementations
by Sven Van Caekenberghe May 16, 2011

May 16, 2011

SSL/HTTPS - SecureSocketStream/SSLSession for Pharo/Squeak and other Smalltalk implementations HTTP client and server functionality has become an essential part of any Smalltalk implementation. There exist various open source solutions delivering this functionality. Users quickly find out that HTTPS is not as readily available as HTTP. Although a solution exists in the form of SqueakSSL, it is not easily portable to Pharo and certainly not to other Smalltalk implementations. Furthermore, SqueakSSL is incomplete and more a working proof of concept than a high quality, high performance, maintainable piece of code, partially because of its dependence on the internals of SocketStream. Hence, some people wanting HTTPS on Pharo as well as one organisation have come foreword with a bounty to force a solution. Here are the requirements, a plan of action and a number of steps to build such a solution. First of all, it would be stupid not to start from the work already done for SqueakSSL. Any new solution should start from the existing plugin, from the existing set of primitives and from the current implementation of these primitives for the Windows, Mac OS X and Linux platforms. The Smalltalk part of the solution should be as platform independent as possible. We therefor need a new, clean implementation of SocketStream, with proper internal buffering and optimised versions of the bulk input and output primitives. The code should be time and space efficient. At first, only binary I/O is needed. Encoding/decoding is best done by wrapping the stream. Maybe a bivalent stream could be an option. The current ASCII support in quite limited. Next a SecureSocketStream can be implemented using this clean base combined with the SSLSession primitives. Here too, time and space efficiency are important although SSL will by definition be less efficient. Eventually, HTTP frameworks can then use this SecureSocketStream to actually implement HTTPS. Although the primary requirement is client functionality, server functionality should be provided as well. Next the existing issues with certificates need to be resolved, on all 3 platforms. Finally, the C code of the plugin for each of the 3 platforms needs to be cleaned up and improved where necessary. This requires contributions from developers who know and understand a platform as well as how SSL is supposed to work. Furthermore they have to understand and be motivated to work on Smalltalk plugins. Up to 3 different developers might be needed. The current implementation on Mac OS X does not seem to (directly) use the standard OpenSSL library from Linux although this library exists on Mac OS X. This could be an opportunity to reduce the number of implementations of the plugin to 2 API's. Needless to say the whole implementation should be open source licensed (MIT), be documented and have a number of units tests to cover it's main functionality as well edge cases encountered in the field. Friendly cooperation with other open source projects in the Smalltalk world is a plus. This project should benefit the whole community. The bounty should be split in different parts. The first part is setting up the new project, delivering the new SocketStream, SSLSession and SecureSocketStream, including the HTTPS client proof of concept. Traction within the community has to be developed. Next the issues with the plugin have to be identified. Then the work on the plugin code for each platform has to be defined and 3 more bounties could be offered. The goal should be to include the plugin in VM's by default. With a proper solution to the plugin issues, SSL server functionality should be no problem. I offer to take on part one and help manage the coordination of this project. So is there anyone capable and willing to help out on the plugin on on one or more platforms for part of the bounty ? Are there others who wish to raise the bounty ? We will need a couple of good beta testers who understand this field as well. Sven

6 18

[Pharo-project] Amazon AWS S3 Monticello Mirror
by Sven Van Caekenberghe May 15, 2011

May 15, 2011

Hello, I did a little proof of concept: I set up an Amazon AWS S3 Monticello Mirror. I wrote a Smalltalk script using the Zn HTTP client, the Zinc-AWS S3 client and some pieces of MCHttpRepository and ZnMonticelloServerDelegate to copy all 273 entries of http://www.squeaksource.com/ZincHTTPComponents/ into a folder called 'ZincHTTPComponents' in an S3 bucket named 'mc-mirror'. Then I configured things a bit to make it look like a public read-only Monticello HTTP repository. The net result is this Monticello repository: MCHttpRepository location: 'http://mc-mirror.s3-website-eu-west-1.amazonaws.com/ZincHTTPComponents/' user: '' password: '' Which works as it should on unmodified images (except that it is read-only). With a proper DNS CNAME entry the hostname could become something more friendly. Next, I will try to turn this little hack into something more robust, that can also efficiently resynchronize the copy when versions are added to the original. Then, this could become the bot I talked about earlier. IMHO this could be a very robust fallback mechanism for SqueakSource, and even a primary one for those repositories you never commit to (which is most of them) and thus take off some the load of SqueakSource. Sven

2 1

[Pharo-project] [ANN] PharoDev-1.3-13201
by Mariano Martinez Peck May 15, 2011

May 15, 2011

Hi. IMPORTANT: This is not the final 1.3 release, it just one simple snapshot and one point. This image is based in PharoCore 1.3 13201 and includes also several fixes for the external packages like OB. Thanks to Fernando the Transcript is now much better. The image is here: https://gforge.inria.fr/frs/download.php/28547/Pharo-1.3-13201.zip And it was build by Hudson: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.3/150/ Nile was removed from dev image which means there are only 3 failing tests :) Best regards, -- Mariano http://marianopeck.wordpress.com

1 0

[Pharo-project] redundancy
by StÃ©phane Ducasse May 15, 2011

May 15, 2011

Yes. So how do we do that? Dale can we use the ssgemstone you host? Stef >> > The problem is that the network operator is down... > > see http://code.google.com/p/pharo/issues/detail?id=4218 > > We should really t hink hard about redundancy... >

3 5

[Pharo-project] [update 1.3] #13201
by stephane ducasse May 15, 2011

May 15, 2011

13201 ----- - Issue 4222: Senders/Implementors cannot remove methods from there nor to right click. - Issue 4230: Need to reinitialize desktop command shortcuts. Thanks Damien Cassou. - Issue 4155: Check for copied methods. Thanks Camillo Bruni.

1 0

[Pharo-project] [update 1.3] #13200
by Marcus Denker May 15, 2011

May 15, 2011

13200 ----- Issue 4227: Failign Test: ImageSegmentTestExport.testSaveAndLoadImageSegmentToDiskWithoutGC Issue 4224: Put search button next to search input text in Finder Issue 4226: Issue 3597 has not been included completely Issue 4225: Latest Transcript changes have broken alt+t and alt+k Issue 3732: Change #standardWindowExtent Was: default omni browser size bigger -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Which mailing-list for issues ?
by laurent laffont May 15, 2011

May 15, 2011

I'm still not subscribed, I want to, but it's not in http://www.pharo-project.org/community nor http://www.pharo-project.org/community/issue-tracking Laurent.

2 2