in simulated service: cannot use lambda and ForEach for all will get triggered at the same time
we want sequential init every second - and thats ok
However we d still want to investigate the issie for the design should have prevented it.
The bad behavior is:
When some planes to fail be added to info api because of several add requests at the same time (what happened there?) instead of being added on re try add request theycontinue to fail to be added and moreover Loop Update is triggered and they continually fail on update loop .
Maybe add re try loop to lifetime managers from http client and replace recursive call with for loop with additional logging for this issue to better track it?
in simulated service: cannot use lambda and ForEach for all will get triggered at the same time we want sequential init every second - and thats ok
However we d still want to investigate the issie for the design should have prevented it. The bad behavior is: When some planes to fail be added to info api because of several add requests at the same time (what happened there?) instead of being added on re try add request theycontinue to fail to be added and moreover Loop Update is triggered and they continually fail on update loop .
Maybe add re try loop to lifetime managers from http client and replace recursive call with for loop with additional logging for this issue to better track it?