[Pharo-dev] Is it possible to add an existing github repository from within the image or does one have to clone on the command line?

SLSIA. I want to clone gitfiletree://github.com/ThierryGoubier/filetree.git but would love to do it form the image and not have to visit the command line. Is this possible yet? _,,,^..^,,,_ best, Eliot

Re: [Pharo-dev] SessionManager Questions

demarey wrote > Do you need to compute the priority dynamically? No. demarey wrote > What is the use case? I have a domain representing servers that takes the following two steps at startup: 1. I use to store objects representing servers. SimplePersistence materializes saved Server instances,

Re: [Pharo-dev] [CI] Cause of the random failures in the CI

Hi Cyril & Guille, > On Tue, Jun 19, 2018 at 5:06 PM Cyril Ferlicot D. > wrote: >> >> > Slightly off-topic, but I'm also wondering why the test scripts >> > download the VM again? Why not just use the one that is already in >> > vmtarget? >> > >> >> Because it is a vm linux and tests are

Re: [Pharo-dev] [CI] Cause of the random failures in the CI

Thanks Cyril, thanks for pushing. I've only given you permissions to re-run the build, so keep yourself and Vincent all the credit! > Slightly off-topic, but I'm also wondering why the test scripts > download the VM again? Why not just use the one that is already in > vmtarget? Yes, on one side

Re: [Pharo-dev] [CI] Cause of the random failures in the CI

On 19/06/2018 17:02, Alistair Grant wrote: > Hi Cyril, > Great work! > Thank you. Also thanks to Guille, Vincent, Marcus that helped to find the problem. > It would be nice if all the temporary files were in a single folder. > Cleaning the environment then becomes a matter of deleting that one

Re: [Pharo-dev] [CI] Cause of the random failures in the CI

Hi Cyril, On Tue, 19 Jun 2018 at 16:55, Cyril Ferlicot D. wrote: > > Hi, > > Since months now there are a lot of random failure on the CI making it > hard to work. > > There is different kind of failures: > - Network problems > - Failing tests > - Incomprehensible problems > > Now I don't see

Re: [Pharo-dev] [CI] Cause of the random failures in the CI

Well done. Great work. > On 19 Jun 2018, at 16:55, Cyril Ferlicot D. wrote: > > Hi, > > Since months now there are a lot of random failure on the CI making it > hard to work. > > There is different kind of failures: > - Network problems > - Failing tests > - Incomprehensible problems > > Now

[Pharo-dev] [CI] Cause of the random failures in the CI

Hi, Since months now there are a lot of random failure on the CI making it hard to work. There is different kind of failures: - Network problems - Failing tests - Incomprehensible problems Now I don't see much failure due to Network. I suppose the Inria infrastructure improved. Failing tests

Re: [Pharo-dev] [Pharo-users] [Ann] Iceberg v1.1.1

On 19/06/2018 09:06, Norbert Hartl wrote: >> We can agree that there is no hard rule on versionning, do we? But I >> try to follow the following guidelines (delta my own interpretation >> that adds some subjectivity :P) >> - Major Version will change when we break backwards compatibility >> -

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Launcher v1.2 release

> On 19 Jun 2018, at 16:01, Tudor Girba wrote: > > Great work! Indeed. Thank you. > Doru > > >> On Jun 19, 2018, at 3:55 PM, Christophe Demarey >> wrote: >> >> Hi all, >> >> I just released PharoLauncher 1.2. It includes a new windows installer that >> you can use without

[Pharo-dev] [ANN] TechTalk Dates second half 2018

Here are the next dates for the Pharo Techtalks. 12 Jul 2018: Pharo TechTalk: Machine Learning with TensorFlow and Pharo https://association.pharo.org/event-2973748 For the others we have no topic yet, but dates are pre-fixed to: 23 Aug 2018: Pharo TechTalk

Re: [Pharo-dev] [Pharo-users] [Ann] Iceberg v1.1.1

> Am 19.06.2018 um 15:22 schrieb Guillermo Polito : > > > On Tue, Jun 19, 2018 at 2:07 PM Norbert Hartl > wrote: > Hi, > > let me wear the project manager hat for a moment. > > let me too, because the fact that I'm younger does not mean I don't know, > right? :)

Re: [Pharo-dev] [Pharo-users] [Ann] Iceberg v1.1.1

Hi, Indeed. Something went amiss in this email exchange. But, I really do not think that you are in disagreement. Cheers, Doru > On Jun 19, 2018, at 4:09 PM, Christophe Demarey > wrote: > > Hi Norbert, > >> Le 19 juin 2018 à 14:06, Norbert Hartl a écrit : >> >> I have no use for an

Re: [Pharo-dev] [Pharo-users] [Ann] Iceberg v1.1.1

Hi Norbert, > Le 19 juin 2018 à 14:06, Norbert Hartl a écrit : > > I have no use for an environment where people only care about coding new cool > stuff. If it would be like this I would quit all my pharo businesses, move to > mainstream and would use pharo only for hobbyist projects because

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Launcher v1.2 release

Great work! Doru > On Jun 19, 2018, at 3:55 PM, Christophe Demarey > wrote: > > Hi all, > > I just released PharoLauncher 1.2. It includes a new windows installer that > you can use without administrator privileges as well as binary signing for OS > X and Windows. Also, Pharo Launcher is

[Pharo-dev] [ANN] Pharo Launcher v1.2 release

Hi all, I just released PharoLauncher 1.2. It includes a new windows installer that you can use without administrator privileges as well as binary signing for OS X and Windows. Also, Pharo Launcher is not anymore identified as ‘Pharo’ application and comes with its own icon. Here is the

Re: [Pharo-dev] [Pharo-users] [Ann] Iceberg v1.1.1

On Tue, Jun 19, 2018 at 2:07 PM Norbert Hartl wrote: > Hi, > > let me wear the project manager hat for a moment. > let me too, because the fact that I'm younger does not mean I don't know, right? :) > > Am 19.06.2018 um 10:59 schrieb Guillermo Polito >: > > Hi, > > About why 1.1.1 and not

[Pharo-dev] Pharo Sprints second half 2018

Pharo Sprints second half 2018 We organise one Pharo “Sprint” per month were we meet to work on boring issue tracker entries together. Goals of the next sprints: - Fix issues for Pharo7 - Backport important fixes to Pharo6 - Clean issue tracker to prepare for release

Re: [Pharo-dev] SessionManager Questions

> On Jun 19, 2018, at 2:50 AM, Christophe Demarey > wrote: > >> Le 17 juin 2018 à 20:20, Sean P. DeNigris a écrit : > >> Also, it seems that "higher" priority in SessionManager means a lower >> number! This seems opposite of both logic and precedent (see Process), no? > > You’re right. It

[Pharo-dev] [Pharo 7.0-dev] Build #1077: 22131-Begin-to-add-requirement-in-Athens-baseline

There is a new Pharo build available! The status of the build #1077 was: FAILURE. The Pull Request #1533 was integrated: "22131-Begin-to-add-requirement-in-Athens-baseline" Pull request url: https://github.com/pharo-project/pharo/pull/1533 Issue Url:

Re: [Pharo-dev] [Pharo-users] [Ann] Iceberg v1.1.1

Hi, let me wear the project manager hat for a moment. > Am 19.06.2018 um 10:59 schrieb Guillermo Polito : > > Hi, > > About why 1.1.1 and not 1.2.0. It’s not about cheap or not, but about > semantics :) for me „caring about semantics“ is just one of the top ten justifications developers use

[Pharo-dev] [Pharo 7.0-dev] Build #1076: 22173-Some-tests-are-rotten-in-OCContextTempMappingTest

There is a new Pharo build available! The status of the build #1076 was: FAILURE. The Pull Request #1572 was integrated: "22173-Some-tests-are-rotten-in-OCContextTempMappingTest" Pull request url: https://github.com/pharo-project/pharo/pull/1572 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #1075: 22170-Improve-comment-of-Jobs-package

There is a new Pharo build available! The status of the build #1075 was: SUCCESS. The Pull Request #1571 was integrated: "22170-Improve-comment-of-Jobs-package" Pull request url: https://github.com/pharo-project/pharo/pull/1571 Issue Url: https://pharo.fogbugz.com/f/cases/22170 Build

[Pharo-dev] [Pharo 7.0-dev] Build #1074: 22092-Add-part-of-the-keyboard-suport-for-the-menubar

There is a new Pharo build available! The status of the build #1074 was: SUCCESS. The Pull Request #1509 was integrated: "22092-Add-part-of-the-keyboard-suport-for-the-menubar" Pull request url: https://github.com/pharo-project/pharo/pull/1509 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #1073: 22160-Improve-StringthreeWayCompareTo

There is a new Pharo build available! The status of the build #1073 was: SUCCESS. The Pull Request #1564 was integrated: "22160-Improve-StringthreeWayCompareTo" Pull request url: https://github.com/pharo-project/pharo/pull/1564 Issue Url: https://pharo.fogbugz.com/f/cases/22160 Build

Re: [Pharo-dev] [Pharo-users] [Ann] Iceberg v1.1.1

Hi, About why 1.1.1 and not 1.2.0. It's not about cheap or not, but about semantics :) We can agree that there is no hard rule on versionning, do we? But I try to follow the following guidelines (delta my own interpretation that adds some subjectivity :P) - Major Version will change when we break

Re: [Pharo-dev] Promote new Pharo 7 VM?

Hi Esteban, On Mon, 18 Jun 2018 at 23:15, Esteban Lorenzano wrote: > > yes, why not :) Thanks! > but, remember the cycle: > > 1. two weeks in latest (that starts today) > 2. one month in stable 7.0 > 3. promote to stable 6.1 > > yes, is annoying, but is the scheme has worked the better to

[Pharo-dev] [Pharo 7.0-dev] Build #1072: 22167-Comment-Growl-package

There is a new Pharo build available! The status of the build #1072 was: SUCCESS. The Pull Request #1565 was integrated: "22167-Comment-Growl-package" Pull request url: https://github.com/pharo-project/pharo/pull/1565 Issue Url: https://pharo.fogbugz.com/f/cases/22167 Build Url:

Re: [Pharo-dev] SessionManager Questions

Hi Sean, > Le 17 juin 2018 à 20:20, Sean P. DeNigris a écrit : > > What is the SessionManager equivalent to `Smalltalk addToStartupList: self > after: AnotherClass`? > To do it manually, I don't see an easy way to query the priority/category of > AnotherClass(edited) SessionManager was