Yaak Logo
Yaak
Feedback/Missing output in the response window

Missing output in the response window

nervocalm ·3 months ago
Needs ReproductionBug

The output shows only the first two columns (even when selecting RAW):


with no scroll bar or possibility to move horizontally.
As far as I know by the interface I only get to columns in this response
If I export this, I get the 9 columns that must show here

Linux2026.1.2

Comments (3)

Sign in to leave a comment.

Gregory SchierNeeds Reproduction

Hmm, I do see a horizontal scrollbar when I try it myself. Are you able to paste the CSV you’re using? (or a small sample)

I just fixed the “Raw” view too. This mode will correctly show the raw text in the next release.

image
nervocalm OP

It is weird because I do call another endpoint in the same API, and only the simplest one has this issue; the other, more complex one is shown “OK” (maybe because this one is a mess, and it’s returning JSONs inside .csv fields and it can’t be rendered OK). image

As you can see, here I also get the horizontal scrollbar.

I leave you here the “problematic one.” It’s exported from Yaak history, and, as you can see, it has all the columns, even when they aren’t showing in the GUI.

I tried even with the horizontal layout, and I can’t see either the rest of the columns or the horozontal scrollbar: image

Maybe there is some issue with the WM or X11? This is what I am using:

Operating System: Manjaro Linux 
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.18.8-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 12 × 12th Gen Intel® Core™ i5-1235U
Memory: 16 GiB of RAM (15,4 GiB usable)
Graphics Processor: Intel® Graphics
Manufacturer: EXO S.A.
Product Name: Smart G12
System Version: ADL_P_IDL525_S_S3_V0.59.3
nervocalm OP

Today I tested v2026.2.4, and this issue still remains. The RAW view has worked OK since the 2026.2.1 update, but the “rendered” response still shows 2 columns. I tested it on Wayland and several window decorations (just in case), but I had the same result. I think the process reads the first row and assumes the return is a two-column output and renders the rest accordingly. I know this API is a little bit peculiar and applies this “header” to the output, which, in my opinion, is not the best practice. For me, it is not a big issue anymore since I mostly use the RAW view, but maybe it is good to fix it (or at least consider the case of an API like this).

Type to search feedback...