New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error updating to MongoDb latest driver version and Elsa 2.11 #4000
Comments
alkampfergit
added a commit
to alkampfergit/elsa-core
that referenced
this issue
May 4, 2023
Added an option to allow the user to opt-in for LINQ3 provider that actually causes regressions. See elsa-workflows#4000
alkampfergit
added a commit
to alkampfergit/elsa-core
that referenced
this issue
May 4, 2023
Added an option to allow the user to opt-in for LINQ3 provider that actually causes regressions. See elsa-workflows#4000
Actually there is probably a bug in the new mongodb driver that does not allow registring own ObjectSerializer, because in the LINQ3 provider (LINQ2 is fine) there is an hard cast to MongoDb driver own implementation of ObjectSerializer, I've opened a bug in mongo C# library. |
alkampfergit
added a commit
to alkampfergit/elsa-core
that referenced
this issue
May 9, 2023
Added an option to allow the user to opt-in for LINQ3 provider that actually causes regressions. See elsa-workflows#4000
It looks like this is the same issue as #3975. I'll close the other one since you provided a PR associated with this issue. |
sfmskywalker
pushed a commit
that referenced
this issue
May 11, 2023
Added an option to allow the user to opt-in for LINQ3 provider that actually causes regressions. See #4000
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Upgrading to latest mongodb driver required by Elsa 2.11 we have problem due to the new LINQ3 provider of 2.19 version of MongoDB C# drivers that is causing serious regressions in the provider. See here to view one of the complaint
Due to this bug actually elsa persistence layer does not work anymore throwing exceptions.
Actually to solve the problem we need to let the user to choose to default to old LINQ2 provider and migrate to LINQ3 provider once it will be stable.
The text was updated successfully, but these errors were encountered: