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

msgs9 and msgs10 are not compatible #449

Closed
ceccocats opened this issue Jun 26, 2024 · 1 comment
Closed

msgs9 and msgs10 are not compatible #449

ceccocats opened this issue Jun 26, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@ceccocats
Copy link

I can communicate beetween two different version of gz-msgs and gz-transport but updates on message version 10 break compatibility for no reason.

Example:

Version9

message IMU
{
  /// \brief Optional header data
  Header header                = 1;

  string entity_name           = 2;
  Quaternion orientation       = 3;
  Vector3d angular_velocity    = 4;
  Vector3d linear_acceleration = 5;
}

Version10

message IMU
{
  /// \brief Optional header data
  Header header                          = 1;
                                         
  string entity_name                     = 2;

  Quaternion orientation                 = 3;
  /// Row major about x, y, z
  Float_V orientation_covariance         = 4;

  Vector3d angular_velocity              = 5;
  /// Row major about x, y, z
  Float_V angular_velocity_covariance    = 6;

  Vector3d linear_acceleration           = 7;
  /// Row major about x, y, z
  Float_V linear_acceleration_covariance = 8;
}

There is no reason to re-enumerate fields of proto, it should have been like this:

message IMU
{
  /// \brief Optional header data
  Header header                = 1;

  string entity_name           = 2;
  Quaternion orientation       = 3;
  Vector3d angular_velocity    = 4;
  Vector3d linear_acceleration = 5;
  Float_V orientation_covariance         = 6;
  Float_V angular_velocity_covariance    = 7;
  Float_V linear_acceleration_covariance = 8;
}

There is any specific reason why its like that?

@ceccocats ceccocats added the bug Something isn't working label Jun 26, 2024
@azeey
Copy link
Contributor

azeey commented Jun 26, 2024

It was probably done to keep similar fields grouped together. In hind sight, we should have added those new fields without changing the existing field positions. At this point, changing it in gz-msgs10 would break ABI, so I would not be in favor of that.

@azeey azeey closed this as not planned Won't fix, can't repro, duplicate, stale Jul 22, 2024
@github-project-automation github-project-automation bot moved this from Inbox to Done in Core development Jul 22, 2024
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
Archived in project
Development

No branches or pull requests

2 participants