Maksim Derbasov

Running this test with `taskset -c 1 ./UNIT_Server_TEST` to limit physical threads can help to reproduce this problem (on one of my set-ups it shoots 1:10) I guess it's related...

For automation I'm using `for i in {1..101}; do echo "Iteration: $i"; taskset -c 1 ./UNIT_Server_TEST || break ; done` but once I had almost 100 runs in a row...

Hm.. It fells like old file was started. I made PR to my fork with same changes: https://github.com/ntfshard/Remotery/pull/3 (https://github.com/ntfshard/Remotery/actions/runs/16171921319?pr=3)

I researched same problem related to gpu-lidars and I believe problem in gz-transport. But also people suggesting to try orge instead of orge 2. https://github.com/gazebosim/ros_gz/issues/368 Topics working through network (even...

Proposal: keep sdf structure similar to sdf joint definition http://sdformat.org/spec?ver=1.9&elem=joint e.g. physics -> ode -> (new fields) And also possible to use defaults from sdf instead of optional for consistency

> > Proposal: keep sdf structure similar to sdf joint definition http://sdformat.org/spec?ver=1.9&elem=joint > > e.g. physics -> ode -> (new fields) > > I thought about this, but decided it...

> Have you seen #1538? No UPD: I tried to use python bindings to generate sdf files and got error msg, which bring me to missing implementation. Now I see...

> Have you seen #1538? What would you suggest to do in this case? Fortunately we rewrote sdf generation on a pure python and don't constrained by this PR, but...