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

Re: [Pharo-dev] [update 3.0] #30261

by Marcus Denker

On Jul 11, 2013, at 10:27 AM, Friedrich Dominicus <frido(a)q-software-solutions.de> wrote: > Marcus Denker <marcus.denker(a)inria.fr> writes: > >> 30261 >> ----- >> >> 11138 Implementation of user directories is a mess >> https://pharo.fogbugz.com/f/cases/11138 >> >> Diff information: >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Traits-MarcusDenker.542.diff >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/FileSystem-Core-MarcusDenker.… > Stupid question how am I supposed to read that stuff on fogbugz? > Sadly right now one needs an account... There are multiple bugs that make the experience right now a bit sub-optimal 1) to get an account quickly there is http://bugs.pharo.org *but* there is a bug that it does not work with a dot in the email address. 2) http://bugs.pharo.org *should* be a complete list of all the open bugs and the links in the mail *should* point there, but sadly it is not up to date. For all these there are of course bugs reportedâ¦ but sadly they don't solve themselves. Marcus

July 11, 2013

Re: [Pharo-dev] Some Spec questions

by Andrei Vasile Chis

> Actually Erwan Douaille is doing WidgetAbstractWrapper to solve this > problem (I've just learnt that a few minutes ago). You may discuss with him > about that. > Super. Thanks for all the help and the info Andrei

July 11, 2013

Re: [Pharo-dev] [update 3.0] #30263

by Marcus Denker

I will revert this updateâ¦ we *really* need something that runs the tests of the submitted fixesâ¦ it seems that 11147 FileReference(Object)>>doesNotUnderstand: #other is not working *at all*. On Jul 11, 2013, at 10:00 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 30263 > ----- > > 10304 FileStreamTest should cleanup test files created > https://pharo.fogbugz.com/f/cases/10304 > > 10466 Better interruption > https://pharo.fogbugz.com/f/cases/10466 > > 11147 FileReference(Object)>>doesNotUnderstand: #other > https://pharo.fogbugz.com/f/cases/11147 > > > Diff information: > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tests-MarcusDenker.583.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-MarcusDenker.1515.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/FileSystem-Tests-Core-MarcusD… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/FileSystem-Core-MarcusDenker.… >

July 11, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/… 25 regressions found. FileSystem.Tests.Disk.DiskFileSystemTest.testCopy FileSystem.Tests.Disk.DiskFileSystemTest.testCopyDestExists FileSystem.Tests.Disk.DiskFileSystemTest.testCopySourceDoesntExist FileSystem.Tests.Disk.DiskFileSystemTest.testCopyWithCorrectBasename FileSystem.Tests.Disk.DiskFileSystemTest.testDirectory FileSystem.Tests.Disk.DiskFileSystemTest.testEnsureDirectory FileSystem.Tests.Disk.DiskFileSystemTest.testEnsureDirectoryCreatesParent FileSystem.Tests.Disk.DiskFileSystemTest.testEnsureDirectoryExists FileSystem.Tests.Disk.DiskFileSystemTest.testEntriesAt FileSystem.Tests.Disk.DiskFileSystemTest.testEntryAt FileSystem.Tests.Disk.FileHandleTest.testAt FileSystem.Tests.Disk.FileHandleTest.testAtPut FileSystem.Tests.Disk.FileHandleTest.testAtPutBinaryAscii FileSystem.Tests.Disk.FileHandleTest.testAtWriteBinaryAscii FileSystem.Tests.Disk.FileHandleTest.testClose FileSystem.Tests.Disk.FileHandleTest.testCreatedOpen FileSystem.Tests.Disk.FileHandleTest.testEnsureClosed FileSystem.Tests.Disk.FileHandleTest.testIO FileSystem.Tests.Disk.FileHandleTest.testReadBufferTooLarge FileSystem.Tests.Disk.FileHandleTest.testReadOnly ...

July 11, 2013

[update 3.0] #30263

by Marcus Denker

30263 ----- 10304 FileStreamTest should cleanup test files created https://pharo.fogbugz.com/f/cases/10304 10466 Better interruption https://pharo.fogbugz.com/f/cases/10466 11147 FileReference(Object)>>doesNotUnderstand: #other https://pharo.fogbugz.com/f/cases/11147 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tests-MarcusDenker.583.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-MarcusDenker.1515.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/FileSystem-Tests-Core-MarcusD… http://smalltalkhub.com/mc/Pharo/Pharo30/main/FileSystem-Core-MarcusDenker.…

July 11, 2013

Re: [Pharo-dev] Some updates to GLorp

by StÃ©phane Ducasse

On Jul 10, 2013, at 10:04 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi guys > > I did a couple of things related to Glorp. I commited 2 fixes related to the connection pool. > Also, for the native postgres driver, I adapted the pool we have for OpenDBXDriver. It's quite ugly because we are duplicating quite a lot of code, but the hierarchy make things complicated here and I don't have more time to improve it (at least not right now). If someone wants to give it a shoot :) You can give it as an exercise to a student hahaha. > > So...to sum up, some fixes in GlorpOpenDBXDriver and the new connection pool to > GlorpDriverPostgreSQL. > Hi mariano I think that this is important that you allocate a certain percentage of your dev time to improve the tools you use else there is no possibility of progress. I would not wait for a student to fix code that nobody in our team (except esteban probably) ever used. Stef > Cheers, > > -- > Mariano > http://marianopeck.wordpress.com

July 11, 2013

Re: [Pharo-dev] the return of the strange methods

by StÃ©phane Ducasse

On Jul 11, 2013, at 8:32 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Jul 11, 2013, at 8:26 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> I would really like to have Sunit 5 in Pharo. >> > > Of course we added lots of things to Sunit, so this means rewriting tests. (e.g. skip). > > And we will get the sunit* methods backâ¦ I hate them :-) this is why we should - have the possibility to have two different Unit frameworks - take the time to get the new version. Stef

July 11, 2013

Re: [Pharo-dev] the return of the strange methods

by Marcus Denker

On Jul 11, 2013, at 8:26 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I would really like to have Sunit 5 in Pharo. > Of course we added lots of things to Sunit, so this means rewriting tests. (e.g. skip). And we will get the sunit* methods backâ¦ I hate them :-) > Stef > > On Jul 10, 2013, at 6:45 PM, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: > >>> What you want is a TAssertable>>#should:raise: that: >>> - takes a one arg block as second argument that is evaluated with the >>> exception thrown >>> - fails if no exception is raised >>> >> >> Then please call it #should:raise:suchThat: >> That's what is in upcoming SUnit 5.0 [1] >> >> Also I would avoid using traits in SUnit, this is >> non-portable. The TestAsserter class was introduced already >> in SUnit 4.0. Indeed, only if you at all care about having SUnit in sync >> with other dialects :-) >> >> Best, Jan >> >> [1]: https://swing.fit.cvut.cz/hg/stx.goodies.sunit/file/fb932a5daa97/TestAssert… >> > >

July 11, 2013

Re: [Pharo-dev] the return of the strange methods

by StÃ©phane Ducasse

I would really like to have Sunit 5 in Pharo. Stef On Jul 10, 2013, at 6:45 PM, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: >> What you want is a TAssertable>>#should:raise: that: >> - takes a one arg block as second argument that is evaluated with the >> exception thrown >> - fails if no exception is raised >> > > Then please call it #should:raise:suchThat: > That's what is in upcoming SUnit 5.0 [1] > > Also I would avoid using traits in SUnit, this is > non-portable. The TestAsserter class was introduced already > in SUnit 4.0. Indeed, only if you at all care about having SUnit in sync > with other dialects :-) > > Best, Jan > > [1]: https://swing.fit.cvut.cz/hg/stx.goodies.sunit/file/fb932a5daa97/TestAssert… >

July 11, 2013

Re: [Pharo-dev] sunit failures vs errors

by StÃ©phane Ducasse

camillo frankly there are plenty of things that should be improved but for SUnit. First we should look at the main branch in VW because it changes since we forked it Second Smalltalk/X people probably enhance it too. Fourth there is also assess the frameworks of andres that has really nice extensions for benchmarking. And I vote against changing SUnit. If each time somebody ask a question in the mailing-lit we get a change we will never focus on the important items. Stef On Jul 10, 2013, at 1:47 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > On 2013-07-10, at 13:32, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> Precisely. There is a huge difference between invalidating a known contract (i.e., failure) and raising an unexpected error (i.e., error). > > In which sense? > As a programmer I have to tackle them both the same way: start debugging. > > I really do not see the difference. In both cases the code does not behave as expected. > One might even say that there is a global contract that the code does not raise exceptions. > > Tackling the failures first is purely a habit induced by the existing system that errors are worse than failures

July 11, 2013