Skip to content

fix: increase VERIFY_TIMEOUT_MS from 10s to 120s for local LLMs#29102

Closed
NaturalTensor wants to merge 1 commit intoopenclaw:mainfrom
NaturalTensor:fix/verify-timeout-local-llms
Closed

fix: increase VERIFY_TIMEOUT_MS from 10s to 120s for local LLMs#29102
NaturalTensor wants to merge 1 commit intoopenclaw:mainfrom
NaturalTensor:fix/verify-timeout-local-llms

Conversation

@NaturalTensor
Copy link

Summary

Increases the verification timeout during custom model onboarding from 10 seconds to 120 seconds.

Problem

Users running local LLMs (e.g., Qwen3 14B on a laptop GPU via llama.cpp) frequently exceed the 10-second verification timeout, causing onboarding to fail unnecessarily. The model works fine — it just needs more time to generate its first response.

Fix

Bump VERIFY_TIMEOUT_MS from 10_000 (10s) to 120_000 (120s). This is generous enough for slow local models while still providing a reasonable upper bound.

Closes #28972

Local LLMs (e.g. Qwen3 14B on laptop GPU via llama.cpp) can easily
exceed 10s for the verification response. Bump to 120s so onboarding
does not fail for users with slower local models.

Closes openclaw#28972
@openclaw-barnacle openclaw-barnacle bot added commands Command implementations size: XS labels Feb 27, 2026
@greptile-apps
Copy link
Contributor

greptile-apps bot commented Feb 27, 2026

Greptile Summary

Increased verification timeout from 10s to 120s to accommodate slower local LLMs during custom model onboarding.

  • The timeout change is appropriate for the use case (local LLMs like Qwen3 14B on consumer hardware)
  • Uses numeric separator (120_000) for better readability
  • Issue: Test file at src/commands/onboard-custom.test.ts:223 still advances timers by 10s and needs updating to 120s to properly test the timeout behavior

Confidence Score: 3/5

  • This PR is mostly safe but has a test that needs updating to match the new timeout
  • The timeout increase itself is reasonable and well-justified for local LLMs, but the test file wasn't updated to reflect the new timeout value, which means the timeout test will no longer work correctly
  • Pay attention to src/commands/onboard-custom.test.ts - the test needs to be updated to use the new 120s timeout

Last reviewed commit: dc26bd9

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

1 file reviewed, 1 comment

Edit Code Review Agent Settings | Greptile

@greptile-apps
Copy link
Contributor

greptile-apps bot commented Feb 27, 2026

Additional Comments (1)

src/commands/onboard-custom.test.ts
Test advances timer by 10s but timeout is now 120s

    await vi.advanceTimersByTimeAsync(120_000);
Prompt To Fix With AI
This is a comment left during a code review.
Path: src/commands/onboard-custom.test.ts
Line: 223

Comment:
Test advances timer by 10s but timeout is now 120s

```suggestion
    await vi.advanceTimersByTimeAsync(120_000);
```

How can I resolve this? If you propose a fix, please make it concise.

@philipp-spiess
Copy link
Member

Thank you for the contribution and for pushing this forward.

We consolidated this fix path in #27380 so we can land one complete solution for onboarding custom-provider verification reliability with full test coverage.

Closing this as superseded, with appreciation.

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

Labels

commands Command implementations size: XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: VERIFY_TIMEOUT_MS in onboard-custom.ts is too short for local LLMs.

2 participants