-
Notifications
You must be signed in to change notification settings - Fork 765
feature: store piece md5s with native bytes #616
Conversation
Codecov Report
@@ Coverage Diff @@
## master #616 +/- ##
==========================================
+ Coverage 46.07% 46.14% +0.06%
==========================================
Files 99 99
Lines 5853 5843 -10
==========================================
- Hits 2697 2696 -1
+ Misses 2930 2924 -6
+ Partials 226 223 -3
Continue to review full report at Codecov.
|
| pieceMD5s = strings.Split(string(bytes), "\n") | ||
|
|
||
| for _, v := range pieceMD5s { | ||
| logrus.Infof("success to read piece md5 file: %s", v) |
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.
It's better to log this one line with taskId on debug level.
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.
In fact, they are some code for test. So sorry for that. I have deleted them. 😢
Signed-off-by: Starnop <[email protected]>
lowzj
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.
LGTM
feature: store piece md5s with native bytes
feature: store piece md5s with native bytes
Signed-off-by: Starnop [email protected]
Ⅰ. Describe what this PR did
We store the piece md5s with json.Marsal(slice), and we will get piece md5 files like this
It's unfriendly to read and most importantly, it's not compatible with the Java version which looks like this
So I update the way to store the piece md5s.
Ⅱ. Does this pull request fix one issue?
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗?)
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews