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

Time-travel debugging #2

Closed
nwinter opened this Issue Jan 2, 2014 · 3 comments

Comments

Projects
None yet
1 participant
@nwinter
Contributor

nwinter commented Jan 2, 2014

See the CodeCombat sister issue for context. Basically, Aether should be able to grab and serialize all the variable states we might want to see from a debugging perspective.

@nwinter

This comment has been minimized.

Show comment
Hide comment
@nwinter

nwinter Jan 17, 2014

Contributor

I'm going to build this soon. If anyone wants to collaborate with me on it, let me know and we'll get into it.

Contributor

nwinter commented Jan 17, 2014

I'm going to build this soon. If anyone wants to collaborate with me on it, let me know and we'll get into it.

@nwinter

This comment has been minimized.

Show comment
Hide comment
@nwinter

nwinter Jan 31, 2014

Contributor

It's going well, although performance and edge cases need work.

Contributor

nwinter commented Jan 31, 2014

It's going well, although performance and edge cases need work.

@nwinter

This comment has been minimized.

Show comment
Hide comment
@nwinter

nwinter May 21, 2014

Contributor

This is pretty much working in CodeCombat now that we're running the flow only lazily in a separate simulation and not being so dumb about serializing it.

Contributor

nwinter commented May 21, 2014

This is pretty much working in CodeCombat now that we're running the flow only lazily in a separate simulation and not being so dumb about serializing it.

@nwinter nwinter closed this May 21, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment