From a5365e6228f791910e4c722262ed430df6a03a6a Mon Sep 17 00:00:00 2001
From: Adam Gutglick <adam@spiraldb.com>
Date: Wed, 17 Jun 2026 11:56:56 +0100
Subject: [PATCH] Ignore the other pyo3 RUSTSEC advisory

Signed-off-by: Adam Gutglick <adam@spiraldb.com>
---
 deny.toml | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/deny.toml b/deny.toml
index a2a6935ba5b..1e2443c1fd8 100644
--- a/deny.toml
+++ b/deny.toml
@@ -21,7 +21,10 @@ ignore = [
     # 0.29.0. We cannot bump until pyo3-bytes, pyo3-log, and pyo3-object_store support 0.29 (all
     # pin pyo3 to <0.29, and pyo3-ffi `links = "python"` forbids two pyo3 versions in the graph).
     # Not exploitable here: `vortex-python` never calls `nth`/`nth_back` on these iterators.
-    "RUSTSEC-2026-0176"
+    "RUSTSEC-2026-0176",
+    # Another issue that will be fixed once we can bump pyo3 to 0.29.
+    # PyCFunction::new_closure is missing a `Sync` bound.
+    "RUSTSEC-2026-0177"
 ]
 
 [licenses]