Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom gz-msgs example raises "File already exists in database" warnings #460

Open
romulogcerqueira opened this issue Sep 10, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@romulogcerqueira
Copy link

romulogcerqueira commented Sep 10, 2024

Environment

  • OS Version: Ubuntu 22.04
  • Source build: gz-msgs10 / commit: 0da35a8

Description

When compiling the generating_custom_msgs example and setting the GZ_DESCRIPTOR_PATH environment variable to point to the path of the generated .gz_desc file, the following warnings are raised when running the Gazebo stack.

[libprotobuf ERROR google/protobuf/descriptor_database.cc:120] File already exists in database: gz/msgs/time.proto
[libprotobuf ERROR google/protobuf/descriptor_database.cc:120] File already exists in database: gz/msgs/header.proto

Steps to reproduce / Output

image

@romulogcerqueira romulogcerqueira added the bug Something isn't working label Sep 10, 2024
@azeey azeey moved this from Inbox to To do in Core development Nov 11, 2024
@azeey
Copy link
Contributor

azeey commented Nov 11, 2024

@iche033 to test if this is fixed by #472

@iche033
Copy link
Contributor

iche033 commented Nov 11, 2024

after taking a closer look, I think this is unrelated to #472. Tested and saw that warnings are still printed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: To do
Development

No branches or pull requests

4 participants