Conversation
Send a relay_session_root UUID in the Fabric caller context for every turn of a platform agent session. Fabric adapters that own an in-process Relay scope use it as the propagation root, and Relay 0.9 derives the ATIF session id from the root, so the turns land in Intake as one session with a trajectory each. Platform session ids are not UUIDs, so the root is a UUIDv5 of the session id under a fixed namespace. Fabric 0.4.0 ignores the key; this takes effect with the Fabric release that includes NVIDIA/NeMo-Fabric#358. Signed-off-by: mschwab <mschwab@nvidia.com>
❌ ErrorsYour PR has failed checks. Please review the issues below and take necessary action before merging. 🚦 4 Pipeline jobs failed
Useful? React with 👍 / 👎 This comment will be updated automatically if new data arrives.🔗 Commit SHA: e104d0a | Docs | View more details | Give us feedback! |
Contributor
|
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Each turn of a platform agent session now sends
relay_session_rootin the Fabric caller context, next tosession_id. It is a UUIDv5 of the platform session id under a fixed namespace, so every turn of one session sends the same value and different sessions never collide. Platform session ids are not UUIDs, which is why the key cannot just carrysession_id.Why
Studio chats and other session-backed calls land in Intake as one session per turn. Relay 0.9 derives the ATIF
session_idfrom the propagation root, and Fabric roots propagation at each request unless the caller supplies a session root. NVIDIA/NeMo-Fabric#358 adds that key; this sends it, so a conversation records as one Intake session with one trajectory per turn.Dependencies and limits
X-Nemo-Session-Idare unchanged.Still to land before this is ready
nemo-fabric*pins to the release with feat: root Relay propagation at the caller's session NVIDIA/NeMo-Fabric#358 and relock.session_id: ClickHouse spans and the evaluation rollup group onsession_id, andtrajectory_idbecomes the unique key.session_idwith distincttrajectory_id.Verification
plugins/nemo-agents/tests/unit/test_fabric_server.pyandtest_fabric_runtime.py: 67 passed. Newtest_turns_of_one_session_share_a_relay_session_rootpins a stable root per session, a distinct root per session, and a root Relay can use.tyclean.