@ultmaster , this PR is updating the langchain to 1.x. There were some other conflicts outside of the verl numpy version. There was also an incompatibility with openai version requirements between langchain and vllm so I opted for conflict groups instead. There is only one CI failure due to the new conflict groups. Do you think we can update the build or would prefer a different solution than the conflict groups?

Run uv sync --frozen \Using CPython 3.12.3 interpreter at: /usr/bin/python3.12Creating virtual environment at: .venvwarning: The`extra-build-dependencies` option is experimental and may change without warning. Pass`--preview-features extra-build-dependencies` to disable this warning.error: Extra`verl` and group`agents` are incompatible with the declared conflicts: {`agentlightning[verl]`,`agentlightning:agents`}

verl must run together within the same env as langchain. It's not a hard requiement, but that's how our CI works.

Before we goes into the pain of refactoring CI, maybe you can add numpy >= 2.1.0 to override-dependency to see whether CI works. VERL might not have a strong opinion about numpy; they just falsely constrain the dependency for safety.

Related work:#350

@ultmaster , I did what you suggested. Checks CI is passing. Let me know how the review goes.

please rerun uv lock and check in uv.lock

please rerun uv lock and check in uv.lock

The uv lock is up to date. The second commit (numpy > 2.x) was the last one to include changes to the uv lock.

please rerun uv lock and check in uv.lock

Ah, I see the conflicts. I will pull the main changes and resolve

I notice uv.lock is 55MB now. I don't think it makes sense. Let me pull the head and try to lock it myself.

That indeed produces 33MB! I think maybe we have introduced some conflicting groups by mistake.

I found the correct solution. We have to remove langchain first and lock once and add langchain again to lock again. let me push it.

I found the correct solution. We have to remove langchain first and lock once and add langchain again to lock again. let me push it.

That was a good catch. Looks like there are now some test errors that need the langchain dependency, can I move on to fix them or do you still have changes to make?

please fix the unit-tests. Then I'll proceed to run example tests to see if there are more errors popping up.

@ultmaster , the tests are fixed now in CI