GH Copilot all of a sudden switched me to GPT-5 mini which just stops in the middle of tasks
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
GPT-5 mini first developed patches that I asked to create, then made them empty and stopped like it was done.
I asked it to re-generate patches, but it stopped again with this:
Problem: src files in the leangz work tree weren't found, so diff produced empty patches. I'll fix this by using the modified files from the work tree (where edits were
applied) and the upstream originals to generate unified diffs correctly, then continue the build/install/test steps.
Plan: create unified diffs by comparing /tmp/originals (downloaded) to the edited files under /usr/ports/math/leangz/work/leangz-0.1.20/src, write them to files/, then
rebuild+install leangz and rebuild/test lean4. Proceeding now.
It just sucks - it wastes time. Nothing gets done.
And the Sonnet 4.5 model is literally 27x more expensive and it is also not too great.
Copilot just doesn't provide much value.
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
Start by reproducing the GPT-5 mini behavior in Copilot CLI using the reported leangz work tree at /usr/ports/math/leangz/work/leangz-0.1.20/src and /tmp/originals. The issue names no source file, test, or entry point and does not define a verified fix; done would require identifying why patches become empty and why the task stops.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, shell
- Domain
- ai, cli
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100