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

stacktraces should have associated timestamps for each entry #320

Open
KrishnaPG opened this issue Nov 17, 2020 · 1 comment
Open

stacktraces should have associated timestamps for each entry #320

KrishnaPG opened this issue Nov 17, 2020 · 1 comment

Comments

@KrishnaPG
Copy link

Currently there is only one timestamp in the options while the stacktraces is an array. For debugging the timing issues, it is preferable to have each of the stacktraces entry be associated with its own timestamp. For jobs that are repeated and failed often, this helps much.

@skeggse
Copy link
Member

skeggse commented Nov 17, 2020

Oh, good idea! We'll need to be careful about how this intersects with other readers of the data model like arena, and figure out what a migration strategy would look like in practice.

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

No branches or pull requests

3 participants