Embeddings template needs pinecone update

Similar to https://github.com/wasp-lang/wasp/issues/1725, but now pinecone has released v3 which removes the need for an environment when setting up the API. This makes the tutorial a bit confusing as the example .env file includes PINECON_ENV of which there is now no reference on the Pinecone site. Recommend upgrading to Pinecone ^3.0.2, removing reference to PINECONE_ENV and adding a spec property in the generateEmbeddings.ts file as per pinecone docs
await pinecone.createIndex({
// add this
spec: {
serverless: {
cloud: "aws",
region: "us-east-1",
},
}
});
await pinecone.createIndex({
// add this
spec: {
serverless: {
cloud: "aws",
region: "us-east-1",
},
}
});
GitHub
Issues · wasp-lang/wasp
The fastest way to develop full-stack web apps with React & Node.js. - Issues · wasp-lang/wasp
15 Replies
kapa.ai
kapa.ai2mo ago
Hi @Alex Jukes. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- Thank you for bringing this to our attention. It seems like the Wasp Embedding template needs to be updated to accommodate the changes in the new Pinecone version (^3.0.2). As per your suggestion, the PINECONE_ENV reference should be removed from the .env file and a spec property should be added in the generateEmbeddings.ts file. The new code would look like this:
await pinecone.createIndex({
// add this
spec: {
serverless: {
cloud: "aws",
region: "us-east-1",
},
}
});
await pinecone.createIndex({
// add this
spec: {
serverless: {
cloud: "aws",
region: "us-east-1",
},
}
});
This issue is similar to a previous one discussed in a Discord support thread (https://discord.com/channels/686873244791210014/1203689209894928404) where the Pinecone version in the Embedding template needed to be updated. I recommend creating a new issue on the Wasp Github repository (https://github.com/wasp-lang/wasp/issues) to address this update. This way, the Wasp team and community can work together to implement and test these changes. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @Alex Jukes, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?
Filip
Filip2mo ago
@Vinny (@Wasp) Tagging you to make sure you don't miss it. @Alex Jukes Thanks for the heads up! Any chance you'd be up for opening a PR?
Alex Jukes
Alex Jukes2mo ago
@Filip where can I find the code for the embeddings template? I've had a look but it wasn't imemdiately obvious, if you could point me in the right direction I'd be happy to
MEE6
MEE62mo ago
Wohooo @Alex Jukes, you just became a Waspeteer level 1!
miho
miho2mo ago
This is where we store the starters code: https://github.com/wasp-lang/starters/tree/dev/embeddings
GitHub
starters/embeddings at dev · wasp-lang/starters
Starting points for Wasp applications with batteries included - wasp-lang/starters
martinsos
martinsos2mo ago
That would be awesome @Alex Jukes !
Vinny (@Wasp)
Vinny (@Wasp)2mo ago
Yeah, that would be much appreciated. let me know if you have any Qs along the way 🙂
Alex Jukes
Alex Jukes4w ago
hey @martinsos @Vinny (@Wasp) i've got the changes on a branch locally but seem unable to push to the repo (getting permission denied errors with HTTPS and failures when using SSH). This could well be something my end, but wanted to check there's not a permission thing I'm missing
miho
miho4w ago
In order to contribute, you need to fork the repo 🙂 Did you do that?
Alex Jukes
Alex Jukes2w ago
I had not! Ok, fix is finally on a PR. Sorry it took so long!
Alex Jukes
Alex Jukes2w ago
cc/ @Vinny (@Wasp) @miho @martinsos
Vinny (@Wasp)
Vinny (@Wasp)2w ago
Hey I’ll take a look soon. We’ve busy this week with launch week stuff 🙂 Thanks so much for the PR
martinsos
martinsos2w ago
awesome!
Vinny (@Wasp)
Vinny (@Wasp)4d ago
approved and merged! thanks again 👍
Want results from more Discord servers?
Add your server