prefetch: fix underlying unexpected-eof taken as EOF

[D3Hunter]

What problem does this PR solve?

Issue Number: ref #59495

Problem Summary:

What changed and how does it work?

the underlying reader might also return unexpected-eof, we need different between them, introduced in #59496

• add rangeSize to prefetch.Reader to determine where UnexpectedEOF comes from
• check error equals using goerrors.Is instead of ==. we might add stack to the error to help debug
  • Note: for the implementation of io.Reader, we still follow the API definition to return the io.EOF directly without stack, our byteReader doesn't follow the API of io.Reader, so it's ok to add stack to the error
  • And to unify code, we always use goerrors.Is to check io.EOF even for errors from io.Reader
• avoid retry when context cancel

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)

same test in #50451, before it will fail with unexpected-eof, now success

• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from d3hunter, ensuring that each of them provides their approval before proceeding. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS
• br/pkg/storage/OWNERS
• pkg/lightning/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tiprow]

Hi @D3Hunter. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[D3Hunter]

it prints too many logs when context cancel due to some goroutine in the same group failed, it's not needed, there is no further usefully info in it.

[D3Hunter]

no need to retry on context cancel

[codecov]

Codecov Report

Attention: Patch coverage is 80.59701% with 13 lines in your changes missing coverage. Please review.

Project coverage is 74.6646%. Comparing base (a5d433a) to head (4d4b432).
Report is 13 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #59752        +/-   ##
================================================
+ Coverage   72.9537%   74.6646%   +1.7109%     
================================================
  Files          1697       1743        +46     
  Lines        468912     478514      +9602     
================================================
+ Hits         342089     357281     +15192     
+ Misses       105752      98695      -7057     
- Partials      21071      22538      +1467     

Flag	Coverage Δ
integration	48.8150% <0.0000%> (?)
unit	72.1729% <80.5970%> (+0.0239%)	⬆️

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	61.3519% <50.0000%> (+16.2525%)	⬆️