From f34f4c4692e5dd451016a8138b38175702d30185 Mon Sep 17 00:00:00 2001 From: Simran Spiller Date: Fri, 12 Jan 2024 07:31:12 +0100 Subject: [PATCH 1/3] Some arangod exit codes changed --- .../version-3.12/incompatible-changes-in-3-12.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md b/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md index ed9fc5c738..61ce93a5c6 100644 --- a/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md +++ b/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md @@ -119,6 +119,12 @@ can now be configured with the `--transaction.streaming-max-transaction-size` startup option. The default value remains 128 MiB but configuring a lower limit can cause previously working Stream Transactions to fail. +## Exit code adjustments + +For some fatal errors like a require database upgrade or a failed version check, +_arangod_ set the generic exit code of `1`. It now returns a different, more +specific exit code in these cases. + ## Client tools ### jslint feature in arangosh From 5f2567a97a72b845447fd785b56d2b2a3c8b943c Mon Sep 17 00:00:00 2001 From: Simran Spiller Date: Fri, 12 Jan 2024 07:35:37 +0100 Subject: [PATCH 2/3] Backports --- .../version-3.10/incompatible-changes-in-3-10.md | 8 ++++++++ .../version-3.11/incompatible-changes-in-3-11.md | 8 ++++++++ .../version-3.12/incompatible-changes-in-3-12.md | 2 ++ 3 files changed, 18 insertions(+) diff --git a/site/content/3.10/release-notes/version-3.10/incompatible-changes-in-3-10.md b/site/content/3.10/release-notes/version-3.10/incompatible-changes-in-3-10.md index 72186005a9..c19b3bc00a 100644 --- a/site/content/3.10/release-notes/version-3.10/incompatible-changes-in-3-10.md +++ b/site/content/3.10/release-notes/version-3.10/incompatible-changes-in-3-10.md @@ -192,6 +192,14 @@ It is also an error if you specify an edge collection that is not part of the named graph's definition or of the list of edge collections (code `1939` and HTTP status `400 Bad Request`). +## Exit code adjustments + +Introduced in: v3.10.13 + +For some fatal errors like a require database upgrade or a failed version check, +_arangod_ set the generic exit code of `1`. It now returns a different, more +specific exit code in these cases. + ## Startup Options ### Handling of Invalid Startup Options diff --git a/site/content/3.11/release-notes/version-3.11/incompatible-changes-in-3-11.md b/site/content/3.11/release-notes/version-3.11/incompatible-changes-in-3-11.md index 98f736710d..989c0d277f 100644 --- a/site/content/3.11/release-notes/version-3.11/incompatible-changes-in-3-11.md +++ b/site/content/3.11/release-notes/version-3.11/incompatible-changes-in-3-11.md @@ -251,6 +251,14 @@ the result array for the respective documents, along with the successful ones: {"_key":"valid","_id":"coll/valid","_rev":"_gG9JHsW---"} ``` +## Exit code adjustments + +Introduced in: v3.10.13, v3.11.7 + +For some fatal errors like a require database upgrade or a failed version check, +_arangod_ set the generic exit code of `1`. It now returns a different, more +specific exit code in these cases. + ## Batch-reading an empty list of documents succeeds Introduced in: v3.11.1 diff --git a/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md b/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md index 61ce93a5c6..dcf565b16f 100644 --- a/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md +++ b/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md @@ -121,6 +121,8 @@ can cause previously working Stream Transactions to fail. ## Exit code adjustments +Introduced in: v3.10.13, v3.11.7, v3.12.0 + For some fatal errors like a require database upgrade or a failed version check, _arangod_ set the generic exit code of `1`. It now returns a different, more specific exit code in these cases. From 48337cb3325b1ecb2ee149e537e51ca4cce49b41 Mon Sep 17 00:00:00 2001 From: Simran Spiller Date: Fri, 12 Jan 2024 10:26:36 +0100 Subject: [PATCH 3/3] Fix typo --- .../release-notes/version-3.10/incompatible-changes-in-3-10.md | 2 +- .../release-notes/version-3.11/incompatible-changes-in-3-11.md | 2 +- .../release-notes/version-3.12/incompatible-changes-in-3-12.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/site/content/3.10/release-notes/version-3.10/incompatible-changes-in-3-10.md b/site/content/3.10/release-notes/version-3.10/incompatible-changes-in-3-10.md index c19b3bc00a..6a6279714f 100644 --- a/site/content/3.10/release-notes/version-3.10/incompatible-changes-in-3-10.md +++ b/site/content/3.10/release-notes/version-3.10/incompatible-changes-in-3-10.md @@ -196,7 +196,7 @@ HTTP status `400 Bad Request`). Introduced in: v3.10.13 -For some fatal errors like a require database upgrade or a failed version check, +For some fatal errors like a required database upgrade or a failed version check, _arangod_ set the generic exit code of `1`. It now returns a different, more specific exit code in these cases. diff --git a/site/content/3.11/release-notes/version-3.11/incompatible-changes-in-3-11.md b/site/content/3.11/release-notes/version-3.11/incompatible-changes-in-3-11.md index 989c0d277f..33c13a254b 100644 --- a/site/content/3.11/release-notes/version-3.11/incompatible-changes-in-3-11.md +++ b/site/content/3.11/release-notes/version-3.11/incompatible-changes-in-3-11.md @@ -255,7 +255,7 @@ the result array for the respective documents, along with the successful ones: Introduced in: v3.10.13, v3.11.7 -For some fatal errors like a require database upgrade or a failed version check, +For some fatal errors like a required database upgrade or a failed version check, _arangod_ set the generic exit code of `1`. It now returns a different, more specific exit code in these cases. diff --git a/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md b/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md index dcf565b16f..3e211eee99 100644 --- a/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md +++ b/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md @@ -123,7 +123,7 @@ can cause previously working Stream Transactions to fail. Introduced in: v3.10.13, v3.11.7, v3.12.0 -For some fatal errors like a require database upgrade or a failed version check, +For some fatal errors like a required database upgrade or a failed version check, _arangod_ set the generic exit code of `1`. It now returns a different, more specific exit code in these cases.