Was the repeat-invocation of CustomizeGlobalDependencies fixed?

[craigfowler]

Unfortunately this relates to an old issue from the SpecFlow repository. Since the owners decided to remove it, all the old issues and the history of those issues went with it😭.

In a project of my own, a SpecFlow plugin which I'm now upgrading to work with Reqnroll, I have a "note to myself" in that plugin which looks like this (specifically the remarks):

/// <summary>
/// Event handler for the <c>CustomizeGlobalDependencies</c> runtime plugin event.
/// </summary>
/// <remarks>
/// <para>
/// It is a known/documented issue that this event may be triggered more than once in a single run of SpecFlow:
/// <see href="https://github.com/techtalk/SpecFlow/issues/948"/>, and by more than one thread.
/// Thus, to prevent double-initialisation, this method occurs in a thread-safe manner which ensures that even if it
/// is executed more than once, there is no adverse consequence.
/// </para>
/// </remarks>
/// <param name="sender">The event sender</param>
/// <param name="args">Event args to customize the global dependencies</param>
void OnCustomizeGlobalDependencies(object sender, CustomizeGlobalDependenciesEventArgs args)
{
    // Impl omitted but it includes that extra thread-safety and avoidance of double-initialisation mentioned above
}

That's on a method which listens to the event RuntimePluginEvents.CustomizeGlobalDependencies, from inside my type which implements IRuntimePlugin.

My question is: Was this issue ever resolved? Is there anybody around who remembers, without having access to the old issues?
Does the issue need to be recreated (still applicable)? I took a look around the Reqnroll issues and other conversations here but couldn't find anything explicitly mentioning it.

Thanks!

[gasparnagy]

I have some vague memories about the issue and I think it has been fixed, but I'm not certain so we need to retest.