- Pharo-dev - lists.pharo.org

version 50 of SecureSession is released
by Robert Withers Dec. 18, 2015

Dec. 18, 2015

SecureSession is now FEC encoded. thanks, -- . .. .. ^,^ robert

1 2

Pharo Sprint in Santiago de Chile
by Juraj Kubelka Dec. 18, 2015

Dec. 18, 2015

Hi, We are having Pharo Sprint in about one hour. If anyone is aware of an issue that is important to fix, we will appreciate if you mark it in FogBugz by sprint tag or post it here. Thanks, Juraj -- Juraj Kubelka

3 9

Serious issue with OSProcess on Mac
by Alexandre Bergel Dec. 18, 2015

Dec. 18, 2015

Hi! On my mac, using Spur, the following expression: (PipeableOSProcess command: 'ls /tmp') output return an empty string. This breaks completely the Git integration :-( Thierry has asked for credential to commit in the vm source code, but he is still waiting for a reply. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 2

Re: [Pharo-dev] potential to include cryptography in base image
by Sven Van Caekenberghe Dec. 18, 2015

Dec. 18, 2015

Robert, I think that the Pharo community, part of which is more business oriented, is absolutely interested in more and better Crypto code. In any case, I am. What we absolutely want, if it is not already the case (I did not check), is that the Crypto code can be loaded using 1 single action (through our validated Monticello configurations and Catalog mechanism) - I am sure you will find help to achieve and maintain (through a CI process) that goal. Whether it should be a base part of the image is another question. Modularity is a huge goal for Pharo. This is a much harder discussion (as the same can be said of or asked for for many packages that are generally useful: XML, CSV, JSON, SQL, ...). In any the case, the first step is the one described in the previous paragraph. Then you need traction, usage, and maybe demand for full inclusion. Regards, Sven > On 15 Dec 2015, at 11:00, Robert Withers <robert.w.withers(a)gmail.com> wrote: > > It was suggested to me that I write to the list and raise the question about cryptography being included in the base image. Really I have 3 questions I would ask you all: > > â¢ is it desirable to include cryptography? > â¢ is it feasible to include cryptography? > â¢ what is the time frame for including cryptography? > Given the thread on password hashing (and salting and so on), there are good, solid implementations in the cryptography package. Looking in the Cryptography repository, there is a Pharo 5.0 compatible Cryptography package. > > In light of another recent thread discussing random number generation, discussion about the best approach to random algorithms in cryptography ought be engaged. For instance, the SecureRandom algorithm evidently provides some level of guarantee. > > To underline the solidity I am attaching a profile of all 102 cryptography tests passing green. This profile demonstrates that there are no areas of particular inefficiency - nothing stands out to be improved - means that the entire library is maximally efficient. > > And so I please ask that we have these discussions, for there is a lot of value in this package for general and basic use. > > > -- > . .. ... ^,^ best, robert > <Cryptography Spy Results.text.gz>

4 17

OT: Convince me github is a wise choice
by Eliot Miranda Dec. 18, 2015

Dec. 18, 2015

Hi Ben, Hi All, I'm quite conservative when it comes to relying on others' infrastructure so I need some help making me take the plunge. Please see below: On Thu, Dec 17, 2015 at 7:15 AM, Ben Coman <btc(a)openinworld.com> wrote: > > > On Wed, Dec 16, 2015 at 1:00 AM, Ben Coman <btc(a)openinworld.com> wrote: > >> > >> > >> On Wed, Dec 16, 2015 at 10:43 AM, Ryan Macnak <rmacnak(a)gmail.com> > wrote: > >> > > >> > What would be more helpful is if the VM build was fixed to work with > a cross compiler, so it would compile fast enough to test ARM and MIPS on > Travis CI alongside IA32 and X64. > >> > > >> > It would also help if the top-of-tree Intel VMs were always kept > working so we'd know which change broke something. Moving the Subversion > repository to a more reliable host (which likely means migrating to Git) > would also cut down on the false positives Travis reports because the > Subversion server has a habit of dropping connections. > >> > >> +1 github :) > > btw, Did you know that github supports subversion clients since 2011 [1]? > Here are supported features [2]. Are these sufficient for your > current svn workflows? > Potentially we could have ONE repository and those liking subversion > can stick with it and those liking git can use that. Of course, this > would need to be proven. > Ah, that's interesting. So my concern is whether github is a safe long-term bet. Specifically what is there to prevent some third party from buying github, or of github going public and the board taking the decision, or github on its own, deciding to charge for hosting, keeping the data hostage to extract payment? What safeguards are in place to prevent this? I'm not interested in "this will never happen" arguments. I'm interested in hard data please. [4] Provides pragmatic advice for cutting over. Esteban appears to > have done similar to step 1 and 2 [3] - but it seem sometimes his > modifications directly update this mirror so its not clear to see when > that branch is an *exact* copy of the current svn trunk. So I'd love > to see a github repository that is always an *exact* mirror of the svn > repository, with any pharo mods occurring in a branch off that. Even > better if the repository for svn users resides on github in place of > that mirror. > > I've been googling around for problems reported using github via an > svn client, and haven't found any smoking guns. > Is this something we can trial? I'm willing to put some effort into > it. A key requirement would be not interrupting Eliots work on > Spur-64. Potentially we could stay for months on step 3 [4] with the > CI infrastructure running on the git side, but code check-ins > continuing onthe svn side. > > btw2, [5] provides a use case for the advantages of a full switch. > > cheers -ben > > [1] https://github.com/blog/966-improved-subversion-client-support > [2] https://help.github.com/articles/support-for-subversion-clients/ > [3] https://github.com/pharo-project/pharo-vm/network > [4] > http://blogs.atlassian.com/2013/01/atlassian-svn-to-git-migration-technical… > [5] > http://blogs.atlassian.com/2013/01/svn-to-git-how-atlassian-made-the-switch… > -- _,,,^..^,,,_ best, Eliot

8 11

New version (47) of SecureSession for Pharo & Squeak
by Robert Withers Dec. 18, 2015

Dec. 18, 2015

Please load the SecureSession.47 and drive it about a bit. I am missing crypto plugins on Pharo, so avoid the performance test, tto stay responsive. Here are some of the changes: - frame-based pipeline - header per msg so no mutable session state - header is written with message in Asn1Der encoding. - most header fields currently optional - adding per-connection msgId to header - timeSent set also - reworked TransportEndpoint to be better scoped. Looking forward: - extend frames into the strategy utilities - events Any issues or questions, please reach out. Thanks, robert

1 0

Bugs I found during the lectures in Yaounde
by stepharo Dec. 17, 2015

Dec. 17, 2015

Hi today and yesterday I'm giving 6 hours of pharo lecture to 100 students and we have fun. Here are the bugs I found (I'm working on the latest 50) - we cannot bring menu in certain part of the debugger (may inspector) - class definitions are not logged in changes - when we write self shoulnt: [Dice new faces: 20 ] raise: Error the debugger does not show the create menu for the method faces: It would be good to record this. I have a reeeeeeallllly slow internet connection and only from time to time. Stef

3 3

Fuel materialization on spur
by Norbert Hartl Dec. 17, 2015

Dec. 17, 2015

We have a test build for pharo5 that checks if we need to do stuff for future migrations. Since yesterday it fails, of course. I have a fueled out object graph stored as byte array in a method. The fuel bytes are serialized using a non-spur image. Now when the spur image reads the bytes I get an exception. Has this something to do with immediate characters? Is there a way to fix that or will it just not be possible to exchange objects between spur and non-spur using fuel? thanks, Norbert primitive #value: in Character class failed Stacktrace Character class(Object)>>primitiveFailed: Character class(Object)>>primitiveFailed Character class>>value: Character class>>materializeFrom: FLHookPrimitiveCluster>>materializeInstanceWith: FLHookPrimitiveCluster(FLIteratingCluster)>>materializeInstancesStepWith: FLMaterialization>>clusterInstancesStep [ self clusterInstancesStep ] in FLMaterialization>>instancesStep SmallInteger(Integer)>>timesRepeat: FLMaterialization>>instancesStep FLMaterialization>>run [ :aDecoder | (FLMaterialization with: aDecoder) run; yourself ] in FLMaterializer>>setDefaultMaterialization FLMaterializer>>materializeFrom: FLMaterializer class>>materializeFromByteArray: MAPExampleModels class>>readModelFromSelector: MAPExampleModels class>>readModelNamed: [ self readModelNamed: aString ] in MAPExampleModels class>>named: [ self at: key put: aBlock value ] in Dictionary>>at:ifAbsentPut: Dictionary>>at:ifAbsent: Dictionary>>at:ifAbsentPut: MAPExampleModels class>>named: MAPTest>>model MAPTest>>tcapModule MAPTest>>testInsertSubscriberDataBitStringAccess [ testMethod perform: testMethod selector ] in Given>>produceReturnValueAt: [ self at: key put: aBlock value ] in Dictionary>>at:ifAbsentPut: Dictionary>>at:ifAbsent: Dictionary>>at:ifAbsentPut: Given>>produceReturnValueAt: MAPTest(Phexample)>>performTest

