feat(core): cyper transport - #8042
Open
George-Miao wants to merge 2 commits into
Open
Conversation
George-Miao
force-pushed
the
feat/cyper-transport
branch
from
August 9, 2026 11:16
8ceca43 to
177ad0f
Compare
2 tasks
Member
|
Should this PR use #8038 as base? It's hard to check the diff. |
Contributor
Author
I don't think that's possible since that branch is on my forked repo. Target has to be a branch on the main repo. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Part of #8039, stacked on #8038.
Rationale for this change
Reqwest is not compatible with compio, we need cyper as the http transport layer.
What changes are included in this PR?
Added
opendal-http-transport-cyper.Are there any user-facing changes?
New transport crate & feature is added.
AI Usage Statement
I used codex's gpt-5.6-sol to brainstorm & implement part of the PR. I have thoroughly reviewed the change and fixed any issue I found before submitting this PR.