November 2017 - Pharo-users

Re: [Pharo-users] P3 timeout

by Sven Van Caekenberghe

Hi Pierce, Thanks for the feedback. Yes, I did run into the timeout issue for heavy queries myself as well. I was already planning to add this option. https://github.com/svenvc/P3/commit/ce68fd206b47c0411b75f0992ef4f4e119eb4ff1 Added P3Client>>#timeout[:] option (thx Pierce Ng) Added P3ClientTests>>#testTimeout Refactored host/port/user/password/database into properties Now you can do the following: P3ClientTests>>#testTimeout "Reconnect with an explicit timeout" client close. client url: url. client timeout: 1. "second" self assert: client isWorking. "The following (sleeping for 0.5 seconds) should just pass successfully" client execute: 'SELECT pg_sleep(0.5)'. "While the following (sleeping for 1.5 seconds) should time out" self should: [ client execute: 'SELECT pg_sleep(1.5)' ] raise: ConnectionTimedOut About Zdc streams. They have their own default timeout (5 seconds). I think it is not a good idea to have global timeout setting, these should be done per actual (client) instance. I like relatively short timeouts, so that I get faster feedback. BTW, I am also interested in your experience using P3. How did it go ? Sven > On 26 Nov 2017, at 09:43, Pierce Ng <pierce(a)samadhiweb.com> wrote: > > Hi Sven and all, > > I have a PostgreSQL database running in a resource-light Linux VM with ~4 > million rows consisting of mostly text. My query executes regexp_matches() on > the text and it runs noticeably slowly. > > I am encountering ConnectionTimedOut using P3 to run my query. PostgresV2 and > Python's pg8000 do work though. I see that PostgresV2's PGConnection uses > "Socket standardTimeout". I changed ZdcSimpleSocketStream class-side's > #openConnectionToHostNamed:port: bottom part to add the same timeout because > P3Client>>open calls it: > > ZdcSimpleSocketStream class>>openConnectionToHostNamed: hostName port: portNumber > [...] > ^ socketStream > timeout: Socket standardTimeOut; "<== added this line" > connectTo: hostIP port: portNumber; > yourself > > Now my query returns instead of timing out. > > It does look like ZdcSimpleSocketStream's three class-side methods could use > some refactoring love. > > Pierce >

Nov. 26, 2017

Re: [Pharo-users] Pharo-users Digest, Vol 55, Issue 206

by Ben Coman

On 26 November 2017 at 21:28, Herby VojÄÃk <herby(a)mailbox.sk> wrote: > Ben Coman wrote: > >> >> >> On 25 November 2017 at 15:18, ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð² >> <vikenti.potapov(a)gmail.com <mailto:vikenti.potapov@gmail.com>> wrote: >> >> >> I downloaded the latest PharoLauncher image, use VM for Pharo 6.1. >> 1) On load i got an error with UTF8 encoding. >> 2) Every time i tried to create image (for example, Pharo 7 image) i >> get an error "Can't find the requested origin". >> >> Reported. >> >> Best regards, Vikenti Potapov >> >> >> The overall difficulty here in getting this addressed is difficulty in >> reproducing your environment. >> For example, I think it would be awkward for me to operate with OS >> locale set to Russian. >> You'll see little action on it until there is an Issue logged at >> pharo.fogbugz.com <http://pharo.fogbugz.com/> with a simple set of steps >> to reproduced for standard environments (i.e. using English locales) >> >> Reviewing your other posts, I'd suggest initially creating a script to >> wrap Pharo startup that cleans all the environment variables to ascii >> > > -1. > > It should all work in other locales. Maybe you should set some if not all > of the jenkins jobs under different locales (at least russian and japanese) > to catch those things fast. > > Your (I hate to use the word) privilege to be fine with ASCII only > actually masks lot of bugs from you. I think you misunderstand me. This suggestion was only to help isolate the problem during troubleshooting. The best way to troubleshoot something is to a.) start with something working and then b.) be able to reliability break it. Vikenti doesn't have (a.) so I was giving him a hack to get that, to be able to proceed to (b.) But your suggestion to the running some CI jobs under different locals and timezones could be useful. cheers -ben > > Herby > > P.S.: Other masking thing is the timezone which is UTC in case of UK, > France and lot of the rest of Western Europe. That should also be set to. > say, Sydney and Honolulu to get big GMT+ and GMT- shifts. > > > characters, temporarily creating required directories so at lest you can >> get it started. Then extend that script to reintroduce the error, like >> a single non-ascii character in a single environment variable that >> causes an error. That extended part then provides a path for others to >> reproduce your problem, which you would attach to the Issue. Then as >> you investigate a solution yourself, ask questions about it on pharo-dev >> to keep the Issue active and over time you'll likely get some action >> from others on it. >> >> cheers -ben >> >> >> >> > >

Nov. 26, 2017

Re: [Pharo-users] Pharo-users Digest, Vol 55, Issue 207

by Ben Coman

On 26 November 2017 at 20:57, ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð² <vikenti.potapov(a)gmail.com> wrote: > > I will be glad to help to find solution with this problem that started > with later versions of Pharo 6. > While Pharo has such problems - it is not production-ready. > > Just point me from where to start my investigation of code. > > --- The full stack --- > WindowsResolver(PlatformResolver)>>cantFindOriginError > [ self cantFindOriginError ] in WindowsResolver(PlatformResolver)>> > directoryFromEnvVariableNamed: > [ ^ arg2 value ] in WindowsResolver(PlatformResolver)>> > directoryFromEnvVariableNamed:or: > BlockClosure>>cull: > Context>>evaluateSignal: > Context>>handleSignal: > PrimitiveFailed(Exception)>>signal > PrimitiveFailed class(SelectorException class)>>signalFor: > Win32Environment(Object)>>primitiveFailed: > Win32Environment(Object)>>primitiveFailed > Win32Environment(Object)>>primitiveFail > Win32Environment(OSEnvironment)>>getEnv: > Win32Environment>>getEnv: > Win32Environment(OSEnvironment)>>at:ifAbsent: > [ Smalltalk os environment at: arg1 ifAbsent: [ ] ] in WindowsResolver( > PlatformResolver)>>directoryFromEnvVariableNamed:or: > BlockClosure>>on:do: > WindowsResolver(PlatformResolver)>>directoryFromEnvVariableNamed:or: > WindowsResolver(PlatformResolver)>>directoryFromEnvVariableNamed: > WindowsResolver>>home > WindowsResolver>>documents > Well I see... WindowsResolver>>home "Value of the $USERPROFILE environment variable." ^ self directoryFromEnvVariableNamed: 'USERPROFILE' Win32Environment(OSEnvironment)>>getEnv: "This method calls the Standard C Library getenv() function." <primitive: 'primitiveGetenv' module: '' error: ec> You can see that implementation by searching for "primitiveGetenv(void)" at... * https://raw.githubusercontent.com/OpenSmalltalk/opensmalltalk-vm/Cog/spursr… where I guess that "var<--'USERPROFILE'" So are you able to compile, run and report with this small C program... int main() { char *result; char *var = "USERPROFILE"; result = getenv(var); if (result != 0) { printf("SUCCESS"); } else { printf("FAILED"); } } Experiment with: * different env vars holding either unicode or non-unicode characters. * https://msdn.microsoft.com/en-us/library/tehxacec.aspx cheers -ben > > > The overall difficulty here in getting this addressed is difficulty in > > reproducing your environment. > > For example, I think it would be awkward for me to operate with OS locale > > set to Russian. > > You'll see little action on it until there is an Issue logged at > > pharo.fogbugz.com with a simple set of steps to reproduced for standard > > environments (i.e. using English locales) > > > > Reviewing your other posts, I'd suggest initially creating a script to > wrap > > Pharo startup that cleans all the environment variables to ascii > > characters, temporarily creating required directories so at lest you can > > get it started. Then extend that script to reintroduce the error, like a > > single non-ascii character in a single environment variable that causes > an > > error. That extended part then provides a path for others to reproduce > > your problem, which you would attach to the Issue. Then as you > > investigate a solution yourself, ask questions about it on pharo-dev to > > keep the Issue active and over time you'll likely get some action from > > others on it. > > > > cheers -ben > > >

Nov. 26, 2017

Re: [Pharo-users] How do you store and manage small programs?

by Ben Coman

On 26 November 2017 at 20:36, Norbert Hartl <norbert(a)hartl.name> wrote: > Andy, > > I use the filesystem for it. Letâs say you have a directory called > âscriptsâ. If you inspect > > âscriptsâ asFileReference > nice trick cheers -ben > > you get kind of a browser of the files in there. If the have the file > extension .st syntax highlighting is enabled if you look at it. You can > create new scripts there,too. > I like that the most because the scripts are not in the image anymore and > the probability to loose them is lower. > > I have a scripts folder in my home directory (global) and one in the > project folder (project specific). And inspectors to bith location are > opened by the script that prepares a new image. > > Norbert > > > Am 25.11.2017 um 18:34 schrieb Andy Burnett < > andy.burnett(a)knowinnovation.com>: > > > > I have just created a couple of small playground scripts that do some > useful data wrangling. The chances are that I will reuse them from time to > time, but with tweaks. Does version 6 Have some way to store them? I think > I am after a sort of scripts catalogue. > >

