search

langchain-ai / langchain

🦜🔗 Build context-aware reasoning applications
https://python.langchain.com
MIT License
84.83k stars 13.11k forks source link

docs: `integrations/providers` fixes #20958

Open leo-gan opened 2 weeks ago

leo-gan commented 2 weeks ago

Fixed documentation inconsistencies, formats. Added descriptions and links. NOTE: I had to change several cookbooks and notebooks (unrelated to this PR) to pass the linking. Changes are small and easy. These changes were inflicted by Updating ruff (... -> 0.4.2)

vercel[bot] commented 2 weeks ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
langchain ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 1, 2024 0:51am
leo-gan commented 2 weeks ago

@baskaryan @efriis @eyurtsev How to deal with errors in the Vercel check? I don't have access to the errors in this check hence cannot fix errors. Does somebody from the LangChain team provide contributors with the error logs or fix them instead of contributors?

sepiatone commented 2 weeks ago

@baskaryan @efriis @eyurtsev How to deal with errors in the Vercel check? I don't have access to the errors in this check hence cannot fix errors. Does somebody from the LangChain team provide contributors with the error logs or fix them instead of contributors?

I had the same problem. On trying to access the Vercel logs I always got a 404 error. (One of the maintainers fixed the problem, whatever it was.)

Is there some way we can have access in an automated way to the error logs? Then we can take responsibility for the correctness of our PRs and only depend on the maintainers for the actual review.

baskaryan commented 1 week ago

@baskaryan @efriis @eyurtsev How to deal with errors in the Vercel check? I don't have access to the errors in this check hence cannot fix errors. Does somebody from the LangChain team provide contributors with the error logs or fix them instead of contributors?

I had the same problem. On trying to access the Vercel logs I always got a 404 error. (One of the maintainers fixed the problem, whatever it was.)

Is there some way we can have access in an automated way to the error logs? Then we can take responsibility for the correctness of our PRs and only depend on the maintainers for the actual review.

it's a good question, @efriis and i should look into some way of propagating the vercel error logs to github