You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, once the retries fail, we reach to raise statement. Such behaviour results in clearing the memory and start as if its the first time!
Cant we modify the logic to handle such behavior and return a static messages indicating inability to generate a code? with this, we will keep the history running (better than just a raise)
The text was updated successfully, but these errors were encountered:
@faresmalik I would not say this is bug but rather an idea of enhancement. Labeling it as such. However, not sure it would be better not to raise an error when retries fails. Local logs keep all history and memory also.
P.S.Ensure to use the latest version, 3.0 b14, as error handling and code generation was improved significantly
System Info
pandasai 12b
🐛 Describe the bug
Currently, once the retries fail, we reach to raise statement. Such behaviour results in clearing the memory and start as if its the first time!
Cant we modify the logic to handle such behavior and return a static messages indicating inability to generate a code? with this, we will keep the history running (better than just a raise)
The text was updated successfully, but these errors were encountered: