Re: [Pharo-dev] Beacon for Pharo 7

Hi Norbert 2018-05-25 23:50 GMT+03:00 Norbert Hartl : > Really?? Don‘t you think the overhead is massive compared to the gain? > I am sure that you were agreed with this when we push Beacon two yeas ago. But look at my explanation in previous mail. > > Norbert > > Am

Re: [Pharo-dev] Beacon for Pharo 7

2018-05-25 20:03 GMT+03:00 Stephan Eggermont : > Denis Kudriashov > wrote: > > > > Because when you will fix or improve Beacon-SysLog you will probably do > not > > want to update Beacon-Core version which will force you to update Pharo > > (where SysLog

Re: [Pharo-dev] Crash on GC garbageCollect

Esteban Lorenzano wrote: > > >> On 25 May 2018, at 23:48, Stephan Eggermont wrote: >> >> Esteban Lorenzano >> wrote: >>> that’s because 6.1 images still comes with an old VM. >>> I think I will backport the newer, but next week

Re: [Pharo-dev] Crash on GC garbageCollect

Hi Andreas, On Fri, May 25, 2018 at 1:24 AM, Andreas Brodbeck wrote: > Hi all > > I have a 6.0 image which crashes on garbage collect. If I run "Smalltalk > garbageCollect" it crashes. The crash log is attached. But I don't really > understand that crash log. I run it with a

[Pharo-dev] [Pharo 7.0-dev] Build #954: 21916-OSWindow-SDL2-leaks-because-there-are-strong-references-on-OSSDL2WindowHandle

There is a new Pharo build available! The status of the build #954 was: FAILURE. The Pull Request #1369 was integrated: "21916-OSWindow-SDL2-leaks-because-there-are-strong-references-on-OSSDL2WindowHandle" Pull request url: https://github.com/pharo-project/pharo/pull/1369 Issue Url:

Re: [Pharo-dev] Crash on GC garbageCollect

> On 25 May 2018, at 23:48, Stephan Eggermont wrote: > > Esteban Lorenzano > wrote: >> that’s because 6.1 images still comes with an old VM. >> I think I will backport the newer, but next week (testing time has passed, I >> think). > > You probably

Re: [Pharo-dev] Crash on GC garbageCollect

Esteban Lorenzano wrote: > that’s because 6.1 images still comes with an old VM. > I think I will backport the newer, but next week (testing time has passed, I > think). You probably want to include the TLS fix from this week for Win7 so github repos eork Stephan

Re: [Pharo-dev] Beacon for Pharo 7

Norbert Hartl wrote: > Really?? Don‘t you think the overhead is massive compared to the gain? As long as the baselines are nice trees, described only one level deep, it should be ok-ish. That never seems to be the case though, and as soon as you get diamond dependency issues

[Pharo-dev] [Pharo 7.0-dev] Build #953: 21983-Fixing-Slot-propagation-in-Traits-Tests

There is a new Pharo build available! The status of the build #953 was: SUCCESS. The Pull Request #1425 was integrated: "21983-Fixing-Slot-propagation-in-Traits-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/1425 Issue Url: https://pharo.fogbugz.com/f/cases/21983

Re: [Pharo-dev] Beacon for Pharo 7

Really?? Don‘t you think the overhead is massive compared to the gain? Norbert > Am 25.05.2018 um 21:08 schrieb Tudor Girba : > > Hi, > > Yes, we want to have the concrete loggers managed with separate baselines. I > would also put them in individual repositories. > >

Re: [Pharo-dev] Crash on GC garbageCollect

that’s because 6.1 images still comes with an old VM. I think I will backport the newer, but next week (testing time has passed, I think). cheers, Esteban > On 25 May 2018, at 17:02, Ben Coman wrote: > > There was a period where a new GC algorithm had some teething

Re: [Pharo-dev] Beacon for Pharo 7

Hi, Yes, we want to have the concrete loggers managed with separate baselines. I would also put them in individual repositories. Cheers, Doru > On May 25, 2018, at 5:58 PM, Denis Kudriashov wrote: > > > 2018-05-25 17:21 GMT+03:00 Stephan Eggermont :

[Pharo-dev] [Pharo 7.0-dev] Build #952: added an example to the method '->'

There is a new Pharo build available! The status of the build #952 was: FAILURE. The Pull Request #1427 was integrated: "added an example to the method '->'" Pull request url: https://github.com/pharo-project/pharo/pull/1427 Issue Url: https://pharo.fogbugz.com/f/cases/20315 Build Url:

Re: [Pharo-dev] feenk log

Very impressive!! Hope Bloc and Brick move along to be included in pharo soon!! Norbert > Am 25.05.2018 um 13:30 schrieb Tudor Girba : > > Hi, > > We were a bit silent the last couple of months. Quite a bit happened in the > meantime, so here is a summary (for more fine

Re: [Pharo-dev] Beacon for Pharo 7

Denis Kudriashov wrote: > > Because when you will fix or improve Beacon-SysLog you will probably do not > want to update Beacon-Core version which will force you to update Pharo > (where SysLog is not loaded). I seem to be missing something here. Why would you update the

Re: [Pharo-dev] Beacon for Pharo 7

2018-05-25 17:21 GMT+03:00 Stephan Eggermont : > Denis Kudriashov > wrote: > > Hi. > > > > I was looking at Beacon again to prepare integration. Some changes was > > needed in baseline for better granularity. So I send pull request > because I > > have no

Re: [Pharo-dev] Crash on GC garbageCollect

There was a period where a new GC algorithm had some teething issues, but those were resolved. Where did you get the newest VMs? The one from your report seems old... "VM: 201708271955" What platform are you on? How are your starting your Image? Can you move your development to a fresh download

Re: [Pharo-dev] Beacon for Pharo 7

Denis Kudriashov wrote: > Hi. > > I was looking at Beacon again to prepare integration. Some changes was > needed in baseline for better granularity. So I send pull request because I > have no permissions. > > But now I remember that we had idea to integrate only core part

[Pharo-dev] ImageReadWriter and GIFs

Hi guys, As mentioned in pharo-users, I am refactoring / fixing the implementation of GIFReadWriter, which currently doesn't work correctly. My primary motivation at the start came because I could not open animated GIFs in the World. I am close to having a solution, but could use some input from

[Pharo-dev] [Pharo 7.0-dev] Build #951: 21966-bindings-ok-to-use-array-of-associations

There is a new Pharo build available! The status of the build #951 was: SUCCESS. The Pull Request #1413 was integrated: "21966-bindings-ok-to-use-array-of-associations" Pull request url: https://github.com/pharo-project/pharo/pull/1413 Issue Url: https://pharo.fogbugz.com/f/cases/21966

[Pharo-dev] Beacon for Pharo 7

Hi. I was looking at Beacon again to prepare integration. Some changes was needed in baseline for better granularity. So I send pull request because I have no permissions. But now I remember that we had idea to integrate only core part of Beacon which requires MemoryLogger and TranscriptLogger.

[Pharo-dev] [Pharo 7.0-dev] Build #950: 21925-SharedPool-subclasses-should-not-trigger-class-not-referenced--QA-Rule-if-they-are-used

There is a new Pharo build available! The status of the build #950 was: FAILURE. The Pull Request #1381 was integrated: "21925-SharedPool-subclasses-should-not-trigger-class-not-referenced--QA-Rule-if-they-are-used" Pull request url: https://github.com/pharo-project/pharo/pull/1381

Re: [Pharo-dev] [SPAM] feenk log

"What is more important: To be happy, or to make happy?" My response: “To be happy by making happy”! ;) Sent from my iPad > On 25 May 2018, at 13:30, Tudor Girba wrote: > > "What is more important: To be happy, or to make happy?"

[Pharo-dev] [Pharo 7.0-dev] Build #949: 21965-SmaltlalkImagecompiler--use-globals-as-default-environment-not-just-self

There is a new Pharo build available! The status of the build #949 was: FAILURE. The Pull Request #1416 was integrated: "21965-SmaltlalkImagecompiler--use-globals-as-default-environment-not-just-self" Pull request url: https://github.com/pharo-project/pharo/pull/1416 Issue Url:

Re: [Pharo-dev] feenk log

Hi Tudor. Very impressive progress. I have one question about scrolling support. How it works or is it works with elements which are based on infinite layout like mentioned grid widget? Does grid implemented with PannableElement too? 2018-05-25 14:30 GMT+03:00 Tudor Girba

[Pharo-dev] feenk log

Hi, We were a bit silent the last couple of months. Quite a bit happened in the meantime, so here is a summary (for more fine grained announcements, you can follow us on Twitter): Bloc - Scrolling. We finally have a good scrolling support:

[Pharo-dev] [Pharo 7.0-dev] Build #948: 21956-tiny-cleanup-simplify-methods-related-to-pools-in-Class

There is a new Pharo build available! The status of the build #948 was: FAILURE. The Pull Request #1409 was integrated: "21956-tiny-cleanup-simplify-methods-related-to-pools-in-Class" Pull request url: https://github.com/pharo-project/pharo/pull/1409 Issue Url:

Re: [Pharo-dev] [Pharo-users] pharo location include korean charactor then look is not good.

I made the following quick changes: UnixEnvironment>>#environAt: index ^ (self environ at: index) ifNotNil: [ :string | string asByteArray utf8Decoded ] OSPlatform>>#currentWorkingDirectoryPathWithBuffer: aByteString ^ (self getPwdViaFFI: aByteString size:

[Pharo-dev] [Pharo 7.0-dev] Build #947: 21781-trait-composition-should-not-copy-slots-everytime-it-is-asked

There is a new Pharo build available! The status of the build #947 was: SUCCESS. The Pull Request #1253 was integrated: "21781-trait-composition-should-not-copy-slots-everytime-it-is-asked" Pull request url: https://github.com/pharo-project/pharo/pull/1253 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #946: 21954-cleanup-copyOfMethodDictionary-and-copyMethodDictionaryFrom

There is a new Pharo build available! The status of the build #946 was: FAILURE. The Pull Request #1408 was integrated: "21954-cleanup-copyOfMethodDictionary-and-copyMethodDictionaryFrom" Pull request url: https://github.com/pharo-project/pharo/pull/1408 Issue Url:

[Pharo-dev] Crash on GC garbageCollect

Hi all I have a 6.0 image which crashes on garbage collect. If I run "Smalltalk garbageCollect" it crashes. The crash log is attached. But I don't really understand that crash log. I run it with a 6.0 VM, tried it also with newest 6.1 VM and 7.0 VM, but always the same error. I read here in