September 2014 - Pharo-dev - lists.pharo.org

[Issue Tracker] Call for CleanUp of the issue tracker

by Marcus Denker

Hello, There are right now 675 open issues. (we managed to close 63 just the last 7 daysâ¦). A lot of those issues are very old. A lot are in a bad shape: -> not reproducible -> *completely* unclear what action could lead to solve the issue -> outdated (e.g. small improvements submitted ages ago, but even the author does not care to submit a new version for Pharo4) I think we should be more radical in closing issues. If someone submits something but can not even answer a simple question in 2 months â> this is the same as âI donât careâ. So *PLEASE*: -> check all the issue that *you* submitted. Are they still relevant? Is there enough information for anyone to do anything? -> check all the issues you where involved with in discussions. It is much easier for you than for me to understand what the conclusion of the discussion is. -> help checking *old* entries. Is is still relevant? What is the next action? Marcus

Sept. 17, 2014

Re: [Pharo-dev] Monticello superslow/freezing

by phil＠highoctane.be

I think that I've found why it got slow like that. I had the store diff instead of full versions (mistakenly selected I guess) and switching things back did the trick. What's that option? Never noticed it and it for sure hurt or plain doesn't work. Phil On Wed, Sep 17, 2014 at 11:18 AM, Thierry Goubier <thierry.goubier(a)gmail.com > wrote: > Is it caught in a kind of loop trying to find the base version? Scanning > through the ancestors and adding all those to the package cache? > > Thierry > > 2014-09-17 11:07 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > >> Filesize is around 1MB. >> >> Here is what I do get in the debugger when stopping. >> >> TIA >> Phil >> >> >> >> >> On Wed, Sep 17, 2014 at 11:02 AM, Thierry Goubier < >> thierry.goubier(a)gmail.com> wrote: >> >>> Hi Phil, >>> >>> how large is your package? We talked about very large packages with >>> Sebastian Sastre not so long ago. >>> >>> Can you interrupt it to see where it is stuck? >>> >>> Thierry >>> >>> >>> 2014-09-17 10:26 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: >>> >>>> Monticello kinds of freezes my image for a *very* long time. >>>> Long, meaning that it never completes I guess. >>>> >>>> Memory use shoots through the roof. >>>> >>>> What could cause that? >>>> >>>> I have been saving more than 200 versions of my package. >>>> >>>> Thanks for some advice from the trenches. >>>> >>>> Phil >>>> >>> >>> >> >

Sept. 17, 2014

Re: [Pharo-dev] Monticello superslow/freezing

by Thierry Goubier

Is it caught in a kind of loop trying to find the base version? Scanning through the ancestors and adding all those to the package cache? Thierry 2014-09-17 11:07 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > Filesize is around 1MB. > > Here is what I do get in the debugger when stopping. > > TIA > Phil > > > > > On Wed, Sep 17, 2014 at 11:02 AM, Thierry Goubier < > thierry.goubier(a)gmail.com> wrote: > >> Hi Phil, >> >> how large is your package? We talked about very large packages with >> Sebastian Sastre not so long ago. >> >> Can you interrupt it to see where it is stuck? >> >> Thierry >> >> >> 2014-09-17 10:26 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: >> >>> Monticello kinds of freezes my image for a *very* long time. >>> Long, meaning that it never completes I guess. >>> >>> Memory use shoots through the roof. >>> >>> What could cause that? >>> >>> I have been saving more than 200 versions of my package. >>> >>> Thanks for some advice from the trenches. >>> >>> Phil >>> >> >> >

Sept. 17, 2014

Re: [Pharo-dev] Monticello superslow/freezing

by phil＠highoctane.be

Filesize is around 1MB. Here is what I do get in the debugger when stopping. TIA Phil On Wed, Sep 17, 2014 at 11:02 AM, Thierry Goubier <thierry.goubier(a)gmail.com > wrote: > Hi Phil, > > how large is your package? We talked about very large packages with > Sebastian Sastre not so long ago. > > Can you interrupt it to see where it is stuck? > > Thierry > > > 2014-09-17 10:26 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > >> Monticello kinds of freezes my image for a *very* long time. >> Long, meaning that it never completes I guess. >> >> Memory use shoots through the roof. >> >> What could cause that? >> >> I have been saving more than 200 versions of my package. >> >> Thanks for some advice from the trenches. >> >> Phil >> > >

Sept. 17, 2014

Re: [Pharo-dev] Monticello superslow/freezing

by Thierry Goubier

Hi Phil, how large is your package? We talked about very large packages with Sebastian Sastre not so long ago. Can you interrupt it to see where it is stuck? Thierry 2014-09-17 10:26 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > Monticello kinds of freezes my image for a *very* long time. > Long, meaning that it never completes I guess. > > Memory use shoots through the roof. > > What could cause that? > > I have been saving more than 200 versions of my package. > > Thanks for some advice from the trenches. > > Phil >

Sept. 17, 2014

Spec-Morphic tab manager broken

by Yuriy Tymchuk

Hi. If you have any knowledge on how Spec adapters work, maybe you can take a look. To reproduce the bug: execute: "TabsExample open" and select one of (non-active) the tabs. Case here: https://pharo.fogbugz.com/f/cases/14030/MorphicTabManagerAdapter-doesNotUnd… <https://pharo.fogbugz.com/f/cases/14030/MorphicTabManagerAdapter-doesNotUnd…> Uko

Sept. 17, 2014

Re: [Pharo-dev] Pharo Launcher Impressions

by Torsten Bergmann

Sept. 17, 2014

Re: [Pharo-dev] Monticello superslow/freezing

by Sven Van Caekenberghe

On which operation ? I have 400+ versions of some packages, the size of your local package-cache might be an issue (you could try deleting everything older than a year for example, it's a cache after all). Working with a slow repository might also be an issue, some network operations sometimes seem to hang for a while. Doing version compare (merge/changes) operations on large packages (like Glorp) sometimes feels a bit slow, but not unbearably so. On 17 Sep 2014, at 10:26, phil(a)highoctane.be wrote: > Monticello kinds of freezes my image for a *very* long time. > Long, meaning that it never completes I guess. > > Memory use shoots through the roof. > > What could cause that? > > I have been saving more than 200 versions of my package. > > Thanks for some advice from the trenches. > > Phil

Sept. 17, 2014

config change ci server Pharo4: run AsmJIT tests

by Marcus Denker

Hi, We disabled running ASMJit tests before releasing Pharo2â¦ (because of random crashed back then). Of course we forgot to turn it on again. I did that now. This is https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-2.1-Validation-A-L/ Marcus

Sept. 17, 2014

Monticello superslow/freezing

by phil＠highoctane.be

Monticello kinds of freezes my image for a *very* long time. Long, meaning that it never completes I guess. Memory use shoots through the roof. What could cause that? I have been saving more than 200 versions of my package. Thanks for some advice from the trenches. Phil

Sept. 17, 2014