Closed 0x703cd8 closed 3 months ago
Perfect. Thanks. Now just a round of clang-tidy fixes and we are ready to go: https://github.com/libcpr/cpr/actions/runs/8466060069/job/23195757541?pr=1033
Are you able to access the build output behind this link?
Perfect. Thanks. Now just a round of clang-tidy fixes and we are ready to go: https://github.com/libcpr/cpr/actions/runs/8466060069/job/23195757541?pr=1033
Are you able to access the build output behind this link?
I can see it, I'll go take a look
Perfect. Thanks. Now just a round of clang-tidy fixes and we are ready to go: https://github.com/libcpr/cpr/actions/runs/8466060069/job/23195757541?pr=1033
Are you able to access the build output behind this link?
A troublesome problem has arisen: error: consider replacing 'long' with 'int64' [google-runtime-int,-warnings-as-errors]
.
I need some time to figure out a solution.
I quickly fixed all the open clang-tidy issues. Let me know if those changes are OK for you and then we are ready to merge your PR :)
I quickly fixed all the open clang-tidy issues. Let me know if those changes are OK for you and then we are ready to merge your PR :)
No problem, then you can merge it.
In some environments (such as Win11 Visual Studio 2022), the long type is 32 bit, while the time_t type is 64 bit.
So in util.cpp>parseCookies()>
const std::time_t expires = static_cast<time_t>(std::stoul(tokens.at(static_cast<size_t>(CurlHTTPCookieField::Expires))));
, there may be an "stoul argument out of range" issue. BecauseCookie.ExpiresString
may be 64 bit, while the parameter forstd::stoul()
may be 32 bit.(From the source code of curl, it can be seen that the type ofCookie.ExpiresString
istime_t
)So I added function
sTimestampToT()
to parseCookie.ExpiresString
based on different types oftime_t
.What do everyone think? Welcome to correct.
Wishing everyone a happy life.