-
Notifications
You must be signed in to change notification settings - Fork 8
fix: initialise default tsa_uri in c2pa::Signer constructor with an empty string
#104
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
Open
kostiantynperehuda
wants to merge
1
commit into
contentauth:main
Choose a base branch
from
kostiantynperehuda:c++23-compatibility-pr
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+2
−2
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer to change this to the following, if we are going to make a change to the API:
Header
Implementation
Since we are already changing the API, let's make it more semantically correct. Also, using a string as the default changes the behavior of the API. Using a zero length string would mean we are passing a non-nullptr to the Rust code, which may change the behavior of the rust sdk. Lemme know what you think!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We already include in the headers and use it in other apis, so this is the right approach here.
FYI, we are a little inconsistent, usually just referring to optional instead of std:optional in the source.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey. Thanks for the comment. Just gave it a quick test, and you are absolutely right. The rust sdk does in fact treat the nullptr as the absence of the value, but treats an empty string as a uri and crashes when it tries to make a request to that uri.
I will patch the commit to use an optional instead.
I also found that none of the tests actually attempt to construct the Signer with default tsa_uri, and doing this with current implementation results in a segfault on the c++ side. Shall we add a test to capture this?