-
Notifications
You must be signed in to change notification settings - Fork 79
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
[DO NOT MERGE] feat: trigger status-go panic button #16850
Conversation
Jenkins BuildsClick to see older builds (28)
|
d9204e8
to
f1ab2f9
Compare
@igor-sirotin can we get somehow a build for mobile to test it? |
@churik, in this mobile PR status-im/status-mobile#21682 we will get a permanent way to trigger panics via the UI and it will be behind a feature flag, using the same feature flag system we use that is always disabled for users (release builds). I just need to finish it to take it out of draft. In order to test the integration with the production Sentry project, I can temporarily change the PR to allow testing the Sentry panic button as a release build. Then I can easily revert that commit and leave the PR in a mergeable state with the option feature flagged. I'd still keep the feature flagged option to trigger panics because it will be useful again for mobile in the future. |
f1ab2f9
to
6cb7a55
Compare
e08e086
to
9758be5
Compare
Closing this as tested. If needed, we can always pick this up and embed under a feature flag. |
Caution
For testing purposes only. Do not merge.
Description
This PR adds a button that calls the
IntendedPanic
status-go endpoint.How to test
Share usage data with Status
enabledSettings
->Advanced
and clickTrigger status-go panic