Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UnexpectedTracerError when enabling EQX_ON_ERROR=breakpoint #73

Closed
Randl opened this issue Aug 10, 2024 · 1 comment
Closed

UnexpectedTracerError when enabling EQX_ON_ERROR=breakpoint #73

Randl opened this issue Aug 10, 2024 · 1 comment
Labels
question User queries

Comments

@Randl
Copy link
Contributor

Randl commented Aug 10, 2024

While working on #71 I got an XlaRuntimeError in which the error message suggested to turn EQX_ON_ERROR=breakpoint. However, when I do that, many tests, even ones that didn't fail before, start failing with UnexpectedTracerError.

Steps to reproduce

  1. Set envvar EQX_ON_ERROR=breakpoint
  2. Run test_minimise tests.
@patrick-kidger
Copy link
Owner

I suspect you also need to set EQX_ON_ERROR_BREAKPOINT_FRAMES; see also the docs at https://docs.kidger.site/equinox/api/errors/#equinox.error_if. This is all to work around a known JAX bug, which is likely what you're bumping into.

This is something I've already improevd for the next release. EQX_ON_ERROR_BREAKPOINT_FRAMES will be set to 1 by default (so that this error doesn't trigger at all, even if you can't navigate the stack), and I've added a lot of extra printout when you open the debugger, better instructing you what to do.

@patrick-kidger patrick-kidger added the question User queries label Aug 10, 2024
@Randl Randl closed this as completed Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question User queries
Projects
None yet
Development

No branches or pull requests

2 participants