Skip to content

[WRONG BRANCH] fix(config): validate provider modelInputModalities maps as string-array records - #223

Draft
luvs01 wants to merge 1 commit into
mainfrom
codex/fix-malformed-modality-overrides-issue
Draft

[WRONG BRANCH] fix(config): validate provider modelInputModalities maps as string-array records#223
luvs01 wants to merge 1 commit into
mainfrom
codex/fix-malformed-modality-overrides-issue

Conversation

@luvs01

@luvs01 luvs01 commented Aug 9, 2026

Copy link
Copy Markdown
Owner

Motivation

  • Prevent malformed modelInputModalities persisted or management-submitted values (e.g. "grok-4.3": null) from being cloned/spread and throwing a TypeError during registry enrichment.

Description

  • Add a stringArrayRecordConfigError validator in src/config.ts that enforces a plain object whose values are arrays of strings.
  • Hook that validator into the disk/load-time provider validation so malformed persisted modelInputModalities produce a controlled config diagnostic instead of surviving parsing.
  • Validate modelInputModalities at the management API admission boundary in src/server/auth-cors.ts so POST/PUT provider submissions with invalid modality maps return 400 rather than letting enrichment crash.
  • Add regression tests covering a malformed persisted modelInputModalities and invalid management POST payloads in tests/config.test.ts and tests/management-provider-validation.test.ts respectively.

Testing

  • Ran bun run typecheck which completed successfully.
  • Ran bun run privacy:scan which passed.
  • Ran targeted unit tests tests/config.test.ts, tests/management-provider-validation.test.ts, and tests/catalog-vision-sidecar-modalities.test.ts, and those targeted test files passed.
  • Executed an ad-hoc check invoking providerManagementConfigError with a null modality entry which returned a modelInputModalities validation error as expected.
  • The full test suite was attempted but encountered unrelated environment timeouts and external-resolution delays; the failures were not introduced by this change and are outside the scope of the focused validation fix.

Codex Task

@coderabbitai

coderabbitai Bot commented Aug 9, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@luvs01, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 40 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 54a9d2de-fe93-4620-b47e-d4372b1dbd42

📥 Commits

Reviewing files that changed from the base of the PR and between 121f1ad and 1cd9f4c.

📒 Files selected for processing (4)
  • src/config.ts
  • src/server/auth-cors.ts
  • tests/config.test.ts
  • tests/management-provider-validation.test.ts

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added the bug Something isn't working label Aug 9, 2026
@github-actions

github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown

Deterministic PR hygiene checks passed.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1cd9f4cdad

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/config.ts
for (const [key, entry] of Object.entries(value)) {
if (!key.trim()) return `${field} keys must be nonblank model ids`;
if (!Array.isArray(entry) || entry.some(item => typeof item !== "string")) {
return `${field}.${key} must be an array of strings`;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Redact model IDs before constructing validation errors

When a malformed persisted map uses a secret-shaped model key, such as {"sk-...": null}, this message embeds that key verbatim; loadConfig() then passes the Zod issue to warnAndBackupInvalidConfig(), which prints the full message to stderr. The management validation path likewise returns the unredacted key. Redact and JSON-escape the key before including it in the diagnostic, as the nearby retryOn429 validation already does.

AGENTS.md reference: AGENTS.md:L233-L234

Useful? React with 👍 / 👎.

@github-actions

github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown

⏳ DRAFT

  • wrong target branch (main); retarget to dev.

What to do

  • Retarget this PR to dev — all contributions go to dev.

Its title has been prefixed with [WRONG BRANCH].
This pull request was already a draft. Its draft status will be preserved after every issue above is resolved.

@github-actions github-actions Bot changed the title fix(config): validate provider modelInputModalities maps as string-array records [WRONG BRANCH] fix(config): validate provider modelInputModalities maps as string-array records Aug 9, 2026
@github-actions
github-actions Bot marked this pull request as draft August 9, 2026 06:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

aardvark bug Something isn't working codex

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant