-
Notifications
You must be signed in to change notification settings - Fork 670
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
NPE on clone.bundle #1092
Comments
I am having this same issue. with gitblit 1.80, adding an account using Tower git.
|
I am having the same issue too. It happened after I pushed to a ticket to test things out. Looks like the direct issue is Here are some debug lines I added in
Seems the issue is the |
I was able to get it working with this patch, but I have no clue on the validity of the change. It didn't cause any negative side effects that I could see or find yet.
|
The NPE is easy enough to fix. The question is, where does it come from, i.e. what is the URL that was used, what was the client, what was the intended target repository, operation, etc. In the first case, I didn't trigged on "repo tool", or clone.bundle, so it took me (quite a while) to realise you used the Android Repo tool from Google as a client. That is correct, that will not work this way, not even when the NPE is fixed. GitBlit does currently not support the "git bundle" command. When using Repo as a client against GitBlit, please use the |
In the second case I cannot help much because I have no information what the URL was, that caused the misbehaviour. The client is Tower, but as that is a commercial tool and not available to me for testing, I cannot check what URL was generated. Was it also issuing a bundle command? In that case I don't know a work-around. |
In the third case, I don't know what is going on. The URL reaching the server seems to be I guess the only fix for now is to prevent the NPE and to complain about clone.bundle being a unsupported command. |
This is used by the repo tool. Upon bundle commands the server returns HTTP 500 and the log shows this error:
The text was updated successfully, but these errors were encountered: