Skip to content

fetch('+refs/pull/*:refs/heads/pull/*') fails #243

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.

Sign up for GitHub

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

Jump to bottom
Closed
ghost opened this issue Jan 22, 2015 · 5 comments
Closed

fetch('+refs/pull/*:refs/heads/pull/*') fails #243

ghost opened this issue Jan 22, 2015 · 5 comments
Assignees
@Byron
Labels
acknowledged
Milestone
v0.3.6 - Features

Comments

@ghost
Copy link

ghost commented Jan 22, 2015 

>>> r.remotes.origin.fetch('+refs/pull/*:refs/heads/pull/*')
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/local/lib/python2.7/dist-packages/git/remote.py", line 613, in fetch
    res = self._get_fetch_info_from_stderr(proc, progress or RemoteProgress())
  File "/usr/local/lib/python2.7/dist-packages/git/remote.py", line 555, in _get_fetch_info_from_stderr
    for err_line, fetch_line in zip(fetch_info_lines, fetch_head_info))
  File "/usr/local/lib/python2.7/dist-packages/git/remote.py", line 555, in 
    for err_line, fetch_line in zip(fetch_info_lines, fetch_head_info))
  File "/usr/local/lib/python2.7/dist-packages/git/remote.py", line 292, in _from_line
    raise TypeError("Cannot handle reference type: %r" % ref_type_name)
TypeError: Cannot handle reference type: u"'refs/pull/1/head'"

with the command line

$ git fetch origin +refs/pull/*:refs/heads/pull/*
remote: Counting objects: 9, done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 9 (delta 2), reused 9 (delta 2)
Unpacking objects: 100% (9/9), done.
From http://github.com/loic-bot/testrepo
 * [new ref]         refs/pull/1/head -> pull/1/head
 * [new ref]         refs/pull/1/merge -> pull/1/merge
 * [new ref]         refs/pull/2/head -> pull/2/head
 * [new ref]         refs/pull/2/merge -> pull/2/merge
 * [new ref]         refs/pull/3/head -> pull/3/head
 * [new ref]         refs/pull/3/merge -> pull/3/merge
@Byron Byron added this to the v0.3.6 - Features milestone Jan 22, 2015
@Byron
Copy link
Member

Byron commented Jan 22, 2015

I could reproduce the issue and am pretty sure there will be a fix today, along with a v0.3.6 release.

What happens is that the fetch succeeds, but it can't make sense of the refs/pull/... paths for some reason and thus fails to wrap it into a corresponding object.

@ghost
Copy link
Author

ghost commented Jan 22, 2015

cool :-)

@Byron Byron self-assigned this Jan 22, 2015
@Byron Byron closed this as completed in 06bec1b Jan 22, 2015
@Byron
Copy link
Member

Byron commented Jan 22, 2015

Your can watch the archived live-stream on youtube.
thumb.

@loic-bot
Copy link

Oo that's the first time I see that kind of live coding. Amazing. Do you do that often. And thanks, of course !

@Byron
Copy link
Member

Byron commented Jan 22, 2015

I always and only do it. Started about 12 days ago, and I wouldn't want to miss it anymore.
I'd call it "exstream programming", as it's like pair programming, except for your partner being an anonymous crowd. In any way, it changes and improves the way you approach things, I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Byron Byron

Labels
acknowledged
Milestone
v0.3.6 - Features
Development

No branches or pull requests
2 participants
@Byron @loic-bot