Python API triggers add events even after refresh promise has resolved

Jupyter extension invokes the refreshEnvironments API method. However even after this promise resolves, we get events being triggered for onDidChangeEnvironments. Meaning the discovery has not been completed.

I.e. once refreshEnvironments, then this means all discovery has been completed, however events being triggered means this is still in progress.

I would not expect any more events to be triggered for onDidChangeEnvironments after the refreshEnvironments promise resolves. Similarly I would not expect any changes to known after this refresh promise.

Exceptions include users creating/removing python environments, however when it comes to refresh the expectation is that this promise should resolve after everything has been completed.

[DonJayamanne]

Damn, sorry, you are right, I can no longer repro this issue, must have been doing something wrong at my end. Apologies for creating this issue.

[karrtikr]

We do have a lot of async code, not sure how that would affect this. With async code the event loop should still handle the callbacks and the resolution of the promise in order.

Each loop starts in order but can yield control in between if callback itself is async, so finish order is not guaranteed. Anyways glad you were able to verify its okay.