BadFormatImageException while performing Query

[Michael Kolback]

Describe the bug
I'm attempting to create a List of queries to be performed and the Tasks are faulting before execution.

Expected behavior
The query is supposed to find two vertices of the same type via equality expressions, determine whether they are adjacent, and if not create an edge.

Version information
8.0.0
Minimal working example

        {
            await _g
                .V(sourceVertex.Id)
                .Out()
                .OfType<T>()
                .Where(equalityExpression1)
                .As((__, nodeSetTrigger) => __
                    .V(sourceVertex.Id)
                    .Out()
                    .OfType<T>()
                    .Where(equalityExpression2)
                    .Coalesce(
                        (q) => q.InE<U>().Where(__ => __.OutV().OfType<T>().Where(x => x == nodeSetTrigger)),
                        (q) => q.AddE<U>(edgeObject).From(nodeSetTrigger).ForceInEdge<T>()
                    )
                )
.FirstOrDefaultAsync()
        }

Exception has occurred: CLR/System.BadImageFormatException
An exception of type 'System.BadImageFormatException' occurred in System.Private.CoreLib.dll but was not handled in user code: 'An attempt was made to load a program with an incorrect format. (0x8007000B)'

Additional context
Add any other context about the problem here.

[label-actions]

Hello @mike-kolback,

thanks for your interest in ExRam.Gremlinq. The issue was labelled "Repro repository missing" because although the issue template asks for either "a link to GitHub repository containing a minimal executable project structure that exposes the unexpected behaviour" or "a pull request to ExRam.Gremlinq that adds a failing unit test to the ExRam.Gremlinq tests asserting the expected behaviour", it seems you provided neither. Most problems already solve themselves when isolated and if they don't, you will have made it easier for the maintainer of this project to investigate a possible bug.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.