tinyhumansai/openhuman · error
'{key}'={value} exceeds configured limit {limit}
Error message
'{key}'={value} exceeds configured limit {limit} What it means
validate_coordinate rejects a coordinate exceeding the configured per-key maximum. This bounds automation input to the plausible viewport/config range, catching out-of-range model output before it reaches the backend.
Source
Thrown at src/openhuman/tools/impl/browser/browser.rs:562
)
.await
.context("Playwright browser action failed")?;
Ok(ToolResult::success(
serde_json::to_string_pretty(&output).unwrap_or_default(),
))
}
fn validate_coordinate(&self, key: &str, value: i64, max: Option<i64>) -> anyhow::Result<()> {
if value < 0 {
anyhow::bail!("'{key}' must be >= 0")
}
if let Some(limit) = max {
if limit < 0 {
anyhow::bail!("Configured coordinate limit for '{key}' must be >= 0")
}
if value > limit {
anyhow::bail!("'{key}'={value} exceeds configured limit {limit}")
}
}
Ok(())
}
fn read_required_i64(
&self,
params: &serde_json::Map<String, Value>,
key: &str,
) -> anyhow::Result<i64> {
params
.get(key)
.and_then(Value::as_i64)
.ok_or_else(|| anyhow::anyhow!("Missing or invalid '{key}' parameter"))
}
fn validate_computer_use_action(
&self,View on GitHub (pinned to 7491200858)
Solutions
- Use a coordinate within the configured limit for that key.
- Raise the configured limit if larger coordinates are legitimately needed.
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at src/openhuman/tools/impl/browser/browser.rs:562 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of tinyhumansai/openhuman@7491200858 (2026-08-17).
Data as JSON: /api/errors/82abe40f0f688de7.
Report an issue: GitHub.