Skip to main content

Browsing files

Results live on a shared storage. QA-Board serves its files under /s/: the folder /mnt/qaboard/my-project/outputs is at https://<qaboard>/s/mnt/qaboard/my-project/outputs/. When you open a folder in your browser, you get QA-Board's file browser. You land there from the folder icons of the web app (e.g. on each run's card), from the links printed by the qa CLI, or by typing a path.

The file browser in the images folder of a detector run: the path as breadcrumbs, the run bar, a filter box, and 25 images sorted naturally, 1.jpg, 2.jpg, then 10.jpg after 9.jpg, with their sizes and dates.
A run's output folder: 2.jpg comes before 10.jpg, and every file has its size and date.

What you can do​

  • Navigate: click a folder, or a part of the path at the top. The browser's back and forward buttons work, and links open in new tabs as usual.
  • Go to a path: click next to the path at the top, or press g, and type or paste a Linux path, a Windows path (\\server\share\...) or a QA-Board URL.
  • Copy paths: Copy path and Windows at the top copy the folder's path. Hover a file to copy its path, or download it.
  • Filter: type part of a name, or a glob like *.png or frame_??.raw. Hidden files (starting with .) are not shown, unless they match the filter or you click the eye icon.
  • Sort: click a column's name. Folders always come first, and names are sorted "naturally": frame2 comes before frame10.
  • See more: hover a size for the exact number of bytes, a date for the exact time, and a name for its permissions (and where a link points to).

Files open in the browser, exactly as before: nginx sends them, so large files and logs load fast.

Runs​

In a run's output folder, or in a folder inside it, a bar shows the run: its status, the input it ran on, its batch and who started it. From there you can:

  • open its Results (metrics, logs...) in QA-Board,
  • Redo it, e.g. after a failure. Its files are replaced when it starts again,
  • Delete it: its folder and its results in QA-Board. Check Only delete its files to keep the run in QA-Board, like "Delete Output Files" in the web app,
  • Mark as failed a run stuck as pending or running, whose job is gone.
The run bar above a run's files: Done, run on profiles/steady-high.yaml on linux by ci, and the Results, Redo and Delete buttons.
In a run's folder, the run bar says which run it is and how it went, with Results, Redo and Delete at hand.

You need to be signed in. You act on whole runs, like in the web app: the file browser doesn't delete single files.

Keyboard shortcuts​

Press ? to see them all.

The keyboard shortcuts dialog of the file browser: filter, go to a path, next and previous, open, parent folder, copy the path, show hidden files, refresh.
Press ? anywhere in the file browser to list its shortcuts.
KeyWhat it does
/Filter. Enter opens the first match, Esc clears the filter.
gGo to a path
j k or ↓ ↑Select the next or previous file
Enter or →Open the selected file or folder
Backspace or ←Go to the parent folder, with the folder you were in selected
cCopy the path of the selected file, or of the folder
wCopy the Windows path
.Show or hide hidden files
rRefresh, e.g. while a run is writing files
j and k move through the files, / filters them, Enter opens the selection and c copies its path.

Restricted folders​

Your admins can restrict who can see the files of some projects or folders. If you see Sign in to see these files, sign in with the button. If you see You don't have access, ask them for access.

The plain index​

Scripts and tools like curl and wget still get nginx's plain index of the folders. To see it in your browser, click Plain index at the bottom of the page, or add ?view=nginx to the URL.