Unclear errors from beartype/typeguard (possibly misused!) about jaxtyping HOT 2 CLOSED

For beartype, this is the error message I get:

beartype.roar.BeartypeCallHintReturnViolation: Function __main__.update_hidden_state() return "Traced<ShapedArray(float32[10])>with<DynamicJaxprTrace(level=1/0)>" violates type hint <class 'jaxtyping.Float[Array, 'embedding']'>, as <protocol "jax._src.interpreters.partial_eval.DynamicJaxprTracer"> "Traced<ShapedArray(float32[10])>with<DynamicJaxprTrace(level=1/0)>" not instance of <class "jaxtyping.Float[Array, 'embedding']">.

I do note that it is producing coloured output in my terminal. Perhaps your terminal doesn't support colour, and this produces your odd-looking error message? I'd suggest opening a beartype issue if so; ideally beartype should disable its use of colour in this scenario.

I can't reproduce your typeguard error. I get error:

typeguard.TypeCheckError: the return value (jax._src.interpreters.partial_eval.DynamicJaxprTracer) is not an instance of jaxtyping.Float[Array, 'embedding']

which looks like the expected error message.
(I'll grant you that it doesn't really tell you that it's due to a shape error in particular -- this is a known issue (#6) and something that at least beartype has plans to fix (beartype/beartype#235))

This is in a fresh conda environment with the same versions of the packages as you list.

from jaxtyping.

Thanks for double checking! It turned out that the main difference was me operating within a VSCode notebook environment (definitely should have mentioned) -- perhaps Jupyter is not the intended usage of the runtime type checkers? I'll search around and see if theres a good place to report this behaviour in the respective libs.

Will close, thanks again!

from jaxtyping.