Skip to content
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

Sjc/update to .net8 #2124

Closed
wants to merge 7 commits into from

Conversation

stevencl840
Copy link

No description provided.

zentron and others added 7 commits July 1, 2022 14:06
Update assembly to Octopus.LibGit2Sharp

Add Nuke for the builds. Note this is parallel to the existing Azure Devops build steps

Dont set the framework

Output packages to solution default directory
Set the native libgit2 error message when an exception is thrown in the subtransport
…uilding unknown exception types

The exception constructors in GitErrorsToLibGit2SharpExceptions make use of the error category by passing it through to the NativeException(string message, GitErrorCategory category) constructor which adds ("libgit2.category", category) to Data on System.Exception.

We were calling new LibGit2SharpException(m, c), but this was resolving to the string formatting constructor on LibGit2SharpException, because it does not have a constructor that takes a category. This runs a string format, so if the errorMessage contained any curly braces, that constructor would throw an System.FormatException.

This has been changed to just use the message constructor (with no format arguments), and will drop the error code (which is always Unknown anyway).
…error

Do not use string formatting LibGit2SharpException constructor
@stevencl840 stevencl840 deleted the sjc/update-to-.net8 branch September 18, 2024 01:46
@stevencl840 stevencl840 restored the sjc/update-to-.net8 branch September 18, 2024 01:48
@akirayamamoto
Copy link

I assume this was closed in favor of

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants