From d8245f146e3a33005713091bf7297f8ea0921c26 Mon Sep 17 00:00:00 2001 From: Marten Wijnja Date: Wed, 13 Aug 2025 13:49:39 +0200 Subject: [PATCH 1/2] Bump version numbers (this was forgotten in release 34) --- Cargo.lock | 4 ++-- libs/opsqueue_python/Cargo.toml | 2 +- opsqueue/Cargo.toml | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/Cargo.lock b/Cargo.lock index 2fea136..312d7f9 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -2066,7 +2066,7 @@ dependencies = [ [[package]] name = "opsqueue" -version = "0.30.4" +version = "0.30.5" dependencies = [ "anyhow", "arc-swap", @@ -2120,7 +2120,7 @@ dependencies = [ [[package]] name = "opsqueue_python" -version = "0.30.4" +version = "0.30.5" dependencies = [ "anyhow", "chrono", diff --git a/libs/opsqueue_python/Cargo.toml b/libs/opsqueue_python/Cargo.toml index a7a5620..520a2a0 100644 --- a/libs/opsqueue_python/Cargo.toml +++ b/libs/opsqueue_python/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "opsqueue_python" -version = "0.30.4" +version = "0.30.5" edition = "2021" # See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html diff --git a/opsqueue/Cargo.toml b/opsqueue/Cargo.toml index 724d373..112096b 100644 --- a/opsqueue/Cargo.toml +++ b/opsqueue/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "opsqueue" -version = "0.30.4" +version = "0.30.5" edition = "2021" description = "lightweight batch processing queue for heavy loads" repository = "https://github.com/channable/opsqueue" From c01c0217c9fd1e6ad5b53eb5113cf6f0dd108cd1 Mon Sep 17 00:00:00 2001 From: Maarten van den Berg Date: Wed, 20 Aug 2025 17:20:51 +0200 Subject: [PATCH 2/2] README: Add double whitespace also present on internal version --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 50f00b0..71b5855 100644 --- a/README.md +++ b/README.md @@ -339,6 +339,7 @@ Under the hood, the producer and the queue talk with each other using a JSON-RES The communication between the consumer and the queue on the other hand is done in COBR over a persistent WebSocket connection. A heartbeating protocol is used to ensure that a closed or broken connection is detected early. The goal is that the system will recognize and recover from network problems or crashed consumers within seconds. Similarly, as a user no detailed understanding of this should be necessary as it is abstracted away inside the client library. + ### Consumer <-> Opsqueue Heartbeating For heartbeating between the queue and the consumer, the following approach is used: