Re: [Pharo-dev] About the infinite debugger

I have more special cases where debugger hangs: 19662 , 19928 , 20274

Re: [Pharo-dev] About the infinite debugger

Hi. Good job guys. I just checked my case 19848 . And it is now fixed. Thanks 2018-06-29 15:48 GMT+01:00 Guillermo Polito : > Hi all, > > during today's sprint we

Re: [Pharo-dev] [rmod] About the infinite debugger

Thanks Paul - I’d forgotten about that option (been using the close all to right option). It’s just jarring - but worse is that none of the debuggers (even the first one) having anything useful in them... other than the error msg in the title. So you have to start all over again. Still, it

Re: [Pharo-dev] [rmod] About the infinite debugger

Hi Tim, Just in the event you didn't know there is an option in the World menu to close all the open debuggers. Its in the "Windows" section, about half way down. Paul Tim Mackinnon wrote > ... > > On the plus side - its rare that you crash you image and then have to > recover changes -

Re: [Pharo-dev] New Iceberg Version 1.2.1

Only adding a small detail, the Metacello expression is used to generate the project that is offered. Also I see it as the Detached head status for projects that are loaded using Metacello. Maybe we should display the dirtiness in other way, but I think that is not a problem. It is normal that a

Re: [Pharo-dev] New Iceberg Version 1.2.1

Hi, I'll write down some of the reasons of the project's design, like that I can afterwards copy paste it in the wiki :). First, this design did not came up from an egg. We worked on it for about two months. And it is thought to be backwards compatible and manage lots of metacello

[Pharo-dev] [Pharo 7.0-dev] Build #1161: Modified the code to be similar to #select:thenDo:.

There is a new Pharo build available! The status of the build #1161 was: SUCCESS. The Pull Request #1651 was integrated: "Modified the code to be similar to #select:thenDo:." Pull request url: https://github.com/pharo-project/pharo/pull/1651 Issue Url:

Re: [Pharo-dev] [Pharo 7.0-dev] Build #1160: Integrating Iceberg v1.2.1

yes. I find the message (SUCCESS or FAILURE) a bit misleading: it means some tests failed (usually the ones related to network problems). Cheers, Esteban > On 7 Aug 2018, at 12:32, Norbert Hartl wrote: > > Is it the case that as soon as a mail like this (let’s assume it would have > been a

Re: [Pharo-dev] Minheadless trial

Guys - do keep pushing on this - I think its quite important in this world of serverless… it shows we are very relevant. +10 > On 7 Aug 2018, at 13:36, Esteban Lorenzano wrote: > > I’m slowly working on that VM because we want it to be the default for Pharo > 8. > In our vision, it should be

Re: [Pharo-dev] Minheadless trial

I’m slowly working on that VM because we want it to be the default for Pharo 8. In our vision, it should be a responsibility of the image to start or not a graphical UI, so we are preparing (we have been preparing to it for years, actually) to achieve this behaviour. To make this work, we need

Re: [Pharo-dev] New Iceberg Version 1.2.1

Forgot one thing. I find the new project feature quite intrusive. It will add those file to all repos unasked. So I have a lot of dirty projects I have no write access to. How is this supposed to work. Isn’t it better to assume defaults and add an option to add project files? Norbert > Am

Re: [Pharo-dev] New Iceberg Version 1.2.1

Great, thanks! I used 1.2.0 a few days ago and I had some problems: - some repos like voyage had a .properties file in the repo with content „{}“. This made the repo unusable. The only thing noticed is that in the repo view in iceberg the packages were named Voyage-Core.package instead of

Re: [Pharo-dev] [Pharo 7.0-dev] Build #1160: Integrating Iceberg v1.2.1

Is it the case that as soon as a mail like this (let’s assume it would have been a success) arrives at the mailing list there is a new pharo image on get.pharo.org that has it? Norbert > Am 07.08.2018 um 12:07 schrieb ci-pharo-ci-jenki...@inria.fr: > > There is a new

[Pharo-dev] [Pharo 7.0-dev] Build #1160: Integrating Iceberg v1.2.1

There is a new Pharo build available! The status of the build #1160 was: FAILURE. The Pull Request #1672 was integrated: "Integrating Iceberg v1.2.1" Pull request url: https://github.com/pharo-project/pharo/pull/1672 Issue Url: https://pharo.fogbugz.com/f/cases/22297 Build Url:

[Pharo-dev] New Iceberg Version 1.2.1

New Iceberg Version 1.2.1 [ https://github.com/pharo-vcs/iceberg/releases/tag/v1.2.0 + https://github.com/pharo-vcs/iceberg/releases/tag/v1.2.1] Thanks to all brave users, issue reporters, and contributors :). This version includes the implementation of projects. Projects are a way of defining

Re: [Pharo-dev] [rmod] About the infinite debugger

Also, we have found that once the problem starts the image will present bad behavior from that on. Sometimes it can be fixed by restarting the UIProcess, but it is a brute force process. You have to do it many times. It is true that we cannot assert that the bug is not in other places. On Tue,

Re: [Pharo-dev] [rmod] About the infinite debugger

This is a good writeup - however I get infinite debuggers when not running tests too? So I’m wondering if there are multiple problems - or if this hints at a wider issue? Its not all of the time - but when you get it it, it seems to happen over and over again. Its possible its when using

Re: [Pharo-dev] [rmod] About the infinite debugger

Hello, We have implemented a "patch" for Pharo 7, that is already integrated. I have created a slice to backport the "patch" to Pharo6. Basically, the previous situation is the following: - In the normal execution everything works, the problem is during the execution of over. - To implement

Re: [Pharo-dev] Minheadless trial

What keeps you from doing a pull request to opensmalltalk-vm ? > Am 07.08.2018 um 07:47 schrieb Esteban Lorenzano : > > Hi Ben, > > Sorry for coming here so late, I didn’t see this thread before. > I already have a working minheadless branch that was adapted to Eliot’s > process. > It was