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

16041 16103 uncache #524

Merged
merged 3 commits into from
Feb 4, 2019
Merged

16041 16103 uncache #524

merged 3 commits into from
Feb 4, 2019

Conversation

thatandromeda
Copy link
Contributor

Ready for merge?

YES

What does this PR do?

Fixes overly aggressive caching bugs.

Helpful background context (if appropriate)

There are only two hard things in computer science...

How can a reviewer manually see the effects of these changes?

Perform the behavior in the tickets, except it yields the desired behavior. Make sure that you have caching turned on first and that you've performed at least one search in order to have it cached.

What are the relevant tickets?

Screenshots (if appropriate)

Todo:

  • Tests
  • [ ] Documentation
  • Stakeholder approval

Requires Database Migrations?

NO

Includes new or updated dependencies?

NO

@coveralls
Copy link

Pull Request Test Coverage Report for Build 863

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 83.413%

Totals Coverage Status
Change from base Build 860: 0.0%
Covered Lines: 1750
Relevant Lines: 2098

💛 - Coveralls

@thatandromeda thatandromeda merged commit fa9b978 into dev Feb 4, 2019
@thatandromeda thatandromeda deleted the 16041_16103_uncache branch February 4, 2019 18:16
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 this pull request may close these issues.

None yet

3 participants