Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Bug]: nvpair-tui panics (index out of range) in Nodes table renderer on first node discovery

Aperta
  • Qualcosa non va?
#46 2 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 5 giorni

@Noah-Tervalon-Nvidia ci sta già lavorando.

Dal 11/9/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Summary

nvpair-tui panics with an index out of range error in the Nodes-tab table renderer shortly after starting, once it discovers at least one node on the network. The panic is unrecoverable and kills the TUI (bubbletea's panic recovery catches it and shuts down cleanly, but the interface exits rather than staying usable).

Environment

  • PAIR version: 0.1.1 (NVPAIR-Setup-0.1.1-amd64.deb)
  • OS: Linux Mint 22.3 "Zena" (Ubuntu 24.04 Noble base), x86_64
  • Install method: official .deb package (sudo apt install ./NVPAIR-Setup-0.1.1-amd64.deb)
  • Invoked via: nvpair (the installed CLI wrapper, which execs /opt/PAIR/resources/cli-bin/nvpair-tui), run over SSH in a fresh tmux session (no desktop app running at the same time)

Steps to reproduce

  1. Install the .deb release on a machine with at least one Ollama or LM Studio engine reachable on the LAN.
  2. Run nvpair (or nvpair-tui directly) from a terminal — no $DISPLAY, purely headless/SSH.
  3. Wait for it to discover a node on the network (its own local node, or another one).
  4. The TUI panics and exits within a few seconds of a node appearing.

Actual behavior

Caught panic:

runtime error: index out of range [0] with length 0

Restoring terminal...

goroutine 1 [running]:
runtime/debug.Stack()
	runtime/debug/stack.go:26 +0x5e
runtime/debug.PrintStack()
	runtime/debug/stack.go:18 +0x13
github.com/charmbracelet/bubbletea.(*Program).recoverFromPanic(0x37925edde3c0, {0x5f70c0, 0x37925edd0108})
	github.com/charmbracelet/[email protected]/tea.go:847 +0xac
github.com/charmbracelet/bubbletea.(*Program).Run.func2()
	github.com/charmbracelet/[email protected]/tea.go:638 +0x10c
panic({0x5f70c0?, 0x37925edd0108?})
	runtime/panic.go:860 +0x13a
github.com/charmbracelet/bubbles/table.(*Model).renderRow(0x37925ee54010, 0x0)
	github.com/charmbracelet/[email protected]/table/table.go:431 +0x7a5
github.com/charmbracelet/bubbles/table.(*Model).UpdateViewport(0x37925ee54010)
	github.com/charmbracelet/[email protected]/table/table.go:279 +0x135
github.com/charmbracelet/bubbles/table.(*Model).SetRows(...)
	github.com/charmbracelet/[email protected]/table/table.go:315
nvpair-tui/ui.(*nodesView).setNodes(0x37925ee54008, {0x37925edb2960, 0x1, 0x5c3680?})
	nvpair-tui/ui/nodes.go:193 +0x37f
nvpair-tui/ui.(*nodesView).Update(0x37925ee54008, {0x5da820?, 0x37925edb2900})
	nvpair-tui/ui/nodes.go:111 +0x108
nvpair-tui/ui.(*Model).broadcast(0x37925f01b6e8, {0x5da820, 0x37925edb2900})
	nvpair-tui/ui/model.go:158 +0xcd
nvpair-tui/ui.Model.Update({0x37925edd4190, 0x37925edc9260, {{{0x37925edacf60, 0x3, 0x3}, {{...}, {...}}, 0x0}, {{0x37925edacf90, 0x3, ...}, ...}, ...}, ...)
	nvpair-tui/ui/model.go:108 +0xd7
github.com/charmbracelet/bubbletea.(*Program).eventLoop(0x37925edde3c0, {0x621940?, 0x37925ee34008?}, 0x37925ed9a310)
	github.com/charmbracelet/[email protected]/tea.go:494 +0x7ce
github.com/charmbracelet/bubbletea.(*Program).Run(0x37925edde3c0)
	github.com/charmbracelet/[email protected]/tea.go:716 +0xae7
nvpair-tui/ui.Run(0x37925edd4190, {0x620c40, 0x37925ed820d0})
	nvpair-tui/ui/ui.go:26 +0x145
main.main()
	nvpair-tui/main.go:73 +0x419
13:43:29.800 [nvpair-tui] ERROR ui error err="program was killed: program experienced a panic"
13:43:29.816 [nvpair-tui] INFO shutdown complete

Expected behavior

The Nodes tab should render the discovered node(s) without crashing.

Notes

The trace points at nodesView.setNodes (ui/nodes.go:193) calling into bubbles/table's SetRows/UpdateViewport/renderRow, which panics on a table with zero configured rows/columns receiving row data — looks like the nodes table's columns/dimensions aren't initialized before the first setNodes call lands from broadcast. Didn't find an existing issue for this via search, apologies if it's a duplicate.

Happy to provide more logs/details if useful.

Lingua principale
Go
Stelle
1.6k
Fork
266
Merge medio
3g 6h
PR unite (30g)
22

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di NVIDIA/Personal-AI-Router

Tutte le issue di NVIDIA/Personal-AI-Router

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.