ccurme 26ad239669 core, openai[patch]: prefer provider-assigned IDs when aggregating message chunks (#31080) ... When aggregating AIMessageChunks in a stream, core prefers the leftmost non-null ID. This is problematic because: - Core assigns IDs when they are null to `f"run-{run_manager.run_id}"` - The desired meaningful ID might not be available until midway through the stream, as is the case for the OpenAI Responses API. For the OpenAI Responses API, we assign message IDs to the top-level `AIMessage.id`. This works in `.(a)invoke`, but during `.(a)stream` the IDs get overwritten by the defaults assigned in langchain-core. These IDs [must](https://community.openai.com/t/how-to-solve-badrequesterror-400-item-rs-of-type-reasoning-was-provided-without-its-required-following-item-error-in-responses-api/1151686/9) be available on the AIMessage object to support passing reasoning items back to the API (e.g., if not using OpenAI's `previous_response_id` feature). We could add them elsewhere, but seeing as we've already made the decision to store them in `.id` during `.(a)invoke`, addressing the issue in core lets us fix the problem with no interface changes.		2025-05-02 11:18:18 -04:00
..
chat_models	core, openai[patch]: prefer provider-assigned IDs when aggregating message chunks (#31080)	2025-05-02 11:18:18 -04:00
embeddings	partners[lint]: run pyupgrade to get code in line with 3.9 standards (#30781)	2025-04-11 07:18:44 -04:00
llms	partners[lint]: run pyupgrade to get code in line with 3.9 standards (#30781)	2025-04-11 07:18:44 -04:00
__init__.py
test_compile.py