Zoltan Fedor

Others do see reasonable results with Llama 3 8B function calling: https://www.reddit.com/r/LocalLLaMA/comments/1c7jtwh/function_calling_template_for_llama_3/

I did try function calling by making a function-calling ReAct template for Llama 3 70B (see https://www.reddit.com/r/LocalLLaMA/comments/1c7jtwh/comment/l1dksmx/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button) It seems to be working reasonably well. I have tried it with a...

I think it is important to note, that this change (lack of support for running multiple applications in the v2.x API) also permanently and irreparably breaks integrations like the Haystack-Ray...

This has been added recently in `v0.0.126`, see https://github.com/hwchase17/langchain/pull/2122

This has already been implemented and merged in https://github.com/hwchase17/langchain/pull/2122 See example at https://github.com/hwchase17/langchain/blob/master/docs/modules/memory/examples/agent_with_memory_in_db.ipynb and https://github.com/hwchase17/langchain/blob/master/docs/modules/memory/examples/redis_chat_message_history.ipynb

Redis is not the only option, DynamoDB is also implemented. There is a general class for ANY type of storage - so you can easily implement whatever you need.

@hwchase17, thanks, yes, this is definitely not a small change! :-) I generally would agree regarding `MessageStore` and `ChatMessageHistory`, but the idea for the `MessageStore` was that we would have...

@3coins, I don't really see why would we have `ChatMessageHistoryBase` and `ChatMessageHistory`? Are we expecting multiple `ChatMessageHistory` implementations using the same `ChatMessageHistoryBase`???

@hwchase17, @3coins, I have refactored it to collapse these new classes under the `ChatMessageHistoryBase` class. Now using it is pretty simple: ``` from langchain.chains.conversation.memory import ConversationBufferMemory, from langchain.memory.chat_message_histories import RedisChatMessageHistory...

@KBB99, As far as I am concerned, this PR is ready. It is just waiting for review. Matter of fact I am already using this PR in my codebase.