Hello all 👋🏽

I wish I had more details, but unfortunately I don't have any logs about it.
We recently got an issue in the OTel Demo with the user reporting that the Load-Generator wasn't producing load.

I went through all updates and all dependencies bump and got down to openfeature-provider-flagd as the culprit.

There is something going on with the update from 0.1.5 to 0.2.0, BUT just for the load-generator.

We have 2 Python services in the Demo:

• Recommendation
• Load-Generator

Recommendation uses OTel auto-instrumentation and Load-Generator uses OTel instrumentation libraries.

Here are the steps to reproduce:

• Pull the Demo as is
• build the load-generator (docker compose build load-generator)
• run the demo (make start)
• access Jaeger: http://localhost:8080/jaeger/ui
• refresh the page a couple of times, while the load-generator is producing traffic and spans are arriving at Jaeger. (You should see 19 services)

Now, stop the Demo: make stop.

• Update openfeature-provider-flagd to 0.2.0.
• build the new load-generator (docker compose build load-generator)
• run the demo (make start)
• access Jaeger: http://localhost:8080/jaeger/ui
• refresh the page a couple of times, while the load-generator SHOULD be producing traffic.
• You will get the max of 5 services, as load-generator is not sending any load.

NOTE that recommendation is on version 0.2.0 and working fine, so this seems to be some race condition or call order in the load-generator service.