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

[Stephane Ducasse]

Thanks you!


On Mon, Sep 4, 2017 at 7:37 PM, p...@highoctane.be  wrote:
> Can be around.
>
> I did the MOOC once.
>
> Phil, missing ESUG :-(
>
> On Mon, Sep 4, 2017 at 7:34 PM, Myroslava Romaniuk 
> wrote:
>>
>> Hi I would like to help too, if possible.
>>
>> On 2 September 2017 at 22:33, Rene Paul Mages (ramix) 
>> 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
>>>
>>
>>
>>
>> --
>> З повагою,
>> Мирослава Романюк.
>
>

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

[p...@highoctane.be]

Can be around.

I did the MOOC once.

Phil, missing ESUG :-(

On Mon, Sep 4, 2017 at 7:34 PM, Myroslava Romaniuk 
wrote:

> Hi I would like to help too, if possible.
>
> On 2 September 2017 at 22:33, Rene Paul Mages (ramix) 
> 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
>>
>>
>
>
> --
> З повагою,
> Мирослава Романюк.
>

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

[Myroslava Romaniuk]

Hi I would like to help too, if possible.

On 2 September 2017 at 22:33, Rene Paul Mages (ramix) 
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
>
>


-- 
З повагою,
Мирослава Романюк.

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

[Alexandre Bergel]

Pretty cool!
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



> On Sep 3, 2017, at 8:54 PM, Tudor Girba  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.
> 
> 
> 
> 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."
> 

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

[Guillermo Polito]

On Thu, Aug 24, 2017 at 2:16 PM, Ben Coman  wrote:

>
>
> On Tue, Aug 22, 2017 at 11:51 PM, Guillermo Polito <
> guillermopol...@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*




*Web:* *http://guillep.github.io* 

*Phone: *+33 06 52 70 66 13

[Pharo-dev] Esteban's ChangeLog week of 28 August 2017

[estebanlm]

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=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