Skip to content
This repository has been archived by the owner on Jan 6, 2023. It is now read-only.

Cache invalidation problem #891

Closed
okayawright opened this issue Apr 15, 2019 · 0 comments · Fixed by #892
Closed

Cache invalidation problem #891

okayawright opened this issue Apr 15, 2019 · 0 comments · Fixed by #892
Labels
bug Something isn't working
Projects

Comments

@okayawright
Copy link
Contributor

okayawright commented Apr 15, 2019

Some cached data are sent back from the API whereas they should have been invalidated

Bug Report

Steps to Reproduce

  1. Activate the cache on the API (e.g. through memcache or apcu)
  2. Create a collection through the APP or API
  3. Retrieve at least once the content of this collection through the APP or API
  4. Add a new entry to this collection through the APP or API and save it
  5. Retrieve the collection content once again through the APP or API and observe the data sent back

Expected Behavior

The new entry must appear in the collection content

Actual Behavior

This entry is not visible

Other Context & Screenshots

The cache is not invalidated after performing some important actions, the fresh collection data is not always sent back from the API

Technical Details

latest master

@benhaynes benhaynes added the bug Something isn't working label Apr 15, 2019
@benhaynes benhaynes added this to Needs triage in Bug Triage via automation Apr 15, 2019
@hemratna hemratna moved this from Needs triage to Medium priority in Bug Triage Apr 16, 2019
Bug Triage automation moved this from Medium priority to Closed Apr 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
Bug Triage
  
Closed
Development

Successfully merging a pull request may close this issue.

2 participants