【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

LiquidBounce:重新定义Minecraft模组体验的开源引擎

LiquidBounce:重新定义Minecraft模组体验的开源引擎 【免费下载链接】LiquidBounceA free mixin-based injection hacked client for Minecraft using the Fabric API 项目地址: https://gitcode.com/gh_mirrors/li/LiquidBounce 价值定位:为什么选择LiquidBounce? 开源免费的游戏增强平台 LiquidBounce作为一款基于Fabric API的注入式客户端(动态修改游戏运行逻辑的工具),采用GPL-3.0开源许可证,为Minecraft玩家提供零成本的游戏体验增强方案。与商业客户端相比,它不仅免去订阅费用,更允许用户自由查看和修改源代码,真正实现"我的游戏我做主"。 安全可靠的动态增强方案 通过创新的mixin技术,LiquidBounce能够在不修改Minecraft原始代码的前提下实现功能扩展。这种非侵入式设计就像给游戏装上"可插拔的智能模块",既避免了修改官方文件带来的账号风险,又能随时启用或禁用特定功能,平衡

By Ne0inhk
github如何使用fork和PR进行协作——你为啥直接commit到我的master分支啊

github如何使用fork和PR进行协作——你为啥直接commit到我的master分支啊

github如何使用fork和PR进行协作——🐧🐧你为啥直接commit到我的master分支啊 * 前言 * fork目标仓库 * clone目标仓库到本地 * 配置本地仓库相关信息 * 关联原始仓库为 Upstream (上游) * git fetch vs. git pull 的区别 * 确保主分支为最新 * 创建新分支 * 正式添加/修改文件并push * 添加/修改文件 * add/commit * push * 创建PR并提交 * 返回网页端 * 确认PR目标、来源等信息 * 填写PR描述 * 提交PR * 提交结束及后续 * "Conversation" (讨论) 标签页 * "Commits" (提交) 标签页 * "Checks" (检查) 标签页 * "Files changed"

By Ne0inhk
开源协同∞智算赋能:GitCode+昇腾NPU部署CodeLlama全流程实践

开源协同∞智算赋能:GitCode+昇腾NPU部署CodeLlama全流程实践

作者简介:华为HCIP,昇腾NPU机构专业用户。 一.引言 最近在项目里用昇腾NPU部署CodeLlama-7B,踩了不少坑,也总结了一些经验。CodeLlama在代码生成这块确实好用,昇腾NPU的算力也够用,就是部署过程需要折腾一下。整个流程从环境搭建到性能调优,中间遇到的问题不少,比如模型格式转换、内存优化、推理速度提升等等。这篇文章主要记录一下实际部署CodeLlama-7B-hf的完整过程,包括环境配置、模型适配、性能优化和常见问题处理,希望能帮到有同样需求的开发者。 二.环境搭建和基本配置 1. 测试平台选择 我们选择 GitCode 作为代码托管平台。GitCode 是 ZEEKLOG 和华为云 CodeArts 联合推出的国内开源平台,主要优势是访问速度快,适合国内开发者使用。 主要功能包括: 1. Git 版本控制、仓库管理、WebIDE 在线开发 2. 分支管理、代码审查、Issue 管理等协作功能 3. GPG

By Ne0inhk