Invalidation of cache not working

[GerardPaligot]

In advance, I'm sorry if it isn't the right place for this issue but I didn't find any IRC or mailing list to post my question/issue.

I use drf-extensions on an open-source project where we have private messages. Our API covers these private messages and we have specified a timeout of 15 minutes on our API.

Unfortunately, drf-extensions don't seem to invalidate the cache. If I create a message in a private message and request the list of messages, the cache is always activated and the system doesn't return the new message in the list.

[auvipy]

#119 same as this issue?

[chibisov]

Hi, could you show your view, route and settings source? If it's open source could you provide a link to it?

[GerardPaligot]

The open-source project is this one: https://github.com/zestedesavoir/zds-site. It is a french project. Documentation, issues and pull requests are in french but the code is in english.

You have a module for private message here with its api here. You can see all keys of the cache in the views.py file and its usage in views below in the file.

Maybe, we made something wrong to invalidate the cache?

[auvipy]

Try updating to drf 3.3.2

[GerardPaligot]

We are working on the migration to Django 1.9 and with that, the update to 3.3.2 for DRF.

As soon as it is done, I'll let you know here.

[auvipy]

ok. I'm also working on supporting 1.9 compat for drf-ext

[GerardPaligot]

Well, my open source project released a new version with Django 1.8, Django Rest Framework 3.3.3 and drf-extensions 0.2.8 but the bug is always present.

When I insert new data, the cache isn't invalidated.I must wait for the end of the cache configured on my view before getting new data.

[egregors]

opened this issue on 24 Dec 2015

I have the same problem. Any progress?