Bug Report: CI/Docker build failures due to coreason-server crate rename
Problem Description
In commit 2e1bc4c7128773f9f26c51839d8d585156554351, the server crate was renamed from server to coreason-server. However, references to the package name in Dockerfile, .github/workflows/ci.yml, and user documentation files were not updated. As a result, the Docker image builds and GitHub Actions CI workflows are broken.
Affected Files and Lines
-
Dockerfile
- Line 23:
RUN cargo build --release -p server
- Line 37:
COPY --from=builder /usr/src/coreason/target/release/server /usr/local/bin/server
-
.github/workflows/ci.yml
- Line 50:
run: cargo build -p server --target-dir target/llvm-cov-target
- Line 108:
run: cargo build -p server
-
README.md
- Developer instructions using
cargo build --release -p server
-
science/coreason_manifest/README.md
- Developer instructions using
cargo build --release -p server
Error Logs
From Docker/CI logs:
error: package ID specification `server` did not match any packages
help: a package with a similar name exists: `semver`
ERROR: process "/bin/sh -c cargo build --release -p server" did not complete successfully: exit code: 101
How to Confirm/Replicate the Issue
Run either of the following commands:
-
Local Docker Build:
Expected result: Fails during RUN cargo build --release -p server with package matching error.
-
Local Cargo Check:
Expected result: error: package ID specification 'server' did not match any packages
Proposed Resolution
Update all occurrences of the package flag -p server to -p coreason-server, and update references to the compiled output binary target/release/server to target/release/coreason-server.
- In
Dockerfile:
RUN cargo build --release -p coreason-server
COPY --from=builder /usr/src/coreason/target/release/coreason-server /usr/local/bin/server
- In
.github/workflows/ci.yml:
run: cargo build -p coreason-server --target-dir target/llvm-cov-target
and
run: cargo build -p coreason-server
- In
README.md and science/coreason_manifest/README.md:
Change references to -p coreason-server.
How to Verify the Issue is Resolved
-
Verify Local Docker Build:
Expected result: Completes successfully without syntax or package compilation errors.
-
Verify Local Cargo Build:
cargo check -p coreason-server
Expected result: Compiles the package successfully.
Bug Report: CI/Docker build failures due to
coreason-servercrate renameProblem Description
In commit
2e1bc4c7128773f9f26c51839d8d585156554351, the server crate was renamed fromservertocoreason-server. However, references to the package name inDockerfile,.github/workflows/ci.yml, and user documentation files were not updated. As a result, the Docker image builds and GitHub Actions CI workflows are broken.Affected Files and Lines
DockerfileRUN cargo build --release -p serverCOPY --from=builder /usr/src/coreason/target/release/server /usr/local/bin/server.github/workflows/ci.ymlrun: cargo build -p server --target-dir target/llvm-cov-targetrun: cargo build -p serverREADME.mdcargo build --release -p serverscience/coreason_manifest/README.mdcargo build --release -p serverError Logs
From Docker/CI logs:
How to Confirm/Replicate the Issue
Run either of the following commands:
Local Docker Build:
Expected result: Fails during
RUN cargo build --release -p serverwith package matching error.Local Cargo Check:
Expected result:
error: package ID specification 'server' did not match any packagesProposed Resolution
Update all occurrences of the package flag
-p serverto-p coreason-server, and update references to the compiled output binarytarget/release/servertotarget/release/coreason-server.Dockerfile:.github/workflows/ci.yml:README.mdandscience/coreason_manifest/README.md:Change references to
-p coreason-server.How to Verify the Issue is Resolved
Verify Local Docker Build:
Expected result: Completes successfully without syntax or package compilation errors.
Verify Local Cargo Build:
Expected result: Compiles the package successfully.