-
-
Notifications
You must be signed in to change notification settings - Fork 148
Bump Rust Version #1383
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump Rust Version #1383
Conversation
WalkthroughThis change set primarily reorders import statements across numerous files for consistency and style, updates some error message formatting for readability, and applies minor code simplifications. Notably, it updates the Rust edition and minimum compiler version in Changes
Sequence Diagram(s)sequenceDiagram
participant StoreMetadata
participant UIDUtils
StoreMetadata->>UIDUtils: generate_ulid()
UIDUtils-->>StoreMetadata: ULID string
Note right of StoreMetadata: deployment_id initialized with ULID
Estimated code review effort2 (45 minutes) Possibly related PRs
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (109)
✅ Files skipped from review due to trivial changes (26)
🚧 Files skipped from review as they are similar to previous changes (83)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (10)
✨ Finishing Touches
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
f677e93
to
5116dbf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 3
🧹 Nitpick comments (4)
src/sync.rs (1)
314-325
: Polish logging message wordingMinor copy-editing to make the log a bit clearer/grammatically correct.
- warn!( - "Error while evaluation- {}\nRetrying after sleeping for 1 minute", - err - ); + warn!( + "Error during evaluation: {}. Retrying in 1 minute …", + err + ); @@ - error!( - "Alert with id {} failed to evaluate after 3 retries with err- {}", - id, err - ); + error!( + "Alert {id} failed after 3 retries: {err}", + );src/handlers/http/modal/query/querier_logstream.rs (1)
38-41
: Spelling nit:merge_quried_stats
→merge_queried_stats
Minor readability issue—“queried” is misspelled. If you ever touch this API again consider renaming (with cargo-fix or a re-export) to avoid propagating the typo.
src/analytics.rs (1)
243-244
: Consider replacing long tuple with a struct.
fetch_ingestors_metrics
now returns a 12-element tuple. Even with the formatting tweak, the call-sites remain hard to read and error-prone. Encapsulating these metrics in a dedicated struct (e.g.,IngestorMetrics
) would improve clarity and future maintainability.src/handlers/http/oidc.rs (1)
289-295
: Apply the same hardening to username cookieCookie::build(USER_COOKIE_NAME, username.to_string()) .max_age(time::Duration::days(COOKIE_AGE_DAYS as i64)) .same_site(SameSite::Strict) + .http_only(true) .path("/") .finish()
Even though the username is less sensitive, keeping cookies HttpOnly maintains a consistent security posture.
edition = "2024" | ||
rust-version = "1.88.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Critical: Edition 2024 is not stabilized and causes build failures.
The pipeline failure indicates that edition2024
is not stabilized in Cargo version 1.84.0. This will break builds in environments without the latest nightly Rust toolchain.
Consider using edition = "2021"
until edition 2024 is stabilized:
-edition = "2024"
-rust-version = "1.88.0"
+edition = "2021"
+rust-version = "1.83.0"
Alternatively, if you need features from edition 2024, ensure all CI/CD environments support it and document this requirement.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
edition = "2024" | |
rust-version = "1.88.0" | |
edition = "2021" | |
rust-version = "1.83.0" |
🤖 Prompt for AI Agents
In Cargo.toml at lines 5 to 6, the edition is set to "2024" which is not
stabilized and causes build failures. Change the edition value from "2024" to
"2021" to ensure compatibility with stable Rust toolchains and avoid pipeline
failures. If edition 2024 features are necessary, update all CI/CD environments
to use a nightly Rust toolchain that supports edition 2024 and document this
requirement clearly.
e19cb87
to
1f85aa2
Compare
bumped edition to 2024 bumped version to 1.88.0
1f85aa2
to
c173d9e
Compare
bumped edition to 2024
bumped version to 1.88.0
Mostly
cargo fmt
changes in all the filesFixes #XXXX.
Description
This PR has:
Summary by CodeRabbit
Refactor
Chores
Documentation
No changes to user-facing features or functionality were introduced.