July 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [pharo-project/pharo-core] ac9f62: 60149

by Marcus Denker

> On 13 Jul 2016, at 10:03, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> http://files.pharo.org/image/60/60149.zip >> >> > Strangely it did not build. Wasted already >1 hour on thisâ¦ > Now it is there. Marcus

July 13, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] ac9f62: 60149

by Marcus Denker

> > http://files.pharo.org/image/60/60149.zip > > Strangely it did not build. Wasted already >1 hour on thisâ¦ Marcus

July 13, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60149 Home: https://github.com/pharo-project/pharo-core

July 13, 2016

[pharo-project/pharo-core] ac9f62: 60149

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: ac9f62ce8dea687da1b6f7675d47f43bee08dc65 https://github.com/pharo-project/pharo-core/commit/ac9f62ce8dea687da1b6f767… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-07-13 (Wed, 13 Jul 2016) Changed paths: A OpalCompiler-Core.package/AbstractCompiler.class/instance/accessing/encoderClass_.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/other-tests/testDifferentBlocksWithSameArgumentName.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/other-tests/testModulePrimitive.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/test - array compilation/testMultiElementArray.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/test - array compilation/testSimpleArray.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/test - block returning/testBlockReturning.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testBlockTemp.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testMethodArgument.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testMethodTemp.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testOneFloat.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testReturnBlockInMethod.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testSetUp.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testSteamContentsLimitedToSequenceableCollectionClass.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testToDoArgumentNotInlined.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testToDoInsideTempNotInlined.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testToDoOutsideTempNotInlined.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testWhileModificationAfterNotInlined.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testWhileModificationBeforeNotInlined.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testWhileWithTempNotInlined.st M Pharo-Help.package/PharoWelcomePage.class/class/accessing/title.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60148.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60149.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60148.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60149.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Examples.package/DynamicWidgetChange.class/instance/private/changeToButton.st M Spec-Examples.package/DynamicWidgetChange.class/instance/private/changeToList.st M System-Support.package/SystemVersion.class/instance/printing/shortVersionString.st Log Message: ----------- 60149 18390 System version should be "Pharo 6.0" instead of "Pharo6.0" and PharoWelcomePage should not hard code version https://pharo.fogbugz.com/f/cases/18390 18748 OpalCompiler Tests: OCNewCompilerWithChangesFunctionalTests should set encoder to OpalEncoderForV3PlusClosures https://pharo.fogbugz.com/f/cases/18748 15688 Remove ComposableModel>>#instantiateModels:s senders in Spec-Examples https://pharo.fogbugz.com/f/cases/15688 http://files.pharo.org/image/60/60149.zip

July 13, 2016

Re: [Pharo-dev] bloc status update: june 2016

by stepharo

For now it means that we can write "World new open" and we can use this to write tests. We have Bloc2 SDL worlds side by side and the goal is to have everything ready (tools and widgets) and to get rid of the morphic one. In Bloc1 we did not have other physical window so we had too many constraints and morphic infection points. But we could run Morphic inside Bloc. In Bloc2 this is not possible but we get a better event bubbling model and other possibilities. Stef Le 13/7/16 Ã 03:27, Brad Selfridge a Ã©crit : > Does this mean "worlds within worlds" or "worlds adjacent to other worlds". > If adjacent, will they be able to communicate with each other? > > > > > ----- > Brad Selfridge > -- > View this message in context: http://forum.world.st/bloc-status-update-june-2016-tp4901988p4906373.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

July 13, 2016

Re: [Pharo-dev] bloc status update: june 2016

by stepharo

Hi glenn with bloc2 (yes new implementation) it will be possible, Glenn can open separate worlds and we discussed a lot your point (and we share it). Stef Le 12/7/16 Ã 16:57, Sean P. DeNigris a Ã©crit : > Sean P. DeNigris wrote >> A test case for this, which opens up many exciting possibilities (imagine >> I want to control time in my space e.g. run a simulation at 10x speed...), >> would be to have a world within a world. I dabbled with this idea a bit in >> Morphic, but quickly became frustrated because Morphic makes too many >> assumptions e.g. relying on globals and hardcoded classes. >> >> The last time I tried this in Bloc, the result of the discussion was that >> Alain said that this should be conceptually possible, but that I should be >> patient (http://forum.world.st/Bloc-Space-within-a-Space-td4877474.html) >> Are we any closer to this dream? > Bump!! > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/bloc-status-update-june-2016-tp4901988p4906283.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

July 13, 2016

Re: [Pharo-dev] bloc status update: june 2016

by Brad Selfridge

Does this mean "worlds within worlds" or "worlds adjacent to other worlds". If adjacent, will they be able to communicate with each other? ----- Brad Selfridge -- View this message in context: http://forum.world.st/bloc-status-update-june-2016-tp4901988p4906373.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 13, 2016

Re: [Pharo-dev] Pharo 5.0 Tiny Feature Request

by Sean P. DeNigris

stepharo wrote > open a bug entry. Done: 18757 Simple Shell Command Eval for 5.0 https://pharo.fogbugz.com/f/cases/18757/Simple-Shell-Command-Eval-for-5-0 But I'm not sure how to commit it. It changes UFFI which has a configuration. What do I commit (package, slice, config(s))? And to where (UFFI repo, inbox)? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-5-0-Tiny-Feature-Request-tp4901682p4906352.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 12, 2016

Re: [Pharo-dev] Problem with delay waiting (OSSubprocess code) on Pharo 5.0

by Mariano Martinez Peck

On Wed, May 18, 2016 at 11:39 PM, Ben Coman <btc(a)openinworld.com> wrote: > On Thu, May 19, 2016 at 8:49 AM, Martin McClure <martin(a)hand2mouse.com> > wrote: > > On 05/18/2016 03:17 PM, Martin McClure wrote: > >> > >> On 05/18/2016 08:49 AM, Mariano Martinez Peck wrote: > >>> > >>> Hi guys, > >>> > >>> I am seeing a problem in Pharo 5.0 regarding Delay >> wait. I cannot > >>> explain how this could happened but it does, and it happened to me a > couple > >>> of times (but not fully reproducible). > >>> > >> > >> Hmm. The schedulerResumptionTime is, somehow, being (approximately) > >> doubled. It's not clear how that can happen, but I'll look a little > more. > >> > > > > Mario, is there any chance that you might be saving the image during one > of > > these Delays? > > > > > > This one smells like a race condition, and I think I see something that > > *might* explain it. But I don't have any more time to spend on this one, > so > > I'll leave the rest to someone else. I hope this is helpful: > > > > The only way I immediately see for the schedulerResumptionTime to become > > approximately doubled is if the Delay's resumption time is adjusted by > > #restoreResumptionTimes without previously having been adjusted by > > #saveResumptionTimes. > > > > The only time either of those are sent, that I can see, is on saving the > > image. Both are normally sent, (save before the snapshot, restore > > afterwards), but there may be a hole there. > > > > #saveResumptionTimes is only sent (by this scheduler class) when the > > accessProtect semaphore is held, but #handleTimerEvent: is executed in > the > > timing Process *without* the protection of accessProtect, in the case of > the > > VM signaling the timingSemaphore. If the VM signals the timingSemaphore, > > #handleTimerEvent: could run in the middle of #saveResumptionTimes. If > some > > Delay expires because of that timer event, our Delay could move from > being > > the first suspended delay to being the active delay. If that happens > after > > we've adjusted the active delay, but before we've processed the suspended > > delays, that Delay will not get adjusted, and will show the symptoms that > > Mariano is seeing. > > A quick experiment to test this might be in shutDown/#startUp trying... > [ self saveResumptionTimes ] valueAt: Processor timingPriority > [ self resumeResumptionTimes ] valueAt: Processor timingPriority > > > > > Also, I'm not sure how the Heap that holds the suspendedDelays will > react to > > being modified in the middle of an enumeration. That might open a larger > > window for the problem. > > > > Regards, > > > > -Martin > > > > Even if not directly related to Mariano's problem, I agree with your > general assessment. I'm not comfortable with the way that > #save/#restoreResumptionTimes (which manipulate suspendedDelays) are > called from user priority code via #shutDown/#startUp. Per the > original code**, accessProtect can't be used inside the timing > priority #handleTimerEvent since accessProtect is held by the user > priority #schedule when it uses "timingSemaphore signal" to invoke > invokes #handleTimerEvent. accessProtect never protected > timingPriority manipulation of suspendedDelays by #handleTimerEvent, > nor expired delays waking up. But ahhh... the disabling of > accessProtect previously prevented new delays being scheduled between > a #save and #restore. If a new delay is scheduled after the #save, > when it is #restore'd its resumptionTime would be wrong. > > Waiting in the wings for Pharo 6 I have changes that should help: > * have #save/#restoreResumptionTimes *only* called from timing > priority event loop (i.e. #handleTimerEvent) > * shutDown/startUp suspends/resumes the timing priority event loop, > instead of trying to block signals to timingSemaphore > > I haven't touched it for a few months so I'll need to chase it up to > provide a preview. > > Mariano, can you try DelayMillisecondScheduler (which however is > missing some fixes for other issues). > > Ben, Did you find a chance to do something else with this? I am still finding lookups every in a while even with the DelayMillisecondScheduler :( Thanks! -- Mariano http://marianopeck.wordpress.com

July 12, 2016

Re: [Pharo-dev] bloc status update: june 2016

by Tudor Girba

Hi, That is one of the variables we have on the radar. Whether we can make it in the first iteration, remains to be seen. Cheers, Doru > On Jul 12, 2016, at 4:57 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Sean P. DeNigris wrote >> A test case for this, which opens up many exciting possibilities (imagine >> I want to control time in my space e.g. run a simulation at 10x speed...), >> would be to have a world within a world. I dabbled with this idea a bit in >> Morphic, but quickly became frustrated because Morphic makes too many >> assumptions e.g. relying on globals and hardcoded classes. >> >> The last time I tried this in Bloc, the result of the discussion was that >> Alain said that this should be conceptually possible, but that I should be >> patient (http://forum.world.st/Bloc-Space-within-a-Space-td4877474.html) >> Are we any closer to this dream? > > Bump!! > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/bloc-status-update-june-2016-tp4901988p4906283.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > -- www.tudorgirba.com www.feenk.com "Sometimes the best solution is not the best solution."

July 12, 2016