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.
As noted in #347, we currently don't properly check numpy-related types since numpy 1.19 (required by TensorFlow 2.4 and 2.5) doesn't yet have type stubs . Looking at the typing issues caught in numpy 1.20, it seems most are the result of us using a TensorType result from e.g. a sample call as if it must be a tf.Tensor (which it will be in practice, but is not what the type says). We have two options on how to fix this:
This PR shows what option 1 looks like in the code and in one of the notebooks. If it looks ok then I'll make it for the other notebooks too.