Rust: re-enable dedicated CI job with toolchain 1.85.1#3417
Rust: re-enable dedicated CI job with toolchain 1.85.1#3417santiagomed wants to merge 4 commits intoapache:masterfrom
Conversation
|
Follow-up codegen change: #3414. Please review this Rust CI fix first. |
|
Could you please check e4666f2 on how to enable cross tests as well for Rust, this change only enables unit tests |
69d0f5e to
d91566b
Compare
|
@kpumuk you're right I had missed the commit, fixed. |
|
Last changes go in weird directions :-) Java formatting is fixed in master, not quite sure what Node.js are for... |
89db116 to
40c36c4
Compare
|
@kpumuk Thanks, removed the Java file. The Node.js commits fix cross-test failures that show up when Rust CI is re-enabled: the Node.js binary/compact protocol decoders were rejecting raw UUID bytes from the Rust client, and the test harness needed |
|
Does anyone know any way I can avoid waiting for a workflow approval for this PR? It would help me iterate faster. At xAI we need #3414 to land ASAP since it is causing issues. |
|
The easiest option to avoid waiting it to allow the pipeline to run on your fork and iterate there :) |
69167c3 to
6c64e0e
Compare
3f1d38a to
251fa92
Compare
251fa92 to
0b61008
Compare
|
Can I get a workflow approval? I think CI should pass now santiagomed#1 |
The uuid npm package v13 validates that stringified UUIDs conform to RFC 4122 (version nibble in [1-8], variant nibble in [89ab]). The previous test value 00010203-0405-0607-0809-0a0b0c0d0e0f has version=0 and variant=0, causing stringify() to throw TypeError on the Node.js server side. Use the same UUID as the Go cross-test client (00112233-4455-6677-8899-aabbccddeeff) which passes validation. Client: rs
0b61008 to
61cf80f
Compare
|
@Jens-G looks like I need another approval. Can you take a look please? |
Client: rust This closes apache#3417
Summary
rust-toolchainpin to 1.85.1Why
The dedicated Rust CI job was disabled, and the previous 1.83.0 toolchain no longer resolves the current dependency graph cleanly. This restores a working Rust validation path.
Follow-up work in #3414 depends on having dedicated Rust CI healthy again, but GitHub cannot stack that upstream PR directly on a fork-only base branch. Review these PRs together, with this one first.
Validation
cargo +1.85 test --manifest-path lib/rs/Cargo.toml --lockedcargo +1.85 test --manifest-path lib/rs/test/Cargo.tomlcargo +1.85 test --manifest-path test/rs/Cargo.toml