Summary
In the Lumen AI explorer, the "Full data" checkbox overlaps the bottom-right of the SQL code editor instead of sitting cleanly above the results table.
Screenshot
Cause
In LumenEditor._render_pipeline (lumen/ai/editors.py) the controls row that holds the "Full data" toggle is absolutely positioned:
controls = Row(
styles={'position': 'absolute', 'right': '40px', 'top': '-35px'}
)
...
return Column(controls, table)
The top: -35px floats the controls row 35px above the table's top edge, which places it over the SQL editor that sits directly above the table.
Steps to reproduce
lumen-ai serve <dataset with more than 1,000,000 rows> so the query result hits the SQLLimit cap and the "Full data" toggle becomes visible.
- Ask the assistant to show the table. An exploration opens with the SQL editor and a results table.
- The "Full data" toggle overlaps the bottom-right corner of the SQL editor.
I reproduced this with a NetCDF dataset loaded as an XArraySQLSource (the 1M-row view triggers the limit), but it should reproduce with any source large enough to hit the cap.
Expected
The "Full data" toggle should sit within or just above the results table header without overlapping the editor.
Environment
- lumen 1.2.1.dev0 (main @ 7cc94fb)
- panel 1.8.10a0, panel-material-ui 0.9.1
- Python 3.14.3, macOS
Notes
A small change should fix it, for example adding top padding to the table area or reducing the negative top offset so the toggle no longer reaches into the editor. I can attach a screenshot showing the overlap.
Summary
In the Lumen AI explorer, the "Full data" checkbox overlaps the bottom-right of the SQL code editor instead of sitting cleanly above the results table.
Screenshot
Cause
In
LumenEditor._render_pipeline(lumen/ai/editors.py) the controls row that holds the "Full data" toggle is absolutely positioned:The
top: -35pxfloats the controls row 35px above the table's top edge, which places it over the SQL editor that sits directly above the table.Steps to reproduce
lumen-ai serve <dataset with more than 1,000,000 rows>so the query result hits theSQLLimitcap and the "Full data" toggle becomes visible.I reproduced this with a NetCDF dataset loaded as an
XArraySQLSource(the 1M-row view triggers the limit), but it should reproduce with any source large enough to hit the cap.Expected
The "Full data" toggle should sit within or just above the results table header without overlapping the editor.
Environment
Notes
A small change should fix it, for example adding top padding to the table area or reducing the negative
topoffset so the toggle no longer reaches into the editor. I can attach a screenshot showing the overlap.