Skip to content

fix(frontend): replace vendor logos in operator icons with typographic icons - #8999

Merged
mengw15 merged 2 commits into
apache:mainfrom
mengw15:fix/8982-replace-vendor-logo-icons
Oct 27, 2026
Merged

mengw15 merged 2 commits into
apache:mainfrom
mengw15:fix/8982-replace-vendor-logo-icons

Conversation

@mengw15

@mengw15 mengw15 commented Oct 15, 2026

Copy link
Copy Markdown
Contributor

What changes were proposed in this PR?

Per #8982, thirteen operator icons under frontend/src/assets/operator_images/ were other organisations' logos (Twitter, Reddit, PostgreSQL, MySQL, Hugging Face, the Python logo), a photo of an iris, or stock-looking artwork, with no recorded source or licence. None of them has a licence that lets an Apache source release redistribute it, so this replaces them with project-made icons.

The new icons follow the UDF icons from #5686: a large hero word with an optional gray descriptor on a 1024×1024 transparent canvas, so they match Py, R and Java on the canvas. They were drawn with Pillow, and the text uses Aileron Regular (CC0), the font bundled with Pillow, so no LICENSE entry is needed. File names are unchanged, so the assets/operator_images/<operatorType>.png lookup still finds them.

JavaUDF.png on main is already the project-made icon from #5686, so it isn't touched. On release/v1.2 it is still the Java logo, because #5686 wasn't backported, and that branch has no HuggingFace.png, so the v1.2 backport needs both adjusted.

Any related issues, documentation, discussions?

Part of #8982; its Jupyter item is #8997 and #8998. Part of #8800.

How was this PR tested?

Asset swap only, with no code change. Previewed the icons at the 35 px size the workflow canvas draws them at, and checked that the commit applies cleanly to release/v1.3.

Was this PR authored or co-authored using generative AI tooling?

Generated-by: Claude Code (claude-opus-5-5)

…c icons

Thirteen operator icons were other organisations' logos (Twitter,
Reddit, PostgreSQL, MySQL, Hugging Face, the Python logo), a photo of an
iris, or stock artwork, with no recorded source or licence (apache#8982).
Replace them with project-made typographic icons in the style of the UDF
icons from apache#5686: a large hero word with an optional gray descriptor on a
1024x1024 transparent canvas. The text is rendered with Aileron Regular
(CC0), the font bundled with Pillow. File names are unchanged.
@mengw15
mengw15 requested a balanced review from Copilot October 15, 2026 16:57

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.

@github-actions github-actions Bot added fix frontend Changes related to the frontend GUI labels Oct 15, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Automated Reviewer Suggestions

Based on the git blame history of the changed files, we recommend the following reviewers:

  • Contributors with relevant context: @Yicong-Huang, @yunyad, @PG1204
    You can notify them by mentioning @Yicong-Huang, @yunyad, @PG1204 in a comment.

@Yicong-Huang Yicong-Huang added release/v1.3 back porting to release/v1.3 release/v1.2 back porting to release/v1.2 labels Oct 15, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Backport auto-label report

This fix: PR was checked against each actively-supported release branch. A release/* label nominates a backport target; the branch's release manager approving this PR is what sends the fix there. The required Backport Approvals check stays red until every label below is approved, so each manager either approves or removes their own label — which is why the labels left on a merged PR are exactly the branches it reached.

Release branch Analysis
✅ release/v1.3 Change detected on this branch — label added; this fix is queued to backport here.
✅ release/v1.2 Change detected on this branch — label added; this fix is queued to backport here. @xuang7 decides: approving sends the fix here, removing this label declines it. The merge waits on one or the other. Review requested.

Auto-label run.

@codecov-commenter

codecov-commenter commented Oct 15, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.14%. Comparing base (3c7318c) to head (b560c4e).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main    #8999      +/-   ##
============================================
+ Coverage     91.98%   93.14%   +1.15%     
+ Complexity     5084     5004      -80     
============================================
  Files          1281     1274       -7     
  Lines         55812    61921    +6109     
  Branches       7076     8654    +1578     
============================================
+ Hits          51340    57677    +6337     
+ Misses         2732     2495     -237     
- Partials       1740     1749       +9     
Flag Coverage Δ *Carryforward flag
access-control-service 77.38% <ø> (-0.07%) ⬇️ Carriedforward from 2b795f4
agent-service 99.14% <ø> (-0.02%) ⬇️ Carriedforward from 2b795f4
amber 87.46% <ø> (+1.03%) ⬆️ Carriedforward from 2b795f4
computing-unit-managing-service 60.27% <ø> (-3.26%) ⬇️ Carriedforward from 2b795f4
config-service 87.37% <ø> (-0.13%) ⬇️ Carriedforward from 2b795f4
file-service 82.01% <ø> (-0.29%) ⬇️ Carriedforward from 2b795f4
frontend 96.94% <ø> (+0.41%) ⬆️
notebook-migration-service 83.73% <ø> (-0.04%) ⬇️ Carriedforward from 2b795f4
pyamber 98.53% <ø> (-0.02%) ⬇️ Carriedforward from 2b795f4
workflow-compiling-service 72.43% <ø> (-1.82%) ⬇️ Carriedforward from 2b795f4

*This pull request uses carry forward flags. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@xuang7 xuang7 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM! All 13 replacements are text-based and contain no third-party branding. All 13 replacements are typographic with no third-party marks, and since only the rendered PNGs are committed (Aileron is CC0 anyway), no LICENSE entry is needed.

One minor suggestion: could we simply remove the Twitter-related images, since the service appears to be deprecated? See #4463.

@mengw15
mengw15 enabled auto-merge October 27, 2026 22:23
@mengw15
mengw15 disabled auto-merge October 27, 2026 22:33
@mengw15
mengw15 enabled auto-merge October 27, 2026 22:33
@mengw15
mengw15 added this pull request to the merge queue Oct 27, 2026
Merged via the queue into apache:main with commit 1aa7e2a Oct 27, 2026
35 checks passed
@mengw15
mengw15 deleted the fix/8982-replace-vendor-logo-icons branch October 27, 2026 22:44
@github-actions

Copy link
Copy Markdown
Contributor

Backport PR opened: #9191 (#9191) to release/v1.3 — the cherry-pick was clean, so it is ready for review, waiting on @mengw15. It needs to be reopened once to start its checks; the PR says how.

@github-actions

Copy link
Copy Markdown
Contributor

Backport PR opened: draft #9192 (#9192) to release/v1.2, assigned to @mengw15 — needs manual work because the cherry-pick conflicts.

mengw15 added a commit that referenced this pull request Oct 27, 2026
…h release/v1.2 does not have)

The cherry-pick added frontend/src/assets/operator_images/HuggingFace.png,
which release/v1.2 never had and nothing there refers to. The other 12 icons
are as in #8999.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fix frontend Changes related to the frontend GUI release/v1.2 back porting to release/v1.2 release/v1.3 back porting to release/v1.3

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants