NOTASK: Fix exporter decoding of unsigned Slurm values - #2990
Draft
ali-sattari wants to merge 1 commit into
Draft
ali-sattari wants to merge 1 commit into
ali-sattari wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Exporter collection fails when Slurm returns unsigned values such as job priority 4294967293 that overflow the generated client’s signed integer fields.
Solution
Decode only fields needed for metrics, widen RPC counters and user IDs, and handle unset/infinite numeric sentinels.
Testing
Validated with regression tests reproducing the failures on main, race-enabled tests, lint, and repository-wide compilation.
Release Notes
Fix exporter collection failures due to int overflow when Slurm API returns unsigned values.