-
-
Notifications
You must be signed in to change notification settings - Fork 14
It returns message "maximum recursion depth exceeded" #19
Comments
Thank you for reporting. Please give me tracebacked error message. |
looks like it returns attachment instead of text now, response.bin, dunno have not dig much, so sorry if that makes no sense |
Would it still work if I leave the Gemini object as is and only rerun the generate content method? I'll check again tomorrow. I was aware of the bot server change, but since the old bot server was still running, I didn't make the switch, though I'm a bit scared, I'll check it again. Before posting it on the readme, I'll first post it on this issue page. Since it's difficult to code and check, I'll get back to you within 12 hours! Thank you. |
|
Thank you for reporting. I will check this issue ASAP. |
I just update to Ver 2.2.0 and it still returns "maximum recursion depth exceeded" |
phamxtien However, recognizing that errors could technically occur in that syntax, I have clarified and corrected it again. I've made modifications to change the recursive calls in property definitions in GeminiModelOutput. Could you please reinstall the version from GitHub and check again?
or try to using v2.2.1 |
Thank you for your guide |
Are you sure to use Or try to use It seems the issue is related to a property, which might confuse other users. I'm concerned but will fix it as soon as possible. Please keep following the issue for updates; I'll correct it soon and adjust the settings to address the error. In reality, there's still a lot to refactor and implement, but due to a busy schedule, I haven't been able to devote much time to it. Thank you. |
I use print(response.response_dict) |
I release |
it works, and response format is also changed
|
Thanks, it runs smooth |
Thank you for reporting! Have a nice day. I will close this issue as complet. |
Describe the bug
Gemini returns message "maximum recursion depth exceeded"
Version
OS: Ubuntu 23.10
Python: 3.11
Gemini API: 2.0.0
Using proxy: None
Legion:
Code
Error
The text was updated successfully, but these errors were encountered: