Drop viser dependency

[jiwenc-nv]

Summary by CodeRabbit

• Chores
  • Updated viser dependency requirement to version 1.0.0 or higher.

[github-actions]

📝 Docs preview is not auto-deployed for fork PRs.

A maintainer with write access to NVIDIA/IsaacTeleop can deploy a preview by
commenting /preview-docs on this PR. Once deployed, the preview
will live at:

https://nvidia.github.io/IsaacTeleop/preview/pr-501/

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates the viser library dependency constraint in two files. The example teleop ROS2 project's pyproject.toml changes from a pinned version viser==0.1.0 to a minimum version viser>=1.0.0. The same dependency is added to the core grounding runtime requirements file with the same minimum version constraint.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• NVIDIA/IsaacTeleop#500: Both PRs modify the same file (src/core/python/requirements-grounding.txt) to add the runtime dependency "viser>=1.0.0", indicating closely related or parallel dependency updates.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title 'Drop viser dependency' contradicts the actual changes, which update and add viser dependency constraints, not remove them.	Update the title to reflect the actual changes, such as 'Relax viser version constraints' or 'Update viser to >=1.0.0', matching the PR objective to 'relax viser version'.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@examples/teleop_ros2/python/pyproject.toml`:
- Around line 16-18: The dependency line currently allows viser>=1.0.0 which
reintroduces yourdfpy (and trimesh) despite the comment; change the version
constraint for the package reference "viser>=1.0.0" to a specific range that
excludes releases that depend on yourdfpy (for example pin to "viser<1.0.0" or
to a known safe release like "viser==0.x.y" or a later safe range if available),
or update the comment to accurately state you intend to allow viser>=1.0.0;
locate and modify the dependency token "viser>=1.0.0" in the pyproject.toml and
ensure the comment above it matches the new constraint.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 6ec84a2b-8a61-4a73-a7ca-aa3696849db5

📥 Commits

Reviewing files that changed from the base of the PR and between 3cad769 and 4afc4be.

📒 Files selected for processing (2)

• examples/teleop_ros2/python/pyproject.toml
• src/core/python/requirements-grounding.txt