client fetch errors when remote repo is empty
Bug #1060462 reported by
milki
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Dulwich |
Fix Released
|
Medium
|
milki |
Bug Description
If a remote git repo is empty (newly created with git init --bare), when dulwich.client tries to fetch from the repo, _read_refs will error.
Examples:
https:/
This happens because _read_refs does not enter the for loop where it will set server_capabilities to something not None and set(None) errors.
_read_refs should return something sane in this case and dependents should handle this case.
Changed in dulwich: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in dulwich: | |
milestone: | none → 0.9.0 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Change read_refs to return None, set([]) and check for this in send_pack
Note: This doesn't patch the http client