- Pharo-users - lists.pharo.org

Re: [Pharo-users] Shutting down persona.org in November 2016

by Mariano Martinez Peck

Damien, offtopic question, but do you know if it is possible to see the pillar code of those stuff in http://pillarhub.pharocloud.com?? It would be very very handy to see compiled output (like that one) and then see the pillar file to see how someone manage to do something. If it is not there, is it elsewhere what I am searching for? Thoughts? On Tue, Jan 12, 2016 at 6:17 AM, Damien Cassou <damien.cassou(a)inria.fr> wrote: > Hi, > > both pharo.org and pillarhub.pharocloud.com rely on persona.org for > authentication. This service will disappear. > > > > ---------- Forwarded message ---------- > From: Ryan Kelly <rfkelly(a)mozilla.com> > To: "dev-identity(a)lists.mozilla.org" <dev-identity(a)lists.mozilla.org>, > persona-notices(a)mozilla.org > Cc: > Date: Mon, 11 Jan 2016 17:06:54 -0800 > Subject: Shutting down persona.org in November 2016 > > Hi Everyone, > > > When the Mozilla Identity team transitioned Persona to community > ownership, we committed resources to operational and security support > throughout 2014 [1], and renewed that commitment for 2015 [2]. Due to > low, declining usage, we are reallocating the projectâs dedicated, > ongoing resources and will shut down the persona.org services that we run. > > Persona.org and related domains will be taken offline on November 30th, > 2016. > > If you run a website that relies on Persona, you will need to implement > an alternative login solution for your users. We have assembled a wiki > page with additional information and guidelines for migration [3], but > here are the important things you need to know: > > Between now and November 30th, 2016, Mozilla will continue to support > the Persona service at a maintenance level: > > * Security issues will be resolved in a timely manner and the services > will be kept online, but we do not expect to develop or deploy any > new features. > > * Support will continue to be available on the dev-identity mailing > list [4] and in the #services-dev IRC channel [5]. > > * All websites that rely on persona.org will need to migrate to > another means of authentication during this period. > > Beginning on November 30th, 2016, the Persona service hosted by Mozilla > will be decommissioned: > > * All services hosted on the persona.org domain will be shut down. > > * Mozilla will retain control of the persona.org domain and will > not transfer it to a third party. > > * Since the privacy of user data is of utmost importance to Mozilla, > we will destroy all user data stored on the persona.org servers, > and will not transfer it to third parties. > > We intentionally designed Persona to expose email addresses rather than > opaque identifiers, which should ease the transition to other systems > that provide verified email addresses. You can find guidelines on > alternative login solutions on the wiki [3] and we will continue to > update them over the coming year. We strongly encourage affected teams > to openly discuss and blog about their migrations on the dev-identity > mailing list so that others can learn from their experience. > > Thank you for your support and involvement with Persona. If you have any > questions, please post them to the dev-identity mailing list. > > > Ryan > > > [1] > > http://identity.mozilla.com/post/78873831485/transitioning-persona-to-commu… > [2] > https://groups.google.com/forum/#!topic/mozilla.dev.identity/rPIm7GxOeNU > [3] > https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers > [4] https://lists.mozilla.org/listinfo/dev-identity > [5] http://irc.mozilla.org/#services-dev > _______________________________________________ > Persona-notices mailing list > Persona-notices(a)mozilla.org > https://mail.mozilla.org/listinfo/persona-notices > > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill > > -- Mariano http://marianopeck.wordpress.com

Jan. 12, 2016

Shutting down persona.org in November 2016

by Damien Cassou

Hi, both pharo.org and pillarhub.pharocloud.com rely on persona.org for authentication. This service will disappear. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Jan. 12, 2016

Re: [Pharo-users] Failling Tests are green if BlockCannotReturn exception

by ClÃ©ment Bera

2016-01-12 0:40 GMT+01:00 Vincent BLONDEAU < vincent.blondeau(a)polytech-lille.net>: > Hi, > > > > It is expected. > > When you evaluate a block with a return, the method containing the block > definition (here testBlock) will return. > > So the test will pass. > > > > BTW, you donât need to put a return in a block. By default, the last > instruction will be returned. > > > [ ^ 1 ] => non local return [ 1 ] => local return The 2 blocks are very different from each other. One returns to the closure activation sender, while the other returns to the closure creating context sender. See the chapter 14.4 Returning from inside a Block from the free book Deep Into Pharo <http://deepintopharo.com/> So I would not say you don't need to put a return in a block. You want to put a return or not depending on the behavior you want. > Cheers, > > Vincent > > > > *From:* Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] *On > Behalf Of *abdelghani ALIDRA > *Sent:* mardi 12 janvier 2016 00:26 > *To:* Any Question About Pharo Is Welcome > *Subject:* [Pharo-users] Failling Tests are green if BlockCannotReturn > exception > > > > Hi, > > > > I observed this unexpected behavior in test classes. > > In a test class define a method : > > > > > > > > *testBlock |aBlock| aBlock := [ ^1 ]. aBlock value. self > assert: false.* > > > > Althought the assertion is false at the end of the test, the test is green. > > Actually, It does not matter what you put after *aBlock value*, the test > always succedes (I tried to put a self halt, it does not execute) > > I tried this both in Pharo 4 and 5 under Windows and MacOS. > > > > Any ideas? > > > > Cheers > > Abdelghani > > > > >

Jan. 12, 2016

Re: [Pharo-users] Failling Tests are green if BlockCannotReturn exception

by Sven Van Caekenberghe

> On 12 Jan 2016, at 00:26, abdelghani ALIDRA <alidrandco(a)yahoo.fr> wrote: > > Hi, > > I observed this unexpected behavior in test classes. > In a test class define a method : > > testBlock > |aBlock| > aBlock := [ ^1 ]. > aBlock value. > self assert: false. > > Althought the assertion is false at the end of the test, the test is green. > Actually, It does not matter what you put after aBlock value, the test always succedes (I tried to put a self halt, it does not execute) The test is 'does an explicit return from a block return from the whole method'. Of course it does. But if it would not, you would arrive at the self assert: false and the test would fail. You see ? BTW, this can also be written as self fail - search for the senders of that message for more examples. > I tried this both in Pharo 4 and 5 under Windows and MacOS. > > Any ideas? > > Cheers > Abdelghani > >

Jan. 12, 2016

Re: [Pharo-users] Failling Tests are green if BlockCannotReturn exception

by Vincent BLONDEAU

Hi, It is expected. When you evaluate a block with a return, the method containing the block definition (here testBlock) will return. So the test will pass. BTW, you donât need to put a return in a block. By default, the last instruction will be returned. Cheers, Vincent From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of abdelghani ALIDRA Sent: mardi 12 janvier 2016 00:26 To: Any Question About Pharo Is Welcome Subject: [Pharo-users] Failling Tests are green if BlockCannotReturn exception Hi, I observed this unexpected behavior in test classes. In a test class define a method : testBlock |aBlock| aBlock := [ ^1 ]. aBlock value. self assert: false. Althought the assertion is false at the end of the test, the test is green. Actually, It does not matter what you put after aBlock value, the test always succedes (I tried to put a self halt, it does not execute) I tried this both in Pharo 4 and 5 under Windows and MacOS. Any ideas? Cheers Abdelghani

Jan. 11, 2016

Re: [Pharo-users] Failling Tests are green if BlockCannotReturn exception

by Johan Fabry

Hi Abdelghani, this is actually correct behavior: by putting [ ^1 ] , you are specifying that the method should return 1 when the block is executed. So the result of aBlock value is that the method returns 1. If you want that the result of evaluating the block is 1, you should just put [ 1 ] Hope this helps, > On Jan 11, 2016, at 20:26, abdelghani ALIDRA <alidrandco(a)yahoo.fr> wrote: > > Hi, > > I observed this unexpected behavior in test classes. > In a test class define a method : > > testBlock > |aBlock| > aBlock := [ ^1 ]. > aBlock value. > self assert: false. > > Althought the assertion is false at the end of the test, the test is green. > Actually, It does not matter what you put after aBlock value, the test always succedes (I tried to put a self halt, it does not execute) > I tried this both in Pharo 4 and 5 under Windows and MacOS. > > Any ideas? > > Cheers > Abdelghani > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

Jan. 11, 2016

Failling Tests are green if BlockCannotReturn exception

by abdelghani ALIDRA

Hi, I observed this unexpected behavior in test classes.In a test class define a method : testBlock Â Â Â |aBlock| Â Â Â aBlock := [ ^1 ]. Â Â Â aBlock value. Â Â Â self assert: false. Althought the assertion is false at the end of the test, the test is green.Actually, It does not matter what you put after aBlock value, the test always succedes (I tried to put a self halt, it does not execute) I tried this both in Pharo 4 and 5 under Windows and MacOS. Any ideas? Cheers Abdelghani

Jan. 11, 2016

Re: [Pharo-users] When Pharo 5 is to be released as stable ?

by Dimitris Chloupis

Ah perfect thanks Esteban On Mon, 11 Jan 2016 at 21:14, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > april > > > On 11 Jan 2016, at 19:55, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > > > > I am curious when is Pharo 5 is to be released as stable and move to > Pharo 6 , any idea ? > > >

Jan. 11, 2016

Re: [Pharo-users] When Pharo 5 is to be released as stable ?

by Esteban Lorenzano

april > On 11 Jan 2016, at 19:55, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > I am curious when is Pharo 5 is to be released as stable and move to Pharo 6 , any idea ?

Jan. 11, 2016

When Pharo 5 is to be released as stable ?

by Dimitris Chloupis

I am curious when is Pharo 5 is to be released as stable and move to Pharo 6 , any idea ?

Jan. 11, 2016