-
Notifications
You must be signed in to change notification settings - Fork 533
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
Add architecture info to the 0141 warning #9547
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have the full path to the .so
file? It seems like we could simply put that in the error message and that's it?
If it's from a NuGet package, you will know what package and version from the file path.
I considered that, but I figured most people won't find it actionable anyway. They most likely don't maintain the nuget, |
The full path to the file is more informative than |
log.LogCodedWarning ("XA0141", Properties.Resources.XA0141, packageId, packageVersion, Path.GetFileName (path)); | ||
log.LogCodedWarning ("XA0141", Properties.Resources.XA0141, packageId, packageVersion, Path.GetFileName (path), archName); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we use the overload for LogCodedWarning
where you pass the file path in, and put 0 for line number:
This would include the file, and if you double-clicked the error in an IDE it would open the file.
It is, but it also potentially leaks information about the user's environment, if shared (operating system, user login name), since it's going to be in the nuget cache. |
8aa5ef7
to
e2ad080
Compare
Can we also update the verbiage to be less scary:
|
@jpobst we can change the wording, but there's no "may" about it - they will require that alignment. |
e2ad080
to
30b9c13
Compare
Linux build fails with
@pjcollins @jonathanpeppers any idea what might be causing it? |
This is a weird issue where the source in the target branch appears to have been updated between when the mac build ran and the linux build ran -- we have packages on the PR with different versions: Did the linux build initially fail and re-run? I think we'll need to just kick off a new build |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
This failing check will continue to show on the PR from the old build since we're rebuilding the same commit, and it can be ignored in favor of the new build:
|
Yep, I restarted it two times I think. Let's hope it works fine now, thanks for looking into it :) |
Partial fix for #9544 to make the warning more informative. Architecture information is necessary as the nuget in question might have the same library for various architectures.
30b9c13
to
1fab20c
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Partial fix for #9544 to make
the warning more informative. Architecture information is necessary as
the nuget in question might have the same library for various
architectures.