Greptile Summary

This PR fixes Isaac Lab INFO log records (most notably the joint wrench sensor init message) being silently swallowed after SimulationApp starts and Kit installs its Python logging bridge at DEBUG level. Three static helpers are added to AppLauncher to snapshot the desired log level before Kit starts and then restore it — plus a dedicated scoped StreamHandler — after Kit's bridge is in place.

• Default (WARNING) path — Kit bridge handlers are pinned to WARNING so non-isaaclab noise is suppressed, while the scoped handler lets isaaclab.* INFO records reach sys.stdout directly. This path is tested by the stated test plan and appears correct.
• Verbose / info path — the scoped stdout handler is also added when --verbose or --info is passed, even though _apply_python_logging_level already sets Kit's bridge handlers to INFO/DEBUG; if carb surfaces in the same terminal as Python stdout this will duplicate every isaaclab.* INFO line.
• The elif WARNING branch calls _apply_python_logging_level(WARNING) (which sets root to WARNING) and then immediately overrides root to INFO; the root-level assignment inside the helper is a no-op here, which is worth documenting or restructuring.

Confidence Score: 3/5

The default (no-flag) path is correct and tested; the --info/--verbose path may produce duplicate log output depending on Kit's carb routing, and was not covered by the test plan.

The fix restores the missing joint-wrench initialization log and the WARNING-mode logic is sound. However, the branch that fires when the user explicitly passes --info or --verbose installs the scoped stdout handler at the same time as Kit's bridge is set to INFO/DEBUG — if carb directs its output to the same console, every isaaclab INFO line will appear twice. This code path was not mentioned in the test plan, so the potential duplicate-output regression is unverified.

source/isaaclab/isaaclab/app/app_launcher.py — the verbose/info branch of _load_extensions needs a second look

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[AppLauncher.__init__ called] --> B[_resolve_python_logging_level\nsnapshot level before Kit]
    B --> C[SimulationApp starts\nKit installs Python log bridge at DEBUG]
    C --> D[_load_extensions called]
    D --> E[_apply_python_logging_level\nset root + all handlers to resolved level]
    E --> F{resolved level?}
    F -- "≤ INFO\n(--info / --verbose)" --> G[_ensure_isaaclab_info_stream_handler\nadd scoped stdout handler]
    F -- "== WARNING\n(default)" --> H[_ensure_isaaclab_info_stream_handler\nadd scoped stdout handler]
    H --> I[root logger setLevel INFO\nso scoped handler receives INFO records]
    F -- "> WARNING\n(ERROR / CRITICAL)" --> J[No scoped handler added\nisaaclab INFO hidden]
    G --> K{carb output in same terminal?}
    K -- Yes --> L[Duplicate isaaclab INFO lines\ncarb via bridge + scoped stdout]
    K -- No --> M[isaaclab INFO visible in terminal only]
    I --> N[Kit bridge handlers at WARNING\nfilter non-isaaclab INFO\nScoped handler passes isaaclab INFO to stdout]

_{Reviews (1): Last reviewed commit: "Fix Kit Python info logging" | Re-trigger Greptile}