Skip to content
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

Fix RuntimeError: set_exception can only be called once #4380

Closed
wants to merge 2 commits into from
Closed

Fix RuntimeError: set_exception can only be called once #4380

wants to merge 2 commits into from

Conversation

PicardParis
Copy link

No description provided.

@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Nov 10, 2017
@tseaver tseaver added the api: pubsub Issues related to the Pub/Sub API. label Nov 10, 2017
@tseaver
Copy link
Contributor

tseaver commented Nov 10, 2017

@PicardParis Thanks for the patch! I'll defer to @lukesneeringer about the details, but we need to add one or more testcases / assertions which verify both new codepaths.

@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this State. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

@googlebot googlebot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Nov 27, 2017
self._future.set_exception(exception)
if self._future.done():
# Simply trigger the future.
self._future._trigger()

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

dhermes added a commit to dhermes/google-cloud-python that referenced this pull request Nov 27, 2017
Also modifying a unit test to call `policy.on_exception()`
**outside** of an "assert raises".

I noticed these issues during review of googleapis#4380.
dhermes added a commit that referenced this pull request Nov 27, 2017
Also modifying a unit test to call `policy.on_exception()`
**outside** of an "assert raises".

I noticed these issues during review of #4380.
@dhermes
Copy link
Contributor

dhermes commented Nov 28, 2017

@PicardParis Thanks a lot for taking the time to write and send this patch. Reading it and writing tests for it certainly helped me understand the implementation as I started to dig in.

After debugging reproducible cases for #4463, it's clear that this approach is not the right one, so we'll be closing this PR.

Thanks!

@dhermes dhermes closed this Nov 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: pubsub Issues related to the Pub/Sub API. cla: no This human has *not* signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants