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

failing test in writing files

by sheridan＠sheridan-mahoney.com

Hi there, I have a failing test and was wondering if anyone would have a sense as to why: | testString filename file | testString := 'ascii String'. filename := 'test-file-' , 99 atRandom printString , '.txt'. filename asFileReference ensureDelete. file := filename asFileReference writeStreamDo: [ :stream | stream nextPutAll: testString; crlf ]. self assert: file species = FileStream. Many thanks, Sheri

Dec. 4, 2014

Re: [Pharo-dev] Please delete .mcz file in http://www.squeaksource.com/MetacelloRepository

by Dale Henrichs

Thanks Dave! On Wed, Dec 3, 2014 at 4:00 PM, David T. Lewis <lewis(a)mail.msen.com> wrote: > On Wed, Dec 03, 2014 at 02:01:28PM -0800, Dale Henrichs wrote: > > The .mcz is triggering Gofer errors for me during automated loads and of > > course the place to get a new version of Gofer from is > > http://www.squeaksource.com/MetacelloRepository ... > > > > If someone with admin privileges could deleted the .mcz file that'd be > > great! > > Hi Dale, > > I have admin access to squeaksource.com, so I will delete it. Note, I have > noticed problems in the past where deleted versions return several days > later like zombies. I will also manually delete the file from the ss file > directory, but let me know if it comes back a few days from now. > > This is the file that was saved with the file name ".mcz": > > File: .mcz > Author: > Timestamp: 2 December 2014 11:14:44 am > UUID: ae6100fd-7bf3-4845-a640-d03e24b3588a > Ancestors: ConfigurationOfRefactoringBrowser-SK.77 > Message: added update methods to AAAObject and subclasses > Diff: .diff > Changeset: (@ConfigurationOfRefactoringBrowser-SK.77).cs > Downloads: Web: 1 > > I saved a backup copy of the file in case it is needed, but whoever was > trying to commit the ConfigurationOfRefactoringBrowser update will need > to save it again with the intended file name. > > HTH, > Dave > > >

Dec. 4, 2014

Re: [Pharo-dev] Please delete .mcz file in http://www.squeaksource.com/MetacelloRepository

by David T. Lewis

On Wed, Dec 03, 2014 at 02:01:28PM -0800, Dale Henrichs wrote: > The .mcz is triggering Gofer errors for me during automated loads and of > course the place to get a new version of Gofer from is > http://www.squeaksource.com/MetacelloRepository ... > > If someone with admin privileges could deleted the .mcz file that'd be > great! Hi Dale, I have admin access to squeaksource.com, so I will delete it. Note, I have noticed problems in the past where deleted versions return several days later like zombies. I will also manually delete the file from the ss file directory, but let me know if it comes back a few days from now. This is the file that was saved with the file name ".mcz": File: .mcz Author: Timestamp: 2 December 2014 11:14:44 am UUID: ae6100fd-7bf3-4845-a640-d03e24b3588a Ancestors: ConfigurationOfRefactoringBrowser-SK.77 Message: added update methods to AAAObject and subclasses Diff: .diff Changeset: (@ConfigurationOfRefactoringBrowser-SK.77).cs Downloads: Web: 1 I saved a backup copy of the file in case it is needed, but whoever was trying to commit the ConfigurationOfRefactoringBrowser update will need to save it again with the intended file name. HTH, Dave

Dec. 4, 2014

Re: [Pharo-dev] Please delete .mcz file in http://www.squeaksource.com/MetacelloRepository

by Dale Henrichs

Fortunately I was able to patch a single (old) configuration to get around the my particular build problem, but that .mcz file is still lurking.... Dale On Wed, Dec 3, 2014 at 2:01 PM, Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > The .mcz is triggering Gofer errors for me during automated loads and of > course the place to get a new version of Gofer from is > http://www.squeaksource.com/MetacelloRepository ... > > If someone with admin privileges could deleted the .mcz file that'd be > great! > > Dale >

Dec. 3, 2014

Please delete .mcz file in http://www.squeaksource.com/MetacelloRepository

by Dale Henrichs

The .mcz is triggering Gofer errors for me during automated loads and of course the place to get a new version of Gofer from is http://www.squeaksource.com/MetacelloRepository ... If someone with admin privileges could deleted the .mcz file that'd be great! Dale

Dec. 3, 2014

how to make ad for PharoDays?

by stepharo

Dear Pharoers we would like to spread some noise around PharoDays and it may be good to send the announce esteban sent around. May be to FOSDEM would be good. Stef

Dec. 3, 2014

Re: [Pharo-dev] Duration year

by Hilaire

Le 02/12/2014 17:34, Sean P. DeNigris a Ã©crit : > One solution (just ignore the source ha ha) - > http://msdn.microsoft.com/en-us/library/system.datetime.addyears%28v=vs.110… > Something like ? Date>>addYears: integer ^ Date year: self year + integer month: self monthIndex day: ((self dayOfMonth = 29 and: [(Year isLeapYear: self year + integer) not and: [Year isLeapYear: self year]]) ifTrue: [ 28 ] ifFalse: [ self dayOfMonth]) -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

Dec. 3, 2014

Re: [Pharo-dev] terminating a String in Smalltalk?

by Sven Van Caekenberghe

> On 03 Dec 2014, at 19:14, sheridan(a)sheridan-mahoney.com wrote: > > > Hi all, > > How do you terminate a string in Smalltalk so that it can be written to a file? > > Thanks, > > Sheridan [ this is a question for pharo-users ] I don't understand the question, what is 'terminate a string' ? Here is how you write to a file: 'myfile.txt' asFileReference writeStreamDo: [ :out | out nextPutAll: 'Hello World!' ]. If you want a line end, you can do 'myfile.txt' asFileReference writeStreamDo: [ :out | out nextPutAll: 'Hello World!'; cr ]. There is also #lf and #crlf. It is also possible to do line end conversions. What are you trying to do, what does not work ? Sven

Dec. 3, 2014

terminating a String in Smalltalk?

by sheridan＠sheridan-mahoney.com

Hi all, How do you terminate a string in Smalltalk so that it can be written to a file? Thanks, Sheridan

Dec. 3, 2014

Re: [Pharo-dev] Code retrieval on primitive failed

by Blondeau Vincent

De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de ClÃ©ment Bera EnvoyÃ© : mercredi 3 dÃ©cembre 2014 17:54 Ã : Pharo Development List Objet : Re: [Pharo-dev] Code retrieval on primitive failed Please send the full stack trace. You don't have only three lines, do you ? No, indeed (the full stack is attached). There's one solution that Igor does sometimes that you can try...For that you need to remember what code you changed that now crashes the image in smalltalk. Do you know what code crash your image ? Could you rewrite it (exactly the same code) in a fresh image ? If so the process is as follow: - rewrite the crashing code in a fresh image - extract the bytecode from the compiled method - open a copy of your image with an hexadecimal editor, look for the bytecode pattern, replace it by returnself (byte 120 the number of times needed) - try open your copy. Do as little things as possible (typically, only file out your packages, monticello will most probably not work) Ok I will try this but this is more a generic printing method that is the problem (see trace)â¦ And not a specific methodâ¦ I tried but it seems not adapted to my caseâ¦ The alternative is to open your image on top of the cog simulator. Word has been that there's a Pharo 3 image running the cog simulator, you can use that to debug the code and fix it. Alternatively use a squeak vmmaker image that you can build with this script: $ svn co http://www.squeakvm.org/svn/squeak/branches/Cog/image $ cd ./image $ ./buildsqueaktrunkvmmakerimage.sh You put a halt on the implementation of primitive 117 in the simulator (named primitives call such as NB calls) to catch the crash and fix it from there in the simulator. That seems better ! I am trying this way. Good luck and have fun :-) Thanks :) 2014-12-03 17:04 GMT+01:00 Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>>: Hello everyone, I am doing some developments with NativeBoost and unfortunaly I succeed to save my image in a unstable state. I am using the last moose image i.e.: Pharo3.0 - Latest update: #30860. So when I want to launch my image, I get a primitive faillure. The interesting part of the stack trace is : Stack backtrace: [07EE7A1B] ??? + 0 in (null) [00539AB5] ??? + 1284789 in Pharo.exe Smalltalk stack dump: 0x2410b8 M NBFFICallout class(NBNativeCodeGen class)>retrySend: 0x4c70b4c: a(n) NBFFICallout class 0x2410ec I NBFFICallout class(NBNativeCodeGen class)>retrySend: 0x4c70b4c: a(n) NBFFICallout class 0x78a0d90 s RDoubleVector(OrderedCollection)>at: Then I wanted to retrieve my changes on a new image but, as the doIts are not recorded, I have neither the method deletions nor all the operations on classes nor the trait methods that are recorded as Doits with preamble: Trait method. I tried to launch my image with squeak (which doesnât support NativeBoost) to hope saving or commit my code. But as I am calling a primitive at startup of the image to initialize the external environement. I got the following trace : [31m==== Startup Error: PrimitiveFailed: primitive #isEnabled in NativeBoost class failed [0mNativeBoost class(Object)>>primitiveFailed: NativeBoost class(Object)>>primitiveFailed NativeBoost class>>isEnabled NativeBoost class>>forCurrentPlatform NativeBoost class>>loadSymbol:fromModule: RSession class(Object)>>nbGetSymbolAddress:module: So what can I do to retrieve all my code without loose a day to rewrite it? Thanks in advance Vincent ________________________________ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. ________________________________ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Dec. 3, 2014