[miinhho]

What is this PR for?

The server filters interpreter settings by the current user's permissions, so an empty list is a valid response. The New Note and Clone Note dialogs share a handler that unconditionally reads the first setting's name, causing a TypeError when no settings are available.

Use optional chaining to leave the default interpreter unset for an empty response while preserving first-setting selection for nonempty responses. An empty response also clears any previous selection and allows change detection to complete.

Add component tests for interpreter selection transitions and existing new/clone note naming behavior.

What type of PR is it?

Bug Fix

Todos

• Handle an empty interpreter settings response.
• Add regression tests and existing note naming coverage.
• Verify component tests and browser modal behavior.

What is the Jira issue?

• https://issues.apache.org/jira/browse/ZEPPELIN-6645

How should this be tested?

From zeppelin-web-angular:

npm run test:shell -- src/app/share/note-create/note-create.component.spec.ts

All 9 component tests pass. Coverage includes:

• Empty and nonempty interpreter lists.
• Selection clearing and recovery across responses.
• New note naming at root and nested paths.
• Maximum note numbering and clone numbering.
• Literal handling of regex metacharacters in source names.

For server-backed reproduction:

1. Configure permissions on all interpreter settings so a test user is authorized for none.
2. As that user, open New Note and Clone Note for a readable note.
3. Confirm neither dialog reports the TypeError and New Note leaves the default interpreter unset.
4. Check normal first-interpreter selection with an authorized user.

Questions:

• Does the license files need to update? No
• Is there breaking changes for older versions? No
• Does this needs documentation? No

[voidmatcha]

LGTM 👍

[voidmatcha]

Merged into master (237b067).