From 4d5c46a1641b7ffda3bfc91baa0f75aa5bda3ef1 Mon Sep 17 00:00:00 2001
From: "pre-commit-ci[bot]"
 <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Date: Mon, 21 Oct 2024 19:36:53 +0000
Subject: [PATCH] [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci
---
 virtualizarr/writers/icechunk.py | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/virtualizarr/writers/icechunk.py b/virtualizarr/writers/icechunk.py
index e23553c9..96adfaf9 100644
--- a/virtualizarr/writers/icechunk.py
+++ b/virtualizarr/writers/icechunk.py
@@ -147,13 +147,14 @@ def write_manifest_virtual_refs(
     # loop over every reference in the ChunkManifest for that array
     # TODO inefficient: this should be replaced with something that sets all (new) references for the array at once
     # but Icechunk need to expose a suitable API first
-    it = np.nditer( 
-        [manifest._paths, manifest._offsets, manifest._lengths], # type: ignore[arg-type]
+    it = np.nditer(
+        [manifest._paths, manifest._offsets, manifest._lengths],  # type: ignore[arg-type]
         flags=[
             "refs_ok",
             "multi_index",
             "c_index",  # TODO is "c_index" correct? what's the convention for zarr chunk keys?
-        ], op_flags=[["readonly"]] * 3, # type: ignore
+        ],
+        op_flags=[["readonly"]] * 3,  # type: ignore
     )
     for path, offset, length in it:
         index = it.multi_index