-
Notifications
You must be signed in to change notification settings - Fork 648
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
Endpoints containing sagas fail to start when a scanned assembly contains a ref struct #7179
Comments
it is a side effect of
it doesn't seem to respect the message convention. so if u have any type in that assembly that conflicts with a type constraint it will blow up. |
stack:
|
@boblangley what was the outcome of the Triage? |
We ranked it as a priority bug, but not critical. This means we have queued it for work with the other priority bugs and a team will take this on when one becomes available to work on it. I don't have an ETA, the team should say something on this issue when they start working on it. |
Thanks @SimonCropp we are working on a fix for this #7187 |
@andreasohlund thanks |
@SimonCropp we're doing some more testing but if you want to play with 9.2.3 in advance to verify that you issue is solved you can get it here https://feedz.io/org/particular-software/repository/packages/packages/NServiceBus/9.2.3 |
This has now been released, thanks for the detailed bug report @SimonCropp |
@andreasohlund @boblangley thanks peeps |
Symptoms
Endpoints fail to start and a
System.TypeLoadException
is logged indicating that aref struct
type violates the constraint of a type parameter.Who's affected
You are affected if you have endpoints containing sagas and a scanned assembly contains a
ref struct
.Root cause
Checking whether a type is a saga timeout does not consider that
ref struct
is not valid as generic type arguments.Original Bug Report
Since MakeGenericType is used without checking if the type constraints are met
Steps to reproduce
Have a Ref struct in message scanning
NSB 9.2.2.0
.net: 8
Backported to
The text was updated successfully, but these errors were encountered: