- Pharo-dev - lists.pharo.org

[Pharo-project] Call for Participation in the Smalltalk Devroom at FOSDEM 2013
by Stephan Eggermont Nov. 9, 2012

Nov. 9, 2012

Call for Participation in the Smalltalk Devroom at FOSDEM 2013. http://www.fosdem.org " A devroom for the Pharo, Squeak, Amber, GST, EtoilÃ©, Seaside, Moose Smalltalk projects & Newspeak as derived language. Smalltalk environments offer a very high development productivity, unmatched by their successors. Come do some pair programming with us and experience yourself the advantages of a real OO environment" The meetup will take place Sunday, February 3, 2013, from 9AM until 5PM, building AW. This room has 72 seats, a VGA video projector and wireless internet. More information will be available later. Proposals on content and format are welcome. People interested in running a session should announce that on the smalltalk-devroom mailing list, with the following information: - Their name - The project they are associated with - A short bio, to be put on the website along with their speaker name - (optionally) a picture of themselves - The title of their session (which will go on the website and in the booklet) - A abstract describing the session in further detail. - The desired length of the session. - The desired time slot in which they want to hold the session. Suggested values for the duration are 55min, 25min, 6m40 (Pecha Kucha). The desired time slot is meant to help you prevent conflicts with other dev rooms in which you might have a talk or your travel arrangements. There are alternative, non smalltalk-specific tracks available: lightning talk and the main track The deadline for submissions is December 31, 23:00 GMT+1. Discussion takes place on the smalltalk-devroom(a)lists.fosdem.org mailing list. Please subscribe if you are interested: https://lists.fosdem.org/listinfo/smalltalk-devroom The local VUB/ULB Smalltalkers have been asked to organize a sprint/BSUG meeting/Camp Smalltalk on Saturday February 2. Devroom related URLs: http://www.pharo-project.org http://www.squeak.org/ http://etoileos.com/ http://www.seaside.st/ http://smalltalk.gnu.org/ http://www.moosetechnology.org http://amber-lang.net http://newspeaklanguage.org/ http://www.esug.org

1 0

[Pharo-project] Pharo wiki?
by Sebastian Nozzi Nov. 9, 2012

Nov. 9, 2012

Hello Pharo Community, are there plans to host a Pharo wiki somewhere? (for tutorials, tips, faqs, documentation, ideas, brainstorming, etc.) Cheers, Sebastian

3 2

[Pharo-project] New command line option: load updates
by Marcus Denker Nov. 8, 2012

Nov. 8, 2012

Hi, There is now a command line option to load updates. To test it: wget --quiet -qO - http://pharo.gforge.inria.fr/ci/ciPharo20NBCog.sh | bash ./vm.sh Pharo.image update What is does it to load updates, then snapshot and quit. The idea is to use this in the new CI setup so we don't need any external scripts. -- Marcus Denker -- http://marcusdenker.de

3 2

[Pharo-project] [update 2.0] #20386
by Marcus Denker Nov. 8, 2012

Nov. 8, 2012

[update 2.0] #20386 20386 ----- Issue 6933: Fixing the fact that typing ... http://code.google.com/p/pharo/issues/detail?id=6933 Issue 6853: Monticello merge conflicts on reordered package names http://code.google.com/p/pharo/issues/detail?id=6853 Issue 6760: Traits dont get repackaged http://code.google.com/p/pharo/issues/detail?id=6760 Issue 6938: poolDictionaryNames in wrong package http://code.google.com/p/pharo/issues/detail?id=6938 Diff information: http://ss3.gemstone.com/ss/Pharo20/Traits-MarcusDenker.442.diff http://ss3.gemstone.com/ss/Pharo20/NECompletion-MarcusDenker.67.diff http://ss3.gemstone.com/ss/Pharo20/Monticello-MarcusDenker.728.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1236.diff -- Marcus Denker -- http://marcusdenker.de

3 3

[Pharo-project] pharo-2.0-tests Â» win - Build # 467 - Failure!
by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr Nov. 8, 2012

Nov. 8, 2012

1 1

[Pharo-project] pharo-2.0-tests Â» mac - Build # 467 - Failure!
by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr Nov. 8, 2012

Nov. 8, 2012

1 1

[Pharo-project] pharo-2.0-tests Â» linux - Build # 467 - Failure!
by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr Nov. 8, 2012

Nov. 8, 2012

1 1

[Pharo-project] [update 2.0] #20385
by Marcus Denker Nov. 8, 2012

Nov. 8, 2012

20385 ----- Issue 6936: Compiler tests dependent on TextMorph http://code.google.com/p/pharo/issues/detail?id=6936 Issue 6935: CompilerEvaluationTest dependent on Debugger http://code.google.com/p/pharo/issues/detail?id=6935 Issue 6934: move encodeForHTTP tests to own class http://code.google.com/p/pharo/issues/detail?id=6934 Issue 6918: Right click on packages over a category without MC corresponding package raises DNU http://code.google.com/p/pharo/issues/detail?id=6918 Diff information: http://ss3.gemstone.com/ss/Pharo20/NetworkTests-MarcusDenker.79.diff http://ss3.gemstone.com/ss/Pharo20/CompilerTests-MarcusDenker.127.diff http://ss3.gemstone.com/ss/Pharo20/CollectionsTests-MarcusDenker.578.diff http://ss3.gemstone.com/ss/Pharo20/CI-Core-MarcusDenker.48.diff -- Marcus Denker -- http://marcusdenker.de

