-
Notifications
You must be signed in to change notification settings - Fork 13
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
order in cleanup function #265
Comments
Branch 265-order-in-cleanup-function created! |
@SBlechmann could you provide some simple coded for reproducing the error? |
Is it the correct workflow to:
|
@SystemsPurge could you reproduce this error and implement it into a unitest, maybe under |
@djs0109 test is written. Still to see why assertRaises is not catching the HTTPError exception in this case. |
@djs0109 Test was not working because it involves clear methods that are subsequently used by the teardown method, so i added a try , except at the teardown but maybe someone should have a better look into that. Should this be pushed to 215? EDIT: Okay i should read more carefully next time. |
The order in which the cleanup functions are called is important (afaik, only if there is an iot device holding a command).
In the tutorials, the order of the functions called is correct.
Yet, we just discovered this when calling the functions in a different order, e.g. clear the cb and then the iota, the iota throws an 400 error that the connection to the cb failed.
Maybe we should add this to the docs somewhere?
The text was updated successfully, but these errors were encountered: