Skip to content

Updates from other forks#1

Draft
BatmanAoD wants to merge 26 commits intomasterfrom
main
Draft

Updates from other forks#1
BatmanAoD wants to merge 26 commits intomasterfrom
main

Conversation

@BatmanAoD
Copy link
Copy Markdown

See upstream_commit_recommendations.txt, written by Claude Haiku 4.5. Claude then created a merge request with the described commit chain and manual changes.

I selected the name rigetti-hyper-proxy for the crate.

The final commit, "do a few more dependency updates," is from simply running cargo upgrade -i. (The "upgrade" command comes from cargo-edit.)

Rather than merging this, we should simply switch the default branch to main once we're satisfied that this looks correct.

@BatmanAoD
Copy link
Copy Markdown
Author

We should also delete this fork: https://github.com/rigetti/hyper-proxy2

override: true
- uses: katyo/publish-crates@v2
with:
registry-token: ${{ secrets.CRATES_IO_SECRET }} No newline at end of file
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Collaborator

@jselig-rigetti jselig-rigetti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Once tests are passing, this looks reasonable

Comment thread Cargo.toml
authors = ["Johann Tuffe <tafia973@gmail.com>"]
name = "rigetti-hyper-proxy"
version = "1.1.1"
authors = ["MetalBear Tech LTD <hi@metalbear.co>"]
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should probably change this, just in case people use this email to ask for support?

Comment thread Cargo.toml
repository = "https://github.com/tafia/hyper-proxy"

documentation = "https://docs.rs/rigetti-hyper-proxy"
repository = "https://github.com/metalbear-co/hyper-http-proxy"
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same thing with this

Comment thread README.md
[![Checks](https://github.com/metalbear-co/hyper-http-proxy/actions/workflows/checks.yaml/badge.svg)](https://github.com/metalbear-co/hyper-http-proxy/actions/workflows/checks.yaml)
[![MIT licensed](https://img.shields.io/github/license/metalbear-co/hyper-http-proxy)](./LICENSE-MIT.md)
[![crates.io](https://img.shields.io/crates/v/rigetti-hyper-proxy)](https://crates.io/crates/rigetti-hyper-proxy)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should probably change these references too

Comment thread LICENSE-MIT.md

Copyright (c) 2017 Johann Tuffe
Copyright (c) 2024 Natsuki Ikeguchi
Copyright (c) 2024 MetalBear Tech LTD
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we append ourselves to this..?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes

Comment thread src/stream.rs
.get_ref()
.get_ref()
.get_ref()
.inner()
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

now that's what I call nested

@jselig-rigetti
Copy link
Copy Markdown
Collaborator

We should also delete this fork: https://github.com/rigetti/hyper-proxy2

@BatmanAoD Ok, I've archived it

@rigetti rigetti deleted a comment from BatmanAoD Apr 17, 2026
Comment thread LICENSE-MIT.md

Copyright (c) 2017 Johann Tuffe
Copyright (c) 2024 Natsuki Ikeguchi
Copyright (c) 2024 MetalBear Tech LTD
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add us here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants