Orange-OpenSource / Orange-OpenSource/its-client

Fix Rust (1.90?) version

Open
#454 0 comments 0 reactions 2 assignees View on GitHub

@tigroo is already working on this.

Since Oct 20, 2025.

Rust
Dominant language
Java
Stars
19
Forks
12
Avg merge
6d 8h
Merged PRs (30d)
3

Description

Just to mention, the collector example code need Rust 1.90 to work, it does not build under 1.85

error[E0658]: `let` expressions in this position are unstable
   --> examples/collector/main.rs:208:32
    |
208 | ...                   if let Some(file_exporter) = &exporter.file
    |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information

error[E0658]: `let` expressions in this position are unstable
   --> examples/collector/main.rs:209:36
    |
209 | ...                   && let Some(ref mut current_log_file) = log_file
    |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information

error[E0658]: `let` expressions in this position are unstable
   --> examples/collector/main.rs:225:36
    |
225 | ...                   && let Some(ref mut current_publish_client) = publish_client
    |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information

For more information about this error, try `rustc --explain E0658`.
error: could not compile `libits-client` (example "collector") due to 3 previous errors

Originally posted by @nbuffon in https://github.com/Orange-OpenSource/its-client/issues/417#issuecomment-3405327766

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.