Skip to content

Conversation

@chen-harrison
Copy link
Contributor

Summary

  • Requested by @azeey from gz-common: Profiler gazebo_test_cases#1749
  • Explicitly create new project directory called profiler_example
  • Download profiler.cc into directory using wget
  • Remove unnecessary grep dependency
  • Clarify the CMakeLists is being created, not modified
  • Separate the different options for running the profiler visualization into multiple blocks, with the conditions described more clearly
  • Would like confirmation on what IP address http.server broadcasts to; tutorial says it's the container's IP address, but it always showed up as 0.0.0.0 (localhost) for me in my container
  • I looked through the contributing guidelines and couldn't find any information on linting tests or formatting standards for these Markdown files, so please point me to them if available!

Checklist

  • Signed all commits for DCO
  • Added tests
  • Updated documentation (as needed)
  • Updated migration guide (as needed)
  • Consider updating Python bindings (if the library has them)
  • codecheck passed (See contributing)
  • All tests passed (See test coverage)
  • While waiting for a review on your PR, please help review another open pull request to support the maintainers
  • Was GenAI used to generate this PR? If so, make sure to add "Generated-by" to your commits. (See this policy for more info.)

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by and Generated-by messages.

- Explicitly create new project directory called profiler_example
- Download profiler.cc into directory using wget
- Remove unnecessary grep dependency
- Clarify the CMakeLists is being created, not modified
- Separate the different options for running the profiler visualization
  into multiple blocks, with the conditions described more clearly
- Would like confirmation on what IP address http.server broadcasts to;
  tutorial says it's the container's IP address, but it always showed up
  as 0.0.0.0 (localhost) for me in my container

Signed-off-by: Harrison Chen <hchen.robotics@gmail.com>
@github-project-automation github-project-automation bot moved this from Inbox to In review in Core development Sep 23, 2025
@ahcorde ahcorde changed the title Improvments to Profiler Tutorial Improvements to Profiler Tutorial Sep 23, 2025
@azeey azeey enabled auto-merge (squash) October 16, 2025 16:15
@chen-harrison
Copy link
Contributor Author

I don't have much context for this error - is this something for me to fix on my end? If it's a formatting issue, I had asked in the description about formatting guidelines, if those are available somewhere. I wasn't able to find them.

@azeey
Copy link
Contributor

azeey commented Oct 16, 2025

@chen-harrison I'm not sure what the windows failure is, but this is just a documentation update, so it shouldn't cause any test failures. It might be related to gazebo-tooling/release-tools#1405

cc @j-rivero

I'll go ahead and merge this.

@azeey azeey disabled auto-merge October 16, 2025 19:17
@azeey azeey merged commit 2b33445 into gazebosim:gz-common7 Oct 16, 2025
13 of 14 checks passed
@github-project-automation github-project-automation bot moved this from In review to Done in Core development Oct 16, 2025
@azeey
Copy link
Contributor

azeey commented Oct 16, 2025

@Mergifyio backport gz-common6 gz-common5 ign-common4

@mergify
Copy link
Contributor

mergify bot commented Oct 16, 2025

backport gz-common6 gz-common5 ign-common4

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Oct 16, 2025
- Explicitly create new project directory called profiler_example
- Download profiler.cc into directory using wget
- Remove unnecessary grep dependency
- Clarify the CMakeLists is being created, not modified
- Separate the different options for running the profiler visualization
  into multiple blocks, with the conditions described more clearly
- Would like confirmation on what IP address http.server broadcasts to;
  tutorial says it's the container's IP address, but it always showed up
  as 0.0.0.0 (localhost) for me in my container

Signed-off-by: Harrison Chen <hchen.robotics@gmail.com>
Co-authored-by: Addisu Z. Taddese <addisu@openrobotics.org>
(cherry picked from commit 2b33445)

# Conflicts:
#	tutorials/profiler.md
mergify bot pushed a commit that referenced this pull request Oct 16, 2025
- Explicitly create new project directory called profiler_example
- Download profiler.cc into directory using wget
- Remove unnecessary grep dependency
- Clarify the CMakeLists is being created, not modified
- Separate the different options for running the profiler visualization
  into multiple blocks, with the conditions described more clearly
- Would like confirmation on what IP address http.server broadcasts to;
  tutorial says it's the container's IP address, but it always showed up
  as 0.0.0.0 (localhost) for me in my container

Signed-off-by: Harrison Chen <hchen.robotics@gmail.com>
Co-authored-by: Addisu Z. Taddese <addisu@openrobotics.org>
(cherry picked from commit 2b33445)

# Conflicts:
#	tutorials/profiler.md
mergify bot pushed a commit that referenced this pull request Oct 16, 2025
- Explicitly create new project directory called profiler_example
- Download profiler.cc into directory using wget
- Remove unnecessary grep dependency
- Clarify the CMakeLists is being created, not modified
- Separate the different options for running the profiler visualization
  into multiple blocks, with the conditions described more clearly
- Would like confirmation on what IP address http.server broadcasts to;
  tutorial says it's the container's IP address, but it always showed up
  as 0.0.0.0 (localhost) for me in my container

Signed-off-by: Harrison Chen <hchen.robotics@gmail.com>
Co-authored-by: Addisu Z. Taddese <addisu@openrobotics.org>
(cherry picked from commit 2b33445)

# Conflicts:
#	tutorials/profiler.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🪵 jetty Gazebo Jetty

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants