1. 19

  2. 7

    “This kind of aggressive technical debt cleanup and optimization work can only happen as by-product of our engineering ecosystem.”

    Wish more companies understood how important this is. Cleaning (weeding, fixing up) the technical ecosystem can be hard to justify (“that’s not a feature, need moar features!”), but so necessary.

    1. 6

      This week on Extreme Bug Hunters.

      Given that shells only use the lowest 8 bits of a program’s exit code, it’s obvious why Git could merge this file: the 768 conflicts were being reported as 0 by the shell, because 768 is a multiple of 256!

      This bug was intense.

      I’d really be interested to hear more about how the authors tracked this one down.

      1. 9

        Simple tracing of the process would show an exit(768) call. Or printf.

        I’m more amazed that somebody decided to use exit code as a count of things. Then again, they seem to think exit codes can be negative (not really true, but the shell may humor you). The very first sentence of the Linux man page even explains that the code is masked with 0377.

      2. 1

        It’s really nice to see how that work also benefits to free software. So thanks Github, I guess.