Clicking a file in the dataset file tree leaves no visible trace: the picked row is never highlighted
I maintainer di solito rispondono entro 1 giorno
@yangzhang75 ci sta già lavorando.
Dal 16/11/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
What happened?
user-dataset-version-filetree is the file tree every dataset and model browser uses: the versions/files browser (on the dataset page and on the model page), the dataset-selection modal and the model-selection modal. Its click handler (actionMapping.mouse.click in user-dataset-version-filetree.component.ts) toggles a folder open and, for a file, emits selectedTreeNode to the host -- and does nothing else. It never calls the tree library's TREE_ACTIONS.ACTIVATE, so the tree never has an active node, the library never marks the clicked row, and the only sign that a file was picked is whatever the host does with the event.
On the dataset and model pages the host loads the file's preview, so the click has a visible result there. In the dataset-selection modal (file mode, used to pick a file for a UDF parameter) the host only stores the path (onFileSelected sets selectedPath): the clicked row looks exactly like every other row, and the one hint that a pick happened is the Select button turning enabled. A user clicking from file to file cannot see which one is current, and clicking a file that is already picked gives no feedback at all. In the model-selection modal the tree is not even bound to a handler, so a click there does nothing visible either.
Expected: the clicked file reads as picked -- the row is the tree's active node and is drawn like a selected row elsewhere in the app (the ant blue-1 fill with a blue accent that the dashboard's list rows and the workspace's selected cards use), on every host, including a re-click of the same file.
How to reproduce?
- Add a CSV File Scan (any operator with a
fileNameproperty, which renders as the dataset file selector) and click its Select File button: the dataset-selection modal opens in file mode. - Pick a dataset (its first version is selected for you) so the file tree shows; click a file, then another, then the first one again.
- No row stays highlighted after a click (only the tree library's hover tint shows while the pointer is over a row); only the Select button's enabled state changes. The tree behaves the same in the model picker, and in the UDF parameter's dataset picker (version mode, where a file click is not an answer at all and still looks like one could be).
Version/Branch
1.4.0-incubating-SNAPSHOT (main)
Commit Hash (Optional)
No response
What browsers are you seeing the problem on?
No response
Relevant log output
- Lingua principale
- Scala
- Stelle
- 333
- Fork
- 202
- Merge medio
- 3g 11h
- PR unite (30g)
- 185
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di apache/texera
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
addOperator returns an error but still adds the operatorForse già presa @sunny-kavixo l’ha presa 5 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
apache/texera#9121 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Failed tool calls are marked as succeeded (isError is always false)Forse già presa @oliarmak-web l’ha presa 14 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
apache/texera#9120 · 8 commenti · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
apache/texera#8682 · 5 commenti ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di apache/texera
Issue simili
-
? - Needs Triage bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
NVIDIA/cudf-spark#16937 ·
I maintainer di solito rispondono entro 1 giorno
-
LFST not-issued-store count truncation can incorrectly clear strictShouldWaitForse già presa @weidingliu l’ha presa oggi. Apertamodule: memory type: bug/reported
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
OpenXiangShan/XiangShan#6974 · 1 commento · 1 assegnatario ·
I maintainer di solito rispondono entro 3 giorni
-
bug indigo
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
PurpleKingdomGames/indigoengine#300 · 1 commento ·
-
JavaReservoirSampleOperator returns the whole input when the dataset size is unknownForse già presa @sasmith-14 l’ha presa 2 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
apache/wayang#884 · 3 commenti ·
I maintainer di solito rispondono entro 2 giorni
-
AI Generated CI/CD ⚒️ Flaky-tests 🐦 python 🐍
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
valkey-io/valkey-glide#7722 ·
I maintainer di solito rispondono entro 1 giorno