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

[Bug]: Long delay before new messages unpause the agent #4678

Open
1 task done
rbren opened this issue Nov 1, 2024 · 1 comment
Open
1 task done

[Bug]: Long delay before new messages unpause the agent #4678

rbren opened this issue Nov 1, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@rbren
Copy link
Collaborator

rbren commented Nov 1, 2024

Is there an existing issue for the same bug?

  • I have checked the existing issues.

Describe the bug and reproduction steps

This is a flaky issue--no consistent way to repro that I can tell. I will try and spot a log pattern at least

Sometimes, when the agent is "waiting for user input", when I send a new message, nothing happens. If I refresh the page, the message is there (meaning it made it to the backend, so websocket is connected) and then the agent starts running.

EDIT: pretty sure it's actually a delay! the state changes only when a new event comes back from the agent. probably some async locking going on

OpenHands Installation

Docker command in README

OpenHands Version

main

Operating System

None

Logs, Errors, Screenshots, and Additional Context

No response

@rbren rbren added the bug Something isn't working label Nov 1, 2024
@rbren rbren changed the title [Bug]: New messages don't always unpause the agent [Bug]: Long delay before new messages unpause the agent Nov 1, 2024
@enyst
Copy link
Collaborator

enyst commented Nov 1, 2024

This sounds kind of like something weird I noticed on your branch. So this was on main. 🤔

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

No branches or pull requests

2 participants