Chris1320 / Chris1320/TagStudio-CreativeFlow-AutoTag
Upload rejected by Gemini. Classifying from metadata only. (Upload has already been terminated.)
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This happens on some assets being classified. This leads to less accurate classification due to the file being unavailable to Gemini.
Contributor guide
No contributing guide indexed for this repository
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
Start by reproducing classification for an asset that triggers the Gemini upload rejection and trace the upload-to-classification entry point. No files or tests are named in the issue, so locate the Gemini upload handling first. Done means affected assets are not classified from metadata only after an upload is terminated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100