- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

Dec. 21, 2016

[pharo-project/pharo-core] 420e59: 60334

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 420e59ef1f9acba9c16c30c9ec56d47efb47872e https://github.com/pharo-project/pharo-core/commit/420e59ef1f9acba9c16c30c9… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-12-21 (Wed, 21 Dec 2016) Changed paths: M GeneralRules.package/GRVariableAssignedLiteralRule.class/instance/accessing/name.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60333.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60334.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60333.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60334.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tool-CriticBrowser.package/SingleCodeCriticResultList.class/instance/initialization/setTextModelForTransformationRule_.st A Tool-CriticBrowser.package/SingleCodeCriticResultList.class/instance/private/diffSeparator.st A Tool-CriticBrowser.package/SingleCodeCriticResultList.class/instance/private/diffTextForChange_.st Log Message: ----------- 60334 19479 Typo in name attribute of GRVariableAssignedLiteralRule https://pharo.fogbugz.com/f/cases/19479 19478 Criticsbrowser shows a refactoring class name instead of the text diff https://pharo.fogbugz.com/f/cases/19478 19438 Widen tolerance for DelayScheduler timing tests https://pharo.fogbugz.com/f/cases/19438 http://files.pharo.org/image/60/60334.zip

Dec. 21, 2016

Re: [Pharo-dev] MQTT for Pharo

by phil＠highoctane.be

Sven, I am currently working with IoT and MQTT is necessary. At this point I use mosquitto as the broker and your Pharo client is nice to have and I will test it and give you feedback. I've got a working microPython codebase so can compare what is in there (this for the LoPy device): Thx for the module! Phil On Wed, Dec 21, 2016 at 12:15 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > MQTT is a light-weight publish/subscribe messaging protocol, originally > created around 1998. It is now an official open industry ISO standard. It > is perfect for large-scale Internet of Things applications and high > performance mobile messaging. > > The publish/subscribe messaging pattern requires a message broker. The > broker is responsible for distributing messages to interested clients based > on the topic of a message. Parties communicating with each other over MQTT > would all be clients in different roles, like producers and consumers, > using the broker as middleware. > > Many client libraries for different programming languages and multiple > brokers/servers are available. Facebook Messenger and Amazon AWS IOT are > two users, among many others. > > > A good client library for Pharo was not yet available. I started a new > MQTT project and I am looking for collaborators to help me finish it. The > official specification is quite readable and there is a lot of information > available (see the References/Links section at the end). > > > Right now, a first version of the following features is available: > > - reading & writing of all 14 binary packet types > > - an experimental client with support for connection open/close, ping, > subscribe/unsubscribe, QoS levels 0 (at most once), 1 (at least once) and 2 > (exactly once) for application (publish) messages in both directions, > message/package IDs and keep alive (heartbeat) > > - unit tests, for packet reading/writing and for clients against 3 > publicly available sandbox/test brokers > > Basically, the code works but needs polishing and maturing. Also, it might > be useful to experiment with alternative client API design. Not all > features are yet implemented. It would also be nice to implement an actual > server/broker, not to replace production quality servers, but as a proof of > concept and tools during development. > > > Code > > http://smalltalkhub.com/#!/~SvenVanCaekenberghe/MQTT/ > > Right now, documentation is limited, but there are class comments and the > most important public API methods are commented too. There is no Metacello > configuration yet, just load the 3 packages. > > > References/Links > > - http://mqtt.org > - https://en.wikipedia.org/wiki/MQTT > - http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html > - https://github.com/mqtt/mqtt.github.io/wiki/software > - http://mosquitto.org > - https://github.com/emqtt/emqttd > - http://kamilfb.github.io/mqtt-spy/ > - https://github.com/eclipse/paho.mqtt-spy/wiki > - https://eclipse.org/paho/ > - https://eclipse.org/paho/clients/c/embedded/ > - http://www.rabbitmq.com/mqtt.html > - https://vernemq.com > - https://www.ibm.com/developerworks/community/ > blogs/c565c720-fe84-4f63-873f-607d87787327/entry/mqtt_security > > > Sandbox/test Servers/Brokers > > iot.eclipse.org:1883 > test.mosquitto.org:1883 > broker.mqtt-dashboard.com:1883 > > > Sven > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > >

Dec. 21, 2016

Re: [Pharo-dev] MQTT for Pharo

by Henrik Johansen

Hi Sven! One thing I noticed when testing the RabbitMQ client with keepalive > 0, was connection being closed and all subscriptions lost when receiving large payloads, due to timeout before the keepalive packet could be sent before waiting to receive next object. I see the default in ExperimentalClient is to disregard ConnectionTimedOut when that happens, and resend a ping. Are MQTT servers generally more lenient wrt dropping subscriptions once the timeout occurs, or will that lead to no new data being received from the broker? (Also, doesn't there need to be a guarantee that timeout < keepalive when keepalive is > 0, for this logic to work as intended?) Cheers, Henry > On 21 Dec 2016, at 12:15 , Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > MQTT is a light-weight publish/subscribe messaging protocol, originally created around 1998. It is now an official open industry ISO standard. It is perfect for large-scale Internet of Things applications and high performance mobile messaging. > > The publish/subscribe messaging pattern requires a message broker. The broker is responsible for distributing messages to interested clients based on the topic of a message. Parties communicating with each other over MQTT would all be clients in different roles, like producers and consumers, using the broker as middleware. > > Many client libraries for different programming languages and multiple brokers/servers are available. Facebook Messenger and Amazon AWS IOT are two users, among many others. > > > A good client library for Pharo was not yet available. I started a new MQTT project and I am looking for collaborators to help me finish it. The official specification is quite readable and there is a lot of information available (see the References/Links section at the end). > > > Right now, a first version of the following features is available: > > - reading & writing of all 14 binary packet types > > - an experimental client with support for connection open/close, ping, subscribe/unsubscribe, QoS levels 0 (at most once), 1 (at least once) and 2 (exactly once) for application (publish) messages in both directions, message/package IDs and keep alive (heartbeat) > > - unit tests, for packet reading/writing and for clients against 3 publicly available sandbox/test brokers > > Basically, the code works but needs polishing and maturing. Also, it might be useful to experiment with alternative client API design. Not all features are yet implemented. It would also be nice to implement an actual server/broker, not to replace production quality servers, but as a proof of concept and tools during development. > > > Code > > http://smalltalkhub.com/#!/~SvenVanCaekenberghe/MQTT/ > > Right now, documentation is limited, but there are class comments and the most important public API methods are commented too. There is no Metacello configuration yet, just load the 3 packages. > > > References/Links > > - http://mqtt.org > - https://en.wikipedia.org/wiki/MQTT > - http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html > - https://github.com/mqtt/mqtt.github.io/wiki/software > - http://mosquitto.org > - https://github.com/emqtt/emqttd > - http://kamilfb.github.io/mqtt-spy/ > - https://github.com/eclipse/paho.mqtt-spy/wiki > - https://eclipse.org/paho/ > - https://eclipse.org/paho/clients/c/embedded/ > - http://www.rabbitmq.com/mqtt.html > - https://vernemq.com > - https://www.ibm.com/developerworks/community/blogs/c565c720-fe84-4f63-873f-… > > > Sandbox/test Servers/Brokers > > iot.eclipse.org:1883 > test.mosquitto.org:1883 > broker.mqtt-dashboard.com:1883 > > > Sven > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > >

Dec. 21, 2016

MQTT for Pharo

by Sven Van Caekenberghe

Hi, MQTT is a light-weight publish/subscribe messaging protocol, originally created around 1998. It is now an official open industry ISO standard. It is perfect for large-scale Internet of Things applications and high performance mobile messaging. The publish/subscribe messaging pattern requires a message broker. The broker is responsible for distributing messages to interested clients based on the topic of a message. Parties communicating with each other over MQTT would all be clients in different roles, like producers and consumers, using the broker as middleware. Many client libraries for different programming languages and multiple brokers/servers are available. Facebook Messenger and Amazon AWS IOT are two users, among many others. A good client library for Pharo was not yet available. I started a new MQTT project and I am looking for collaborators to help me finish it. The official specification is quite readable and there is a lot of information available (see the References/Links section at the end). Right now, a first version of the following features is available: - reading & writing of all 14 binary packet types - an experimental client with support for connection open/close, ping, subscribe/unsubscribe, QoS levels 0 (at most once), 1 (at least once) and 2 (exactly once) for application (publish) messages in both directions, message/package IDs and keep alive (heartbeat) - unit tests, for packet reading/writing and for clients against 3 publicly available sandbox/test brokers Basically, the code works but needs polishing and maturing. Also, it might be useful to experiment with alternative client API design. Not all features are yet implemented. It would also be nice to implement an actual server/broker, not to replace production quality servers, but as a proof of concept and tools during development. Code http://smalltalkhub.com/#!/~SvenVanCaekenberghe/MQTT/ Right now, documentation is limited, but there are class comments and the most important public API methods are commented too. There is no Metacello configuration yet, just load the 3 packages. References/Links - http://mqtt.org - https://en.wikipedia.org/wiki/MQTT - http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html - https://github.com/mqtt/mqtt.github.io/wiki/software - http://mosquitto.org - https://github.com/emqtt/emqttd - http://kamilfb.github.io/mqtt-spy/ - https://github.com/eclipse/paho.mqtt-spy/wiki - https://eclipse.org/paho/ - https://eclipse.org/paho/clients/c/embedded/ - http://www.rabbitmq.com/mqtt.html - https://vernemq.com - https://www.ibm.com/developerworks/community/blogs/c565c720-fe84-4f63-873f-… Sandbox/test Servers/Brokers iot.eclipse.org:1883 test.mosquitto.org:1883 broker.mqtt-dashboard.com:1883 Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Dec. 21, 2016

[pharo-project/pharo-core] 258c2c: 60333

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 258c2c569dd82ba6184a5bd6facfd13aa0d172da https://github.com/pharo-project/pharo-core/commit/258c2c569dd82ba6184a5bd6… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-12-21 (Wed, 21 Dec 2016) Changed paths: M BaselineOfMorphic.package/BaselineOfMorphic.class/instance/actions/postload_package_.st A Monticello.package/MonticelloBootstrap.class/README.md A Monticello.package/MonticelloBootstrap.class/class/instance-creation/bootstrapDefault.st A Monticello.package/MonticelloBootstrap.class/class/instance-creation/inDirectory_.st A Monticello.package/MonticelloBootstrap.class/definition.st A Monticello.package/MonticelloBootstrap.class/instance/accessing/directory_.st A Monticello.package/MonticelloBootstrap.class/instance/accessing/localRepository.st A Monticello.package/MonticelloBootstrap.class/instance/bootstrapping/bootstrap.st A Monticello.package/MonticelloBootstrap.class/instance/bootstrapping/createWorkingCopies.st A Monticello.package/MonticelloBootstrap.class/instance/bootstrapping/loadBootstrapPackageNamed_.st A Monticello.package/MonticelloBootstrap.class/instance/bootstrapping/loadBootstrapPackages.st A Monticello.package/MonticelloBootstrap.class/instance/bootstrapping/loadBootstrapPackagesNamed_.st A Monticello.package/MonticelloBootstrap.class/instance/bootstrapping/loadPackageNamed_.st A Monticello.package/MonticelloBootstrap.class/instance/bootstrapping/loadPackageVersion_.st A Monticello.package/MonticelloBootstrap.class/instance/bootstrapping/loadPackagesNamed_.st A Monticello.package/MonticelloBootstrap.class/instance/versions/bootstrapVersionsExcept_.st A Monticello.package/MonticelloBootstrap.class/instance/versions/bootstrapVersionsSatisfying_.st A Monticello.package/MonticelloBootstrap.class/instance/versions/fileNameForPackageNamed_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60332.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60333.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60332.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60333.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60333 19484 BaselineOfMorphic references unexisting class https://pharo.fogbugz.com/f/cases/19484 19483 Add bootstrap specific code in Monticello https://pharo.fogbugz.com/f/cases/19483 http://files.pharo.org/image/60/60333.zip

Dec. 21, 2016

[pharo-project/pharo-core]

by GitHub

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

Dec. 21, 2016

Re: [Pharo-dev] Epicea user experience report

by Denis Kudriashov

2016-12-21 8:03 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > I think I would prefer to not have to think about this choice at all when > in the world menu level. The user interface from the Epicea window already > allows me to switch between current session and all sessions, and usually > the decision of what to look at is based on whether I find what I am > looking for or not. So, rather then asking the user to think about it > upfront, I would prefer to have one command that opens the Epicea window on > the current session and allow the user to dive deeper. This would also > imply that we would have only one command in the menu item. What do you > think? > +1

Dec. 21, 2016

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

by Esteban Lorenzano

would be possible to have one of your crashing images? so I can testâ¦ because one of my problems is that Iâm not able to reproduce the problem when I try, and is hard to fix blindly... Esteban > On 21 Dec 2016, at 08:09, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > I had plenty of elements in my Roassal visualization, and on some point it just crashed. > I have the impression that having many elements and / or animations (as in the case of Johan Fabry) triggers the crash. > > Alexandre > > >> On Dec 20, 2016, at 9:12 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> So what was your crash problem? >> >> >> On Tue, Dec 20, 2016 at 8:43 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> so did it work? >>> Is there something that we should do? >> >> I had no problem, but as Henrik and Peter said, the problem is likely to be more complex >> >> Alexandre >> >> >>> >>> On Fri, Dec 16, 2016 at 5:06 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> Okay, tryingâ¦ >>> >>> Alexandre >>> >>> >>>> On Dec 16, 2016, at 4:40 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: >>>> >>>> According to crash.dmp TRMorph>drawOn: draws an image using FormCanvas>>#image:at:sourceRect:rule: at a coordinate represented by a Float point. >>>> Try to round it to integer point. >>>> >>>> Cheers, >>>> Alex >>>> >>>> On 16 December 2016 at 16:34, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>> Hi! >>>> >>>> Vincent and I are experiencing many crashes from GrafPort>copyBits. It crashes every couple of minutes. >>>> >>>> I know that not much can be done so far. Stability is my biggest concern with Pharo :-( >>>> I use the latest VM. >>>> >>>> Cheers, >>>> Alexandre >>>> >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)list.inf.unibe.ch >>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>>> >>>> >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Dec. 21, 2016

Re: [Pharo-dev] [Moose-dev] Too frequent crashes :-(

by Tudor Girba

Hi Nicolai, Thanks for the explanation! Peter said that his fix works for Windows. Why would this fix only work for Windows? And what can we do for other platforms? Cheers, Doru > On Dec 21, 2016, at 8:48 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > Am 21.12.2016 8:10 vorm. schrieb "Alexandre Bergel" <alexandre.bergel(a)me.com>: > I had plenty of elements in my Roassal visualization, and on some point it just crashed. > I have the impression that having many elements and / or animations (as in the case of Johan Fabry) triggers the crash. > > > One problem, the one peter (partly) fixed, is n issue with bitblt, Cairo (as a surface plugin) and garbage collection. > Bitblt my call the surface plugin to request some information about the Form. > NB-based ffi for Cairo just called gen. asm code. But with UFFI, we now callback to Smalltalk code, which may trigger a GC. > So every time bitblt, makes a call to the surface plugin (Cairo) and this callback allocates a new ST-Object, the GC may run and moves(!)the objects, to which bitblt still holds a reference. > Accessing this objects in bitblt, after the callback returns (may) result in a segfault. > Depending on the concrete bltoperation, the object memory layout, the size(!) of the initial Cairo surface. > With peters fix/hack, the code does not crash but it still may access and operates on moved objects. > Pining the objects may help, but you need to know where in the (vm image) code a form is used for drawing, and if it is a real form or external data managed by the surface plugin. > And of course, when to "unpin" the object. > > A saver way would be, to just disable any GC during the executing of the callback, if it was called by a plugin (here:bitblt) > > > > Alexandre > > > > On Dec 20, 2016, at 9:12 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > > > So what was your crash problem? > > > > > > On Tue, Dec 20, 2016 at 8:43 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > > so did it work? > > > Is there something that we should do? > > > > I had no problem, but as Henrik and Peter said, the problem is likely to be more complex > > > > Alexandre > > > > > > > > > > On Fri, Dec 16, 2016 at 5:06 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > > Okay, tryingâ¦ > > > > > > Alexandre > > > > > > > > > > On Dec 16, 2016, at 4:40 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > > > > > > > > According to crash.dmp TRMorph>drawOn: draws an image using FormCanvas>>#image:at:sourceRect:rule: at a coordinate represented by a Float point. > > > > Try to round it to integer point. > > > > > > > > Cheers, > > > > Alex > > > > > > > > On 16 December 2016 at 16:34, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > > > Hi! > > > > > > > > Vincent and I are experiencing many crashes from GrafPort>copyBits. It crashes every couple of minutes. > > > > > > > > I know that not much can be done so far. Stability is my biggest concern with Pharo :-( > > > > I use the latest VM. > > > > > > > > Cheers, > > > > Alexandre > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > > Alexandre Bergel http://www.bergel.eu > > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Moose-dev mailing list > > > > Moose-dev(a)list.inf.unibe.ch > > > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > > > > > > > > > > > > > -- > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > Alexandre Bergel http://www.bergel.eu > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > -- www.tudorgirba.com www.feenk.com "Quality cannot be an afterthought."

Dec. 21, 2016