libgit2 / libgit2/libgit2sharp
LibGit2Sharp.LibGit2SharpException: could not set credentials: could not open libssl
还没有人认领这个 Issue。
- 主要语言
- C#
- 星标
- 3.5k
- 派生
- 925
- PR 合并指标
- 30 天内没有已合并 PR
描述
You are opening a bug report against the LibGit2Sharp project: we
use GitHub Issues for tracking bug reports and feature requests. If
you have a question about an API or usage, please ask on StackOverflow:
http://stackoverflow.com/questions/tagged/libgit2sharp.
Otherwise, to report a bug, please fill out the reproduction steps
(below) and delete these introductory paragraphs. Thanks!
Reproduction steps
Just to try clone a repository form Azure DevOps.
var options = new CloneOptions
{
FetchOptions = {
CredentialsProvider = CredentialsProvider,
OnTransferProgress = OnTransferProgress
},
OnCheckoutProgress = OnCheckoutProgress
};
Repository.Clone(remoteUrl, local.FullName, options);
Expected behavior
Actual behavior
Error thrown
LibGit2Sharp.LibGit2SharpException: could not set credentials: could not open libssl
at LibGit2Sharp.Core.Ensure.HandleError(Int32 result) in /_/LibGit2Sharp/Core/Ensure.cs:line 154
at LibGit2Sharp.Core.Ensure.ZeroResult(Int32 result) in /_/LibGit2Sharp/Core/Ensure.cs:line 172
at LibGit2Sharp.Core.Proxy.git_clone(String url, String workdir, GitCloneOptions& opts) in /_/LibGit2Sharp/Core/Proxy.cs:line 278
at LibGit2Sharp.Repository.Clone(String sourceUrl, String workdirPath, CloneOptions options) in /_/LibGit2Sharp/Repository.cs:line 824
Version of LibGit2Sharp (release number or SHA1)
0.30
Operating system(s) tested; .NET runtime tested
dotnet 8.0 image (ubuntu 22.04 + libssl3)
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
首先,在所述的带有 libssl3 的 .NET 8 Ubuntu 22.04 镜像上复现 Azure DevOps 克隆。阅读 Ensure.cs、Proxy.cs 和 Repository.cs 中失败的路径,然后跟踪凭据和原生 SSL 依赖项的加载位置。当提供的 CloneOptions 能够在不出现 libssl 错误的情况下完成克隆时,即视为完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- csharp, git, linux, ubuntu
- 领域
- devtools, operating-systems
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 28/100