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

[PROPOSAL] Fix Slower Results Display #286

Closed
9 tasks
thealphadollar opened this issue Jun 3, 2019 · 0 comments · Fixed by #311
Closed
9 tasks

[PROPOSAL] Fix Slower Results Display #286

thealphadollar opened this issue Jun 3, 2019 · 0 comments · Fixed by #311
Assignees

Comments

@thealphadollar
Copy link
Contributor

Please prefix your issue with one of the following: [BUG], [PROPOSAL], [QUESTION].

Sample platform commit (found at the bottom of each page) : X.X.X

In raising this issue, I confirm the following (please check boxes, eg [X]):

  • I have read and understood the contributors guide.
  • I have checked that the bug-fix I am reporting can be replicated, or that the feature I am suggesting isn't already present.
  • I have checked that the issue I'm posting isn't already reported.
  • I have checked that the issue I'm posting isn't already solved and no duplicates exist in closed issues and in opened issues
  • I have checked the pull requests tab for existing solutions/implementations to my issue/suggestion.

My familiarity with the project is as follows (check one, eg [X]):

  • I have never visited/used the platform.
  • I have used the platform just a couple of times.
  • I have used the platform extensively, but have not contributed previously.
  • I am an active contributor to the platform.

The result page currently is based on an old style which leads to multiple slower
operations. One such example is the display of the below failed test result from
test#2087.

The following changes are required to resolve the issues:

  • Send only first 50 headlines of change if larger than 50.
  • Provide option to download entire diff as txt.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant