Giter VIP home page Giter VIP logo

Comments (8)

juanlofer-eprosima avatar juanlofer-eprosima commented on June 12, 2024

Hi @263868161

We would need to know more information in order to help you.

  • What version of ShapesDemo is being run? Are you compiling it or taking it from a Docker image / runner?
  • Why are you generating the types? The code related to dynamic types for Shape is already present.
  • Which idl are you using as input? It seems like you added the ros2_interface::msg module/namespace right?

from dds-record-replay.

263868161 avatar 263868161 commented on June 12, 2024

Hi @263868161

We would need to know more information in order to help you.

  • What version of ShapesDemo is being run? Are you compiling it or taking it from a Docker image / runner?
    version:2.11.1,compiling it.
  • Why are you generating the types? The code related to dynamic types for Shape is already present.
    I want to do some different tests.
  • Which idl are you using as input? It seems like you added the ros2_interface::msg namespace right?
    I added the ros2_interface::msg namespace myself,I used three IDL files,'Shape.idl','Header.idl',and 'Time.idl',Shape.idl is the main IDL file,'Shape.idl' contains 'Header.idl',Header.idl contains 'Time.idl',When the ShapeDemp is running,the data of ‘Shape.idl‘ will be sent.

from dds-record-replay.

juanlofer-eprosima avatar juanlofer-eprosima commented on June 12, 2024

It's hard to draw any conclusion with only these hints, would it be possible to share your IDL files? Have you tried merging all three IDL files into a single one? Also, I would try to simplify the setup by removing the namespace.

Needless to say, ShapesDemo is not meant to be modified the way you are doing, so something else other than just substituting the generated files might be required to make it work. Is there any reason why you are not writing your own publishing application?

As a last comment, I believe the type you are describing (2-level structure dependency) would not be supported by Fast-DDS in master branch as of today. Please have a look at eProsima/Fast-DDS-spy#52 (comment) for more information on this regard.

from dds-record-replay.

263868161 avatar 263868161 commented on June 12, 2024

My project has been uploaded as an attachment, which contains the IDL file

from dds-record-replay.

rookybird avatar rookybird commented on June 12, 2024

I met the same issue. Record and Replay works well. But foxglove can not process my mcap file.

image
Any hints?

from dds-record-replay.

juanlofer-eprosima avatar juanlofer-eprosima commented on June 12, 2024

My project has been uploaded as an attachment, which contains the IDL file

Hi @263868161 , I tested the failing cases and you are right, there seems to be issues related to dynamic types which eventually lead to the recorder not storing the information required by Foxglove in order to de-serialize recorded data. We are working on a deep refactor of the dynamic types module (within Fast-DDS library) that should be completed in the upcoming months, tackling this issue as well as other ones identified.

However, I also tested with an unsupported Fast-DDS branch containing a bunch of temporary workarounds, also generating types with the unsupported Fast-DDS-Gen branch, with which the failing cases were successful.

Once the dynamic types refactor is completed, we will check your case and close the issue if everything works fine.

from dds-record-replay.

juanlofer-eprosima avatar juanlofer-eprosima commented on June 12, 2024

I met the same issue. Record and Replay works well. But foxglove can not process my mcap file.

image Any hints?

Hi @rookybird , this again looks like the recorder has not received the type information Foxglove requires for visualizing these topics. Are you sure your applications are generating and sending this type information? Please read this tutorial for more details, and open a different issue if needed.

from dds-record-replay.

rookybird avatar rookybird commented on June 12, 2024

I met the same issue. Record and Replay works well. But foxglove can not process my mcap file.
image Any hints?

Hi @rookybird , this again looks like the recorder has not received the type information Foxglove requires for visualizing these topics. Are you sure your applications are generating and sending this type information? Please read this tutorial for more details, and open a different issue if needed.

Hi @juanlofer-eprosima, thanks for the information!
Previously, I realized that I didn't use the dynamic type. I went through the tutorial, changed the code, and now it works.

from dds-record-replay.

Related Issues (12)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.