Nov. 26, 2017

Re: [Pharo-users] Pharo-users Digest, Vol 55, Issue 206

by Herby VojÄÃk

Ben Coman wrote: > > > On 25 November 2017 at 15:18, ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð² > <vikenti.potapov(a)gmail.com <mailto:vikenti.potapov@gmail.com>> wrote: > > > I downloaded the latest PharoLauncher image, use VM for Pharo 6.1. > 1) On load i got an error with UTF8 encoding. > 2) Every time i tried to create image (for example, Pharo 7 image) i > get an error "Can't find the requested origin". > > Reported. > > Best regards, Vikenti Potapov > > > The overall difficulty here in getting this addressed is difficulty in > reproducing your environment. > For example, I think it would be awkward for me to operate with OS > locale set to Russian. > You'll see little action on it until there is an Issue logged at > pharo.fogbugz.com <http://pharo.fogbugz.com/> with a simple set of steps > to reproduced for standard environments (i.e. using English locales) > > Reviewing your other posts, I'd suggest initially creating a script to > wrap Pharo startup that cleans all the environment variables to ascii -1. It should all work in other locales. Maybe you should set some if not all of the jenkins jobs under different locales (at least russian and japanese) to catch those things fast. Your (I hate to use the word) privilege to be fine with ASCII only actually masks lot of bugs from you. Herby P.S.: Other masking thing is the timezone which is UTC in case of UK, France and lot of the rest of Western Europe. That should also be set to. say, Sydney and Honolulu to get big GMT+ and GMT- shifts. > characters, temporarily creating required directories so at lest you can > get it started. Then extend that script to reintroduce the error, like > a single non-ascii character in a single environment variable that > causes an error. That extended part then provides a path for others to > reproduce your problem, which you would attach to the Issue. Then as > you investigate a solution yourself, ask questions about it on pharo-dev > to keep the Issue active and over time you'll likely get some action > from others on it. > > cheers -ben > > >

Nov. 26, 2017

Re: [Pharo-users] Pharo-users Digest, Vol 55, Issue 206

by Stephane Ducasse

+ 1 On Sat, Nov 25, 2017 at 9:58 AM, Ben Coman <btc(a)openinworld.com> wrote: > > > On 25 November 2017 at 15:18, ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð² <vikenti.potapov(a)gmail.com> > wrote: >> >> >> I downloaded the latest PharoLauncher image, use VM for Pharo 6.1. >> 1) On load i got an error with UTF8 encoding. >> 2) Every time i tried to create image (for example, Pharo 7 image) i get >> an error "Can't find the requested origin". >> >> Reported. >> >> Best regards, Vikenti Potapov >> > > The overall difficulty here in getting this addressed is difficulty in > reproducing your environment. > For example, I think it would be awkward for me to operate with OS locale > set to Russian. > You'll see little action on it until there is an Issue logged at > pharo.fogbugz.com with a simple set of steps to reproduced for standard > environments (i.e. using English locales) > > Reviewing your other posts, I'd suggest initially creating a script to wrap > Pharo startup that cleans all the environment variables to ascii characters, > temporarily creating required directories so at lest you can get it started. > Then extend that script to reintroduce the error, like a single non-ascii > character in a single environment variable that causes an error. That > extended part then provides a path for others to reproduce your problem, > which you would attach to the Issue. Then as you investigate a solution > yourself, ask questions about it on pharo-dev to keep the Issue active and > over time you'll likely get some action from others on it. > > cheers -ben > > >

Nov. 26, 2017

Re: [Pharo-users] I love the launcher!!!!

by Herby VojÄÃk

