Sorry for meeting such an asshole maintainer. I’d never do this, especially for someone who actually did the preparatory work to find the location of the bug.
I’ve changed some of the details so it’s not easily googlable because it’s linked to my RL identity. The bug is a purely cosmetic off-by-one error though. And I didn’t give any indication I thought it was important or urgent. But the concise description of the bug, reproduction steps, why I strongly suspect it’s happening, and where I strongly suspect the fix needs to be made were all included.
The maintainer’s comments are pretty much verbatim.
This happens every single time I try to file a good bug report, without exception. I suspect they see the woman’s name on my account and assume I have no idea what I’m talking about?
I’m working on a major website migration right now, and was literally hashing things out with timestamps yesterday. If I had to deal with encountering a 24th/no 0th-hour bug, I’d call up the old dev and ask them how they avoid shitting on their loved ones while being such a giant asshole. Make me fucking convert the hours to a number so that I can subtract by one, and then convert it back to a timestamp. I know it’s a simple solution, but I would have definitely first wasted hours trying to figure out why and which of my 50,000 posts was causing my migration to fail.
Point being, what you call a cosmetic error could singularly fuel my nightmares for a month. Shame on the maintainer for acting so indignant over what I now consider the kindest bug report of all time. I’m so grateful that users like you exist.
Sorry for meeting such an asshole maintainer. I’d never do this, especially for someone who actually did the preparatory work to find the location of the bug.
Seriously that’s an incredible bug report.
I’ve changed some of the details so it’s not easily googlable because it’s linked to my RL identity. The bug is a purely cosmetic off-by-one error though. And I didn’t give any indication I thought it was important or urgent. But the concise description of the bug, reproduction steps, why I strongly suspect it’s happening, and where I strongly suspect the fix needs to be made were all included.
The maintainer’s comments are pretty much verbatim.
This happens every single time I try to file a good bug report, without exception. I suspect they see the woman’s name on my account and assume I have no idea what I’m talking about?
Computer science used to be for women until men realised there was money in it, and now they act like women are too stupid to understand it.
I’m working on a major website migration right now, and was literally hashing things out with timestamps yesterday. If I had to deal with encountering a 24th/no 0th-hour bug, I’d call up the old dev and ask them how they avoid shitting on their loved ones while being such a giant asshole. Make me fucking convert the hours to a number so that I can subtract by one, and then convert it back to a timestamp. I know it’s a simple solution, but I would have definitely first wasted hours trying to figure out why and which of my 50,000 posts was causing my migration to fail.
Point being, what you call a cosmetic error could singularly fuel my nightmares for a month. Shame on the maintainer for acting so indignant over what I now consider the kindest bug report of all time. I’m so grateful that users like you exist.
For real!
And then, is 20260124-24:59:30 the morning of the 24th, or the 25th? Who knows?
Yeah, I’d buy that reporter a beer or something.
It’s starting to go from bug report to peer review. if she made the fix too, it’d be a fucking pull request
EDIT : Fix’d pronoun
He?
I made an assumption and didn’t see/realise their pronoun indicators. 🤷
Let’s less assumptions next time and then less mistakes :3
I wish the ones I get were half as good.
Then stop writing such obscure bugs?
You can’t tell them what to do! Submit a PR, if you’ve already figured it out