You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by "wu-sheng (via GitHub)" <gi...@apache.org> on 2026/10/18 13:55:44 UTC

[PR] Fix what the LangChain receiver and plugin lost before 0.6.0 [skywalking-ai-sessionizer]

wu-sheng opened a new pull request, #83:
URL: https://github.com/apache/skywalking-ai-sessionizer/pull/83

   Fixes from the release review of 0.6.0 for the LangChain receiver and the LangChain plugin.
   
   ## The receiver and collector
   
   - **A run's arrivals in one request are read together.** A completion that came before its start in one multipart
     request lost its answer and its provider body, and a failed tool could be joined to the wrong call. Every arrival of
     a run is now merged (earlier start, later end), and a response lands after its request even when it came first.
     Neither LangSmith client measured sends that order; a hand-written one can.
   - **A run named only by its path.** LangSmith JS with `autoBatchTracing: false` sends `PATCH /runs/{id}` with no id in
     the body, which was refused with 400, so every run's end was lost. The id is taken from the path; a body id that
     disagrees is refused. Receiver and collector share one rule.
   - **A model call traced on its own.** A root chat model run's `inputs.messages` is a list of lists, which the reader
     took for a flat list, so the person's question did not land as external input.
   - **Pending trace memory.** A long-running trace kept every descendant run id for ever. A trace now forgets a run when
     the run is forgotten, keeping the runs a remembered run ran inside.
   
   ## The plugin
   
   - **Which project a tool's changes are filed under.** The plugin took the project from the environment, while a
     tracer given `project_name` put the run under another one, so changes landed under the wrong conversation. The plugin
     now sends a tool's begin record once both it and the tracer have been told of the tool's start, with the project of
     the tracer that traces the tool's run. A tool no tracer traces, or traced with tracing turned off, records nothing,
     since there is no run to join its changes to. The limits of what it can tell are on the plugin's setup page.
   - CI installs `langchain-core` and `langsmith` at the versions the capture harness measured, so these tests run there.
   
   ## Checked
   
   - `make check` passes; the plugin's 27 tests pass with LangChain installed. Every collector test lands and parses
     twice, and each guard was proven by reverting it.
   


-- 
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: notifications-unsubscribe@skywalking.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] Fix what the LangChain receiver and plugin lost before 0.6.0 [skywalking-ai-sessionizer]

Posted by "wu-sheng (via GitHub)" <gi...@apache.org>.
wu-sheng merged PR #83:
URL: https://github.com/apache/skywalking-ai-sessionizer/pull/83


-- 
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: notifications-unsubscribe@skywalking.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org