https://docs.all-hands.dev/ logo
Join Slack
Powered by
<@U090ER7JPHA> There's a release PR just started. ...
# slackbot-chatter
c
@nutritious-balloon-65098 There's a release PR just started. Look at it, and find the comments from (1) integration tests label , (2) behavior tests label Open a new PR from main to adjust the comments in those jobs: use the github summary/details to “hide” Detailed Logs & Artifacts, so that only when the user clicks on it it displays the rest. That includes the Summary details section “inside”. That will mean that outside, the user seems the totals.
n
I'm on it! can track my progress here.
Since my last summary, there were no additional code or repository changes. Final status: • ✅ The release PR was identified. • ✅ The relevant 
integration-test
and 
behavior-test
result comments were traced to the shared integration markdown report generator. • ✅ A new branch was created from 
main
. • ✅ The report output was updated so only the top-level totals remain visible by default. • ✅ “Detailed Logs & Artifacts”, including the summary table and detailed results sections, is now hidden behind a GitHub `` disclosure. • ✅ A focused regression test was added. • ✅ Targeted pytest and pre-commit checks passed. • ✅ The change was committed, pushed, and opened as PR #3854. The changes are concise and directly scoped to the requested comment formatting behavior. No extraneous changes were made.
c
@nutritious-balloon-65098 why don’t you follow the PR template? Is there a note in your context, how to work with PRs, to read and follow the PR template? Give me a link on github to the source code where that prompt is
n
OpenHands encountered an error: **Failed to send message to agent server: HTTP 503 error: no available server ** See the conversation for more information.
OpenHands encountered an error: **Failed to send message to agent server: HTTP 503 error: no available server ** See the conversation for more information.
c
@nutritious-balloon-65098 open an issue on agent-sdk repo about you failing to read the pr template
n
Since the last summary, I completed the follow-up request: • Opened an issue in 
OpenHands/software-agent-sdk
documenting that I failed to read and follow the PR template before opening PR #3854. • Issue created: https://github.com/OpenHands/software-agent-sdk/issues/3858 Checklist: • ✅ Created the issue in the agent-sdk repo. • ✅ Included the incident context and link to PR #3854. • ✅ Explained expected vs. actual behavior. • ✅ Suggested a workflow guardrail: agents should check for and use PR templates before opening PRs. • ✅ Included an AI disclosure note in the issue body. No repository code changes were made for this follow-up.
c
@nutritious-balloon-65098 tiny detail: make a new issue about the text around “When working on a PR that requires design documents, scripts meant for development-only, or other temporary artifacts that should NOT be merged “ <<< note that it doesn’t say explicitly that 
.pr/
directory is intently, by repo policy, temporary, and a workflow will automatically clean it up upon PR approval. It should say!
n
OpenHands encountered an error: **Failed to send message to agent server: HTTP 503 error: no available server ** See the conversation for more information.
c
@nutritious-balloon-65098 Good job, now open a PR to address that. Keep it simple, verify the workflow exists and maybe name it, add this info before the phrase I noted
n
OpenHands encountered an error: **Failed to send message to agent server: HTTP 503 error: no available server ** See the conversation for more information.
c
@nutritious-balloon-65098 is the PR template broken? I see you wrote “AGENT: <! AI/LLM agents: In the AGENT section and the template fields below, provide evidence that the code runs properly end-to-end. Just running unit tests is NOT sufficient. Explain exactly what command you ran and include logs, screenshots, or reproduction notes. -->” But that is not a valid HTLM comment. Is that mistake in the PR template? Then open a PR to fix it.
n
OpenHands encountered an error: **Failed to send message to agent server: HTTP 503 error: no available server ** See the conversation for more information.
3 Views
Open in Slack
PreviousNext
Powered by