Closed Jamminroot closed 1 year ago
Ok, I think I found the problem.
ChatGPT uses a message history similar to the blockchain (dont you dare talk about crypto) and when you switch to a different conversation, you also need to change the parent ID to match the last message ID in the chain
Imma try solving it without creating anymore lag
On a second thought - addressing that might not be a good call; Rather a requirement when using the library API. Maybe it's better to hint that parent_id should be a "child" of certain "conv_id", and they both should be valid values?
Describe the bug Trying to continue previous conversation returns 429 upon request:
error: {"detail":"Something went wrong, please try reloading the conversation."}! Refreshing session...
To Reproduce Steps to reproduce the behavior:
ask()
with specific conv_id(A)ask()
again (in my case conv_id was None), say it is conv_id(B)ask()
again with conv_id(A)Expected behavior Ability to continue old conversation
Output Sorry for not providing logs as per instruction (couldn't really figure the
--debug
flag, sry); Error is throwin inChatGPT.py:121
Environment (please complete the following information):
Please update your packages before reporting!
pip3 install --upgrade revChatGPT
python -V
pip3 show revChatGPT
Additional context As an extra - If I try to continue conv_id(A) right after a restart, it works just fine