Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@vmcj
Copy link
Collaborator

@vmcj vmcj commented May 18, 2025

We use this often for DOMjudge so it helps to detect some of the raised issues automatically.

I didn't update the eclipse part as I don't know (yet) how to set that one up. I think this can be extended to send the error to Sentry each time that the Trace has a level of ERROR and merging the Trace & Sentry calls in a custom wrapper. Before I put in that time I would like to know if this is even something which is wanted.

Copy link
Collaborator

@nickygerritsen nickygerritsen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like sentry so I'm all for it. We should find a way to have the properties file not be hardcoded in git maybe though? I think we could use an env var / system property

@vmcj
Copy link
Collaborator Author

vmcj commented May 18, 2025

I like sentry so I'm all for it. We should find a way to have the properties file not be hardcoded in git maybe though? I think we could use an env var / system property

My idea was to put it in the .gitignore after this is merged, passing an ENV does also work but makes it harder to set the other properties. So a combination is probably needed.

@vmcj
Copy link
Collaborator Author

vmcj commented May 18, 2025

Linked to: #1076

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants