Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update @pinecone-database/pinecone dependency to "^3.0.3" #6970

Closed
5 tasks done
ladrians opened this issue Oct 11, 2024 · 2 comments
Closed
5 tasks done

update @pinecone-database/pinecone dependency to "^3.0.3" #6970

ladrians opened this issue Oct 11, 2024 · 2 comments
Labels
auto:bug Related to a bug, vulnerability, unexpected error with an existing feature

Comments

@ladrians
Copy link

Checked other resources

  • I added a very descriptive title to this issue.
  • I searched the LangChain.js documentation with the integrated search.
  • I used the GitHub search to find a similar question and didn't find it.
  • I am sure that this is a bug in LangChain.js rather than my code.
  • The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code

We experienced Pinecone timeout connection issues on a stress test, similar to this output

[cause]: ConnectTimeoutError: Connect Timeout Error (attempted addresses: <ips>)

We were using "@langchain/pinecone": "^0.0.9" updated to "@langchain/pinecone": "^0.1.1" with similar results.

Finally checking some internal dependencies and links decided to directly add and update the dependency @pinecone-database/pinecone dependency to "^3.0.3" and started working.

Not sure what was the internal change there, maybe related to fetching.

Error Message and Stack Trace (if applicable)

The log details

[cause]: ConnectTimeoutError: Connect Timeout Error (attempted addresses: <ips>)

Description

Update the internal dependency for the pinecone store

System Info

node v18.18.2
"@langchain/pinecone": "^0.0.9"

@dosubot dosubot bot added the auto:bug Related to a bug, vulnerability, unexpected error with an existing feature label Oct 11, 2024
@ladrians
Copy link
Author

yes please! it seems to be simple to update the dependency and check on your side the CI/CD cases works fine for pinecone.

@jacoblee93
Copy link
Collaborator

We've bumped to support Pinecone 4.x here: #7175

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto:bug Related to a bug, vulnerability, unexpected error with an existing feature
Projects
None yet
Development

No branches or pull requests

2 participants