Devin Bost
Devin Bost
This would be a huge value add. I can look into it further.
We would be the only platform on the market to my knowledge with a no-code option for LangChain, and we could co-market it in all the LangChain forums, etc.
The interface for the document loader is pretty simple: `load()` `lazy_load()` and in some cases: `load_and_split(text_splitter)` We would just need to account for the constructors, which seem to be more...
The other things we'd really want to find a way to hook into (from the LangChain project) would be `chains`, `embeddings`, `prompts`, and`llms`
It looks like we have support for this capability since we have a Document Loader example here: https://github.com/LangStream/langstream/issues/429 However, it looks like with the current design, we'd need to add...
I believe that's exactly what I'm doing unless I'm missing something.
Hi Italo, Thank you very much for the help! I'm actually wondering if there's a solution that doesn't require exporting the keys' values. The reason I don't want to export...
When I swapped out the OpenAI component with the OLlama component, I got the same behavior. It's not specific to OpenAI. Logs are below: ``` wikichat-langflow-1 | DEBUG 2024-10-02 16:39:51...
The way to reproduce this (in terms of app configuration) is to create a routing issue where the front-end cannot access the langflow streaming endpoint directly. That being said, it's...