Tried it with plain old https authentication via prompting or cache,
worked fine.

Tried it with plain old https authentication via jamming username and
password into git url, got the infinite loop again.

That narrows it down a bit - has nothing to do with ci tokens, and
more to do with how urls containing explicit authentication are
handled.
(And it's not surprising there might be a problem there, that feature
is seldom used.  It'll be used more now that ci tokens are supported,
I bet.)

On Fri, Jul 22, 2016 at 3:41 PM, Dan Kegel <d...@kegel.com> wrote:
> On Fri, Jul 22, 2016 at 3:38 PM, Stan Hu <sta...@gmail.com> wrote:
>> Thanks for reporting. You may want to try disabling Rack Attack until we
>> resolve the issue.
>
> Thanks.  Tried that.  Now the symptom is different:
>
> $ git lfs install
> $ git lfs clone
> https://gitlab-ci-token:remo...@gitlab.removed.com/pastries/funkychicken.git
> Cloning into 'funkychicken'...
> remote: Counting objects: 67, done.
> remote: Compressing objects: 100% (65/65), done.
> remote: Total 67 (delta 19), reused 7 (delta 0)
> Unpacking objects: 100% (67/67), done.
> Checking connectivity... done.
> warning: current Git remote contains credentials
> warning: current Git remote contains credentials
> warning: current Git remote contains credentials
> warning: current Git remote contains credentials
> warning: current Git remote contains credentials
> warning: current Git remote contains credentials
> warning: current Git remote contains credentials
> warning: current Git remote contains credentials
> ...
> and it never finishes.   Looks like it's doing the same https fetches
> over and over, about once a second.

-- 
You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/CAPF-yOaDSC21TOL%3Dj7hk_%2Bty5GK6wROU2CQkKfY6UKNkrA%3DP-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to