-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add an unique id for every entry in history #1073
Comments
Using date-time might also help in time-performance analysis |
Yes, I agree |
This is solid idea. @Anindyadeep wanna add a PR to the new dspy.LM client? |
sure, would be happy to do it |
Hi @okhat I have one question though should it be added on the Edit: From what I see, I do not see any such scope to add those in modules section. Although we can discuss if we need to add in modules here. |
Hey, also I added an another issue, while I was solving this one, let me know your thoughts. |
We can infer that, history in dspy acts as a trace, where we can see previous LLM response along with all the additional arguments. However, with more and more llm responses, it becomes hard to follow along the traces, since this is a list. And this becomes a common problem for all the supported LLMs in
dsp.modules
So my proposal is to have some id parameter with the following example standard:
or we can also use uuid but then add, date-time parameter seperately. The reason I put emphasis on datetime, because it makes easier to do some filter operations.
Let me know what everyone thinks on this.
The text was updated successfully, but these errors were encountered: