Thanks to visit codestin.com
Credit goes to github.com

Skip to content

fix: toolcall error count#1562

Merged
tusharmath merged 15 commits into
mainfrom
tool-call-failure-count
Sep 16, 2025
Merged

fix: toolcall error count#1562
tusharmath merged 15 commits into
mainfrom
tool-call-failure-count

Conversation

@tusharmath

Copy link
Copy Markdown
Collaborator
  • chore: add ErrorCounter
  • chore: add more tests

@tusharmath tusharmath changed the title tool call failure count fix: toolcall error count Sep 16, 2025
@github-actions github-actions Bot added the type: fix Iterations on existing features or infrastructure. label Sep 16, 2025
Comment thread crates/forge_domain/src/tool_call.rs Outdated
Comment thread crates/forge_domain/src/tool_call.rs
Comment thread crates/forge_app/src/orch.rs Outdated
@tusharmath tusharmath enabled auto-merge (squash) September 16, 2025 11:47
Comment thread crates/forge_domain/src/tool_call.rs
@openhands-ai

openhands-ai Bot commented Sep 16, 2025

Copy link
Copy Markdown

Looks like there are a few issues preventing this PR from being merged!

  • GitHub Actions are failing:
    • ci

If you'd like me to help, just leave a comment, like

@OpenHands please fix the failing actions on PR #1562 at branch `tool-call-failure-count`

Feel free to include any additional details that might help me get this PR into a better state.

You can manage your notification settings

@tusharmath tusharmath merged commit d845afc into main Sep 16, 2025
9 checks passed
@tusharmath tusharmath deleted the tool-call-failure-count branch September 16, 2025 17:59
Comment on lines +402 to +404
.adjust(&[read], &[])
.adjust(&[read], &[])
.adjust(&[read], &[]); // Exactly at limit

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Test logic inconsistency with implementation. The test comment says 'Exactly at limit' but calls adjust 4 times for a limit of 3, expecting the tool to be maxed out. However, due to the bug in line 250 using > limit instead of >= limit, this test is actually testing the wrong behavior and masking the boundary condition bug.

Spotted by Diamond

Fix in Graphite


Is this helpful? React 👍 or 👎 to let us know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: fix Iterations on existing features or infrastructure.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants