[Bug]: renaming a provider kills in-flight work in every thread using it
Open
Nobody has claimed this yet.
accepted
bug
via-triage
- Dominant language
- TypeScript
- Stars
- 23k
- Forks
- 5.9k
- Avg merge
- 11h 14m
- Merged PRs (30d)
- 357
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
Not sure
Steps to reproduce
- Have one or more threads actively running against provider X.
- Go into settings and delete provider X, or edit its name.
- Return to the threads.
Expected behavior
running threads finish their current turn; the provider record is looked up by a stable ID, so a rename is cosmetic. At worst, a warning before deleting a provider that has active threads.
Actual behavior
all work in every thread on that provider stops.
Impact
Blocks work completely
Version or commit
No response
Environment
No response
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
No response
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 at the settings flow for renaming or deleting a provider, then trace how active threads look up and use that provider. Done means a regression test or reproduction shows that an active thread finishes its current turn after a rename, while the deletion behavior matches the chosen handling for active threads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100