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

aString translated

by Sean P. DeNigris

Why is #translated sent to all the window menu strings, but not the world menu ones? ----- Cheers, Sean -- View this message in context: http://forum.world.st/aString-translated-tp4693253.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 14, 2013

Re: [Pharo-dev] Zinc problem with PUT requests

by Sean P. DeNigris

Sean P. DeNigris wrote > when I try to log in I get "Error: Not enough space for external objects, > set a larger size at startup!" Update2: I bumped my RAM to 4GB with the same error. System details: * Debian 6.0.7 * Parallels 8 * get.pharo.org/vm from today * Last successful image artifact from sthub Jenkins job ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-dev-Zinc-problem-with-PUT-requests-tp4688705p46… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 14, 2013

Re: [Pharo-dev] Zinc problem with PUT requests

by Sean P. DeNigris

Sean P. DeNigris wrote > WAKom startOn: 8080. Update: after installing Seaside-Adaptors-Comanche-lr.70, I get an undefined HttpService... If I go back to Zinc, after creating a user, when I try to log in I get "Error: Not enough space for external objects, set a larger size at startup!" ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-dev-Zinc-problem-with-PUT-requests-tp4688705p46… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 14, 2013

Re: [Pharo-dev] Zinc problem with PUT requests

by Sean P. DeNigris

Nicolas Petton wrote > Thanks sven, I'll try it later today. > > On May 21, 2013, at 1:01 PM, Sven Van Caekenberghe < > sven@ > > wrote: >> The problem you reported can easily be fixed by loading the latest >> version of Zinc-Seaaside (the one in the StHub image is very old). Now, >> it still does not fully work, but I don't understand all the Sh and MA >> stuff, I am afraid. Bump. What's the status? The instructions on Jenkins [1] still say: WAKom startOn: 8080. "you could use Zinc, but there seems to be a bug with PUT requests (ZnZincServerAdaptor startOn: 8080)" However WAKom is not included in the build artifact. [1] https://ci.inria.fr/pharo-contribution/job/SmalltalkHub ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-dev-Zinc-problem-with-PUT-requests-tp4688705p46… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 14, 2013

Re: [Pharo-dev] [BUG]: Extension Methods Missing from Packages

by Sean P. DeNigris

This bug is a major PITA. Pleeeeease review and integrate the fixes!!! ----- Cheers, Sean -- View this message in context: http://forum.world.st/BUG-Extension-Methods-Missing-from-Packages-tp4692842… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 14, 2013

Re: [Pharo-dev] Hosting your own SmalltlakHub: turning off/on the web

by Mariano Martinez Peck

On Thu, Jun 13, 2013 at 7:14 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Anyone? > I really need to disable the smalltalkhub frontend and let running the MC > serving part. > Any ideas? > > Thanks > > > On Mon, Jun 3, 2013 at 9:08 AM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> >> >> >> On Fri, May 31, 2013 at 11:39 AM, Mariano Martinez Peck < >> marianopeck(a)gmail.com> wrote: >> >>> Hi Nico, >>> >>> First, let me say that without a lot of pain, I have my own (actually, >>> its for a client) SmalltalkHub instance running with Pharo 2.0, mongoDB, >>> nginx and HTTPS :) >>> >>> Usually we need the web interface quite infrequently, that is, when we >>> create a new user or a new project. So I would like to turn off the website >>> for most of the time and just turn it on when I need something like that. >>> Of course when I mean turn off the website I mean that: only the website. >>> Monticello should continue working :) >>> >>> One "solution" I found is that since I have nginx listening in an SSL >>> port and then this is forwarded to the port zinc is listening, I can just >>> turn off nginx. That way noone can reach the website from outside... but >>> maybe there is a better solution... >>> >>> >> Of course this doesn't actually help because when I turn off nginx I not >> only turn off the website but also the "monticello server" part :( >> Any ideas? >> >> >> >>> Thanks! >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >>> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > > > -- > Mariano > http://marianopeck.wordpress.com > -- Mariano http://marianopeck.wordpress.com

June 13, 2013

Re: [Pharo-dev] Modification on CollectionsExtensions

by Sean P. DeNigris

Tudor Girba-2 wrote > We will release Moose at the end of this month and we will move to Pharo > 3.0 I'm impressed! Did you move Moose to Pharo 2.0 before it was released? I have been hesitant to move my projects to the alpha/beta versions because we are making so much progress (i.e. breaking things, lol)... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-dev-Modification-on-CollectionsExtensions-tp469… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 13, 2013

Re: [Pharo-dev] Modification on CollectionsExtensions

by Tudor Girba

First, thanks for looking at CollectionsExtensions. But, please do not remove flatCollect: yet! This is used everywhere in Moose. We will release Moose at the end of this month and we will move to Pharo 3.0, and then we can do what we want. Doru -- www.tudorgirba.com "Every thing has its own flow." On 12.06.2013, at 17:41, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > but pay attention because in 2.0 you will need it. > :) > > On Jun 12, 2013, at 4:13 PM, Guillaume Larcheveque <guillaume.larcheveque(a)gmail.com> wrote: > >> Ok so if everyone agree I will remove the flatCollect: method from CollectionExtensions since Sebastian made the correction in Pharo 3.0. >> >> >> 2013/6/12 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>> >>> On Jun 12, 2013, at 1:02 PM, Sebastian Tleye <stleye(a)gmail.com> wrote: >>> >>>> ok, i understood, >>>> >>>> Discussing with Marcus we believe that it would be better to keep Collecition>>gather: and add Collection>>flatCollect: (with the same implementation) and put a comment in gather: saying that is kept for compatibility purposes. >>>> >>>> flatCollect: will be included in Pharo and will be removed from CollectionExtensions. >>> >>> + 1 >>> >> >> >> >> -- >> Guillaume Larcheveque >

June 13, 2013

Jenkins build is back to stable : Pharo-2.0-Tests Â» run 1,vm,linux #250

by no-reply＠ci.inria.fr

See <https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/./Run=run%201,VM=vm,label=lin…>

June 13, 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=li… 1 regressions found. NetworkTests.Kernel.NetNameResolverTest.testLocalHostName

June 13, 2013