- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #721: 2449-Automatic-rewriting-of-deprecated-code-needs-feedback-to-developers-whose-code-is-changed
by ci-pharo-ci-jenkins2＠inria.fr Sept. 10, 2019

Sept. 10, 2019

There is a new Pharo build available! The status of the build #721 was: SUCCESS. The Pull Request #4539 was integrated: "2449-Automatic-rewriting-of-deprecated-code-needs-feedback-to-developers-whose-code-is-changed" Pull request url: https://github.com/pharo-project/pharo/pull/4539 Issue Url: https://github.com/pharo-project/pharo/issues/2449 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #720: 4542-update-rfEnsure
by ci-pharo-ci-jenkins2＠inria.fr Sept. 10, 2019

Sept. 10, 2019

There is a new Pharo build available! The status of the build #720 was: SUCCESS. The Pull Request #4543 was integrated: "4542-update-rfEnsure" Pull request url: https://github.com/pharo-project/pharo/pull/4543 Issue Url: https://github.com/pharo-project/pharo/issues/4542 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

when can we have DrTests
by ducasse Sept. 10, 2019

Sept. 10, 2019

I desesperately need it.

1 0

[Pharo 8.0] Build #719: Fix bug introduced with Spec2 migration.
by ci-pharo-ci-jenkins2＠inria.fr Sept. 10, 2019

Sept. 10, 2019

There is a new Pharo build available! The status of the build #719 was: FAILURE. The Pull Request #4538 was integrated: "Fix bug introduced with Spec2 migration." Pull request url: https://github.com/pharo-project/pharo/pull/4538 Issue Url: https://github.com/pharo-project/pharo/issues/4529 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/
by monty Sept. 10, 2019

Sept. 10, 2019

I will move it to github, if that makes things easier for everyone else. ___ montyos.wordpress.com > Sent: Wednesday, January 30, 2019 at 3:13 PM > From: "Sven Van Caekenberghe" <sven(a)stfx.eu> > To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Cc: monty <monty2(a)programmer.net> > Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/ > > > > > On 3 Oct 2018, at 07:43, monty <monty2(a)programmer.net> wrote: > > > > I am the principal maintainer of those projects, but any PharoExtras dev can contribute. And the blog below (which I plan on updating) provides additional information on them. > > Has there been any progress in this area ? > > It would be really great if this important project moved to GitHub. > > Sven > >

8 11

Slot definition API?
by ducasse Sept. 9, 2019

Sept. 9, 2019

Hi Iâm fixing the class definition parser and I have a question. Iâm stabilizing the API of CDSlotNode 1 âfirst' => LazyClassVariable default: 5. 2 âsecond' => InstanceVariableSlot. 3 âinstVar3â Here is a proposal slotdefinition(3) name ? variable name >>> âinstVar3' slotDefinition(2) slotClass? >>> InstanceVariableSlot slotDefinition(1) initializationMessage >>> 'default: 5â or better >>> Node(default: 5) if it exist S.

6 21

Step by step contribute
by Hilaire Sept. 9, 2019

Sept. 9, 2019

Hi, Reading the tutorial https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo * At https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo#solvi… I don't have Detached Working Copy but uncommited changes. * When I create a new branch from issue, should I use origin or pharo repo ? When I fill in the issue number with origin I have an INVALID-ISSUE title With pharo-project repo, it fetches the title correctly though. So I take this one. * https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo#step-… To push the change, (I need to pull to push?). A question is raised "pharo has ongoing modifications (uncommit changes) Indeed I did not commit. It was not mentioned in tutorial. Was it forgotten or do I miss something? So I commit it. Ah, now when I create the pull request, it complains the branch does not exist and I should commit before and push the changes. Likely I should not have commited in the first place. What should I do now? Hilaire -- Dr. Geo http://drgeo.eu

2 5

[Pharo 8.0] Build #718: 4535-Is-there-a-reason-new-completion-does-not-use-RBProgramNodeVisitor
by ci-pharo-ci-jenkins2＠inria.fr Sept. 9, 2019

Sept. 9, 2019

There is a new Pharo build available! The status of the build #718 was: SUCCESS. The Pull Request #4536 was integrated: "4535-Is-there-a-reason-new-completion-does-not-use-RBProgramNodeVisitor" Pull request url: https://github.com/pharo-project/pharo/pull/4536 Issue Url: https://github.com/pharo-project/pharo/issues/4535 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #717: 4530-Auto-completion-fail-on-thisContext
by ci-pharo-ci-jenkins2＠inria.fr Sept. 9, 2019

Sept. 9, 2019

There is a new Pharo build available! The status of the build #717 was: SUCCESS. The Pull Request #4531 was integrated: "4530-Auto-completion-fail-on-thisContext" Pull request url: https://github.com/pharo-project/pharo/pull/4531 Issue Url: https://github.com/pharo-project/pharo/issues/4530 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

possible Windows Update "1903" Iceberg problem
by Ben Coman Sept. 9, 2019

Sept. 9, 2019

IThis morning the May 2019 Windows Update "1903" forced itself onto my computer and now 64-bits Pharo seems to have a problem with git_remote_fetch() FFI callout. I no longer have a non-1903 machine to directly compare behaviour before "1903". Can someone familiar with this area with both "pre-1903" and "1903" machines triage whether "1903" is indeed the cause? A few other recent reports are noted here... https://github.com/pharo-project/pharo/issues/3418 cheers -ben

7 18