Somebody is closing unfixed bugs
What version of Codex is running?
n/a
What subscription do you have?
n/a
Which model were you using?
n/a
What platform is your computer?
n/a
What terminal emulator and version are you using (if applicable)?
n/a
What issue are you seeing?
We put effort into reporting bugs, so you can FIX them.
It is a rude slap-in-the-face F.U. to all of us when someone comes along and just does this to all of us:-
See https://github.com/openai/codex/issues/5588#issuecomment-3762676151
What steps can reproduce the bug?
spend hours working out why something does not work.
file a bug report for it.
watch while it does not get fixed.
observe someone closing the issue anyhow.
What is the expected behavior?
Honesty.
Do not close anything that's not verified as fixed.
Additional information
If this kind of deception over product quality exists, I shudder to think what other sketchy practices are taking place which we cannot see!
Do NOT close this issue, until all the improperly closed issues have been re-opened, and a process put in place to stop premature-closing taking place.
This is an AI product guys - it's not that hard to get it to check and verify bugs without humans having to lie about things!
3 Comments
@gitcnd, thanks for the feedback. We have a lot of older bug that do not have adequate repro steps or are likely no longer valid because of changes and fixes that have been introduced. We also have bug reports for issues that were affecting one user and are likely due to their unique configuration or setup. We want to focus our efforts on bug fixes that have the most impact for most users.
If you see a bug report that is closed but is still affecting you, let us know and I can reopen it.
How many other people's bug reports have you closed without fixing them?
You should NOT be doing this!
It is dangerous, dishonest, and disrespectful.
As a general rule, we close bug reports only if they've received no upvotes or additional engagement for over two months. That's a good signal that it's a stale issue — one that is no longer affecting users because it has been fixed, is no longer relevant, or was due to user-specific configuration issues rather than a real Codex problem. Old bug reports like this tend to require significant time to investigate and have very low rates of actually resolving. Effective issue management requires good triage and prioritization. We want to spend our time on the issues that matter most to our users. Keeping large numbers of stale bug reports open works against that goal.
As I said, if you're experiencing a bug that is described by a bug report that has been closed, let us know, and I'll reopen it.