[fix] tracking whether transition has started

[almogtavor]

Tests

• Run the tests with npm test and lint the project with npm run lint

[benmccann]

Is there an issue in the tracker describing how this manifests or should there be a test for this?

[almogtavor]

No there's no referring issue

[benmccann]

Can you give some more details? The current code is clearly broken, but how do you trigger this and what's the symptom? E.g. I'm wondering if it's better to fix started as you're doing here or just remove it if it's unused and has no effect

[almogtavor]

Well I think it's pretty hard to trigger such thing. The symptom isn't too harmful - just potentially calling the go function redundantly, because it has been already called. I don't think there's a reason to delete this function since it can hurt transition's internal functionalities, which seems pretty fine.

[almogtavor]

@benmccann what do you think?

[benmccann]

Can you add a test that fails without the change?

[Conduitry]

This has been released in 3.40.2.