-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Handle subscription list for specific topic separately. #1411
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
Handle subscription list for specific topic separately. #1411
Conversation
|
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed, please reply here (e.g.
|
|
Cytora signed it! |
c3030ba to
3dc9cc0
Compare
Handle subscription list for specific topic separately.
|
Thanks for the PR! Not sure I understand what's happening here. Can you share a bit more about what you're trying to do? And maybe add some tests? |
|
Sorry for not adding any description and tests. It is basically a bug fix. When we tried to use this functionality: we got the following error. It also fails with different error if param topic_name is not specified returns The code we implemented basically solve a problem with inconsistency of GCloud REST API. It worked for us and was very quick fix. If you think this should be solved in a different way, I would be happy to hear your ideas. I just took a look on tests now and it seems that tests do not reflect the output from GCloud REST API. GCloud REST API response for a specific topic does not return a list of format [{'name': SUB_PATH, 'topic': TOPIC_PATH}], but returns list of strings (['topic1 name', 'topic2 name', ...]). It also seems pagination is on by default, which is not reflected in tests. I am wondering. Is there a bug on GCLOUD REST API or on the gcloud-python side. If you think that this needs to be fix, I can refactor tests as well. I hope it is clearer now. If you need any more informations, please do not hesitate to ask me. |
6e7b4d3 to
08064bc
Compare
|
/cc @tseaver : This seems like a legit concern. Curious why our system tests don't catch this? |
setup.py
Outdated
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
|
@andrazhribernik can you supply the value of |
|
@tseaver Value of resource is different whether param 'topic_name' is specified or not.
Error is raised, if there is any subscription for a topic that has already been deleted (
Error is raised for every request of this type. I hope this explanation will help to understand my code updates. |
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
|
@andrazhribernik I believe that #1440 should address this issue. @jgeewax, it also adds a system test for |
This allows generator users to set the numeric-enum-response parameter at generation time via the BUILD rule. The default is `False` for backward compatibility.
No description provided.