tinyhumansai/openhuman · error · anyhow::Error
Missing 'path' parameter
Error message
Missing 'path' parameter
What it means
Required-parameter guard in the image_info tool's execute: the `path` argument (image file, absolute or workspace-relative) is absent or not a string. The schema requires path with optional include_base64; fires before the file is opened, so no file access occurred.
Source
Thrown at src/openhuman/tools/impl/browser/image_info.rs:151
"properties": {
"path": {
"type": "string",
"description": "Path to the image file (absolute or relative to workspace)"
},
"include_base64": {
"type": "boolean",
"description": "Include base64-encoded image data in output (default: false)"
}
},
"required": ["path"]
})
}
async fn execute(&self, args: serde_json::Value) -> anyhow::Result<ToolResult> {
let path_str = args
.get("path")
.and_then(|v| v.as_str())
.ok_or_else(|| anyhow::anyhow!("Missing 'path' parameter"))?;
let include_base64 = args
.get("include_base64")
.and_then(serde_json::Value::as_bool)
.unwrap_or(false);
// Security check: validate path string, resolve symlinks, confirm workspace containment.
let resolved = match self.security.validate_path(path_str).await {
Ok(p) => p,
Err(msg) => return Ok(ToolResult::error(msg)),
};
let metadata = tokio::fs::metadata(&resolved)
.await
.map_err(|e| anyhow::anyhow!("Failed to read file metadata: {e}"))?;
let file_size = metadata.len();
View on GitHub (pinned to 7491200858)
Solutions
- Include `path` as a string pointing at the image file
- Use an absolute path or one relative to the workspace
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at src/openhuman/tools/impl/browser/image_info.rs:151 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/af4fd34ac68eb241.
Report an issue: GitHub.