5 Commits (8c986221e4b5bd3de204ff9dd303454ca9a94786)

Author	SHA1	Message	Date
Predrag Gruevski	7e63270e04	Ensure the in-project venv gets cached in CI tests. (#9336) ... The previous caching configuration was attempting to cache poetry venvs created in the default shared virtualenvs directory. However, all langchain packages use `in-project = true` for their poetry virtualenv setup, which moves the venv inside the package itself instead. This meant that poetry venvs were not being cached at all. This PR ensures that the venv gets cached by adding the in-project venv directory to the cached directories list. It also makes sure that the cache key *only* includes the lockfile being installed, as opposed to *all lockfiles* (unnecessary cache misses) or just the *top-level lockfile* (cache hits when it shouldn't).	1 year ago
Harrison Chase	f35db9f43e	(WIP) set up experimental (#7959)	1 year ago
Eugene Yurtsev	3ecd7c9641	Add check to verify poetry.toml (#4794) ... # Add poetry check to github action Check poetry toml file during tests for errors	1 year ago
Eugene Yurtsev	14bedf1cc5	Github Action: Fix poetry lock file checking (#4789) ... Fix how poetry lock file is checked to avoid skipping caches silently.	1 year ago
Eugene Yurtsev	80558b5b27	Add workflow for testing with all deps (#4410) ... # Add action to test with all dependencies installed PR adds a custom action for setting up poetry that allows specifying a cache key: https://github.com/actions/setup-python/issues/505#issuecomment-1273013236 This makes it possible to run 2 types of unit tests: (1) unit tests with only core dependencies (2) unit tests with extended dependencies (e.g., those that rely on an optional pdf parsing library) As part of this PR, we're moving some pdf parsing tests into the unit-tests section and making sure that these unit tests get executed when running with extended dependencies.	1 year ago