tinyhumansai/openhuman · error · anyhow::Error
people_get: {e}
Error message
people_get: {e} What it means
Error-surfacing wrapper in the people_get tool's execute: after parse_person_id and people_guard succeeded, the get_person driver call failed and the error is re-wrapped with the people_get prefix. Means the lookup itself failed — typically an unknown person_id or driver/transport error; it does not indicate missing arguments.
Source
Thrown at src/openhuman/memory/tools/people.rs:234
fn parameters_schema(&self) -> serde_json::Value {
json!({
"type": "object",
"properties": { "person_id": { "type": "string", "description": "Person id (UUID)." } },
"required": ["person_id"]
})
}
async fn execute(&self, args: serde_json::Value) -> anyhow::Result<ToolResult> {
log::debug!("[tool][people] get invoked");
let person_id = parse_person_id(&args)?;
let guard = people_guard().await?;
let person = guard
.as_people()
.expect("checked")
.get_person(&person_id)
.await
.map_err(|e| anyhow::anyhow!("people_get: {e}"))?;
Ok(ToolResult::success(serde_json::to_string(&json!({
"person": person,
}))?))
}
fn is_concurrency_safe(&self, _args: &serde_json::Value) -> bool {
true
}
}
/// Attach a handle alias to a person.
pub struct PeopleAddAliasTool;
#[async_trait]
impl Tool for PeopleAddAliasTool {
fn name(&self) -> &str {
"people_add_alias"
}View on GitHub (pinned to 7491200858)
Solutions
- Handle not-found persons gracefully in the caller
- Retry transient driver errors
- Check the person id came from a prior people_list/resolve
Defensive patterns
Strategy: retry
When it happens
Trigger: Thrown at src/openhuman/memory/tools/people.rs:234 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/401c6a289f9fd24e.
Report an issue: GitHub.