2 1

Re: [Pharo-project] Increase memory
by Fernando Olivero Nov. 8, 2012

Nov. 8, 2012

Ciao Roberto, which is the current size of the image? (the .image file). If you evaluate the following a couple of times (print it cmd-p), you will cleanup most of the unreferenced objects in the image, it returns a number so you can compare it to successive evaluations. Smalltalk garbageCollect. You can also follow the pointers to objects, to detect objects which you suspect are just hanging around, and fail to be garbage collected, to clear those references. Open an inspector an any object,and the menu has that option. ( {Object. 1. #hello} inspect) . You can also, start with a fresh image. pd: if you search the mailing list, i remember Tudor writing about large images and vm's. On Thu, Nov 8, 2012 at 2:16 PM, roberto.minelli(a)usi.ch < roberto.minelli(a)usi.ch> wrote: > Hi, > > I was executing a piece of code that collects the revisions of a Git repo > in Pharo but it seems Pharo requires more memory.. > > How do I increase the available memory? > > Here is the log: > > SmalltalkImage>>signalLowSpace > OutOfMemory>>defaultAction > UndefinedObject>>handleSignal: > OutOfMemory(Exception)>>pass > PasteUpMorph>>becomeActiveDuring: in Block: [:ex | ... > BlockClosure>>cull: > MethodContext(ContextPart)>>handleSignal: in Block: [self > exceptionHandlerBlock cull: exception] > BlockClosure>>ensure: > MethodContext(ContextPart)>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > OutOfMemory(Exception)>>signal > OutOfMemory class(Exception class)>>signal > ByteArray class(Behavior)>>basicNew: > ByteArray class(Behavior)>>new: > ByteArray(SequenceableCollection)>>copyFrom:to: > ReadStream(PositionableStream)>>contents > GitPackedNonDelta(GitPackedObject)>>compressedData > GitPackedNonDelta(GitPackedObject)>>computeCRC > GitPackedNonDelta(GitPackedObject)>>loadFrom: > GitPackedObject class>>fromPack:at:in: > GitPackFile>>objectAtOffset: > GitPackFile>>objectNamed: > GitRepository>>packedObjectNamed:ifAbsent: in Block: [:pack | (pack > objectNamed: aHexHash)... > GitRepository>>packsDo: in Block: [:pack | aBlock value: pack] > OrderedCollection>>do: > GitRepository>>packsDo: > GitRepository>>packedObjectNamed:ifAbsent: > GitRepository>>objectNamed:ifAbsent: in Block: [self packedObjectNamed: > aHash ifAbsent: aBlock] > GitRepository>>looseObjectNamed:ifAbsent: in Block: [^ aBlock value] > False>>ifTrue:ifFalse: > > Thanks, > Roberto >

2 1

[Pharo-project] Increase memory
by roberto.minelli＠usi.ch Nov. 8, 2012

Nov. 8, 2012

Hi, I was executing a piece of code that collects the revisions of a Git repo in Pharo but it seems Pharo requires more memory.. How do I increase the available memory? Here is the log: SmalltalkImage>>signalLowSpace OutOfMemory>>defaultAction UndefinedObject>>handleSignal: OutOfMemory(Exception)>>pass PasteUpMorph>>becomeActiveDuring: in Block: [:ex | ... BlockClosure>>cull: MethodContext(ContextPart)>>handleSignal: in Block: [self exceptionHandlerBlock cull: exception] BlockClosure>>ensure: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: OutOfMemory(Exception)>>signal OutOfMemory class(Exception class)>>signal ByteArray class(Behavior)>>basicNew: ByteArray class(Behavior)>>new: ByteArray(SequenceableCollection)>>copyFrom:to: ReadStream(PositionableStream)>>contents GitPackedNonDelta(GitPackedObject)>>compressedData GitPackedNonDelta(GitPackedObject)>>computeCRC GitPackedNonDelta(GitPackedObject)>>loadFrom: GitPackedObject class>>fromPack:at:in: GitPackFile>>objectAtOffset: GitPackFile>>objectNamed: GitRepository>>packedObjectNamed:ifAbsent: in Block: [:pack | (pack objectNamed: aHexHash)... GitRepository>>packsDo: in Block: [:pack | aBlock value: pack] OrderedCollection>>do: GitRepository>>packsDo: GitRepository>>packedObjectNamed:ifAbsent: GitRepository>>objectNamed:ifAbsent: in Block: [self packedObjectNamed: aHash ifAbsent: aBlock] GitRepository>>looseObjectNamed:ifAbsent: in Block: [^ aBlock value] False>>ifTrue:ifFalse: Thanks, Roberto

2 1