- Pharo-dev - lists.pharo.org

slow RPackageOrganizer >> packageNamed:
by Camillo Bruni Sept. 24, 2013

Sept. 24, 2013

@Esteban what is the reason we have to do a case-ignored check for looking up a package in #packageNamed:? seems unnecessary slow to me :/, maybe we can add a #packageNamedIgoreCase: ?

2 1

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Sept. 24, 2013

Sept. 24, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=wi… 1 regressions found. Zinc.Zodiac.ZnHTTPSTests.testGetPharoVersion

1 0

[update 3.0] #30421
by Marcus Denker Sept. 24, 2013

Sept. 24, 2013

1 0

Re: [Pharo-dev] Smalltalkhub - REST API :) (a.k.a. Sorry, if I broke it...^^)
by Stephan Eggermont Sept. 24, 2013

Sept. 24, 2013

And please don't all at the same time download and run the DeprecationFinder code, until Nicolas tells you he wants to do a load test! Stephan

1 0

Re: [Pharo-dev] Smalltalkhub - REST API :) (a.k.a. Sorry, if I broke it...^^)
by Stephan Eggermont Sept. 24, 2013

Sept. 24, 2013

Hi Marcel, >my goal is to find the big ones to take a closer look at. Thus, next steps would be to fetch the latest MCZ of all projects and then analyze their contents. :) That is in DeprecationFinder. (load in a Moose 4.8 after loading NeoJSon). Current analysis is just getting the invocations from a MooseMonticelloImporter for the latest packageversion. It needs to be extended to also walk the team projects. Further steps would be to make it incremental and have a fuel file as artefact in a Jenkins build. Stephan

1 0

SHA1 changed ??
by Sven Van Caekenberghe Sept. 24, 2013

Sept. 24, 2013

Max, Why was the contract of SHA1>>hashStream: changed ? It used to return a ByteArray like other HashFunction subclasses, now it returns an Integer. I see that you also changed the tests with this assumption. MD5 hashMessage: 'foo'. #[172 189 24 219 76 194 248 92 237 239 101 79 204 196 164 216] SHA1 hashMessage: 'foo'. 68123873083688143418383284816464454849230703155 It broke Zinc-WebSockets in 3.0 and now I will have to do an ugly hack to make the code work on multiple Pharo versions. Can you please explain ? Sven

5 8

Re: [Pharo-dev] Use pharo users mailing list
by Stephan Eggermont Sept. 23, 2013

Sept. 23, 2013

Hannes wrote: > In reply to this post by Stephan Eggermont > On 9/23/13, Stephan Eggermont <[hidden email]> wrote: > > Kilon wrote > >>Here is a radical suggestion you probably don't want to hear. > >>Close down Pharo users mailing list, redirect everyone to stackoverflow. > > > > Definitely not. Stackoverflow is nearly dead, and seriously unsuitable for > > small languages. > > There are obstacles but one cannot say that it is "seriously > unsuitable". I feel fully qualified to make that statement. Getting voted on by majority views is not exactly what we need. Especially not in a cargo-cult driven profession. > >Good questions will get closed by clueless people. > Mostly if the form does not fit. Nope. there has been a strong change in what is deemed to be an acceptable question on SO in the past years. And not in the right direction. I know several posters here who have been bitten by that. > And if there are Pharo people (maybe earned in another area) with > enough reputation points this may be prevented That would be nice, but isn't the case. Stackoverflow doesn't work like that. > > Good answers will get downvoted because they go against majority > > views. > > Why? Because stackoverflow is an opinion site, dominated by popularity. Nobody says an answer has to be right. Like I said, take a look at questions on OODBs. > >The ranking system is heavily skewed towards popular languages. > > It is based on the number of hits which is naturally less in less > popular languages. > However subcommunities may function well in stackoverflow. No, not really. It means that members of subcommunities have less rights and power. There is no value in subdividing our community further. Stephan

3 4

[update 2.0] #20419
by Marcus Denker Sept. 23, 2013

Sept. 23, 2013

20419 ----- 11502 Override Class >> #setName: https://pharo.fogbugz.com/f/cases/11502 There is a dirty package after this, it will be fixed in 420. Marcus

2 3

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Sept. 23, 2013

Sept. 23, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=ma… 1 regressions found. KernelTests.Classes.ClassTest.testClassRespectsPolymorphismWithTrait

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Sept. 23, 2013

Sept. 23, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=wi… 1 regressions found. KernelTests.Classes.ClassTest.testClassRespectsPolymorphismWithTrait

1 0