April 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Fixes to the SqueakSSL Plugin

by Ron Teitelbaum

Hi Tobias, I've ported squeakssl over to github. Did you want access to the repo at: https://github.com/itsmeront/squeakssl/ You could create a Pharo branch there. All the best, Ron Teitelbaum -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Tobias Pape Sent: Tuesday, April 21, 2015 11:00 AM To: The general-purpose Squeak developers list; Squeak Virtual Machine Development Discussion; Pharo Development List; metacello(a)googlegroups.com Subject: [Pharo-dev] Fixes to the SqueakSSL Plugin Dear Smalltalkers Starting with Levente Uzonyi's patches to the Linux version of the SqueakSSL-Plugin, we (Marcel Taeumel and me) have ported this to the OS X and Windows version as well. Find three binaries[1] that can be used instead of the ones found on versions found on SqueakSSL's google code page. SqueakSSL: - x86 32bit Linux ELF dynamic library - Contains Levente's SNI feature - needs SqueakSSL-ul.29 or equivalent for SNI support - can work without. - NOT linked against OpenSSL, but _statically_ linked against LibreSSL 2.1.6 [2]. - It should work on older and newer Debian/Ubuntu as well as on CentOS/RedHat/SuSE systems. SqueakSSL.dll - x86 32bit Windows dll (built with Visual Studio 2013) - Uses Schannel API - SNI Support - needs SqueakSSL-ul.29 or equivalent for SNI support - can work without. - setting an Int property via sqSetIntPropertySSL(...) - Unicode problems when extracting the correct peerName in sqExtractPeerName SqueakSSL.bundle - x86 32bit OS X Mach-O dylib (Linked against OS X 10.5 SDK) - Uses Security-Framework - SNI Support - needs SqueakSSL-ul.29 or equivalent for SNI support - can work without. ---------------------------------------------------------------------------- ----- The changes necessary for Windows and OS X are not yet available in the squeakvm svn, the linux ones are. I have not yet found a good way to include the static linking in either the way the Autoconf works for Cog or CMake works for the interpreter, but I'll follow-up to this. ---------------------------------------------------------------------------- ---- Best regards -Tobias [1]: http://forum.world.st/file/n4820846/squeakssl.zip [2]: http://www.libressl.org/

April 21, 2015

Re: [Pharo-dev] missing packages in the Pharo50 repository

by Esteban Lorenzano

> On 21 Apr 2015, at 16:39, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > However I think that repositories of this project should be in the > list of default repositories. Maybe we should add copy of the > configurations to the Pharo50 repository too. yes, I agree

April 21, 2015

Fixes to the SqueakSSL Plugin

by Tobias Pape

Dear Smalltalkers Starting with Levente Uzonyi's patches to the Linux version of the SqueakSSL-Plugin, we (Marcel Taeumel and me) have ported this to the OS X and Windows version as well. Find three binaries[1] that can be used instead of the ones found on versions found on SqueakSSL's google code page. SqueakSSL: - x86 32bit Linux ELF dynamic library - Contains Levente's SNI feature - needs SqueakSSL-ul.29 or equivalent for SNI support - can work without. - NOT linked against OpenSSL, but _statically_ linked against LibreSSL 2.1.6 [2]. - It should work on older and newer Debian/Ubuntu as well as on CentOS/RedHat/SuSE systems. SqueakSSL.dll - x86 32bit Windows dll (built with Visual Studio 2013) - Uses Schannel API - SNI Support - needs SqueakSSL-ul.29 or equivalent for SNI support - can work without. - setting an Int property via sqSetIntPropertySSL(...) - Unicode problems when extracting the correct peerName in sqExtractPeerName SqueakSSL.bundle - x86 32bit OS X Mach-O dylib (Linked against OS X 10.5 SDK) - Uses Security-Framework - SNI Support - needs SqueakSSL-ul.29 or equivalent for SNI support - can work without. --------------------------------------------------------------------------------- The changes necessary for Windows and OS X are not yet available in the squeakvm svn, the linux ones are. I have not yet found a good way to include the static linking in either the way the Autoconf works for Cog or CMake works for the interpreter, but I'll follow-up to this. -------------------------------------------------------------------------------- Best regards -Tobias [1]: http://forum.world.st/file/n4820846/squeakssl.zip [2]: http://www.libressl.org/

April 21, 2015

Re: [Pharo-dev] Fwd: exception handling problem when running tests in Nautilus

by Christophe Demarey

Le 21 avr. 2015 Ã 16:32, Otto Behrens a Ã©crit : > Thanks. I do <alt>jc on a method sometimes when I have changed a > method. So sometimes I so <alt>jm and then immediately <alt>jc to > check all the tests in the class. > >> Indeed, Nautilus logic to run test differs a bit from the TestRunner logic. > > Does it really have to be? No, it should not. >> For example, if your test fails, it is run a second time to open a debugger but it could do side effects. > > This has been a problem for me for a long time. I would *love* it if > Nautilus runs a single test in debug mode (and not a second time). It > is especially painful when running selenium tests in our environment, > because firefox is launched on every test suite run, which makes > running a single test relatively expensive. I suppose solving the > problem of tests running a long time is first prize. > >> Why don't you just run your tests from the test runner or using MyTestClass run: #testSelector ? > > Because I normally run the tests that I work on while I'm in the > Nautilus browser (using shortcut keys). Why would I want to launch a > different browser, search for the class I'm working on and run the > tests there? It was a suggestion for your use case. If you only want to run the test you are working on, Nautilus helps. > I could be missing it totally here. I'm quite interested to know how > other people work. A sort of work flow, to the point of running tests. We miss a functionality in Pharo to easily run (a shorcut) a set of selected tests (ex: your project tests). This way, you can have a quick feedback on your updates. As it is not so easy, I often fallback to run tests from Nautilus (a test class or sometimes only a test method). > To run all my tests take a long time. There are quite a few. > >> We will need to clean this kind of logic that should not be part of Nautilus. Could you open a bug entry for that? > > https://pharo.fogbugz.com/f/cases/15374/exception-handling-when-running-tes… Yes.

April 21, 2015

Re: [Pharo-dev] Interrupt a locked pharo image from outside

by Thierry Goubier

Thanks, that works... now to make sense of all the debug stuff coming out ;) Thierry 2015-04-21 16:47 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > You may use: > > kill -USR1 <pid> > > Cheers, > -- Pavel > > > > 2015-04-21 16:36 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > > Hi all, > > > > anybody knows if it would be possible to generate an external > interruption > > (a signal) from outside the Pharo process which would trigger a Ctrl+. > > interrupt? > > > > OSProcess 4.5.13 has a tendancy to lock the image on some linux systems > > (ubuntu 14.10 at least), and it would be nice to be able to interrupt it > to > > be able to see where it is blocked. > > > > "killall pharo" or Ctrl+C does not give much information :( > > > > Thanks, > > > > Thierry > >

April 21, 2015

Re: [Pharo-dev] Interrupt a locked pharo image from outside

by Pavel Krivanek

You may use: kill -USR1 <pid> Cheers, -- Pavel 2015-04-21 16:36 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > Hi all, > > anybody knows if it would be possible to generate an external interruption > (a signal) from outside the Pharo process which would trigger a Ctrl+. > interrupt? > > OSProcess 4.5.13 has a tendancy to lock the image on some linux systems > (ubuntu 14.10 at least), and it would be nice to be able to interrupt it to > be able to see where it is blocked. > > "killall pharo" or Ctrl+C does not give much information :( > > Thanks, > > Thierry

April 21, 2015

Re: [Pharo-dev] missing packages in the Pharo50 repository

by Pavel Krivanek

2015-04-21 15:21 GMT+02:00 stepharo <stepharo(a)free.fr>: > @esteban Pavel is not stupid. So we could ask him what are his scenarios. > > @Pavel So pavel can you explain what and why you need? > > And yes we will have to have another level of tooling because > now it can be really difficult I simply wanted to make a local Pharo FileTree repository to have a free hands for testing of system configurations. Something like a personal Pharo fork. The fact that this packages are all missing because they are already handled by configurations is welcomed information. However I think that repositories of this project should be in the list of default repositories. Maybe we should add copy of the configurations to the Pharo50 repository too. Cheers, -- Pavel > > @esteban > we should add the repositories to the projects because we should be able to > publish > in this repositories. Else it will be again the time of the guy fixing a > problem that will be consumed. > > Or we can also simply say to people that we do not care of their time, but I > would prefer that we pay attention. > In that case this is simple for me I will not fix or even look at code that > is not in the > main system and with this approach we will all have lost something. > > > Stef >

April 21, 2015

Interrupt a locked pharo image from outside

by Thierry Goubier

Hi all, anybody knows if it would be possible to generate an external interruption (a signal) from outside the Pharo process which would trigger a Ctrl+. interrupt? OSProcess 4.5.13 has a tendancy to lock the image on some linux systems (ubuntu 14.10 at least), and it would be nice to be able to interrupt it to be able to see where it is blocked. "killall pharo" or Ctrl+C does not give much information :( Thanks, Thierry

April 21, 2015

Re: [Pharo-dev] Fwd: exception handling problem when running tests in Nautilus

by Otto Behrens

Thanks. I do <alt>jc on a method sometimes when I have changed a method. So sometimes I so <alt>jm and then immediately <alt>jc to check all the tests in the class. > Indeed, Nautilus logic to run test differs a bit from the TestRunner logic. Does it really have to be? > For example, if your test fails, it is run a second time to open a debugger but it could do side effects. This has been a problem for me for a long time. I would *love* it if Nautilus runs a single test in debug mode (and not a second time). It is especially painful when running selenium tests in our environment, because firefox is launched on every test suite run, which makes running a single test relatively expensive. I suppose solving the problem of tests running a long time is first prize. > Why don't you just run your tests from the test runner or using MyTestClass run: #testSelector ? Because I normally run the tests that I work on while I'm in the Nautilus browser (using shortcut keys). Why would I want to launch a different browser, search for the class I'm working on and run the tests there? I could be missing it totally here. I'm quite interested to know how other people work. A sort of work flow, to the point of running tests. To run all my tests take a long time. There are quite a few. > We will need to clean this kind of logic that should not be part of Nautilus. Could you open a bug entry for that? https://pharo.fogbugz.com/f/cases/15374/exception-handling-when-running-tes… Is this the right place? > > Regards, > Christophe. > > Le 21 avr. 2015 Ã 15:34, Otto Behrens a Ã©crit : > >> I realised I may have posted this on the wrong list. Is there anyone >> that can help with this one please? >> >> >> ---------- Forwarded message ---------- >> From: Otto Behrens <otto(a)finworks.biz> >> Date: Sun, Apr 19, 2015 at 10:08 AM >> Subject: exception handling problem when running tests in Nautilus >> To: pharo-users(a)lists.pharo.org >> >> >> Hi, >> >> Thanks everyone for the new Pharo and all the work done. I like Spotter! >> >> I gave Pharo 4 a try today and ran into a problem with running tests >> in a TestCase (test class -> run tests). I just get the debugger >> popping up with WARequestContextNotFound. >> >> In the setUp of our test case, we call WACurrentRequestContext value, >> but handle the error when we do not have a context, for example: >> >> [ WACurrentRequestContext value. true ] >> on: WARequestContextNotFound >> do: [ :e | false ] >> >> This handler: "[ :e | false ]" is never called. What influences this >> is the exception handling in: >> >> AbstractNautilusUI >> #runTestsOfClass:notifying: >> >> Firstly, I think that it may be slighly better to call "e pass" or "e >> outer" in stead of "e defaultAction", as this would give another outer >> handler a chance to do something. The defaultAction is called when >> there are no more outer handlers anyway. >> >> After trying this, it did not help my cause. And I think that this is >> because the WACurrentRequestContext is a Notification and not an >> Error. >> >> I then replaced Exception with Error in the handler in >> AbstractNautilusUI. This seem to work. What also works is to >> completely remove the exception handling in AbstractNautilusUI >> >> #runTestsOfClass:notifying: >> >> What is a bit strange is the inconsistency in this exception handling >> when running a suite or an individual test. Perhaps this kind of code >> could be better on the TestSuite and not in the Nautilus UI? >> >> Can anyone please help? Should I be doing something else? >> >> Cheers >> Otto >> >

April 21, 2015

Re: [Pharo-dev] Fwd: exception handling problem when running tests in Nautilus

by Nicolai Hess

2015-04-21 16:03 GMT+02:00 Christophe Demarey <Christophe.Demarey(a)inria.fr>: > Indeed, Nautilus logic to run test differs a bit from the TestRunner logic. > > We will need to clean this kind of logic that should not be part of > Nautilus. > Just for reference: 13024 <https://pharo.fogbugz.com/default.asp?13024> Discrepancy between TestRunner and Nautilus test running for method #shouldNotImplementMethod 14864 <https://pharo.fogbugz.com/default.asp?14864> Nautillus do not launch the test cases on some classes 12851 <https://pharo.fogbugz.com/default.asp?12851> Test is executed twice when failling > > Regards, > Christophe. > > Le 21 avr. 2015 Ã 15:34, Otto Behrens a Ã©crit : > > > I realised I may have posted this on the wrong list. Is there anyone > > that can help with this one please? > > > > > > ---------- Forwarded message ---------- > > From: Otto Behrens <otto(a)finworks.biz> > > Date: Sun, Apr 19, 2015 at 10:08 AM > > Subject: exception handling problem when running tests in Nautilus > > To: pharo-users(a)lists.pharo.org > > > > > > Hi, > > > > Thanks everyone for the new Pharo and all the work done. I like Spotter! > > > > I gave Pharo 4 a try today and ran into a problem with running tests > > in a TestCase (test class -> run tests). I just get the debugger > > popping up with WARequestContextNotFound. > > > > In the setUp of our test case, we call WACurrentRequestContext value, > > but handle the error when we do not have a context, for example: > > > > [ WACurrentRequestContext value. true ] > > on: WARequestContextNotFound > > do: [ :e | false ] > > > > This handler: "[ :e | false ]" is never called. What influences this > > is the exception handling in: > > > > AbstractNautilusUI >> #runTestsOfClass:notifying: > > > > Firstly, I think that it may be slighly better to call "e pass" or "e > > outer" in stead of "e defaultAction", as this would give another outer > > handler a chance to do something. The defaultAction is called when > > there are no more outer handlers anyway. > > > > After trying this, it did not help my cause. And I think that this is > > because the WACurrentRequestContext is a Notification and not an > > Error. > > > > I then replaced Exception with Error in the handler in > > AbstractNautilusUI. This seem to work. What also works is to > > completely remove the exception handling in AbstractNautilusUI >> > > #runTestsOfClass:notifying: > > > > What is a bit strange is the inconsistency in this exception handling > > when running a suite or an individual test. Perhaps this kind of code > > could be better on the TestSuite and not in the Nautilus UI? > > > > Can anyone please help? Should I be doing something else? > > > > Cheers > > Otto > > > >

April 21, 2015