chore: rename pegainfer → openinfer across the workspace#318
Merged
Conversation
Project renamed pegainfer -> openinfer; repo is now openinfer-project/openinfer. Mechanical rename across all four case forms: pegainfer -> openinfer (crate names, dirs, Rust paths, docs) PEGAINFER -> OPENINFER (env vars: build + CLI + CI) PegaInfer -> OpenInfer (prose / CamelCase) Pegainfer -> Openinfer 32 crate dirs renamed (17 top-level + 15 openinfer-comm subcrates), 2 doc files, ~555 files total. The external KV-offload dep `pegaflow` is left untouched. The server binary is now `openinfer`. Verified: `cargo build --release` green; core/kernels/kv/model/server lib tests pass. (The GDR test in openinfer-comm fails only for lack of RDMA hardware on this box — a pre-existing hardware gate, unrelated to the rename.) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
`pegainfer_*` (p-e) and `openinfer_*` (o) sort to different alphabetical positions, so the rename left two `use` blocks mis-ordered. `cargo fmt --all` re-sorts them; build/behavior unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Rebrand pegainfer → openinfer following the repo move to
openinfer-project/openinfer.What changed
Mechanical rename across all four case forms (each is exactly 9 chars, so formatting is byte-stable — zero alignment churn):
pegainferopeninferPEGAINFEROPENINFERPegaInferOpenInferPegainferOpeninferopeninfer-core,openinfer-kernels,openinfer-qwen3-4b,openinfer-kimi-k2,openinfer-server, …) + 15openinfer-commsubcrates.openinfer.pegaflowis untouched (verified: 90 occurrences intact, 0 cross-contamination).PEGAINFER_*→OPENINFER_*(hard rename, no aliases). Build now readsOPENINFER_TRITON_PYTHON, testsOPENINFER_TEST_MODEL_PATH, etc.Verification
cargo build --release— green (1m06s, all crates compile asopeninfer-*).cargo metadata— 40 packages, none stillpegainfer, dep graph self-consistent.openinfer-commGDRgdr_copy_flag_GPU) is a pre-existing RDMA-hardware gate unrelated to the rename (no GDR hardware on this box).Note
A workspace-wide rename conflicts with every open branch. The other open PRs (#315/#304/#299/#202) will need a rebase after this merges.
🤖 Generated with Claude Code