September 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] The mooc is looking for forum moderators

by Myroslava Romaniuk

Hi I would like to help too, if possible. On 2 September 2017 at 22:33, Rene Paul Mages (ramix) <pharo(a)rmages.com> wrote: > > > Le 01/09/2017 Ã 11:40, Serge Stinckwich a Ã©crit : > > I should be able to help like last year. > > Count me also in the forum moderators team. > > -- > Amicalement. > Rene Paul Mages ( GnuPG_key 1024D/2CC455D9 ) > http://blog.pharo.fr > > -- Ð Ð¿Ð¾Ð²Ð°Ð³Ð¾Ñ, ÐÐ¸ÑÐ¾ÑÐ»Ð°Ð²Ð° Ð Ð¾Ð¼Ð°Ð½ÑÐº.

Sept. 4, 2017

Re: [Pharo-dev] [ann] moldable editor - transcript with adornments

by Alexandre Bergel

Pretty cool! -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Sep 3, 2017, at 8:54 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > We are happy to announce that the moldable editor helped us create a richer transcript: GT Transcript. > > The transcript is traditionally a stream of plain text. As we now have an elaborate editor, we can take advantage of it to help us display richer representations. > > The API is backward compatible with the existing transcript. To enable the new features, we introduced a builder. For example: > transcript nextPutAll: âsomethingâ > becomes > transcript next putAll: âsomethingâ > and after #next we can add multiple attributes that we want to affect the following insertion of a text. > > Below you can find an example detailing most of the API. The most notable additions is the support for expandable adornments. For example, #showException: provides an in-place expansion of the stack of the exception context. > > <transcript-api.png> > > To get an idea of how this tool can be useful, take a look at the following video showing the visual logging of a Bloc animation: > https://youtu.be/9VATYNaLwJY > > <transcript-animation.png> > > The code can be found in the new incarnation of GToolkit: > Iceberg enableMetacelloIntegration: true. > Metacello new > baseline: 'GToolkit'; > repository: 'github://feenkcom/gtoolkit/src'; > load. > > Cheers, > The feenk team > > -- > www.tudorgirba.com > www.feenk.com > > âSoftware has no shape. Actually, it has no one shape. It has many." >

Sept. 4, 2017

Re: [Pharo-dev] [ Pharo 70 ] Build 52 to 54

by Guillermo Polito

On Thu, Aug 24, 2017 at 2:16 PM, Ben Coman <btc(a)openinworld.com> wrote: > > > On Tue, Aug 22, 2017 at 11:51 PM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> Hi Marcus, >> >> Please, do not relaunch the build if there is a test failure. That >> simply does not fix the problem, it just adds noise. There are two >> problems: >> >> 1) we have some sporadic test failures (sometimes network, sometimes >> some mutex or delay issues). They do not happen all the time and >> that's why sometimes there is one or two failing tests. We should >> detect these tests and fix them to be more robust >> >> >> Note, is there some brave soul that would like to take action here? >> >> 2) sometimes the vm crashes while running the tests. We should detect >> the bug and fix it. >> >> >> Note, is there some brave soul that would like to take action here? >> >> Now, if we are integrating a fix, this means that the PR was **already >> validated as green**. That means that the integrated commit can be >> bootstrapped and tested (and all tests are green). >> >> Moreover, running the tests after integration (and its build color) >> does not change the integration in itself: the commit was already >> merged and pushed into the main branch, so even if it fails always, >> it's too late. > > > I thought the idea of CI was to merge into the main branch *after* the > tests pass. > It is the way we do it, nothing should be merged if tests are not green. BUT, we are also running the tests after merging, just because :). And it is in that second test-run when you may have some failing tests... > Why is the PR-branch not checked out to run the tests on...? > https://help.github.com/articles/checking-out-pull-requests-locally/ > > cheers -ben > > -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Sept. 4, 2017

Esteban's ChangeLog week of 28 August 2017

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 28 August 2017 to 3 September 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=28/8/2017&to=3/9/2017 ChangeLog ========= 29 August 2017: --------------- * I just released [Iceberg v0.5.7](https://github.com/pharo-vcs/iceberg/releases/tag/v0.5.7) with some minor (but necessary) fixes. * fixes cherry pick bug on multiple packages (issue #450) * indirectly fixes issues #403, #440 and #442 * fixes windows crashes (and from 0.5.6) * fixes "restore" clone * adds IceLog to query history * minor enhancements This version also updates 0.25.1 branch from [libgit2 bindings](https://github.com/pharo-vcs/libgit2-pharo-bindings/tree/v0.25.1), who makes Windows not crash :) Now, there are still a remaining problem which is: writing the index for windows is taking ages for pharo project, which means any huge project will also take ages... I need to dig into this more in detail :( cheers! Esteban

Sept. 4, 2017

Re: [Pharo-dev] State of 64bits? Errors during configuration loading

by Ben Coman

On Sat, Sep 2, 2017 at 2:31 AM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > On ven. 1 sept. 2017 at 20:24, Tim Mackinnon <tim(a)testit.works> wrote: > >> I've probably done 100 builds on 64bits - I've had one crash (reported >> here). >> >> So it's not common, but does happen. >> >> Tim >> >> Sent from my iPhone >> > > > We must be unlucky :) 2 builds, 2 vm crashes. > >> >> >> Perhaps something different in environments. What version of Ubuntu are you on? cheers -ben

Sept. 4, 2017

[ann] moldable editor - transcript with adornments

by Tudor Girba

Hi, We are happy to announce that the moldable editor helped us create a richer transcript: GT Transcript. The transcript is traditionally a stream of plain text. As we now have an elaborate editor, we can take advantage of it to help us display richer representations. The API is backward compatible with the existing transcript. To enable the new features, we introduced a builder. For example: transcript nextPutAll: âsomethingâ becomes transcript next putAll: âsomethingâ and after #next we can add multiple attributes that we want to affect the following insertion of a text. Below you can find an example detailing most of the API. The most notable additions is the support for expandable adornments. For example, #showException: provides an in-place expansion of the stack of the exception context. To get an idea of how this tool can be useful, take a look at the following video showing the visual logging of a Bloc animation: https://youtu.be/9VATYNaLwJY The code can be found in the new incarnation of GToolkit: Iceberg enableMetacelloIntegration: true. Metacello new baseline: 'GToolkit'; repository: 'github://feenkcom/gtoolkit/src'; load. Cheers, The feenk team -- www.tudorgirba.com www.feenk.com âSoftware has no shape. Actually, it has no one shape. It has many."

Sept. 3, 2017

Re: [Pharo-dev] [ Pharo 70 ] Build 83 PR 236 introduce-at-at-in-dictionary

by Henrik Nergaard

The Link to 236 points to something else that is not #at:at: in https://github.com/pharo-project/pharo/commit/00f8cff298cf359b63cee4ab1c0a8… Why are new sub dictionaries instansiated as a normal Dictionary instead of species/class? I would expect a sub-Dictionary be of the same class as its parent. Here is a test case: ---------- | dct key1 key2 subDct | dct := IdentityDictionary new. key1 := 'a'. key2 := key1 copy. dct at: #a at: key1 put: 1; at: #a at: key2 put: 2. subDct := dct at: #a. TestCase new assert: subDct size equals: 2; assert: (subDct at: key1) equals: 1; assert: (subDct at: key2) equals: 2 ---------- Best regards, Henrik ________________________________ Fra: Pharo-dev <pharo-dev-bounces(a)lists.pharo.org> pÃ¥ vegne av Stephane Ducasse <stepharo.self(a)gmail.com> Sendt: 3. september 2017 15:56:36 Til: Pharo Development List Emne: [Pharo-dev] [ Pharo 70 ] Build 83 PR 236 introduce-at-at-in-dictionary https://github.com/pharo-project/pharo/pull/236 https://pharo.fogbugz.com/f/cases/20203/

Sept. 3, 2017

[ Pharo 70 ] Build 83 PR 236 introduce-at-at-in-dictionary

by Stephane Ducasse

https://github.com/pharo-project/pharo/pull/236 https://pharo.fogbugz.com/f/cases/20203/

Sept. 3, 2017

Re: [Pharo-dev] The mooc is looking for forum moderators

by Rene Paul Mages (ramix)

Le 01/09/2017 Ã 11:40, Serge Stinckwich a Ã©crit : > I should be able to help like last year. Count me also in the forum moderators team. -- Amicalement. Rene Paul Mages ( GnuPG_key 1024D/2CC455D9 ) http://blog.pharo.fr

Sept. 2, 2017

About allDirectories vs. directories

by Stephane Ducasse

Hi I have been hacking a little page generator based on pillar for the mooc table of contents and I got surprised by the behavior of allDirectories it returns all the subdirectories including itself This is strange and inconsistent with the API in Behavior X = one level allX = deep below withAllX = deep below including me. subclasses allSubclasses withAllSubclasses So now when we do a deep we have to remov the first or scan the result to remove the receiver. I found that not nice. May be I miss something obvious such as .. which would be a child and return the parent = the starting container. Stef

Sept. 2, 2017