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

Re: [Pharo-project] Need help with 1.3 Full Image

by Marcus Denker

On Fri, May 13, 2011 at 10:25 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > I'm really surprised. I'm also surprised that you say that when you did not > even tried to port your tools to 1.2 during the release candidate phase and that people > tried and failed and you started to port your tool when 1.2 was released. > As a result, we will just never do a beta/rc1/rc2/rc3 phase again. When 1.3 will be released, it will be what used to be beta. And everyone who just uses releases will be therefore tricked into using it :-) Marcus -- Marcus DenkerÂ --Â denker(a)acm.org http://www.marcusdenker.de

May 13, 2011

Re: [Pharo-project] 1.3-Core

by Sven Van Caekenberghe

On 12 May 2011, at 22:50, Alexandre Bergel wrote: >> Can you try a simple thing like: >> >> ZnClient get: 'http://zn.stfx.eu/zn/small.html' > > It returns: a ZnResponse(400 Bad Request text/html 3181B) OK, here is a quick fix/patch: ZnRequestLine>>writeOn: stream | writeStream | writeStream := ZnBivalentWriteStream on: stream. writeStream nextPutAll: self method; space. ZnNetworkingUtils default isProxySet ifTrue: [ self uri printOn: writeStream ] ifFalse: [ self uri printPathQueryFragmentOn: writeStream ]. writeStream space; nextPutAll: self version; nextPutAll: String crlf The problem was that for an HTTP request through a proxy, the url in the request line must be absolute. Let me know if this works for you. There is another problem as well: access to, at least localhost, should not go through the proxy. I am fixing that right now. I want you to be able to run all Zn unit tests with a proxy set, but half of them are accessing localhost. Anyway, the full fixes will be committed to the Zn repos first, and will have to be migrated to Pharo next. Regards, Sven

May 13, 2011

Re: [Pharo-project] Need help with 1.3 Full Image

by StÃ©phane Ducasse

On May 13, 2011, at 9:37 AM, Lukas Renggli wrote: >> I personally think this really wants to tell us something, but that's just me. > > Yes, indeed. Thank you for fixing all the things in Pharo 1.2. This is > really important. > > I really don't understand why Pharo is pushing so hard towards Pharo > 1.3 while even Pharo 1.2.1 is not really stable for daily work yet. > The number of really critical bugs that appear in Pharo 1.2 every day > makes me wonder how many people are just stuck with Pharo 1.1? :-( uh? what are these bugs? I'm really surprised. I'm also surprised that you say that when you did not even tried to port your tools to 1.2 during the release candidate phase and that people tried and failed and you started to port your tool when 1.2 was released. You were undermining our process sadly. Stef > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >

May 13, 2011

Re: [Pharo-project] Need help with 1.3 Full Image

by Marcus Denker

On May 13, 2011, at 9:38 AM, Lukas Renggli wrote: >> I personally think this really wants to tell us something, but that's just me. > > Yes, indeed. Thank you for fixing all the things in Pharo 1.2. This is > really important. > > I really don't understand why Pharo is pushing so hard towards Pharo > 1.3 while even Pharo 1.2.1 is not really stable for daily work yet. Keep in mind that 1.2.1 is unchanged. Fixes are added to 1.2.2a, and due to a change in 1.2 (that was *a bad idea*!!!), you need to set the version number to 1.2.2a to see any updates. The first update of 1.2.2a fixes this wrong change. We should release 1.2.2 just to get this problem fixed and update updates again. Another thing I would like is to not have one rolling release for stable. that is, there is 1.2 update 12XXX And nothing else, fixes get pushed, images build by Hudson, no releases on that level. > The number of really critical bugs that appear in Pharo 1.2 every day There is no bug reported in 1.2 that is not already in 1.1: http://code.google.com/p/pharo/issues/list?can=2&q=milestone%3D1.2.2 > makes me wonder how many people are just stuck with Pharo 1.1? :-( Maybe we need a dedicated stable team? From my financing, it would be hard to justify working purely on 1.2... I can work on 1.3, because we want to change the system to be something really great. But maintaining 1.2 is hard to justify as a researcher.... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 13, 2011

Re: [Pharo-project] About Releasing 1.2.2

by Mariano Martinez Peck

On Fri, May 13, 2011 at 8:53 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > Hello, > > We should do a 1.2.2 release very soon. I suggest this weekend for Core, > and then the Agony beginns again > to find someone who is willing to fix Full... > > 1) One Thing to do in Core 1.2.2: > - > http://code.google.com/p/pharo/issues/list?can=2&q=milestone%3D1.2.2 > Issue 3732: Change #standardWindowExtent Was: default omni > browser size bigger > The problem is that the RealEstateAgent is made for 1996 iMacs.. so > it actually gives out very small windows > up to a tiny maximum, leading for OB to open witha very, very very > ugly small screen. > Workaround Fix: hack to return a minum windows that is large enough > (war to go, I guess) > Real fix: rewrite RealEstateAgent to do something sensible for > today's screens. (for later) > > > 2) One Thing to do in Full 1.2.2: > - > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2.2-DevImage > Issue 4166: Failing Tests: OBFakeBrowserTest > (ConfigurationOfOmniBrowser needs update) > This means someone needs to update the MetaCello config to load the > right versions of OB (which need > to be copied to the pharo OB repo, too) > > I did this for Pharo 1.3. ConfigurationOfOmniBrowser version 1.3. MAYBE (I have no idea) it also works in Pharo 1.2. In which case we may try to use it. > > Wo wants do do these? > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > -- Mariano http://marianopeck.wordpress.com

May 13, 2011

Re: [Pharo-project] Need help with 1.3 Full Image

by Tudor Girba

Hi, On 13 May 2011, at 09:37, Lukas Renggli wrote: >> I personally think this really wants to tell us something, but that's just me. > > Yes, indeed. Thank you for fixing all the things in Pharo 1.2. This is > really important. Indeed. Thanks, Marcus. > I really don't understand why Pharo is pushing so hard towards Pharo > 1.3 while even Pharo 1.2.1 is not really stable for daily work yet. > The number of really critical bugs that appear in Pharo 1.2 every day > makes me wonder how many people are just stuck with Pharo 1.1? :-( What kind of critical bugs are these? Cheers, Doru > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > -- www.tudorgirba.com "Relationships are of two kinds: those we choose and those that happen. They both matter."

May 13, 2011

Re: [Pharo-project] Need help with 1.3 Full Image

by Lukas Renggli

> I personally think this really wants to tell us something, but that's just me. Yes, indeed. Thank you for fixing all the things in Pharo 1.2. This is really important. I really don't understand why Pharo is pushing so hard towards Pharo 1.3 while even Pharo 1.2.1 is not really stable for daily work yet. The number of really critical bugs that appear in Pharo 1.2 every day makes me wonder how many people are just stuck with Pharo 1.1? :-( Lukas -- Lukas Renggli www.lukas-renggli.ch

May 13, 2011

[Pharo-project] Need help with 1.3 Full Image

by Marcus Denker

Hi, In the past, the build of the Full/Dev image was broken most of the time, leading to bugs being discovered late, bugs not fixed while everyone is using the system and getting bitten by them... Now the Dev/Full image exactly is a such a thing that has no bottleneck: it's just some load scripts loading third party tools/libs. Just editing scripts and bug the maintainers. Nothing else to do. So it should be fixed far faster and much easier than Core, as it can be done in parallel? Right? Right? Wrong. The only person doing anyting is Mariano... (and me, I fixed 1.2 Full after is was broken an *astonishing* 23 *days* !!!!) I personally think this really wants to tell us something, but that's just me. So what we need is people who look at this list: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.3-DevImage And *fix* the issues. Fast. I can not. Really not. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 13, 2011

[Pharo-project] About Releasing 1.2.2

by Marcus Denker

Hello, We should do a 1.2.2 release very soon. I suggest this weekend for Core, and then the Agony beginns again to find someone who is willing to fix Full... 1) One Thing to do in Core 1.2.2: - http://code.google.com/p/pharo/issues/list?can=2&q=milestone%3D1.2.2 Issue 3732: Change #standardWindowExtent Was: default omni browser size bigger The problem is that the RealEstateAgent is made for 1996 iMacs.. so it actually gives out very small windows up to a tiny maximum, leading for OB to open witha very, very very ugly small screen. Workaround Fix: hack to return a minum windows that is large enough (war to go, I guess) Real fix: rewrite RealEstateAgent to do something sensible for today's screens. (for later) 2) One Thing to do in Full 1.2.2: - http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2.2-DevImage Issue 4166: Failing Tests: OBFakeBrowserTest (ConfigurationOfOmniBrowser needs update) This means someone needs to update the MetaCello config to load the right versions of OB (which need to be copied to the pharo OB repo, too) Wo wants do do these? Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 13, 2011

Re: [Pharo-project] Small question in OSProcess

by StÃ©phane Ducasse

thanks david for your explanations! On May 12, 2011, at 11:13 PM, David T. Lewis wrote: > On Tue, May 10, 2011 at 04:02:02PM +0200, Adrien BARREAU wrote: >> >> Hi all, >> >> I just have a little question: >> Is there a way to change the working directory of my terminal with something in OSProcess? >> >> I mean: >> - I know I can change the working directory of the current process with "OSProcess thisOSProcess chDir: '/'" but of course it does nothing on the terminal >> - "OSProcess thisOSProcess command: 'cd /'" does absolutly nothing >> >> I hope it's clean enough. >> >> Regards, >> Adrien. >> > > The Unix or Windows concept of "current working directory" does not > really have any meaning in Squeak/Pharo itself. In Unix, which maintains > a single tree structured view of the file system(s), you may think of > it as associated with the shell that you are running. In Windows it > is similar but needs to accommodate the idea of separate volumes > (C:, D:, etc). > > The CommandShell package is a companion to OSProcess that implements > a simulation of Unix and Windows shell behaviour. Try loading CommandShell > in addition to OSProcess and I think that you will find what you are > looking for. > > If your question refers to a Unix (Linux, OS X, etc) platform, and you > are trying to do is change the current working directory for the terminal > from which you started your Pharo image, then it's a different issue. > This is basic Unix behavior - the program you are running (the VM) is > a child process of the program that started it (the shell in your > terminal window). A child process does not have access to its parent > process to do things like change its working directory. So when you > are doing things such as setting environment variables and so forth, > it affects the process that you are current in (the VM process), and > has no effect on the parent (the shell in your terminal window). > > HTH, > Dave > >

May 13, 2011