Reset non reproducible

[ShuffleWire]

Describe the Bug When using the Reset, I've meet case that give me different sensors values after the Reset that the one I've got before. I've tried to provide a minimal example showing the issue, but that not perfect. I can't nailed down better the issue, even if it happen deeply buried in my project, so that still better :) Removing anything else make the issue disappear.

The following procedure demonstrate that the output of a Compass Node change after Reset. Please validate first on your configuration that you get the same issue, and ideally the same values.

Steps to Reproduce

1. Open world reset_bug.zip (ensure controller is built) (don't be afraid by the warning when loading the world, it doesn't impact the result)
2. Run, it should print "0.00000150747052294190 0.99999999998302735449 -0.00000562786575188646" (1)
3. Reset, re-run, it should print "0.00000150747052322629 0.99999999998302735449 -0.00000562786575213521" (2) , which is different from the first time

For the purpose of this bug report, I've tried to implement a one click solution, so using the controller to Reset itself the world, and the result was surprising :

1. Un-comment the code in the controller and re-build
2. Reload, and run
3. It should print "0.00000150747052294190 0.99999999998302735449 -0.00000562786575188646" (3) "0.00000000000000000000 1.00000000000000000000 0.00000000000000000000" (4)

As expected Reload ensure that (1)==(3), but we should get (2)==(4) However that could be a separate bug, waiting for advice on that one.

After that, each reset done manually give the value (2)

Expected behavior We should always get the same value : (1)==(2)==(3)==(4)

System

• Operating System: Windows 11 (WSL Ubuntu 20) and Linux Debian 12
• Webots 2023b