European programmers take an extended lunch break as GitHub goes TITSUP* again

All fixed now so get back to work

Big sack o' source GitHub is having a hellish week as the Microsoft tentacle suffered wobbles aplenty even as it tipped the scorn bucket over the emissions of the US administration.

Having fallen over in dramatic style on 21 April, seen its notifications totter on 22 April, and had trouble with Actions Workflows in the small hours of 23 April, the platform decided to take an extended lunch break today.

Twitter was its usual supportive self as developers found themselves faced with the dread error code 500 and a humorous depiction of the GitHub mascot tumbling into a ravine (like the unfortunate Wile E Coyote of Looney Tunes fame).

GitHub itself recognised that there were "issues" at 13:20 UTC. By 13:33 UTC, engineers reckoned they had found the source of the borkage and were hurriedly plugging the servers back in working on a fix.

Then again, we don't know too many developers who would refuse an extended luncheon (or extra morning coffee, depending on the timezone) so a short interruption may not be the end of the world. Access to Vulture Central, at least, seemed to return shortly before 14:00 UTC.

The issue looked to be global, although the timing meant that much of the US remained in blissful ignorance while Europe and the rest of the world wailed.

The issues come after GitHub made all core features of the platform available for everyone, declaring that "every developer on earth should have access to GitHub. Price shouldn't be a barrier."

Stability, on the other hand, does seem to have presented the house of code with a few issues recently, raising the unpleasant spectre of scalability. Certainly, new owner Microsoft has famously struggled to meet the recent unprecedented levels of demand on its own cloud.

As for the current topple?

Until, of course, the next time. ®

* Total Inability To Service User Pulls

Similar topics

Other stories you might like

  • Open source body quits GitHub, urges you to do the same
    Paid-for Copilot trained on FOSS code final straw for Software Freedom Conservancy

    The Software Freedom Conservancy (SFC), a non-profit focused on free and open source software (FOSS), said it has stopped using Microsoft's GitHub for project hosting – and is urging other software developers to do the same.

    In a blog post on Thursday, Denver Gingerich, SFC FOSS license compliance engineer, and Bradley M. Kuhn, SFC policy fellow, said GitHub has over the past decade come to play a dominant role in FOSS development by building an interface and social features around Git, the widely used open source version control software.

    In so doing, they claim, the company has convinced FOSS developers to contribute to the development of a proprietary service that exploits FOSS.

    Continue reading
  • Arrogant, subtle, entitled: 'Toxic' open source GitHub discussions examined
    Developer interactions sometimes contain their own kind of poison

    Analysis Toxic discussions on open-source GitHub projects tend to involve entitlement, subtle insults, and arrogance, according to an academic study. That contrasts with the toxic behavior – typically bad language, hate speech, and harassment – found on other corners of the web.

    Whether that seems obvious or not, it's an interesting point to consider because, for one thing, it means technical and non-technical methods to detect and curb toxic behavior on one part of the internet may not therefore work well on GitHub, and if you're involved in communities on the code-hosting giant, you may find this research useful in combating trolls and unacceptable conduct.

    It may also mean systems intended to automatically detect and report toxicity in open-source projects, or at least ones on GitHub, may need to be developed specifically for that task due to their unique nature.

    Continue reading
  • For a few days earlier this year, rogue GitHub apps could have hijacked countless repos
    A bit of a near-hit for the software engineering world

    A GitHub bug could have been exploited earlier this year by connected third-party apps to hijack victims' source-code repositories.

    For almost a week in late February and early March, rogue applications could have generated scoped installation tokens with elevated permissions, allowing them to gain otherwise unauthorized write or administrative access to developers' repos. For example, if an app was granted read-only access to an organization or individual's code repo, the app could effortlessly escalate that to read-write access.

    This security blunder has since been addressed and before any miscreants abused the flaw to, for instance, alter code and steal secrets and credentials, according to Microsoft's GitHub, which assured The Register it's "committed to investigating reported security issues."

    Continue reading

Biting the hand that feeds IT © 1998–2022