Use a retry counter/limit to fetch thumbnails. #7618

Merged
Ruk33 merged 1 commit from 7617-some-channel-thumbnails-can-trigger-a-large-number-of-requests-to-fetch-thumbnail into master 2022-06-28 17:25:21 +02:00
Ruk33 commented 2022-06-20 17:30:24 +02:00 (Migrated from github.com)

Fixes

Issue Number: https://github.com/lbryio/lbry-desktop/issues/7617

What is the current behavior?

Some channels can trigger many network requests in order to fetch
the channel's thumbnail.

What is the new behavior?

A limit of retries (3 in this case) is set to prevent multiple requests.
If the image couldn't be fetched after those retries, the default picture
will be used instead.

Other information

PR Checklist

Toggle...

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting)
  • Refactoring (no functional changes)
  • Documentation changes
  • Other - Please describe:

Please check all that apply to this PR using "x":

  • I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
  • I added a line describing my change to CHANGELOG.md
  • I have checked that this PR does not introduce a breaking change
  • This PR introduces breaking changes and I have provided a detailed explanation below
## Fixes Issue Number: https://github.com/lbryio/lbry-desktop/issues/7617 <!-- Tip: - Add keywords to directly close the Issue when the PR is merged. - Skip the keyword if the Issue contains multiple items. - https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword --> ## What is the current behavior? Some channels can trigger many network requests in order to fetch the channel's thumbnail. ## What is the new behavior? A limit of retries (3 in this case) is set to prevent multiple requests. If the image couldn't be fetched after those retries, the default picture will be used instead. ## Other information <!-- If this PR contains a breaking change, please describe the impact and solution strategy for existing applications below. --> ## PR Checklist <!-- For the checkbox formatting to work properly, make sure there are no spaces on either side of the "x" --> <details><summary>Toggle...</summary> What kind of change does this PR introduce? - [x] Bugfix - [ ] Feature - [ ] Code style update (formatting) - [ ] Refactoring (no functional changes) - [ ] Documentation changes - [ ] Other - Please describe: Please check all that apply to this PR using "x": - [x] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged) - [ ] I added a line describing my change to CHANGELOG.md - [x] I have checked that this PR does not introduce a breaking change - [ ] This PR introduces breaking changes and I have provided a detailed explanation below </details>
jessopb (Migrated from github.com) reviewed 2022-06-20 17:30:24 +02:00
jessopb commented 2022-06-22 20:56:20 +02:00 (Migrated from github.com)

will look at today

will look at today
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-desktop#7618
No description provided.