error_if now has a breakpoint option #421
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
patrick-kidger
force-pushed
the
better-error-if
branch
from
457abb4
to
ce36ca3
Compare
…oved from tracebacks.
patrick-kidger
force-pushed
the
better-error-if
branch
from
ce36ca3
to
bef34e1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In particular this is controlled through a new
EQX_ON_ERROR=<raise|breakpoint>environment variable.Note that
EQX_ON_ERROR=breakpointsometimes runs afoul of this bug in core JAX: google/jax#16732. If so this can be worked around by deleting intermediatejax.jit/eqx.filter_jitdecorators.