-
Notifications
You must be signed in to change notification settings - Fork 591
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
Homepage sample for pubsub does not work #6
Comments
/cc @jpvic |
This has been fixed. Closing, feel free to comment if you still have issues @jpvic |
The typo is corrected.
the examples ends with the same error:
|
I'm not able to reproduce that, can you tell me your gcloud version and full python version? |
python -c 'import sys; print(sys.version)'2.7.10 (default, Jul 5 2015, 14:15:43) pip show gcloudMetadata-Version: 1.1 |
Thanks, did you create a topic and subscription before running the sample? |
It seems we could do a better job catching the error instead of trying to If you could, use triple backticks to format the stacktrace (easier on the eyes). Or @jonparrott could edit your post to add the formatting. |
edited. |
indeed. I used the topic and subscription of my project. I do use the messaging platform with no problems in the project. |
Can you try with a new topic/subscription? The subscription should be pull subscription. You can create them with these gcloud commands:
|
I didn't created the original topic with gcloud command I retried with with the proposed command : ( watch out typo 'subcriptions' ==> subscriptions )
same result 👍
|
@dhermes any ideas? |
@jonparrott Can you format the above stacktrace with triple quotes (I don't have edit privileges)? Yes, I think the error payload is HTML only, we have a flag It's possible here that his payload is a more generic error, I'd need a debugger to actually find out, but I can try to reproduce myself as well (pending the code formatting 😄) |
Done, and I couldn't reproduce it on my end. |
These samples have been removed, so I'm closing this issue. |
Original issue
The text was updated successfully, but these errors were encountered: