- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Crash on GC garbageCollect

by Stephan Eggermont

Esteban Lorenzano <estebanlm(a)gmail.com> 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

May 25, 2018

Re: [Pharo-dev] Beacon for Pharo 7

by Stephan Eggermont

Norbert Hartl <norbert(a)hartl.name> 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 the duplication of volatile information creates a lot of commit ripple Iâd would like to see a description of how that is supposed to work with all the duplicated baselines and repos. Stephan

May 25, 2018

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

by ci-pharo-ci-jenkins2＠inria.fr

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 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 25, 2018

Re: [Pharo-dev] Beacon for Pharo 7

by Norbert Hartl

Really?? Donât you think the overhead is massive compared to the gain? Norbert > Am 25.05.2018 um 21:08 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > > 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 <dionisiydk(a)gmail.com> wrote: >> >> >> 2018-05-25 17:21 GMT+03:00 Stephan Eggermont <stephan(a)stack.nl>: >> Denis Kudriashov <dionisiydk(a)gmail.com> >> 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 of Beacon >>> which requires MemoryLogger and TranscriptLogger. And we wanted to manage >>> logger backends using separate baselines. So we need separate repos to have >>> separate versioning. >> >> Why would you want separate baselines for that? And on top of that separate >> repos? >> >> 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). >> >> >> Stephan > > -- > www.tudorgirba.com > www.feenk.com > > "In a world where everything is moving ever faster, > one might have better chances to win by moving slower." > > > > >

May 25, 2018

Re: [Pharo-dev] Crash on GC garbageCollect

by Esteban Lorenzano

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 <btc(a)openInWorld.com> wrote: > > 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 of latest 6.1 Image & VM and report if that has any problems? > http://pharo.org/download <http://pharo.org/download> > > HTH > cheers -ben > > On 25 May 2018 at 16:24, Andreas Brodbeck <dassi(a)mindclue.ch <mailto:dassi@mindclue.ch>> 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 6.0 VM, tried it also with newest 6.1 VM and 7.0 VM, but always the same error. > > I read here in the list about crash problems with GC, memory leaks and similar, but I really don't see what I could do. > > Any pointers in which direction I could investigate? > > Thanks and cheers, > Andreas > > -- > Andreas Brodbeck > www.mindclue.ch <http://www.mindclue.ch/> > > >

May 25, 2018

Re: [Pharo-dev] Beacon for Pharo 7

by Tudor Girba

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 <dionisiydk(a)gmail.com> wrote: > > > 2018-05-25 17:21 GMT+03:00 Stephan Eggermont <stephan(a)stack.nl>: > Denis Kudriashov <dionisiydk(a)gmail.com> > 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 of Beacon > > which requires MemoryLogger and TranscriptLogger. And we wanted to manage > > logger backends using separate baselines. So we need separate repos to have > > separate versioning. > > Why would you want separate baselines for that? And on top of that separate > repos? > > 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). > > > Stephan -- www.tudorgirba.com www.feenk.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."

May 25, 2018

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

by ci-pharo-ci-jenkins2＠inria.fr

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: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 25, 2018

Re: [Pharo-dev] feenk log

by Norbert Hartl

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 <tudor(a)tudorgirba.com>: > > 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: > https://twitter.com/feenkcom/status/991690465224331264 > This might sound like a trivial feature, but it turns out it is not. We had a bug that forced us to rethink the support quite deeply in order to be able to debug it. To do this, we now can simulate time in Bloc, which is really cool: > https://twitter.com/feenkcom/status/989797367523233797 > https://twitter.com/feenkcom/status/988753142299938817 > (as a side note, the bug we fought with was the last > > - Pannable element is a combination of a scrollable element with a scalable element, and it offers the possibility either to zoom in/out + scroll, or to fit screen and resize when the parent resizes. > > - PDF, SVG, PNG, JPG export (based on the underlying Moz2D support): > https://twitter.com/feenkcom/status/976580153802358786 > https://twitter.com/feenkcom/status/976578060429484032 > > - Better curve support: > https://twitter.com/feenkcom/status/990967109193781249 > https://twitter.com/feenkcom/status/990971530615107584 > > - Better debugging support for understanding bounds: > https://twitter.com/feenkcom/status/989138457288167424 > > ---- > Brick > ---- > > - We now have simple list and columned list widgets. The list is both fast and scalable and supports rows of variable heights: > https://twitter.com/feenkcom/status/984744251920658432 > https://twitter.com/feenkcom/status/984143821192744961 > > - Basic tab widget: > https://twitter.com/feenkcom/status/974420432240685062 > > - Looks: a mechanism for specifying element-specific composition and interaction. > > ---- > GT > ---- > > - Documenter saw some major improvements. Just a reminder, Documenter is the tool that enables live programming and previews directly within Pillar documents. > We now have a capability similar to notebooks like Jupyter: > https://twitter.com/feenkcom/status/996310432225820672 > We use it extensively to document our code. For example, here is a tutorial about playing with looks in Bloc: > https://twitter.com/feenkcom/status/973899862482866176 > And we can also express whole tutorials based on Epicea: > https://twitter.com/feenkcom/status/999975333972541440 > > - Diagrammer. We now have better editing support for detailed things such as arrow head: > https://twitter.com/feenkcom/status/976341449267531776 > While Diagrammer is apparently a tool for diagrams, it has a rather generic design that can be utilized for all sorts of use cases. For example, one side effect is that now all elements can be visually edited: > https://twitter.com/feenkcom/status/982656456968241152 > > - Mondrian: Using the new pannable element, we can now zoom in/out and scroll, and we can also set element to fit screen. We can also drag elements around. > > - Inspector: we now have an initial support for multiple views associated with an object. The support is similar to the one from the current inspector. > > > Have fun, > The feenk team > > -- > www.tudorgirba.com > www.feenk.com > > "What is more important: To be happy, or to make happy?" > >

May 25, 2018

Re: [Pharo-dev] Beacon for Pharo 7

by Stephan Eggermont

Denis Kudriashov <dionisiydk(a)gmail.com> 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 baseline for that? Stephan

May 25, 2018

Re: [Pharo-dev] Beacon for Pharo 7

by Denis Kudriashov

2018-05-25 17:21 GMT+03:00 Stephan Eggermont <stephan(a)stack.nl>: > Denis Kudriashov <dionisiydk(a)gmail.com> > 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 of Beacon > > which requires MemoryLogger and TranscriptLogger. And we wanted to manage > > logger backends using separate baselines. So we need separate repos to > have > > separate versioning. > > Why would you want separate baselines for that? And on top of that separate > repos? > 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). > Stephan > > >

May 25, 2018