October 2013 - Pharo-dev - lists.pharo.org

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=ma… 1 regressions found. Tests.Traits.TraitPureBehaviorTest.testChangeSuperclass

Oct. 8, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=li… 1 regressions found. Tests.Traits.TraitPureBehaviorTest.testChangeSuperclass

Oct. 8, 2013

Re: [Pharo-dev] external semaphoresâ¦again

by Igor Stasenko

On 7 October 2013 18:01, Henrik Johansen <henrik.s.johansen(a)veloxit.no>wrote: > > On Oct 7, 2013, at 5:40 , Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > > On 7 October 2013 17:25, Henrik Johansen <henrik.s.johansen(a)veloxit.no>wrote: > >> >> On Oct 7, 2013, at 4:36 , Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> > 1 thing. >> > >> > can you tell me what given expression yields for your VM/image: >> > >> > Smalltalk vm maxExternalSemaphores >> > >> > (if it gives you number less than 10000000 then i think i know what is >> your problem :) >> > >> >> Uhm, I didn't read your implementation, but the proper thing to do for a >> VM which doesn't care about the external objects table (splObjs at: 39) >> growing, is returning nil from maxExternalSemaphores, like it will for >> pre-Cog VM's. >> > > or.. release VM + image, where image aware of current VM capabilities, and > refuses to run on older ones, and get rid of all this stuff altogether. > > i changed the low-level implementation (C level), but not primitive level. > sure thing more cleanup & polishing can be done, > but the changes i made never get reviewed and properly tested (though, > there was no problems reported since year from when it was introduced, > except from last unfortunate rollback to Eliot's original implementation). > > > I know, which is why I thought you might like the feedback :P > AFAICT, it would be nice to couple the changes you made with changing > parameterAt: 49 back to returning nil, as well as returning an error for > parameterAt: 49 put: that the section is not in use/obsolete, instead of > returning bogus values. > > Though, sounds a bit strange how parameterAt: 49 can return a huge number > without any changes to the related code (which would then still be reading > from a 16bit field :P) > > > > >> Otherwise, you'll get a domain error when you eventually (yes,yes, it'll >> take awhile) run out, and maxExternalSemaphoresSilently: tries to set the >> new max to a value that won't fit in the 16bit header field where it >> expects to put itâ¦ >> >> yes.. theoretically.. but i have gut feeling that your image/setup will > experience a lot of other different problems (memory consumption/amount of > available OS handles etc), before you get to that point. And at that point, > you will need to modify VM/OS/image anyways (or figure how to work around > limits in other way).. > > > > Yap, I guess you could say changing to a nil return would be more a change > to play by established conventions when reporting capabilities/needs of the > VM than anything with practical impact. > > i agree. i will create a bug entry for it then.. > > Cheers, > Henry > -- Best regards, Igor Stasenko.

Oct. 8, 2013

Re: [Pharo-dev] Commit right on github.com/pharo-project/pharo-vm/

by Camillo Bruni

can you remake the pull request on the development branch? I changed the branches and added travis in the meantime. sorry for the inconvenience :( On 2013-10-08, at 10:19, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > Hi all, > > I made a pull request on github a week ago on the pharo-vm repo. > https://github.com/pharo-project/pharo-vm/pulls > > Can someone give me commit rights there? > > Bug entry is there: https://pharo.fogbugz.com/f/cases/11698/Serial-Plugin-primitives-ByName > > Cheers, > > #Luc

Oct. 8, 2013

[Issue Tracker] 129 issues tagged 3.0

by Marcus Denker

Hello, There are 129 issues that need to be fixed before we can even think about releasing Pharo3: https://pharo.fogbugz.com/f/filters/37/3-0-Work-Needed There are two options: 1) fix all of them. (unrealistic) 2) decided if all of them are real show stoppers, lower it and fix this hopefully smaller number actively. I know people don't like this option 2), but I do not see any realistic alternative. Marcus

Oct. 8, 2013

Commit right on github.com/pharo-project/pharo-vm/

by Luc Fabresse

Hi all, I made a pull request on github a week ago on the pharo-vm repo. https://github.com/pharo-project/pharo-vm/pulls Can someone give me commit rights there? Bug entry is there: https://pharo.fogbugz.com/f/cases/11698/Serial-Plugin-primitives-ByName Cheers, #Luc

Oct. 8, 2013

Re: [Pharo-dev] [Issue tracker] Help needed

by Benjamin

I would advice every fogbugz user who let such comment, to also add a "Do Later" task to remind them one week afterward to have a look :) I usually do that, adding to my comment that in case of no move, the case will be closed one week after. Ben On Oct 8, 2013, at 9:38 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hello, > > There are still many,many reports that are stuck. E.g. the last comment was "I can not see a committed Slice" > or "X, can you have a look?". > > There is *nothing* that anyone other than the original person meant in the last comment can do. > > Or maybe a good question: If you are that person X, what do you expect? How do *you* think the issue can > be moved forward? > > Marcus >

Oct. 8, 2013

[Issue tracker] Help needed

by Marcus Denker

Hello, There are still many,many reports that are stuck. E.g. the last comment was "I can not see a committed Slice" or "X, can you have a look?". There is *nothing* that anyone other than the original person meant in the last comment can do. Or maybe a good question: If you are that person X, what do you expect? How do *you* think the issue can be moved forward? Marcus

Oct. 8, 2013

Re: [Pharo-dev] [pharo-project/pharo-core] fda431: 30461

by Damien Cassou

On Mon, Oct 7, 2013 at 11:39 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > I still have to do a pass and convert the line-endings on the old commits... thank you so much Camillo -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Oct. 8, 2013

Re: [Pharo-dev] Please try to reproduce this bug

by Damien Cassou

On Mon, Oct 7, 2013 at 11:21 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > I have a lot of issues that this or like this. I get the sources problem as well as images I work for some time tell me that my working directory doesn't exist. I need to save and reopen the image to be able to do anything. do you use the Ubuntu PPA? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Oct. 8, 2013