November 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] InterruptedContext vs suspendedContext

by Andrei Chis

Hi, >From what I remember they are not always redundant, but I'm not 100% sure they are both needed. `suspendedContext` from Process is always the top context of a process. After execution actions like Step Into, Step Over, Step Through it will be the same as interruptedContext in the debugger. They will be different when opening the debugger as a result of an exception. Exception>>#debug triggers the workflow for opening a debugger. This uses `self signalerContext` as the context that is being debugged. This is the context where the exception was raised and this will be put in the interruptedContext. As this point the execution of the current process is not over and it will continue up to `MorphicUIManager>>#debugProcess:context:label:fullView:notification: ` where the current process is suspended. At that point the two will be different, as suspendedContext will be the context of the method MorphicUIManager>>#debugProcess:context:label:fullView:notification: and the interruptedContext the context that triggered the exception. But it might be that they are not both needed. One possible option might be to force the process to step to the context that raised the exception when the debugger is created. For example in DebugSession>>process:context:. Apart from when opening the debugger I do not know if there is another situation where those two can diverge. Cheers, Andrei On Fri, Nov 30, 2018 at 11:54 AM Thomas Dupriez < tdupriez(a)ens-paris-saclay.fr> wrote: > Hello, > > > Instances of DebugSession have an "interruptedContext" and an > "interruptedProcess" instance variable. > > Instances of Process have a "suspendedContext" instance variable. > > Does someone know if there is a relation between the interruptedContext of > a DebugSession and the suspendedContext of its interruptedProcess? At first > glance it seems like these two variables are redundant and store the same > Context. > > Thomas Dupriez >

Nov. 30, 2018

[Pharo 7.0-dev] Build #1429: 22679-Metacello-attributes-should-be-based-on-SystemVersion-instead-of-hardcoding

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1429 was: FAILURE. The Pull Request #1999 was integrated: "22679-Metacello-attributes-should-be-based-on-SystemVersion-instead-of-hardcoding" Pull request url: https://github.com/pharo-project/pharo/pull/1999 Issue Url: https://pharo.fogbugz.com/f/cases/22679 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 30, 2018

[Pharo 7.0-dev] Build #1428: 22679-Metacello-attributes-should-be-based-on-SystemVersion-instead-of-hardcoding

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1428 was: FAILURE. The Pull Request #1999 was integrated: "22679-Metacello-attributes-should-be-based-on-SystemVersion-instead-of-hardcoding" Pull request url: https://github.com/pharo-project/pharo/pull/1999 Issue Url: https://pharo.fogbugz.com/f/cases/22679 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 30, 2018

[Pharo 7.0-dev] Build #1427: 19927-scanFor-should-not-elide-extended-byte-codes

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1427 was: SUCCESS. The Pull Request #1872 was integrated: "19927-scanFor-should-not-elide-extended-byte-codes" Pull request url: https://github.com/pharo-project/pharo/pull/1872 Issue Url: https://pharo.fogbugz.com/f/cases/19927 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 30, 2018

[Pharo 7.0-dev] Build #1426: Fix the layout of Glamour tabulator rows and columns in the presence â¦

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1426 was: SUCCESS. The Pull Request #2004 was integrated: "Fix the layout of Glamour tabulator rows and columns in the presence â¦" Pull request url: https://github.com/pharo-project/pharo/pull/2004 Issue Url: https://pharo.fogbugz.com/f/cases/fixLayout Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 30, 2018

InterruptedContext vs suspendedContext

by Thomas Dupriez

Hello, Instances of DebugSession have an "interruptedContext" and an "interruptedProcess" instance variable. Instances of Process have a "suspendedContext" instance variable. Does someone know if there is a relation between the interruptedContext of a DebugSession and the suspendedContext of its interruptedProcess? At first glance it seems like these two variables are redundant and store the same Context. Thomas Dupriez

Nov. 30, 2018

[Pharo 7.0-dev] Build #1425: 22712-speed-up-mustBeBooleanDeOptimizeIn-by-a-factor-of-200-by-caching

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1425 was: SUCCESS. The Pull Request #2026 was integrated: "22712-speed-up-mustBeBooleanDeOptimizeIn-by-a-factor-of-200-by-caching" Pull request url: https://github.com/pharo-project/pharo/pull/2026 Issue Url: https://pharo.fogbugz.com/f/cases/22712 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 30, 2018

Re: [Pharo-dev] [Pharo-users] [Ann] TaskIt v1.0

by Santiago Bragagnolo

Hey those are good news :). Tell me if I can help you on that. Santiago El jue., 29 de nov. de 2018 17:55, Norbert Hartl <norbert(a)hartl.name> escribiÃ³: > Hi Santiago, > > > Am 29.11.2018 um 17:48 schrieb Santiago Bragagnolo < > santiagobragagnolo(a)gmail.com>: > > Hi Norbert! > > We don't have yet implemented any nor all combinations. I will add it to > the list of things to do for next release. Looks like a simple and useful > thing to have. (Or if you have already something I wouldn't mind to > integrate it) > > I donât have it now but I think when we change to TaskIt we will make them > and we could provide it then. > > Norbert > > > > Thanks. > Santiago > > > El jue., 29 de nov. de 2018 17:36, Norbert Hartl via Pharo-users < > pharo-users(a)lists.pharo.org> escribiÃ³: > >> Great, thanks! >> >> Does TaskIt include implementations for combining futures such as the ALL >> and the ANY futures which resolve either when all or one future resolves? >> From the documentation it looks that rather not. >> >> Norbert >> >> >> Am 29.11.2018 um 15:29 schrieb Santiago Bragagnolo < >> santiagobragagnolo(a)gmail.com>: >> >> Hi everybody :). >> >> I am happy to announce TaskIt v1.0. >> >> In this version we add some new features, passed over the red tests and >> clean up some dead code. And did a pass in the documentation >> >> A bit from the DOC >> Downloading >> >> Current stable version of taskit can be downloaded using metacello as >> follows: >> >> Metacello new >> baseline: 'TaskIt'; >> repository: 'github://sbragagnolo/taskit'; >> load. >> >> If you want a specific release such as v1.0, you can load the associated >> tag as follows >> >> Metacello new >> baseline: 'TaskIt'; >> repository: 'github://sbragagnolo/taskit:v1.0'; >> load. >> >> Otherwise, if you want the latest development version, take a look at the >> development branchs and load the latest: >> >> Metacello new >> baseline: 'TaskIt'; >> repository: 'github://sbragagnolo/taskit:dev-1.1'; >> load. >> >> >> <https://github.com/sbragagnolo/taskit/blob/master/README.md#major-features>Major >> Features >> >> - Actors (ActIt) >> - Configuration Profiles >> - Service >> >> >> Check specially the configuration profiles. The default profile usage is >> #development, which sets up the environment for debugging exceptions in a >> process. >> >> I want to thank a lot to the contributors, Guillermo Polito Max Leske >> and Daniel Sasu. >> I want as well to thanks the users, specially to those that bring me >> feedback (blames and ideas) in person (Esteban, Pablo) or through the >> different channels (Holger Freyther, Juraj Kubelka, Philippe Back). >> >> >> I want also to apologise the delay of my responses on the issue board :) >> (Really, sorry). I am constantly using TaskIt in other projects, but much >> times I cannot do it my priority. >> >> >> thanks a lot, >> >> Santiago Bragagnolo. >> >> >> >> >> >> >> >> >> >> >> >

Nov. 29, 2018

Re: [Pharo-dev] [Pharo-users] [Ann] TaskIt v1.0

by Norbert Hartl

