Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue 50179: Exceptions logged by Radeox are difficult to track #5802

Merged
merged 4 commits into from
Aug 27, 2024

Conversation

labkey-jeckels
Copy link
Contributor

Rationale

Radeox can spam our log files when it encounters non-fatal issues rendering wikis. In general, we want to capture a pointer back to the original source so that we can determine if there's a real problem. And in most cases, we want to relax the logging and simply render the original text even if Radeox can't interpret it.

Changes

  • Pass a sourceDescription through to Radeox so we can point to the wiki, announcement, etc where the source came from
  • Update to a new Radeox version that quiets a little logging and adds the sourceDescription via the RenderContext in error messages

@labkey-jeckels labkey-jeckels merged commit f85632a into develop Aug 27, 2024
3 checks passed
@labkey-jeckels labkey-jeckels deleted the fb_50179_radeoxLogging branch August 27, 2024 16:58
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