Time.msg is subject to year 2038 problems

[clalancette]

Bug report

Time.msg currently defines the seconds as an int32 and the nanoseconds as a uint32. Since time in ROS 2 is measured as time since the Epoch, this means that these messages are subject to the Year-2038 problem. This actually is bubbling up from the underlying DDS standard, which has a similar problem: https://issues.omg.org/issues/DDS15-13 .

@richiprosima @cwyark @neil-rti What's the state of the DDS standard on this? How is OMG (and your libraries) planning to deal with this problem?

Thanks in advance for any info here.

Required Info:

• Operating System:
  • All
• Installation type:
  • Source
• Version or commit hash:
  • a7ea280
• DDS implementation:
  • All (Fast-RTPS, Connext, Opensplice)
• Client library (if applicable):
  • All?