Skip to content

Fix TypeError when random_state is None in OT/EOT explainers - #8

Merged
jaydu1 merged 1 commit into
mainfrom
fix/random-state-none
Oct 3, 2026
Merged

jaydu1 merged 1 commit into
mainfrom
fix/random-state-none

Conversation

@Yuewen210

Copy link
Copy Markdown
Collaborator

Crossfitting passes random_state=None to OT/EOT explainers, which causes a TypeError.

This PR makes OTExplainer and EOTExplainer fall back to 0 when random_state is None, consistent with FlowExplainer.

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Code review skipped — your organization has no extra usage available to pay for this review.

If your organization's extra usage balance is empty, an organization admin can add extra usage credits at claude.ai/admin-settings/usage. If its monthly spend limit was reached, an admin can raise it on the same page. If neither applies, contact Anthropic support.

Once extra usage is available, comment @claude review on this pull request, or push a new commit, to trigger a review.

@jaydu1
jaydu1 merged commit 5201142 into main Oct 3, 2026
5 checks passed
@jaydu1
jaydu1 deleted the fix/random-state-none branch October 3, 2026 11:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants