roshiiiz opened a new pull request, #7821:
URL: https://github.com/apache/texera/pull/7821
<!--
Thanks for sending a pull request (PR)! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
[Contributing to
Texera](https://github.com/apache/texera/blob/main/CONTRIBUTING.md)
2. Ensure you have added or run the appropriate tests for your PR
3. If the PR is work in progress, mark it a draft on GitHub.
4. Please write your PR title to summarize what this PR proposes, we
are following Conventional Commits style for PR titles as well:
- `fix` is for behavior that worked before and no longer does; adding
or
removing a functionality, or reworking one so that user-facing
behavior
intentionally changes, is a `feat`; a change that leaves the
user-facing
behavior unchanged is a `refactor`.
- A test-only PR is `test(<module>): ...`; repairing a broken test is
`fix(test, <module>): ...`.
- A dependency bump is `fix(deps, <module>): ...` when it patches a CVE
and `chore(deps, <module>): ...` otherwise; GitHub Actions bumps take
`ci` as their module, e.g. `chore(deps, ci): ...`.
- A PR targeting a release branch appends the version as the last scope
component, e.g. `fix(deps, frontend, v1.2): ...`.
See CONTRIBUTING.md for the full convention.
5. Be sure to keep the PR description updated to reflect all changes.
-->
### What changes were proposed in this PR?
<!--
Please clarify what changes you are proposing. The purpose of this section
is to outline the changes. Here are some tips for you:
1. If you propose a new API, clarify the use case for a new API.
2. If you fix a bug, you can clarify why it is a bug.
3. If it is a refactoring, clarify what has been changed.
3. It would be helpful to include a before-and-after comparison using
screenshots or GIFs.
4. Please consider writing useful notes for better and faster reviews.
-->
This PR fixes a critical bug where providing a `maxSteps` value of `0` or
negative would cause the agent execution loop to hang indefinitely.
Changes made:
- Updated the Elysia validation schema in `server.ts` to enforce a `{
minimum: 1 }` rule for `maxSteps`. This guarantees the server rejects invalid
limits at the API boundary with a 400 Bad Request.
- Added a fallback boundary clamp using `Math.max(1, updates.maxSteps)` in
`texera-agent.ts` during agent settings updates. This guarantees internal state
strictly enforces the limit even if schema validation is bypassed.
- Added a new automated unit test to `texera-agent.spec.ts` asserting that
`maxSteps` is correctly clamped to 1 if `0` or a negative number is provided.
### Any related issues, documentation, discussions?
<!--
Please use this section to link other resources if not mentioned already.
1. If this PR fixes an issue, please include `Fixes #1234`, `Resolves
#1234`
or `Closes #1234`. If it is only related, simply mention the issue
number.
2. If there is design documentation, please add the link.
3. If there is a discussion in the mailing list, please add the link.
-->
Closes #7484
### How was this PR tested?
<!--
If tests were added, say they were added here. Or simply mention that if the
PR
is tested with existing test cases. Make sure to include/update test cases
that
check the changes thoroughly including negative and positive cases if
possible.
If it was tested in a way different from regular unit tests, please clarify
how
you tested step by step, ideally copy and paste-able, so that other
reviewers can
test and check, and descendants can verify in the future. If tests were not
added,
please describe why they were not added and/or why it was difficult to add.
-->
Tested manually via local API and verified with automated unit tests:
1. Booted the local `agent-service` via `bun run dev`.
2. Issued a `PATCH /api/agents/:id/settings` HTTP request passing
`{"maxSteps": 0}`.
3. Verified the server correctly rejected the payload with a `400 Bad
Request` schema validation error ("Expected number to be greater or equal to
1").
4. Ran the automated `agent-service` test suite (`bun test`) which executes
the new dedicated unit test asserting the clamping behavior. The entire suite
successfully passed.
### Was this PR authored or co-authored using generative AI tooling?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please include the phrase: 'Generated-by: ' followed by the name of the tool
and its version. If no, write 'No'.
Please refer to the [ASF Generative Tooling
Guidance](https://www.apache.org/legal/generative-tooling.html) for details.
-->
Generated-by: Antigravity (DeepMind)
<img width="897" height="301" alt="image"
src="https://github.com/user-attachments/assets/3c6b76c9-0fd2-4609-9a9b-1187e7f19ca0";
/>
=========================================================================================================================================================================================================================================================
<img width="917" height="402" alt="image"
src="https://github.com/user-attachments/assets/7a01398e-0db2-4088-a32f-9f810458d692";
/>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
