Phoenix UINT range checking breaks on hex values

[cartermak]

Checked for duplicates

No - I haven't checked

Is this a regression?

No - This is a new bug

Version

2.11.2

Describe the bug

When writing hex values for UINT command arguments in SeqN, the Phoenix editor's range checking seems to misbehave.

I don't have a clear characterization of the issue, but this is what I've seen:

1. On one UINT argument (second of five arguments) with a large max value (4294967292), users receive a range error even for hex values that are within the valid range.
2. On another UINT argument (the last of the five arguments) with a small max value (100), users receive no error even if the specified hex value is outside the allowed range.

On their own, 1. would suggest that Phoenix doesn't know to parse the value as hex when assessing whether it's in range, but 2. would suggest Phoenix doesn't range check hex values at all. I haven't dug in to characterize whether either of the variables I identified (position of the argument and magnitude of the max range) actually affect this behavior.

It doesn't seem like the range checking issue affects the generated SeqJSON.

Reproduction

See my repro on Clipper-internal ticket: https://github.jpl.nasa.gov/Europa-PESS/clipper-phoenix-adaptation/issues/60

Logs

No response

System Info

Cloud deployment of Aerie 2.11.2 for Clipper.

Severity

Moderate