tinyhumansai/openhuman · error · anyhow::Error
people_score: {e}
Error message
people_score: {e} What it means
The driver's score call for a person failed after person_id parsing — closeness score components could not be computed. The {e} chain carries the driver's reason; the tool itself only parses and delegates.
Source
Thrown at src/openhuman/memory/tools/people.rs:194
"Return the closeness score and its components (recency, frequency, \
reciprocity, depth) plus interaction count for one `person_id`."
}
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] score invoked");
let person_id = parse_person_id(&args)?;
let guard = people_guard().await?;
let outcome = rpc::handle_score(guard.as_people().expect("checked"), &person_id)
.await
.map_err(|e| anyhow::anyhow!("people_score: {e}"))?;
Ok(ToolResult::success(serde_json::to_string(&outcome.value)?))
}
fn is_concurrency_safe(&self, _args: &serde_json::Value) -> bool {
true
}
}
/// Read a full person record.
pub struct PeopleGetTool;
#[async_trait]
impl Tool for PeopleGetTool {
fn name(&self) -> &str {
"people_get"
}
fn description(&self) -> &str {View on GitHub (pinned to 7491200858)
Solutions
- Verify the person_id exists (people_get)
- Retry transient driver failures
- Inspect the chained error for the scoring fault
Defensive patterns
Strategy: retry
When it happens
Trigger: Thrown at src/openhuman/memory/tools/people.rs:194 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/2f589b6615f889fb.
Report an issue: GitHub.