Hi Santiago, > Am 29.11.2018 um 17:48 schrieb Santiago Bragagnolo <santiagobragagnolo(a)gmail.com>: > > Hi Norbert! > > We don't have yet implemented any nor all combinations. I will add it to the list of things to do for next release. Looks like a simple and useful thing to have. (Or if you have already something I wouldn't mind to integrate it) > I donât have it now but I think when we change to TaskIt we will make them and we could provide it then. Norbert > > > Thanks. > Santiago > > > El jue., 29 de nov. de 2018 17:36, Norbert Hartl via Pharo-users <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>> escribiÃ³: > Great, thanks! > > Does TaskIt include implementations for combining futures such as the ALL and the ANY futures which resolve either when all or one future resolves? From the documentation it looks that rather not. > > Norbert > > >> Am 29.11.2018 um 15:29 schrieb Santiago Bragagnolo <santiagobragagnolo(a)gmail.com <mailto:santiagobragagnolo@gmail.com>>: >> >> Hi everybody :). >> >> I am happy to announce TaskIt v1.0. >> >> In this version we add some new features, passed over the red tests and clean up some dead code. And did a pass in the documentation >> >> A bit from the DOC >> Downloading >> >> Current stable version of taskit can be downloaded using metacello as follows: >> >> Metacello new >> baseline: 'TaskIt'; >> repository: 'github://sbragagnolo/taskit <>'; >> load. >> If you want a specific release such as v1.0, you can load the associated tag as follows >> >> Metacello new >> baseline: 'TaskIt'; >> repository: 'github://sbragagnolo/taskit:v1.0 <>'; >> load. >> Otherwise, if you want the latest development version, take a look at the development branchs and load the latest: >> >> Metacello new >> baseline: 'TaskIt'; >> repository: 'github://sbragagnolo/taskit:dev-1.1 <>'; >> load. >> <https://github.com/sbragagnolo/taskit/blob/master/README.md#major-features>Major Features >> >> Actors (ActIt) >> Configuration Profiles >> Service >> >> Check specially the configuration profiles. The default profile usage is #development, which sets up the environment for debugging exceptions in a process. >> >> I want to thank a lot to the contributors, Guillermo Polito Max Leske and Daniel Sasu. >> I want as well to thanks the users, specially to those that bring me feedback (blames and ideas) in person (Esteban, Pablo) or through the different channels (Holger Freyther, Juraj Kubelka, Philippe Back). >> >> >> I want also to apologise the delay of my responses on the issue board :) (Really, sorry). I am constantly using TaskIt in other projects, but much times I cannot do it my priority. >> >> >> thanks a lot, >> >> Santiago Bragagnolo. >> >> >> >> >> >> >> >> >> >

Nov. 29, 2018

Re: [Pharo-dev] [Pharo-users] [Ann] TaskIt v1.0

by Santiago Bragagnolo

Hi Norbert! We don't have yet implemented any nor all combinations. I will add it to the list of things to do for next release. Looks like a simple and useful thing to have. (Or if you have already something I wouldn't mind to integrate it) Thanks. Santiago El jue., 29 de nov. de 2018 17:36, Norbert Hartl via Pharo-users < pharo-users(a)lists.pharo.org> escribiÃ³: > Great, thanks! > > Does TaskIt include implementations for combining futures such as the ALL > and the ANY futures which resolve either when all or one future resolves? > From the documentation it looks that rather not. > > Norbert > > > Am 29.11.2018 um 15:29 schrieb Santiago Bragagnolo < > santiagobragagnolo(a)gmail.com>: > > Hi everybody :). > > I am happy to announce TaskIt v1.0. > > In this version we add some new features, passed over the red tests and > clean up some dead code. And did a pass in the documentation > > A bit from the DOC > Downloading > > Current stable version of taskit can be downloaded using metacello as > follows: > > Metacello new > baseline: 'TaskIt'; > repository: 'github://sbragagnolo/taskit'; > load. > > If you want a specific release such as v1.0, you can load the associated > tag as follows > > Metacello new > baseline: 'TaskIt'; > repository: 'github://sbragagnolo/taskit:v1.0'; > load. > > Otherwise, if you want the latest development version, take a look at the > development branchs and load the latest: > > Metacello new > baseline: 'TaskIt'; > repository: 'github://sbragagnolo/taskit:dev-1.1'; > load. > > > <https://github.com/sbragagnolo/taskit/blob/master/README.md#major-features>Major > Features > > - Actors (ActIt) > - Configuration Profiles > - Service > > > Check specially the configuration profiles. The default profile usage is > #development, which sets up the environment for debugging exceptions in a > process. > > I want to thank a lot to the contributors, Guillermo Polito Max Leske > and Daniel Sasu. > I want as well to thanks the users, specially to those that bring me > feedback (blames and ideas) in person (Esteban, Pablo) or through the > different channels (Holger Freyther, Juraj Kubelka, Philippe Back). > > > I want also to apologise the delay of my responses on the issue board :) > (Really, sorry). I am constantly using TaskIt in other projects, but much > times I cannot do it my priority. > > > thanks a lot, > > Santiago Bragagnolo. > > > > > > > > > > >

Nov. 29, 2018