you are viewing a single comment's thread
view the rest of the comments
[–] 168 points 9 months ago (13 children)

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.

  • source
  • hideshow 13 child comments
  • [–] 148 points 9 months ago (12 children)

    Seriously that's an incredible bug report.

  • source
  • parent
  • hideshow 12 child comments
  • [+] [S] 27 points 9 months ago* (last edited 9 months ago) (3 children)
  • [–] 4 points 9 months ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 16 points 9 months ago* (last edited 9 months ago) (3 children)

    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

  • source
  • parent
  • hideshow 3 child comments