sentry.README.md

Currently using "@sentry/browser" instead of '@sentry/electron' because of bugs long ago, which could be fixed by now. As a result we're only getting errors from the Render process.

This is currently hosted at sentry.io.

1. curl -sL https://sentry.io/get-cli/ | bash # may need some other install method on windows

2. Set a LAMETA_SENTRY_AUTH_TOKEN environment variable with a sentry auth token that has permissions org:read, project:read, project:releases

3. run ./make-sentry-release.sh in a bash shell

Other commands: sentry-cli login Note that while the ./make-sentry-release.sh will use the LAMETA_SENTRY_AUTH_TOKEN environment variable, these raw sentry-cli commands do not know about it. sentry-cli releases files \$VERSION list start over with the uploads: sentry-cli releases files \$VERSION delete --all

--- Troubleshooting ---

The sentry-cli is fairly user-hostile at the moment. Note the required ordering here (ref):

sentry-cli projects -o "onset-org" list sentry-cli repos -o "onset-org" list Note that even if you set SENTRY_ORG, you cannot omit -o parameter.

However I've added .sentryclirc with the org and project set, so you can omit the other parameters. YOu would need to add your own:

[defaults]
url=https://sentry.io/
org=onset-org
project=lameta

[auth]
token=the api token

These should all work

sentry-cli info sentry-cli repos list sentry-cli projects list sentry-cli releases list

---

Note about source-map-support, and how it messes this up.

If you want to rely on Sentry's source map resolution, make sure that your code is not using the source-map-support package, as it overwrites the captured stack trace in a way that makes it impossible for our processors to correctly parse it.

getsentry/sentry-javascript#2929 questions using "source-map-support".

So I removed source-map-support, no change in the frame we're sending.

I investigated source-map-support

Normally if I do yarn build-production-renderer && yarn start then do the test throw, I get frame of {lineno:467 colno: 43411 filename: render-bundle.js} This is actually correct... it points to the line where the throw happened.

If I add import "source-map-support/register"; at the top of menu.ts, then I get {lineno:19 colno: 294 filename: menu.ts}. Which is what it is supposed to do. However sentry clearly says they cannot handle that.

older notes

Problem: sentry-cli seems to read AUTH from sentry.properties (which is committed and thus low permissions), rather than the key I give it in sentry-cli login.