【git】WARNING: connection is not using a post-quantum key exchange algorithm.

【git】WARNING: connection is not using a post-quantum key exchange algorithm.

问题:

推送代码提示下面信息:

16:22:54.422: [C:\git\yang-teambition] git -c credential.helper= -c core.quotepath=false -c log.showSignature=false push --progress --porcelain origin refs/heads/dev_tianzhi:dev_tianzhi ** WARNING: connection is not using a post-quantum key exchange algorithm. ** This session may be vulnerable to "store now, decrypt later" attacks. ** The server may need to be upgraded. See https://openssh.com/pq.html Enumerating objects: 59, done. Counting objects: 1% (1/59) Counting objects: 3% (2/59) Counting objects: 5% (3/59) Counting objects: 6% (4/59) Counting objects: 8% (5/59) Counting objects: 10% (6/59) Counting objects: 11% (7/59) Counting objects: 13% (8/59) Counting objects: 15% (9/59) Counting objects: 16% (10/59) Counting objects: 18% (11/59) Counting objects: 20% (12/59) Counting objects: 22% (13/59) Counting objects: 23% (14/59) Counting objects: 25% (15/59) Counting objects: 27% (16/59) Counting objects: 28% (17/59) Counting objects: 30% (18/59) Counting objects: 32% (19/59) Counting objects: 33% (20/59) Counting objects: 35% (21/59) Counting objects: 37% (22/59) Counting objects: 38% (23/59) Counting objects: 40% (24/59) Counting objects: 42% (25/59) Counting objects: 44% (26/59) Counting objects: 45% (27/59) Counting objects: 47% (28/59) Counting objects: 49% (29/59) Counting objects: 50% (30/59) Counting objects: 52% (31/59) Counting objects: 54% (32/59) Counting objects: 55% (33/59) Counting objects: 57% (34/59) Counting objects: 59% (35/59) Counting objects: 61% (36/59) Counting objects: 62% (37/59) Counting objects: 64% (38/59) Counting objects: 66% (39/59) Counting objects: 67% (40/59) Counting objects: 69% (41/59) Counting objects: 71% (42/59) Counting objects: 72% (43/59) Counting objects: 74% (44/59) Counting objects: 76% (45/59) Counting objects: 77% (46/59) Counting objects: 79% (47/59) Counting objects: 81% (48/59) Counting objects: 83% (49/59) Counting objects: 84% (50/59) Counting objects: 86% (51/59) Counting objects: 88% (52/59) Counting objects: 89% (53/59) Counting objects: 91% (54/59) Counting objects: 93% (55/59) Counting objects: 94% (56/59) Counting objects: 96% (57/59) Counting objects: 98% (58/59) Counting objects: 100% (59/59) Counting objects: 100% (59/59), done. Delta compression using up to 20 threads Compressing objects: 3% (1/27) Compressing objects: 7% (2/27) Compressing objects: 11% (3/27) Compressing objects: 14% (4/27) Compressing objects: 18% (5/27) Compressing objects: 22% (6/27) Compressing objects: 25% (7/27) Compressing objects: 29% (8/27) Compressing objects: 33% (9/27) Compressing objects: 37% (10/27) Compressing objects: 40% (11/27) Compressing objects: 44% (12/27) Compressing objects: 48% (13/27) Compressing objects: 51% (14/27) Compressing objects: 55% (15/27) Compressing objects: 59% (16/27) Compressing objects: 62% (17/27) Compressing objects: 66% (18/27) Compressing objects: 70% (19/27) Compressing objects: 74% (20/27) Compressing objects: 77% (21/27) Compressing objects: 81% (22/27) Compressing objects: 85% (23/27) Compressing objects: 88% (24/27) Compressing objects: 92% (25/27) Compressing objects: 96% (26/27) Compressing objects: 100% (27/27) Compressing objects: 100% (27/27), done. Writing objects: 2% (1/37) Writing objects: 5% (2/37) Writing objects: 8% (3/37) Writing objects: 10% (4/37) Writing objects: 13% (5/37) Writing objects: 16% (6/37) Writing objects: 18% (7/37) Writing objects: 21% (8/37) Writing objects: 24% (9/37) Writing objects: 27% (10/37) Writing objects: 29% (11/37) Writing objects: 32% (12/37) Writing objects: 35% (13/37) Writing objects: 37% (14/37) Writing objects: 40% (15/37) Writing objects: 43% (16/37) Writing objects: 45% (17/37) Writing objects: 51% (19/37) Writing objects: 54% (20/37) Writing objects: 56% (21/37) Writing objects: 59% (22/37) Writing objects: 62% (23/37) Writing objects: 64% (24/37) Writing objects: 67% (25/37) Writing objects: 70% (26/37) Writing objects: 72% (27/37) Writing objects: 75% (28/37) Writing objects: 78% (29/37) Writing objects: 81% (30/37) Writing objects: 83% (31/37) Writing objects: 86% (32/37) Writing objects: 89% (33/37) Writing objects: 91% (34/37) Writing objects: 94% (35/37) Writing objects: 97% (36/37) Writing objects: 100% (37/37) Writing objects: 100% (37/37), 3.62 KiB | 463.00 KiB/s, done. Total 37 (delta 18), reused 0 (delta 0), pack-reused 0 (from 0) Read from remote host gitlab.xxx.com: Connection reset by peer client_loop: send disconnect: Connection reset by peer send-pack: unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly 

这是 Git 在推送代码到远程仓库时,连接被远端强制断开Connection reset by peer)导致的失败。常见原因和解决方式如下:


✅ 可能原因与对应处理

原因说明解决方式
1. 大文件或提交过多你这次推送了 37 个对象,虽然不算特别大,但如果包含大文件(如 PDF、图片、jar 包),容易触发 GitLab 的限制。检查是否有大文件被提交:
`git rev-list --objects --all
grep -E '.(pdf|jar|zip|png|jpg)'<br>如有,用 git filter-repoBFG` 清理历史。
2. 网络不稳定 / VPN 中断你公司 GitLab 地址是 gitlab.hezhihulian.com,可能是内网或 VPN 环境,连接中断。重试几次:
git push origin dev_tianzhi
或换网络 / 换 SSH 端口。
3. GitLab 服务器限制服务端配置了超时或最大包大小限制(如 Nginx、GitLab 本身的 git timeout)。联系运维确认 GitLab 日志 /var/log/gitlab/gitlab-workhorse/current 是否报错。
4. SSH 密钥或权限问题虽然报错不是权限拒绝,但某些 GitLab 版本在权限异常时会直接断连。确认你有 dev_tianzhi 分支的推送权限,且 SSH key 已正确配置。

你可以立即尝试的排查/修复步骤

检查是否有大文件

git ls-tree -r -l dev_tianzhi | sort -k4 -n | tail -10

使用 HTTPS 推送测试(排除 SSH 问题):

git remote set-url origin https://gitlab.yang.com/xxx/xxx.git git push origin dev_tianzhi

减小包大小(分批推送): 如果你本地有多个提交,可以尝试分批次推送:

git rebase -i HEAD~10 # 把多个提交合并成1~2个 git push origin dev_tianzhi

重试推送(最简单):

git push origin dev_tianzhi



Read more

Web 服务基石 Nginx

NGINX Nginx是一款由俄罗斯程序员 Igor Sysoev 开发的 轻量级、高性能的 HTTP 和反向代理服务器,同时也是一个 IMAP/POP3/SMTP 代理服务器。自 2004 年首次发布以来,Nginx 凭借其 高并发处理能力、低内存消耗和稳定性,成为全球最受欢迎的 Web 服务器之一,广泛应用于静态资源服务、反向代理、负载均衡、API 网关等场景 NGINX安装 源码编译 #解压压缩包 tar zxf nginx-1.24.0.tar.gz cd nginx-1.24.0 #编译 ./configure --prefix=/usr/local/nginx --user=

By Ne0inhk
【Spring AI】第二弹:Prompt 优化技巧、AI 应用开发、实战 Spring AI 特性 (自定义Advisor、结构化输出、对话记忆持久化、PromptTemplate模板、多模态)

【Spring AI】第二弹:Prompt 优化技巧、AI 应用开发、实战 Spring AI 特性 (自定义Advisor、结构化输出、对话记忆持久化、PromptTemplate模板、多模态)

本节重点 熟悉 Prompt‏ 工程和优化技巧,并设计开发一款 A‏I 恋爱大师应用,实战 Spring‏ AI 调用大模型、对话记忆、Adv‏isor、结构化输出、自定义对话记忆‌、Prompt 模板等特性。 具体内容包括: * Prompt 工程基本概念 * Prompt 优化技巧 * AI 恋爱大师应用需求分析 * AI 恋爱大师应用方案设计 * Spring AI ChatClient / Advisor / ChatMemory 特性 * 多轮对话 AI 应用开发 * Spring AI 自定义 Advisor * Spring AI 结构化输出 - 恋爱报告功能 * Spring AI 对话记忆持久化 * Spring

By Ne0inhk
《MySQL 亿级数据表平滑分表实践:基于时间分片的架构演进》

《MySQL 亿级数据表平滑分表实践:基于时间分片的架构演进》

个人名片 🎓作者简介:java领域优质创作者 🌐个人主页:码农阿豪 📞工作室:新空间代码工作室(提供各种软件服务) 💌个人邮箱:[[email protected]] 📱个人微信:15279484656 🌐个人导航网站:www.forff.top 💡座右铭:总有人要赢。为什么不能是我呢? * 专栏导航: 码农阿豪系列专栏导航 面试专栏:收集了java相关高频面试题,面试实战总结🍻🎉🖥️ Spring5系列专栏:整理了Spring5重要知识点与实战演练,有案例可直接使用🚀🔧💻 Redis专栏:Redis从零到一学习分享,经验总结,案例实战💐📝💡 全栈系列专栏:海纳百川有容乃大,可能你想要的东西里面都有🤸🌱🚀 目录 * 《MySQL 亿级数据表平滑分表实践:基于时间分片的架构演进》 * 引言 * 一、为什么我们需要分表? * 1.1 单表数据量过大的问题 * 1.2 分表方案选型 * 二、

By Ne0inhk
VS code 安装依赖包出现的一系列报错:node.js

VS code 安装依赖包出现的一系列报错:node.js

场景: VS code安装依赖包的一系列报错 问题描述 问题1:VS code使用npm install 安装包的时候,出现 **npm:无法将“npm项识别为 cmdlet、函数、脚本文件或可运行程序的名称。请检查名称的拼写,如果包括路径,请确保路径正确,然后再试一次。 所在位置 行:1 字符:1 +npm i +CategoryInfo:ObjectNotFound:(npm:String) (],CommandNotFoundException 4FullyQualifiedErrorId :CommandNotFoundException** 因为没有安装node.js,所以识别不了,下面安装node.js: 参考https://blog.ZEEKLOG.net/weixin_42182741/article/details/152072795 感谢大佬提供的详细教程! 安装之后,

By Ne0inhk