- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #482: 3446-String-has-many-methods-about-searching-in-the-accessing-category fix #3446
by ci-pharo-ci-jenkins2＠inria.fr July 12, 2019

July 12, 2019

There is a new Pharo build available! The status of the build #482 was: FAILURE. The Pull Request #3907 was integrated: "3446-String-has-many-methods-about-searching-in-the-accessing-category fix #3446" Pull request url: https://github.com/pharo-project/pharo/pull/3907 Issue Url: https://github.com/pharo-project/pharo/issues/3446 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] [Pharo-users] Test Completion has been added to Pharo 8 - please test!
by Cyril Ferlicot July 12, 2019

July 12, 2019

On Wed, Jul 3, 2019 at 2:29 AM Myroslava Romaniuk via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hi all, > > we added an intermediate version of the upcoming test completion to Pharo 8, it would be cool if you tested it and let us know the results. Here's a blog post about it - link, and here's a tweet I'd be grateful if you shared - link so perhaps people who don't read the mailing list would also see it. In the blog post you can find more info how to enable the completion in the settings and details about the whole thing in general. If something doesn't work, or if something works differently than it used to in the old completion (both if you don't like it or perhaps if you prefer it) let me know either replying here, on twitter, or submitting an issue request directly for the github repository here - link. > Hi, Since the new code completion is enable I have problem with variables completion. I saw it the most with temporary variables that are not proposed for completion anymore. This is really annoying since I often have long variables names to be explicit in my code :( I hope it can help you improve it :) > Thanks very much, > Myroslava -- Cyril Ferlicot https://ferlicot.fr

2 1

[Pharo 8.0] Build #481: Deprecated #addSelector:withMethod:notifying: methods should be in Deâ¦
by ci-pharo-ci-jenkins2＠inria.fr July 12, 2019

July 12, 2019

There is a new Pharo build available! The status of the build #481 was: FAILURE. The Pull Request #3890 was integrated: "Deprecated #addSelector:withMethod:notifying: methods should be in Deâ¦" Pull request url: https://github.com/pharo-project/pharo/pull/3890 Issue Url: https://github.com/pharo-project/pharo/issues/3889 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #480: Put a NotFoundError into Deprecated80 for compatibility
by ci-pharo-ci-jenkins2＠inria.fr July 12, 2019

July 12, 2019

There is a new Pharo build available! The status of the build #480 was: FAILURE. The Pull Request #3899 was integrated: "Put a NotFoundError into Deprecated80 for compatibility" Pull request url: https://github.com/pharo-project/pharo/pull/3899 Issue Url: https://github.com/pharo-project/pharo/issues/3898 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #479: 3847-TestRunner-code-coverage-does-not-need-to-use-method-reference-wrapping
by ci-pharo-ci-jenkins2＠inria.fr July 12, 2019

July 12, 2019

There is a new Pharo build available! The status of the build #479 was: FAILURE. The Pull Request #3849 was integrated: "3847-TestRunner-code-coverage-does-not-need-to-use-method-reference-wrapping" Pull request url: https://github.com/pharo-project/pharo/pull/3849 Issue Url: https://github.com/pharo-project/pharo/issues/3847 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #478: 3895-improve-RGMethodDefinitionprintOn-and-name
by ci-pharo-ci-jenkins2＠inria.fr July 12, 2019

July 12, 2019

There is a new Pharo build available! The status of the build #478 was: FAILURE. The Pull Request #3896 was integrated: "3895-improve-RGMethodDefinitionprintOn-and-name" Pull request url: https://github.com/pharo-project/pharo/pull/3896 Issue Url: https://github.com/pharo-project/pharo/issues/3895 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #477: Consistency in how compilerOptions are represented
by ci-pharo-ci-jenkins2＠inria.fr July 12, 2019

July 12, 2019

There is a new Pharo build available! The status of the build #477 was: FAILURE. The Pull Request #3893 was integrated: "Consistency in how compilerOptions are represented" Pull request url: https://github.com/pharo-project/pharo/pull/3893 Issue Url: https://github.com/pharo-project/pharo/issues/compilerOptions Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #476: 3471-SmallIntegers-comment-is-out-of-date (fixes #3471)
by ci-pharo-ci-jenkins2＠inria.fr July 12, 2019

July 12, 2019

There is a new Pharo build available! The status of the build #476 was: FAILURE. The Pull Request #3888 was integrated: "3471-SmallIntegers-comment-is-out-of-date (fixes #3471)" Pull request url: https://github.com/pharo-project/pharo/pull/3888 Issue Url: https://github.com/pharo-project/pharo/issues/3471 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #475: Cleanup ASTCache
by ci-pharo-ci-jenkins2＠inria.fr July 12, 2019

July 12, 2019

There is a new Pharo build available! The status of the build #475 was: FAILURE. The Pull Request #3878 was integrated: "Cleanup ASTCache" Pull request url: https://github.com/pharo-project/pharo/pull/3878 Issue Url: https://github.com/pharo-project/pharo/issues/3877 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Changes proposal on Pre debugger
by Cyril Ferlicot D. July 12, 2019

July 12, 2019

Hi, After talking with Steven (in copy) we agreed on possible improvements around the pre debugger. I would like to share our vision and check if the community agrees. Context: The pre debugger is the window opening when an exception is signalled and not catched. This window currently has two views: - On warnings it display a text explaining the encountered problem. You can the proceed, abandon or debug. For example, this happens on Deprecations. - On other exceptions it display a short stack of the context in which the error was raised. You can abandon, open a full debugger, ... Before, both views were managed via the same UI class. Yesterday I slitted this class. Proposed change: In our opinion, the pre debugger displaying a stack is useless. All the options it proposes are in the full debugger within one click reach. The only value we see for the pre debugger is about warnings. Thus, we propose to remove the stack pre debugger and display directly the full debugger for anything else than a warning. This will save everyone one click each time we want to debug something. We would keep the textual view for warnings. In case we do this, I wonder if we should keep the setting "Open full debugger". I think most users of this option are using it in order to not see the stack pre debugger and not to skip warnings. So, do someone have an opinion about keeping or removing this setting in case we remove the stack pre debugger? Possible future changes: In the future I would also like it if the opening of the pre (or full) debugger would be delegated to the raised exception in order to allow the introduction of different pre debuggers. But it's just an idea and not the scope of this mail. :) -- Cyril Ferlicot https://ferlicot.fr

8 12