On 21.05.2013, at 10:01, Sven Van Caekenberghe <[email protected]> wrote:

> Max,
> 
> On 21 May 2013, at 09:43, Max Leske <[email protected]> wrote:
> 
>> Not sure if this is related, but my FileSystem-Git build for 2.0 broke this 
>> morning with a Zn stack trace (bad gateway): 
>> https://ci.inria.fr/pharo-contribution/job/FileSystem-Git/PHARO=20,VERSION=development,VM=vm/53/
> 
> Assuming you are loading Zn's #bleedingEdge, could you send me the URL you 
> try to access and that fails ?

Hm, doesn't seem to be bleeding edge (although is 2.0 dev). The test is fine on 
my local machine, so perhaps there's something wrong at inria?

Here's the incantation:
ZnClient new
                url: aUrl asZnUrl / 'info' / 'refs';
                queryAt: 'service' put: 'git-upload-pack';
                "username: 'admin' password: 'admin';"
                enforceHttpSuccess: true;
                streaming: true;
                get;
                yourself

with url: 'https://git.gitorious.org/gitorious/mainline.git'

Thanks Sven.

> 
> I mean a standalone version of what is happening here
> 
> ZnClient>>get
> GitDumbHTTPProtocol class>>initialRequestTo:
> GitDumbHTTPProtocol class>>connectTo:
> GitAbstractProtocol class>>url:
> GitSmartHTTPProtocolTest(GitAbstractProtocolTest)>>newProtocol
> GitSmartHTTPProtocolTest(GitAbstractProtocolTest)>>testTags
> GitSmartHTTPProtocolTest(TestCase)>>performTest
> 
> If that is possible without giving out credentials.
> 
> Sven
> 
>> Max
>> 
>> On 21.05.2013, at 09:38, Sven Van Caekenberghe <[email protected]> wrote:
>> 
>>> 
>>> On 21 May 2013, at 09:30, Damien Cassou <[email protected]> wrote:
>>> 
>>>> - continue working on the configuration (it looks like Zinc has a bug with 
>>>> its handling of PUT requests)
>>> 
>>> Hi Damien, please elaborate, maybe I can help.
>>> 
>>> Sven
>>> 
>>> 
>>> --
>>> Sven Van Caekenberghe
>>> Proudly supporting Pharo
>>> http://pharo.org
>>> http://association.pharo.org
>>> http://consortium.pharo.org
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
>> 
> 
> 


Reply via email to