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

crash reporting v2 #733

Closed
mvines opened this issue Jul 23, 2018 · 2 comments
Closed

crash reporting v2 #733

mvines opened this issue Jul 23, 2018 · 2 comments
Labels
stale [bot only] Added to stale content; results in auto-close after a week.
Milestone

Comments

@mvines
Copy link
Member

mvines commented Jul 23, 2018

v1 crash reporting just emits a metrics datapoint so we know the event occurred (#651), but this is not enough to debug crashes effectively. We need a mechanism to grab the backtrace and recent stdout/stderr output from a panicking or crashing fullnode, perhaps even a core dump in certain situations.

@mvines mvines added this to the The Future! milestone Jul 23, 2018
@stale
Copy link

stale bot commented Sep 17, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale [bot only] Added to stale content; results in auto-close after a week. label Sep 17, 2020
@stale
Copy link

stale bot commented Sep 24, 2020

This stale issue has been automatically closed. Thank you for your contributions.

@stale stale bot closed this as completed Sep 24, 2020
vkomenda pushed a commit to vkomenda/solana that referenced this issue Aug 29, 2021
Bumps [eslint](https://github.com/eslint/eslint) from 7.12.0 to 7.12.1.
- [Release notes](https://github.com/eslint/eslint/releases)
- [Changelog](https://github.com/eslint/eslint/blob/master/CHANGELOG.md)
- [Commits](eslint/eslint@v7.12.0...v7.12.1)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
stale [bot only] Added to stale content; results in auto-close after a week.
Projects
None yet
Development

No branches or pull requests

1 participant