- Pharo-dev - lists.pharo.org

[Pharo-project] trying to load seaside from scratch into Pharo 1.1 or 1.1.1
by Lawson English Dec. 15, 2010

Dec. 15, 2010

I get a pristine one-click image for 1.1 or 1.1.1 from the pharo-project website and do: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside'; load. ConfigurationOfSeaside load. an hour or so into the install, I get message: Error: stream is already in a subclass of WAHtmlDocument. This is using Mac OS X SnowLeopard. :-( Lawson

1 0

[Pharo-project] Background changer script kills Pharo
by Tony Fleig Dec. 14, 2010

Dec. 14, 2010

I tried using the following background changer for Pharo (from http://book.pharo-project.org/book/CustomizingPharo/PuttingABackgroundPictu…) All was well and it nicely changed the background image to various images from socwall.com. I walked away and when I came back, Pharo was no longer running. To make a long story short, on Linux and OS X (I did not try Windows), after some period of time, regardless of whether I am actively using Pharo, Pharo either hangs (becomes unresponsive to input, using 100% CPU, images no longer changing) or disappears abruptly. I tried several variations of the script, including loading images from a local directory (i.e. no network code at all) and even loading images into an ImagePreview morph. In all cases, Pharo eventually either aborts or hangs. I have found nothing in the logs to indicate what happened -- no entries at the time of the abort or hang at all. Decreasing the delay seems to make it happen sooner; I can usually make it happen within 15 minutes of execution with a 2 second delay. It seems to happen more quickly when changing the background image than in an ImagePreview morph. I monitored Pharo's memory usage and it increased from 106 MB to 109 MB during the execution. Plenty of free memory on the system. My questions are: 1. How to debug this? Log to a file to see where it is hanging? 2. How to regain control of a hung Pharo. I tried Cmd-<everything> to no avail. 3. Does anyone have any idea what might be happening? Some resource being used up, a race condition, etc.? Here's the original script [[[ | rx str url form | str := (HTTPSocket httpGet: 'http://www.socwall.com/browse/index.php?wpLimit=1&wpSortby=8') contents. rx := '.*(http\://.+tb_.+\.jpg).*' asRegex. url := (rx matches: str) ifTrue: str := (rx subexpression: 2) copyWithRegex: 'tb_' matchesReplacedWith: '' ] ifFalse: [ nil ]. url ifNotNil: [ form := ImageReadWriter formFromStream: (HTTPSocket httpGet: url). World backgroundImage: form layout: #scaled]] on: Error do: [:ex| ]. 1 minute asDelay wait ] repeat ] newProcess name: 'Random background changer'; priority: Processor userBackgroundPriority; resume Regards, TF

4 5

Re: [Pharo-project] TODO for 1.2...
by Marcus Denker Dec. 14, 2010

Dec. 14, 2010

On Dec 14, 2010, at 9:34 PM, csrabak(a)bol.com.br wrote: > Why in the first link even with the selection "Open Issues", items marked "Fixed" or "Closed" are showing? > Closed: a bug of the bug tracker. Highly annyoing. Fixed. This means: the entry contains something that is a propesed fix in a loadable form. Needs to be integrated. But sometimes, it means more something like "Stef wants to look at this later and if it's not tagged it will be lost". :-) Marus > Just trying to understand... > > -- > Cesar Rabak > > > > > > Em 13/12/2010 14:54, Marcus Denker < marcus.denker(a)inria.fr > escreveu: > Open Bugs: > > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2 > > Failing Tests: > > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/lastCompleted… > > > and a failing build of non-Core: > > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/8/console > > > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] TODO for 1.2...
by Marcus Denker Dec. 14, 2010

Dec. 14, 2010

Open Bugs: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2 Failing Tests: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/lastCompleted… and a failing build of non-Core: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/8/console Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

4 5

[Pharo-project] updating ConfigurationOfPharo
by laurent laffont Dec. 14, 2010

Dec. 14, 2010

Hi, I want to update ConfigurationOfPharo to include last ProfStef. Should I update #version12beta2 or create #version12beta3 ? Laurent Laffont

3 3

[Pharo-project] Issue 3409 in pharo: KillTextConstants class and package needs to be removed
by pharo＠googlecode.com Dec. 14, 2010

Dec. 14, 2010

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2 New issue 3409 by marcus.denker: KillTextConstants class and package needs to be removed http://code.google.com/p/pharo/issues/detail?id=3409 KillTextConstants class and package needs to be removed

1 1

[Pharo-project] Issue 3408 in pharo: Remove an unsent message from DialogItemsChooserUI (reference to non-existing ivar)
by pharo＠googlecode.com Dec. 14, 2010

Dec. 14, 2010

Status: Fixed Owner: marcus.denker Labels: Milestone-1.2 New issue 3408 by marcus.denker: Remove an unsent message from DialogItemsChooserUI (reference to non-existing ivar) http://code.google.com/p/pharo/issues/detail?id=3408 Remove an unsent message from DialogItemsChooserUI (reference to non-existing ivar) Attachments: SmallCleans.1.cs 632 bytes

1 1

[Pharo-project] Issue 3423 in pharo: Debugger little usability enh
by pharo＠googlecode.com Dec. 14, 2010

Dec. 14, 2010

