Skip to content

[26.0] Fix error handling for Help Forum integration#22604

Open
davelopez wants to merge 2 commits intogalaxyproject:release_26.0from
davelopez:26.0/fix_forum_error_handling
Open

[26.0] Fix error handling for Help Forum integration#22604
davelopez wants to merge 2 commits intogalaxyproject:release_26.0from
davelopez:26.0/fix_forum_error_handling

Conversation

@davelopez
Copy link
Copy Markdown
Contributor

Fixes #22599

The Help forum returned Service Unavailable (503), but there was no error handling in the /api/help/forum/search endpoint. The JSONDecodeError: Expecting value: line 1 column 1 (char 0) error in #22599 was somewhat misleading because response.json() was trying to parse the 503 HTML error as JSON.

This properly handles most errors and surfaces the connectivity ones to the user to clarify expectations. Potential parsing errors are still considered internal, but should be reported more clearly in Sentry.

How to test the changes?

  • I've included appropriate automated tests.
  • This is a refactoring of components with existing test coverage.
  • Instructions for manual testing are as follows:
    1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

  • I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

@mvdbeek
Copy link
Copy Markdown
Member

mvdbeek commented May 3, 2026

Could the connection error handling could potentially be masking real issues that require some kind of server action (like updating the url, certificate checks etc)? I've been ignoring a low error rate in Sentry so far.

Enhances error reporting and logging for Help Forum API failures,
distinguishing between connection errors, timeouts, client errors,
and server errors. Provides more actionable error messages for
misconfiguration cases and improves diagnostics for administrators.
@davelopez
Copy link
Copy Markdown
Contributor Author

Good point! The last commit suggested by Copilot should ensure that actionable errors are reported to Sentry with better exception details.

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

Projects

Status: Needs Review

Development

Successfully merging this pull request may close these issues.

2 participants