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

feat: Switch from wsgi to asgi (attempt 3) #21579

Merged
merged 6 commits into from
Apr 17, 2024
Merged

feat: Switch from wsgi to asgi (attempt 3) #21579

merged 6 commits into from
Apr 17, 2024

Conversation

frankh
Copy link
Contributor

@frankh frankh commented Apr 16, 2024

Problem

See: #21334
See: #21572

I have a good feeling about this time :)

Changes

👉 Stay up-to-date with PostHog coding conventions for a smoother review.

Does this work well for both Cloud and self-hosted?

How did you test this code?

Canary deploy! 🐤

frankh added 4 commits April 16, 2024 14:32
By default I don't believe this will change anything (everything runs
sync by default), but it will allow us to wrap e.g. clickhouse calls in
sync_to_async wrappers to stop them blocking for ages
This was relying on wsgi_environ which is replaced by asgi_scope
@frankh frankh added the canary label Apr 16, 2024
@neilkakkar
Copy link
Contributor

make sure to fix the lint failures! (missed in the previous one 😅 )

@frankh frankh merged commit 2c0dc75 into master Apr 17, 2024
96 of 97 checks passed
@frankh frankh deleted the frank/asgi branch April 17, 2024 10:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants