langchain

Commit Graph

Author	SHA1	Message	Date
Eugene Yurtsev	146616aa5d	Test workflow, fix minor typos (#4495 ) # Fix 2 minor typos in test workflow. This PR does not result in any functional changes.	1 year ago
Eugene Yurtsev	f373883c1a	Refactor test workflow (#4457 ) # Refactor the test workflow This PR refactors the tests to run using a single test workflow. This makes it easier to relaunch failing tests and see in the UI which test failed since the jobs are grouped together. ## Before submitting ## Who can review?	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
Zander Chase	0870a45a69	Add Pull Request Template (#4247 )	1 year ago
Zander Chase	cc068f1b77	Add Issue Templates (#4021 ) Add issue templates for - bug reports - feature suggestions - documentation and a link to the discord for general discussion. Open to other suggestions here. Could also add another "Other" template with just a raw text box if we think this is too restrictive <img width="1464" alt="image" src="https://user-images.githubusercontent.com/130414180/236115358-e603bcbe-282c-40c7-82eb-905eb93ccec0.png">	1 year ago
Ehsan M. Kermani	5d0674fb46	Use a consistent poetry version everywhere (#3250 ) Fixes the discrepancy of poetry version in Dockerfile and the GAs	1 year ago
Noah Gundotra	577ec92f16	Include testing instructions for getting setup in CONTRIBUTING.md (#3020 ) Running tests is good sanity check for new users to ensure their development environment is setup correctly.	1 year ago
sergerdn	90973c10b1	fix: tests with Dockerfile (#2382 ) Update the Dockerfile to use the `$POETRY_HOME` argument to set the Poetry home directory instead of adding Poetry to the PATH environment variable. Add instructions to the `CONTRIBUTING.md` file on how to run tests with Docker. Closes https://github.com/hwchase17/langchain/issues/2324	1 year ago
andrewmelis	7ed8d00bba	Remove extra word in CONTRIBUTING.md (#2370 ) "via by a developer" -> "by a developer" --- Thank you for all your hard work!	1 year ago
Matt Tucker	fa2e546b76	Add workaround for debugpy install issue to contrib docs. (#1835 ) When following the Quick Start instructions in the contributing docs, I was getting a "WheelFileValidationError" on installation of debugpy which was blocking the installation of a number of other deps. Google turned up this [GitHub issue](https://github.com/microsoft/debugpy/issues/1246) indicating a regression in Poetry 1.4.1 and workarounds. This PR updates the contrib docs noting the issue and the workarounds.	1 year ago
Harrison Chase	b053f831cd	Harrison/contributing (#1542 ) Co-authored-by: Saurav Maheshkar <sauravvmaheshkar@gmail.com>	1 year ago
Harrison Chase	012a6dfb16	Harrison/makefile (#1033 ) Co-authored-by: blob42 <contact@blob42.xyz> Co-authored-by: blob42 <spike@w530>	1 year ago
Steven Hoelscher	a5999351cf	chore: add release workflow (#360 ) Adds release workflow that (1) creates a GitHub release and (2) publishes built artifacts to PyPI Release Workflow 1. Checkout `master` locally and cut a new branch 1. Run `poetry version <rule>` to version bump (e.g., `poetry version patch`) 1. Commit changes and push to remote branch 1. Ensure all quality check workflows pass 1. Explicitly tag PR with `release` label 1. Merge to mainline At this point, a release workflow should be triggered because: * The PR is closed, targeting `master`, and merged * `pyproject.toml` has been detected as modified * The PR had a `release` label The workflow will then proceed to build the artifacts, create a GitHub release with release notes and uploaded artifacts, and publish to PyPI. Example Workflow run: https://github.com/shoelsch/langchain/actions/runs/3711037455/jobs/6291076898 Example Releases: https://github.com/shoelsch/langchain/releases -- Note, this workflow is looking for the `PYPI_API_TOKEN` secret, so that will need to be uploaded to the repository secrets. I tested uploading as far as hitting a permissions issue due to project ownership in Test PyPI.	1 year ago
Harrison Chase	9753bccc71	Feature: linkcheck-action (#534 ) (#542 ) - Add support for local build and linkchecking of docs - Add GitHub Action to automatically check links before prior to publication - Minor reformat of Contributing readme - Fix existing broken links Co-authored-by: Hunter Gerlach <hunter@huntergerlach.com> Co-authored-by: Hunter Gerlach <HunterGerlach@users.noreply.github.com> Co-authored-by: Hunter Gerlach <hunter@huntergerlach.com>	1 year ago
Hunter Gerlach	482611f426	unit test / code coverage improvements (#322 ) This PR has two contributions: 1. Add test for when stop token is found in middle of text 2. Add code coverage tooling and instructions - Add pytest-cov via poetry - Add necessary config files - Add new make instruction for `coverage` - Update README with coverage guidance - Update minor README formatting/spelling Co-authored-by: Hunter Gerlach <hunter@huntergerlach.com>	1 year ago
Christian Clauss	2fbb152386	Add Python 3.11 to the testing (#324 )	1 year ago
Christian Clauss	d946be2f3d	Add Python 3.11 to the testing (#323 )	1 year ago
Harrison Chase	3c1c7ba672	update branch name in gha (#274 )	1 year ago
Steven Hoelscher	98fb19b535	chore: use poetry as dependency manager (#242 ) * Adopts [Poetry](https://python-poetry.org/) as a dependency manager * Introduces dependency version requirements * Deprecates Python 3.7 support TODO - [x] Update developer guide - [x] Add back `playwright`, `manifest-ml`, and `jupyter` to dependency group Not Doing => Fast Follow - Investigate single source for version, perhaps relying on GitHub tags and [tackling this issue](https://github.com/hwchase17/langchain/issues/26)	2 years ago
Predrag Gruevski	1a95252f00	Use `pull_request` not `pull_request_target` in GitHub Actions. (#139 ) `pull_request` runs on the merge commit between the opened PR and the target branch where the PR is to be merged — `master` in this case. This is desirable because that way the new changes get linted and tested. The existing `pull_request_target` specifier causes lint and test to run _on the target branch itself_ (i.e. `master` in this case). That way the new code in the PR doesn't get linted and tested at all. This can also lead to security vulnerabilities, as described in the GitHub docs: ![image](https://user-images.githubusercontent.com/2348618/201735153-c5dd0c03-2490-45e9-b7f9-f0d47eb0109f.png) Screenshot from here: https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target Link from the screenshot: https://securitylab.github.com/research/github-actions-preventing-pwn-requests/	2 years ago
Harrison Chase	6cff2837bb	Harrison/fix lint (#80 )	2 years ago
Harrison Chase	9679bdc34c	run workflows on forks (#78 ) per https://stackoverflow.com/questions/58221321/is-github-actions-available-on-forked-repositories	2 years ago
Harrison Chase	18aeb72012	initial commit	2 years ago

... 3 4 5 6 7

323 Commits (master)