Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Bug in jax_debug_nans
See original GitHub issueVersions 0.1.42+, out_buf referrence before assignment in line 371 of xla.py.
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Tips for debugging NaNs in gradient? #475 - google/jax - GitHub
Hi there, I am running an optimisation using gradients from Jax, and everything goes well for a number of steps until the gradients...
Read more >python - Jax - Debugging NaN-values - Stack Overflow
i spent the last 6 hours trying to debug seemingly randomly occuring NaN-values in Jax. I have narrowed down that the NaNs initially...
Read more >JAX debugging flags - JAX documentation - Read the Docs
jax_debug_nans is a JAX flag that when enabled, automatically raises an error when a NaN is detected. It has special handling for JIT-compiled...
Read more >Files · debug-nans-stores · mutsuki / jax · GitLab
Please help by trying it out, reporting bugs, and letting us know what you think! import jax.numpy as jnp from jax import grad,...
Read more >chex - PyPI
Debugging in JAX is made more difficult by code transformations such as jit and pmap , which introduce optimizations that make code hard...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You are right, @mattjj. I’ve just rebuilt it from source and it’s running under debug_nans flag like a charm. Thanks!
No worries, it’s the kind of thing where the context of how this came to be broken is helpful (in short, we revised the core so that jaxprs always have multiple return values rather than possibly returning tuples, and this code wasn’t updated properly).
Even more importantly, you’ve also found that we don’t have a test for this code! We should close this issue only once we have a test in place.