* Use Sentry Error boundary.
* Add a button for throwing error to test the sentry error boundary.
* trigger an error during rendering.
* Move the throwing of error.
* Fix the error boundary state.
* Try to throw an error from the project list.
* Revert to using react error boundary.
* Minor fixes.
* Add an example page for throwing an exception to be caught by Sentry. Remove the error filter from the Sentry client config.
* Remove config for allowing errors only from our code.
* When capturing an exception with Sentry, add a tag if the exception is in the boundary.
* Minor fixes.
* Remove testing code.
* Move forgotten code.
* Add a function for anonymized user id.
* Set the sentry user id by anonymizing the actual user id.
* Don't send Sentry reports if the user hasn't consented to the telemetry.
* Add a helper function whether the studio can send telemetry data.
* Reuse the helper function in the _app file.
* First round of wrapping RQ errors with handleError
* Remove the throw before the handleError usage.
* Make the handling of an API error more versatile. Add logging in Sentry if the error is of unknown type.
* Remove throwing of the handleError function.
* Add return type to the handleError function to be never so that we're sure it always throws.
* Second round of wrapping RQ errors with handleError
* Temp fix in delete credential mutation, and fix loading state
---------
Co-authored-by: Ivan Vasilov <vasilov.ivan@gmail.com>
Fix mistake in users.mdx
Generally I dont like fixing spelling mistakes in repos, but this one specifically is bothering me as I am already slightly confused by Row Level Security, in particular when to use the Postgres roles, and when to use application roles (like making a `profile` table where each profile has a `role` column). This is a mistake, or not?
* First round of wrapping RQ errors with handleError
* Remove the throw before the handleError usage.
* Make the handling of an API error more versatile. Add logging in Sentry if the error is of unknown type.
* Remove throwing of the handleError function.
* Add return type to the handleError function to be never so that we're sure it always throws.
---------
Co-authored-by: Ivan Vasilov <vasilov.ivan@gmail.com>
* Support more granular updates via events for spinning up replica
* Add duration estimates as tooltips
* Show granular error message if error happens during replica set up
* Add support for hours in duration estimates
* Make the sentry message more explanatory.
* Add intentional error for testing the sentry reports.
* Fix the intentional errors.
* Remove the buttons for testing.
* Remove feature preview for the conversational AI for SQL editor.
* Remove all code related to the previous implementation of editor ai.
* Update the snapshots for the ai commands.
* Remove unneeded code from the ai panel.
* Show the diff bar when debugging.
* Convert the updateEditor function into a callback.
* Simplify the debugging functionality by using react state instead of react context.
* Erase the AI disclaimer when formatting code as modification.
* Add a button to clear the chat history.
* Init replication lag chart in database reports
* Navigate to replication lag chart via query params
* Add view replication lag CTA in map view
* Add replication lag metric to instance node view
* Prettier
* Support checking API reports by replicas
* Fix API report for replica and add error handling
* Fix tests
* Add load balancer as an option for API reports
Ivan Vasilov