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.

Sign up for GitHub

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

Jump to bottom

Add a bug tracker #196

Open
sgkim126 opened this issue Jun 12, 2018 · 3 comments
Open

Add a bug tracker #196

sgkim126 opened this issue Jun 12, 2018 · 3 comments

Comments

@sgkim126
Copy link
Contributor

sgkim126 commented Jun 12, 2018 •
edited by kseo

We need a bug tracker like sentry.
@sgkim126 sgkim126 mentioned this issue Jun 12, 2018
Open
@sgkim126 sgkim126 added this to the Testnet milestone Aug 8, 2018
@kseo kseo removed the enhancement label Aug 11, 2018
@kseo kseo removed this from the Testnet milestone Aug 14, 2018
@sgkim126 sgkim126 added this to the Release Candidate milestone Jan 9, 2019
@majecty majecty self-assigned this Feb 25, 2019
@majecty
Copy link
Contributor

majecty commented Feb 25, 2019

I want to see the call stack of the panicked node easily.

@kseo
Copy link
Member

kseo commented May 3, 2019

@majecty any progress? does codechain-dashboard support this?

@sgkim126
Copy link
Contributor Author

sgkim126 commented May 3, 2019 •
edited by kseo

@kseo We don't work on this issue. And I have a question whether we really need it. Reporting the backtrace without other context doesn't give enough information for debugging.

@kseo kseo removed this from the Release Candidate milestone May 15, 2019
@kseo kseo changed the title Add bug tracker Add a bug tracker May 15, 2019
@majecty majecty removed their assignment Dec 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@majecty @sgkim126 @kseo