Qiao-yq opened a new pull request, #1608:
URL: https://github.com/apache/dubbo-admin/pull/1608

   **Please provide a description of this PR:**
   
   Draft. This PR is blocked by and must be merged after 
[#1596](https://github.com/apache/dubbo-admin/pull/1596).
   
   Recheck Session access before each model iteration while retaining the 
interaction's stable context snapshot. This prevents an already-loaded snapshot 
from being used for another model call after the Session becomes inaccessible.
   
   - keep the latest #1596 context-window implementation, message ordering, 
snapshot transaction, and Agent defaults
   - document the shared context-window contract and extend Memory/GORM 
regression coverage for zero/bounded/oversized windows, inactive or missing 
Turns, deep copies, and snapshot stability after appends
   - narrow the legacy-Session adoption helper to the capability it actually 
uses
   
   This is the prerequisite fix for the production authentication and 
usage/audit PR. It adds no JWT adapter or accounting records.
   
   While #1596 is open, GitHub's comparison against `ai` also includes its 
dependency changes. The changes on top of #1596 can be reviewed 
[here](https://github.com/Qiao-yq/dubbo-admin/compare/6ada40334596bc938829b349ac075a7a6bcbb480...fix/ai-1539-context-window).
   
   Validation from `ai/`:
   
   - `go test ./... -timeout 120s`
   - `go test -race ./component/agent/react ./component/server/... ./store/... 
-timeout 180s`
   - `git diff --check`
   
   GORM tests use SQLite; this does not establish production MySQL/PostgreSQL 
acceptance.
   
   Part of #1539. Blocked by #1596.
   
   **To help us figure out who should review this PR, please put an X in all 
the areas that this PR affects.**
   
   - [ ] Docs
   - [ ] Installation
   - [ ] User Experience
   - [ ] Dubboctl
   - [ ] Console
   - [x] Core Component
   
   **Please check any characteristics that apply to this pull request.**
   
   - [x] Includes tests
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to