There seems to be both Protocol V1 and V2 files in the codebase. Is the target of the repo to support both protocol versions or just focus on the V2 highlighted in googleblog a few weeks ago? Regardless, better clarity would be nice in the readme.

Additionally what are some of the future tasks? I would love to be a contributor.

In order to contribute, having clear vision help us to specify missions.

Could you please explain more the vision of this repository?
i.e: audience ... and so on.

Hi,

I am reviewing the implementation here for my personal project and I think there are still some unfinished pieces.

The spec for V2 were also added some new functionality in recent months.

I was wondering if PR are accepted or would you prefer others maintaining a fork? Or perhaps contributing this to https://github.com/go-git/go-git which is still missing a Protocol V2 implementation?

How to reproduce

# Setup server
git clone https://github.com/sluongng/git-cache/
git checkout 07f1136c7d09c8281e4e0d8a8b96e3816dffbdac
go run .

# Setup client
# This should clone git.git from Github through the simple golang proxy
git -c http.extraHeader='GIT-CACHE-UPSTREAM: https://github.com' clone -vvv http://127.0.0.1:8080/git/git.git

Expected result

The middleware layer in sluongng/git-cache@07f1136#diff-0eb779b9e49d8e44b0f36923fdb8d87d5ee024f886eefc45deec4ec88380a087R56 should be able to parse the request body into ProtocolV2RequestChunk and serialize the Chunks as JSON and log them out.

Actual result

ls-ref command seems to work fine, but the one next git-upload-pack command failed to be parse by gitprotocolio

Unable to scan request: strconv.ParseUint: parsing "\x1f\x8b\b\x00": invalid syntax

Which most likely coming from