Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 10:08
    MatthiasKillat commented #859
  • 10:07
    MatthiasKillat commented #859
  • 10:06
    MatthiasKillat commented #859
  • 09:58
    MatthiasKillat edited #859
  • 09:56
    codecov[bot] commented #863
  • 09:56
    MatthiasKillat commented #859
  • 09:56
    codecov[bot] commented #863
  • 09:55
    MatthiasKillat commented #859
  • 09:52
    MatthiasKillat commented #859
  • 09:51
    MatthiasKillat commented #859
  • 09:50
    MatthiasKillat commented #859
  • 09:46
    MatthiasKillat commented #859
  • 09:32
    codecov[bot] commented #863
  • 09:32
    elBoberido synchronize #863
  • 09:29
    elBoberido reopened #27
  • 09:29
    elBoberido labeled #858
  • 09:29
    elBoberido unlabeled #858
  • 09:29

    elBoberido on master

    iox-#27 Add new queue policies … iox-#27 Add options client port… iox-#27 Use client options in c… and 13 more (compare)

  • 09:29
    elBoberido closed #858
  • 09:29
    elBoberido closed #27
Simon Hoinkis
@mossmaurice
Thanks for voting everyone! The iceoryx releases will be named after ice cream flavours :icecream: We'll choose them in an alphabetical order. The v1.0 will be named Almond
elBoberido
@elBoberido
No vote for the name? This is tyranny 😄
Simon Hoinkis
@mossmaurice
https://en.wikipedia.org/wiki/List_of_ice_cream_flavors At least on this list, there's not too much choice as there is this company from Cupertino :P
elBoberido
@elBoberido
Well the list is not exhaustive, there is Amaretto or Amaretto Cheesecake (https://frostyfrogcreamery.com/gourmet-ice-cream/gourmet-ice-cream-flavors/)
Michael Pöhnl
@budrus
I would go for a single word. I would prefer Almond over Amaretto. But also fine for me to have a ice vote
Can we agree that we follow the alphabet like ROS does
elBoberido
@elBoberido
I'm also fine with Almond. Don't take me too serious ;)
Martin Hintz
@marthtz
Go for it :rocket:
Simon Hoinkis
@mossmaurice

Hi, as announced in last weeks developer meetup, here's the vote for the new iceoryx logo: https://dudle.inf.tu-dresden.de/XwDk-kpK5Q/

Standing or moving iceoryx, which one do you prefer? Thanks for voting!

