New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Github Clone Broken on Latest Version #1899
Comments
It works on my end. You need to provide more information what exactly you're using. Browser, OS, maybe the problem is with your browser extension, so you can try in incognito mode or in different browser. So it may be only problem for you. This project doesn't have main developer that write code and fix all bugs. It's community driven, features and bug fixes are written by individual contributors like you, so if you're the only one that have this issue, no one will probably fix the issue for you. But if you want to contribute you're more than welcome, but not that need to write unit tests that fail (note that all test are working, and they use real browsers) and pass after the fix. |
Cool, makes sense! It does still seem broken for me but I'll try coming up with a more consistent repro and then open an issue or try to fix it. |
If it's still broken for you, then you don't need to close the issue. Just comment here if you find a reproduction, root cause or a fix. |
same as me net::ERR_QUIC_PROTOCOL_ERROR 200, seems to be cors proxy timeout maybe slow network problems |
Can you use your own proxy and see if it works? |
For now it works again, for next i just develop ported for my own cors-proxy to be able for hosted in cloudflare https://github.com/cristminix/hono-isomorphic-cors-proxy , thanks for all team works |
POST https://cors.isomorphic-git.org/github.com/isomorphic-git/isomorphic-git/git-upload-pack net::ERR_QUIC_PROTOCOL_ERROR 200 (OK)
I'm using isomorphic-git for another project and I noticed this started happening since around Saturday afternoon with varying levels of consistency, and is fully broken now. I think Github may have changed something? I tried upgrading to
1.25.7
after looking at this issue, but that didn't fix the problem either.Happy to help debug or provide more context if needed!
The text was updated successfully, but these errors were encountered: