-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
"dotnet-pgo dump" throws "Same type X
used as both ValueType and non-ValueType"
#61604
Comments
dotnet-issue-labeler
bot
added
area-System.Reflection
untriaged
New issue has not been triaged by the area owner
labels
Nov 15, 2021
Tagging subscribers to this area: @buyaa-n Issue Details
and
@AndyAyersMS @davidwrighton does it ring a bell? I used the latest version of
|
No, not familiar with this one. |
Hmm, I tried to fix this problem in #52963. I wonder why we are seeing it again. |
jeffschwMSFT
removed
the
untriaged
New issue has not been triaged by the area owner
label
Jan 11, 2022
davidwrighton
added a commit
to davidwrighton/runtime
that referenced
this issue
Jun 9, 2023
…ception in those cases
ghost
added
the
in-pr
There is an active PR which will close this issue when it is merged
label
Jun 9, 2023
ghost
removed
the
in-pr
There is an active PR which will close this issue when it is merged
label
Jun 12, 2023
ghost
locked as resolved and limited conversation to collaborators
Jul 13, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
and
@AndyAyersMS @davidwrighton does it ring a bell? I used the latest version of
dotnet-pgo
tool (7.0.*)The text was updated successfully, but these errors were encountered: