From c7336735050be3722d71a178dcbd180641043b72 Mon Sep 17 00:00:00 2001 From: soryu Date: Sat, 31 Jan 2026 22:51:47 +0000 Subject: [WIP] Heartbeat checkpoint - 2026-01-31 22:51:47 UTC --- makima/src/server/handlers/mesh_red_team.rs | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) (limited to 'makima/src/server') diff --git a/makima/src/server/handlers/mesh_red_team.rs b/makima/src/server/handlers/mesh_red_team.rs index 1d8e0b0..2822baa 100644 --- a/makima/src/server/handlers/mesh_red_team.rs +++ b/makima/src/server/handlers/mesh_red_team.rs @@ -793,11 +793,21 @@ pub async fn get_task_diff( /// /// This helper function can be used by the red team to filter task output /// notifications to only include outputs from work tasks in its contract. +/// +/// # Arguments +/// * `notification` - The task output notification to filter +/// * `_contract_id` - The contract ID to filter for (used in database lookup) +/// * `owner_id` - The owner ID for data isolation +/// * `_pool` - Database pool for looking up task contract association +/// +/// # Note +/// This is a simplified check. Full contract association verification +/// requires a database lookup which should be done at the subscription level. pub fn filter_task_output_for_contract( notification: &TaskOutputNotification, - contract_id: Uuid, + _contract_id: Uuid, owner_id: Uuid, - pool: &sqlx::PgPool, + _pool: &sqlx::PgPool, ) -> bool { // Note: This is a placeholder for the actual filtering logic. // In practice, the filtering would be done at the subscription level -- cgit v1.2.3