-
Notifications
You must be signed in to change notification settings - Fork 20
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
improve error handling for builtin assistants #350
Conversation
@@ -103,10 +103,11 @@ testpaths = [ | |||
] | |||
filterwarnings = [ | |||
"error", | |||
"ignore::ResourceWarning", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can find plenty of issues all over the web that have problems with unclosed resource warnings when using pytest
. We are properly using context managers everywhere, so whatever warning is happening in the test suite stems from it rather than the code we are trying to test.
] | ||
|
||
|
||
@skip_on_windows |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried multiple things now, but got nothing to work. All data points to the test code being the problem rather than the code that is tested here. Let's ignore this for now. Maybe someone else has more insights later.
I spend almost an hour today trying to find a bug that wasn't there, because we didn't raise a proper error when our API call failed.