The GitHub Actions job "Backport Checks" on texera.git/fix/8587-cu-picker has succeeded. Run started by GitHub user mengw15 (triggered by mengw15).
Head commit for run: 1db843014236ffbe93b754ca42db98cbae533057 / mengw15 <[email protected]> fix(frontend): make the computing-unit picker say which picker it is, and let its button be clicked Two pickers now sit side by side in the toolbar showing nothing but a name. The computing-unit trigger gains the deployment-unit icon its own dashboard tab uses, and its tooltip reads "Computing Unit: <name> (<status>)" — one tooltip on the control instead of one on the badge and another on the name, carrying the name the trigger ellipsises at 220px and the status the badge can only show as a colour. With nothing selected, both the trigger and the run button now name what is missing — "Computing Unit", as the warehouse side says "Warehouse" — instead of "Connect", so the pair reads the same way. The form view's run button follows, since it mirrors the canvas's disable conditions. That button was also disabled in exactly the state it exists for: the run button's guard ended in `selectedComputingUnit?.accessPrivilege !== Privilege.WRITE`, which with no unit selected compares against undefined and is therefore always true, so the button offered to connect and refused every click — leaving runWorkflow's create-unit branch unreachable, though the form view's comments describe it as the click target. The privilege is now only asked of a unit that exists; a unit the user may only read still refuses to run. The badge no longer claims "processing" when nothing is selected, which ant renders as a pulsing blue dot for work that is not happening. Closes #8587. Report URL: https://github.com/apache/texera/actions/runs/35316862956 With regards, GitHub Actions via GitBox
