Skip to content

Keep deployment concurrency values integral for integer API fields - #1165

Closed
rudycelekli wants to merge 1 commit into
deeplethe:devfrom
rudycelekli:fix/deployment-integral-concurrency-20261009
Closed

rudycelekli wants to merge 1 commit into
deeplethe:devfrom
rudycelekli:fix/deployment-integral-concurrency-20261009

Conversation

@rudycelekli

Copy link
Copy Markdown
Contributor

Decimal input is accepted by all three concurrency controls and submitted as a JSON fraction, which the server integer fields reject. Truncate the control values before storing them while retaining their existing bounds.

Validation: actual worker, default-model and per-model input handler regressions fail on baseline behavior (exported only for test access); all three pass fixed with hook boundaries controlled. Typecheck, style guard and production build pass.

Signed-off-by: Rudy Celekli <rudy@gradiahq.com>
@WaylandYang

Copy link
Copy Markdown
Contributor

Thank you for going through the codebase this carefully. We are taking eight from this batch (#1140, #1143, #1147, #1148, #1157, #1163, #1166, #1168), each a behaviour someone using Utopia would hit.

We are closing this one: it guards against an input we have not seen in use, and we keep the code and its tests to what the product needs today.

If you see this happen in a real deployment, please open an issue with the case and we will take it. For future sweeps, one issue listing the findings first would let us pick together before you write the fixes.

Thanks again for the time you put into this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants