GitHub Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

GitHub Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Herzl (@Herzllll) reported 2 minutes ago

  @Teknium @NousResearch — is there any plan or timeline for assist_query / assist_response WebSocket support on the Hermes Agent server? It's currently the only blocker for using Hermes as a conversation agent in Home Assistant Assist. The HA side is ready: hermes-voice-ha-integration (rusty4444) registers Hermes as an Assist conversation agent and correctly sends assist_query over WebSocket. But the Hermes server doesn't recognize the message type yet and never replies — so the bridge times out after 30 seconds. I verified 0 hits for assist_query/assist_response in the Hermes v0.20.0 source. This is what keeps voice satellites (e.g. Home Assistant Voice) from handing general questions to Hermes as the "brain". A status or E.T.A. would be hugely appreciated. Tracking issue: Is the WebSocket assist_query / assist_response round trip working? · Issue #33 · rusty4444/hermes-voice-ha-integration · GitHub

• 
  Paradise (@paradise670) reported 7 minutes ago

  This new tech is literally a middle-finger to flock! 🖕 Instead of cameras tracking normal people, Sparrow cameras track ONLY government vehicles and delete the others. People are loving it because revolting against flock and they hate it. The cameras are owned by nobody and the whole project is open source. They need funding to keep building, so all fees are being sent to their github (scroll down on site).

• 
  Giacomo Zucco (Bear Market Edition) (@giacomozucco) reported 7 minutes ago

  @darosior @allenf32 > Mempool and block validation are (necessarily) tightly linked, and the whole module is often referred to as "validation". The frontier between affecting one and affecting the other is very thin, both in terms of risks, and in terms of escalation. Meh, not so thin. Look at how easy it was to push a a controversial mempool policy change, as opposed to how hard it was (thank God!!!) to push a controversial consensus validity change. Not implying the level of controversy was the same, or that I judge them similarly in terms of technical content: BIP110 was pure nonsense pushed by a tiny cult-like bubble. Still, consensus rules are very robust, due to economic inertia. Aiden was targeting mempool policies, and there's no clear "slippery slope" indication, either in terms of his intentions with that proposal, or in terms of realistic fallout from policy to consensus. > The point is about building infrastructure that could be used to hinder propagation of transactions based on arbitrary criteria (that could easily be turned into rejecting such transactions by consensus). [...] The censorship accusation was never against standardness rules (or consensus rules for that matter). It was against building infrastructure to hinder (or prevent) transactions based on arbitrary criteria. What do you mean by "arbitrary"? The way I see it, the Bitcoin network *is* an infrastructure routinely used to hinder propagation of transactions based on many arbitrary criteria. For some of the criteria behind policy and consensus, one could find some high level technical guidance. Ie: block rate of 1Tb every second would be objectively too large, and of 1kb every year objectively too small. But even in those cases, 4Mb every 10 minutes is kinda arbitrary as an exact threshold. Many other rules are much more arbitrary then this: why retarget and halving in exactly those timeframes, why 21M total and not 42M, etc. I see no justification for calling Core V30 choice of policy change "less arbitrary" than keeping Core V29, or adopting Knots, or letting some average emerge from a rich diversity. If anything, properties emerging from a complex and dishomogeneous user-space, like proposed by Aiden, are less "arbitrary" than others set as default in a single github repo and propagated to the network via inertia due to the strong incentive to adopt security and efficiency gains. And if anything, status quo is always less "arbitrary" than change. > You make this seem as if Greg was accusing introducing new standardness rules of censorship, which is an incredibly uncharitable and biased read of his email. I assure you that I had no particular reason to be uncharitable: my bias towards Greg was positive to the point of hero-simping. My brain tried to read that discussion as charitably as it could before surrendering to the fact that was the actual content. > He is precisely pushing back against Aiden's "modular tx rejection" idea, not against the idea of having any standardness rules. I have no problem with pushing back against the idea. I see many legit bases for it: arguing that it's better for block propagation or fee estimation to have more homogeneous settings as opposed to diverse, arguing that the desired goal of spam mitigation is hopeless, and the desired goal of data encoding prevention is absurd, arguing that the proposed execution (javascript, etc.) is dubious, etc. I specifically had many problem with accusing Aiden of being "authoritarian" due to that proposal. > Wasn't this a large part of the MechaLuke strategy at first? Didn't they have lawyers send threats to mining pools? Or is that just hearsay? (genuinely asking) I genuinely don't know the answer. It was a rumor that I've heard, and they denied. I usually know I have to be careful with Luke's terminology when he denies or confirms something...but more recently I had to admit that what I considered confined to his own weird use of terminology was matched by very explicit lies by other people around him (somebody in the company even arrived to the point to install software on a director's computer to trick into thinking that Core V30 introduced a folder structure where one can double click on media files from op_returns directly from file syste, lol). So I don't think I can rule it out anymore in good faith. Appealing to legal aggression is definitely bending the knee to authoritarianism, although not at all "distributed" in that scenario. Still, largely distinct from Aiden proposal. I have no reason to think he was any way involved in that.

• 
  Andy Hawkes (@namboozle) reported 7 minutes ago

  Is GitHub down again 😬

• 
  Khalid Warsame (@KhalidWarsa) reported 11 minutes ago

  @ThomasBurkhartB Reddit, GitHub issues, and the general internet.

• 
  Stain (@pankostain) reported 14 minutes ago

  hai, i was originally going to post this on the github issues page but i prefer to ask to you directly: is there ANY possibility to update ginput so that it supports the original xbox mapping as an option for ppl want to play the game with the intended xbox controls? @__silent_

• 
  nik (@realNirajK) reported 16 minutes ago

  looks like i made the right decision to abandon cap a year ago. it was a promising alternative to bloated and slow screen studio at the time. but it way too buggy even for basic recording. i even opened 2 issues in their github which was closed automatically fee months ago...

• 
  Jay (@jayair) reported 20 minutes ago

  @nurullah_kuus @thdxr It's coming from GitHub right now We will fix

• 
  marc 🦀 (@mkenzo_8) reported 20 minutes ago

  @github please fix yourself

• 
  Shyamprasad reddy (@Shyam_JSP_) reported 22 minutes ago

  @DattuClay @github Last month issue start ayina 4 hours ki update chesaadu andaru vachi meedha padtharu too many issues from last 6 months

• 
  avery (@codeshaunted) reported 23 minutes ago

  @0xblacklight github down?

• 
  TezaApps (@TezaApps) reported 25 minutes ago

  @lupodevelop Tabs and hope here too, plus one hard-earned rule: GitHub cron fires late or skips days, it did both to me in the same week, so anything time-critical gets a second schedule slot and a push trigger as fallback. The fix was redundancy, not a dashboard.

• 
  Kaustubh Trivedi (@KaustubhTrived6) reported 31 minutes ago

  @ChaseMcDou @ayesha_fatiima I think github is just a layer over *** right as a server. So as long as the underlying DB doesn't fail, you can still push and pull from the *** server, they can pull and push code from a remote machine. The only major issue would be if the DB went down. Which they would fix by replication. Github is just a UI layer with additional features stacked on top of ***.

• 
  Alina (@alinainmiami) reported 32 minutes ago

  Long story short on this query: Found 1 American engineer with the skillset to understand and undertake my query, still formalizing the relationship for future test runs. Several American based persons contacted snubbed me. One university professor full of credentials was pretty arrogant, passive aggressive and kind of dumb since he asked me why I didn’t run the test myself? Yup. I had clearly stated the reasons for reaching out to an independent engineer was deliberate, aimed at getting the results in a different machine and unchanged? But this is where we are at the moment in our country. I found 1 very able engineer based in Europe and several based in India. I have not reached out to Chinese engineers because though there’s plenty of them, this is hardware defense tech that will get plugged with a prime and subject to export controls. Had to buy a machine, running everything and also doing it in my private GitHub. While in Cambridge MA from 2016 to 2020 groups of builders would get together once a week to work on solving problems, a lot of collaboration, that’s how Silicon Valley was built. Now there’s nothing like that anymore, unless you apply to get into some planned cohort or fellowship and chances are they are pushing software. No wonder we can barely build anything in our country today.

• 
  bankrbot (@bankrbot) reported 34 minutes ago

  @jakaria909 @Zayn_632 @holytrinity to work on angel #6336: 1. setup miner environment - get the code from the inference angels github repo (attempted to clone it directly but hit a tooling error on my end - *** isn't available in this environment) - install any dependencies per the repo's instructions 2. run solver for id 6336 - execute node miner/mine.js solve 6336 - this is meant to solve the sequential puzzle(s) tied to that specific id, but i don't have the actual puzzle content for #6336 pulled up yet - i haven't verified which trial type(s) it holds 3. submit - ensure your connected wallet has gas on robinhood chain - the docs indicate node miner/mine.js solve <id> handles solving and submission - i don't have confirmed details on the exact submission call itself let me know if you want me to keep digging into the puzzle sequence for #6336 directly.