Re: [Pharo-dev] [Pharo6][Issue Tracker] Please check Issues tagged Milestone-6.0

2017-02-20 Thread denker
> On 20 Feb 2017, at 08:30, denker wrote: > > Hi, > > We have right now 112 issues tagged to be fixed before we can release Pharo6: > > https://pharo.fogbugz.com/f/filters/1192/6-0-All > > > It would be nice if

Re: [Pharo-dev] WeakValueDictionary: shouldn't be "absent" after GC?

2017-02-20 Thread p...@highoctane.be
This makes sense, no? | dictionary | dictionary := WeakValueDictionary with: 'hello' -> nil copy. "Smalltalk garbageCollect." r:={ dictionary values includes: nil. dictionary at: 'hello'. dictionary at: 'hello' ifAbsent: [ 'absent' ]. dictionary at: 'hello' ifAbsentPut: [ 'put' ]. }. r and I get

Re: [Pharo-dev] [pharo-project/pharo-core] 986ba2: 60402

2017-02-20 Thread p...@highoctane.be
There are quite a few Themers + hard coded colors in GT. Maybe someone from the GT team can pair for an hour or two with me so that we can get this done. I can do this in the evening CET as I am pretty busy this week (managed to have Pharo a large part of my daily work now). Phil On Mon, Feb

[Pharo-dev] WeakValueDictionary: shouldn't be "absent" after GC?

2017-02-20 Thread Martin Dias
Hi. The answer of: | dictionary | dictionary := WeakValueDictionary with: 'hello' -> 'world' copy. Smalltalk garbageCollect. { dictionary values includes: nil. dictionary at: 'hello'. dictionary at: 'hello' ifAbsent: [ 'absent' ]. dictionary at: 'hello' ifAbsentPut: [ 'put' ]. } is: #(true nil

[Pharo-dev] [pharo-project/pharo-core]

2017-02-20 Thread GitHub
Branch: refs/tags/60404 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] ff896f: 60404

2017-02-20 Thread GitHub
Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: ff896f34e7b21806530e6d8b9668d454533732d2 https://github.com/pharo-project/pharo-core/commit/ff896f34e7b21806530e6d8b9668d454533732d2 Author: Jenkins Build Server Date:

Re: [Pharo-dev] [pharo-project/pharo-core] 69aea4: 60403

2017-02-20 Thread denker
> > Log Message: > --- > 60403 > Moose > http://files.pharo.org/image/60/60403.zip > > This actually is a merge for GT… with: The version moves the inspector to FastTable. More precisely it moves the Raw presentation and the presentations for collections to FastTable. For that it

[Pharo-dev] [pharo-project/pharo-core]

2017-02-20 Thread GitHub
Branch: refs/tags/60403 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 69aea4: 60403

2017-02-20 Thread GitHub
Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 69aea4253803150fbd46f2d53c8f6c2a44d16462 https://github.com/pharo-project/pharo-core/commit/69aea4253803150fbd46f2d53c8f6c2a44d16462 Author: Jenkins Build Server Date:

Re: [Pharo-dev] [pharo-project/pharo-core] 986ba2: 60402

2017-02-20 Thread Sven Van Caekenberghe
Thanks. Not that it is a big deal, but the default background does not really match, but that might be taste as well. > On 20 Feb 2017, at 17:41, p...@highoctane.be wrote: > > I have fixed the spotter styling but need to get a 6.0 and move it there. > > > > On Mon, Feb 20, 2017 at 5:25 PM,

[Pharo-dev] [pharo-project/pharo-core]

2017-02-20 Thread GitHub
Branch: refs/tags/60402 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 986ba2: 60402

2017-02-20 Thread GitHub
Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 986ba23013b6a211ee2f02693494240aec1bf922 https://github.com/pharo-project/pharo-core/commit/986ba23013b6a211ee2f02693494240aec1bf922 Author: Jenkins Build Server Date:

Re: [Pharo-dev] Development dashboard for pharo-project repositories

2017-02-20 Thread Sean P. DeNigris
Rafael Luque wrote > I expect you enjoy it and get insights about the Pharo community. Very cool :) This should get much more interesting when/if we are submitting fixes to Pharo core via Pull requests. - Cheers, Sean -- View this message in context:

Re: [Pharo-dev] WorkingSession UUID looks "sketchy"

2017-02-20 Thread Sean P. DeNigris
Guillermo Polito wrote >> So if image crashes or I am running it headlessly without saving I am >> actually still on the same session. >> > Peter, how can we make this an actionable point? Yes, that doesn't sound good! - Cheers, Sean -- View this message in context:

[Pharo-dev] [pharo-project/pharo-core] fa70f9: 60401

2017-02-20 Thread GitHub
Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: fa70f974f905df2af78bce55c4d9d00d732055ff https://github.com/pharo-project/pharo-core/commit/fa70f974f905df2af78bce55c4d9d00d732055ff Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

2017-02-20 Thread GitHub
Branch: refs/tags/60401 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] WorkingSession UUID looks "sketchy"

2017-02-20 Thread Guillermo Polito
On Mon, Feb 6, 2017 at 6:54 PM, Peter Uhnak wrote: > 1. Regarding WorkingSession > > The WS' comment claims "On each image startup the current session is > invalidated and a new session is created.", > but in reality WS is reset only save, and not on startup... isn't > that

[Pharo-dev] [ANN] Pharo Sprint March 3

2017-02-20 Thread Marcus Denker
Pharo Sprint March 3 We will organize a Pharo sprint / Moose dojo March, 03, starting at 10:00am. (Local Time Paris). Goals of this sprint: • Clean issue tracker to prepare for release Pharo6 • remove Pharo6 tag from not-important cases • Check Pharo5 Issues and pending

Re: [Pharo-dev] Segmentation fault while installing Scale

2017-02-20 Thread Guillermo Polito
Maybe it's something to do with his gentoo's version of some library? libc? It looks like it's some problem of Pharo in gentoo, not necessarily scale. On Sun, Feb 12, 2017 at 11:05 AM, Sven Van Caekenberghe wrote: > Note that he managed to run the System Report UI, which means his

Re: [Pharo-dev] 2 seconds default time limit for tests

2017-02-20 Thread Ben Coman
When we come to do this, could there be some mechanism to scale *all* these timeouts. For example, to investigate VM crashes we might want to run all tests under a debug VM which would greatly extend the time taken for each test, and it would be a pain to get a bundle of false positives. Perhaps

Re: [Pharo-dev] Catalog loading in Spotter

2017-02-20 Thread Sven Van Caekenberghe
> On 20 Feb 2017, at 10:30, Pavel Krivanek wrote: > > > > 2017-02-20 10:27 GMT+01:00 Guillermo Polito : > As far as I remember, the main problem was not bandwidth but a blocking and > non-responsive UI. > Imagine I'm in the university, or

Re: [Pharo-dev] Catalog loading in Spotter

2017-02-20 Thread Pavel Krivanek
2017-02-20 10:27 GMT+01:00 Guillermo Polito : > As far as I remember, the main problem was not bandwidth but a blocking > and non-responsive UI. > Imagine I'm in the university, or in a company with a proxy. And I forget > to set the proxy. Then, while spotter tries to

Re: [Pharo-dev] Catalog loading in Spotter

2017-02-20 Thread Guillermo Polito
As far as I remember, the main problem was not bandwidth but a blocking and non-responsive UI. Imagine I'm in the university, or in a company with a proxy. And I forget to set the proxy. Then, while spotter tries to fetch catalog entries, it would block the image and throw a timeout error some

Re: [Pharo-dev] Esteban's ChangeLog week of 13 February 2017

2017-02-20 Thread Esteban Lorenzano
> On 20 Feb 2017, at 08:00, esteba...@gmail.com wrote: > > Hello! > > This is my weekly ChangeLog, from 13 February 2017 to 19 February 2017. > You can see it in a better format by going here: > http://log.smallworks.eu/web/search?from=13/2/2017=19/2/2017 > > ChangeLog > = > > 17