Repository navigation
Conversation
4 of 8 tasks
1fanwang
force-pushed
the
fix-breadcrumb-uses-executed-workflow
branch
from
August 24, 2026 10:06
2f51a4a to
240301a
Compare
The execution breadcrumb read its self-link, name, version, project, and domain from the launch-plan identifier. When a launch plan name differed from its workflow name, the breadcrumb pointed at a workflow page that did not exist. Read the identity from the executed workflow and relabel the breadcrumb as Workflow Name. Signed-off-by: 1fanwang <1fannnw@gmail.com>
Identical project and domain values let the self-link test pass even when it read the launch-plan identifier. Separate every identity so the route assertion covers project and domain as well as the workflow name. Signed-off-by: 1fanwang <1fannnw@gmail.com>
1fanwang
force-pushed
the
fix-breadcrumb-uses-executed-workflow
branch
from
August 24, 2026 10:28
240301a to
c8ac8f0
Compare
Signed-off-by: 1fanwang <1fannnw@gmail.com>
Signed-off-by: 1fanwang <1fannnw@gmail.com>
Contributor
Author
|
@Sovietaced could you review when you have time? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Read then delete this section
Release version rules
TL;DR
An execution's workflow breadcrumb can use the launch plan's project and domain instead of the workflow's. The detail link, version menu and full-version-list link now use the workflow that ran. Direct task executions keep their task names and versions.
Type
Are all requirements met?
Complete description
The detail link and version menu use the workflow identifier in the execution closure. The version request uses that workflow's project and domain too. Direct task executions still use the task identifier.
Testing Done
I ran the breadcrumb functions against a local HTTP server returning protobuf execution and version-list responses. The product cache, HTTP client, protobuf decoder and version-request functions were unchanged. The execution, launch plan and workflow have different identities.
With Node 16.19.0 and the checkout's installed dependencies, save the source below as breadcrumb_repro.cjs in the repository root and run:
Reproducer source: breadcrumb_repro.cjs
The new version-menu case failed because the request used the browsing project and domain:
The HTTP server is a local substitute for FlyteAdmin. I did not run a full browser or live-backend smoke test. The regression suite above passed; ESLint and Prettier checks passed too.
Tracking Issue
N/A
Follow-up issue
N/A