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.

Sign up for GitHub

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

Jump to bottom

searching "furry" 504s and loads forever #180

Closed
advaith1 opened this issue Nov 11, 2020 · 7 comments
Closed

searching "furry" 504s and loads forever #180

advaith1 opened this issue Nov 11, 2020 · 7 comments
Assignees
@IceeMC @carolinaisslaying
Labels
bug Issue/PR related to an error, fault, or flaw. low priority Issue/PR is low priority.

Comments

@advaith1
Copy link
Member

image
@advaith1 advaith1 added the bug Issue/PR related to an error, fault, or flaw. label Nov 11, 2020
@advaith1 advaith1 added the moderate priority Issue/PR is moderate priority. label Nov 11, 2020
@carolinaisslaying
Copy link
Member

tf

@IceeMC
Copy link
Member

IceeMC commented Dec 24, 2020

im hurt deeply

@advaith1
Copy link
Member Author

also happens with "anime" and probably other queries

@carolinaisslaying carolinaisslaying added low priority Issue/PR is low priority. and removed moderate priority Issue/PR is moderate priority. labels Feb 8, 2022
@TheAlienKnight
Copy link
Contributor

So, the issue is that servers, aren't cached on startup, or on search. They are only cached on edit, submission, and autosync. It is why on the production site you can currently only find 1 page of server listings.

It took me a while to wrap my head around why results weren't showing up, and it seemed inconsistent depending on what selectors you chose. Bots, templates, and users, are cached. Servers are not, leading to a generally empty dataset that breaks the query and seems to cause an error.

I'll see what I can come up with as far as a solution goes and make a PR in connection to this issue!

@TheAlienKnight
Copy link
Contributor

I went ahead and added this to the current open PR since it's a small fix/change, I referenced the full, actual cause here TheAlienKnight#10

@carolinaisslaying
Copy link
Member

@TheAlienKnight Is this resolved

@carolinaisslaying
Copy link
Member

pretty sure this is resolved

@github-project-automation github-project-automation bot moved this to Closed / Merged in Triage Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@IceeMC IceeMC

@carolinaisslaying carolinaisslaying

Labels
bug Issue/PR related to an error, fault, or flaw. low priority Issue/PR is low priority.
Projects
Triage
Status: Closed / Merged
Milestone
No milestone
Development

No branches or pull requests
4 participants
@advaith1 @IceeMC @carolinaisslaying @TheAlienKnight