Skip to content

Ask a question

How to get help with Tuneline Studio, and how to ask so that someone can answer quickly.

Check the docs first

Many problems have a known fix:

  • Troubleshooting lists common errors (runs that stay in launching, Kaggle refusing to start, out-of-memory errors, gated models, an offline computer) and what to do about each.
  • The FAQ answers common questions about costs, keys, models and where runs happen.
  • The run page itself often tells you: the failed step is red, and its message says what went wrong.

What to include in your question

A good question lets someone reproduce or recognize the problem without asking you for more details. Include:

Include Where to find it
The run number (for example Run #12) and its status The run page header, or the Runs page.
Where it ran (Kaggle, Notebook, My computer, Modal, RunPod or Hugging Face Jobs) and the GPU The run page header.
The template or a short description of the pipeline The pipeline's name and the template it came from. The YAML tab has the whole pipeline as text.
The failing step and its message The red step on the run graph, or the banner above the pipeline canvas.
The relevant log lines, usually the last 20 to 50 lines of the failing step The run page's Logs tab: filter by the step, then select Download for the full log.
For My computer runs: your operating system, GPU, and the output of tuneline doctor Run & "$env:USERPROFILE\.tuneline\venv\Scripts\tuneline.exe" doctor (Windows) or ~/.tuneline/venv/bin/tuneline doctor (macOS / Linux). The worker's log on Windows is %USERPROFILE%\.tuneline\worker.log.
What you expected and what happened instead Your own words.
What you already tried For example, "retried with QLoRA turned off".

Never share secrets

Before you post anything, check that it contains no keys or tokens. Treat all of these as secrets:

Looks like What it is
hf_... A Hugging Face access token.
tlw_... A Tuneline worker token, in the setup file and install command for your computer.
tlr_... A Tuneline run token, in run commands and downloaded notebooks.
Keys for Modal, RunPod, Kaggle, Weights & Biases or an OpenAI-compatible API Your provider keys.

Tuneline never prints key values in its logs, but commands you copied, notebooks you downloaded and setup files do contain tokens. Replace them with ... before you share. If you think a secret leaked:

  • delete the provider key in Settings → API keys and revoke it in the provider's console;
  • remove the computer in Settings → Your computers and add it again, which invalidates its worker token.

Where to ask

Ask on the project's issue tracker.

  • Bug reports: something doesn't work as documented. Include the details from the table above.
  • Questions: how to do something, or whether Tuneline can do it.
  • Feature requests: describe the problem you want to solve, not only the solution.

Search existing issues first: someone may have asked already.

If you use a Tuneline site run by your organization, contact the person who operates it for account, sign-in and email problems, since those depend on how that site is set up.

Reporting a security problem

If you find a security vulnerability, don't post it publicly. Contact the maintainers privately through the issue tracker's private reporting option, or the contact listed there.