- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] WhatsUp from: 2014-12-01 until: 2014-12-14

by Sven Van Caekenberghe

Nice ! > On 01 Dec 2014, at 15:01, phil(a)highoctane.be wrote: > > On Mon, Dec 1, 2014 at 7:00 AM, <seaside(a)rmod.lille.inria.fr> wrote: > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: > > Two commercial installs of a Pharo/Seaside based solution. > Some tweets with the #pharo tag. > > > > ### What's next, until 2014-12-14 (*): > > More installs. More deals. > Using Mongodb more extensively for one application. > Start of a new application module on business dashboarding. > Documentation of our system writing using Pillar. > CommandLineHandler based tool for console based administration of the system. > > > > (*) we'll be expecting results by then ;) > >

Dec. 1, 2014

Re: [Pharo-dev] WhatsUp from: 2014-12-01 until: 2014-12-14

by phil＠highoctane.be

On Mon, Dec 1, 2014 at 7:00 AM, <seaside(a)rmod.lille.inria.fr> wrote: > Hi! We're sending this automatic email twice a month, to give the > community an opportunity to easily know what's happening and to coordinate > efforts. Just answer informally, and feel free to spawn discussions > thereafter! > > ### Here's what I've been up to since the last WhatsUp: > Two commercial installs of a Pharo/Seaside based solution. Some tweets with the #pharo tag. > > ### What's next, until 2014-12-14 (*): > More installs. More deals. Using Mongodb more extensively for one application. Start of a new application module on business dashboarding. Documentation of our system writing using Pillar. CommandLineHandler based tool for console based administration of the system. > > (*) we'll be expecting results by then ;) > >

Dec. 1, 2014

Re: [Pharo-dev] tests coverage of minimal Pharo

by Pavel Krivanek

Right. Some tests ended with out-of-memory errors or vm crash. One problem was in a trait so I had to put all users of it on the blacklist. Cheers, -- Pavel 2014-12-01 14:21 GMT+01:00 Alejandro Infante <alejandroinfante91(a)gmail.com>: > Hapao works using method wrappers, and do some stuff for every method > execution. If Hapao use something you are instrumenting, you are start > looping endlessly. So blacklisted classes are classes you are not going to > instrument. > > But, I was trying to understand all the classes you blacklisted, and I donât > understand why you have some tests blacklisted, any reason for them? > > Cheers, > Alejandro > > On Dec 1, 2014, at 7:57 AM, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > ignorant question: What is a black listed class? :) > > On Sun, Nov 30, 2014 at 7:21 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: >> >> Hi, >> >> I set the job for tests coverage testing of the mimimal Pharo using Hapao: >> >> >> https://ci.inria.fr/pharo/view/4.0-Bootstrap/job/Pharo-4.0-Bootstrap-Step-2… >> >> To load results you should load ConfigurationOfSUnit and >> ConfigurationOfKernelTests from Pharo/SystemConfigurations repository >> into an image with Hapao. Then inspect: >> >> FLMaterializer materializeFromFileNamed: 'hapao.fuel'. >> >> Do not try to visualise it ;-) >> >> Currently blacklisted classes are: >> >> Array Association ArrayedCollection Behavior BlockClosure ByteSymbol >> ByteString ClassDescription CompiledMethod Class Dictionary >> Hapao2Package HashedCollection IdentityDictionary Integer LookupKey >> FileStream Magnitude Object ProtoObject Process ProcessLocalVariable >> ProcessorScheduler ProcessSpecificVariable RPackageOrganizer RPackage >> SmalltalkImage SequenceableCollection Set Semaphore SmallInteger >> Symbol String SourceFileArray VirtualMachine OCCompilerTest >> SortedCollectionTest DictionaryTest SetTest ArrayTest SymbolTest >> BagTest StringTest HeapTest FloatArrayTest OrderedCollectionTest >> LinkedListTest S2BasicNewStub S2BasicNewStubClass S2BasicNewStubMethod >> S2BasicNewStubPackage S2BasicNewTest S2C S2CClass S2CMethod S2CPackage >> S2Class S2ClassPlugin S2Context S2InsertBehaviorPlugin S2Lock S2Method >> S2MethodPlugin S2Package S2Plugin S2PluginTest S2PointNewPlugin >> S2Profiler S2ProfilerPlugin S2ProfilerTest S2SenderTest S2SpyStack >> S2StringNewPlugin S2TestException S2Tester S2TesterClass >> S2TesterMethod S2TesterPackage S2TesterSpy S2py S2pyA S2pyB >> S2pyDummyTest S2pySenderStub S2pySenderStubClass S2pySenderStubMethod >> S2pySenderStubPackage >> >> Cheers, >> -- Pavel >> > >

Dec. 1, 2014

Re: [Pharo-dev] merge conflict (issue validator)

by Nicolai Hess

2014-12-01 13:39 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > > On 01 Dec 2014, at 11:40, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 29 Nov 2014, at 23:04, Nicolai Hess <nicolaihess(a)web.de> wrote: > > I don't understand this merge conflict in hte issue validation for case > 14288 <https://pharo.fogbugz.com/default.asp?14288> > I can manually load the slice and it does not show any conflicts. > > > I actually looked at it when the same time it failed with the monkye, and > I got the > same conflicts. > > I think this is a bug that might be related to MC not getting the right > file to diff sometimes > from SmalltalkHub. > > I have put it back to review needed to see if it works now. > > > This time it worked fine, I will integrate it now. > > Marcus > > Thank you.

Dec. 1, 2014

Re: [Pharo-dev] tests coverage of minimal Pharo

by Alejandro Infante

Hapao works using method wrappers, and do some stuff for every method execution. If Hapao use something you are instrumenting, you are start looping endlessly. So blacklisted classes are classes you are not going to instrument. But, I was trying to understand all the classes you blacklisted, and I donât understand why you have some tests blacklisted, any reason for them? Cheers, Alejandro > On Dec 1, 2014, at 7:57 AM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > ignorant question: What is a black listed class? :) > > On Sun, Nov 30, 2014 at 7:21 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: > Hi, > > I set the job for tests coverage testing of the mimimal Pharo using Hapao: > > https://ci.inria.fr/pharo/view/4.0-Bootstrap/job/Pharo-4.0-Bootstrap-Step-2… <https://ci.inria.fr/pharo/view/4.0-Bootstrap/job/Pharo-4.0-Bootstrap-Step-2…> > > To load results you should load ConfigurationOfSUnit and > ConfigurationOfKernelTests from Pharo/SystemConfigurations repository > into an image with Hapao. Then inspect: > > FLMaterializer materializeFromFileNamed: 'hapao.fuel'. > > Do not try to visualise it ;-) > > Currently blacklisted classes are: > > Array Association ArrayedCollection Behavior BlockClosure ByteSymbol > ByteString ClassDescription CompiledMethod Class Dictionary > Hapao2Package HashedCollection IdentityDictionary Integer LookupKey > FileStream Magnitude Object ProtoObject Process ProcessLocalVariable > ProcessorScheduler ProcessSpecificVariable RPackageOrganizer RPackage > SmalltalkImage SequenceableCollection Set Semaphore SmallInteger > Symbol String SourceFileArray VirtualMachine OCCompilerTest > SortedCollectionTest DictionaryTest SetTest ArrayTest SymbolTest > BagTest StringTest HeapTest FloatArrayTest OrderedCollectionTest > LinkedListTest S2BasicNewStub S2BasicNewStubClass S2BasicNewStubMethod > S2BasicNewStubPackage S2BasicNewTest S2C S2CClass S2CMethod S2CPackage > S2Class S2ClassPlugin S2Context S2InsertBehaviorPlugin S2Lock S2Method > S2MethodPlugin S2Package S2Plugin S2PluginTest S2PointNewPlugin > S2Profiler S2ProfilerPlugin S2ProfilerTest S2SenderTest S2SpyStack > S2StringNewPlugin S2TestException S2Tester S2TesterClass > S2TesterMethod S2TesterPackage S2TesterSpy S2py S2pyA S2pyB > S2pyDummyTest S2pySenderStub S2pySenderStubClass S2pySenderStubMethod > S2pySenderStubPackage > > Cheers, > -- Pavel > >

Dec. 1, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40392 Home: https://github.com/pharo-project/pharo-core

Dec. 1, 2014

[pharo-project/pharo-core] 8be654: 40392

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 8be654fa95e7a5c6d96607b7513e3dde8a1ffb74 https://github.com/pharo-project/pharo-core/commit/8be654fa95e7a5c6d96607b7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-12-01 (Mon, 01 Dec 2014) Changed paths: A Kernel.package/Float.class/class/instance creation/fromIEEE64Bit_.st A Kernel.package/Float.class/instance/printing/binaryLiteralString.st A Kernel.package/Float.class/instance/printing/printBinaryLiteralOn_.st A KernelTests.package/FloatTest.class/instance/tests - printing/testBinaryLiteralString.st A Manifest-Core.package/extension/RBExplicitRequirementMethodsRule/instance/category.st A Nautilus.package/CodeSearchingAcceptor.class/README.md A Nautilus.package/CodeSearchingAcceptor.class/definition.st A Nautilus.package/CodeSearchingAcceptor.class/instance/protocol/accept_notifying_.st A NautilusRefactoring.package/CodeSearchingRule.class/README.md A NautilusRefactoring.package/CodeSearchingRule.class/definition.st A NautilusRefactoring.package/CodeSearchingRule.class/instance/accessing/matcher_.st A NautilusRefactoring.package/CodeSearchingRule.class/instance/accessing/name.st M NautilusRefactoring.package/NautilusRefactoring.class/instance/rewrite code/searchCode.st A NautilusRefactoring.package/extension/NautilusUI/instance/searchCode_.st A Refactoring-Critics.package/RBExplicitRequirementMethodsRule.class/README.md A Refactoring-Critics.package/RBExplicitRequirementMethodsRule.class/definition.st A Refactoring-Critics.package/RBExplicitRequirementMethodsRule.class/instance/accessing/name.st A Refactoring-Critics.package/RBExplicitRequirementMethodsRule.class/instance/accessing/rationale.st A Refactoring-Critics.package/RBExplicitRequirementMethodsRule.class/instance/running/checkClass_.st M SUnit-Core.package/TestCase.class/instance/printing/printOn_.st A SUnit-Core.package/TestCase.class/instance/printing/printTestSelectorDefiningClass_on_.st A SUnit-Core.package/TestCase.class/instance/printing/printTestSelectorOn_.st M SUnit-Tests.package/SUnitTest.class/instance/testing/testFileOutResult.st M SUnit-UI.package/TestRunner.class/instance/browsing/browseSelectedTest_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script392.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40392.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Inspector.package/EyeFloatInspector.class/instance/list/addSpecialFields_.st Log Message: ----------- 40392 14550 testTraitExplicitRequirementMethodsMustBeImplementedInTheClassOrInASuperclass failing 200 times https://pharo.fogbugz.com/f/cases/14550 14288 Show binary literal for Floats in inspectors https://pharo.fogbugz.com/f/cases/14288 14551 Pharo 4.0: Fix "Search Code" refactoring menu item in Nautilus https://pharo.fogbugz.com/f/cases/14551 14546 Failed inherited tests should show home class (in TestRunner, like the debugger) https://pharo.fogbugz.com/f/cases/14546 http://files.pharo.org/image/40/40392.zip

