Merge pull request #6 from sykwer/update

update

Author: atsushi421

docs/environment-setup/configuration.md

@@ -25,13 +25,28 @@ fs.mqueue.msg_max = 256
 fs.mqueue.queues_max = 1024
 ```
 
-If running many Agnocast processes, you may also need to increase the per-user message queue memory limit:
+#### Per-user POSIX message queue memory limit
+
+Each bridge manager message queue consumes memory proportional to the maximum message size and queue depth. When running many Agnocast processes simultaneously, the per-user POSIX message queue memory limit (`RLIMIT_MSGQUEUE`) may be exceeded, causing `mq_open` to fail.
+
+To increase the limit, either add the following line to `/etc/security/limits.conf`:
 
 ```bash
-# In /etc/security/limits.conf or systemd unit
 * - msgqueue unlimited
 ```
 
+Or use `prlimit` to change the limit for the current shell:
+
+```bash
+sudo prlimit --pid=$$ --msgqueue=unlimited
+```
+
+You can verify the current limit with:
+
+```bash
+ulimit -q
+```
+
 ## RT Throttling (for CallbackIsolatedExecutor)
 
 If using real-time scheduling with the CallbackIsolatedExecutor, you may need to increase the RT throttling limit. The default allows RT tasks to use 95% of each period:

docs/environment-setup/index.md

@@ -48,8 +48,8 @@ Install kernel headers (required for DKMS to build the kernel module) and the Ag
 ```bash
 sudo apt install linux-headers-$(uname -r)
 sudo apt install \
-  agnocast-kmod-v2.3.1 \
-  agnocast-heaphook-v2.3.1
+  agnocast-kmod-v2.3.3 \
+  agnocast-heaphook-v2.3.3
 ```
 
 !!! note
@@ -65,22 +65,22 @@ sudo apt install \
     - **minor** — Incremented when the kmod syscall API changes. `agnocastlib` and `agnocast-kmod` with matching major and minor versions are guaranteed to work correctly together.
     - **patch** — Incremented for all other changes.
 
-    Packages use version-pinned names (e.g., `agnocast-kmod-v2.3.1`) to ensure all components are at exactly the same version.
+    Packages use version-pinned names (e.g., `agnocast-kmod-v2.3.3`) to ensure all components are at exactly the same version.
 
 ### 3. Build the ROS packages from source
 
 Since the ROS packages are not yet distributed from the ROS build farm, build them from source:
 
 ```bash
-git clone --branch 2.3.1 https://github.com/autowarefoundation/agnocast.git
+git clone --branch 2.3.3 https://github.com/autowarefoundation/agnocast.git
 cd agnocast
 rosdep install --from-paths src --ignore-src -y
 colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release
 source install/setup.bash
 ```
 
 !!! info
-    Once the ROS build farm release is available, the ROS packages will also be installable via apt (e.g., `ros-jazzy-agnocast=2.3.1*`), and this source build step will no longer be necessary.
+    Once the ROS build farm release is available, the ROS packages will also be installable via apt (e.g., `ros-jazzy-agnocast=2.3.3*`), and this source build step will no longer be necessary.
 
 ### 4. Load the kernel module
 

docs/environment-setup/upgrading.md

@@ -12,7 +12,7 @@ sudo apt install \
   agnocast-heaphook-v<NEW_VERSION>
 ```
 
-For example, to upgrade from 2.3.1 to 2.4.0:
+For example, to upgrade from 2.3.3 to 2.4.0:
 
 ```bash
 sudo apt install agnocast-kmod-v2.4.0 agnocast-heaphook-v2.4.0
@@ -29,7 +29,7 @@ source install/setup.bash
 ```
 
 !!! info
-    Once the ROS build farm release is available, the ROS packages will also be installable via apt (e.g., `ros-jazzy-agnocast=2.3.1*`), and this source build step will no longer be necessary.
+    Once the ROS build farm release is available, the ROS packages will also be installable via apt (e.g., `ros-jazzy-agnocast=2.3.3*`), and this source build step will no longer be necessary.
 
 ## 3. Reload the kernel module
 
@@ -45,6 +45,6 @@ sudo modprobe agnocast
 
 When upgrading, keep the [versioning rules](index.md) in mind:
 
-- **Patch upgrades** (e.g., 2.3.1 → 2.3.2) — Safe. No API or syscall changes.
+- **Patch upgrades** (e.g., 2.3.3 → 2.3.2) — Safe. No API or syscall changes.
 - **Minor upgrades** (e.g., 2.3.x → 2.4.0) — `agnocastlib` and `agnocast-kmod` must be upgraded together, as the kmod syscall API may have changed.
 - **Major upgrades** — User-facing API may have breaking changes. Review the changelog before upgrading.

docs/migration-guide/bridge.md

@@ -142,6 +142,9 @@ graph TD
 ```bash
 ros2 agnocast generate-bridge-plugins \
   --packages std_msgs sensor_msgs geometry_msgs
+
+# Or for all available message types
+ros2 agnocast generate-bridge-plugins --all
 ```
 
 **Step 2:** Build the plugins:

docs/tips/containers.md

@@ -13,7 +13,7 @@ The Agnocast kernel module (`agnocast-kmod`) must be installed on the **host** s
 **Non-Ubuntu hosts** (or environments where `apt` is not available) — Build the kernel module from source:
 
 ```bash
-git clone --branch 2.3.1 https://github.com/autowarefoundation/agnocast.git
+git clone --branch 2.3.3 https://github.com/autowarefoundation/agnocast.git
 cd agnocast/agnocast_kmod
 make
 sudo insmod agnocast.ko