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

[New] A utility to dump info for debugging / reproducing #355

Open
saharan-deshaw opened this issue Aug 27, 2024 · 1 comment
Open

[New] A utility to dump info for debugging / reproducing #355

saharan-deshaw opened this issue Aug 27, 2024 · 1 comment

Comments

@saharan-deshaw
Copy link
Collaborator

saharan-deshaw commented Aug 27, 2024

Hi,

Logging this issue as an FYI that we (D.E. Shaw) will be contributing a utility to the pyflyby repo that can be used for debugging and reproducing any issues.

Background: Sometimes it’s challenging to share a reproducer with other teams when an issue originates from their code. Users will be able to use this utility to dump useful info into a file and share it with the other team so that they can reproduce the issue themselves.

Info dumped in the file: This utility will dump the error stack frames into the file in a pickled form, specifically the values of the local variables from the stack frames. By default, only the last frame from the bottom will be dumped. The utility will provide options to configure the frames and the variables that the user wants to dump.

This utility will be provided with two interfaces:

  1. As a script: For cases where the user wants to create a dump file for their failing script or command.
  2. As a function: For interactive cases. For instance, if the user is already in an IPython debugger, they can use this function to dump the required info.
@deshaw deshaw deleted a comment Aug 27, 2024
@saharan-deshaw
Copy link
Collaborator Author

Raised the PR against this issue: #356

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

No branches or pull requests

1 participant