hutiefang76 opened a new pull request, #12633:
URL: https://github.com/apache/seatunnel/pull/12633

   ### Purpose of this pull request
   
   Conversation summaries bypassed the redaction used for saved history: 
recognized credentials could reach the summarization model or remain in the 
stored summary. Redact the selected messages before truncation and model 
submission, then redact both generated and directly updated summaries before 
saving.
   
   ### Does this PR introduce _any_ user-facing change?
   
   Yes, in dev. Recognized credentials are removed from summary prompts and 
stored summaries using the existing redaction policy. This is not a guarantee 
of detecting every secret format. The original in-memory conversation remains 
unchanged.
   
   ### How was this patch tested?
   
   - `python3 -m pytest -q`: 214 passed, 3 subtests passed. Mocked model tests 
cover input/output redaction, direct summary updates and credentials longer 
than the prompt snippet limit.
   - Root `-N spotless:apply` and `-N -DskipTests verify` passed. Modified 
Python files passed the fatal-error Ruff checks.
   - Full-repository `-DskipTests verify` was attempted but stopped at 
`seatunnel-engine-ui`: the npm mirror returned HTTP 403 for `tslib-2.3.0.tgz`. 
This is not a successful full-repository build.
   
   ### Check list
   
   * [x] No new JAR binary or dependency is added.
   * [x] EN/ZH documentation updated.
   * [ ] Incompatibility guide updated. Not applicable: no schema or 
configuration incompatibility.
   * [ ] Connector registration updates: not applicable.
   
   Implemented with Codex assistance; the reproduction and checks above were 
run against this branch.
   
   ---
   [![Compound 
Engineering](https://img.shields.io/badge/Built_with-Compound_Engineering-6366f1)](https://github.com/EveryInc/compound-engineering-plugin)
   


-- 
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]

Reply via email to