Skip to content

Unresolved conflict in pubsub/cloud-client/requirements.txt file #1550

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

Closed
carusology opened this issue Jul 3, 2018 · 2 comments
Closed

Unresolved conflict in pubsub/cloud-client/requirements.txt file #1550

carusology opened this issue Jul 3, 2018 · 2 comments

Comments

@carusology
Copy link

In which file did you encounter the issue?

pubsub/cloud-client/requirements.txt

Did you change the file? If so, how?

I did not. I tried to load it using pip install -r requirements.txt

Here's a link to the commit that appears to have broken it.
0f26000

Describe the issue

I am attempting to follow the instructions on this page to use this SDK to test the Pubsub emulator, but the requirements.txt file it references looks to have an unresolved conflict in here. The commit touching this file claims to have resolved a host of conflicts, but it looks like this file got missed.

@techieshark
Copy link

Here's the exact spot that's broken.

Easy to reproduce:

git clone [email protected]:GoogleCloudPlatform/python-docs-samples.git
cd python-docs-samples/pubsub/cloud-client/
pip install -r requirements.txt

results in a glaring problem from pip:

Invalid requirement: '<<<<<<< HEAD'
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/site-packages/pip/_internal/req/req_install.py", line 252, in from_line
    req = Requirement(req)
  File "/usr/local/lib/python2.7/site-packages/pip/_vendor/packaging/requirements.py", line 97, in __init__
    requirement_string[e.loc:e.loc + 8]))
InvalidRequirement: Invalid requirement, parse error at "u'<<<<<<< '"

("'<<<<<<< HEAD") is the dead giveaway. Must have accidentally been missed during a merge (thanks, git!).

@nnegrey
Copy link
Contributor

nnegrey commented Dec 14, 2018

This issue appears to have been fixed. Please feel free to reopen if that is not the case. :)

@nnegrey nnegrey closed this as completed Dec 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants