Upgrade sled to 0.34.7

This fixes a bug where the frontend did not receive file list updates.

server/Cargo.toml

@@ -22,7 +22,7 @@ log = { version = "0.4.14", features = ["kv_unstable", "kv_unstable_std"] }
 serde_json = "1.0.79"
 ron = "0.7.0"
 thiserror = "1.0.30"
-sled = "0.34.6"
+sled = "0.34.7"
 sleigh = { path = "../sleigh" }
 itertools = "0.10.3"
 structopt = "0.3.26"

server/src/main.rs

@@ -72,7 +72,7 @@ async fn ws_list_events(state: Arc<State>, conn: ws::Conn) -> tide::Result<()> {
     // Hence, we buffer the subscriber events while the initial scan is working.
     // In this use case, we can coalesce the events by key.
     // That might consume a lot of memory, but in this use case we're roughly bounded by the number of files changes noticed in one scan, which we assume we can already hold in memory elsewhere.
-    let subscriber = state.media.watch_prefix("");
+    let mut subscriber = state.media.watch_prefix("");
 
     // Do sled tree watching in a separate thread, with a channel between them, to notice slow consumers and kick them out, instead of blocking the database.
     let (sender, receiver) = std::sync::mpsc::sync_channel(1000);

sleigh/Cargo.toml

@@ -8,5 +8,5 @@ edition = "2018"
 bincode = "1.3.3"
 lazy_static = "1.4.0"
 serde = "1.0.136"
-sled = "0.34.6"
+sled = "0.34.7"
 thiserror = "1.0.30"

sleigh/src/lib.rs

@@ -203,7 +203,7 @@ where
     }
 
     pub fn next_timeout(
-        &self,
+        &mut self,
         timeout: Duration,
     ) -> Result<Event<V>, SubscriberTimeoutError<Enc::Error>> {
         let orig = self.sub.next_timeout(timeout)?;