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
[BUG] LanguageModelQueryRouter.parse(String choices) throws NumberFormatException when no results are found #588
Comments
|
@stephanj thank you so much for reporting! Going to fix this ASAP |
|
@stephanj in this case, when the model cannot decide, I guess there should be a configurable fallback behavior:
Any other ideas? |
|
Maybe the different listed strategies should be configurable for the developer? |
|
@stephanj yes, of couse! I was just wondering which one should be a default one (without any specific configuration) |
|
Probably "Route all" because I would prefer an answer instead of nothing. |
|
Hmm. By "not route" I mean just not retrieve anything, pass this query directly to the LLM without any additional context. |
Please provide as much details as possible, this will help us to deliver a fix as soon as possible.
Thank you!
Describe the bug
Using LanguageModelQueryRouter, when it gets a question which it can't answer it's trying to parse a String text value to Int
Either filter strings that are only digits, or some other checks "higher up"
OR
Setup used:
Log and Stack trace
To Reproduce
Probably ask a question where the AI Service can't find an answer
Expected behavior
Something like "Sorry, I can't give you an answer to that question"
Please complete the following information:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: