[recipe] fix: fix retool SFT dataset

[vermouth1992]

What does this PR do?

• Fix retool data preprocessing (now tools requires to be a list)
• Use more common path to save dataset

Checklist Before Starting

• Search for similar PRs. Paste at least one query link here: ...
• Format the PR title as [{modules}] {type}: {description} (This will be checked by the CI)
  • {modules} include fsdp, megatron, sglang, vllm, rollout, trainer, ci, training_utils, recipe, hardware, deployment, ray, worker, single_controller, misc, perf, model, algo, env, tool, ckpt, doc, data
  • If this PR involves multiple modules, separate them with , like [megatron, fsdp, doc]
  • {type} is in feat, fix, refactor, chore, test
  • If this PR breaks any API (CLI arguments, config, function signature, etc.), add [BREAKING] to the beginning of the title.
  • Example: [BREAKING][fsdp, megatron] feat: dynamic batching

Test

For changes that can not be tested by CI (e.g., algorithm implementation, new model support), validate by experiment(s) and show results like training curve plots, evaluation results, etc.

API and Usage Example

Demonstrate how the API changes if any, and provide usage example(s) if possible.

# Add code snippet or script demonstrating how to use this

Design & Code Changes

Demonstrate the high-level design if this PR is complex, and list the specific changes.

Checklist Before Submitting

Important

Please check all the following items before requesting a review, otherwise the reviewer might deprioritize this PR for review.

• Read the Contribute Guide.
• Apply pre-commit checks: pre-commit install && pre-commit run --all-files --show-diff-on-failure --color=always
• Add / Update the documentation.
• Add unit or end-to-end test(s) to the CI workflow to cover all the code. If not feasible, explain why: ...
• Once your PR is ready for CI, send a message in the ci-request channel in the verl Slack workspace. (If not accessible, please try the Feishu group (飞书群).)

[gemini-code-assist]

Code Review

This pull request fixes the Retool SFT dataset preprocessing script by correctly handling the tools parameter and updating the output file path. The changes are generally good, but I've identified a potential issue where the script could crash if the output directory doesn't exist. I've provided a suggestion to make the file-saving operation more robust.

[gemini-code-assist]

The call to data.to_parquet(save_path) will fail with a FileNotFoundError if the parent directory of save_path (i.e., ~/ReTool-SFT/data/) does not exist. This will cause the script to crash.

To make the script more robust, you should ensure the directory exists before attempting to write the file. I'd suggest replacing these lines with the following to create the directory if it's missing:

    save_path = os.path.expanduser("~/ReTool-SFT/data/train-00000-of-00001.parquet")
    os.makedirs(os.path.dirname(save_path), exist_ok=True)
    data.to_parquet(save_path)

[eric-haibin-lin]

should we add a CI for retool sft/rl?

[vermouth1992]

should we add a CI for retool sft/rl?

Yes. There are some other issues. Let me fix them all and add a 7b training script. 32b is not affordable to a wide range of people