And we have an OSS sponsorship program: https://blog.cloudflare.com/cloudflare-new-oss-sponsorships-...
4,543 karma · joined July 22, 2010
twitter: rickyrobinett email: rrobinett@cloudflare.com
And we have an OSS sponsorship program: https://blog.cloudflare.com/cloudflare-new-oss-sponsorships-...
Our bot protection can help with that :) How can we make this easier? Any other product/feature requests in this space I can float to our product team?
He created an environment where (at our best) we could have fun doing work that had a real impact, and we could it with people we enjoyed doing the work with. He pushed us to be creative to authentically empower and inspire developers. Wanna build a video game that teaches developers how to code and use Twilio? Let's try it! Wanna build an AI application with Tony Hawk and have Tony Hawk debug the code live on stage? Sure!
And Jeff would always be spending time with developer tools and Twilio's products himself, to the point that he could live code at the drop of a hat to show off what we'd been working on. This meant his own understanding of developers and their problems never ceased to amaze me.
But more than all of that, he was a rare CEO that led with empathy, humility and care.
Thank you, jeffiel. We can't wait to see what you build next.
Edit:
Ok. I haven't been able to reproduce this issue (I know "it worked on my machine" is the worst answer. But I did do a fresh setup on two other machines to see if I can recreate so it worked on three of my machines?).
If you want to drop me an email (my email is in my profile), I'm happy to help find time to debug live and I'd personally love to find out what the issue is. And/or hook you up with a t-shirt :)
Digging in, this specific error looks like it is happening when LangChain is trying to strip out new lines (you can see the code in LangChain here: https://github.com/hwchase17/langchainjs/blob/main/langchain...). For some reason your documents or embeddings are undefined. But I've been unable to create a scenario where that happens.
I wondered if perhaps your OpenAI API Key wasn't set correctly and it was causing the Embeddings to fail, but I tried both deleting my key and setting to bogus key and the error was different.
Any chance you switched out the URL we were pulling from? That didn't cause the same error for me either, but thinking through what else it could be.
Sorry to not resolve, but please feel free to drop me an email. I'll keep trying to reproduce as well, and will jump back in this comment if I do (and find a fix).
I personally feel like with a lot of these emerging AI tools I still find myself still in the exploration phase. Trying to understand how they work and what they do, to then wrap my ahead around why I use them. Some of this post is a look into how I've been wrapping my head around the what and how of LangChain. Doing a follow-up digging deeper into the "why" and what benefits folks may see from this kind of setup is a really good nudge for me. Thanks!
If you have any specific questions, or want to chat with someone else using it, please don't be shy. My email and twitter handle are both in my profile. I truly love talking about all of this and hearing what other folks are working on.
Caleb Joseph is the original author: https://github.com/calebj0seph
In this case, while these environment variables appear to be sensitive, they are ephemeral keys, uniquely issued to the Function as part of running within Lambda. Their associated actions and permissions have been reviewed, approved and are required to run the Function. There is no risk of any Twilio customer’s Function being accessed or modified by disclosure of these keys.
That said, we much appreciate the community raising potential concerns. If y’all ever see anything that looks like a vulnerability, we’d love for you to submit it to our Bug Bounty program: https://bugcrowd.com/twilio
My mom had her leg amputated 8 years ago, and seeing her go through the process of getting a prosthesis I couldn't agree more. Due to wear and tear, she has to get a new prosthesis approximately every 2 years. We're in the US, and with insurance it ends up costing $10,000. I'm unbelievably excited to see new and innovative approaches to tackle this problem.
Traveling Nuker's site links to coverage on Yahoo Finance and SPN. A Google search points to numerous videos where the founders outline what they're working on.
It's not like these guys were trying to stay under the radar. Spending 10 minutes searching on Google would have made it obvious they aren't terrorist.
The fact that there are questions as to whether the FBI understands this distinction is terrifying.
From a developer point of view, we all have bugs. I remember the first time one of my bugs impacted customers and it was awful. If there's any community that should be understanding that things like this happen in the tech world, it should be us.
Disclaimer: I work at Ordr.in.
I really love that idea. Such a good point.