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

Revert "feat: use DuplexStream instead of UnixStream to communicate with workers #326

Merged
merged 1 commit into from
Apr 22, 2024

Conversation

nyannyacha
Copy link
Collaborator

This reverts commit 4e53e2ade212bce63f474b3f917d60683121db6f.

# Conflicts:
#	crates/base/src/server.rs
#	crates/cli/src/main.rs

What kind of change does this PR introduce?

Revert commit

Description

An unexpected pipe closure behavior for DuplexStream that differed from UnixStream caused a regression in connection lifetime tracking behavior.

Revert the change until this issue is resolved.

…te with workers (supabase#320)"

This reverts commit 4e53e2a.

# Conflicts:
#	crates/base/src/server.rs
#	crates/cli/src/main.rs
@laktek
Copy link
Contributor

laktek commented Apr 22, 2024

Will have to prefix the revert commit as a feat to generate a minor version release

@nyannyacha nyannyacha changed the title Revert "feat: use DuplexStream instead of UnixStream to communicate with workers feat: Revert "feat: use DuplexStream instead of UnixStream to communicate with workers Apr 22, 2024
@nyannyacha nyannyacha merged commit 31986d1 into supabase:main Apr 22, 2024
3 checks passed
@nyannyacha nyannyacha changed the title feat: Revert "feat: use DuplexStream instead of UnixStream to communicate with workers Revert "feat: use DuplexStream instead of UnixStream to communicate with workers Apr 22, 2024
@nyannyacha nyannyacha deleted the revert-perf-req branch April 22, 2024 23:24
Copy link

🎉 This PR is included in version 1.46.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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.

None yet

2 participants