-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It can't make it work #4
Comments
same issue here |
I think the issue is with the glob pattern can you try the same with two
See https://pypi.org/project/globre/ for more about glob patterns I know they're not always the most intuitive (albeit very useful for path selection) you can always resort to regex if you prefer |
Ok thanks, I didn't know of glob patters. However I just copied and pasted your command and it doesn't work: I waited more that 5 minutes and the command is still pending. From taskmanager it continues to consume constantly 0.1Mbps (my Internet connection is surely faster), but the destination folder remains empty. I'm using python 3.8 in Powershell. Finally, when I press CRTL+C, I get the following traceback:
|
please run
the run your command again with the |
Run the command
after the export GIT_PYTHON_TRACE='full'. The result is:
|
you're posting the exception without the output all this tells me is that you hit ctrl+c to interrupt the operation while the gitlab API is being queried, Does
|
Hi @ezbz I am having this issue and the curl works for me....any ideas? |
@projasmine can you post the command you're running (and add the |
I'm guessing most people cancel after several minutes, assuming failure. For me, the command command works after nearly 12 minutes. I assume due to https://Gitlab.com ratelimiting |
Observe gitlab.com rate limits, closing due to inactivity |
Hi,
I was trying to test this tool, but the script always fails. Just to make an example, I would clone all the repo of a public project (this).
I've launched the following command
it says, after many seconds:
What's wrong?
The text was updated successfully, but these errors were encountered: