Skip to content

fix(phd-dashboard): bump builder to rust:1.85-slim (edition2024) - #530

Merged
gHashTag merged 1 commit into
mainfrom
fix/phd-dashboard-rust-1.85
May 7, 2026
Merged

gHashTag merged 1 commit into
mainfrom
fix/phd-dashboard-rust-1.85

Conversation

@gHashTag

@gHashTag gHashTag commented May 7, 2026

Copy link
Copy Markdown
Collaborator

Summary

Railway deployment of phd-dashboard (service a99f1adc-75b0-40d3-97df-f9107c2730be) was failing during cargo build because the Dockerfile pinned the builder image to rust:1.78-slim. A transitively pulled crate (block-buffer 0.12.0 via the sqlx → sha2 → block-buffer chain) declares edition = "2024" in its manifest, which requires Rust 1.85+.

error: failed to parse manifest at `…/block-buffer-0.12.0/Cargo.toml`
Caused by:
  feature `edition2024` is required
  …not stabilized in this version of Cargo (1.78.0)

Change

Bump builder image to rust:1.85-slim in crates/phd-dashboard/Dockerfile. Runtime stage (debian:bookworm-slim) unchanged — still produces a small final image.

- FROM rust:1.78-slim AS builder
+ FROM rust:1.85-slim AS builder

Verification

  • Local cargo (1.85+ in workspace) builds phd-dashboard cleanly
  • After merge, Railway deploy 8cd0afbe will be retriggered

Closes

Closes #529

φ² + φ⁻² = 3

…d by block-buffer 0.12)

Railway build failed:
  feature `edition2024` is required
  The package requires the Cargo feature called `edition2024`, but that feature is not stabilized in this version of Cargo (1.78.0).

block-buffer 0.12.0 (transitively pulled by sqlx/sha2 chain) declares edition = "2024" which requires Rust 1.85+. Bumping the builder image accordingly. Runtime stage stays on debian:bookworm-slim.
@gHashTag
gHashTag merged commit 8da2d7f into main May 7, 2026
15 checks passed
@gHashTag
gHashTag deleted the fix/phd-dashboard-rust-1.85 branch May 7, 2026 04:49
gHashTag pushed a commit that referenced this pull request May 7, 2026
… (refs #446 #509 #521 #531)

Build cpu_train (release) failed at run 25477123014 with:

  error: rustc 1.85.0 is not supported by the following packages:
    icu_normalizer@2.2.0 requires rustc 1.86
    icu_normalizer_data@2.2.0 requires rustc 1.86
    icu_properties@2.2.0 requires rustc 1.86
    ...

icu_normalizer is pulled transitively (likely via tokio-postgres-rustls or
serde stack). PR #530 only bumped phd-dashboard's docker builder; the
trainer-igla CI here picked the older 1.85 pin.

Bump to 1.86.0 (still pinned, not floating). Trainer-igla Cargo.lock
exactly versions every dep, so reproducibility is preserved.

R10 atomic: single-line workflow change.

Part of #446
Closes #531 when L-FH4 green
Resolves #509 when L-FH4 green

Anchor: phi^2 + phi^-2 = 3 · DOI 10.5281/zenodo.19227877
gHashTag pushed a commit that referenced this pull request May 7, 2026
… (refs #446 #509 #521 #531)

Build cpu_train (release) failed at run 25477123014 with:

  error: rustc 1.85.0 is not supported by the following packages:
    icu_normalizer@2.2.0 requires rustc 1.86
    icu_normalizer_data@2.2.0 requires rustc 1.86
    icu_properties@2.2.0 requires rustc 1.86
    ...

icu_normalizer is pulled transitively (likely via tokio-postgres-rustls or
serde stack). PR #530 only bumped phd-dashboard's docker builder; the
trainer-igla CI here picked the older 1.85 pin.

Bump to 1.86.0 (still pinned, not floating). Trainer-igla Cargo.lock
exactly versions every dep, so reproducibility is preserved.

R10 atomic: single-line workflow change.

Part of #446
Closes #531 when L-FH4 green
Resolves #509 when L-FH4 green

Anchor: phi^2 + phi^-2 = 3 · DOI 10.5281/zenodo.19227877
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.

phd-dashboard: Railway build fails — block-buffer 0.12 needs Rust 1.85+ (edition2024)

1 participant