[Pharo-dev] File List -- MNU: RubTextEditor>>doIt

[Martin McClure]

So I open Pharo 5, and the *very* *first* thing I do is to open a file 
list, select a file that contains the Metacello expression to load my 
project, and select "Do it" from the menu.


And get MNU: RubTextEditor>>doIt

:-(

This was on Linux, in case that makes a difference.

I couldn't quickly track down how this is *supposed* to work.

Regards,

-Martin

Re: [Pharo-dev] fogbugz process Check seems to be stuck

[Sven Van Caekenberghe]

Hi Alistair,

Everything is OK. 

Once Issue Validation succeeds, your slice is ready to be integrated (a review 
by another human would help too). Integration itself is a manual process done 
by an integrator.

The reason there was a second check is that every time a new build is done, all 
open issues are rechecked.

It got stuck, but also unstuck automatically.

HTH,

Sven

> On 18 May 2016, at 07:03, Alistair Grant  wrote:
> 
> Hi All,
> 
> Would someone mind clarifying the issue process for me.
> 
> pharo.org states:
> 
> In success, the state will be "Fix Reviewed by the Monkey". This is
> where humans come into the picture: your code needs to be reviewed, if
> possible by 2-3 people. If they accept it, the state moves to "Fix to
> Include", after which it will be committed to the development branch as
> soon as possible.
> 
> After I submitted the slice to issue 18248 the monkey successfully
> reviewed it and then assigned it back to me.
> 
> Then a little while later the monkey complained that the "Check seems to
> be stuck. I will try again".  It looks like the second validation also
> succeeded.
> 
> Do I need to do something to initiate the human review, or should I be
> taking some other action?
> 
> Thanks,
> Alistair
> 
> 

[Pharo-dev] fogbugz process Check seems to be stuck

[Alistair Grant]

Hi All,

Would someone mind clarifying the issue process for me.

pharo.org states:

In success, the state will be "Fix Reviewed by the Monkey". This is
where humans come into the picture: your code needs to be reviewed, if
possible by 2-3 people. If they accept it, the state moves to "Fix to
Include", after which it will be committed to the development branch as
soon as possible.

After I submitted the slice to issue 18248 the monkey successfully
reviewed it and then assigned it back to me.

Then a little while later the monkey complained that the "Check seems to
be stuck. I will try again".  It looks like the second validation also
succeeded.

Do I need to do something to initiate the human review, or should I be
taking some other action?

Thanks,
Alistair

Re: [Pharo-dev] about spurious conflicts

[Denis Kudriashov]

Yes.
It should be solved by 18251


2016-05-17 22:08 GMT+02:00 stepharo :

> Hi
>
>
> while migrating some of the issues from 50 to 60, I noticed that many of
> the conflicts are
>
> not conflicts since the code of both methods and the protocols are the
> same.
>
> Does anybody experienced the same?
>
> Here are some examples and I'm puzzled.
>
>
> https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/417//artifact/validationReport.html
>
>
> https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/418//artifact/validationReport.html
>
>
> Stef
>
>
>

Re: [Pharo-dev] about spurious conflicts

[Max Leske]

> On 17 May 2016, at 22:08, stepharo  wrote:
> 
> Hi
> 
> 
> while migrating some of the issues from 50 to 60, I noticed that many of the 
> conflicts are
> 
> not conflicts since the code of both methods and the protocols are the same.
> 
> Does anybody experienced the same?
> 
> Here are some examples and I'm puzzled.
> 
> https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/417//artifact/validationReport.html
> 
> https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/418//artifact/validationReport.html
> 
> 
> Stef
> 
> 

Yes, I saw the same with Fuel. But a simple manual merge with the latest 
version fixed that.

Re: [Pharo-dev] about spurious conflicts

[Nicolai Hess]

2016-05-17 22:08 GMT+02:00 stepharo :

> Hi
>
>
> while migrating some of the issues from 50 to 60, I noticed that many of
> the conflicts are
>
> not conflicts since the code of both methods and the protocols are the
> same.
>
> Does anybody experienced the same?
>
> Here are some examples and I'm puzzled.
>
>
> https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/417//artifact/validationReport.html
>
>
> https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/418//artifact/validationReport.html
>
>
The packages, these slices depends on, are older than what we have in the
image.
This packages were only in the inbox. Every new package version (Nautilus
for example) we
included afterwards, don't have these changes.

I am afraid all this changes needs to be redone again.



>
> Stef
>
>
>

[Pharo-dev] [pharo-project/pharo-core] 96698c: 60010

[GitHub]

  Branch: refs/heads/6.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: 96698cbeb27393860effe85738f937fb4dd96338
  
https://github.com/pharo-project/pharo-core/commit/96698cbeb27393860effe85738f937fb4dd96338
  Author: Jenkins Build Server 
  Date:   2016-05-17 (Tue, 17 May 2016)

  Changed paths:
M Collections-Strings.package/String.class/instance/converting/repeat_.st
M Collections-Tests.package/StringTest.class/instance/testing - 
converting/testRepeat.st
R ScriptLoader60.package/ScriptLoader.class/instance/pharo - 
scripts/script60009.st
A ScriptLoader60.package/ScriptLoader.class/instance/pharo - 
scripts/script60010.st
R ScriptLoader60.package/ScriptLoader.class/instance/pharo - 
updates/update60009.st
A ScriptLoader60.package/ScriptLoader.class/instance/pharo - 
updates/update60010.st
M 
ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st

  Log Message:
  ---
  60010
18229 Allow String>>#repeat: to repeat a string 0 times
https://pharo.fogbugz.com/f/cases/18229

http://files.pharo.org/image/60/60010.zip

[Pharo-dev] [pharo-project/pharo-core]

[GitHub]

  Branch: refs/tags/60010
  Home:   https://github.com/pharo-project/pharo-core

[Pharo-dev] about spurious conflicts

[stepharo]

Hi


while migrating some of the issues from 50 to 60, I noticed that many of 
the conflicts are


not conflicts since the code of both methods and the protocols are the 
same.


Does anybody experienced the same?

Here are some examples and I'm puzzled.

https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/417//artifact/validationReport.html

https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/418//artifact/validationReport.html


Stef

Re: [Pharo-dev] UnifiedFFI Interrupted system call error on OSX

[stepharo]

Le 17/5/16 à 21:33, Jan van de Sandt a écrit :

Hi,

I'm helping with the port of LibGit [1] from Pharo 4 to Pharo 5 [2].


BIG THANKS
This project provides Smalltalk bindings for the libgit2 library. Very 
useful for better Git support in Pharo. The port means using the new 
UnifiedFFI instead of NativeBoost.


The project is still in the alpha stage but a lot of the libgit2 
features are already accessible. Some libgit2 calls access the 
network. For example to clone a repository or to push a commit. The 
calls that use https work on Linux and on Windows but on OSX we always 
get the following error in Pharo 5:


LGit_GIT_ERROR: Failed to connect to github.com : 
Interrupted system call.


In Pharo4/NB this error does not occur. Could this be an issue in UFFI 
or perhaps in the VM ?


To reproduce the problem in Pharo 5 (after loading [2]):


| repo |
repo := LGitRepository on: 'my-test-repo' asFileReference.
repo cloneHttps: 'https://github.com/theseion/LibGit.git'


Jan.

[1] https://github.com/theseion/LibGit
[2] https://github.com/jvdsandt/LibGit

Re: [Pharo-dev] more robust tests

[stepharo]

thanks.

I would like to have the system in a state where we can release the next 
day :)



Le 17/5/16 à 21:43, Andrei Chis a écrit :

We'll have a look.

Cheers,
Andrei

On Sun, May 15, 2016 at 3:06 PM, stepharo > wrote:


Hi

While integrating some changes in P6.0 I got such tests failing.
Only failing on mac.

Could you check?

Stef


Regression

GT.EventRecorder.Tests.Core.GTEventRecorderTest.testAddCollector3
(from GT-EventRecorder-Tests)

Failing for the past 1 build (Since Unstable#7 )
Took 0.96 sec.
add description
Error Message

Assertion failed
Stacktrace

GTEventRecorderTest(TestAsserter)>>assert:
GTEventRecorderTest(TestAsserter)>>deny:
GTEventRecorderTest>>assertReceiverSemaphore
GTEventRecorderTest>>waitForDelivery
GTEventRecorderTest>>testAddCollector3
GTEventRecorderTest(TestCase)>>performTest


Stef

Re: [Pharo-dev] more robust tests

[Andrei Chis]

We'll have a look.

Cheers,
Andrei

On Sun, May 15, 2016 at 3:06 PM, stepharo  wrote:

> Hi
>
> While integrating some changes in P6.0 I got such tests failing. Only
> failing on mac.
>
> Could you check?
>
> Stef
>
>
> Regression
>
> GT.EventRecorder.Tests.Core.GTEventRecorderTest.testAddCollector3 (from
> GT-EventRecorder-Tests)
>
> Failing for the past 1 build (Since Unstable#7 )
> Took 0.96 sec.
> add description
> Error Message
>
> Assertion failed
> Stacktrace
>
> GTEventRecorderTest(TestAsserter)>>assert:
> GTEventRecorderTest(TestAsserter)>>deny:
> GTEventRecorderTest>>assertReceiverSemaphore
> GTEventRecorderTest>>waitForDelivery
> GTEventRecorderTest>>testAddCollector3
> GTEventRecorderTest(TestCase)>>performTest
>
>
> Stef
>
>
>

[Pharo-dev] UnifiedFFI Interrupted system call error on OSX

[Jan van de Sandt]

Hi,

I'm helping with the port of LibGit [1] from Pharo 4 to Pharo 5 [2]. This
project provides Smalltalk bindings for the libgit2 library. Very useful
for better Git support in Pharo. The port means using the new UnifiedFFI
instead of NativeBoost.

The project is still in the alpha stage but a lot of the libgit2 features
are already accessible. Some libgit2 calls access the network. For example
to clone a repository or to push a commit. The calls that use https work on
Linux and on Windows but on OSX we always get the following error in Pharo
5:

LGit_GIT_ERROR: Failed to connect to github.com: Interrupted system call.

In Pharo4/NB this error does not occur. Could this be an issue in UFFI or
perhaps in the VM ?

To reproduce the problem in Pharo 5 (after loading [2]):


| repo |
repo := LGitRepository on: 'my-test-repo' asFileReference.
repo cloneHttps: 'https://github.com/theseion/LibGit.git'


Jan.

[1] https://github.com/theseion/LibGit
[2] https://github.com/jvdsandt/LibGit

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

[Alistair Grant]

On Tue, May 17, 2016 at 06:16:07PM +0200, Esteban Lorenzano wrote:
> there was a problem with the repositorio (I forget to make it public). 
> now you should be able to commit (of course, you still need an smalltalkhub 
> user :P)
> 
> Esteban

Thanks!  I've successfully uploaded the slice now.

There are two versions, the first when Max uploaded it as part of
looking in to the problem, and the second the one I just uploaded.

They should be the same, of course. :-)

Cheers,
Alistair


> 
> > On 17 May 2016, at 17:54, Alistair Grant  wrote:
> > 
> > On Tue, May 17, 2016 at 09:11:07AM +0200, Max Leske wrote:
> >>On 17 May 2016, at 09:09, Sven Van Caekenberghe  wrote:
> >>On 17 May 2016, at 06:48, Max Leske  wrote:
> >>No, it’s publicly writeable. You may have found a bug. Can you link 
> >> to
> >>the .mcz you’re trying to upload? Then we can give it a try.
> >> 
> >> 
> >>Don't you have to be part of team Pharo ?
> >> 
> >> 
> >> Hm… then “public” is certainly a misleading label...
> > 
> > Who should I contact to be added to the team?
> > 
> > Thanks,
> > Alistair
> > 
> > 
> 
> 

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

[Esteban Lorenzano]

there was a problem with the repositorio (I forget to make it public). 
now you should be able to commit (of course, you still need an smalltalkhub 
user :P)

Esteban

> On 17 May 2016, at 17:54, Alistair Grant  wrote:
> 
> On Tue, May 17, 2016 at 09:11:07AM +0200, Max Leske wrote:
>>On 17 May 2016, at 09:09, Sven Van Caekenberghe  wrote:
>>On 17 May 2016, at 06:48, Max Leske  wrote:
>>No, it’s publicly writeable. You may have found a bug. Can you link to
>>the .mcz you’re trying to upload? Then we can give it a try.
>> 
>> 
>>Don't you have to be part of team Pharo ?
>> 
>> 
>> Hm… then “public” is certainly a misleading label...
> 
> Who should I contact to be added to the team?
> 
> Thanks,
> Alistair
> 
> 

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

[Alistair Grant]

On Tue, May 17, 2016 at 09:11:07AM +0200, Max Leske wrote:
> On 17 May 2016, at 09:09, Sven Van Caekenberghe  wrote:
> On 17 May 2016, at 06:48, Max Leske  wrote:
> No, it’s publicly writeable. You may have found a bug. Can you link to
> the .mcz you’re trying to upload? Then we can give it a try.
> 
> 
> Don't you have to be part of team Pharo ?
> 
> 
> Hm… then “public” is certainly a misleading label...

Who should I contact to be added to the team?

Thanks,
Alistair

[Pharo-dev] [pharo-project/pharo-core]

[GitHub]

  Branch: refs/tags/60009
  Home:   https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 2c1c3f: 60009

[GitHub]

  Branch: refs/heads/6.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: 2c1c3fbfb52006c6c1d6aadc6518a42230638777
  
https://github.com/pharo-project/pharo-core/commit/2c1c3fbfb52006c6c1d6aadc6518a42230638777
  Author: Jenkins Build Server 
  Date:   2016-05-17 (Tue, 17 May 2016)

  Changed paths:
A 
Reflectivity-Tools.package/extension/CompiledMethod/instance/hasBreakpoint.st
A 
Reflectivity-Tools.package/extension/RBProgramNode/instance/hasBreakpoint.st
R Reflectivity.package/extension/CompiledMethod/instance/hasBreakpoint.st
R Reflectivity.package/extension/RBProgramNode/instance/hasBreakpoint.st
M 
ReleaseTests.package/ReleaseTest.class/instance/testing/testKeyClassesArePresentInStartupList.st
R ScriptLoader60.package/ScriptLoader.class/instance/pharo - 
scripts/script60008.st
A ScriptLoader60.package/ScriptLoader.class/instance/pharo - 
scripts/script60009.st
R ScriptLoader60.package/ScriptLoader.class/instance/pharo - 
updates/update60008.st
A ScriptLoader60.package/ScriptLoader.class/instance/pharo - 
updates/update60009.st
M 
ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st

  Log Message:
  ---
  60009
18191 remove FFI classes from 
ReleaseTest>>#testKeyClassesArePresentInStartupList
https://pharo.fogbugz.com/f/cases/18191

18201 Reflectivity depends on Relfectivity-Tools
https://pharo.fogbugz.com/f/cases/18201

http://files.pharo.org/image/60/60009.zip

Re: [Pharo-dev] PhD Thesis offer

[jannik laval]

nop,

I don't know these lists.

Jannik

2016-05-15 22:49 GMT+02:00 stepharo :

> did you forward it to spanish speaking mailing lists?
>
>
> Stef
>
> Le 4/5/16 à 12:37, jannik laval a écrit :
>
> Dear friends,
>
> I am looking for a french student (or someone speaking french) who wants
> to engage in a CIFRE PhD thesis (it is a thesis with a french company).
>
> The subject is attached to the mail.
>
> Best regards,
> --
> ~~Jannik Laval~~
> Enseignant-chercheur
> Responsable Pédagogique Licence Coordonnateur de Projet en Système
> d'Information
> IUT Lumière, Université Lyon Lumière
> laboratoire DISP
> http://www.jannik-laval.eu
> http://www.phratch.com
> http://www.approchealpes.info
>
>
>


-- 
~~Jannik Laval~~
Enseignant-chercheur
Responsable Pédagogique Licence Coordonnateur de Projet en Système
d'Information
IUT Lumière, Université Lyon Lumière
laboratoire DISP
http://www.jannik-laval.eu
http://www.phratch.com
http://www.approchealpes.info

Re: [Pharo-dev] PharoVM-spur32 test newVMTestImage --> Pharo 2.0 ??

[Esteban Lorenzano]

newVMtestImage is old, yes. 
we are not using it for now because I’m running tests in github, before build 
it (but I’m missing windows tests, a situation I will fix soon (™))

Esteban

> On 17 May 2016, at 12:44, Ben Coman  wrote:
> 
> In the PharoVM-spur32 CI build, newVMTestImage.sh [1] doesn't seem current?
> 
>> wget http://files.pharo.org/vm/src/vm-test-image-20.zip 1>&2
>> unzip vm-test-image-20.zip -d vm-test-image 1>&2
>> 
>> wget http://files.pharo.org/sources/PharoV20.sources 
>> --output-document=vm-test-image/PharoV20.sources 1>&2
>> 
>> PHARO_IMAGE=`find vm-test-image -name \*.image` 1>&2
>> echo $PHARO_IMAGE
> 
> cheers -ben
> 
> [1] 
> https://ci.inria.fr/pharo/job/PharoVM-spur32/Architecture=32,Slave=vm-builder-linux/ws/cog/image/newVMTestImage.sh/*view*/
> 

[Pharo-dev] PharoVM-spur32 test newVMTestImage --> Pharo 2.0 ??

[Ben Coman]

In the PharoVM-spur32 CI build, newVMTestImage.sh [1] doesn't seem current?

> wget http://files.pharo.org/vm/src/vm-test-image-20.zip 1>&2
> unzip vm-test-image-20.zip -d vm-test-image 1>&2
>
> wget http://files.pharo.org/sources/PharoV20.sources 
> --output-document=vm-test-image/PharoV20.sources 1>&2
>
> PHARO_IMAGE=`find vm-test-image -name \*.image` 1>&2
> echo $PHARO_IMAGE

cheers -ben

[1] 
https://ci.inria.fr/pharo/job/PharoVM-spur32/Architecture=32,Slave=vm-builder-linux/ws/cog/image/newVMTestImage.sh/*view*/

Re: [Pharo-dev] Moving fogbugz entries from Pharo 5 to Pharo 6

[Pavel Krivanek]

I copied all current Pharo 6 packages to the Pharo60 and Pharo60Inbox
repositories. It should solve at least part of the problems.

-- Pavel

2016-05-17 11:08 GMT+02:00 Denis Kudriashov :

> Copy slice from Monticello Browser also copies dependencies.
> But now I always got merge conflicts from Monkey while no conflicts when I
> merge it manually
>
> 2016-05-17 9:06 GMT+02:00 Sven Van Caekenberghe :
>
>> Yes, it is fragile.
>>
>> It's a bit like an application that saves a document as a couple of
>> files. When you later copy only one file, you break the format.
>>
>> > On 17 May 2016, at 08:37, Peter Uhnák  wrote:
>> >
>> > But how come saving a slice in the beginning also saves the dependents?
>> I thought it acted like a package.
>> >
>> > Wouldn't this be a bug then? It is certainly bug-inducing.
>> >
>> > On Tue, May 17, 2016 at 8:12 AM, Sven Van Caekenberghe 
>> wrote:
>> >
>> > > On 17 May 2016, at 08:01, Clément Bera 
>> wrote:
>> > >
>> > > Well I tried that and sometimes the integrator can't integrate
>> because of a "Missing ancestor".
>> >
>> > You have to copy all dependents as well, a slice is just an empty
>> holder. But I guess you already know.
>> >
>> > > I guess I will do what you say for my bugs and when the problem
>> arises again I will ask again with a concrete example.
>> > >
>> > > Nvm
>> > >
>> > > On Mon, May 16, 2016 at 3:34 PM, Peter Uhnák 
>> wrote:
>> > > Is there a problem in simply adding Inbox50 repo and clicking on the
>> "Copy" button to put it to Inbox60? Or am I missing something?
>> > >
>> > > Peter
>> > >
>> > > On Mon, May 16, 2016 at 2:12 PM, Clément Bera 
>> wrote:
>> > > Hello,
>> > >
>> > > I have a problem in several bugs I opened on the bug tracker. When I
>> opened them, Pharo 6 development has not started, so the slices were
>> committed in the Pharo 5 inbox. As Pharo 5 was in stabilization phasis for
>> release, my slices were not integrated but postponed to Pharo 6 (which I
>> understand and accept). But since now the development is in Pharo 6, the
>> monkey checks the slice in Pharo 6 inbox and can't find my slices because
>> they are in Pharo 5 inbox. See for example 18039 or 17451.
>> > >
>> > > What is the right way to move the slices from Pharo 5 inbox to Pharo
>> 6 inbox ? I don't want to end up in a situation where it is not possible to
>> integrate my slice because of a "Missing ancestor", so how can I move the
>> slices from Pharo 5 inbox to Pharo 6 inbox without having that problem ?
>> > >
>> > > Thanks.
>> > >
>> > >
>> >
>> >
>> >
>>
>>
>>
>

Re: [Pharo-dev] Moving fogbugz entries from Pharo 5 to Pharo 6

[Denis Kudriashov]

Copy slice from Monticello Browser also copies dependencies.
But now I always got merge conflicts from Monkey while no conflicts when I
merge it manually

2016-05-17 9:06 GMT+02:00 Sven Van Caekenberghe :

> Yes, it is fragile.
>
> It's a bit like an application that saves a document as a couple of files.
> When you later copy only one file, you break the format.
>
> > On 17 May 2016, at 08:37, Peter Uhnák  wrote:
> >
> > But how come saving a slice in the beginning also saves the dependents?
> I thought it acted like a package.
> >
> > Wouldn't this be a bug then? It is certainly bug-inducing.
> >
> > On Tue, May 17, 2016 at 8:12 AM, Sven Van Caekenberghe 
> wrote:
> >
> > > On 17 May 2016, at 08:01, Clément Bera  wrote:
> > >
> > > Well I tried that and sometimes the integrator can't integrate because
> of a "Missing ancestor".
> >
> > You have to copy all dependents as well, a slice is just an empty
> holder. But I guess you already know.
> >
> > > I guess I will do what you say for my bugs and when the problem arises
> again I will ask again with a concrete example.
> > >
> > > Nvm
> > >
> > > On Mon, May 16, 2016 at 3:34 PM, Peter Uhnák 
> wrote:
> > > Is there a problem in simply adding Inbox50 repo and clicking on the
> "Copy" button to put it to Inbox60? Or am I missing something?
> > >
> > > Peter
> > >
> > > On Mon, May 16, 2016 at 2:12 PM, Clément Bera 
> wrote:
> > > Hello,
> > >
> > > I have a problem in several bugs I opened on the bug tracker. When I
> opened them, Pharo 6 development has not started, so the slices were
> committed in the Pharo 5 inbox. As Pharo 5 was in stabilization phasis for
> release, my slices were not integrated but postponed to Pharo 6 (which I
> understand and accept). But since now the development is in Pharo 6, the
> monkey checks the slice in Pharo 6 inbox and can't find my slices because
> they are in Pharo 5 inbox. See for example 18039 or 17451.
> > >
> > > What is the right way to move the slices from Pharo 5 inbox to Pharo 6
> inbox ? I don't want to end up in a situation where it is not possible to
> integrate my slice because of a "Missing ancestor", so how can I move the
> slices from Pharo 5 inbox to Pharo 6 inbox without having that problem ?
> > >
> > > Thanks.
> > >
> > >
> >
> >
> >
>
>
>

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

[Max Leske]

> On 17 May 2016, at 09:09, Sven Van Caekenberghe  wrote:
> 
>> 
>> On 17 May 2016, at 06:48, Max Leske  wrote:
>> 
>>> 
>>> On 16 May 2016, at 22:49, Alistair Grant  wrote:
>>> 
>>> Hi,
>>> 
>>> I'm attempting to upload a SLICE for issue 18248 to:
>>> 
>>> MCHttpRepository
>>> location: 'http://smalltalkhub.com/mc/Pharo/Pharo60Inbox/main'
>>> user: ''
>>> password: ''
>>> 
>>> with username: Alistair
>>> 
>>> following the instructions in the video at
>>> https://www.youtube.com/watch?v=iFomI-7h4qQ (from the Contributing to
>>> Pharo video at pharo.org).
>>> 
>>> but am getting a Error 500 Internal Server Error response.
>>> 
>>> I can log in to the smalltalkhub.com website without any problems, so I
>>> believe my password is correct.
>>> 
>>> Do I need to be granted write access?  The Pharo60Inbox project doesn't
>>> have the mailing list link at the bottom of the page anymore.
>> 
>> No, it’s publicly writeable. You may have found a bug. Can you link to the 
>> .mcz you’re trying to upload? Then we can give it a try.
> 
> Don't you have to be part of team Pharo ?

Hm… then “public” is certainly a misleading label...

> 
>> Cheers,
>> Max
>> 
>>> 
>>> Thanks!
>>> Alistair

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

[Sven Van Caekenberghe]

> On 17 May 2016, at 06:48, Max Leske  wrote:
> 
>> 
>> On 16 May 2016, at 22:49, Alistair Grant  wrote:
>> 
>> Hi,
>> 
>> I'm attempting to upload a SLICE for issue 18248 to:
>> 
>> MCHttpRepository
>>  location: 'http://smalltalkhub.com/mc/Pharo/Pharo60Inbox/main'
>>  user: ''
>>  password: ''
>> 
>> with username: Alistair
>> 
>> following the instructions in the video at
>> https://www.youtube.com/watch?v=iFomI-7h4qQ (from the Contributing to
>> Pharo video at pharo.org).
>> 
>> but am getting a Error 500 Internal Server Error response.
>> 
>> I can log in to the smalltalkhub.com website without any problems, so I
>> believe my password is correct.
>> 
>> Do I need to be granted write access?  The Pharo60Inbox project doesn't
>> have the mailing list link at the bottom of the page anymore.
> 
> No, it’s publicly writeable. You may have found a bug. Can you link to the 
> .mcz you’re trying to upload? Then we can give it a try.

Don't you have to be part of team Pharo ?

> Cheers,
> Max
> 
>> 
>> Thanks!
>> Alistair

Re: [Pharo-dev] Moving fogbugz entries from Pharo 5 to Pharo 6

[Sven Van Caekenberghe]

Yes, it is fragile.

It's a bit like an application that saves a document as a couple of files. When 
you later copy only one file, you break the format.

> On 17 May 2016, at 08:37, Peter Uhnák  wrote:
> 
> But how come saving a slice in the beginning also saves the dependents? I 
> thought it acted like a package.
> 
> Wouldn't this be a bug then? It is certainly bug-inducing.
> 
> On Tue, May 17, 2016 at 8:12 AM, Sven Van Caekenberghe  wrote:
> 
> > On 17 May 2016, at 08:01, Clément Bera  wrote:
> >
> > Well I tried that and sometimes the integrator can't integrate because of a 
> > "Missing ancestor".
> 
> You have to copy all dependents as well, a slice is just an empty holder. But 
> I guess you already know.
> 
> > I guess I will do what you say for my bugs and when the problem arises 
> > again I will ask again with a concrete example.
> >
> > Nvm
> >
> > On Mon, May 16, 2016 at 3:34 PM, Peter Uhnák  wrote:
> > Is there a problem in simply adding Inbox50 repo and clicking on the "Copy" 
> > button to put it to Inbox60? Or am I missing something?
> >
> > Peter
> >
> > On Mon, May 16, 2016 at 2:12 PM, Clément Bera  
> > wrote:
> > Hello,
> >
> > I have a problem in several bugs I opened on the bug tracker. When I opened 
> > them, Pharo 6 development has not started, so the slices were committed in 
> > the Pharo 5 inbox. As Pharo 5 was in stabilization phasis for release, my 
> > slices were not integrated but postponed to Pharo 6 (which I understand and 
> > accept). But since now the development is in Pharo 6, the monkey checks the 
> > slice in Pharo 6 inbox and can't find my slices because they are in Pharo 5 
> > inbox. See for example 18039 or 17451.
> >
> > What is the right way to move the slices from Pharo 5 inbox to Pharo 6 
> > inbox ? I don't want to end up in a situation where it is not possible to 
> > integrate my slice because of a "Missing ancestor", so how can I move the 
> > slices from Pharo 5 inbox to Pharo 6 inbox without having that problem ?
> >
> > Thanks.
> >
> >
> 
> 
> 

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

[Max Leske]

Done. I had no problems at all… Are you behind a proxy maybe? I seem to 
remember something about HTTPS behind proxies being a problem…

Cheers,
Max

> On 17 May 2016, at 08:59, Alistair Grant  wrote:
> 
> On Tue, May 17, 2016 at 08:43:29AM +0200, Max Leske wrote:
>> 
>>> On 17 May 2016, at 08:31, Alistair Grant  wrote:
>>> 
>>> On Tue, May 17, 2016 at 06:48:06AM +0200, Max Leske wrote:
 
> On 16 May 2016, at 22:49, Alistair Grant  wrote:
> 
> Hi,
> 
> I'm attempting to upload a SLICE for issue 18248 to:
> 
> MCHttpRepository
>   location: 'http://smalltalkhub.com/mc/Pharo/Pharo60Inbox/main'
>   user: ''
>   password: ''
> 
> with username: Alistair
> 
> following the instructions in the video at
> https://www.youtube.com/watch?v=iFomI-7h4qQ (from the Contributing to
> Pharo video at pharo.org).
> 
> but am getting a Error 500 Internal Server Error response.
> 
> I can log in to the smalltalkhub.com website without any problems, so I
> believe my password is correct.
> 
> Do I need to be granted write access?  The Pharo60Inbox project doesn't
> have the mailing list link at the bottom of the page anymore.
 
 No, it’s publicly writeable. You may have found a bug. Can you link to the 
 .mcz you’re trying to upload? Then we can give it a try.
>>> 
>>> Sure...
>>> https://www.dropbox.com/s/18v6flzrc17jcnq/SLICE-Issue-18248-TextActionrubActOnClickforineditor-missing-AlistairGrant.1.mcz?dl=0
>> 
>> I’ll need the Rubric .mcz too :)
> 
> Rubric-AlistairGrant.365.mcz: 
> https://www.dropbox.com/s/uxm5r82duh3ndgp/Rubric-AlistairGrant.365.mcz?dl=0
> Rubric-TheIntegrator.364.mcz (just in case :-)): 
> https://www.dropbox.com/s/eqq5ofjszoxicn6/Rubric-TheIntegrator.364.mcz?dl=0
> 
> Thanks,
> Alistair
> 
> 

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

[Alistair Grant]

On Tue, May 17, 2016 at 08:43:29AM +0200, Max Leske wrote:
> 
> > On 17 May 2016, at 08:31, Alistair Grant  wrote:
> > 
> > On Tue, May 17, 2016 at 06:48:06AM +0200, Max Leske wrote:
> >> 
> >>> On 16 May 2016, at 22:49, Alistair Grant  wrote:
> >>> 
> >>> Hi,
> >>> 
> >>> I'm attempting to upload a SLICE for issue 18248 to:
> >>> 
> >>> MCHttpRepository
> >>>   location: 'http://smalltalkhub.com/mc/Pharo/Pharo60Inbox/main'
> >>>   user: ''
> >>>   password: ''
> >>> 
> >>> with username: Alistair
> >>> 
> >>> following the instructions in the video at
> >>> https://www.youtube.com/watch?v=iFomI-7h4qQ (from the Contributing to
> >>> Pharo video at pharo.org).
> >>> 
> >>> but am getting a Error 500 Internal Server Error response.
> >>> 
> >>> I can log in to the smalltalkhub.com website without any problems, so I
> >>> believe my password is correct.
> >>> 
> >>> Do I need to be granted write access?  The Pharo60Inbox project doesn't
> >>> have the mailing list link at the bottom of the page anymore.
> >> 
> >> No, it’s publicly writeable. You may have found a bug. Can you link to the 
> >> .mcz you’re trying to upload? Then we can give it a try.
> > 
> > Sure...
> > https://www.dropbox.com/s/18v6flzrc17jcnq/SLICE-Issue-18248-TextActionrubActOnClickforineditor-missing-AlistairGrant.1.mcz?dl=0
> 
> I’ll need the Rubric .mcz too :)

Rubric-AlistairGrant.365.mcz: 
https://www.dropbox.com/s/uxm5r82duh3ndgp/Rubric-AlistairGrant.365.mcz?dl=0
Rubric-TheIntegrator.364.mcz (just in case :-)): 
https://www.dropbox.com/s/eqq5ofjszoxicn6/Rubric-TheIntegrator.364.mcz?dl=0

Thanks,
Alistair

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

[Max Leske]

> On 17 May 2016, at 08:31, Alistair Grant  wrote:
> 
> On Tue, May 17, 2016 at 06:48:06AM +0200, Max Leske wrote:
>> 
>>> On 16 May 2016, at 22:49, Alistair Grant  wrote:
>>> 
>>> Hi,
>>> 
>>> I'm attempting to upload a SLICE for issue 18248 to:
>>> 
>>> MCHttpRepository
>>> location: 'http://smalltalkhub.com/mc/Pharo/Pharo60Inbox/main'
>>> user: ''
>>> password: ''
>>> 
>>> with username: Alistair
>>> 
>>> following the instructions in the video at
>>> https://www.youtube.com/watch?v=iFomI-7h4qQ (from the Contributing to
>>> Pharo video at pharo.org).
>>> 
>>> but am getting a Error 500 Internal Server Error response.
>>> 
>>> I can log in to the smalltalkhub.com website without any problems, so I
>>> believe my password is correct.
>>> 
>>> Do I need to be granted write access?  The Pharo60Inbox project doesn't
>>> have the mailing list link at the bottom of the page anymore.
>> 
>> No, it’s publicly writeable. You may have found a bug. Can you link to the 
>> .mcz you’re trying to upload? Then we can give it a try.
> 
> Sure...
> https://www.dropbox.com/s/18v6flzrc17jcnq/SLICE-Issue-18248-TextActionrubActOnClickforineditor-missing-AlistairGrant.1.mcz?dl=0

I’ll need the Rubric .mcz too :)

> 
> Thanks,
> Alistair
> 
> 

Re: [Pharo-dev] Moving fogbugz entries from Pharo 5 to Pharo 6

[Peter Uhnák]

But how come saving a slice in the beginning also saves the dependents? I
thought it acted like a package.

Wouldn't this be a bug then? It is certainly bug-inducing.

On Tue, May 17, 2016 at 8:12 AM, Sven Van Caekenberghe  wrote:

>
> > On 17 May 2016, at 08:01, Clément Bera  wrote:
> >
> > Well I tried that and sometimes the integrator can't integrate because
> of a "Missing ancestor".
>
> You have to copy all dependents as well, a slice is just an empty holder.
> But I guess you already know.
>
> > I guess I will do what you say for my bugs and when the problem arises
> again I will ask again with a concrete example.
> >
> > Nvm
> >
> > On Mon, May 16, 2016 at 3:34 PM, Peter Uhnák  wrote:
> > Is there a problem in simply adding Inbox50 repo and clicking on the
> "Copy" button to put it to Inbox60? Or am I missing something?
> >
> > Peter
> >
> > On Mon, May 16, 2016 at 2:12 PM, Clément Bera 
> wrote:
> > Hello,
> >
> > I have a problem in several bugs I opened on the bug tracker. When I
> opened them, Pharo 6 development has not started, so the slices were
> committed in the Pharo 5 inbox. As Pharo 5 was in stabilization phasis for
> release, my slices were not integrated but postponed to Pharo 6 (which I
> understand and accept). But since now the development is in Pharo 6, the
> monkey checks the slice in Pharo 6 inbox and can't find my slices because
> they are in Pharo 5 inbox. See for example 18039 or 17451.
> >
> > What is the right way to move the slices from Pharo 5 inbox to Pharo 6
> inbox ? I don't want to end up in a situation where it is not possible to
> integrate my slice because of a "Missing ancestor", so how can I move the
> slices from Pharo 5 inbox to Pharo 6 inbox without having that problem ?
> >
> > Thanks.
> >
> >
>
>
>

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

[Alistair Grant]

On Tue, May 17, 2016 at 06:48:06AM +0200, Max Leske wrote:
> 
> > On 16 May 2016, at 22:49, Alistair Grant  wrote:
> > 
> > Hi,
> > 
> > I'm attempting to upload a SLICE for issue 18248 to:
> > 
> > MCHttpRepository
> > location: 'http://smalltalkhub.com/mc/Pharo/Pharo60Inbox/main'
> > user: ''
> > password: ''
> > 
> > with username: Alistair
> > 
> > following the instructions in the video at
> > https://www.youtube.com/watch?v=iFomI-7h4qQ (from the Contributing to
> > Pharo video at pharo.org).
> > 
> > but am getting a Error 500 Internal Server Error response.
> > 
> > I can log in to the smalltalkhub.com website without any problems, so I
> > believe my password is correct.
> > 
> > Do I need to be granted write access?  The Pharo60Inbox project doesn't
> > have the mailing list link at the bottom of the page anymore.
> 
> No, it’s publicly writeable. You may have found a bug. Can you link to the 
> .mcz you’re trying to upload? Then we can give it a try.

Sure...
https://www.dropbox.com/s/18v6flzrc17jcnq/SLICE-Issue-18248-TextActionrubActOnClickforineditor-missing-AlistairGrant.1.mcz?dl=0

Thanks,
Alistair

Re: [Pharo-dev] Moving fogbugz entries from Pharo 5 to Pharo 6

[Sven Van Caekenberghe]

> On 17 May 2016, at 08:01, Clément Bera  wrote:
> 
> Well I tried that and sometimes the integrator can't integrate because of a 
> "Missing ancestor".

You have to copy all dependents as well, a slice is just an empty holder. But I 
guess you already know.

> I guess I will do what you say for my bugs and when the problem arises again 
> I will ask again with a concrete example.
> 
> Nvm
> 
> On Mon, May 16, 2016 at 3:34 PM, Peter Uhnák  wrote:
> Is there a problem in simply adding Inbox50 repo and clicking on the "Copy" 
> button to put it to Inbox60? Or am I missing something?
> 
> Peter
> 
> On Mon, May 16, 2016 at 2:12 PM, Clément Bera  wrote:
> Hello,
> 
> I have a problem in several bugs I opened on the bug tracker. When I opened 
> them, Pharo 6 development has not started, so the slices were committed in 
> the Pharo 5 inbox. As Pharo 5 was in stabilization phasis for release, my 
> slices were not integrated but postponed to Pharo 6 (which I understand and 
> accept). But since now the development is in Pharo 6, the monkey checks the 
> slice in Pharo 6 inbox and can't find my slices because they are in Pharo 5 
> inbox. See for example 18039 or 17451.
> 
> What is the right way to move the slices from Pharo 5 inbox to Pharo 6 inbox 
> ? I don't want to end up in a situation where it is not possible to integrate 
> my slice because of a "Missing ancestor", so how can I move the slices from 
> Pharo 5 inbox to Pharo 6 inbox without having that problem ?
> 
> Thanks.
> 
> 

Re: [Pharo-dev] Moving fogbugz entries from Pharo 5 to Pharo 6

[Clément Bera]

Well I tried that and sometimes the integrator can't integrate because of a
"Missing ancestor".

I guess I will do what you say for my bugs and when the problem arises
again I will ask again with a concrete example.

Nvm

On Mon, May 16, 2016 at 3:34 PM, Peter Uhnák  wrote:

> Is there a problem in simply adding Inbox50 repo and clicking on the
> "Copy" button to put it to Inbox60? Or am I missing something?
>
> Peter
>
> On Mon, May 16, 2016 at 2:12 PM, Clément Bera 
> wrote:
>
>> Hello,
>>
>> I have a problem in several bugs I opened on the bug tracker. When I
>> opened them, Pharo 6 development has not started, so the slices were
>> committed in the Pharo 5 inbox. As Pharo 5 was in stabilization phasis for
>> release, my slices were not integrated but postponed to Pharo 6 (which I
>> understand and accept). But since now the development is in Pharo 6, the
>> monkey checks the slice in Pharo 6 inbox and can't find my slices because
>> they are in Pharo 5 inbox. See for example 18039 or 17451.
>>
>> What is the right way to move the slices from Pharo 5 inbox to Pharo 6
>> inbox ? I don't want to end up in a situation where it is not possible to
>> integrate my slice because of a "Missing ancestor", so how can I move the
>> slices from Pharo 5 inbox to Pharo 6 inbox without having that problem ?
>>
>> Thanks.
>>
>
>