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

Event API caches old result after setting an event to draft #2197

Closed
timobrembeck opened this issue Apr 4, 2023 · 0 comments · Fixed by #2215
Closed

Event API caches old result after setting an event to draft #2197

timobrembeck opened this issue Apr 4, 2023 · 0 comments · Fixed by #2215
Assignees
Labels
‼️ prio: high Needs to be resolved ASAP. 🐛 bug Something isn't working ☺️ effort: low Should be doable in <4h
Milestone

Comments

@timobrembeck
Copy link
Member

Describe the Bug

Events are still delivered via the events API when the result is cached via django-cachalot.

Steps to Reproduce

  1. Enable redis cache
  2. Fetch events API to populate cache
  3. Set event to draft
  4. Fetch events API again

Expected Behavior

An event that is set to draft should not be delivered via the API

Actual Behavior

The event is still delivered when the result is cached and not manually invalidated

Additional Information

@timobrembeck timobrembeck added 🐛 bug Something isn't working ‼️ prio: high Needs to be resolved ASAP. ☺️ effort: low Should be doable in <4h labels Apr 4, 2023
@timobrembeck timobrembeck added this to the 23Q2 milestone Apr 4, 2023
@timobrembeck timobrembeck self-assigned this Apr 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
‼️ prio: high Needs to be resolved ASAP. 🐛 bug Something isn't working ☺️ effort: low Should be doable in <4h
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant