June 2018 - Pharo-dev - lists.pharo.org

unnamed processes

by Ben Coman

An uncommon situation but it exposes something that would be nice to correct anyhow... If interCyclePause is commented out like... WorldState >>doOneCycleFor: aWorld "self interCyclePause: MinCycleLapse." self doOneCycleNowFor: aWorld. in Process Browser there is a build-up of unnamed priority 31 processes. I haven't been able to track down where these arise from to work out what their name should be. Anyone who contributed code which creates forks a new process, could you check if this is the source and provide a name? cheers -ben P.S. I wonder if the default name of forked processes should be something like "thisContext sender receiver"

June 14, 2018

Re: [Pharo-dev] Sista & Pharo 7

by Tim Mackinnon

Sad - but a wise decision, there was a already a lot going on. Tim Sent from my iPhone Sent from my iPhone > On 14 Jun 2018, at 07:42, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > yes, Sista will not be in P7 sadly. > we postponed almost all VM relative stuff because of complications to get it ready

June 14, 2018

Re: [Pharo-dev] Sista & Pharo 7

by Esteban Lorenzano

yes, Sista will not be in P7 sadly. we postponed almost all VM relative stuff because of complications to get it ready (64bit windows is still there). cheers, Esteban > On 14 Jun 2018, at 07:53, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > Latest release is on Pharo 6 (https://clementbera.wordpress.com/2017/07/19/sista-open-alpha-release/ <https://clementbera.wordpress.com/2017/07/19/sista-open-alpha-release/>) > That's the release where the published benchmarks happened and where multiple developers got involved. > > No plan to release on Pharo 7 alpha. Ask again once Pharo 7 is released. > > Repository is in migration though, I migrated to github earlier this year, but with recent changes & new organization, I think the repository will be merged with open-smalltalk-vm repository. Documentation will be merged too, so it's going to be easier to build images and matching VMs or move code from VM-side to image-side or the other way around. > > I think questions related to Sista should be on vm-dev since there are only alpha releases (i.e. no interest for non VM developers). > > On Thu, Jun 14, 2018 at 5:28 AM, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: > Is Sista operational in the latest Pharo 7 builds? > > What is the plan for Sista in relation to Pharo 7? > > cheers -ben > > > > -- > ClÃ©ment BÃ©ra > https://clementbera.github.io/ <https://clementbera.github.io/> > https://clementbera.wordpress.com/ <https://clementbera.wordpress.com/>

June 14, 2018

[Pharo 7.0-dev] Build #1055: 22135-Remove-use-of-Transcript-from-AST-Core

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1055 was: SUCCESS. The Pull Request #1538 was integrated: "22135-Remove-use-of-Transcript-from-AST-Core" Pull request url: https://github.com/pharo-project/pharo/pull/1538 Issue Url: https://pharo.fogbugz.com/f/cases/22135 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 14, 2018

[Pharo 7.0-dev] Build #1054: 22138 Comment RBBrowserEnvironmentTest

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1054 was: FAILURE. The Pull Request #1540 was integrated: "22138 Comment RBBrowserEnvironmentTest" Pull request url: https://github.com/pharo-project/pharo/pull/1540 Issue Url: https://pharo.fogbugz.com/f/cases/22138 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 14, 2018

Re: [Pharo-dev] Sista & Pharo 7

by ClÃ©ment Bera

Latest release is on Pharo 6 ( https://clementbera.wordpress.com/2017/07/19/sista-open-alpha-release/) That's the release where the published benchmarks happened and where multiple developers got involved. No plan to release on Pharo 7 alpha. Ask again once Pharo 7 is released. Repository is in migration though, I migrated to github earlier this year, but with recent changes & new organization, I think the repository will be merged with open-smalltalk-vm repository. Documentation will be merged too, so it's going to be easier to build images and matching VMs or move code from VM-side to image-side or the other way around. I think questions related to Sista should be on vm-dev since there are only alpha releases (i.e. no interest for non VM developers). On Thu, Jun 14, 2018 at 5:28 AM, Ben Coman <btc(a)openinworld.com> wrote: > Is Sista operational in the latest Pharo 7 builds? > > What is the plan for Sista in relation to Pharo 7? > > cheers -ben > -- ClÃ©ment BÃ©ra https://clementbera.github.io/ https://clementbera.wordpress.com/

June 14, 2018

reinstating original UI thread after debugging

by Ben Coman

I notice... DebugSession >> resumeProcess "Make sure the interrupted process is restored properly and restart the low space handler" interruptedProcess isTerminated ifFalse: [ errorWasInUIProcess ifTrue: [ UIManager default resumeUIProcess: interruptedProcess ] ifFalse: [ interruptedProcess resume ]]. "restart low space handler" Smalltalk installLowSpaceWatcher. and... MorphicUIManager >> resumeUIProcess: aProcess "Adopt aProcess as the project process -- probably because of proceeding from a debugger" UIProcess := aProcess. UIProcess resume This doesn't seem to do anything regarding the second UI process spawned in... MorphicUIManager >> debugProcess:context:label:fullView:notification: With Process Browser running with auto-update on, running the following experiment confirms that the second spawned UI is killed. TestCase subclass: #Example2 Example2 >> test1 Processor activeProcess name: 'ORIGINAL UI'. self halt So I'm curious, where is the code killing the second UI ? Also curious, when the first UI turns into a debuggger, why later reinstate the first UI and kill the second UI? If the second UI started clean and is running happily, why not leave it running and let first UI thread terminate normally? I get some strange behaviour** sometimes , and wonder if the swap back it might be related to this. ** Like today #testUserPriority below not opening a debugger at the first halt statement, or opening a pre-debug window that has a blank pane. testUserPriority debug := true. Processor activeProcess priority: 38. self halt. highPriorityProcess := self highPriorityRunLoop. Transcript cr. debug ifTrue: [self halt]. 3 timesRepeat: [ Transcript crShow: 'U'. self wakeHighPriorityLoop.]. highPriorityProcess terminate. cheers -ben

June 14, 2018

Sista & Pharo 7

by Ben Coman

Is Sista operational in the latest Pharo 7 builds? What is the plan for Sista in relation to Pharo 7? cheers -ben

June 14, 2018

Re: [Pharo-dev] ApplicationSecurity Questions

by Sean DeNigris

> Now I've fixed the BaselineOfApplicationSecurity Yes, successfully installed. > I don't have time to try it or support it in Pharo 5 now :( No problem. I only tried because I failed in Pharo 6 :) > Add an adaptor using the Control Panel then go to: Ah, yes! Up and running :) > Please let me know how it is going, Wil do

June 13, 2018

Re: [Pharo-dev] Recent Pharo does not work (to me) with "El Capitan"

by Esteban Lorenzano

> On 13 Jun 2018, at 22:57, Jordi Delgado <jdelgado(a)cs.upc.edu> wrote: > > Yes, I did. Same result. > > All the same happens with the latest version of Squeak. > > I tried with High Sierra. In HS Pharo 6.1 starts, the image opens but > then it complains about not being able to create some file in > /Private/var/... and the image becomes unusable. In High Sierra the > latest version of Squeak opens correctly. this is because you are trying to execute a non-signed VM then it puts you in a sandbox. easy fix: copy your VM into Applications and execute from there. > > Tomorrow I will try with Sierra, on a clean computer (a computer that > never had a Smalltalk installed in it). > > I insist. You do not find any of these problems with Ubuntu. Quoting > Robert de Niro, f*ck Apple ;) well, but is very weird. most of use work on mac and we do not have this problems (yes the one about the signed VM, but just that one). Esteban > > El 13/6/18 a les 21:55, Tim Mackinnon ha escrit: >> Have you tried the 32bit version - just to rule that out? You did the 64bit version - not sure how El Capitan faired with that? >> >> > > -- > Salut! > > Jordi Delgado > > Computer Science Department - Universitat PolitÃ¨cnica de Catalunya > Campus Nord, Omega building, > Office S115 c/Jordi Girona Salgado, 1-3 > 08034 Barcelona, Spain. > Phone: +34.93.413.40.18 > Public Key: https://pgp.mit.edu/pks/lookup?op=get&search=0xB7911543AD9E79A8 >

June 13, 2018