Status: FixedWaitingToBePharoed Owner: stephane.ducasse Labels: Milestone-1.3 New issue 3423 by stephane.ducasse: Debugger little usability enh http://code.google.com/p/pharo/issues/detail?id=3423 Name: Tools-fbs.283 Author: fbs Time: 1 December 2010, 3:09:44.682 pm UUID: 810789fa-9417-a340-a578-0df71274f43d Ancestors: Tools-ul.282 When a method changes out from under your feet in the Debugger (e.g., you remove an instvar triggering a recompile of a method through which you've stepped), the Debugger blanks out contents. In the UI, this manifests as a blank code pane. This change resets the contents ivar by setting it to the new, recompiled, CompiledMethod as a side effect of calling self selectedMessage. =============== Diff against Tools-ul.282 =============== Item was changed: ----- Method: Debugger>>contents (in category 'accessing') ----- contents "Depending on the current selection, different information is retrieved. Answer a string description of that information. This information is the method in the currently selected context." + contents == nil ifTrue: [^ self selectedMessage]. - contents == nil ifTrue: [^ String new]. ^ contents copy!

1 2

[Pharo-project] Issue 3428 in pharo: Semaphore Enh
by pharo＠googlecode.com Dec. 14, 2010

Dec. 14, 2010

Status: FixedWaitingToBePharoed Owner: stephane.ducasse CC: siguctua Labels: Milestone-1.3 New issue 3428 by stephane.ducasse: Semaphore Enh http://code.google.com/p/pharo/issues/detail?id=3428 Name: Kernel-ul.520 Author: ul Time: 8 December 2010, 3:19:51.682 am UUID: da185163-27f6-6a47-8ecb-e00f9fd8dd3a Ancestors: Kernel-ul.519 A few changes to Semaphore: - save a block creation + activation + a possible context switch in #critical:ifCurtailed: - save a block creation + activation in #critical:ifError:, this changes the behavior when mutuallyExcludedBlock doesn't understand #ifError: - #critical:ifLocked: is guaranteed to not get locked. The earlier implementation sent #critical: which could cause a context switch, so another process could enter the critical section before the current. Also fixed the comments of this method. =============== Diff against Kernel-ul.519 =============== Item was changed: ----- Method: Semaphore>>critical:ifCurtailed: (in category 'mutual exclusion') ----- critical: mutuallyExcludedBlock ifCurtailed: terminationBlock "Evaluate mutuallyExcludedBlock only if the receiver is not currently in the process of running the critical: message. If the receiver is, evaluate mutuallyExcludedBlock after the other critical: message is finished." + ^self critical: [ mutuallyExcludedBlock ifCurtailed: terminationBlock ] - ^self critical:[[mutuallyExcludedBlock value] ifCurtailed: terminationBlock] ! Item was changed: ----- Method: Semaphore>>critical:ifError: (in category 'mutual exclusion') ----- critical: mutuallyExcludedBlock ifError: errorBlock "Evaluate mutuallyExcludedBlock only if the receiver is not currently in the process of running the critical: message. If the receiver is, evaluate mutuallyExcludedBlock after the other critical: message is finished." | blockValue hasError errMsg errRcvr | hasError := false. blockValue := self critical:[ + mutuallyExcludedBlock ifError: [ :msg :rcvr | - [mutuallyExcludedBlock value] ifError:[:msg :rcvr| hasError := true. errMsg := msg. errRcvr := rcvr ]. ]. hasError ifTrue:[ ^errorBlock value: errMsg value: errRcvr]. ^blockValue! Item was changed: ----- Method: Semaphore>>critical:ifLocked: (in category 'mutual exclusion') ----- critical: mutuallyExcludedBlock ifLocked: alternativeBlock "Evaluate mutuallyExcludedBlock only if the receiver is not currently in + the process of running the critical: message. If the receiver is, then evaluate + alternativeBlock and return." + "See the comment of #critical: for the explanation how this pattern works + before changing the code." + + | caught | + caught := false. + ^[ + "We're using #== here instead of #=, because it won't introduce a + suspension point, while #= may do that." + excessSignals == 0 + ifTrue: [ alternativeBlock value ] + ifFalse: [ + excessSignals := excessSignals - 1. + caught := true. + mutuallyExcludedBlock value ] ] + ensure: [ caught ifTrue: [ self signal ] ]! - the process of running the critical: message. If the receiver is, evaluate - mutuallyExcludedBlock after the other critical: message is finished." - - "Note: The following is tricky and depends on the fact that the VM will not switch between processes while executing byte codes (process switches happen only in real sends). The following test is written carefully so that it will result in bytecodes only. - Do not change the following #== for #=, as #== is not a real message send, just a bytecode." - excessSignals == 0 ifTrue: [ - "If we come here, then the semaphore was locked when the test executed. - Evaluate the alternative block and answer its result." - ^alternativeBlock value - ]. - ^self critical: mutuallyExcludedBlock!

1 1

[Pharo-project] Issue 3433 in pharo: Color improvement
by pharo＠googlecode.com Dec. 14, 2010

Dec. 14, 2010

Status: FixedWaitingToBePharoed Owner: stephane.ducasse Labels: Milestone-1.3 Difficulty-Easy New issue 3433 by stephane.ducasse: Color improvement http://code.google.com/p/pharo/issues/detail?id=3433 Levente Uzonyi uploaded a new version of Morphic to project The Trunk: http://source.squeak.org/trunk/Morphic-ul.490.mcz ==================== Summary ==================== Name: Morphic-ul.490 Author: ul Time: 9 December 2010, 3:06:57.133 am UUID: e54bc2a6-58ae-8f42-b64e-f17a63bc00e6 Ancestors: Morphic-laza.489 - simplified Morph >> #colorString: =============== Diff against Morphic-laza.489 =============== Item was changed: ----- Method: Morph>>colorString: (in category 'printing') ----- colorString: aColor + + aColor ifNil: [ ^'nil' ]. + ^aColor name + ifNil: [ aColor storeString ] + ifNotNil: [ :colorName | 'Color ', colorName ]! - aColor ifNil: [^'nil']. - Color colorNames - do: [:colorName | aColor = (Color perform: colorName) ifTrue: [^'Color ' , colorName]]. - ^aColor storeString!

1 0