-
Notifications
You must be signed in to change notification settings - Fork 2.1k
[forward_port] Verify checksums command #31082
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #31082 +/- ##
============================================
+ Coverage 62.47% 62.5% +0.03%
- Complexity 18237 18268 +31
============================================
Files 1145 1146 +1
Lines 68313 68397 +84
Branches 1234 1234
============================================
+ Hits 42678 42753 +75
- Misses 25274 25283 +9
Partials 361 361
Continue to review full report at Codecov.
|
PVince81
left a comment
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.
👍
| return rtrim($checksumString); | ||
| } | ||
|
|
||
| public function testFilePutContentsClearsChecksum() { |
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.
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.
The checksum must not be cleared anymore, the checksum wrapper recalculates the new checksum on file_put_contents. The above tests is from the old checksum impl. where the client just sent some checksum and it got written to the db without any checks.
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.
Checksums are also covered by acceptance tests:
| Feature: checksums |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Forward port of #31008