Dec. 1, 2014

Re: [Pharo-dev] merge conflict (issue validator)

by Marcus Denker

> On 01 Dec 2014, at 11:40, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 29 Nov 2014, at 23:04, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: >> >> I don't understand this merge conflict in hte issue validation for case 14288 <https://pharo.fogbugz.com/default.asp?14288> >> I can manually load the slice and it does not show any conflicts. >> > > I actually looked at it when the same time it failed with the monkye, and I got the > same conflicts. > > I think this is a bug that might be related to MC not getting the right file to diff sometimes > from SmalltalkHub. > > I have put it back to review needed to see if it works now. This time it worked fine, I will integrate it now. Marcus

Dec. 1, 2014

Re: [Pharo-dev] SmalltalkHub bugs & hangs :-(

by Tudor Girba

+1 Doru On Mon, Dec 1, 2014 at 11:19 AM, Hilaire <hilaire(a)drgeo.eu> wrote: > Hello, > > From my experience point of view with SmalltlakHub, I found this tool > remarkably stable, useful, feature complete and quite well integrated > with Monticello. > I want to say thank you guys for the energy you spend to keep it running. > > Hilaire > > > > Le 27/11/2014 11:14, Noury Bouraqadi a Ã©crit : > > SmalltalkHub is slow, so donât click too fast :-( > > > > While Iâm grateful to developers of SmalltalkHub and previously > > SqueakSource, I believe as a small community, we cannot afford > > developing everything by ourselves. We donât have enough man-power. We > > can see the symptoms since SmalltalkHub is in beta stage since way too > > long... > > > > Itâs better to use some mainstream platform such as github. > > Weâll we have support for it in Pharo 4? > > > > It would be interesting also from the communication point of view to > > make the world a little bit more aware of Pharo. > > > > Noury > > > -- > Dr. Geo - http://drgeo.eu > iStoa - http://istoa.drgeo.eu > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 1, 2014

Re: [Pharo-dev] SmalltalkHub bugs & hangs :-(

by kilon alios

No of course not. That would have been a deal braker. Personally I prefer using Sourcetree to browser history of commits than using the pharo on board tools. Pharo is good on that respect, but sourcetree is better and smartgit I have used in the past. It also has nice visualisation for branches , merges etc. I have not shown these features in my video tutorial as I was planning to show them to a separate tutorial. I would not mind bypassing monticello completely since its usage is unnecessary at least to me with all these git tools that one can download and use for free. The same is true for other IDEs out there , generally people prefer using dedicate tools. Usually dedicate tools are hard to beat this is why I believe modularising Pharo is extremely important as will make integrating external tools way easier. I think however that Roassal can be used to visualise in similar way the history as Sourcetree does. So pharo is not far from it but as always its a matter of someone doing the hard work. On Mon, Dec 1, 2014 at 12:21 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Le 27/11/2014 11:29, kilon alios a Ã©crit : > > My personal opinion on Github and Pharo is that it already works great > > with Pharo. The workflow with filetree is exactly the same as other > > languages that gives the added advantage that you can use all the > > powerful tools you use with other languages for commiting to git and > > github. I have not experienced any kind of issue of problem using github > > with Pharo nor my experience has been any worse than other languages. > > > > With git, don't you lost the capability to browse the history of changes > in your code? > > Hilaire > > > -- > Dr. Geo - http://drgeo.eu > iStoa - http://istoa.drgeo.eu > > >

Dec. 1, 2014