fix(agents): pin boto3/langchain-aws to fix pip resolution-too-deep (ASTD-164)#33
Merged
Merged
Conversation
…ASTD-164) `pip install nemo-platform[services]` failed during dependency resolution with `Dependency resolution exceeded maximum depth`. The resolver backtracked across the full boto3 release history while resolving `langchain-aws` via `nvidia-nat-langchain` (kitchen-sink) in the `nemo-agents-plugin` extra. The workspace already constrains these via uv `override-dependencies`, but those overrides don't reach the published wheel. Carry the same bounds in the plugin's declared deps so they propagate to the `nemo-platform[services]` extra: langchain-aws==1.1.0 boto3>=1.40.46,<1.40.62 botocore>=1.40.46,<1.40.62 The `<1.40.62` upper bound matches `aiobotocore 2.25.1`'s cap (required by `aioboto3 15.5.0` in files-service). A wider pin lets pip backtrack on aiobotocore + wrapt + yarl simultaneously. Verified with `pip install --dry-run dist/nemo_platform-*.whl[services]` in a fresh venv: resolution completes cleanly (334 packages).
mckornfield
approved these changes
May 22, 2026
Contributor
mckornfield
left a comment
mckornfield
left a comment
There was a problem hiding this comment.
each day the deptree grows
Contributor
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
pip install nemo-platform[services]fails during dependency resolution withDependency resolution exceeded maximum depth. The resolver backtracks across the fullboto3release history while resolvinglangchain-aws(pulled in vianvidia-nat-langchaininnemo-agents-plugin).override-dependenciesin the rootpyproject.toml, but those overrides don't reach the published wheel. This PR carries the same bounds inplugins/nemo-agents/pyproject.tomlso they propagate to thenemo-platform[services]extra:langchain-aws==1.1.0boto3>=1.40.46,<1.40.62botocore>=1.40.46,<1.40.62<1.40.62upper bound matchesaiobotocore 2.25.1's cap (required byaioboto3 15.5.0in files-service). A wider pin lets pip backtrack onaiobotocore+wrapt+yarlsimultaneously and time out.Linear: https://linear.app/nvidia/issue/ASTD-164
Test plan
uv build --wheel packages/nemo_platform.pip install --dry-run dist/nemo_platform-*.whl[services]— resolution completes cleanly (334 packages, exit 0). Before the fix this aborted withresolution-too-deep.uv lock --checkpasses.