mirror of https://github.com/zulip/zulip.git
2d5c678614
This removes the production reporting to `/json/report/error` upon `blueslip.error`, and replaces it with reporting to Sentry, if enabled. Sentry provides better reporting and grouping for exceptions than the email- and `#errors`-reporting provided by the `/json/report/error` endpoint. The development behaviour of rendering `blueslip.error` messages and stacktraces immediately, and stopping execution, is preserved. To better chain exception information, the whole previous exception is passed to `blueslip.error`, not just the stack, and the second parameter is formalized to be an object to map to Sentry's "context" concept. |
||
|---|---|---|
| .. | ||
| _static | ||
| _templates | ||
| contributing | ||
| development | ||
| documentation | ||
| git | ||
| images | ||
| outreach | ||
| overview | ||
| production | ||
| subsystems | ||
| testing | ||
| translating | ||
| tutorials | ||
| .gitignore | ||
| Makefile | ||
| README.md | ||
| THIRDPARTY | ||
| code-of-conduct.md | ||
| conf.py | ||
| index.md | ||
README.md
Zulip Markdown documentation hosted elsewhere
The Markdown files in this directory ( /zulip/docs ) are not intended to be read on GitHub. Instead, visit our ReadTheDocs to read the Zulip documentation.