November 2017 - Pharo-users

Re: [Pharo-users] Please consider Apache Integration of Services

by Andrew Glynn

>From the (admittedly not huge) testing Iâve done, Storm is slower, has more overhead, and more issues with concurrency than simply using the PostgreSQL overlay to HDFS. It would also be easier to do using Gemstone and Pivotal HDB than using Storm, since the code to do from Gemfire is already open source and massively smaller than the code to Storm (or Spark - the main difference is the higher level API). Since I donât see the advantage, what advantage to you see in it? Itâs just my $0.02, and given we no longer have five cent coins in Canad, you can round it to what itâs probably worth â¦ Andrew Glynn Sent from Mail for Windows 10 From: henry Sent: Friday, November 10, 2017 5:12 PM To: Squeak-dev; Pharo-users list Subject: [Pharo-users] Please consider Apache Integration of Services Note, my quote below, Storm is implementable by any language, hello Smalltalk! At the risk of throwing a rock in the pool, I must as well acknowledging the unique offerings we have in Smalltalk spaces. The challenge as I see it is the lack of a coordinated effort to adopt common interfaces used in industry. I would hold up the history of the Cryptography team how different folks came together to join efforts in creating a shared library. Which they did. It holds up over the test of time and is ported through multiple Smalltalk environments. Using that as a reference, were the various cloud and BigData applications be seen as worthy to build good integration with, the access to all the great data-manipulation tools and presentations that Smalltalk environments offer will finally be accessible to put on the table in corporate and advanced data processing environments. Alright, you may accept what I have been saying then for those of us still in contemplation will be curious about what work that entails. Allow me to present a few of the projects working together through Apache Foundation. They are truly leaders in creating the computing of BigData. The core architecture that is commonly used in BigData and Cloud is called the Lambda Architecture, consisting of a fault-tolerant event streaming source, such as Apache Kafka [1], a batch-processing pipe and NoSQL database coordinator, such as Apache Cassandra [2], and a real-time processing pipe, for example Apache Storm [3]. There is also analytics on the other side of storage, such as through Cassandra to Hadoop and queries. What I would like to highlight is Apache Storm. Apache Storm is quite simple in idea though more complex on hardware. One thing to keep in mind is that the fault-tolerance requirement has forced Kafka and Storm to both be replication centric in a de-centralized way. They tend to use Apache Zookeeper [4] to monitor progress through durable queues of data. Storm in particular is a way to consume streams of events, including the ability to join and filter them. Here are two blurbs, one about Storm Architecture and the other about how other languages can implement Storm architecture pieces, especially Bolts. My question is why can't and why shouldn't Smalltalks (Pharo, Squeak, Gemstone, Smalltalk Express, Swift, ST/X, Dolphin) be able to participate? Working software engineers are building this stuff and lots of time and money are being spent converting critical data in industry. It seems now is the time to jump aboard as much computing will be done in these areas and we can compete! Here are blurbs about Storm then links to Kafka [1], Cassandra [2] and Storm [3]. ------ "There are just three abstractions in Storm: spouts, bolts, and topologies. A spout is a source of streams in a computation. Typically a spout reads from a queueing broker such as Kestrel, RabbitMQ, or Kafka, but a spout can also generate its own stream or read from somewhere like the Twitter streaming API. Spout implementations already exist for most queueing systems. A bolt processes any number of input streams and produces any number of new output streams. Most of the logic of a computation goes into bolts, such as functions, filters, streaming joins, streaming aggregations, talking to databases, and so on. A topology is a network of spouts and bolts, with each edge in the network representing a bolt subscribing to the output stream of some other spout or bolt. A topology is an arbitrarily complex multi-stage stream computation. Topologies run indefinitely when deployed." ------ "Storm was designed from the ground up to be usable with any programming language. At the core of Storm is a Thrift definition for defining and submitting topologies. Since Thrift can be used in any language, topologies can be defined and submitted from any language. Similarly, spouts and bolts can be defined in any language. Non-JVM spouts and bolts communicate to Storm over a JSON-based protocol over stdin/stdout. Adapters that implement this protocol exist for Ruby, Python, Javascript, Perl." ------ [1] https://kafka.apache.org/ [2] http://cassandra.apache.org/ [3] http://storm.apache.org/ [4] https://zookeeper.apache.org/ - HH

