Skip to content

adjust cache signal receiver to work with both sync and async backends #28

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
Merged
merged 10 commits into from
Jul 27, 2025
Merged

adjust cache signal receiver to work with both sync and async backends #28

merged 10 commits into from
Jul 27, 2025

Conversation

amirreza8002
Copy link
Member

this is a sub-pr from #24

this PR aims to add experimental signal receiver that works in both sync and async backends

@amirreza8002 amirreza8002 changed the title adjust cache signal receiver to work in async context adjust cache signal receiver to work with bothsync and async backends Jun 10, 2025
@amirreza8002 amirreza8002 added the bug Something isn't working label Jun 10, 2025
@amirreza8002 amirreza8002 changed the title adjust cache signal receiver to work with bothsync and async backends adjust cache signal receiver to work with both sync and async backends Jun 10, 2025
@amirreza8002
Copy link
Member Author

  1. add a signal receiver and hook it in
  2. uninstall django's receiver
  3. migrate to anyio instead of pytest-async for testing
  4. adjust some async test

@amirreza8002 amirreza8002 merged commit e36888b into django-commons:main Jul 27, 2025
38 of 39 checks passed
@amirreza8002 amirreza8002 deleted the async_fix branch July 27, 2025 21:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@amirreza8002