- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Class allSubInstances size takes 23 seconds to run on Pharo 5 on OS X

by Pavel Krivanek

Interesting. It takes very high amount of time on Pharo 2.0 too. -- Pavel 2016-04-20 14:26 GMT+02:00 Bernhard Pieber <bernhard(a)pieber.com>: > Dear Pharoers, > > I found something strange: > Time millisecondsToRun: [ Class allSubInstances size ]. â23617" > > I did this on a new Pharo 5 image > curl get.pharo.org/alpha+vmLatest | bash > > Can somebody confirm this on their machine? What might be the reason? > > Cheers, > Bernhard >

April 20, 2016

Re: [Pharo-dev] Mocketry names again

by Denis Kudriashov

2016-04-20 13:59 GMT+02:00 Dennis Schetinin <chaetal(a)gmail.com>: > Why do we need those sophisticated past-something form after should at > all? Why not simply > > mock should receive someMessage > > ? > Maybe. What others think?

April 20, 2016

Class allSubInstances size takes 23 seconds to run on Pharo 5 on OS X

by Bernhard Pieber

Dear Pharoers, I found something strange: Time millisecondsToRun: [ Class allSubInstances size ]. â23617" I did this on a new Pharo 5 image curl get.pharo.org/alpha+vmLatest | bash Can somebody confirm this on their machine? What might be the reason? Cheers, Bernhard

April 20, 2016

Re: [Pharo-dev] Mocketry names again

by Dennis Schetinin

Why do we need those sophisticated past-something form after should at all? Why not simply mock should receive someMessage ? -- Best regards, Dennis Schetinin 2016-04-20 11:35 GMT+03:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > Hi. > > People start argue that my choice of names are not good. > > For now Mocketry use "should got" to verify that following message was > occurred: > > mock *should got* someMessage > > > This is broken for native english speakers. Do you agree to replace it > with correct #haveReceived? > Can we use more short version #haveGot? > > mock should haveReceived someMessage > > mock should haveGot someMessage > > > Also there is new expression to verify how object was received during > test: > > result should *beReturnedFrom:* [mock someMessage] > > > Should it be #haveReturnedFrom: ? > > > result should haveReturnedFrom: [mock someMessage] > > > I hope we can make consensus and be happy with Mocketry. > > Best regards, > Denis >

April 20, 2016

Re: [Pharo-dev] Ubuntu PPA administration - volunteers?

by Norbert Hartl

Hi, I'll wait for another couple of days but if nobody will step in I'll try. I have the same fear not finding enough time to do it but it is worth a try. My goal with it would be to move from ubuntu ppa to opensuse build service. If integrated there we could build packages for all big linux distributions at once. It woould be nice if you could describe the steps you do more in-depth so the take-over will be easy. Norbert [1] http://openbuildservice.org/ <http://openbuildservice.org/> > Am 19.04.2016 um 09:34 schrieb Markus Fritsche <mfritsche(a)reauktion.de>: > > Hello list, > > I haven't been able to supply as many ppa updates as needed. Right now, > there's a need for a new spur vm and a new graph of dependencies between > the packages that I havent't yet set up. > > Realistically, I think I won't be able to keep up as with pharo > development it deserves :( > > Is there anyone whos willing to help? It involves > - setting up a build environment > - keeping up with pharo vm, pharo launcher releases > - executing build scripts > - react to errors - not that often > - entering your gpg key passphrase > - testing the successful deployment >

April 20, 2016

[pharo-project/pharo-core]

by GitHub

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

April 20, 2016

[pharo-project/pharo-core] 668022: 50702

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 668022f0e62bc208deb8b7ebbd7a31550ea50346 https://github.com/pharo-project/pharo-core/commit/668022f0e62bc208deb8b7eb… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-04-20 (Wed, 20 Apr 2016) Changed paths: A Kernel-Tests.package/CompiledMethodTest.class/instance/tests - testing/testContainsHalt.st M Kernel.package/CompiledMethod.class/instance/testing/containsHalt.st R OpalCompiler-Core.package/OCCopyingTempVariable.class/instance/debugging/writeFromContext_scope_value_.st M OpalCompiler-Tests.package/MethodMapTests.class/instance/testing - temp access/testExampleTempNamedPutCopying2.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50701.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50702.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50701.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50702.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50702 18017 CompiledMethod>>#containsHalt should exclude the selector when checking literals https://pharo.fogbugz.com/f/cases/18017 17702 failting test: OCClosureCompilerTest>>#testDebuggerTempAccess https://pharo.fogbugz.com/f/cases/17702 http://files.pharo.org/image/50/50702.zip

April 20, 2016

Re: [Pharo-dev] What the state of unifying Beacon with SystemLogger?

by Norbert Hartl

Denis, > Am 18.04.2016 um 18:28 schrieb Denis Kudriashov <dionisiydk(a)gmail.com>: > > Hello. > > Year ago Beacon and SystemLogger were announced. There was big discussion about them. And there were plans to provide single solution. What was done around that? > we had some talks but nothing happened afterwards. The whole discussion went somehow off track. The good part is that we had a conclusion that we want to log objects instead of strings. The bad part is that we forget to talk about the "logging" part of it. And the discussion and actions are not a good example for collaboration rather the opposite. The SystemLogger started as a project to build a small core about what is usually done in logging frameworks. Usually log messages are strings with a severity level like error, warn, etc attached. The log messages are dispatched to a central location. At that location there is a bunch of log message consumers that filter by severity level or other criteria. This filtering consumers are attached to sinks that store the messages in some format somewhere. The sinks implement formatting and adaptation to storage like files, syslog, database,â¦ We want to do better and we care about objects instead of strings. In case of writing to a file it will be a string anyway. So we can see that "logging objects" means that the distribution of a log through the system should happen as objects with rich interfaces. And it means that the conversion to a string should happen (if needed at all) at the latest possible moment. So in my opinion the logging framework should support: - having an easy way to emit any kind of log object. The most basic thing a log entity should have is a timestamp. Around it there could be some common use cases but most of it is application specific. - multiple log consumers - filtering of log entities. IMO this includes filtering of objects you log to store. In a typical scenario where you would have a severity level you only want to log certain messages. This can also include filtering for special types of objects. That would mean you filter the kind of objects the consumer can understand - storage facilities. It is quite important to support files storage in many flavors, logging to syslog, logging to database etc. Without that you are just logging in memory and I'm not sure if a lot of people would agree that this is what is meant by using the word logging As an example I can put one of my projects where I use SystemLogger. When sending a push notification I log/emit an object/event of type COMessageSent with sublcasses for apple, google, etc. It is emitted to a central location. In SystemLogger there a three loggers configured. One is in memory and counts the number of events per class. One takes the object, converts it into a short string representation like "apple push sent to XXXX" and sends it via syslog/UDP to a central logging server. Finally the third one takes the object, converts it to json and stores the json in a elasticsearch database. The database allows me to do all sorts of statistical analysis of the data over a long time frame such as number of push messages per month for one year. Which looks like this So if you take my point of view then Beacon is pretty useless. SystemLogger and Beacon both use a singleton to dispatch log entities. In SystemLogger has own implementation of registry for that loggers. Beacon uses Announcements for it. That's basically the difference. I like the idea of using Announcements and not invent yet another distribution mechanism. But with Announcements you can only filter by class and not by instance. So it cannot do what system logger can do. Doru writes that he is working on that and it would be great. Although I have doubt this can be done performant I would be lucky to have it. On the other hand Beacon implements a handful of classes for some use cases but nothing more. So I see Svens point that you don't need it really because Announcements are there anyway and most of the stuff is application specific so I can just do that without having to integrate a "framework". > What exactly should be merged between this libraries? Was Beacon or SystemLogger planned to be end solution? > I'm not sure anymore. I can see some good things in Beacon that enable to register a logger for part of the execution. The drawback is that if you think about output facilities like log files there is no central place to attach it. And I surely don't want to have log configurations in the middle of my code. Beacon is not well thought in that direction, yet. IMHO I'd like to have a SystemLogger with the distribution of objects like it is done in Beacon. Filtering is to be solved. This is hard to do with Announcements and to be honest I don't really like it how it is done in SystemLogger. > We definitely need legacy logging tool for Pharo. And I am going to work on this direction. > Personally I prefer metaphor and names from Beacon. But both libraries implement similar idea. > Agreed. As I said above. If you take to point of view from legacy logging tool Beacon is not a big help. But the ideas in it are good and should be integrated somewhere. If you are talking about legacy tooling it might ok to use the terms logging as well, no? I personally like the work Beacon but in my opinion it is wrong for this purpose. A beacon sends a uniform signal in order to be discovered. The Beacon code sends signals to a beacon. And I can register at the beacon in which signals I'm interested in. Feels wrong to me. Norbert

April 20, 2016

Re: [Pharo-dev] [Ann] New version of Mocketry 3.0

by Denis Kudriashov

2016-04-20 2:27 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Tudor Girba-2 wrote > > It is your prerogative :), but âshould got" sounds broken :(. > > Sounds like fingernails on a chalkboard IMH-native-english-speaker-O ;) > Ok. I open new thread about names

April 20, 2016

Mocketry names again

by Denis Kudriashov

Hi. People start argue that my choice of names are not good. For now Mocketry use "should got" to verify that following message was occurred: mock *should got* someMessage This is broken for native english speakers. Do you agree to replace it with correct #haveReceived? Can we use more short version #haveGot? mock should haveReceived someMessage mock should haveGot someMessage Also there is new expression to verify how object was received during test: result should *beReturnedFrom:* [mock someMessage] Should it be #haveReturnedFrom: ? result should haveReturnedFrom: [mock someMessage] I hope we can make consensus and be happy with Mocketry. Best regards, Denis

April 20, 2016