11 29

[pharo-project/pharo-core]
by GitHub Dec. 17, 2015

Dec. 17, 2015

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

1 0

[pharo-project/pharo-core] 83deba: 50507
by GitHub Dec. 17, 2015

Dec. 17, 2015

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 83deba4317d51c05e322ee26e3403a43621b87e8 https://github.com/pharo-project/pharo-core/commit/83deba4317d51c05e322ee26… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-12-17 (Thu, 17 Dec 2015) Changed paths: R Kernel-Tests.package/BehaviorTest.class/instance/tests/testUncompactClassNotAllowed.st R Kernel.package/Integer.class/class/class initialization/initialize.st M Kernel.package/Object.class/instance/memory usage/sizeInMemory.st M OpalCompiler-Core.package/CCompilationContext.class/class/initialize/initialize.st M OpalCompiler-Core.package/CompilationContext.class/class/initialize/initialize.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50506.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50507.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50506.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50507.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot-Tests.package/SlotBasicTest.class/instance/tests-basic/testNewCompiledMethodClass.st M Slot-Tests.package/SlotBasicTest.class/instance/tests-basic/testNewPointerClass.st M Slot-Tests.package/SlotBasicTest.class/instance/tests-basic/testNewVariableByteClass.st M Slot-Tests.package/SlotBasicTest.class/instance/tests-basic/testNewVariableWordClass.st M Slot-Tests.package/SlotBasicTest.class/instance/tests-basic/testNewWeakClass.st M Tool-Finder.package/MethodFinder.class/instance/initialize/initialize.st M Traits.package/TBehavior.class/instance/private/becomeCompact.st M Traits.package/TBehavior.class/instance/private/becomeCompactSimplyAt_.st M Traits.package/TBehavior.class/instance/private/becomeUncompact.st R Traits.package/TBehavior.class/instance/private/checkCanBeUncompact.st M Traits.package/TBehavior.class/instance/testing/isCompact.st Log Message: ----------- 50507 17258 remove "super initialize" from CompilationContext and CCcompilationContext https://pharo.fogbugz.com/f/cases/17258 17266 Compact classes cleanup https://pharo.fogbugz.com/f/cases/17266 17262 AST-FFI-Pharo50Compatibility has wrong repository associated https://pharo.fogbugz.com/f/cases/17262 http://files.pharo.org/image/50/50507.zip

1 0