Skip to content

Challenge Listing Page: Challenges are not displayed in Past Challenges for some Subtrack and Keyword Filters #2383

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

Closed
nithyaasworld opened this issue May 30, 2019 · 7 comments
Assignees
Labels
Challenge Listing P2 Important (resolve within 3 days)

Comments

@nithyaasworld
Copy link
Collaborator

Describe the bug
Challenges are not displayed in Past Challenges for some Subtrack filters (Example: Bug Hunt, Design)
Similary When Keyword filter is applied in Past Challenges, it displays only half the results and the remaining are displayed like boxes

To Reproduce
Steps to reproduce the behavior:

  1. Go to https://www.topcoder.com/challenges?
  2. Click on Past Challenges
  3. Then apply the filter Subtrack = Bughunt or Design
  4. Check the results
  5. Similary check the results of the filter: Keyword = QA or Python

Expected behavior
All matching challenges should be displayed

Actual behavior

  1. For some of the Subtrack values, it shows nothing on screen. Just the grey boxes are displayed
  2. For Keyword values, it loads only the first few challenges and rest are all displayed as boxes.

Screenshots

image

image

@nithyaasworld
Copy link
Collaborator Author

@sushilshinde Tagging you as I am not able to assign this to you! Please check. Thanks.

@nithyaasworld nithyaasworld added the P3 Normal (resolved within 7 days) label Jun 1, 2019
@nithyaasworld
Copy link
Collaborator Author

As part of this ticket, we should also fix and verify this: #1992

@nithyaasworld nithyaasworld added P2 Important (resolve within 3 days) and removed P3 Normal (resolved within 7 days) labels Jun 5, 2019
@nithyaasworld
Copy link
Collaborator Author

@sushilshinde We have increased the Priority for this from P3 to P2. CC: @ThomasKranitsas

@sushilshinde
Copy link
Collaborator

We will cover this in server-side filtering @nithyaasworld can you log this issue with Performance label on beta if that still exists.

FYI... @ThomasKranitsas

@nithyaasworld
Copy link
Collaborator Author

This exact issue is not present in SSF , but we have a similar one #2391

Priority of this issue has been set to P2 (Resolve in 3 days). Can we get all SSF fixes in 3 days and deploy to production?

Your thoughts please? @sushilshinde

@huangqun
Copy link
Collaborator

Is there going to be a fix for this soon?

@SathyaJayabal
Copy link
Collaborator

This has been fixed in #3610 and #3609

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Challenge Listing P2 Important (resolve within 3 days)
Projects
None yet
Development

No branches or pull requests

5 participants