- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] github-cache organisation

by Dimitris Chloupis

The zip is not needed and it should be deleted after extraction cause it serves no role. This create a problem also because if you try to install agin the repo it won't redownload the zip , instead it will use the same zip. For me this make little sense because in the vast majority of cases your intention would be to download the repo version containing the latest commit. There is a command to do this though. Personally I don't like this behavior. On Fri, 22 Jul 2016 at 06:41, Ben Coman <btc(a)openinworld.com> wrote: > Just a general observation and first impression of installing a github > hosted project. > > After installing OSSubprocess from the Catalog Browser on Pharo 50760, > which uses repository... > github://marianopeck/OSSubProcess:v0.2.4/repository > > ...I see file > "github--marianopeckOSSubprocessv0241266307023333901887488330764830.zip" > sitting next to my .image file. That would seem to dirty up that area > when I start to use git more often. I'd expect that file to be placed in > one of the cache folders. > > cheers -ben >

July 22, 2016

Re: [Pharo-dev] git feature request

by Dimitris Chloupis

Actually you can , there was even a tool for Pharo that uses the github api to do most common git actions, github api does not need git installed because it does everything online. Alternatively you can use GitHub web GUI , you will have to be added to the repo as contributor though to have the required permissions to do commits, push and pulls , it should work also for pull requests . In the case of a pull request you won't need to be a contributor to the repo but you will have to fork it. Of course you can do that via github api, it's actually very powerful. You need git installed only to version control locally on your hard drive. But if you are fine with working online , the github api should be enough. You can learn more about it in the github website at the help section. On Fri, 22 Jul 2016 at 06:57, Ben Coman <btc(a)openinworld.com> wrote: > I'm not sure what the roadmap is for git integration, but just a use case > that occurs to me while I work "a bit with git" for the first time from > Pharo. > > I install a project via a Baseline from git and makes a small improvement. > What is the easiest way to contribute back? I can't push back to the > personal repo I downloaded from, so the easiest thing would be a single > menu item to: > 1. Fork original repository > 2. Push current in-Image code to a new branch in that fork. > > Maybe even... > 3. Issue a pull request to the original repository. > > cheers -ben >

July 22, 2016

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

by Ben Coman

On Fri, Jul 22, 2016 at 4:42 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Sun, Jul 17, 2016 at 6:46 AM, Ben Coman <btc(a)openinworld.com> wrote: > > >> Do you have some test code or a test image I could run to reproduce >> the problem? >> > > > The problem is that I cannot reproduce it immediately. It takes me some > days and likely some image save and start again until I reproduce it. > Could you try How about something that invokes > > >> >> Now I have one thing for you to try. In the move of DelaySchedulerXxx >> from milliseconds to microseconds, the code for dealing with clock >> wrap-around was removed, but I wonder if it was also covering clock >> jitter as a side effect. Could you try again the SpinScheduler but >> restore this code... >> >> From handletTimerEvent... >> "Check for clock wrap-around." >> millisecondNowTick < activeDelayStartTime ifTrue: [ >> "clock wrapped" >> self saveResumptionTimes. >> self restoreResumptionTimes ]. >> activeDelayStartTime := millisecondNowTick. >> >> From runTimerEventLoop... >> Time millisecondClockValue < millisecondNowTick >> ifTrue:[ timingSemaphore signal ]. "retry" >> >> From startup... >> activeDelayStartTime := Time millisecondClockValue. >> >> > OK, I put back the code into the spin scheduler. Then I kept using > milisecond one until I finished the changes. Then I saved image and switch > to spin one: the image hungs. I cannot even interrupt it. I attach my > modifications. > Do they look correct? > I confirm that locked my image also. One change of milli to micro was missed at the bottom of runTimeEventLoop... That is... Time millisecondClockValue < microsecondNowTick to... Time microsecondClockValue < microsecondNowTick (just a case of domestic blindness) [1] :) :) cheers -ben [1] http://www.urbandictionary.com/define.php?term=domestic%20blindness P.S. A trick to debug delays is to bypass interCycleDelay by at the top of it putting... true ifTrue: [^self].

July 22, 2016

git feature request

by Ben Coman

I'm not sure what the roadmap is for git integration, but just a use case that occurs to me while I work "a bit with git" for the first time from Pharo. I install a project via a Baseline from git and makes a small improvement. What is the easiest way to contribute back? I can't push back to the personal repo I downloaded from, so the easiest thing would be a single menu item to: 1. Fork original repository 2. Push current in-Image code to a new branch in that fork. Maybe even... 3. Issue a pull request to the original repository. cheers -ben

July 22, 2016

github-cache organisation

by Ben Coman

Just a general observation and first impression of installing a github hosted project. After installing OSSubprocess from the Catalog Browser on Pharo 50760, which uses repository... github://marianopeck/OSSubProcess:v0.2.4/repository ...I see file "github--marianopeckOSSubprocessv0241266307023333901887488330764830.zip" sitting next to my .image file. That would seem to dirty up that area when I start to use git more often. I'd expect that file to be placed in one of the cache folders. cheers -ben

July 22, 2016

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

by Mariano Martinez Peck

On Sun, Jul 17, 2016 at 6:46 AM, Ben Coman <btc(a)openinworld.com> wrote: > On Wed, Jul 13, 2016 at 12:30 AM, Mariano Martinez Peck > <marianopeck(a)gmail.com> wrote: > > > > > > 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 :( > > Hi Mariano, > > Sorry for the delay attending to this. I got a bit twisted up on > whether I'm complicating things too much with my DelayScheduler > refactoring for Pharo 6 (I should just put it out for early review), > but then I had to get through a Netflix addiction to the Star Trek > prequel Enterprise, and family time over my kids school holidays. I'm > back looking at it now - and taking a step back to see what is the > minimum change required to fix this. > > hahaha no problem. > Do you have some test code or a test image I could run to reproduce > the problem? > The problem is that I cannot reproduce it immediately. It takes me some days and likely some image save and start again until I reproduce it. > > Now I have one thing for you to try. In the move of DelaySchedulerXxx > from milliseconds to microseconds, the code for dealing with clock > wrap-around was removed, but I wonder if it was also covering clock > jitter as a side effect. Could you try again the SpinScheduler but > restore this code... > > From handletTimerEvent... > "Check for clock wrap-around." > millisecondNowTick < activeDelayStartTime ifTrue: [ > "clock wrapped" > self saveResumptionTimes. > self restoreResumptionTimes ]. > activeDelayStartTime := millisecondNowTick. > > From runTimerEventLoop... > Time millisecondClockValue < millisecondNowTick > ifTrue:[ timingSemaphore signal ]. "retry" > > From startup... > activeDelayStartTime := Time millisecondClockValue. > > OK, I put back the code into the spin scheduler. Then I kept using milisecond one until I finished the changes. Then I saved image and switch to spin one: the image hungs. I cannot even interrupt it. I attach my modifications. Do they look correct? Thanks! -- Mariano http://marianopeck.wordpress.com

July 21, 2016

Re: [Pharo-dev] [Ann] Major Seamless update

by Nick Papoylias

On Thu, Jul 21, 2016 at 2:24 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > I glad to finally release new version of Seamless (0.8.2). > It could be loaded by: > > Gofer it > smalltalkhubUser: 'Pharo' project: 'Seamless'; > configuration; > loadStable. > > It works in Pharo 5 and 6. > Great work Denis ! Keep pushing ;) > > It is complete redesign of original version with the goal to make it more > flexible, reliable and simple. > (original version was created by Nikolaos Papoulias) > > Seamless is foundation for RemoteDebuggingTools. It allows reuse existing > debugger to work with remote process by transparent network communication. > Particularly new version provides required flexibility to reduce number of > requests between distributed objects. No debugger changes was needed to > make it work relatively fast with remote model. > > For more details look at my blog > <http://dionisiydk.blogspot.fr/2016/07/major-seamless-update.html> and > read docs: Seamless > <https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre…> and > Basys > <https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre…> > > > As usual feedback is welcome. > > Best regards, > Denis >

July 21, 2016

Re: [Pharo-dev] [Ann] Major Seamless update

by Denis Kudriashov

Hi Ben. 2016-07-21 16:42 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > It will be a while before I play with it, but the manual was an > interesting read. Some minor nit-picks... > > * Perhaps use a dash for compound-words like receiver-peer and > sender-peer. This phrase was a bit hard to decipher... > > "When request is executed on receiver peer sender peer should > receive..." > versus... > "When request is executed on receiver-peer, the sender-peer should > receive..." > > * Check spelling ==> knowk? ;) > Done. (pillar, not built yet) Writing papers/docs is hard to me. Any help/reviews are super welcome. So thank's you very much Ben

July 21, 2016

Re: [Pharo-dev] [Ann] Major Seamless update

by Ben Coman

On Thu, Jul 21, 2016 at 8:24 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > I glad to finally release new version of Seamless (0.8.2). > It could be loaded by: > > Gofer it > smalltalkhubUser: 'Pharo' project: 'Seamless'; > configuration; > loadStable. > > It works in Pharo 5 and 6. > > It is complete redesign of original version with the goal to make it more > flexible, reliable and simple. > (original version was created by Nikolaos Papoulias) > > Seamless is foundation for RemoteDebuggingTools. It allows reuse existing > debugger to work with remote process by transparent network communication. > Particularly new version provides required flexibility to reduce number of > requests between distributed objects. No debugger changes was needed to > make it work relatively fast with remote model. > > For more details look at my blog > <http://dionisiydk.blogspot.fr/2016/07/major-seamless-update.html> and > read docs: Seamless > <https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre…> and > Basys > <https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre…> > > > As usual feedback is welcome. > > Best regards, > Denis > It will be a while before I play with it, but the manual was an interesting read. Some minor nit-picks... * Perhaps use a dash for compound-words like receiver-peer and sender-peer. This phrase was a bit hard to decipher... "When request is executed on receiver peer sender peer should receive..." versus... "When request is executed on receiver-peer, the sender-peer should receive..." * Check spelling ==> knowk? ;) cheers -ben

July 21, 2016

[Ann] Major Seamless update

by Denis Kudriashov

I glad to finally release new version of Seamless (0.8.2). It could be loaded by: Gofer it smalltalkhubUser: 'Pharo' project: 'Seamless'; configuration; loadStable. It works in Pharo 5 and 6. It is complete redesign of original version with the goal to make it more flexible, reliable and simple. (original version was created by Nikolaos Papoulias) Seamless is foundation for RemoteDebuggingTools. It allows reuse existing debugger to work with remote process by transparent network communication. Particularly new version provides required flexibility to reduce number of requests between distributed objects. No debugger changes was needed to make it work relatively fast with remote model. For more details look at my blog <http://dionisiydk.blogspot.fr/2016/07/major-seamless-update.html> and read docs: Seamless <https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre…> and Basys <https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre…> As usual feedback is welcome. Best regards, Denis

July 21, 2016