Repo search is still pretty funky :sadblob:
# proj-agent-canvasw
wooden-umbrella-84098
09/22/2025, 9:14 AMRepo search is still pretty funky sadblob
wooden-umbrella-84098
09/22/2025, 11:04 AManother data point
wooden-umbrella-84098
09/22/2025, 11:04 AM@millions-afternoon-47582 @freezing-spoon-14104 are we tracking this issue?
m
millions-afternoon-47582
09/22/2025, 11:29 AMI've created this Github issue (https://github.com/All-Hands-AI/OpenHands/issues/11057). Thank you! thankyou
đź‘Ť 1
millions-afternoon-47582
09/22/2025, 1:06 PMIt appears to be a back-end issue. When entering the keyword “runtime”, the API does not return any results.
However, when using the search keyword in the format “All-Hands-AI/runtime”, the API successfully returns the expected results.
w
wooden-umbrella-84098
09/22/2025, 1:09 PMnod not shocked the issue is on the backend. But we should figure out how to get GitHub to return better results
thankyou 1
c
calm-artist-7206
09/22/2025, 1:10 PMI saw something weird like this, but it was roughly under the form:
• I started to type "play..."
• two personal repos appeared, enyst/ai-playground and enyst/playground (as expected)
• I tried to select the second => it disappeared
• typed "playg"
• they both showed up again
• tried to select the second => nope
• writing it fully or something (being quick?) did work
thankyou 1
f
freezing-spoon-14104
09/24/2025, 11:57 AMWhat is most likely happening here is that we filter the current fetched results first (instant when typing) vs debounced fetch right after you finish typing. It's a tricky problem that has to do with the limitations of the GH API if I remember correctly. We already have an open issue here: https://github.com/All-Hands-AI/OpenHands/issues/10785