dkroenke
@dkroenke
Github Actions are currently facing technical issues on the availability of the CI Runners: https://www.githubstatus.com/incidents/fjrtcnfz2cpd Please postpone push commits on Pull-Requests to avoid stacking up the wait queue in the CI.
Indra5196
@Indra5196
Hi all. No meeting today?
Simon Hoinkis
@mossmaurice
Hi Indra, seems like we had a daylight saving issue today :( Sorry about that. The dev meetup took place at 5PM CET.
We postponed the dynamic data type agenda item to the next meetup.
If you want to talk about it earlier we can schedule a separate meeting
Simon Hoinkis
@mossmaurice
Almond RC2 is out now! Expect the Almond v1.0 LTS to land end of April. Feedback is very welcome!
Michael Pöhnl
@budrus
We'll have an extra meeting before the developer meeting on April 15. Topic is the request/response feature we now want to continue with. Details see https://github.com/eclipse-iceoryx/iceoryx/wiki/2021-04-15-Alignment-request-response-feature
April 15 2 pm CET, 5:30 pm IST,...
elBoberido
@elBoberido
Today is a special day for iceoryx. We are pleased to release v1.0.0 https://github.com/eclipse-iceoryx/iceoryx/releases/tag/v1.0.0
Martin Hintz
@marthtz
:rocket:
Martin Hintz
@marthtz
Where and when can we get new stickers? :wink:
elBoberido
@elBoberido
Nihal Chari
@nihalchari
Hello, https://github.com/eclipse-iceoryx/iceoryx/blob/master/iceoryx_posh/source/runtime/posh_runtime.cpp:154 , getServiceRegistryChangeCounter() returns same pointer on every call, i would like to create a isssue to fix this if not already created
Simon Hoinkis
@mossmaurice
Hi @nihalchari the current plan is to rework the service discovery feature with #415, we might be able to remove the getServiceRegistryChangeCounter() then. Could you have a look at the issue and post a comment with your thoughts on it? Thanks!
Yonggang Luo
@lygstate
Is that possible implement iceoryx_meta in pure c?
elBoberido
@elBoberido
@lygstate I'm not sure what you mean. iceoryx_meta is just a convenient cmake target to build iceoryx. Can you elaborate what you intend to do?
Yonggang Luo
@lygstate
Oh sorry, I am talking about the core part of iceoryx
cyclonedds are implement in pure c and it's depends on iceoryx, but iceoryx are implement in C++17, that's so much different
elBoberido
@elBoberido
I think that is out of scope for iceoryx, but there a C language bindings so it can be used from a C codebase
Simon Hoinkis
@mossmaurice
@lygstate I think there was a misunderstanding. iceoryx is implemented in C++14. That's defacto state-of-the-art in the automotive industry and I think this won't change over the next years. However, some C++17 constructs like std::variant and std::optional are custom implemented in C++14 and widely used in iceoryx.
Indra5196
@Indra5196
Hi @elBoberido. I was discussing with @budrus in today's meeting regarding RPCBaseHeader usage for Request / Response communication. Thing is that, ChunkSender Allocates a chunk with ChunkHeader. Hence we cannot use ChunkSender for now to allocate request / response chunks. We also discussed regarding using RPCBaseHeader as a userHeader for ChunkHeader. But my question was, shall we treat RPC header as User headers? as its implementation is not going to be upto the user. Or is it better we create a base header class for both types of headers?
4 replies
Michael Pöhnl
@budrus
As most of the attendees are located in Germany and there is a holiday this Thursday, we will cancel the developer meeting this week
elBoberido
@elBoberido
Hi guys,
end of last week two PRs were merged which might affect your local branches. One is the refactoring of smartC to posixCall. Besides the name change, the abstraction now uses the Builder Pattern and makes it easier to use. The second PR will almost definitely affect you since the iceoryx_utils got renamed to iceoryx_hoofs. The idea behind this change is to make this building blocks more prominent and make them visible as standalone library which could also be used without iceoryx_posh. The renaming has a rather big effect on your local branches. Please take care that new files you created in iceoryx_utils will also be moved to iceoryx_hoofs when you merge/rebase with master.
Bernd Eickhoff
@bishibashiB
Thx for sharing / mentioning about iceoryx_hoofs. Interesting name if I may add. Is that the name for the oryx hoof? or another 'abbreviation' (https://www.abbreviations.com/HOOF)?
Will 'hoofs' eventually move to a separate repo (-> mentioned 'standalone' library)? ...
elBoberido
@elBoberido
there is no plan to move it to a separate repo since it's quite handy to have everything in the same repo but it might be possible to build it standalone
Walter Gray
@yeswalrus
Question - I'm evaluating using Iceoryx directly in a major project currently using ROS1 for serialization & IPC. Does anyone know if there is some mode where Iceoryx does not require RouDi to be running? Cyclone DDS as a ROS2 implementation seems to indicate this is possible, since ROS2 explicitly doesn't require a master, but using Cyclone+Iceoryx could add that requirement so I'm not entirely sure.
elBoberido
@elBoberido
@yeswalrus RouDi is always required, also with Cyclone DDS. As far as I know there is a fallback if RouDi is not running, but I have to ask @MatthiasKillat. He has more knowledge about this
Walter Gray
@yeswalrus
Good to know, thank you!
One other question - Is it possible to have multiple concurrent networks running, or multiple instances of RouDi running concurrently? Especially for testing it would be nice to be able to execute multiple isolated networks in parallel.
dkroenke
@dkroenke

@yeswalrus Currently, there is only one running instance of RouDi per system allowed, you can check it by trying to start another instance of RouDi that will fail with an error message.
The recommendation is to run RouDi in multiple docker containers optionally orchestrated by docker-compose to test networking. An example how this can be done is here.

The current dds gateway example on master is unfortunately broken but there is a bugfix in the pipeline on this branch if you want to try it.

Michael Pöhnl
@budrus
@yeswalrus Both of your points are solvable I guess. In ROS 2 there is a Python daemon that is automatically started when you use the ROS 2 command line interface. So it should also be possible to automatically start the RouDi daemon when needed and it is not yet running. Currently we ensure that only one RouDi instance is running. But Internally we already deal with IDs for RouDi. So it should be possible to extend it in a way to allow starting of several RouDis with different IDs. Then you would have to set in your application the one you want to use. What dio you think @dkroenke @elBoberido. Would this be a feature for the roadmap?
elBoberido
@elBoberido
@budrus short answer, yes. I also thought about multiple RouDi for some time. The big issue is how to tell the application which one to use. We could either define it by an environment variable or by extending initRuntime with a second parameter for the RouDi IPC name. On the RouDi side this could also be done either by environment variable or by a setting in the config file. One thing I don't have a solution for is when you want an application to use multiple RouDi to transfer data between domains but maybe that's a task for DDS.
elBoberido
@elBoberido
FYI, last week @dkroenke added some git hooks to iceoryx. This is quite helpful to prevent some common mistakes like forgetting to use clang-format or using the issue number in the commit message. Have a look at https://github.com/eclipse-iceoryx/iceoryx/blob/master/tools/git-hooks/Readme.md on how to use them
Simon Hoinkis
@mossmaurice
Hi all, tomorrow at 16:00 CET there'll be a talk happening in the ROS Safety Working Group that will touch on the future of iceoryx hoofs: https://discourse.ros.org/t/safety-working-group-june-presentation-writing-safer-code/20362 Feel free to join!
Simon Hoinkis
@mossmaurice
Hi all, another talk is happening tomorrow at 17:00 CET: https://www.crowdcast.io/e/vecm_iceoryx Topic will be "Introducing Eclipse iceoryx Almond" and will contain a introduction to iceoryx and a summary of the new features in Almond. Feel free to join!
elBoberido
@elBoberido
Hi all. Since writing mocks for methods with the noexcept specifier is quite cumbersome with GMock v1.8 I'd like to upgrade to v1.10 in the near future. This is the related issue eclipse-iceoryx/iceoryx#841
Oliver Schünemann
@oschuene
I would like to put the vector size 0 topic on the agenda for the developer meeting this evening.
Simon Hoinkis
@mossmaurice
Simon Hoinkis
@mossmaurice
Hi all, does anyone have topics for today's developer meetup?