Nov. 10, 2017

Please consider Apache Integration of Services

by henry

Note, my quote below, Storm is implementable by any language, hello Smalltalk! At the risk of throwing a rock in the pool, I must as well acknowledging the unique offerings we have in Smalltalk spaces. The challenge as I see it is the lack of a coordinated effort to adopt common interfaces used in industry. I would hold up the history of the Cryptography team how different folks came together to join efforts in creating a shared library. Which they did. It holds up over the test of time and is ported through multiple Smalltalk environments. Using that as a reference, were the various cloud and BigData applications be seen as worthy to build good integration with, the access to all the great data-manipulation tools and presentations that Smalltalk environments offer will finally be accessible to put on the table in corporate and advanced data processing environments. Alright, you may accept what I have been saying then for those of us still in contemplation will be curious about what work that entails. Allow me to present a few of the projects working together through Apache Foundation. They are truly leaders in creating the computing of BigData. The core architecture that is commonly used in BigData and Cloud is called the Lambda Architecture, consisting of a fault-tolerant event streaming source, such as Apache Kafka [1], a batch-processing pipe and NoSQL database coordinator, such as Apache Cassandra [2], and a real-time processing pipe, for example Apache Storm [3]. There is also analytics on the other side of storage, such as through Cassandra to Hadoop and queries. What I would like to highlight is Apache Storm. Apache Storm is quite simple in idea though more complex on hardware. One thing to keep in mind is that the fault-tolerance requirement has forced Kafka and Storm to both be replication centric in a de-centralized way. They tend to use Apache Zookeeper [4] to monitor progress through durable queues of data. Storm in particular is a way to consume streams of events, including the ability to join and filter them. Here are two blurbs, one about Storm Architecture and the other about how other languages can implement Storm architecture pieces, especially Bolts. My question is why can't and why shouldn't Smalltalks (Pharo, Squeak, Gemstone, Smalltalk Express, Swift, ST/X, Dolphin) be able to participate? Working software engineers are building this stuff and lots of time and money are being spent converting critical data in industry. It seems now is the time to jump aboard as much computing will be done in these areas and we can compete! Here are blurbs about Storm then links to Kafka [1], Cassandra [2] and Storm [3]. ------ "There are just three abstractions in Storm: spouts, bolts, and topologies. A spout is a source of streams in a computation. Typically a spout reads from a queueing broker such as Kestrel, RabbitMQ, or Kafka, but a spout can also generate its own stream or read from somewhere like the Twitter streaming API. Spout implementations already exist for most queueing systems. A bolt processes any number of input streams and produces any number of new output streams. Most of the logic of a computation goes into bolts, such as functions, filters, streaming joins, streaming aggregations, talking to databases, and so on. A topology is a network of spouts and bolts, with each edge in the network representing a bolt subscribing to the output stream of some other spout or bolt. A topology is an arbitrarily complex multi-stage stream computation. Topologies run indefinitely when deployed." ------ "Storm was designed from the ground up to be usable with any programming language. At the core of Storm is a [Thrift](http://thrift.apache.org/) [definition](https://github.com/apache/storm/blob/master/storm-core/src/stor… for defining and submitting topologies. Since Thrift can be used in any language, topologies can be defined and submitted from any language. Similarly, spouts and bolts can be defined in any language. Non-JVM spouts and bolts communicate to Storm over a [JSON-based protocol](http://storm.apache.org/documentation/Multilang-protocol.html) over stdin/stdout. Adapters that implement this protocol exist for [Ruby](https://github.com/apache/storm/blob/master/storm-multilang/ruby/src/…, [Python](https://github.com/apache/storm/blob/master/storm-multilang/python/…, [Javascript](https://github.com/apache/storm/blob/master/storm-multilang/jav…, [Perl](https://github.com/dan-blanchard/io-storm)." ------ [1] https://kafka.apache.org/ [2] http://cassandra.apache.org/ [3] http://storm.apache.org/ [4] https://zookeeper.apache.org/ - HH

Nov. 10, 2017

Re: [Pharo-users] FileReference basename of current dir

by Alistair Grant

On 9 November 2017 at 22:12, Norbert Hartl <norbert(a)hartl.name> wrote: > is there a good explanation why > > âfooâ asFileReference parent basename > > gives â/â ? I'd like to think about this a bit more, but at first glance the problem seems to be that Path>>basename was written only taking Absolute paths in to consideration. So RelativePath>>basename needs to be added: basename "Returns the base of the basename, i.e. foo/gloops.taz basename is 'gloops.taz' . basename is '.'" self size == 0 "the current directory" ifTrue: [ ^ '.']. ^ self at: self size Cheers, Alistair

Nov. 10, 2017

Re: [Pharo-users] Adding an Iceberg repository at startup

by Stephane Ducasse

I will add this to the tips and tricks except is someone is faster than me. Stef On Fri, Nov 10, 2017 at 7:26 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Thanks guys. I ended up doing this: > > StartupPreferencesLoader default executeAtomicItems: { > StartupAction > name: '02 Iceberg' > code: [ > | repo | > > IceCredentialsProvider default sshCredentials > username: 'git'; > publicKey: '/Users/mariano/.ssh/id_rsa_github.pub'; > privateKey: '/Users/mariano/.ssh/id_rsa_github'; > keyPassphrase: 'YYY'. > > IceCredentialsProvider default plaintextCredentials > username: 'marianopeck(a)gmail.com'; > password: 'XXX'. > > Iceberg enableMetacelloIntegration: true. > IceRepository > shareRepositoriesBetweenImages: true; > sharedRepositoriesLocationString: '/Users/mariano/Pharo/git'. > Iceberg showSystemRepositories: false. > > repo := IceRepositoryCreator new > location: > '/Users/mariano/pharo61/pharo-local/iceberg/marianopeck/OSSubprocess' > asFileReference; > subdirectory: 'repository'; > createRepository. > repo register. > > "more registrations here" > > ] > runOnce: true. > }. > > > On Fri, Nov 10, 2017 at 10:11 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >> You can create repositories programatically. >> >> repo := IceRepositoryCreator new >> location: '/home/user/.../'; >> subdirectory: 'codeSubdirectory'; >> createRepository. >> repo register. >> >> >> On Fri, Nov 10, 2017 at 1:11 PM, Mariano Martinez Peck >> <marianopeck(a)gmail.com> wrote: >>> >>> I would also like that :) >>> >>> On Fri, Nov 10, 2017 at 6:45 AM, Prof. Andrew P. Black <black(a)cs.pdx.edu> >>> wrote: >>>> >>>> I would like to have the git repositories that Iâm working from >>>> automatically added to the list of known repositories in Iceberg at startup >>>> time. In other words, I don;t want to have to do a bunch of âAdd local >>>> repositoryâ commands before I can start work. >>>> >>>> What magic can I put in my settings.st file to make this happen? >>>> >>>> Andrew >>>> >>>> >>> >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >> >> > > > > -- > Mariano > http://marianopeck.wordpress.com

Nov. 10, 2017

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

by Sean P. DeNigris

Tudor Girba-2 wrote > As shown at ESUG, GT Documenter offers an advanced viewer (and editor) for > Pillar working on top of Bloc. Two questions after playing with it: 1. Can one save a live-edited file? 2. Is it possible to make the markup codes invisible? That would seem more appropriate e.g. in a read-only context. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 10, 2017

Re: [Pharo-users] Why does the test runner show red when I correct a test?

by Richard Sargent

> > So after a restart we would expect green > Yes. Add having the test tool able to automate the tear-down and restart of the test would be a good automation. On Fri, Nov 10, 2017 at 11:41 AM, stephan <stephan(a)stack.nl> wrote: > On 10-11-17 18:56, Richard Sargent wrote: > >> That would be fine. >> The point is that, without running the test in its entirety, from start >> to finish, without interruption, error, or failure, one cannot claim >> success. >> > > So after a restart we whould expect green > > Stephan > > >

