Skip to content

ASF-ui should cache GitHub releases #1624

Open
@JustArchi

Description

Checklist

  • I read and understood ASF-ui's Contributing Guidelines
  • I also read FAQ
  • My idea doesn't duplicate existing ASF-ui functionality described on the wiki
  • I believe that my idea falls into ASF-ui's scope and should be offered as part of ASF-ui built-in functionality
  • This is not ASF suggestion

Enhancement purpose

As a third-party service, GitHub has various rate-limits in regards to fetching its resources. We should use cache for all third-party resources that ASF can't fulfill on its own. The caching doesn't have to be excessive, could be even 5 minutes, but lack of any caching can lead to users rate-limiting themselves accidentally purely by navigating across ASF-ui from one tab to another.

Solution

All /api/www/github endpoints should be carefully evaluated and cached. I'm pretty sure the functionality that checks for ASF updates already uses the cache, same mechanism should be used for Releases tab, which from my fast network tab check, always fetches info on each refresh.

Why currently available solutions are not sufficient?

obraz

Can you help us with this enhancement idea?

Somehow, I can test and offer feedback, but can't code

Additional info

/cc @MrBurrBurr

Metadata

Assignees

Labels

✨ EnhancementIssues marked with this label indicate further enhancements to the program, such as new features.👍 PR-okIssues marked with this label are good candidates for being accepted in a pull request.🟢 Low priorityIssues marked with this label are actively being worked on if nothing serious is on the list.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions