Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Search bar autocomplete stops working after a model appears in the suggestions

Open Beginner friendly
  • Is something wrong?
#8,700 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
frontend, search

Research direction

Start in SearchBarComponent.convertToName in search-bar.component.ts and trace the switchMap subscription that feeds the dashboard search bar. Reproduce with a model result, then verify that model suggestions are named and that a failed request or unnameable row does not prevent the next keystroke from searching.

Written by the indexing model from the issue text.

Description

What happened?

Once a model shows up among the dashboard search bar's suggestions, autocomplete stops working for the rest of the session. Later keystrokes never reach the server, and the dropdown stays empty until the page is reloaded.

Root cause. The search bar searches every resource kind (type = null, so resourceType=""). Since #7930 the backend's all-kinds query unions in models, and SearchService.search keeps rows with a model payload. SearchBarComponent.convertToName only names workflows, datasets and files. On a model row it throws Unexpected type in SearchResult.. That throw happens inside the switchMap feeding the search bar's long-lived subscription, and the subscription has no error handler, so the error ends it for good.

Before:  type "my" -> results include a model -> convertToName throws -> subscription errors
         type anything else -> nothing happens (subscription is closed)
After:   type "my" -> model listed by name
         a failed request or unnameable row -> no suggestions for that query; the next keystroke still searches

Any HTTP failure on the search request ends the same subscription the same way, because both HTTP interceptors rethrow. That includes a 5xx, a dropped connection, or a 401.

Expected: model hits are listed by name, and one bad response costs only that query's suggestions.

How to reproduce?
  1. Log in and make sure at least one model you can see matches a keyword, e.g. a model named my-model.
  2. Type my into the dashboard search bar. No suggestions appear, and the browser console logs Error: Unexpected type in SearchResult.
  3. Type a keyword that only matches a workflow. Still no suggestions, and no new dashboard/search request goes out.
Version/Branch

1.4.0-incubating-SNAPSHOT (main)

Commit Hash (Optional)

d102e26978cf0a377992b7d3ded03eaccd5d5c75

What browsers are you seeing the problem on?

No response

Relevant log output
Error: Unexpected type in SearchResult.
    at SearchBarComponent.convertToName (search-bar.component.ts)
Dominant language
Scala
Stars
316
Forks
189
Avg merge
4d 6h
Merged PRs (30d)
161

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/texera

All issues in apache/texera

Similar issues

More Scala issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.