Skip to content

UPSTREAM: <carry>: fix(frontend): prevent long parameter labels from wrapping to multiple lines - #403

Open
jira-autofix[bot] wants to merge 1 commit into
masterfrom
autofix/rhoaieng-56381
Open

UPSTREAM: <carry>: fix(frontend): prevent long parameter labels from wrapping to multiple lines#403
jira-autofix[bot] wants to merge 1 commit into
masterfrom
autofix/rhoaieng-56381

Conversation

@jira-autofix

@jira-autofix jira-autofix Bot commented Jul 11, 2026

Copy link
Copy Markdown

Prevents long parameter labels in the NewRunParametersV2 component from wrapping to multiple lines. CSS rules (whiteSpace: nowrap, overflow: hidden, textOverflow: ellipsis) are applied to MuiInputLabel-root within the textfield style, so labels are truncated with an ellipsis instead of wrapping.

Includes a regression test verifying the label element has the MuiInputLabel-root class for truncation styling.

Jira: RHOAIENG-56381

This iteration fixed the commit message format from conventional commit style to the UPSTREAM: carry: convention required by the repo's commit checker.

Summary by CodeRabbit

  • Bug Fixes

    • Improved handling of long parameter labels by keeping them on a single line and displaying an ellipsis when necessary.
    • Preserved visibility of parameter values alongside truncated labels.
  • Tests

    • Added coverage verifying long parameter names and their default values render correctly.

@openshift-ci
openshift-ci Bot requested review from mprahl and nsingla July 11, 2026 02:29
@openshift-ci

openshift-ci Bot commented Jul 11, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign dsp-developers for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@coderabbitai

coderabbitai Bot commented Jul 11, 2026

Copy link
Copy Markdown
📝 Walkthrough

Walkthrough

Updated NewRunParametersV2 row styling to render long MUI input labels on one line with hidden overflow and ellipsis. Added a test using optimization_max_rag_patterns that verifies the expected label text and default value.

Estimated code review effort: 1 (Trivial) | ~5 minutes

🚥 Pre-merge checks | ✅ 9 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description explains the change but omits the required template sections and checklist items. Add the required template headings, include the checklist items, and state sign-off and DSPO testing status explicitly.
✅ Passed checks (9 passed)
Check name Status Explanation
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Contribution Quality And Spam Detection ✅ Passed No fail: this is a small UI styling fix with a regression test and issue-linked commit; I found no second-category spam/security-theater signal.
No Hardcoded Secrets ✅ Passed No CWE-798 indicators: the PR only adds label-truncation CSS and a test; no API keys, tokens, passwords, private keys, or credentialed URLs were added.
No Weak Cryptography ✅ Passed Patch only adds MUI label-truncation CSS and a regression test; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret comparisons (CWE-327/CWE-208).
No Injection Vectors ✅ Passed Only adds CSS ellipsis styling and a render test; no new CWE-89/78/94/502/79 sinks or user-controlled code execution/HTML insertion.
No Privileged Containers ✅ Passed Only frontend TSX changed; no Kubernetes/OpenShift manifests, Helm templates, or Dockerfiles. No privileged settings to flag (CWE-284/CWE-266).
No Sensitive Data In Logs ✅ Passed No logging APIs or raw request/response bodies were added; the diff is limited to CSS truncation and a regression test, so CWE-532 risk is not introduced.
Title check ✅ Passed The title matches the change and uses the repository's required fix(frontend) style with the upstream carry prefix.

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

@dsp-developers

Copy link
Copy Markdown

Commit Checker results:

**NOTE**: These are the results of the commit checker scans. 
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting
commitchecker verson unknown
Validating 1 commits between 3a1866e3c7ce2d853e93d082255c511433773105...3bd9e0ee7bd8ae0bd620c1d1e32599c754a17b6a

UPSTREAM commit 3bd9e0e has invalid summary fix(frontend): prevent long parameter labels from wrapping to multiple lines.

UPSTREAM commits are validated against the following regular expression:
  ^UPSTREAM: (revert: )?(([\w.-]+/[\w-.-]+)?: )?(\d+:|<carry>:|<drop>:)

UPSTREAM commit summaries should look like:

  UPSTREAM: <PR number|carry|drop>: description

UPSTREAM commits which revert previous UPSTREAM commits should look like:

  UPSTREAM: revert: <normal upstream format>

Examples of valid summaries:

  UPSTREAM: 12345: A kube fix
  UPSTREAM: <carry>: A carried kube change
  UPSTREAM: <drop>: A dropped kube change
  UPSTREAM: revert: 12345: A kube revert


@coderabbitai coderabbitai Bot added the ai-slop label Jul 11, 2026

@coderabbitai coderabbitai 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.

Actionable comments posted: 1

🧹 Nitpick comments (1)
frontend/src/components/NewRunParametersV2.tsx (1)

68-74: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Verify this override is necessary; MUI already provides these styles.

@mui/material@5.18.0 already applies white-space: nowrap, overflow: hidden, text-overflow: ellipsis, and max-width to InputLabelRoot. If a local override causes the wrapping, target that override or document the required specificity; otherwise this duplicates framework CSS. (raw.githubusercontent.com)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@frontend/src/components/NewRunParametersV2.tsx` around lines 68 - 74, Verify
the nested .MuiInputLabel-root override in the component’s styling configuration
is necessary; remove it if MUI’s InputLabelRoot styles already provide the
required nowrap, overflow, and ellipsis behavior, or adjust/document the
override only if a local rule is causing wrapping and requires additional
specificity.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@frontend/src/components/NewRunParametersV2.test.tsx`:
- Around line 1321-1337: Update the “Long parameter label wrapping
(`#RHOAIENG-56381`)” test to query the rendered label element directly rather than
relying on getByLabelText, then assert its whiteSpace, overflow, and
textOverflow styles to verify truncation; use a browser test only if pixel-level
clipping must be validated.

---

Nitpick comments:
In `@frontend/src/components/NewRunParametersV2.tsx`:
- Around line 68-74: Verify the nested .MuiInputLabel-root override in the
component’s styling configuration is necessary; remove it if MUI’s
InputLabelRoot styles already provide the required nowrap, overflow, and
ellipsis behavior, or adjust/document the override only if a local rule is
causing wrapping and requires additional specificity.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 2a85429c-adc1-4759-b767-12913e02696a

📥 Commits

Reviewing files that changed from the base of the PR and between 3a1866e and 3bd9e0e.

📒 Files selected for processing (2)
  • frontend/src/components/NewRunParametersV2.test.tsx
  • frontend/src/components/NewRunParametersV2.tsx

Comment thread frontend/src/components/NewRunParametersV2.test.tsx
@dsp-developers

Copy link
Copy Markdown

A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-403
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-403
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-403
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-403
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-403
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-403
TESTS: quay.io/opendatahub/ds-pipelines-tests:pr-403

@dsp-developers

Copy link
Copy Markdown

An OCP cluster where you are logged in as cluster admin is required.

The Data Science Pipelines team recommends testing this using the Data Science Pipelines Operator. Check here for more information on using the DSPO.

To use and deploy a DSP stack with these images (assuming the DSPO is deployed), first save the following YAML to a file named dspa.pr-403.yaml:

apiVersion: datasciencepipelinesapplications.opendatahub.io/v1
kind: DataSciencePipelinesApplication
metadata:
  name: pr-403
spec:
  dspVersion: v2
  apiServer:
    image: "quay.io/opendatahub/ds-pipelines-api-server:pr-403"
    argoDriverImage: "quay.io/opendatahub/ds-pipelines-driver:pr-403"
    argoLauncherImage: "quay.io/opendatahub/ds-pipelines-launcher:pr-403"
  persistenceAgent:
    image: "quay.io/opendatahub/ds-pipelines-persistenceagent:pr-403"
  scheduledWorkflow:
    image: "quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-403"
  mlmd:  
    deploy: true  # Optional component
    grpc:
      image: "quay.io/opendatahub/mlmd-grpc-server:latest"
    envoy:
      image: "registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2"
  mlpipelineUI:
    deploy: true  # Optional component 
    image: "quay.io/opendatahub/ds-pipelines-frontend:pr-403"
  objectStorage:
    minio:
      deploy: true
      image: 'quay.io/opendatahub/minio:RELEASE.2019-08-14T20-37-41Z-license-compliance'

Then run the following:

cd $(mktemp -d)
git clone git@github.com:opendatahub-io/data-science-pipelines.git
cd data-science-pipelines/
git fetch origin pull/403/head
git checkout -b pullrequest 3bd9e0ee7bd8ae0bd620c1d1e32599c754a17b6a
oc apply -f dspa.pr-403.yaml

More instructions here on how to deploy and test a Data Science Pipelines Application.

@dsp-developers

Copy link
Copy Markdown

Commit Checker results:

**NOTE**: These are the results of the commit checker scans. 
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting
commitchecker verson unknown
Validating 2 commits between 3a1866e3c7ce2d853e93d082255c511433773105...624f72cd938fe5e25ba378bc2579609579253cb3

UPSTREAM commit 624f72c has invalid summary fix(frontend): assert label element directly in truncation test (#RHOAIENG-56381).

UPSTREAM commits are validated against the following regular expression:
  ^UPSTREAM: (revert: )?(([\w.-]+/[\w-.-]+)?: )?(\d+:|<carry>:|<drop>:)

UPSTREAM commit summaries should look like:

  UPSTREAM: <PR number|carry|drop>: description

UPSTREAM commits which revert previous UPSTREAM commits should look like:

  UPSTREAM: revert: <normal upstream format>

Examples of valid summaries:

  UPSTREAM: 12345: A kube fix
  UPSTREAM: <carry>: A carried kube change
  UPSTREAM: <drop>: A dropped kube change
  UPSTREAM: revert: 12345: A kube revert



UPSTREAM commit 3bd9e0e has invalid summary fix(frontend): prevent long parameter labels from wrapping to multiple lines.

UPSTREAM commits are validated against the following regular expression:
  ^UPSTREAM: (revert: )?(([\w.-]+/[\w-.-]+)?: )?(\d+:|<carry>:|<drop>:)

UPSTREAM commit summaries should look like:

  UPSTREAM: <PR number|carry|drop>: description

UPSTREAM commits which revert previous UPSTREAM commits should look like:

  UPSTREAM: revert: <normal upstream format>

Examples of valid summaries:

  UPSTREAM: 12345: A kube fix
  UPSTREAM: <carry>: A carried kube change
  UPSTREAM: <drop>: A dropped kube change
  UPSTREAM: revert: 12345: A kube revert


@dsp-developers

Copy link
Copy Markdown

Change to PR detected. A new PR build was completed.
A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-403
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-403
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-403
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-403
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-403
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-403
TESTS: quay.io/opendatahub/ds-pipelines-tests:pr-403

…wrapping to multiple lines

Long parameter labels in NewRunParametersV2 input fields were wrapping to
multiple lines, making the form difficult to read. Added CSS rules
(whiteSpace: nowrap, overflow: hidden, textOverflow: ellipsis) to the
MuiInputLabel-root class within the textfield style to ensure labels are
truncated with an ellipsis instead of wrapping.

Includes a regression test that verifies the label element has the
MuiInputLabel-root class for truncation styling.

Jira: RHOAIENG-56381

Assisted-by: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: aipcc-bot <aipcc-bot@redhat.com>
@jira-autofix
jira-autofix Bot force-pushed the autofix/rhoaieng-56381 branch from 624f72c to 6a4f787 Compare July 11, 2026 07:23
@jira-autofix jira-autofix Bot changed the title fix(frontend): prevent long parameter labels from wrapping to multiple lines UPSTREAM: <carry>: fix(frontend): prevent long parameter labels from wrapping to multiple lines Jul 11, 2026
@dsp-developers

Copy link
Copy Markdown

Commit Checker results:

**NOTE**: These are the results of the commit checker scans. 
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting
commitchecker verson unknown
Validating 1 commits between 3a1866e3c7ce2d853e93d082255c511433773105...6a4f7872c2ead8f434a5618356b85bfb35290a6e

@dsp-developers

Copy link
Copy Markdown

Change to PR detected. A new PR build was completed.
A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-403
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-403
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-403
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-403
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-403
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-403
TESTS: quay.io/opendatahub/ds-pipelines-tests:pr-403

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant