• Quacksalber@sh.itjust.works
    1·
    1 month ago

    Aren’t those almost always race condition bugs? The debugger slows execution, so the bug won’t appear when debugging.

    • BlueKey@fedia.ioOP
      0·
      1 month ago

      Turned out that the bug ocurred randomly. The first tries I just had the “luck” that it only happened when the breakpoints were on.
      Fixed it by now btw.

      • leisesprecher@feddit.org
        1·
        1 month ago

        One of our customers does that. It happened multiple times already that one dev fixed an issue in production, and the next regular deployment overwrote everything.

        But fortunately, it’s just critical infrastructure and nothing important.

    • Lupec@lemm.ee
      1·
      1 month ago

      Lol my workplace ships Angular in debug mode. Don’t worry though, the whole page kills itself if a dubious third-party library detects the console is open. Very secure and not brittle at all! Please send help

      • Barbarian@sh.itjust.works
        0·
        1 month ago

        Blink-blink-blink. Blink. Blink. Blink. Blink-blink-blink.

        No, I don’t have something in my eyes, I swear I’m fine looks nervously at boss.

    • MultipleAnimals@sopuli.xyz
      1·
      1 month ago

      You can imagine how many node projects there are running in production with npm run. I have encountered js/ts/node devs that don’t even know that you should like, build your project, with npm build and then ship and serve the bundle.