Qihui Xie 57ade13b2b fix llm_inputs duplication problem in intermediate_steps in SQLDatabaseChain (#10279) ... Use `.copy()` to fix the bug that the first `llm_inputs` element is overwritten by the second `llm_inputs` element in `intermediate_steps`. ***Problem description:*** In [line 127]( c732d8fffd/libs/experimental/langchain_experimental/sql/base.py (L127C17-L127C17)), the `llm_inputs` of the sql generation step is appended as the first element of `intermediate_steps`: ``` intermediate_steps.append(llm_inputs) # input: sql generation ``` However, `llm_inputs` is a mutable dict, it is updated in [line 179](https://github.com/langchain-ai/langchain/blob/master/libs/experimental/langchain_experimental/sql/base.py#L179) for the final answer step: ``` llm_inputs["input"] = input_text ``` Then, the updated `llm_inputs` is appended as another element of `intermediate_steps` in [line 180](c732d8fffd/libs/experimental/langchain_experimental/sql/base.py (L180)): ``` intermediate_steps.append(llm_inputs) # input: final answer ``` As a result, the final `intermediate_steps` returned in [line 189](c732d8fffd/libs/experimental/langchain_experimental/sql/base.py (L189C43-L189C43)) actually contains two same `llm_inputs` elements, i.e., the `llm_inputs` for the sql generation step overwritten by the one for final answer step by mistake. Users are not able to get the actual `llm_inputs` for the sql generation step from `intermediate_steps` Simply calling `.copy()` when appending `llm_inputs` to `intermediate_steps` can solve this problem.		2023-10-05 21:32:08 -07:00
..
__init__.py	Update __init__.py (#9955)	2023-09-03 15:02:58 -07:00
base.py	fix llm_inputs duplication problem in intermediate_steps in SQLDatabaseChain (#10279)	2023-10-05 21:32:08 -07:00
prompt.py	Corrected some spelling mistakes and grammatical errors (#10791)	2023-09-19 10:08:59 -07:00
vector_sql.py	Tweak type hints to match dependency's behavior. (#11355)	2023-10-04 22:36:58 -04:00