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

Double-check existing uses of DeterminismLog for missing isActive() checks #47

Closed
burg opened this issue Sep 23, 2012 · 0 comments
Closed
Labels

Comments

@burg
Copy link
Owner

burg commented Sep 23, 2012

Per discussion at the end of Issue #41, we may be missing some checks as to whether the determinism log is currently "active". If not "active", then the script execution context was started by user actions we want to ignore, such as Inspector console commands.

The easiest way to check for this is to find all uses of DeterminismLog; main users will be memoized actions.

burg pushed a commit that referenced this issue Sep 28, 2012
…nismLog::activate,deactivate into setIsActive (per naming conventions). Fixes Issue #47.
@burg burg closed this as completed Sep 28, 2012
burg pushed a commit that referenced this issue Nov 6, 2012
…nismLog::activate,deactivate into setIsActive (per naming conventions). Fixes Issue #47.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant