Repository navigation
Conversation
bagder
force-pushed
the
bagder/1521-NULL-check
branch
from
August 21, 2024 13:17
a6f74ad to
3da3e88
Compare
bagder
marked this pull request as draft
August 21, 2024 14:03
bagder
marked this pull request as ready for review
August 22, 2024 07:24
bagder
force-pushed
the
bagder/1521-NULL-check
branch
from
August 22, 2024 08:08
298a135 to
7fa64c3
Compare
bagder
force-pushed
the
bagder/1521-NULL-check
branch
from
August 22, 2024 08:09
7fa64c3 to
824bf82
Compare
bagder
force-pushed
the
bagder/1521-NULL-check
branch
from
August 22, 2024 14:32
824bf82 to
22a32b4
Compare
bagder
changed the title
bagder
marked this pull request as draft
August 22, 2024 14:48
bagder
marked this pull request as ready for review
August 22, 2024 21:46
instead of returning an error code to the getinfo() call Closes #14634
... and just move them into the accepted range.
Previously this test allowed several error values when setting options. This made this test miss #14629. Now, errors are generally not accepted for setopts: - numerical setopts accept CURLE_BAD_FUNCTION_ARGUMENT for funny input - the first setopt to an option accepts CURLE_NOT_BUILT_IN or CURLE_UNKNOWN_OPTION for when they are disabled/not built-in - there is an allowlist concept for some return code for some variables, managed at the top of the mk-lib1521.pl script In curl.h: remove the OBSOLETE named values from the setopt list. Closes #14634
bagder
force-pushed
the
bagder/1521-NULL-check
branch
from
August 22, 2024 21:49
9c14869 to
ccdde79
Compare
bagder
added a commit
that referenced
this pull request
Aug 23, 2024
Because NULL is documented as default and most options that take pointers accept NULL to reset back to internal default. Closes #14634
bagder
added a commit
that referenced
this pull request
Aug 23, 2024
... and just move them into the accepted range. Like how buffersize and a few other options work. Closes #14634
bagder
added a commit
that referenced
this pull request
Aug 23, 2024
Previously this test allowed several error values when setting options. This made this test miss #14629. Now, errors are generally not accepted for setopts: - numerical setopts accept CURLE_BAD_FUNCTION_ARGUMENT for funny input - the first setopt to an option accepts CURLE_NOT_BUILT_IN or CURLE_UNKNOWN_OPTION for when they are disabled/not built-in - there is an allowlist concept for some return code for some variables, managed at the top of the mk-lib1521.pl script In curl.h: remove the OBSOLETE named values from the setopt list. Closes #14634
dg0yt
reviewed
Aug 31, 2024
Comment on lines
-1355
to
+1354
| /* OBSOLETE, do not use! */ | ||
| CURLOPT(CURLOPT_OBSOLETE72, CURLOPTTYPE_LONG, 72), | ||
|
|
||
| /* 72 = OBSOLETE */ |
Contributor
There was a problem hiding this comment.
Noticed in vpckg CI run on CURL HEAD:
CURLOPT_OBSOLETE72 is still used in the header for
Line 723 in 3fc81be
and CURLOPT_CLOSEPOLICY is used downstream in curlpp and curlcpp.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Previously this test allowed several error values when setting options. This made this test miss #14629.
Now, errors are generally not accepted for setopts:
In curl.h: remove the OBSOLETE named values from the setopt list.