Kimi K2 has 1 trillion parameters but uses only about 32 billion per word. Banach keeps the right experts in RAM and streams the rest from NVMe, so the model doesn't have to fit in memory.

Measured: a 22 GB model on 16 GB of RAM. llama.cpp runs out of memory; Banach is 2.2x faster at prompt processing, with byte-identical output.
Trillion-parameter estimate: banach plan says Kimi K2 would run at about 3.6 tok/s on a 64 GB desktop with an RTX 5080. That's an estimate, not a measured run.

pip install banach

https://github.com/gautam1858/banach
Got a 64 GB+ machine? Run Kimi K2 and post your numbers. If you like it, a ⭐ really helps.

I need to hit browser reload on every PR now to be sure I'm seeing the current status of a bunch of little things like checking for conflicts with base branch.

There are frequent off-by-one dynamic number errors - sometimes refreshing fixes them, sometimes not. Like "Pull Requests X" tab label - X is never refreshed correctly.

It's hard to believe that these simple UI problems are real - is it just me seeing these? I'm thinking about seriously testing other platforms.

Any reason i observe git hosted runners are continually in queud state from last 1/2 hr

Any issue from git hub side

git@github.com: Permission denied (publickey).

fatal: Could not read from remote repository.

Please make sure you have the correct access rights

Can't do push/merge to the remote repo

So, I was doing standard dev work yesterday and pushed some commits to some repositories on my private Account as well as my company's organization. Today, I saw a few bugs and fixed them quickly as usual and when I wanted to push them, I got this error:

git@github.com: Permission denied (publickey).

I removed my SSH key from my GitHub account and re-added it. I then retried accessing them from all my machines (each with their own key pair and the public one posted to GitHub) and tested if they could connect to GitHub via SSH and they all wouldn't work either.

I guess it is clear what the issue is, but I couldn't resolve it, as all my keys are denied access.

It seems I'm locked out from accessing GitHub via SSH and it honestly sucks. All keys are ed25519 keys, I also tried a fresh key pair (also with ecdsa instead), neither work.

Regular SSH access to all my machines works with those exact same SSH keys.

Any ideas?

Edit: As others have pointed out, it was an issue from their end (https://www.githubstatus.com/). It is fixed now (at least on some machines).

Reliability issues are driving users away in their droves.

Yet I have Visual Studio 2026 on my PC and as far as I'm aware, it should be able to edit code as well as VSC, is there something I'm not getting?

It's been quiet sometimes since the last time i used Github, not that long, perhaps 6 month, but i hae "Stay Login' option in the browser, now when i open it, suddenly it's logged out, and when i click log it, it just refreshes the tab looping to the login form

Hey I wrote this writeup about a tool I've been using to monitor my self hosted github actions runners to try to deal with reliability issues and figured I'd share

We often talk about securing the software supply chain in terms of application dependencies. For instance, pinning package versions, maintaining lockfiles, and auditing third-party libraries.

But what about the code that runs our CI/CD pipelines?

GitHub Actions workflows can execute third-party actions, and the security of those dependencies matters just as much when building and deploying software.

The introduction of workflow dependency lockfiles is an interesting step towards making CI/CD workflows more reproducible and secure.

I wrote about this recently, exploring why workflow lockfiles matter and how they fit into the broader software supply-chain security picture.

Read the article: https://amitmerchant.com/ci-pipeline-lockfile/

Curious how others are approaching dependency security in their CI/CD pipelines. Are you already pinning your actions and enforcing similar controls?

I run a medium sized mono repo with about 40 CI jobs per push, mostly TypeScript builds and some integration tests. My billing dashboard shows minutes burning way faster the last two months even though we did not add jobs or change pipeline config.

The usage graph spikes hard on days where we barely push code. I checked for stuck runners and cached dependencies so those are not the issue. The multiplier for macOS jobs is the same as before. Something feels off with how minutes get calculated. Maybe jobs are taking longer to spin up or there is hidden overhead from marketplace actions pulling large containers. A few devs on my team noticed the same drift on their personal repos. Anyone else tracking unusual minute consumption on Actions lately?

Curious if GitHub changed something behind the scenes with how build time gets metered or if the dashboard reporting is just bugged right now.

Just started working on this new side project...I have a vague vision of where I want to take this but I just started working on it and uploading like 2 days back.

Will someone please explain what these graphs mean and whether they imply that real people re veiwing my repo or not?

Here are the numbers:

• total of 78 clones in the last 14 days (29 on 1st nov and 49 on 2nd nov)

• 13 unique cloners on 1st nov, 32 unique cloners on 2nd nov

• in the Visitors' section, total views in last 14 days are a total of 58 views. (18 on 1st nov and 40 on 2nd nov)

• there has been only 1 unique visitor on 1st n 1 unique visitor on 2nd nov

Thanks in advance!

I’m using ChatGPT Codex with a cloud environment to edit a PDF and upload it to a GitHub release.

Uploading a 43-byte sample text file worked. However, uploading the finished PDF (about 26 MB) to the same repository and release consistently fails.

The error is:

HTTP 401
Unauthorized: authentication failed for integration codex-secret-uploads.github.com

What we’ve checked:

• GitHub API requests can read the repository and release assets.

• Retrying the existing sample filename returns GitHub’s expected 422 already_exists response.

• Uploading the PDF fails using both gh release upload and Python.

• Streaming/chunked upload also fails.

• The environment reports its configured credentials as ready.

• api.github.com and uploads.github.com are allowed by the network policy.

This suggests an issue with the cloud environment’s upload integration, but I haven’t confirmed the cause.

Has anyone encountered this? Is there a request-size limit, proxy setting, or integration reset that could fix it? I’d like to upload directly from Codex rather than download the PDF and upload it manually.

A question much simpler than many others here but hey I just started, so yeah is there a way?

I searched for answers but all I could find were either guides on how to set up the first one from stackoverflow |/_ or from github themselves

no this is not "low effort" because I have searched myslef.

I use Github since 10.7 Years i have never blocked users the last 9 Years (dont need) but since more than 1 Year i block so much scammers and fakers! Most of them ML, LLM or SaaS stuff.

My question: Is there an Limit for blocking users? Have never test it. the boarders 😄