Nov. 10, 2017

Re: [Pharo-users] Why does the test runner show red when I correct a test?

by Richard Sargent

I hear you and I understand your pain. However, if you corrected the problem, not by a code change, but by playing in the object's inspector or otherwise causing its internal state to change, and then resumed from the debugger, would you still claim the method was successful and should be coloured green? The only thing we can claim is that there were or were not further errors in the test. Colour it red if there were, but you cannot honestly colour it green. The code doesn't actually work. On Fri, Nov 10, 2017 at 11:29 AM, Tim Mackinnon <tim(a)testit.works> wrote: > My specific usecase is from a pragmatic TDD perspective - failing test, in > the debugger you fix the test and press proceed - expecting green. Getting > red, and then immediately running again to get red takes away from our > story of love coding and loving your debugger - and even Cassie me to > mistrust the tools. > > I get the idea that you can jiffy in the debugger and cause a false pass - > but I feel you are penalised for doing it right at the moment. > > Of course these tests will get run again, but I like the idea that if I > did it right, it should recognise this, not incur an extra click and moment > of doubt. > > A button to rerun the whole lot, or automatically rerun, or just run it > would work for me. > > Tim > > Sent from my iPhone > > On 10 Nov 2017, at 17:56, Richard Sargent <richard.sargent@ > gemtalksystems.com> wrote: > > That would be fine. > The point is that, without running the test in its entirety, from start to > finish, without interruption, error, or failure, one cannot claim success. > > On Fri, Nov 10, 2017 at 9:34 AM, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > >> Richard Sargent wrote >> > The only reliable conclusion one can make from such an interrupted run >> is >> > whether it failed again. So, it would be possible to determine that the >> > test should be coloured red, but it is impossible to *reliably* claim >> that >> > the test should be coloured green. >> >> What if we ran the test again as if from the browser/runner before setting >> the icon? >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >

Nov. 10, 2017

Re: [Pharo-users] Why does the test runner show red when I correct a test?

by stephan

On 10-11-17 18:56, Richard Sargent wrote: > That would be fine. > The point is that, without running the test in its entirety, from start > to finish, without interruption, error, or failure, one cannot claim > success. So after a restart we whould expect green Stephan

Nov. 10, 2017

Re: [Pharo-users] Why does the test runner show red when I correct a test?

by Tim Mackinnon

Sorry "immediately running again to get red " should have been "to get green" Tim Sent from my iPhone > On 10 Nov 2017, at 19:29, Tim Mackinnon <tim(a)testit.works> wrote: > > immediately running again to get red

Nov. 10, 2017

Re: [Pharo-users] Why does the test runner show red when I correct a test?

by Tim Mackinnon

My specific usecase is from a pragmatic TDD perspective - failing test, in the debugger you fix the test and press proceed - expecting green. Getting red, and then immediately running again to get red takes away from our story of love coding and loving your debugger - and even Cassie me to mistrust the tools. I get the idea that you can jiffy in the debugger and cause a false pass - but I feel you are penalised for doing it right at the moment. Of course these tests will get run again, but I like the idea that if I did it right, it should recognise this, not incur an extra click and moment of doubt. A button to rerun the whole lot, or automatically rerun, or just run it would work for me. Tim Sent from my iPhone > On 10 Nov 2017, at 17:56, Richard Sargent <richard.sargent(a)gemtalksystems.com> wrote: > > That would be fine. > The point is that, without running the test in its entirety, from start to finish, without interruption, error, or failure, one cannot claim success. > >> On Fri, Nov 10, 2017 at 9:34 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> Richard Sargent wrote >> > The only reliable conclusion one can make from such an interrupted run is >> > whether it failed again. So, it would be possible to determine that the >> > test should be coloured red, but it is impossible to *reliably* claim that >> > the test should be coloured green. >> >> What if we ran the test again as if from the browser/runner before setting >> the icon? >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >

Nov. 10, 2017