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

Don't reraise exception in finally block #51

Merged
merged 1 commit into from
Nov 18, 2019
Merged

Conversation

OrangeTux
Copy link
Collaborator

@OrangeTux OrangeTux commented Nov 18, 2019

The fix introduced for #46 contained a bug. ChargePoint.call()
could fail with:

	try:
	    await self._send(call.to_json())
	    response = \
		await self._get_specific_response(call.unique_id,
						  self._response_timeout)
	finally:
	    self._call_lock.release()
>           raise
E           RuntimeError: No active exception to reraise

Fixes: #50

The fix introduced for #46 contained a bug. `ChargePoint.call()`
could fail with:

	try:
	    await self._send(call.to_json())
	    response = \
		await self._get_specific_response(call.unique_id,
						  self._response_timeout)
	finally:
	    self._call_lock.release()
>           raise
E           RuntimeError: No active exception to reraise

Fixes: #50
@ghost
Copy link

ghost commented Nov 18, 2019

DeepCode Report (#0cb645)

DeepCode analyzed this pull request.
There are no new issues.

@OrangeTux OrangeTux mentioned this pull request Nov 18, 2019
@OrangeTux OrangeTux merged commit 34f94bd into master Nov 18, 2019
@OrangeTux OrangeTux deleted the 50-reraise-problem branch November 19, 2019 12:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

ChargePoint.call() fails with: " RuntimeError: No active exception to reraise"
2 participants