It was shared on GitHub on Sunday July 22 by lemmy.ca staff. Developers who run the project do not seem to do merges on Saturday and Sunday. I submitted a pull request Sunday evening given the server crash relief this would provide, ready for them first thing Monday. I clearly labeled the pull request as “emergency”.

It is well into Wednesday and merges are being done on new site features for for the past 3 days. Yet, server crash pull request was edited to remove “emergency” from description first thing Monday and sits without any urgency attention.

This is the same pattern I saw for the past 2 months regarding server crashes related to PostgreSQL.

  • RoundSparrowOP
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Day 62, fresh from GitHub, it’s got to be social hazing at play, right?

    • RoundSparrowOP
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      I’ve really never encountered social hazing like this being played on the entire Twitter, Reddit community coming to Lemmy. It’s so unusual to witness the bragging of “high performance” and “full delete” while behind the scenes this kind of attitude towards constant server crashes is going on.

      Somehow it is a social hazing game where performance is cited, but the fact that nobody looked at the broken TRIGGER for 60 days while servers were crashing - code readability and attention on the “bomb”… isn’t a social factor of the developers and project leaders. But the social hazing of the entire Twitter and Reddit communities coming to Reddit seems more likely to explain the responses. Servers were crashing with PostgreSQL hangs and overloads, and for 60 days nobody looked at the TRIGGER statements and saw an obvious problem with a wide-open runaway UPDATE lacking a WHERE clause.