- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #1104: 5097-Creating-a-method-from-debugger-goes-into-infinite-loop-when-typing-something-in-the-class-list
by ci-pharo-ci-jenkins2＠inria.fr Jan. 13, 2020

Jan. 13, 2020

There is a new Pharo build available! The status of the build #1104 was: FAILURE. The Pull Request #5463 was integrated: "5097-Creating-a-method-from-debugger-goes-into-infinite-loop-when-typing-something-in-the-class-list" Pull request url: https://github.com/pharo-project/pharo/pull/5463 Issue Url: https://github.com/pharo-project/pharo/issues/5097 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Mm10s] 2010-01-13
by Esteban Lorenzano Jan. 13, 2020

Jan. 13, 2020

### Last week: - [release] Start Pharo9.0 branch - [release] Fix some issues for Pharo8.0 - [release] Spent a lot of time trying to verify a problem on zerocont (and smalltalkCI) that turned out to be corrected already (but nobody knew it) ;) - [voyage] Fix a cyclic problem on voyage-unqlite. - [Spec2] Fix âcenterâ and âcenterRelativeTo:â properties for Dialogs. ### This week (starting 2019-12-16): - [Release] Organise issues that will enter in P8. - [Release] Prepare release notes - [VM] Check a problem with large installations on AIO/Threaded VM. ### Pipeline - [Release] Pharo 8 Release. - [VM] debug AIO and worker thread VMs on linux and windows.

2 1

about signal
by ducasse Jan. 12, 2020

Jan. 12, 2020

Hi I wanted to explain | semaphore p1 p2 | semaphore := Semaphore new. p1 := [ semaphore wait. 'p1' crTrace ] fork. p2 := [semaphore signal. 'p2' crTrace ] fork. displays p2 and p1. but I would like explain clearly but it depends on the semantics of signal. - ==p1== is scheduled and its execution starts to wait on the semaphore, so it is removed from the run queue of the scheduler and added to the waiting list of the semaphore. - ==p2== is scheduled and it signals the semaphore. The semaphore takes the first waiting process (==p1==) and reschedule it by adding it to the end of the suspended lists. Now this sentence "The semaphore takes the first waiting process (==p1==) and reschedule it by adding it to the end of the suspended lists.â is super naive. Is the semaphore signalling scheduled? or not? signal "Primitive. Send a signal through the receiver. If one or more processes have been suspended trying to receive a signal, allow the first one to proceed. If no process is waiting, remember the excess signal. Essential. See Object documentation whatIsAPrimitive." <primitive: 85> self primitiveFailed "self isEmpty ifTrue: [excessSignals := excessSignals+1] ifFalse: [Processor resume: self removeFirstLink]" I wanted to know what is really happening when a semaphore is signalled. Now resume: does not exist on Processor. I will look in the VM code. S S.

9 36

Interesting bug or feature in exception processing logic
by Denis Kudriashov Jan. 12, 2020

Jan. 12, 2020

Hi. I played a bit with exceptions trying to detect that given block will open the debugger. My idea was to simply catch UnhandledError which normally means that no outer code handles given error and therefore debugger is appeared. For my surprise the following example works from playground but not from the browser editor: [MyTestError signal ] on: UnhandledError do: [ :e | self halt ] In playground you will see the halt. But from the browser the debugger will show MyTestError. After breaking my head I found that there is a difference how scripts are executed in those tools. In Playground it is a deferred action. But in the browser it is evaluated as a deep event processing code (keymap processing) and there is an outer error handler (on: Error do: ) which does some work and passes the exception further (err pass). Following script demonstrates the difference in the error processing logic when there is an outer handler: [ [MyTestError signal ] on: UnhandledError do: [ :e | self halt ] ] on: MyTestError do: [ :z | z pass] Try it from playground. Second line separately will show the halt while all together it will stop at MyTestError signal. Debugging shows that when the outer handler is processed it sets the handler context into the exception and it skips the existing handler for UnhandledError. The question: is it a feature or a bug? Think also how following code should work (unrelated to UnhandledError logic): [ [ 1/0 ] on: MyTestError do: [ :e | self halt ] ] on: ZeroDivide do: [ :z | MyTestError signal ] Currently it will show MyTestError signal. Best regards, Denis

2 14

[Pharo 8.0] Build #1103: 5466-Better-Semaphore-class-comment
by ci-pharo-ci-jenkins2＠inria.fr Jan. 12, 2020

Jan. 12, 2020

There is a new Pharo build available! The status of the build #1103 was: SUCCESS. The Pull Request #5467 was integrated: "5466-Better-Semaphore-class-comment" Pull request url: https://github.com/pharo-project/pharo/pull/5467 Issue Url: https://github.com/pharo-project/pharo/issues/5466 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #5: Fixing FFI Error in Cairo
by ci-pharo-ci-jenkins2＠inria.fr Jan. 11, 2020

Jan. 11, 2020

There is a new Pharo build available! The status of the build #5 was: FAILURE. The Pull Request #5454 was integrated: "Fixing FFI Error in Cairo" Pull request url: https://github.com/pharo-project/pharo/pull/5454 Issue Url: https://github.com/pharo-project/pharo/issues/fixing Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

TechTalks: Dates + Call
by Marcus Denker Jan. 10, 2020

Jan. 10, 2020

Hi, Here are dates for the Pharo TechTalks first half of 2020: January 23: https://association.pharo.org/event-3697009 Thursday 20 https://association.pharo.org/event-3697011 March 19 https://association.pharo.org/event-3697012 April 23 https://association.pharo.org/event-3697013 May 28 https://association.pharo.org/event-3697016 June 18 https://association.pharo.org/event-3697017 We need topics! If you want to take over one of these talks to show your project (or something that you find interesting) â> send me a mail. The date/time can be changed as needed, too. Archive of past techtalks: https://pharo.org/TechTalk

1 0

[Pharo 9.0] Build #4: Improving metalink printing and visualization in Calypso
by ci-pharo-ci-jenkins2＠inria.fr Jan. 10, 2020

Jan. 10, 2020

There is a new Pharo build available! The status of the build #4 was: SUCCESS. The Pull Request #5456 was integrated: "Improving metalink printing and visualization in Calypso" Pull request url: https://github.com/pharo-project/pharo/pull/5456 Issue Url: https://github.com/pharo-project/pharo/issues/Metalink Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Little challenge
by ducasse Jan. 10, 2020

Jan. 10, 2020

Hi I would like know how many instances of Color are instantiated by a theme. I would like to know how many times the same color is created. Iâm creating a theme using a dictionary instead of stupidly returning color. May be like that I can use an LRUCache to see the number of hits. I will see if I can instrument Color new. We really need tools that help us measuring things. Any other ideas? S.

6 10

[Pharo 8.0] Build #1102: 2854-Pharo-7-Saving-the-settings-breaks-local-directory
by ci-pharo-ci-jenkins2＠inria.fr Jan. 10, 2020

Jan. 10, 2020

There is a new Pharo build available! The status of the build #1102 was: SUCCESS. The Pull Request #5431 was integrated: "2854-Pharo-7-Saving-the-settings-breaks-local-directory" Pull request url: https://github.com/pharo-project/pharo/pull/5431 Issue Url: https://github.com/pharo-project/pharo/issues/2854 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0