feat: corrupt data check

[jim3ma]

Signed-off-by: Jim Ma majinjing3@gmail.com

Description

Related Issue

Motivation and Context

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation Update (if none of the other choices apply)

Checklist

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.

[codecov-commenter]

Codecov Report

Merging #1946 (e0f2348) into main (92b01f0) will decrease coverage by 0.04%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #1946      +/-   ##
==========================================
- Coverage   42.79%   42.74%   -0.05%     
==========================================
  Files         133      133              
  Lines       16702    16731      +29     
==========================================
+ Hits         7147     7152       +5     
- Misses       9008     9032      +24     
  Partials      547      547              

Flag	Coverage Δ
Object-compatibility-e2etests	?
e2etests	?
unittests	42.74% <0.00%> (-0.05%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
client/daemon/peer/peertask_conductor.go	52.69% <0.00%> (-0.72%)	⬇️
client/daemon/rpcserver/rpcserver.go	49.14% <0.00%> (-1.00%)	⬇️
client/daemon/peer/piece_manager.go	53.40% <0.00%> (+0.40%)	⬆️
...ent/daemon/peer/peertask_piecetask_synchronizer.go	48.37% <0.00%> (+0.97%)	⬆️

[gaius-qi]

LGTM