Fix ChatFeed / Interface tests and async generator placeholders #6245
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ensures that the tests actually run and raises errors by setting
callback_exception = "raise"
rather than having the errors piped to the chat logsThis resulted in finding a lot of tests failing, but most of them were just tests not written properly (e.g. not using
wait_until
to assert)The only bug I found was a result of #6105, where async generator functions execution time was based on
placeholder_threshold
, i.e.await _schedule_placeholder
had to run in completion, before the actual callback started executing.This was remedied by wrapping
_serialize_response
(where the iteration of the generator was happening) alongside the actual callback so that when checkingtask.done()
, it checks the execution of both of these.