google-deepmind / google-deepmind/chex

Better error report for max traces exceeded

Open
#176 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
957
Forks
74
Avg merge
21h 10m
Merged PRs (30d)
1

Description

In my experience, when chex reports max traces exceeded, it's usually because of me passing parameters to the function with different shapes or data types. Is it possible for chex to report such inconsistency?

e.g.,
```
AssertionError: [Chex] Function '_wrapper' is traced > 1 times!
Difference in input shapes. Last time variable `x` traced with shape "(10, 1)", this time traced with shape "(9, 1)".
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.