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

Unintuitive handling of seed in run.end() #148

Open
TheEimer opened this issue May 22, 2024 · 0 comments
Open

Unintuitive handling of seed in run.end() #148

TheEimer opened this issue May 22, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@TheEimer
Copy link

Wen using the minimal recording example, I tried to add a "seed" to r.end(). Unfortunately, this argument is actually overwritten with None in some cases, spawning a very confusing assertion error of the seed being None when I definitely passed a different value. I don't know why the arguments are overwritten so I can't say if that makes sense or not, but the error should be handled differently in my opinion.

@TheEimer TheEimer added the documentation Improvements or additions to documentation label May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant