# \#cli

**URL:** https://precice.discourse.group/tag/cli/126.md

[Latest](https://precice.discourse.group/latest.md) · [Categories](https://precice.discourse.group/categories.md) · [Tags](https://precice.discourse.group/tags.md)

---

## [Bug in nested profiling section outputs?](https://precice.discourse.group/t/bug-in-nested-profiling-section-outputs/2654)

<div class="topic-metadata">

**Author:** [@ErwinM](https://precice.discourse.group/u/ErwinM)\
**Replies:** 3\
**Last updated:** [November 6, 2025, 1:58pm UTC](https://precice.discourse.group/t/bug-in-nested-profiling-section-outputs/2654 "2025-11-06T13:58:05Z")

</div>

I have been playing around with profiling in my application, and I ran into the following issue. Whenever I created nested profiling sections, the output looks like this: N31:master\_step B31:594768 N32:run\_my\_step B…

---

## [Highlights of the new preCICE release v3.3](https://precice.discourse.group/t/highlights-of-the-new-precice-release-v3-3/2636)

<div class="topic-metadata">

**Author:** [@uekerman](https://precice.discourse.group/u/uekerman)\
**Replies:** 0\
**Last updated:** [October 9, 2025, 3:52pm UTC](https://precice.discourse.group/t/highlights-of-the-new-precice-release-v3-3/2636 "2025-10-09T15:52:04Z")

</div>

Summary: With preCICE v3.3.0, we focused on improving clarity, portability, and tooling. The new release brings clearer coupling-state output and more helpful error messages. Tooling has been reworked significantly and i…