Skip to content

Fix invalid backend message#8772

Closed
bharos wants to merge 1 commit intoapache:mainfrom
bharos:fix-invalid-backend-message
Closed

Fix invalid backend message#8772
bharos wants to merge 1 commit intoapache:mainfrom
bharos:fix-invalid-backend-message

Conversation

@bharos
Copy link
Contributor

@bharos bharos commented Oct 7, 2025

What changes were proposed in this pull request?

(Please outline the changes and how this PR fixes the issue.)

Why are the changes needed?

(Please clarify why the changes are needed. For instance,

  1. If you propose a new API, clarify the use case for a new API.
  2. If you fix a bug, describe the bug.)

Fix: #(issue)

Does this PR introduce any user-facing change?

(Please list the user-facing changes introduced by your change, including

  1. Change in user-facing APIs.
  2. Addition or removal of property keys.)

How was this patch tested?

(Please test your changes, and provide instructions on how to test it:

  1. If you add a feature or fix a bug, add a test to cover your changes.
  2. If you fix a flaky test, repeat it for many times to prove it works.)

@bharos bharos force-pushed the fix-invalid-backend-message branch 3 times, most recently from e2f905d to a1b123e Compare October 7, 2025 21:04
- Replace hardcoded catalog lists with dynamic enum extraction
- Improve error handling pattern for invalid catalog types
@bharos bharos force-pushed the fix-invalid-backend-message branch from a1b123e to 3be7dda Compare October 7, 2025 21:08
@bharos bharos closed this Oct 7, 2025
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.

1 participant