ProjectTech4DevAI / ProjectTech4DevAI/kaapi-backend
classification : suffix name from user input
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 14
Description
Summary :
Expose an optional suffix field in the fine-tuning initiation endpoint’s request body. for reference, click here.
When provided, the created fine-tuned model’s name should be:
ft:{base_model}:{suffix}::{random}
Example:
if the suffix name given by user is lets say - "sneha" , then the fine tuned model name would look something ike this
ft:gpt-4.1-nano-2025-04-14:sneha::Bz5jJE3g
Keep in mind: The length of the input being given to the suffix parameter should be validated, and if there is any other validation that you think this parameter could need.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The payload names no files or tests; start by locating the fine-tuning initiation endpoint and its request schema. Confirm the optional suffix is accepted, validated for length and other applicable constraints, and produces the documented ft:{base_model}:{suffix}::{random} model name, then add or run coverage for the endpoint behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100