Skip to content
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

Exiting a thread without confirming to a tool call prompt, results in the thread erroring out "authorize called multiple times for same ID" for the same message being made in any thread. #148

Closed
sangee2004 opened this issue Aug 13, 2024 · 3 comments
Assignees
Labels
bug Something isn't working threads-gone-bad

Comments

@sangee2004
Copy link

sangee2004 commented Aug 13, 2024

Version 0.10.0-rc2
Steps to reproduce the problem:

  1. Chat with Tildy (Acorn Desktop Assistant)
  2. Ask any question that involves a tool call like - "who won 2024 superbowl?"
  3. When prompted to allow all calls from the github.com/gptscript-ai/answers-from-the-internet repo , do not take any action.
  4. Leave the thread (visit any other thread)
  5. Come back to the thread in step 2.
  6. Notice that the chat message status shows "in progerss" . But we are able to type a message click on it twice to send the message.
Screenshot 2024-08-13 at 4 49 29 PM
  1. Ask the same question that involves answers-from-the-internet tool call from step 2 - "who won 2024 superbowl?"
  2. User is presented with the following error message:
Screenshot 2024-08-13 at 4 43 49 PM
  1. Start a new chat with Tildy (Acorn Desktop Assistant) and ask the same question - "who won 2024 superbowl?"
  2. User is presented with the following error message:
Screenshot 2024-08-13 at 4 43 49 PM

Once user uses "Restart script" option he can get out of this state.

@sangee2004 sangee2004 added the bug Something isn't working label Aug 13, 2024
@sangee2004 sangee2004 changed the title Existing a thread without confirming to a tool call prompt, results in the thread erroring out "authorize called multiple times for same ID" on re-entry. Existing a thread without confirming to a tool call prompt, results in the thread erroring out "authorize called multiple times for same ID" for the same message being made in any thread. Aug 13, 2024
@sangee2004 sangee2004 changed the title Existing a thread without confirming to a tool call prompt, results in the thread erroring out "authorize called multiple times for same ID" for the same message being made in any thread. Exiting a thread without confirming to a tool call prompt, results in the thread erroring out "authorize called multiple times for same ID" for the same message being made in any thread. Aug 14, 2024
@StrongMonkey StrongMonkey self-assigned this Aug 21, 2024
@cjellick
Copy link
Contributor

You can also see this behavior on the Edit Assistant page.

Here's a avideo of it. You can see it at 0:44:49 of this video or by looking in the transcript for

Okay, refresh. Dang it. This is a bug. Um, refreshing when it's kind of waiting for a prompt puts it in a bad state.

https://www.loom.com/share/4c46566fc8c5437b93f125c6a87989ae

Steps to repro (roughly, watch the video for better context):

  1. In assistant editor, get the chat pane to a state where its prompting you to Allow something
  2. make a change to the assistant, like just update the prompt (not sure if this step is necessary)
  3. Click the Refresh Chat

The chat pane gets an error that says "authorize called multiple times"

@thedadams
Copy link
Contributor

PR: #407

@sangee2004
Copy link
Author

Tested with build - 9d46166

"authorize called multiple times for same ID" error is not seen when testing both the scenarios tracked in this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working threads-gone-bad
Projects
None yet
Development

No branches or pull requests

4 participants