Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repeated calls to get Issues #117

Open
vigneshsankariyer1234567890 opened this issue Apr 3, 2023 · 2 comments
Open

Repeated calls to get Issues #117

vigneshsankariyer1234567890 opened this issue Apr 3, 2023 · 2 comments

Comments

@vigneshsankariyer1234567890
Copy link
Contributor

Describe the bug
There are many repeated calls to get Issues from GitHub, as seen in the screenshot. This made sense for CATcher, as it was an application which required real-time data. However, WATcher does not need to refresh the issues every 5 seconds, and users can afford to just view non-updated data.

This makes sense as we want to reduce the number of calls.

image

To Reproduce
Login to WATcher and open network. Issues are polled every 5 seconds using IssueService::startPollIssues.

Desktop (please complete the following information):

  • OS: MacOS Monterey
  • Browser Chrome
@seetohjinwei
Copy link
Contributor

Hi! For this, do we want to just disable the issue polling entirely or reduce the latency to something much longer (maybe 5 minutes)?

@Eclipse-Dominator
Copy link
Contributor

This could be a possible solution, but by the nature of WATcher, it might be better to replace the polling with a manual refresh. (perhaps the a sync button).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants