langchain-ai/docs
1
0
Fork 0
mirror of https://github.com/langchain-ai/docs.git synced 2026-07-22 12:25:55 -04:00
Code Issues 490 Packages Projects Releases Wiki Activity

[PR #1205] [MERGED] docs: Enhance HumanInTheLoopMiddleware configuration for email review #1376

New Issue
Closed
opened 2026-02-17 17:22:15 -05:00 by yindo · 0 comments
yindo commented 2026-02-17 17:22:15 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/1205
Author: @mcavdar
Created: 10/30/2025
Status: ✅ Merged
Merged: 11/18/2025
Merged by: @lnhsingh

Base: main ← Head: patch-11

📝 Commits (3)

  • d9907f2 Enhance HumanInTheLoopMiddleware configuration for email review
  • 05158ac enabled field is not part of InterruptOnConfig
  • 84290a4 Merge branch 'main' into patch-11

📊 Changes

1 file changed (+10 additions, -6 deletions)

View changed files

📝 src/oss/python/migrate/langchain-v1.mdx (+10 -6)

📄 Description

Overview

The current config produces an issue:

Traceback (most recent call last):
  File "<stdin>", line 4, in <module>
  File "/home/mc/.venv-langchain-v1/lib/python3.10/site-packages/langchain/agents/middleware/human_in_the_loop.py", line 193, in __init__
    elif tool_config.get("allowed_decisions"):
AttributeError: 'str' object has no attribute 'get'

The old example conflicts with the configuration options described in LangChain’s documentation

The description field is part of InterruptOnConfig, so the dictionary value should be an InterruptOnConfig object.

Type of change

Type: [Update existing documentation /bug/Remove outdated content]

Related issues/PRs

  • GitHub issue:
  • Feature PR:
  • Linear issue:
  • Slack thread:

Checklist

  • I have read the contributing guidelines
  • I have tested my changes locally using docs dev
  • All code examples have been tested and work correctly
  • I have used root relative paths for internal links
  • I have updated navigation in src/docs.json if needed
  • I have gotten approval from the relevant reviewers
  • (Internal team members only / optional) I have created a preview deployment using the Create Preview Branch workflow

Additional notes

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langchain-ai/docs/pull/1205 **Author:** [@mcavdar](https://github.com/mcavdar) **Created:** 10/30/2025 **Status:** ✅ Merged **Merged:** 11/18/2025 **Merged by:** [@lnhsingh](https://github.com/lnhsingh) **Base:** `main` ← **Head:** `patch-11` --- ### 📝 Commits (3) - [`d9907f2`](https://github.com/langchain-ai/docs/commit/d9907f2fc2b3cd79525c7a8c0609e78c2d519631) Enhance HumanInTheLoopMiddleware configuration for email review - [`05158ac`](https://github.com/langchain-ai/docs/commit/05158ac2012f855f592945f81b2843d18ae12e2d) enabled field is not part of InterruptOnConfig - [`84290a4`](https://github.com/langchain-ai/docs/commit/84290a4cfa1c314a2932f7d89d29e6ee32af9241) Merge branch 'main' into patch-11 ### 📊 Changes **1 file changed** (+10 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `src/oss/python/migrate/langchain-v1.mdx` (+10 -6) </details> ### 📄 Description ## Overview The current config produces an issue: ``` Traceback (most recent call last): File "<stdin>", line 4, in <module> File "/home/mc/.venv-langchain-v1/lib/python3.10/site-packages/langchain/agents/middleware/human_in_the_loop.py", line 193, in __init__ elif tool_config.get("allowed_decisions"): AttributeError: 'str' object has no attribute 'get' ``` The old example conflicts with the configuration options described in [LangChain’s documentation](https://docs.langchain.com/oss/python/langchain/middleware#human-in-the-loop) The description field is part of InterruptOnConfig, so the dictionary value should be an InterruptOnConfig object. ## Type of change **Type:** [Update existing documentation /bug/Remove outdated content] ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-17 17:22:15 -05:00
yindo closed this issue 2026-02-17 17:22:15 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
deepagents
docs-infra
external
external
help wanted
integration
internal
internal
javascript
js/ts
langchain
langgraph
langsmith
needs-title
pull-request
Mirrored from GitHub Pull Request
 python
reference
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/docs#1376
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?