Uh oh!
There was an error while loading. Please reload this page.
Add architecture info to the 0141 warning - #9547
Conversation
jonathanpeppers
left a comment
There was a problem hiding this comment.
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.
grendello
commented
Nov 22, 2024
I considered that, but I figured most people won't find it actionable anyway. They most likely don't maintain the nuget, |
jonathanpeppers
commented
Nov 22, 2024
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.
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.
grendello
commented
Nov 22, 2024
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
e2ad080Comparejpobst
commented
Nov 22, 2024
Can we also update the verbiage to be less scary: |
grendello
commented
Nov 22, 2024
@jpobst we can change the wording, but there's no "may" about it - they will require that alignment. |
e2ad080 to
30b9c13Comparegrendello
commented
Nov 25, 2024
Linux build fails with @pjcollins@jonathanpeppers any idea what might be causing it? |
pjcollins
commented
Nov 25, 2024
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 |
pjcollins
commented
Nov 25, 2024
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
pjcollins
commented
Nov 25, 2024
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:
|
grendello
commented
Nov 25, 2024
Yep, I restarted it two times I think. Let's hope it works fine now, thanks for looking into it :) |
30b9c13 to
1fab20cComparegrendello
commented
Nov 28, 2024
/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.
1fab20c to
c60b54aCompare| </data> | ||
| <data name="XA0141" xml:space="preserve"> | ||
| <value>NuGet package '{0}' version '{1}' contains a shared library '{2}' which is not correctly aligned. See https://developer.android.com/guide/practices/page-sizes for more details</value> | ||
| <value>NuGet package '{0}' version '{1}' contains a shared library '{2}' ({3}) which is not aligned to the {4} byte boundary. Google will require such alignment in the future. See https://developer.android.com/guide/practices/page-sizes for more details</value> |
There was a problem hiding this comment.
This is going to clash with https://github.com/dotnet/android/pull/9559/files#diff-4fb7800ecd2e6254dea359880760d5145fe7d214c9cd45935f897b6f6d0d47daR1066.
@jonpryor we need to figure out the wording we want.
grendello
commented
Jan 13, 2025
Superseded by #9559 |

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.