Stephane Ducasse wrote: > Then do not try :) like that you will never get a chance to know :) Could you please explain? I understood your sentence has high dose of homour which I cannot decipher since I lack certain abilities for that. Thanks, Herby > Stef > > > On Sun, Nov 26, 2017 at 1:48 PM, Herby VojÄÃk<herby(a)mailbox.sk> wrote: >> Stephane Ducasse wrote: >>> Why don't you try? It does not bite. >>> >>> For me it works in all scenario. I have projects that i manage over >>> several weeks and others I drop day to day. >>> And I have also startup script per versions. >> >> Maybe I will. The main problem was I didn't what it's good about at all - >> load image for a version, runs it - what's the "wow it's great" about? >> Missed part was it loads correct vm; plus makes sense when you have hundreds >> (I don't). Now it must be combined with the startup script magic to work >> with long-time projects, but those are also new to me - did not know of them >> until your booklet, not using them at all yet. >> >> Herby >> >> >>> Stef >>> >>> On Fri, Nov 24, 2017 at 3:10 PM, Herby VojÄÃk<herby(a)mailbox.sk> wrote: >>>> Thank you all, now I understand it better. Good for lots of "branches". >>>> >>>> However, I wonder how does it work with the rule I read somewhere: "start >>>> each day [of work on a project] with a new image", which means I should >>>> not >>>> reuse clean new image (as it needs populating from VCSes etc.) nor reuse >>>> existing image (I should start with the new one). Or does it combine with >>>> some startup-magic described in one of the recent Steph's booklets, the >>>> "one >>>> start per [new] image" case (but again, one should discriminate projects >>>> from each other)? >>>> >>>> Thanks, Herby >>>> >>>> Peter UhnÃ¡k wrote: >>>>> Hi Herby, >>>>> >>>>> normally people use different images for their different projects, >>>>> different versions, trying things, etc. Which means we end up with many >>>>> locations on disk, and it can be hard to track. >>>>> So PharoLauncher is a nice tool where you can download fresh image just >>>>> by clicking, and you see the list of your local images and can launch >>>>> them, etc. >>>>> >>>>> Peter >>>>> >>>>> On Thu, Nov 23, 2017 at 12:56 PM, Herby VojÄÃk<herby(a)mailbox.sk >>>>> <mailto:herby@mailbox.sk>> wrote: >>>>> >>>>> Stephane Ducasse wrote: >>>>> >>>>> Hi >>>>> >>>>> I love the PharoLauncher. >>>>> >>>>> >>>>> Pardon my question, I have downloaded it and looked at it, but I >>>>> don't get it. What does it do / what are the use cases (honest >>>>> question)? >>>>> >>>>> Thanks, Herby >>>>> >>>>> >>>>> It helps me to manage my parallel development and projects. >>>>> >>>>> We should put a link on the Pharo web site because >>>>> >>>>> http://files.pharo.org/platform/launcher/ >>>>> <http://files.pharo.org/platform/launcher/> >>>>> >>>>> is arcane. >>>>> >>>>> Stef >>>>> >>>>> >>>>> >>>>> >> >

Nov. 26, 2017

Re: [Pharo-users] P3 timeout

by Stephane Ducasse

Hi Pierce It would be cool if we could get a little success stories around what you are doing. A success stories does not mean that you get as rich as Steve Jobs, just that you build something nice successfully. ;) Stef On Sun, Nov 26, 2017 at 9:43 AM, Pierce Ng <pierce(a)samadhiweb.com> wrote: > Hi Sven and all, > > I have a PostgreSQL database running in a resource-light Linux VM with ~4 > million rows consisting of mostly text. My query executes regexp_matches() on > the text and it runs noticeably slowly. > > I am encountering ConnectionTimedOut using P3 to run my query. PostgresV2 and > Python's pg8000 do work though. I see that PostgresV2's PGConnection uses > "Socket standardTimeout". I changed ZdcSimpleSocketStream class-side's > #openConnectionToHostNamed:port: bottom part to add the same timeout because > P3Client>>open calls it: > > ZdcSimpleSocketStream class>>openConnectionToHostNamed: hostName port: portNumber > [...] > ^ socketStream > timeout: Socket standardTimeOut; "<== added this line" > connectTo: hostIP port: portNumber; > yourself > > Now my query returns instead of timing out. > > It does look like ZdcSimpleSocketStream's three class-side methods could use > some refactoring love. > > Pierce >

Nov. 26, 2017

Re: [Pharo-users] I love the launcher!!!!

by Stephane Ducasse

Then do not try :) like that you will never get a chance to know :) Stef On Sun, Nov 26, 2017 at 1:48 PM, Herby VojÄÃk <herby(a)mailbox.sk> wrote: > Stephane Ducasse wrote: >> >> Why don't you try? It does not bite. >> >> For me it works in all scenario. I have projects that i manage over >> several weeks and others I drop day to day. >> And I have also startup script per versions. > > > Maybe I will. The main problem was I didn't what it's good about at all - > load image for a version, runs it - what's the "wow it's great" about? > Missed part was it loads correct vm; plus makes sense when you have hundreds > (I don't). Now it must be combined with the startup script magic to work > with long-time projects, but those are also new to me - did not know of them > until your booklet, not using them at all yet. > > Herby > > >> Stef >> >> On Fri, Nov 24, 2017 at 3:10 PM, Herby VojÄÃk<herby(a)mailbox.sk> wrote: >>> >>> Thank you all, now I understand it better. Good for lots of "branches". >>> >>> However, I wonder how does it work with the rule I read somewhere: "start >>> each day [of work on a project] with a new image", which means I should >>> not >>> reuse clean new image (as it needs populating from VCSes etc.) nor reuse >>> existing image (I should start with the new one). Or does it combine with >>> some startup-magic described in one of the recent Steph's booklets, the >>> "one >>> start per [new] image" case (but again, one should discriminate projects >>> from each other)? >>> >>> Thanks, Herby >>> >>> Peter UhnÃ¡k wrote: >>>> >>>> Hi Herby, >>>> >>>> normally people use different images for their different projects, >>>> different versions, trying things, etc. Which means we end up with many >>>> locations on disk, and it can be hard to track. >>>> So PharoLauncher is a nice tool where you can download fresh image just >>>> by clicking, and you see the list of your local images and can launch >>>> them, etc. >>>> >>>> Peter >>>> >>>> On Thu, Nov 23, 2017 at 12:56 PM, Herby VojÄÃk<herby(a)mailbox.sk >>>> <mailto:herby@mailbox.sk>> wrote: >>>> >>>> Stephane Ducasse wrote: >>>> >>>> Hi >>>> >>>> I love the PharoLauncher. >>>> >>>> >>>> Pardon my question, I have downloaded it and looked at it, but I >>>> don't get it. What does it do / what are the use cases (honest >>>> question)? >>>> >>>> Thanks, Herby >>>> >>>> >>>> It helps me to manage my parallel development and projects. >>>> >>>> We should put a link on the Pharo web site because >>>> >>>> http://files.pharo.org/platform/launcher/ >>>> <http://files.pharo.org/platform/launcher/> >>>> >>>> is arcane. >>>> >>>> Stef >>>> >>>> >>>> >>>> >>> >> > >

Nov. 26, 2017

Re: [Pharo-users] Pharo-users Digest, Vol 55, Issue 207

by ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð²

I will be glad to help to find solution with this problem that started with later versions of Pharo 6. While Pharo has such problems - it is not production-ready. Just point me from where to start my investigation of code. --- The full stack --- WindowsResolver(PlatformResolver)>>cantFindOriginError [ self cantFindOriginError ] in WindowsResolver(PlatformResolver)>>directoryFromEnvVariableNamed: [ ^ arg2 value ] in WindowsResolver(PlatformResolver)>>directoryFromEnvVariableNamed:or: BlockClosure>>cull: Context>>evaluateSignal: Context>>handleSignal: PrimitiveFailed(Exception)>>signal PrimitiveFailed class(SelectorException class)>>signalFor: Win32Environment(Object)>>primitiveFailed: Win32Environment(Object)>>primitiveFailed Win32Environment(Object)>>primitiveFail Win32Environment(OSEnvironment)>>getEnv: Win32Environment>>getEnv: Win32Environment(OSEnvironment)>>at:ifAbsent: [ Smalltalk os environment at: arg1 ifAbsent: [ ] ] in WindowsResolver(PlatformResolver)>>directoryFromEnvVariableNamed:or: BlockClosure>>on:do: WindowsResolver(PlatformResolver)>>directoryFromEnvVariableNamed:or: WindowsResolver(PlatformResolver)>>directoryFromEnvVariableNamed: WindowsResolver>>home WindowsResolver>>documents The overall difficulty here in getting this addressed is difficulty in > reproducing your environment. > For example, I think it would be awkward for me to operate with OS locale > set to Russian. > You'll see little action on it until there is an Issue logged at > pharo.fogbugz.com with a simple set of steps to reproduced for standard > environments (i.e. using English locales) > > Reviewing your other posts, I'd suggest initially creating a script to wrap > Pharo startup that cleans all the environment variables to ascii > characters, temporarily creating required directories so at lest you can > get it started. Then extend that script to reintroduce the error, like a > single non-ascii character in a single environment variable that causes an > error. That extended part then provides a path for others to reproduce > your problem, which you would attach to the Issue. Then as you > investigate a solution yourself, ask questions about it on pharo-dev to > keep the Issue active and over time you'll likely get some action from > others on it. > > cheers -ben

Nov. 26, 2017