Martijn Visser created FLINK-40031:
--------------------------------------
Summary: Exceptions view crashes (NG04008) navigating to an
unassigned TaskManager
Key: FLINK-40031
URL: https://issues.apache.org/jira/browse/FLINK-40031
Project: Flink
Issue Type: Bug
Components: Runtime / Web Frontend
Reporter: Martijn Visser
In the job Exceptions view, clicking the Location cell of an exception that has
no
assigned TaskManager throws:
{code:html}
NG04008: The requested path contains undefined segment at index 1
at JobExceptionsComponent.navigateTo (job-exceptions.component.ts)
{code}
Root cause: {{navigateTo(taskManagerId)}} guards only {{{}taskManagerId !==
null{}}}, but the value is {{undefined}} for unassigned exceptions, so it calls
{{{}router.navigate(['task-manager', undefined, 'metrics']){}}}. The
{{ExceptionInfo }}interface (job-exception.ts) also types {{taskManagerId:
string}} when the REST API can omit it.
Pre-existing (identical on master); not caused by the Angular 21 upgrade in
FLINK-40028,
which is where it was noticed.
Fix: guard with a falsy check ({{{}if (taskManagerId){}}}) and type the
field/param
{{{}string | null{}}}. Check application-exceptions for the same {{navigateTo}}
pattern.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
