sbp commented on issue #639: URL: https://github.com/apache/tooling-trusted-releases/issues/639#issuecomment-3879094273
In fact, we probably do not need to store hashes in the database because there are only a few cases where resolving the conflict depends on knowing the hashes. We need to distinguish between case 10 and case 13 when the inodes differ (if the inodes are the same, we know it's case 10; if the inodes differ, we don't know which case it is). And when all three files are present and all inodes differ, we can't distinguish between cases 4, 5, 8, and 15 on the one hand and 11 on the other. Since these are limited cases, occurring per file, in a situation where there's a rare conflict, I think it's sufficient to look up the relevant hashes from the attestable JSON data. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
