Why does the patch_config function delete run_name?

[L-cloud]

Checked other resources

• I added a very descriptive title to this question.
• I searched the LangChain documentation with the integrated search.
• I used the GitHub search to find a similar question and didn't find it.

Commit to Help

• I commit to help with one of those options 👆

Example Code

chain = joke_template | anthropic_client | json_validation_output_parser | db

result = await chain.ainvoke({"user_input": "joke"}, config=RunnableConfig(run_name="test_run"))

Description

This is my code.

chain = joke_template | anthropic_client | json_validation_output_parser | db

result = await chain.ainvoke({"user_input": "joke"}, config=RunnableConfig(run_name="test_run"))

I want to use the run_name in the config within the last chain, db. However, when looking at the ainvoke function, the run_name is removed in patch_config.

try:
    for i, step in enumerate(self.steps):
        # mark each step as a child run
        config = patch_config(
            config, callbacks=run_manager.get_child(f"seq:step:{i+1}")
        )
        if i == 0:
            input = await step.ainvoke(input, config, **kwargs)
        else:
            input = await step.ainvoke(input, config)

The patch_config function is called, and here the run_name is removed.

if callbacks is not None:
    # If we're replacing callbacks, we need to unset run_name
    # As that should apply only to the same run as the original callbacks
    config["callbacks"] = callbacks
    if "run_name" in config:
        del config["run_name"]
    if "run_id" in config:
        del config["run_id"]

Why does del config["run_name"] occur? What problems arise if it is not removed? And if I want to share a parameter across the entire chain, is there a better method than using config?

---

System Info

langchain==0.2.7
langchain-anthropic==0.1.19
langchain-community==0.2.7
langchain-core==0.2.16
langchain-mongodb==0.1.6
langchain-openai==0.1.15
langchain-text-splitters==0.2.2

[dosubot[bot]]

The patch_config function deletes run_name because when replacing callbacks, the run_name should apply only to the same run as the original callbacks. This ensures that the run_name is not incorrectly associated with a different set of callbacks ^[1].

If you want to share a parameter across the entire chain, using the memory object is a better method. The memory object is called at the start and end of every chain, loading variables at the start and saving any returned variables at the end. This allows for sharing parameters across the entire chain without relying on the config object ^[2].

To continue talking to Dosu, mention @dosu.

[L-cloud]

I solved it by simply adding a new key like config={"col_id":"test_run"}.