-
Notifications
You must be signed in to change notification settings - Fork 147
fix(rest): map invalid history length to InvalidParamsError #715
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
Merged
ehsavoie
merged 10 commits into
a2aproject:main
from
Zhang-Charlie:fix/rest-historylength-validation
Mar 12, 2026
Merged
Changes from 1 commit
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
c41100d
fix(rest): map invalid history length to InvalidParamsError
Zhang-Charlie 758f24e
fix(rest): scope historyLength validation handling in getTask
Zhang-Charlie 3ac5f90
fix(cloud-deployment): use Strimzi-supported Kafka version
Zhang-Charlie ad84170
Revert "fix(cloud-deployment): use Strimzi-supported Kafka version"
Zhang-Charlie 4d7cb1d
Merge branch 'main' into fix/rest-historylength-validation
ehsavoie 91fd77d
Merge branch 'main' into fix/rest-historylength-validation
Zhang-Charlie c2bbaab
fix(rest): return problem+json for historyLength validation errors
Zhang-Charlie c330b8c
Merge branch 'main' into fix/rest-historylength-validation
ehsavoie 105345a
fix: throw InvalidParamsError instead of wrapping in problem response
Zhang-Charlie a32ae7d
refactor(rest): remove duplicate createProblemErrorResponse in RestHa…
Zhang-Charlie File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Catching the generic
IllegalArgumentExceptionis a bit risky here. While it correctly handles the invalidhistoryLengthcase fromTaskQueryParams, it could also catchIllegalArgumentExceptionthrown from other parts of thetryblock (e.g., a bug in an implementation ofrequestHandler.onGetTask). Such cases would indicate a server-side issue and should result in a 500 error, but would be incorrectly reported as a 422 client error.To make this more robust, you could check the exception message to ensure you're only handling the specific error you expect. This avoids masking potential server-side bugs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the review. I agree with the concern about catching IllegalArgumentException too broadly.
I updated the implementation to scope the IllegalArgumentException handling to only the TaskQueryParams construction path, so only parameter-validation failures map to InvalidParamsError (422). Exceptions from downstream logic (e.g., requestHandler.onGetTask) are no longer reclassified as client errors.
Updated in commit 758f24e on this PR branch.