-
Notifications
You must be signed in to change notification settings - Fork 540
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
XML syntax error with Bitbucket private repo #370
Comments
hmm...XML complaints. I think this actually might not have anything to do with protobuf. You're on bitbucket - are you using @mattfarina may have a better immediate idea, but this is the first thing that jumps out at me, because If you're not using |
No I use |
That might do it. Looks like XML is also used in doing remote discovery/detection. Does the remote repository exist, but no commits are yet pushed to it (so, empty repo), or does it simply not exist at all? |
@jtblin might I was just able to reproduce this error when the endpoint on bitbucket.org is an inaccessible or nonexistent repo. If this is a private repo can you updated the - package: bitbucket.org/jtblin/some-repo
repo: git@bitbucket.org:jtblin/some-repo
subpackage:
- apipb This will tell git to use your credentials to access the repo. If this is the case we may be able to catch this bitbucket error and provide better context. |
I pushed some commits and I'm still getting the same error so it doesn't look like it's the issue. Given the error message specifically mentions the code generated from protobuf, it does seem like this is what causing the issue. There are 2 types of files in this directory |
@jtblin I get this error when there's an access issue to the repo. When the This error shouldn't be picked up by protobuf. When you get the error: [ERROR] Error looking for bitbucket.org/jtblin/some-repo/apipb: XML syntax error on line 7: expected attribute name in element I believe it's saying the repo |
I just ran a couple more tests. On bitbucket.org when the repo is private and no I've not tracked this yet but am able to reliable reproduce these errors. I'm going to see if I can get to the bottom of these errors (as I didn't expect this error at all) and provide a better message. You can get more information running |
Thank you @mattfarina, sorry I missed your previous answer. Yes it is a private repo but it is set as Adding
If I do a
The import is for the correct path and my IDE is able to see the imported package so I can confirm that everything is correct from this perspective. I tried deleting all the glide files and started the entire process but same issue. The repo is added in the I tried with another bitbucket private repo which doesn't have protobuf and I am getting the same error so protobuf is not the issue indeed. It seems it just doesn't work with bitbucket private repos. |
What version of Glide are you using and how did you install it? "I Think" that |
I have |
@jtblin now that I know how you got to this I'll look into fixing this. |
This should not be fixed on the tip of master with the use of the latest vcs package. |
With installation from HEAD, xml parsing error is gone but I still get |
@vishr I didn't note it in the release notes but this should now be improved. If there's a not found or access denied it should tell you. |
Over here still happening. |
I have some generated code for grpc.io using the following command
protoc -I ./apipb apipb/*.proto --go_out=plugins=grpc:apipb
.When I run
glide up
from another repo which imports this repo I get the following error:I am not sure exactly which generated code is creating the problem.
Example of protobuf definition:
The generated code is like this
Maybe it's the byte data that creates this issue?
It totally breaks glide and I am not able to generate the
glide.lock
file.Thanks for your help
The text was updated successfully, but these errors were encountered: