https://docs.all-hands.dev/ logo
Join Slack
Powered by
First user message for resolver: it received no co...
# proj-integrations
c
First user message for resolver: it received no context, no comment, from https://github.com/All-Hands-AI/OpenHands/pull/10432/files#r2280639248
c
cc @quick-window-91705 i believe this should be caused by one of our ongoing bug/incident?
c
It has a funny part! It happened twice, and Sonnet immediately responded there’s nothing to summarize. GPT-5 decided to throw several shell commands to make double-sure if anything happened 🫠
I just see where it did get the comment, but it didn't get context of the comment, line number, file. So the LLM somehow came to some hallucinated conclusion what it could be about 😂 https://github.com/All-Hands-AI/OpenHands/pull/10432#discussion_r2281100499
q
Yeah missing context is definitely an issue in the cloud resolver; we gave the agent the freedom to collect the context as needed We're fixing this soon by passing exact context
thanks on a stick 1
c
Ah, I see. TBH that makes a lot of sense to me, just maybe less for per-line-file invocations
q
Def see it misbehaving on review threads as well Some users will leave a msg "`at-openhands` address the feedback" and OH won't pull the previous comments in the thread
Although figuring out what has already been addressed would be tricky, but I think that's true regardless of how we pull in the context
Just less api calls if we give it up front imo
c
nod What is the prompt on that?
q
https://github.com/All-Hands-AI/OpenHands/tree/main/openhands/integrations/templates/resolver/github - all the templates that have the suffix 
conversation_instrutcions.j2
c
I just went through the entire RecallObs included in the conversation, and I don't see this instruction at all. Is that normal? It's like it wasn't included
q
Oh that doesn’t seem normal at all thonk I’ll investigate tmrw
thanks on a stick 1
❤️ 1
Open in Slack
PreviousNext
Powered by