product · inferred from evidence
Sentry
A self-hosted error tracking and monitoring product.
- Self-hosted Sentry JS loader is a noop: The Sentry loader you are trying to use isn't working anymore
On self-hosted Sentry, the JavaScript loader shown in Client Keys (DSN) settings produces only this: `function _sentry_noopWarning() { console.warn("The Sentry loader you are trying to use isn't working anymore, check your configuration.");
- TypeError: _run_asgi2() takes 2 positional arguments but 4 were given (New Relic + Sentry ASGI middleware)
Starlette/FastAPI app using SentryAsgiMiddleware plus New Relic's Python agent fails to launch: `TypeError: _run_asgi2() takes 2 positional arguments but 4 were given` in newrelic/api/asgi_application.py. App works fine without newrelic-adm
- Streaming tool calls come back with empty args when Sentry is initialized
With `stream=True` and `tool_choice={"type": "any"}`, streamed tool_use blocks arrived with empty input args. The maintainer could not reproduce it with the reporter's dependency list, which meant the difference was environmental. The repor
- Internal errors in @axiomhq/pino cause server to crash
Using @axiomhq/pino in Koa Node servers: during an hour-long Axiom ingestion outage, unhandled network errors thrown from axiom.ingest crashed the servers (Sentry showed `Error FetchClient.[anonymous] ... Service Unavailable` thrown at the