• marcos@lemmy.world
    link
    fedilink
    arrow-up
    33
    ·
    1 year ago

    The problem is, how do you fix it if you can’t make it break?

    The worst thing is when somebody comes to you saying “yeah, I had this problem yesterday, but it’s working now”.

    • Neshura@bookwormstory.social
      link
      fedilink
      English
      arrow-up
      21
      ·
      1 year ago

      this is a case for excessive logging man

      likely won’t help you actually fix the issue because miraculously you didn’t log the three variables you actually need but it’ll make you feel better in the meantime

      • kameecoding@lemmy.world
        link
        fedilink
        arrow-up
        8
        ·
        edit-2
        1 year ago

        and gives you some headroom in improving performance since it’s being choked by the excessive logging

      • folkrav@lemmy.world
        link
        fedilink
        arrow-up
        6
        ·
        1 year ago

        Fully agree, but they’re usually kind of annoying to track regardless. On the opposite side, sometimes even getting it to trigger on purpose to be able to add a regression test can be pretty tricky, depending on the cause. Timing or time/date based stuff is a common culprit…

        • ryannathans@aussie.zone
          link
          fedilink
          arrow-up
          5
          ·
          edit-2
          1 year ago

          Don’t tell me about time and date, I am still recovering from some moron that used datetime.now() for some unit test data setup and sometimes two records (which needed to have the same time) had very slightly varying time which caused all sorts of intermittent test failures that were very tricky to nail down. Database triggers were failing causing failures in all sorts of tests in a random fashion