This message was deleted.
# openhands-cloud
d
This message was deleted.
w
I think it's actually just taking a long time to react to your message. It takes O(conversation length) to react
👍 1
@calm-artist-7206 fixed this I think
but it's not out yet
l
Oh, great that it’s fixed. That was confusing
c
Yes, the long wait is fixed. But there might be another thing here, I do think sometimes it just stops receiving the user message, but there is no error, and if I send a second message, in the UI it overwrites the first - and never reacts to it, until refresh.
w
I've seen that too, but not for a while now--I assumed it was fixed (maybe by accident)
c
I do think sometimes it just stops receiving the user message, but there is no error, and if I send a second message, in the UI it overwrites the first - and never reacts to it, until refresh.
yeah i think what i saw in openhands-cloud today is exactly this
yeah i think it may be related to: the FE is not displaying anything when socket.io disconnected. A easy way to repro: start a OH session locally, then kill the backend server -- the UI still stays unchanged. I imagine we'd add some sort of message like "backend disconnected - please refresh // will automatically refresh in 5 seconds"?
w
huh I was just testing exactly that flow and it worked fine for me
maybe I broke something?
I just changed it a couple days ago
l
I encountered this issue just now, if I post messages they show up once in the UI but nothing happens, and then they get replaced. It was with a session that was open for a long time.