Debounce isFetching in the catalog ui

[antgamdia]

Description of the change

• Even if we implement the other mitigations, there are still some edge cases where the state remains inconsistent. For instance, when selecting a repo filter, scrolling down (to trigger pagination), or selecting another repo filter (to unmount the component)... would lead to a request made to the API when the app is in an isFetching=true state.
  • The proposed solution is twofold:
    • Absorb small race conditions with a dummy wait: this will prevent most of the errors to appear, because it will simply retry the request in 1 or 2 seconds. It requires storing a local copy (component's state) of the isFetching global state var.
    • Return an error if a "request_packages" request arrives at the state reducer while in an isFetching=true state. The UI will simply show a "try again" button, and the user can click on it. This check is to ensure no inconsistent data is shown to the user.

Benefits

No more "no data found" because of inconsistent requests coming.

Possible drawbacks

The UI will simply show a "try again" button with an error when the error happens. This check is to ensure no inconsistent data is shown to the user, but still could be seen as a con.

Applicable issues

• related Filter by repo not showing pkgs if exceeding pagination #5165

Additional information

[netlify]

✅ Deploy Preview for kubeapps-dev ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	a1d687e
🔍 Latest deploy log	https://app.netlify.com/sites/kubeapps-dev/deploys/62f37ed650186c0009106f83
😎 Deploy Preview	https://deploy-preview-5188--kubeapps-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.