Tom Dörr
Yes I think it should be clearer now
This issue should be solved by https://github.com/stanfordnlp/dspy/pull/1043
Maybe there should be a new DSPy package release using the latest code in main, the PR that fixes this is already merged
@brando90 How do you have 2.4.17, isn't the newest version 2.4.16? Do you get the exact same error message? If so, could you post relevant code?
Could you post the error message you are getting? Do you use any less commonly used DSPy features?
Don't see how that's related to the 400 Error. I had the same issue you seem to have: https://github.com/stanfordnlp/dspy/issues/1041 This issue also seems to be relevant: https://github.com/stanfordnlp/dspy/issues/1242 Don't have a...
How about using LabeledFewShot or similar teleprompter/optimizer? https://dspy-docs.vercel.app/docs/building-blocks/optimizers#what-dspy-optimizers-are-currently-available That way the LLM has examples to show it how it is supposed to output the float.
Did you set a token limit when initializing your LM? COPRO might have just run out of tokens when generating the new instruction which resulted in the cutoff. Is the...
Is it really an issue? Software development is in English and it's not obvious to me that having instructions in English and processed text in another language is meaningfully harmful...
Ah okay. Would it make sense to throw that as the error message? I spent quite a bit of time trying to solve this myself