Sync documentation of main branch

Author: actions-user

_generated-doc/main/config/quarkus-all-config.adoc

@@ -4921,28 +4921,6 @@ endif::add-copy-button-to-env-var[]
 a|`warn`, `fail`
 |`warn`
 
-a| [[quarkus-core_quarkus-uuid]] [.property-path]##link:#quarkus-core_quarkus-uuid[`quarkus.uuid`]##
-ifdef::add-copy-button-to-config-props[]
-config_property_copy_button:+++quarkus.uuid+++[]
-endif::add-copy-button-to-config-props[]
-
-
-[.description]
---
-A property that allows accessing a generated UUID. It generates that UUID at startup time. So it changes between two starts including in dev mode.  +
-Access this generated UUID using expressions: `$++{++quarkus.uuid++}++`.
-
-
-ifdef::add-copy-button-to-env-var[]
-Environment variable: env_var_with_copy_button:+++QUARKUS_UUID+++[]
-endif::add-copy-button-to-env-var[]
-ifndef::add-copy-button-to-env-var[]
-Environment variable: `+++QUARKUS_UUID+++`
-endif::add-copy-button-to-env-var[]
---
-|string
-|
-
 h|[.configroot-name]##Configuration tracking and dumping##
 h|Type
 h|Default

_generated-doc/main/config/quarkus-core_quarkus.config.adoc

@@ -161,27 +161,5 @@ endif::add-copy-button-to-env-var[]
 a|`warn`, `fail`
 |`warn`
 
-a| [[quarkus-core_quarkus-uuid]] [.property-path]##link:#quarkus-core_quarkus-uuid[`quarkus.uuid`]##
-ifdef::add-copy-button-to-config-props[]
-config_property_copy_button:+++quarkus.uuid+++[]
-endif::add-copy-button-to-config-props[]
-
-
-[.description]
---
-A property that allows accessing a generated UUID. It generates that UUID at startup time. So it changes between two starts including in dev mode.  +
-Access this generated UUID using expressions: `$++{++quarkus.uuid++}++`.
-
-
-ifdef::add-copy-button-to-env-var[]
-Environment variable: env_var_with_copy_button:+++QUARKUS_UUID+++[]
-endif::add-copy-button-to-env-var[]
-ifndef::add-copy-button-to-env-var[]
-Environment variable: `+++QUARKUS_UUID+++`
-endif::add-copy-button-to-env-var[]
---
-|string
-|
-
 |===
 

_versions/main/guides/native-reference.adoc

@@ -2303,6 +2303,19 @@ com.oracle.svm.core.VM=Mandrel-23.1.5.0-Final
 
 See <<gc-logging,Native Memory Management GC Logging section>> for details.
 
+=== Can I get a thread dump of a native executable?
+
+Yes, Quarkus sets up a signal handler for the `SIGQUIT` signal (or `SIGBREAK` on windows) that will result in a thread
+dump being printed when receiving the `SIGQUIT/SIGBREAK` signal.
+You may use `kill -SIGQUIT <pid>` to trigger a thread dump.
+
+[NOTE]
+====
+Quarkus uses its own signal handler, to use GraalVM's default signal handler instead you will need to:
+1. Add `-H:+DumpThreadStacksOnSignal` to `quarkus.native.additional-build-args` and rebuild the application.
+2. Set the environment variable `DISABLE_SIGNAL_HANDLERS` before running the app.
+====
+
 [[heap-dumps]]
 === Can I get a heap dump of a native executable? e.g. if it runs out of memory
 

_versions/main/guides/rest.adoc

@@ -1011,7 +1011,7 @@ public class Endpoint {
     }
 
     interface SomeResponse {
-        Multi<byte[]> data;
+        Multi<byte[]> data();
 
         String myHeader();
     }

_versions/main/guides/smallrye-fault-tolerance.adoc

@@ -576,7 +576,7 @@ implementation("io.quarkus:quarkus-smallrye-fault-tolerance")
 == Additional resources
 
 SmallRye Fault Tolerance has more features than shown here.
-Please check the link:https://smallrye.io/docs/smallrye-fault-tolerance/6.7.2/index.html[SmallRye Fault Tolerance documentation] to learn about them.
+Please check the link:https://smallrye.io/docs/smallrye-fault-tolerance/6.7.3/index.html[SmallRye Fault Tolerance documentation] to learn about them.
 
 In Quarkus, you can use the SmallRye Fault Tolerance optional features out of the box.
 
@@ -608,7 +608,7 @@ quarkus.fault-tolerance.mp-compatibility=true
 ----
 ====
 
-The link:https://smallrye.io/docs/smallrye-fault-tolerance/6.7.2/reference/programmatic-api.html[programmatic API] is present and integrated with the declarative, annotation-based API.
+The link:https://smallrye.io/docs/smallrye-fault-tolerance/6.7.3/reference/programmatic-api.html[programmatic API] is present and integrated with the declarative, annotation-based API.
 You can use the `Guard`, `TypedGuard` and `@ApplyGuard` APIs out of the box.
 
 Support for Kotlin is present (assuming you use the Quarkus extension for Kotlin), so you can guard your `suspend` functions with fault tolerance annotations.