February 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Streaming problem in case of errors

by Damien Cassou

Camillo has another suggestion: https://pharo.fogbugz.com/f/cases/13008 On Fri, Feb 28, 2014 at 2:48 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > You could consider wrapping the actual output stream with a version that counts its output before delegating (ZnBufferedWriteStream does something like that). It might involve some experimentation to get the API right. > > There is also LimitedWriteStream that might help. > > On 28 Feb 2014, at 14:36, Damien Cassou <damien.cassou(a)gmail.com> wrote: > >> On Fri, Feb 28, 2014 at 2:20 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> Please do, I can't imagine why it needs to do positioning just to write output, you know that I think the stream API is way to wide... >> >> >> this is used to count the number of written characters. As soon as >> 150000 characters are wrote, the method writes '...etc...' and then >> stops writing. >> >> I would have to change that by writing to a String-based stream and >> counting there before writing to Transcript. However, this is going to >> take memory space which might not exist as an out of memory could be >> the cause of this method to be executed. >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >> > > -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Feb. 28, 2014

Gettext broken in Pharo 3.0

by Usman Bhatti

Hello, I encountered a problem when trying to export the Gettext file in Pharo 3.0. In a Pharo 3.0 image, load Gettext and then do the following: TextDomainManager registerCategoryPrefix: 'Fuel' domain: 'Fuel'. GetTextExporter exportTemplate. Apparently, there are some deprecations and doing proceed on them shows a DNU: "RBMethodNode does not understand isMessageNode" I can report the bug somewhere to later find some time to correct it but Pharo bug tracker might not be the right place. Any ideas where this bug should be reported? If someone knowledgeable about RB related stuff can have a look at it, it would be great. tx, usman

Feb. 28, 2014

ws vs st extensions

by Esteban A. Maringolo

I have a naive question... Why if the BasicCodeLoader handler looks for .st files does the Workpace offer .ws as the default extension? Why not a single extension for Smalltalk files? (.st) and other for chunked content (changesets?) :) Esteban A. Maringolo

Feb. 28, 2014

Re: [Pharo-dev] Streaming problem in case of errors

by Sven Van Caekenberghe

You could consider wrapping the actual output stream with a version that counts its output before delegating (ZnBufferedWriteStream does something like that). It might involve some experimentation to get the API right. There is also LimitedWriteStream that might help. On 28 Feb 2014, at 14:36, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Fri, Feb 28, 2014 at 2:20 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> Please do, I can't imagine why it needs to do positioning just to write output, you know that I think the stream API is way to wide... > > > this is used to count the number of written characters. As soon as > 150000 characters are wrote, the method writes '...etc...' and then > stops writing. > > I would have to change that by writing to a String-based stream and > counting there before writing to Transcript. However, this is going to > take memory space which might not exist as an out of memory could be > the cause of this method to be executed. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

Feb. 28, 2014

Re: [Pharo-dev] Streaming problem in case of errors

by Damien Cassou

On Fri, Feb 28, 2014 at 2:20 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Please do, I can't imagine why it needs to do positioning just to write output, you know that I think the stream API is way to wide... this is used to count the number of written characters. As soon as 150000 characters are wrote, the method writes '...etc...' and then stops writing. I would have to change that by writing to a String-based stream and counting there before writing to Transcript. However, this is going to take memory space which might not exist as an out of memory could be the cause of this method to be executed. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Feb. 28, 2014

Re: [Pharo-dev] Streaming problem in case of errors

by Sven Van Caekenberghe

On 28 Feb 2014, at 14:12, Damien Cassou <damien.cassou(a)gmail.com> wrote: > P > Hi guys, > > when PharoDebug.log can't be created (e.g., when the image is in a non > writeable directory like /usr/share), the errors are sent to the > Transcript in the hope that they will be redirected to stdout or > stderr. However, ContextPart>>errorReportOn: is called when an > exception is signaled and this method assumes that the stream is > positionable (which is not the case for transscript, stdin and > stderr). I was planing on rewriting ContextPart>>errorReportOn: to > make it independent of #position. What do you think? Please do, I can't imagine why it needs to do positioning just to write output, you know that I think the stream API is way to wide...

Feb. 28, 2014

Streaming problem in case of errors

by Damien Cassou

P Hi guys, when PharoDebug.log can't be created (e.g., when the image is in a non writeable directory like /usr/share), the errors are sent to the Transcript in the hope that they will be redirected to stdout or stderr. However, ContextPart>>errorReportOn: is called when an exception is signaled and this method assumes that the stream is positionable (which is not the case for transscript, stdin and stderr). I was planing on rewriting ContextPart>>errorReportOn: to make it independent of #position. What do you think? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Feb. 28, 2014

Re: [Pharo-dev] git and metacello

by Goubier Thierry

This is because github: only works in Metacello, not in Monticello nor Gofer :( Thierry Le 28/02/2014 11:46, Yuriy Tymchuk a Ã©crit : > So far when I run > > ./pharo Pharo.image configgithub://User/Project:master ConfigurationOfProject --install=development > > > I get > > Error: No Monticello repository for URL scheme github > ZnUrl(Object)>>error: > ZnUrl>>mcRepositoryAsUser:withPassword: > Gofer>>url:username:password: > ConfigurationCommandLineHandler>>gofer > ConfigurationCommandLineHandler>>configuration > ConfigurationCommandLineHandler>>project > ConfigurationCommandLineHandler>>metacelloVersion: > > > > > On 28 Feb 2014, at 10:50, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com > <mailto:Benjamin.VanRyseghem.Pharo@gmail.com>> wrote: > >> On 28 Feb 2014, at 10:23, Yuriy Tymchuk <yuriy.tymchuk(a)me.com >> <mailto:yuriy.tymchuk@me.com>> wrote: >> >>> Can you share a script? Because as far as I understand, You test on >>> read-only staff, and then link you "the oneâ repo on your machine. >> >> Exactly :) >> >> Here is the script to build spec: >> https://github.com/spec-framework/spec/blob/master/install_Spec.sh >> My preference to link Spec repo is: >> https://gist.github.com/BenjaminVanRyseghem/9268250 >> >> Ben > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Feb. 28, 2014

Re: [Pharo-dev] git and metacello

by Yuriy Tymchuk

So far when I run ./pharo Pharo.image config github://User/Project:master ConfigurationOfProject --install=development I get Error: No Monticello repository for URL scheme github ZnUrl(Object)>>error: ZnUrl>>mcRepositoryAsUser:withPassword: Gofer>>url:username:password: ConfigurationCommandLineHandler>>gofer ConfigurationCommandLineHandler>>configuration ConfigurationCommandLineHandler>>project ConfigurationCommandLineHandler>>metacelloVersion: On 28 Feb 2014, at 10:50, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > On 28 Feb 2014, at 10:23, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > >> Can you share a script? Because as far as I understand, You test on read-only staff, and then link you "the oneâ repo on your machine. > > Exactly :) > > Here is the script to build spec: https://github.com/spec-framework/spec/blob/master/install_Spec.sh > My preference to link Spec repo is: https://gist.github.com/BenjaminVanRyseghem/9268250 > > Ben

Feb. 28, 2014

Re: [Pharo-dev] git and metacello

by Benjamin

On 28 Feb 2014, at 10:23, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Can you share a script? Because as far as I understand, You test on read-only staff, and then link you "the oneâ repo on your machine. Exactly :) Here is the script to build spec: https://github.com/spec-framework/spec/blob/master/install_Spec.sh My preference to link Spec repo is: https://gist.github.com/BenjaminVanRyseghem/9268250 Ben

Feb. 28, 2014