Open szokeasaurusrex opened 7 hours ago
@asottile-sentry I updated the tests per your suggestion. Please let me know whether this looks good now
Tests completed | Failed | Passed | Skipped |
---|---|---|---|
323 | 1 | 322 | 9 |
To view more test analytics, go to the Test Analytics Dashboard Got feedback? Let us know on Github
I have no stake in this particular model / implementation so you may want to get sign off from the actual owners
Agreed, do you know who the owners might be @asottile-sentry? There is no code owner assigned in GitHub, and it doesn't look like this file gets edited very often
I have no stake in this particular model / implementation so you may want to get sign off from the actual owners
Agreed, do you know who the owners might be @asottile-sentry? There is no code owner assigned in GitHub, and it doesn't look like this file gets edited very often
have no idea -- which sdk generates these types of files? that would be my guess having no context (beyond probably reformatting this or fixing the types)
I added @loewenheim and @Swatinem since these files get sent by Sentry CLI, and they were the previous maintainers before I took over. Looks like they have touched the file before
The
detect_dif_from_path
function does not correctly identify Proguard files which are chunk uploaded because these files have a randomly-assigned temporary path, and the logic tries to guess whether the file is a Proguard file based on its path. However, thedetect_dif_from_path
function also takes an optionalname
option, which for chunk-uploaded files, is the file name that is specified by the client making the assemble call. This has not been a problem yet, since Sentry CLI does not support chunk uploading Proguard files, but we are adding support in https://github.com/getsentry/sentry-cli/issues/2196, and so we need to fix the backend to allow chunk uploads of Proguard files.Here, we update the logic to check both the
path
and thename
for potentially matching a Proguard file.