Link with CoreServices to fix macOs curl init crash

Closes https://github.com/alexcrichton/curl-rust/issues/524
Fix macOs Sonoma curl initialization crash: https://github.com/curl/curl/issues/11893 by linking with CoreServices as the corresponding curl fix did: https://github.com/curl/curl/commit/6ab7e1990bd548059f08c471d20537bca13c67b6

I am trying to fix the initialization crash with this patch, but when I apply patch on top of https://github.com/sagebind/isahc and run cargo test, I get the same error as in the issue above:
diff --git a/Cargo.toml b/Cargo.toml
index d797d20..af49991 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -50,12 +50,14 @@ waker-fn = "1" # async primitive

 # underlying HTTP engine that powers Isahc
 [dependencies.curl]
-version = "0.4.43"
+git = "https://github.com/SomeoneToIgnore/curl-rust"
+branch = "update-curl"
 default-features = false

 # access to certain curl APIs not exposed in safe wrapper
 [dependencies.curl-sys]
-version = "0.4.55"
+git = "https://github.com/SomeoneToIgnore/curl-rust"
+branch = "update-curl"
 default-features = false

 # used in TLS cert parsing
diff --git a/benchmarks/Cargo.toml b/benchmarks/Cargo.toml
index ddbf688..d3c12d4 100644
--- a/benchmarks/Cargo.toml
+++ b/benchmarks/Cargo.toml
@@ -6,11 +6,14 @@ publish = false

 [dependencies]
 criterion = "0.4"
-curl = "0.4.42"
 rayon = "1"
 rouille = "3"
 reqwest = { version = "0.11.10", features = ["blocking"] }

+[dependencies.curl]
+git = "https://github.com/SomeoneToIgnore/curl-rust"
+branch = "update-curl"
+
 [dependencies.isahc]
 path = ".."

Yet, it appears in curl changelog for curl and libcurl 8.4.0

cmake, configure: also link with CoreServices [32]

is present that includes https://github.com/curl/curl/commit/6ab7e1990bd548059f08c471d20537bca13c67b6
What am I doing wrong and how could I fix curl init for Sonoma?

Thanks for trying to help! However, I think this has several issues:
A. We have to wait for 8.4 to be released before the version can be updated.
B. Updating involves more than just bumping the version number. The submodule and build scripts need to be updated (https://github.com/alexcrichton/curl-rust/pull/528 is a recent example).
C. Updating won't fix the issue you are experiencing. The Rust package does not use cmake to build, and it looks like the upstream changes were specifically in the cmake scripts. The build.rs would need to be updated to mirror whatever changes were done upstream.

Thank you for the elaborations, I have gotten confused by the changelog entry and missed the actual release being absent.
Is there a way to use master branch of curl locally to test the upcoming 8.4.0 version somehow?
I think I'll be able to address the rest of the feedback as soon as I can make it practical.

I have pushed the build.rs update and ensured that the updated curl-sys submodule (to latest master commit which is 65729f65c7c5 there currently) fixes isahc test failures.
Looks like all that's left is to wait for the proper curl release and update it here — I plan to do that when it happens, but please let me know if I overlooked things and there's something else to do.
One side note: curl build seems to emit a lot of warnings currently:

curl deprecation warnings during build
warning: curl/lib/mprintf.c:975:10: warning: 'sprintf' is deprecated: This function is provided for compatibility reasons only.  Due to security concerns inherent in the design of sprintf(3), it is highly recommended that you use snprintf(3) instead. [-Wdeprecated-declarations]
warning:         (sprintf)(work, formatbuf, p->data.dnum);
warning:          ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/stdio.h:180:1: note: 'sprintf' has been explicitly marked deprecated here
warning: __deprecated_msg("This function is provided for compatibility reasons only.  Due to security concerns inherent in the design of sprintf(3), it is highly recommended that you use snprintf(3) instead.")
warning: ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:215:48: note: expanded from macro '__deprecated_msg'
warning:         #define __deprecated_msg(_msg) __attribute__((__deprecated__(_msg)))
warning:                                                       ^
warning: 1 warning generated.
warning: curl/lib/vtls/sectransp.c:1207:7: warning: 'CFURLCreateDataAndPropertiesFromResource' is deprecated: first deprecated in macOS 10.9 - For resource data, use the CFReadStream API. For file resource properties, use CFURLCopyResourcePropertiesForKeys. [-Wdeprecated-declarations]
warning:       CFURLCreateDataAndPropertiesFromResource(NULL,
warning:       ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CFURLAccess.h:52:9: note: 'CFURLCreateDataAndPropertiesFromResource' has been explicitly marked deprecated here
warning: Boolean CFURLCreateDataAndPropertiesFromResource(CFAllocatorRef alloc, CFURLRef url, CFDataRef *resourceData, CFDictionaryRef *properties, CFArrayRef desiredProperties, SInt32 *errorCode) API_DEPRECATED("For resource data, use the CFReadStream API. For file resource properties, use CFURLCopyResourcePropertiesForKeys.", macos(10.0,10.9), ios(2.0,7.0), watchos(2.0,2.0), tvos(9.0,9.0));
warning:         ^
warning: curl/lib/vtls/sectransp.c:1320:20: warning: 'kTLSProtocol1' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:       *darwinver = kTLSProtocol1;
warning:                    ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecProtocolTypes.h:157:5: note: 'kTLSProtocol1' has been explicitly marked deprecated here
warning:     kTLSProtocol1 CF_ENUM_DEPRECATED(10_2, 10_15, 5_0, 13_0) = 4,
warning:     ^
warning: curl/lib/vtls/sectransp.c:1323:20: warning: 'kTLSProtocol11' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:       *darwinver = kTLSProtocol11;
warning:                    ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecProtocolTypes.h:158:5: note: 'kTLSProtocol11' has been explicitly marked deprecated here
warning:     kTLSProtocol11 CF_ENUM_DEPRECATED(10_2, 10_15, 5_0, 13_0) = 7,
warning:     ^
warning: curl/lib/vtls/sectransp.c:1326:20: warning: 'kTLSProtocol12' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:       *darwinver = kTLSProtocol12;
warning:                    ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecProtocolTypes.h:159:5: note: 'kTLSProtocol12' has been explicitly marked deprecated here
warning:     kTLSProtocol12 CF_ENUM_DEPRECATED(10_2, 10_15, 5_0, 13_0) = 8,
warning:     ^
warning: curl/lib/vtls/sectransp.c:1332:22: warning: 'kTLSProtocol13' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:         *darwinver = kTLSProtocol13;
warning:                      ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecProtocolTypes.h:161:5: note: 'kTLSProtocol13' has been explicitly marked deprecated here
warning:     kTLSProtocol13 CF_ENUM_DEPRECATED(10_2, 10_15, 5_0, 13_0) = 10,
warning:     ^
warning: curl/lib/vtls/sectransp.c:1386:6: warning: 'SSLSetProtocolVersionMax' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:   if(SSLSetProtocolVersionMax) {
warning:      ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:494:1: note: 'SSLSetProtocolVersionMax' has been explicitly marked deprecated here
warning: SSLSetProtocolVersionMax  (SSLContextRef      context,
warning: ^
warning: curl/lib/vtls/sectransp.c:1387:34: warning: 'kTLSProtocol1' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:     SSLProtocol darwin_ver_min = kTLSProtocol1;
warning:                                  ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecProtocolTypes.h:157:5: note: 'kTLSProtocol1' has been explicitly marked deprecated here
warning:     kTLSProtocol1 CF_ENUM_DEPRECATED(10_2, 10_15, 5_0, 13_0) = 4,
warning:     ^
warning: curl/lib/vtls/sectransp.c:1388:34: warning: 'kTLSProtocol1' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:     SSLProtocol darwin_ver_max = kTLSProtocol1;
warning:                                  ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecProtocolTypes.h:157:5: note: 'kTLSProtocol1' has been explicitly marked deprecated here
warning:     kTLSProtocol1 CF_ENUM_DEPRECATED(10_2, 10_15, 5_0, 13_0) = 4,
warning:     ^
warning: curl/lib/vtls/sectransp.c:1402:11: warning: 'SSLSetProtocolVersionMin' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:     (void)SSLSetProtocolVersionMin(backend->ssl_ctx, darwin_ver_min);
warning:           ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:458:1: note: 'SSLSetProtocolVersionMin' has been explicitly marked deprecated here
warning: SSLSetProtocolVersionMin  (SSLContextRef      context,
warning: ^
warning: curl/lib/vtls/sectransp.c:1403:11: warning: 'SSLSetProtocolVersionMax' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:     (void)SSLSetProtocolVersionMax(backend->ssl_ctx, darwin_ver_max);
warning:           ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:494:1: note: 'SSLSetProtocolVersionMax' has been explicitly marked deprecated here
warning: SSLSetProtocolVersionMax  (SSLContextRef      context,
warning: ^
warning: curl/lib/vtls/sectransp.c:1488:9: warning: 'SSLGetNumberSupportedCiphers' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:   err = SSLGetNumberSupportedCiphers(ssl_ctx, &all_ciphers_count);
warning:         ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:818:1: note: 'SSLGetNumberSupportedCiphers' has been explicitly marked deprecated here
warning: SSLGetNumberSupportedCiphers (SSLContextRef                     context,
warning: ^
warning: curl/lib/vtls/sectransp.c:1505:9: warning: 'SSLGetSupportedCiphers' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:   err = SSLGetSupportedCiphers(ssl_ctx, all_ciphers,
warning:         ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:832:1: note: 'SSLGetSupportedCiphers' has been explicitly marked deprecated here
warning: SSLGetSupportedCiphers           (SSLContextRef                 context,
warning: ^
warning: curl/lib/vtls/sectransp.c:1527:9: warning: 'SSLSetEnabledCiphers' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:   err = SSLSetEnabledCiphers(ssl_ctx, allowed_ciphers,
warning:         ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:865:1: note: 'SSLSetEnabledCiphers' has been explicitly marked deprecated here
warning: SSLSetEnabledCiphers            (SSLContextRef                  context,
warning: ^
warning: curl/lib/vtls/sectransp.c:1631:9: warning: 'SSLSetEnabledCiphers' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:   err = SSLSetEnabledCiphers(ssl_ctx, selected_ciphers, ciphers_count);
warning:         ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:865:1: note: 'SSLSetEnabledCiphers' has been explicitly marked deprecated here
warning: SSLSetEnabledCiphers            (SSLContextRef                  context,
warning: ^
warning: curl/lib/vtls/sectransp.c:1671:6: warning: 'SSLCreateContext' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:   if(SSLCreateContext) {  /* use the newer API if available */
warning:      ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:316:1: note: 'SSLCreateContext' has been explicitly marked deprecated here
warning: SSLCreateContext(CFAllocatorRef __nullable alloc, SSLProtocolSide protocolSide, SSLConnectionType connectionType)
warning: ^
warning: curl/lib/vtls/sectransp.c:1674:24: warning: 'SSLCreateContext' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:     backend->ssl_ctx = SSLCreateContext(NULL, kSSLClientSide, kSSLStreamType);
warning:                        ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:316:1: note: 'SSLCreateContext' has been explicitly marked deprecated here
warning: SSLCreateContext(CFAllocatorRef __nullable alloc, SSLProtocolSide protocolSide, SSLConnectionType connectionType)
warning: ^
warning: curl/lib/vtls/sectransp.c:1674:47: warning: 'kSSLClientSide' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:     backend->ssl_ctx = SSLCreateContext(NULL, kSSLClientSide, kSSLStreamType);
warning:                                               ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:218:5: note: 'kSSLClientSide' has been explicitly marked deprecated here
warning:     kSSLClientSide CF_ENUM_DEPRECATED(10_2, 10_15, 2_0, 13_0)
warning:     ^
warning: curl/lib/vtls/sectransp.c:1674:63: warning: 'kSSLStreamType' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:     backend->ssl_ctx = SSLCreateContext(NULL, kSSLClientSide, kSSLStreamType);
warning:                                                               ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:223:5: note: 'kSSLStreamType' has been explicitly marked deprecated here
warning:     kSSLStreamType CF_ENUM_DEPRECATED(10_2, 10_15, 2_0, 13_0),
warning:     ^
warning: curl/lib/vtls/sectransp.c:1705:6: warning: 'SSLSetProtocolVersionMax' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:   if(SSLSetProtocolVersionMax) {
warning:      ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:494:1: note: 'SSLSetProtocolVersionMax' has been explicitly marked deprecated here
warning: SSLSetProtocolVersionMax  (SSLContextRef      context,
warning: ^
warning: curl/lib/vtls/sectransp.c:1708:13: warning: 'SSLSetProtocolVersionMin' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:       (void)SSLSetProtocolVersionMin(backend->ssl_ctx, kTLSProtocol1);
warning:             ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:458:1: note: 'SSLSetProtocolVersionMin' has been explicitly marked deprecated here
warning: SSLSetProtocolVersionMin  (SSLContextRef      context,
warning: ^
warning: curl/lib/vtls/sectransp.c:1708:56: warning: 'kTLSProtocol1' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:       (void)SSLSetProtocolVersionMin(backend->ssl_ctx, kTLSProtocol1);
warning:                                                        ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecProtocolTypes.h:157:5: note: 'kTLSProtocol1' has been explicitly marked deprecated here
warning:     kTLSProtocol1 CF_ENUM_DEPRECATED(10_2, 10_15, 5_0, 13_0) = 4,
warning:     ^
warning: curl/lib/vtls/sectransp.c:1711:15: warning: 'SSLSetProtocolVersionMax' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:         (void)SSLSetProtocolVersionMax(backend->ssl_ctx, kTLSProtocol13);
warning:               ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:494:1: note: 'SSLSetProtocolVersionMax' has been explicitly marked deprecated here
warning: SSLSetProtocolVersionMax  (SSLContextRef      context,
warning: ^
warning: curl/lib/vtls/sectransp.c:1711:58: warning: 'kTLSProtocol13' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:         (void)SSLSetProtocolVersionMax(backend->ssl_ctx, kTLSProtocol13);
warning:                                                          ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecProtocolTypes.h:161:5: note: 'kTLSProtocol13' has been explicitly marked deprecated here
warning:     kTLSProtocol13 CF_ENUM_DEPRECATED(10_2, 10_15, 5_0, 13_0) = 10,
warning:     ^
warning: curl/lib/vtls/sectransp.c:1714:15: warning: 'SSLSetProtocolVersionMax' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:         (void)SSLSetProtocolVersionMax(backend->ssl_ctx, kTLSProtocol12);
warning:               ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:494:1: note: 'SSLSetProtocolVersionMax' has been explicitly marked deprecated here
warning: SSLSetProtocolVersionMax  (SSLContextRef      context,
warning: ^
warning: curl/lib/vtls/sectransp.c:1714:58: warning: 'kTLSProtocol12' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:         (void)SSLSetProtocolVersionMax(backend->ssl_ctx, kTLSProtocol12);
warning:                                                          ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecProtocolTypes.h:159:5: note: 'kTLSProtocol12' has been explicitly marked deprecated here
warning:     kTLSProtocol12 CF_ENUM_DEPRECATED(10_2, 10_15, 5_0, 13_0) = 8,
warning:     ^
warning: curl/lib/vtls/sectransp.c:1829:13: warning: 'SSLSetALPNProtocols' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:       err = SSLSetALPNProtocols(backend->ssl_ctx, alpnArr);
warning:             ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:1332:1: note: 'SSLSetALPNProtocols' has been explicitly marked deprecated here
warning: SSLSetALPNProtocols         (SSLContextRef      context,
warning: ^
warning: curl/lib/vtls/sectransp.c:1897:13: warning: 'SSLSetCertificate' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:       err = SSLSetCertificate(backend->ssl_ctx, certs);
warning:             ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:637:1: note: 'SSLSetCertificate' has been explicitly marked deprecated here
warning: SSLSetCertificate                       (SSLContextRef          context,
warning: ^
warning: curl/lib/vtls/sectransp.c:1958:6: warning: 'SSLSetSessionOption' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:   if(SSLSetSessionOption && darwinver_maj >= 13) {
warning:      ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:384:1: note: 'SSLSetSessionOption' has been explicitly marked deprecated here
warning: SSLSetSessionOption                     (SSLContextRef          context,
warning: ^
warning: curl/lib/vtls/sectransp.c:1964:11: warning: 'SSLSetSessionOption' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:     err = SSLSetSessionOption(backend->ssl_ctx,
warning:           ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:384:1: note: 'SSLSetSessionOption' has been explicitly marked deprecated here
warning: SSLSetSessionOption                     (SSLContextRef          context,
warning: ^
warning: curl/lib/vtls/sectransp.c:1965:31: warning: 'kSSLSessionOptionBreakOnServerAuth' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:                               kSSLSessionOptionBreakOnServerAuth,
warning:                               ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:99:2: note: 'kSSLSessionOptionBreakOnServerAuth' has been explicitly marked deprecated here
warning:         kSSLSessionOptionBreakOnServerAuth CF_ENUM_DEPRECATED(10_2, 10_15, 2_0, 13_0) = 0,
warning:         ^
warning: curl/lib/vtls/sectransp.c:2012:11: warning: 'SSLSetPeerDomainName' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:     err = SSLSetPeerDomainName(backend->ssl_ctx, snihost, snilen);
warning:           ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:686:1: note: 'SSLSetPeerDomainName' has been explicitly marked deprecated here
warning: SSLSetPeerDomainName            (SSLContextRef          context,
warning: ^
warning: curl/lib/vtls/sectransp.c:2049:6: warning: 'SSLSetSessionOption' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:   if(SSLSetSessionOption) {
warning:      ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:384:1: note: 'SSLSetSessionOption' has been explicitly marked deprecated here
warning: SSLSetSessionOption                     (SSLContextRef          context,
warning: ^
warning: curl/lib/vtls/sectransp.c:2050:5: warning: 'SSLSetSessionOption' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:     SSLSetSessionOption(backend->ssl_ctx, kSSLSessionOptionSendOneByteRecord,
warning:     ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:384:1: note: 'SSLSetSessionOption' has been explicitly marked deprecated here
warning: SSLSetSessionOption                     (SSLContextRef          context,
warning: ^
warning: curl/lib/vtls/sectransp.c:2050:43: warning: 'kSSLSessionOptionSendOneByteRecord' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:     SSLSetSessionOption(backend->ssl_ctx, kSSLSessionOptionSendOneByteRecord,
warning:                                           ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:123:5: note: 'kSSLSessionOptionSendOneByteRecord' has been explicitly marked deprecated here
warning:     kSSLSessionOptionSendOneByteRecord CF_ENUM_DEPRECATED(10_2, 10_15, 2_0, 13_0) = 4,
warning:     ^
warning: curl/lib/vtls/sectransp.c:2052:5: warning: 'SSLSetSessionOption' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:     SSLSetSessionOption(backend->ssl_ctx, kSSLSessionOptionFalseStart,
warning:     ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:384:1: note: 'SSLSetSessionOption' has been explicitly marked deprecated here
warning: SSLSetSessionOption                     (SSLContextRef          context,
warning: ^
warning: curl/lib/vtls/sectransp.c:2052:43: warning: 'kSSLSessionOptionFalseStart' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:     SSLSetSessionOption(backend->ssl_ctx, kSSLSessionOptionFalseStart,
warning:                                           ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:117:5: note: 'kSSLSessionOptionFalseStart' has been explicitly marked deprecated here
warning:     kSSLSessionOptionFalseStart CF_ENUM_DEPRECATED(10_2, 10_15, 2_0, 13_0) = 3,
warning:     ^
warning: curl/lib/vtls/sectransp.c:2066:13: warning: 'SSLSetPeerID' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:       err = SSLSetPeerID(backend->ssl_ctx, ssl_sessionid, ssl_sessionid_len);
warning:             ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:1285:1: note: 'SSLSetPeerID' has been explicitly marked deprecated here
warning: SSLSetPeerID                            (SSLContextRef          context,
warning: ^
warning: curl/lib/vtls/sectransp.c:2086:13: warning: 'SSLSetPeerID' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:       err = SSLSetPeerID(backend->ssl_ctx, ssl_sessionid, ssl_sessionid_len);
warning:             ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:1285:1: note: 'SSLSetPeerID' has been explicitly marked deprecated here
warning: SSLSetPeerID                            (SSLContextRef          context,
warning: ^
warning: curl/lib/vtls/sectransp.c:2103:9: warning: 'SSLSetIOFuncs' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:   err = SSLSetIOFuncs(backend->ssl_ctx, bio_cf_in_read, bio_cf_out_write);
warning:         ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:418:1: note: 'SSLSetIOFuncs' has been explicitly marked deprecated here
warning: SSLSetIOFuncs                           (SSLContextRef          context,
warning: ^
warning: curl/lib/vtls/sectransp.c:2109:9: warning: 'SSLSetConnection' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:   err = SSLSetConnection(backend->ssl_ctx, cf);
warning:         ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:657:1: note: 'SSLSetConnection' has been explicitly marked deprecated here
warning: SSLSetConnection                        (SSLContextRef                  context,
warning: ^
warning: curl/lib/vtls/sectransp.c:2317:9: warning: 'SSLCopyPeerTrust' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:   ret = SSLCopyPeerTrust(ctx, &trust);
warning:         ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:1261:1: note: 'SSLCopyPeerTrust' has been explicitly marked deprecated here
warning: SSLCopyPeerTrust                        (SSLContextRef          context,
warning: ^
warning: curl/lib/vtls/sectransp.c:2340:9: warning: 'SecTrustEvaluate' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:   ret = SecTrustEvaluate(trust, &trust_eval);
warning:         ^~~~~~~~~~~~~~~~
warning:         SecTrustEvaluateWithError
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecTrust.h:364:10: note: 'SecTrustEvaluate' has been explicitly marked deprecated here
warning: OSStatus SecTrustEvaluate(SecTrustRef trust, SecTrustResultType *result)
warning:          ^
warning: curl/lib/vtls/sectransp.c:2437:11: warning: 'SSLCopyPeerTrust' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:     ret = SSLCopyPeerTrust(ctx, &trust);
warning:           ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:1261:1: note: 'SSLCopyPeerTrust' has been explicitly marked deprecated here
warning: SSLCopyPeerTrust                        (SSLContextRef          context,
warning: ^
warning: curl/lib/vtls/sectransp.c:2441:14: warning: 'SecTrustCopyPublicKey' is deprecated: first deprecated in macOS 11.0 [-Wdeprecated-declarations]
warning:     keyRef = SecTrustCopyPublicKey(trust);
warning:              ^~~~~~~~~~~~~~~~~~~~~
warning:              SecTrustCopyKey
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecTrust.h:476:11: note: 'SecTrustCopyPublicKey' has been explicitly marked deprecated here
warning: SecKeyRef SecTrustCopyPublicKey(SecTrustRef trust)
warning:           ^
warning: curl/lib/vtls/sectransp.c:2543:9: warning: 'SSLHandshake' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:   err = SSLHandshake(backend->ssl_ctx);
warning:         ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:1641:1: note: 'SSLHandshake' has been explicitly marked deprecated here
warning: SSLHandshake                            (SSLContextRef          context)
warning: ^
warning: curl/lib/vtls/sectransp.c:2780:11: warning: 'SSLGetNegotiatedCipher' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:     (void)SSLGetNegotiatedCipher(backend->ssl_ctx, &cipher);
warning:           ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:1314:1: note: 'SSLGetNegotiatedCipher' has been explicitly marked deprecated here
warning: SSLGetNegotiatedCipher          (SSLContextRef          context,
warning: ^
warning: curl/lib/vtls/sectransp.c:2781:11: warning: 'SSLGetNegotiatedProtocolVersion' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:     (void)SSLGetNegotiatedProtocolVersion(backend->ssl_ctx, &protocol);
warning:           ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:803:1: note: 'SSLGetNegotiatedProtocolVersion' has been explicitly marked deprecated here
warning: SSLGetNegotiatedProtocolVersion         (SSLContextRef          context,
warning: ^
warning: curl/lib/vtls/sectransp.c:2783:12: warning: 'kSSLProtocol2' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:       case kSSLProtocol2:
warning:            ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecProtocolTypes.h:164:5: note: 'kSSLProtocol2' has been explicitly marked deprecated here
warning:     kSSLProtocol2 CF_ENUM_DEPRECATED(10_2, 10_15, 5_0, 13_0) = 1,
warning:     ^
warning: curl/lib/vtls/sectransp.c:2787:12: warning: 'kSSLProtocol3' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:       case kSSLProtocol3:
warning:            ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecProtocolTypes.h:165:5: note: 'kSSLProtocol3' has been explicitly marked deprecated here
warning:     kSSLProtocol3 CF_ENUM_DEPRECATED(10_2, 10_15, 5_0, 13_0) = 2,
warning:     ^
warning: curl/lib/vtls/sectransp.c:2791:12: warning: 'kTLSProtocol1' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:       case kTLSProtocol1:
warning:            ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecProtocolTypes.h:157:5: note: 'kTLSProtocol1' has been explicitly marked deprecated here
warning:     kTLSProtocol1 CF_ENUM_DEPRECATED(10_2, 10_15, 5_0, 13_0) = 4,
warning:     ^
warning: curl/lib/vtls/sectransp.c:2796:12: warning: 'kTLSProtocol11' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:       case kTLSProtocol11:
warning:            ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecProtocolTypes.h:158:5: note: 'kTLSProtocol11' has been explicitly marked deprecated here
warning:     kTLSProtocol11 CF_ENUM_DEPRECATED(10_2, 10_15, 5_0, 13_0) = 7,
warning:     ^
warning: curl/lib/vtls/sectransp.c:2800:12: warning: 'kTLSProtocol12' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:       case kTLSProtocol12:
warning:            ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecProtocolTypes.h:159:5: note: 'kTLSProtocol12' has been explicitly marked deprecated here
warning:     kTLSProtocol12 CF_ENUM_DEPRECATED(10_2, 10_15, 5_0, 13_0) = 8,
warning:     ^
warning: curl/lib/vtls/sectransp.c:2806:12: warning: 'kTLSProtocol13' is deprecated: first deprecated in macOS 10.15 [-Wdeprecated-declarations]
warning:       case kTLSProtocol13:
warning:            ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecProtocolTypes.h:161:5: note: 'kTLSProtocol13' has been explicitly marked deprecated here
warning:     kTLSProtocol13 CF_ENUM_DEPRECATED(10_2, 10_15, 5_0, 13_0) = 10,
warning:     ^
warning: curl/lib/vtls/sectransp.c:2821:15: warning: 'SSLCopyALPNProtocols' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:         err = SSLCopyALPNProtocols(backend->ssl_ctx, &alpnArr);
warning:               ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:1354:1: note: 'SSLCopyALPNProtocols' has been explicitly marked deprecated here
warning: SSLCopyALPNProtocols        (SSLContextRef      context,
warning: ^
warning: curl/lib/vtls/sectransp.c:2949:6: warning: 'SecTrustCopyPublicKey' is deprecated: first deprecated in macOS 11.0 [-Wdeprecated-declarations]
warning:   if(SecTrustCopyPublicKey) {
warning:      ^~~~~~~~~~~~~~~~~~~~~
warning:      SecTrustCopyKey
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecTrust.h:476:11: note: 'SecTrustCopyPublicKey' has been explicitly marked deprecated here
warning: SecKeyRef SecTrustCopyPublicKey(SecTrustRef trust)
warning:           ^
warning: curl/lib/vtls/sectransp.c:2951:11: warning: 'SSLCopyPeerTrust' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:     err = SSLCopyPeerTrust(backend->ssl_ctx, &trust);
warning:           ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:1261:1: note: 'SSLCopyPeerTrust' has been explicitly marked deprecated here
warning: SSLCopyPeerTrust                        (SSLContextRef          context,
warning: ^
warning: curl/lib/vtls/sectransp.c:2959:23: warning: 'SecTrustGetCertificateAtIndex' is deprecated: first deprecated in macOS 12.0 [-Wdeprecated-declarations]
warning:         server_cert = SecTrustGetCertificateAtIndex(trust, i);
warning:                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
warning:                       SecTrustCopyCertificateChain
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecTrust.h:523:19: note: 'SecTrustGetCertificateAtIndex' has been explicitly marked deprecated here
warning: SecCertificateRef SecTrustGetCertificateAtIndex(SecTrustRef trust, CFIndex ix)
warning:                   ^
warning: curl/lib/vtls/sectransp.c:3163:11: warning: 'SSLClose' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:     (void)SSLClose(backend->ssl_ctx);
warning:           ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:1731:1: note: 'SSLClose' has been explicitly marked deprecated here
warning: SSLClose                                        (SSLContextRef          context)
warning: ^
warning: curl/lib/vtls/sectransp.c:3165:8: warning: 'SSLCreateContext' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:     if(SSLCreateContext)
warning:        ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:316:1: note: 'SSLCreateContext' has been explicitly marked deprecated here
warning: SSLCreateContext(CFAllocatorRef __nullable alloc, SSLProtocolSide protocolSide, SSLConnectionType connectionType)
warning: ^
warning: curl/lib/vtls/sectransp.c:3271:11: warning: 'SSLGetBufferedReadSize' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:     err = SSLGetBufferedReadSize(backend->ssl_ctx, &buffer);
warning:           ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:1705:1: note: 'SSLGetBufferedReadSize' has been explicitly marked deprecated here
warning: SSLGetBufferedReadSize          (SSLContextRef context,
warning: ^
warning: curl/lib/vtls/sectransp.c:3314:6: warning: 'SSLSetSessionOption' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:   if(SSLSetSessionOption)
warning:      ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:384:1: note: 'SSLSetSessionOption' has been explicitly marked deprecated here
warning: SSLSetSessionOption                     (SSLContextRef          context,
warning: ^
warning: curl/lib/vtls/sectransp.c:3351:11: warning: 'SSLWrite' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:     err = SSLWrite(backend->ssl_ctx, NULL, 0UL, &processed);
warning:           ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:1670:1: note: 'SSLWrite' has been explicitly marked deprecated here
warning: SSLWrite                                        (SSLContextRef          context,
warning: ^
warning: curl/lib/vtls/sectransp.c:3370:11: warning: 'SSLWrite' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:     err = SSLWrite(backend->ssl_ctx, mem, len, &processed);
warning:           ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:1670:1: note: 'SSLWrite' has been explicitly marked deprecated here
warning: SSLWrite                                        (SSLContextRef          context,
warning: ^
warning: curl/lib/vtls/sectransp.c:3406:9: warning: 'SSLRead' is deprecated: first deprecated in macOS 10.15 - No longer supported. Use Network.framework. [-Wdeprecated-declarations]
warning:   err = SSLRead(backend->ssl_ctx, buf, buffersize, &processed);
warning:         ^
warning: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecureTransport.h:1689:1: note: 'SSLRead' has been explicitly marked deprecated here
warning: SSLRead                                         (SSLContextRef          context,
warning: ^
warning: 64 warnings generated.
 Compiling isahc v1.7.0 (/Users/someonetoignore/Downloads/isahc)
  Finished test [unoptimized + debuginfo] target(s) in 13.34s
   Running unittests src/lib.rs (target/debug/deps/isahc-bc75b44d80256336)
.... snip

that seems unrelated to current crash fix, so leaving as is but looks rather dangerous.

Is there a particular reason to wait for a new release to fix the linking issue? Are there changes on the curl side that are needed?

You're right indeed, we don't have to at all, just fix the build.rs
Sorry for circling around and confusing you, have pushed that single change and ensured that isahc tests now do not have the original error.

@ehuss do you think we can merge this (or whatever other fix on your mind)? Even cargo-update is broken on Sonoma which makes me especially sad, and I'd like to fix it.

@ehuss do you think we can merge this (or whatever other fix on your mind)? Even cargo-update is broken on Sonoma which makes me especially sad, and I'd like to fix it.

Take a look at the workarounds I suggested on nabijaczleweli/cargo-update#240

Thank you, that would fix cargo-update, but there are more crates that fail for me (one has a transitive dependency on isahc and working around that is even more tedious) and instead of working around every one of them, I would love to have them all fixed, would that be possible to do somehow?

I would recommend also applying this change to make it easier for the maintainers to publish a new version.
--- a/curl-sys/Cargo.toml
+++ b/curl-sys/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "curl-sys"
-version = "0.4.66+curl-8.3.0"
+version = "0.4.67+curl-8.3.0"
 authors = ["Alex Crichton<EMAIL_ADDRESS> links = "curl"
 build = "build.rs"

Thank you, Monday starts to look not that bad after this.
I've bumped the version, as proposed.

@alexcrichton , seems that you're the one who can help with the final steps to fix Sonoma's issues with curl: if the PR looks fine to you, could you please merge it and make another release?


about parameter auto mapping to vc property

every time i open url , i will need to map the value to some property, i think i should be auto mapped if the  property name is the same .

Please provide PR for this, I don't have time to fix this easy one


Remember accepted profile warnings

Currently, when visiting a profile with a profile warning, you have to accept the warning on every visit. For improved usability it'd be cool if the site remembered if we accepted the warning before.
Note: This should take into account that people might change their profile warning (for whatever reason), so maybe a hash of the content should be stored as state when a warning has been accepted, so in case the warning changed, it can be shown again even when previously accepted.

Fixed, thank you!
This is done fully on client (stored in localStorage.accepted_warnings) because there's no need to store extra stuff like this on the server.
The hash is checked by client JS against the stored hash that we previously accepted. The warning will be shown again if the hash is different.


SVG Component Showing Blank After Updating to Version 15.4.0

Description
After updating to React Native SVG version 15.4.0, everything works as expected except for one specific SVG component, which appears blank

15.3.0
15.4.0

Steps to reproduce
1- Build the application for iOS/Android using version 15.4.0
2- Open the application on a simulator (both iOS and Android)
3- Observe that the SVG component appears blank
Snack or a link to a repository
https://github.com/aljadan/react-native-svg-issue
SVG version
15.4.0
React Native version
0.74.5
Platforms
Android, iOS
JavaScript runtime
None
Workflow
None
Architecture
None
Build type
None
Device
None
Device model
No response
Acknowledgements
Yes

Did you try to update to 15.5.0 version? I saw this in changelog https://github.com/software-mansion/react-native-svg/pull/2345

Hi @aljadan,
I tested your icon on the latest version, v15.8.0, following the recent fixes, and everything is working as expected. Let me know if it’s working on your end or if there's anything that needs to be fixed.

Hello @jakex7
Everything is working as expected, thank you so much for all your hard work


EVP access to CTS based ciphers

Currently CTS is done using a special mode that sits over ECB & CBC.  It does not use EVP level calls and bypasses the provider interface.
To confound things there are multiple definitions of how CTS is done.

@paulidale still an issue?

Not an issue anymore I suspect.  We've some CTS ciphers defined and that's likely good enough.  Closing.


Hotfix/planar tutorial fixes

fix: bug that prevented ORB from finding any features
fix: utilize bounding box in frame bootstrap (previously was entire frame)
feature: add ability to capture input from device
feature: local namespace to avoid Tracker class collision
feature: add optional ROI selection from input data

Thanks! :+1:


Integrations

Depends on this PR. DO NOT MERGE.
Before merging (once PR #13 has been merged), switch the base branch to v2.

This pull request adds the support for integrations.

Self merge.


Getting Started Guide?

I'm new to rust and bl602. Is any Getting Started Guide available? When I run:
cargo run --example bl602-gpio-blinky
I get:
error: linking with `rust-lld` failed: exit status: 1
rust-lld: error: undefined symbol: TimerCh1
rust-lld: error: undefined symbol: Gpio
rust-lld: error: undefined symbol: TimerCh0

rustc 1.54.0-nightly (4de757209 2021-05-01)
MacOS 10.13.6

Sorry for the late reply!
There was a change in sipeed/bl602-hal#21 which required some changes here, which were never applied.
I've gone ahead and added it, so if you update your bl602-rust-guide repo, it should work now.


is date ranges the only field that can be estimated

Issue in /src/pages/guides/endpoints/data-repair/server-call-estimate.md
Cab we make a note whether estimations can include conditions?

Hi @jsoohoo2
When you say "conditions", are you referring to filter criteria added to the Data Repair job?  Assuming this is what you mean, we don't support conditions on the Server Call Estimate endpoint because the API bills on rows scanned, not rows matched/changed.  If we supported conditions, it could significantly underestimate the cost for a job.


[UI] Get onboarding code

@jkralik Extended oAuthConfig for the UI:
{
  "domain": "",
  "clientID": "",
  "audience": "",
  "scope": "",
  "httpGatewayAddress": "",
  "deviceOauthClient": {
    "clientID": "",
    "audience": "",
    "scope": "",
    "providerName": ""
  }
}

@jkralik @ondrejtomcik

Renamed auth_config.json to web_configuration.json
Updated the web_configuration.json structure
Updated the docs dashboard section about the config
Changed scope to scopes array


The Merge layer is deprecated

Thank you for share your work.
When I trying to run the model using market1501 database, I have problem like this:
File "model_for_market1501.py", line 69, in cross_input_asym
tensor_left_padding = K.spatial_2d_padding(tensor_left,padding=(2,2))
File "/usr/local/lib/python2.7/dist-packages/Keras-2.0.3-py2.7.egg/keras/backend/tensorflow_backend.py", line 1834, in spatial_2d_padding
assert len(padding[0]) == 2
TypeError: object of type 'int' has no len()
my tensorflow version is  ** 0.12**
Thankou for help!!

Hi, it's my pleasure to share the work.
I have updated the model definition script last night, you could use the latest version Keras to define the model now. Today I will complete the model compile part.

Is there an update on this? I'm still getting "TypeError: object of type 'int' has no len()." Otherwise, is there a last known version of keras/tensorflow in which this worked?
Regardless, I appreciate your work on this implementation.

Hi, Have you solved this? I met this problem too.

The  versions of keras and tensorflow worked for my case  is  :
keras 2.0.4
Tensorflow 1.2.1
Python 2.7.12
I run with CUHK03
But it is incredibly resource intensive .. it takes days with two 11gb GTX1080ti GPU connected with SLI which I enable it going to /etc/X11/xorg.conf  and core i9 CPU ...  with min_batch of  150 ( though the author recommended to make it 50 if resource is an issue)
Anybody who complete running the model on CUHK03 ? how long does it take ? what environment/resource you used  ?

I completed training the CUHK03 model with two 11G GTX1080ti GPUs, tensorflow 1.1, keras 2.0.0. It takes me about 50 hours. @bmiftah


Pass --linter=rubocop --test=rspec to bundle gem

The generator expects to patch RSpec files, so specifying anything other than rspec as the test framework would break generation. Therefore, it makes sense to specify it ourselves, and save the user the time of having to select it.
It also seems very unlikely that someone would want to generate a RuboCop extension, but use a linter other than RuboCop, so let's save the user the time.

This turns out to be similar to #10, but takes a different approach, by forcing RSpec, rather than checking for it.


[Android] make_apk: Improve the version handling code related messages.

This is an alternative take at XWALK-3473 (compared to #2892), which is about the error messages and option descriptions we have for the --app-version, --app-versionCode and --app-versionCodeBase options being hard to understand.
While here, I've also simplified the code in both MakeVersionCode() and TryCodeBaseFromVersionName() and made them more Pythonic and easier to understand.
BUG=XWALK-3473

@lincsoon @wuhengzhi

LGTM


added support for handlebars

Just checked and it's ok. I will release a new version in a moment. Thanks for the contribution!


Small bug fix in the create_release_map.py script.

An issue #17 was raised where the fisheries dataset would have latitude and longitude column names 'ModelLatitude' and 'ModelLongitude', which would not work nicely with the create_particleset_from_map function. This PR adds the required line to rename the latitude and longitude columns.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 15.43%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #30   +/-   ##
=======================================
  Coverage   15.43%   15.43%
=======================================
  Files           6        6
  Lines         473      473
=======================================
  Hits           73       73
  Misses        400      400

Flag
Coverage Δ

unit-tests
15.43% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


allow 8x8 and 16x8 sprites

the minimum is 16px as you already know.
I want to make small 8px sprites.
also, allow 8px spacing in spritesheets like this:

for now this needs 8px vertical spacing in a 16px sprite, seems wasteful.

Those aren't already allowed? Dang, that's odd...

Those aren't already allowed? Dang, that's odd...

From what I understand, the underlying engine supports 8x8 sprites as an option but the IDE doesn’t support it. It’s possible that this feature could be implemented, but it might make the sprite editor more complicated
Either way, in a scene you are only allowed to have 8x8 or 8x16. You can’t mix and match them. It’s not supported by the hardware. SO if you want 8x8 support, that’s something to think about
Due to the complexity, I imagine it would be more likely a setting that applies to the whole game instead of per scene, since you might have to create different sprites for the different tile sizes

I'd love to be able to use a sprite that is only 8px wide. I don't care if it is 16px tall but I need it to be narrower.

I'd love to be able to use a sprite that is only 8px wide. I don't care if it is 16px tall but I need it to be narrower.

Good news: You already can! Just use one sprite tile. They're always 8px wide. Put it in the canvas and edit the hit box to be 8 wide

I have a fork that uses 8x8 sprite tiles. 8x8 mode can only cover half of the screen real estate that 8x16 mode can, but having more control over the color, properties, and positions of sprites in animations is awesome.
My plan is to make it a per-animation setting and to show a warning on scenes where mixed sprite tile sizes are used.

I have a fork that uses 8x8 sprite tiles. 8x8 mode can only cover half of the screen real estate that 8x16 mode can, but having more control over the color, properties, and positions of sprites in animations is awesome.
My plan is to make it a per-animation setting and to show a warning on scenes where mixed sprite tile sizes are used.

That's awesome. I wonder if you could make that a plugin or scene type

There's no technical reason for it to not work with all scene types.
If you use an 8x16 animation in 8x8 mode, it just turns off the bottom half of each sprite (which could be a neat effect if you toggle the mode). Converting 8x16 animations to work in 8x8 mode could be done easily (ie. duplicate all tiles, move them down 8px, increase their index by 1).
If you use an 8x8 animation in 8x16 mode, you'll get whatever sprite was below it on your sprite sheet. Converting 8x8 to 8x16 would be maybe a bit more difficult, but still doable to some degree (ie. discard all odd indexed tiles where its even numbered counterpart is 8px above it).
I was thinking the feature would look like this:

a project setting for the default mode (the mode that gets set when a game launches
a toggle on the sprite view for which mode you're editing in (similar to the preview as monochrome button)
maybe buttons to convert animations in the way described above
a scene event that let's you change the mode

That would be cool. I can definitely see the benefit because you'd be able to create more colorful sprites using 8x8 sprite mode. Having more granular control over the palettes


Feature request: add get_seed method for Rng

I have a use case where I would like to generate new Rng with random seed and do a bunch of tests with it, but be able to get the seed back when my test fails so I can reproduce it. Currently there is no way to get a seed from Rng, other than transmuteing it into u64 which I think currently would work but is very stupid (unless Rng would become #repr(transparent) but I don't think it's a good idea). My workaround was to generate myself a random seed, store it and then create Rng with that seed. However I would argue that this is quite troublesome and could be very well avoided by adding a simple function to Rng.
I therefore propose adding method get_seed (or any other name) for Rng that would get seed from inner Cell and then return it to user. It has even additional benefit that user would get current seed and not the initial, so there is no need to emulate previous random generations.
I would be happy to provide a PR for that feature or here objections to this proposition if there are any.

I would accept a PR to add this.

@taiki-e Are you saying that you would accept that PR from me, or that you would do it?
Nb. I am new to this project and don't quite know who is the maintainer of this library and from whom should I get a blessing. 😉

I meant "if you (or someone) send a PR, I would accept it and merge it".

don't quite know who is the maintainer of this library and from whom should I get a blessing.

I'm one of the maintainers so I can merge your PR and release it.
(FWIW, one of the ways to know who is the maintainer is to look at who merged past PRs and who created past releases.)

Thank you. I will try to create it as soon as possible.


Why all of return value type are array, if request '/p3/serviceValidate?format=JSON' ?

Hi, this is Yushi.
I'm wondering about something.
If call /p3/serviceValidate endpoint with query of format=JSON, like his.
$ curl -v "http://localhost:8080/cas/p3/serviceValidate/?format=JSON&service=http%3A%2F%2Flocalhost%3A8080%2Fsomeclient%2F&ticket=ST-1-XXXXXXXXXXXXXXXXXXXX-y-koga

Then it returns response but all value type of attributes are array.
{
  "serviceResponse" : {
    "authenticationSuccess" : {
      "user" : "casuser",
      "attributes" : {
        "username" : [ "casuser" ]
        "isFromNewLogin" : [ true ],
        "authenticationDate" : [<PHONE_NUMBER>.644000000 ],
        "successfulAuthenticationHandlers" : [ "AcceptUsersAuthenticationHandler" ],
        "authenticationMethod" : "AcceptUsersAuthenticationHandler",
        "longTermAuthenticationRequestTokenUsed" : [ false ],
      }
    }
  }
}

Although, it's written that we can request JSON at Section 2.5.1 of CAS protocol specification,
Is JSON format supported officially ?

[x] CAS server version

I've confirmed with 5.1.0.

[x] Container/environment type/version (Tomcat, Jetty, Java, Linux/Windows, etc)

Java8, I'm running the CAS web application as an executable WAR.

[ ] Steps to duplicate the problem along with your CAS settings and properties

n/a

[ ] Stacktraces and CAS DEBUG logs where appropriate.

n/a

[ ] Configuration/Overlay pushed to https://github.com/cas-projects/cas-issues/ or attached to the issue.

n/a

Yes it is supported officially. After all, you're getting JSON.


Multi dimensional coord trait

/// A trait for accessing data from a generic Coord.
pub trait CoordTrait<const DIM: usize> {
    type T: CoordNum;

    /// x component of this coord
    fn x(&self) -> Self::T;

    /// y component of this coord
    fn y(&self) -> Self::T;

    fn third_unchecked(&self) -> Self::T;

    fn third_opt(&self) -> Option<Self::T> {
        if DIM >= 3 {
            Some(self.third_unchecked())
        } else {
            None
        }
    }

    fn fourth_unchecked(&self) -> Self::T;

    fn fourth_opt(&self) -> Option<Self::T> {
        if DIM >= 4 {
            Some(self.fourth_unchecked())
        } else {
            None
        }
    }

    fn array(&self) -> [Self::T; DIM];

    /// Returns a tuple that contains the x/horizontal & y/vertical component of the coord.
    fn xy(&self) -> (Self::T, Self::T) {
        (self.x(), self.y())
    }
}

It might also make sense to have a general nth_unchecked(&self, i: usize) -> Self::T
Then
/// A trait for accessing data from a generic LineString.
pub trait LineStringTrait<const DIM: usize>: Sized {
    type T: CoordNum;
    type ItemType<'a>: 'a + CoordTrait<DIM, T = Self::T>
    where
        Self: 'a;
...

Implemented in https://github.com/geoarrow/geoarrow-rs/pull/667


[Logic] Model validation fails with errors

Model validation reports erros when validating responses against .net tests recordings for logic 2015-08-01 spec:
> Operation: IntegrationAccountAgreements_List
> x-ms-examples
> Scenario: ListIntegrationAccountAgreementsGET115
> InnerErrors:
3. code: ENUM_MISMATCH
message: No enum match for: EDIFACT
path: value,1,properties,agreementType
> Operation: IntegrationAccountSchemas_CreateOrUpdate
	> x-ms-examples
		> Scenario: CreateAndDeleteIntegrationAccountSchemaPUT62
			> InnerErrors:
			  1. code: INVALID_TYPE
			     message: Expected type object but found type string
			     path: properties,metadata
			     description: The metadata.
			  2. code: INVALID_TYPE
			     message: Expected type object but found type string
			     path: properties,content
			     description: The content.

From swagger:
    "AgreementType": {
      "type": "string",
      "enum": [
        "NotSpecified",
        "AS2",
        "X12",
        "Edifact"
      ],
      "x-ms-enum": {
        "name": "AgreementType",
        "modelAsString": false
      }
    },

  "IntegrationAccountSchemaProperties": {
      "type": "object",
      "properties": {
        "schemaType": {
          "$ref": "#/definitions/SchemaType",
          "description": "The schema type."
        },
        "targetNamespace": {
          "type": "string",
          "description": "The target namespace."
        },
        "createdTime": {
          "type": "string",
          "format": "date-time",
          "readOnly": true,
          "description": "The created time."
        },
        "changedTime": {
          "type": "string",
          "format": "date-time",
          "readOnly": true,
          "description": "The changed time."
        },
        "content": {
          "type": "object",
          "description": "The content.",
          "properties": {}
        },
        "contentType": {
          "type": "string",
          "description": "The content type."
        },
        "contentLink": {
          "$ref": "#/definitions/IntegrationAccountContentLink",
          "readOnly": true,
          "description": "The content link."
        },
        "metadata": {
          "type": "object",
          "description": "The metadata.",
          "properties": {}
        }
      }
    },

Other models in the spec containing 'metadata' and 'content' show similar issue.
> Operation: Workflows_Validate
	> x-ms-examples
		> Scenario: ValidateWorkflowPOST203
			> InnerErrors:
			  1. code: INVALID_TYPE
			     message: Expected type object but found type string
			     path: properties,definition

Also for logic 2016 spec:
        "definition": {
          "$ref": "#/definitions/Object",
          "description": "The definition."
        },

@kirthik already fixed

@pankajsn - Could you please provide the commit id?

closing and if not fixed this would blocked at a PR level as specs are being updated


Generate keys and certificates in CI.

Generate keys and certificates in CI.
Minor:

Remove a few unused SGX- and TZ-related artefacts.
Remove unused Error cases.

As we discussed in the meeting today, it might be good to replace the RSA keys with ECDSA keys at the same time. Replacing openssl genrsa 2048 with openssl ecparam -name secp521r1 -genkey might work, for example.

The current commit (506a477c7a25a53efed6e9c130196f1cc2434191) passed on CI but veracruz_phase2_intersection_set_sum_three_clients seems to fail on my machine.

Another thing: changes to Cargo.lock files do not seem to have been committed.

When I rebased this onto main, there were no conflicts, but some of the tests failed. Have anyone else tried that?

The problem seems to be with the way the CAKey and CACert are generated: if I regenerate those two files on main with the recipe used in this PR, then the tests fail.

I think you should probably rebase this PR onto main and force-push that, so that we see the CI failure here.
Then replace secp256k1 with prime256v1 in workspaces/shared.mk and push again: with any luck that will pass. (I'm testing locally now.)

What are the changes in vc.c? There doesn't seem to be any obvious link with the description of this PR or the corresponding commit message.

What are the changes in vc.c? There doesn't seem to be any obvious link with the description of this PR or the corresponding commit message.

I updated the PR message now. The vc.c should be changed since we change the structure of the protocol buffer.


Link Icons

My formatter made a complete mess of things but essentially created a Links wrapper component to put an individual Link in and added the ability to have an SVG icon for the link.
I can scrap this and do it over with formatting fixed if requested.

This looks great!
@jeffrainey do you have any suggestions for alignment or maybe putting the icons in their own square in the rectangle?

Closes #15


reconnect after lost connection

Hi! I need reconnect to all text rooms after lost connection or after connection was refused. Please. help. How i can do it?

For this you can use connectivity package to see if connectionstate got disconnected in that event you can use saved user info to connect user back to room if connection is back on, i hope this solves your issue
Closing for now you can reopen if you find bug in package itself

after reconnect i must dispose all?

Well it would be better idea to recreate new session instance and then attach the plugin on it to make sure everything is working as expected

You know what i will add it in my todo list using connectivity package and add auto reconnect in the event of disconnected network state

For the time being you can use the approach i told you

very often the socket crashes on its own. what to do in this case? while my server is working properly. the socket may just fall

I don't believe it would crash on its own unless network state has been changed

Maybe it's my mistake. I try to research. Thanks!

closing as it is not planned, it is not that urgent anyway maybe i will revisit it as an enhancement in future


(PUP-9118) Add option to stringify resource parameters

Before this, the to_data_hash for a Resource would either return
generic data representing rich data, or a stringified version +
warnings or error (depending on strictness).
For use cases such as PDB that cannot handle rich values a more DB
friendly format is required. In order to allow PDB terminus to get a
data hash of a Resource with suitably stringified parameter values (as
produced by the ToStringifiedConverter) it is now possible to get this
by setting :stringify_rich to true in the context.
Puppet.override(:stringify_rich => true, 'example') do
  a_resource.to_data_hash
end

CLA signed by all contributors.


Throw CorruptSegmentInfoException on encountering missing segment info (_N.si) file in CheckIndex

Description
Changes:

Throw CorruptSegmentInfoException on encountering missing segment info (_N.si) file in CheckIndex. This is a step towards enabling #7820

Decided to tackle this in smaller steps -

Made a new (simpler) revision where we throw a more specific error on encountering missing segment info. Created a new exception CorruptSegmentInfoException.java
Will create a new commit (or issue?) to add in fixes and unit tests for exorciseIndex

I edited the PR description to more accurately represent what is being done. We aren't dealing with the exorcism issue yet, but throwing the right exception on encountering missing segment info. I will tackle the final step (actually making exorcism possible) in a subsequent PR

Thanks @gokaai -- I'll try to review soon!
If possible please try not to force-push: it removes the history of the past commits and makes it harder to see what changed on this iteration :)

Thanks @gokaai -- I'll try to review soon!
If possible please try not to force-push: it removes the history of the past commits and makes it harder to see what changed on this iteration :)

Sorry about that @mikemccand . I messed up my workspace and couldn't salvage it - I'll keep it in mind while making any new revisions.

Thanks @gokaai -- I'll try to review soon!
If possible please try not to force-push: it removes the history of the past commits and makes it harder to see what changed on this iteration :)

Sorry about th

Ahh OK no worries.  I experience such git disasters myself far more often than I would hope :)

Thanks @gokaai -- I'll try to review soon!
If possible please try not to force-push: it removes the history of the past commits and makes it harder to see what changed on this iteration :)

Sorry about th

Ahh OK no worries. I experience such git disasters myself far more often than I would hope :)

Look at what git reflog does and how it may help. It is really, really difficult to not be able to recover your work with git.


Project Specs Format

We should agree on some format to list the specs. It can be something like that.

Operation

Type
Required Fields
Access

For example;

Register new user

POST
[name: str, email: str, password: str]
Everyone

Create new post

POST
[title: str, description: str, tags: Array]
Users

Please comment on this issue and lets agree upon a format.
After this, we need to specify the database model and schema (User: {id, name, email, passwordEncrypted, interesAreas ...}). It should be a new issue.

One side note: Type is not model like user or post. It is the request type that helps us identify operations.
Create: POST
Read: GET
Update: PUT
Deletete: DELETE
Reference

I think this is few steps ahead of what we are currently supposed to do. We still need a contextual collection of all the requirements and the scenarios that are within the scope of our product.
If we consider this first meeting as a meeting with our customers, we still need to make a draft and show what we understood to our customers. Then, they will go over what we have and give us a more accurate list of their demands and we will modify the requirements. This will go back and forth until both our customers and our team know what the product will be. We cannot decide on any of the technical issues until we know what we are doing.

Gotcha! We could indeed decide on a spec format for now and start building them only after the project reaches a level of certainty. We will see what the future holds for us 😄.

Outdated.


error when adding Teams Channel owner

I am using the latest Teams PowerShell module from the PowerShell Test Gallery.
PS C:\WINDOWS\system32> add-TeamChanneluser -GroupId 0b910d5d-d1b6-463e-b705-a6377229a5d3 -user<EMAIL_ADDRESS>-displayname xxxxS
PS C:\WINDOWS\system32> add-TeamChanneluser -GroupId 0b910d5d-d1b6-463e-b705-a6377229a5d3 -user<EMAIL_ADDRESS>-role Owner -displayname xxxxS
add-TeamChanneluser : Error occurred while executing
Code: GeneralException
Message: Failed to execute Skype backend request BulkMembershipS2SRequest.PUT.
InnerError:
RequestId: 5f607439-51cc-40e3-b9f6-21740cff6de2
DateTimeStamp: 2019-11-20T23:49:20
HttpStatusCode: GeneralException
At line:1 char:1

add-TeamChanneluser -GroupId 0b910d5d-d1b6-463e-b705-a6377229a5d3 -us ...

  + CategoryInfo          : NotSpecified: (:) [Add-TeamChannelUser], ApiException
  + FullyQualifiedErrorId : Microsoft.TeamsCmdlets.PowerShell.Custom.ErrorHandling.ApiException,Microsoft.TeamsCmdle
 ts.PowerShell.Custom.AddTeamChannelUser

also, -membershiptype is not a parameter for add-TeamChannelUser

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 33e0ac38-cfff-8d8f-5345-2ae93a9fae2e
Version Independent ID: bec44289-e9fa-4464-1601-0ca86d61e6ca
Content: Manage the life cycle of private channels in Microsoft Teams - Microsoft Teams
Content Source: Teams/private-channels-life-cycle-management.md
Service: msteams
GitHub Login: @LanaChin
Microsoft Alias: v-lanac

I have found that this error occurred because I was not an owner of the private channel.  Still, a better message would be useful

@jimcantor thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.

I'm getting an error as well. Would be nice if the group owner automatically has access to all private channels. Can see private channels being ownerless after a while from users leaving/offboarding.


Tonomy network mainnet: resource model

Acceptance criteria

[ ] modify the eosio.bios contract so that it initialises the oncoin.tmy contracts currency as the system resource currency
[ ] modify the eosio.bios contract so that this currency is used as the resource token in the network
[ ] Implement the resource model in the eosio.bios contract
[ ] this should be at least, manually verified as working

use plan here https://docs.google.com/document/d/1mO33PVx_SwBX9OqXoVEQij_Tr3ypUBVrYnE8QksP8ZA/edit#heading=h.ijmdy64x5yj2

previous sprint: 3
next sprint: 2

next sprint: 1
current sprint: 1


Replace let with const

In other places, const is used consistently. I think using let here might cause unnecessary confusion.

I think they intentionally used let here, since these values need to be able to change during a state update. For example, the value of isScrollingDown will toggle between true and false, and the use of const wouldn't allow for that.

Thanks for your reply! But I do not think so :(
The value of isScrollingDown is consistent while ScrollView is executing.
State changes initiated by setIsScrollingDown will cause another execution of ScrollView possibly with a different value of isScrollingDown.
If you assign some value to isScrollingDown, it will be out of sync with "the actual state" managed by React. By using const here, we can avoid this situation.
That's why I think using let here is confusing and we should fix this.

This was fixed separately, but thank you for the PR!


Create Redux CRA+TS template

Now that we have the plain JS template at https://github.com/reduxjs/cra-template-redux published as 1.0.0, we can start working on the TS template.
Based on the process we used for that template, seems like we should:

Create a PR here that adds the entire contents of the standard CRA TS template, minus the version numbers, and merge that in
Create a PR that clears out the source code contents (or possibly just skip all the source in the first PR)
Create a PR that ports the code from the JS template, and converts it all to TS.

@BenLorantfy indicated he was interested in doing this one too ( https://github.com/reduxjs/cra-template-redux/pull/1#issuecomment-587266306 ) , but could probably get a couple folks collaborating here.

I'm interested to help as well. Please let me know if there's anything I can do! @BenLorantfy

@lukyth : thanks!  As a starting point, can you file a PR to add the entire contents of the existing CRA+TS template from https://github.com/facebook/create-react-app/tree/master/packages/cra-template-typescript ?  Move the content to the root of the repo, and go ahead and remove all source files exist for index.tsx.  (Maybe just throw in a tiny const App = () =>
Hello
 in index.tsx as a placeholder.)
See the PR where we added the default JS template as an example:
https://github.com/reduxjs/cra-template-redux/pull/2

Yeah if someone could create a PR with the contents of the default CRA+TS template that would be helpful so we can see the changes between the default CRA+TS template and the Redux+TS template

can you file a PR to add the entire contents of the existing CRA+TS template

Let me take care of that :)

Do you want me to help with bringing content from cra-template-redux over here and convert it to TS? @BenLorantfy

I'm working on that right now

I think this is done


Truly graceful shutdown

The rest of the #365 story. The key idea and the flow are described in comments.
There're still a few things I need to add/check:

[done] tests
[done] documentation
[done] shutdown-gracefully with 1-arity
[done] fix/rethink the problem with executor being shutdown earlier

Sharing this to get early feedback as it got quite complex and there're a few design choices that are not obvious/intuitive.

@ztellman This one is also ready to be reviewed.
What do we have here?

netty/graceful-shutdown with a few timing options, returns deferred that yield when shutting down is finished or timed out.

on-shutdown parameter for a new websocket connection (server) to be notified about the server being shutting down to clean up properly.

netty/ConnectionManager protocol, netty/noop-connections-manager that does not track anything (used for TCP servers and as an option for those whose main concern is performance).

Connection hijacking mechanism (using event triggering through the pipeline) to mark that the connection should be managed manually, not automatically (used for WebSockets and left as "public" API for any other use cases, e.g. long-polling, files transfer etc).

There're quite a few changes here... would love to hear a feedback :)

Thanks for your work on this, I'm going to have to take some time to review it.

@ztellman Sure, this one is kinda tricky 😑Let me also fix those merge conflict here.

Updated.

I just tested out the ft-gracefull-shutdown branch and it made my tests pass.
My tests wouldn't pass by using (.close server) (netty/await-for-close) from aleph 0.4.6 nor 0.4.7-alpha2. Was also seeing the exceptions mentioned in #365

@ztellman Updated to resolve conflicts with the latest introduced :manual-ssl? option

@petterik Your tests fail specifically because of java.lang.ClassNotFoundException, right? Or is there something else?

@kachayev: These are the errors I'm getting [aleph "0.4.6"] and [aleph "0.4.7-aleph2"]:
18-10-30 19:45:03 periksson-mac.local WARN [io.netty.util.concurrent.DefaultPromise:151] - An exception was thrown by aleph.netty$wrap_future$reify__49615.operationComplete()
                                                      java.lang.Thread.run                         Thread.java: 748
                      io.netty.util.concurrent.FastThreadLocalRunnable.run        FastThreadLocalRunnable.java:  30
               io.netty.util.concurrent.GlobalEventExecutor$TaskRunner.run            GlobalEventExecutor.java: 248
                             io.netty.util.concurrent.DefaultPromise$1.run                 DefaultPromise.java: 435
                        io.netty.util.concurrent.DefaultPromise.access$000                 DefaultPromise.java:  33
                io.netty.util.concurrent.DefaultPromise.notifyListenersNow                 DefaultPromise.java: 485
                   io.netty.util.concurrent.DefaultPromise.notifyListener0                 DefaultPromise.java: 511
io.netty.util.concurrent.MultithreadEventExecutorGroup$1.operationComplete  MultithreadEventExecutorGroup.java: 117
                        io.netty.util.concurrent.DefaultPromise.setSuccess                 DefaultPromise.java:  94
                   io.netty.util.concurrent.DefaultPromise.notifyListeners                 DefaultPromise.java: 424
                io.netty.util.concurrent.DefaultPromise.notifyListenersNow                 DefaultPromise.java: 485
                   io.netty.util.concurrent.DefaultPromise.notifyListener0                 DefaultPromise.java: 511
                           aleph.netty/wrap-future/reify/operationComplete                           netty.clj: 199
                                                manifold.deferred/success!                        deferred.clj: 243
                                        manifold.deferred.Deferred/success                        deferred.clj: 398
                                    manifold.deferred.Deferred/fn/<clinit>                        deferred.clj: 398
                                                                       ...
                                                   java.lang.Class.forName                          Class.java: 348
                                                  java.lang.Class.forName0                           Class.java
     java.lang.ClassNotFoundException: clojure/lang/PersistentArrayMap
java.lang.ExceptionInInitializerError:

18-10-30 19:45:14 periksson-mac.local WARN [io.netty.util.concurrent.DefaultPromise:151] - An exception was thrown by aleph.netty$wrap_future$reify__49615.operationComplete()
                                                      java.lang.Thread.run                         Thread.java: 748
                      io.netty.util.concurrent.FastThreadLocalRunnable.run        FastThreadLocalRunnable.java:  30
               io.netty.util.concurrent.GlobalEventExecutor$TaskRunner.run            GlobalEventExecutor.java: 248
                             io.netty.util.concurrent.DefaultPromise$1.run                 DefaultPromise.java: 435
                        io.netty.util.concurrent.DefaultPromise.access$000                 DefaultPromise.java:  33
                io.netty.util.concurrent.DefaultPromise.notifyListenersNow                 DefaultPromise.java: 485
                   io.netty.util.concurrent.DefaultPromise.notifyListener0                 DefaultPromise.java: 511
io.netty.util.concurrent.MultithreadEventExecutorGroup$1.operationComplete  MultithreadEventExecutorGroup.java: 117
                        io.netty.util.concurrent.DefaultPromise.setSuccess                 DefaultPromise.java:  94
                   io.netty.util.concurrent.DefaultPromise.notifyListeners                 DefaultPromise.java: 424
                io.netty.util.concurrent.DefaultPromise.notifyListenersNow                 DefaultPromise.java: 485
                   io.netty.util.concurrent.DefaultPromise.notifyListener0                 DefaultPromise.java: 511
                           aleph.netty/wrap-future/reify/operationComplete                           netty.clj: 199
                                                manifold.deferred/success!                        deferred.clj: 243
                                        manifold.deferred.Deferred/success                        deferred.clj: 398
java.lang.NoClassDefFoundError: Could not initialize class manifold.deferred.Deferred$fn__46265

@petterik Oh, yeah. Those are the same we've discussed in #365. I didn't find any specific reason for ClassNotFoundException to be thrown there. And it does occur quite rarely and quite randomly in my tests. Do you always see the same behavior?  I'm going to spend some more time digging deeper on this matter.

@ztellman Zach, that's the question to you:
Right now aleph.netty/wrap-future creates an intermediate deferred passing nil as an executor. Here. The change was "quietly" introduced with this commit. Was that intentional?

@petterik Would you please run your tests with the latest changes I've pushed to this branch? I'm super curious.

@kachayev There's quite a large number of tests and I did see errors happening every time I ran the test suite. I don't know, however, whether they happen in the same order nor if it's it was the same exact tests that caused these errors.

@kachayev Yes! Will do. Btw, to be clear, I did not get any test errors with this branch earlier, as I wrote here: https://github.com/ztellman/aleph/pull/406#issuecomment-430059912

@petterik Thanks in advance!

@kachayev Looking good! 👍
Ran our test suite 3 times and got no errors using a jar built from your commit:
commit 32d66378db2845cbce4de44015ba94026350d4bb (HEAD, kachayev/ft-gracefull-shutdown)
Author: Alexey Kachayev<EMAIL_ADDRESS>Date:   Thu Nov 1 18:30:06 2018 +0100

    [WIP] Just an experiment to double check that wrap-future is the root of the problem

@petterik Well... on the one hand, that's a really good news. On the other hand, it doesn't make me feel better as I've just avoided calling the function that caused the problem w/ no proper understanding of what the problem was actually about. Could work for now, but not a really sustainable for long running future. So I'm going to leave this solution as a default implementation for now (as it's way better than previous) while still looking for a real root of the problem.

@petterik One another question here: do you experience any issues with leak detector when running your tests? It would not force aleph to fail in any way, it will be just printed into the log (if appropriate leak detection level was set).

Okay... finally I found the cause of the problem and the proper solution for it. @petterik would you please check with your tests suite? Looking forward to hearing the feedback :)

Okay... finally I found what causes the problem. And the proper solution for that. @petterik  would you please run the latest version through your tests suite? I would love to hear your feedback!

Just ran my test suite with b5dd386 and it passes! I totally missed the question you asked earlier, sorry about that.
I'm impressed you found that root cause explained in #425! 👏

@petterik Thanks!

After carefully reviewing this PR (again), I'm going to close this. Overall, the change seems subtle but it might have negative runtime implications (e.g. performance, GC or unpredictable timeouts). Such a fundamental functionality requires careful prod-environment testing which I don't have access to right now. If anyone wants to pick up the branch to do further research/testing, I would be more than happy to provide guidance/explanations.
The only part of this effort that I would love to keep is, in fact, fixed initializer exception in listeners. But it was already back-ported into master branch earlier.


[BEAM-5959] Update GCS apitools client.

Updated to add KMS support.

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

run python postcommit

R: @chamikaramj

LGTM

Retest this please

Looks like client was already upgraded: https://github.com/apache/beam/pull/7017
Closing this PR. Please reopen if this is still needed.


Plug in Babble into Discourse notifications

It does not seem to work out of the box, anyways it should trigger notifications on its own. Make it configurable.

Hey @gtanczyk could you expand a little on what you're thinking here? That getting a new chat message should trigger a notification where? I assume we don't want notifications triggered in the navbar, right?

There is desktop notifications library in Discourse: https://github.com/discourse/discourse/blob/master/app/assets/javascripts/discourse/lib/desktop-notifications.js.es6
I did a quick spike and it is quite easy to use. I used it in Discourse.Babble.refresh.
So this issue is about displaying desktop notifications.

:+1:
On Wed, Aug 12, 2015 at 12:08 PM, Grzegorz Tańczyk<EMAIL_ADDRESS>
wrote:

There is desktop notifications library in Discourse:
https://github.com/discourse/discourse/blob/master/app/assets/javascripts/discourse/lib/desktop-notifications.js.es6
I did a quick spike and it is quite easy to use. I used it in
Discourse.Babble.refresh.
So this issue is about displaying desktop notifications.
—
Reply to this email directly or view it on GitHub
https://github.com/gdpelican/babble/issues/17#issuecomment-130414540.

I'm going to close this as a feature request; it's not on the roadmap at this time.


TimeSeparator has changed from : to . for da-DK in .NET 5+

Description
The time separator has changed from : to . for da-DK in .NET 5 and 6
System.Globalization.CultureInfo.GetCultureInfo("da-DK").DateTimeFormat.TimeSeparator
is : for .NET Framework and .NET Core 3.1, as expected
https://dotnetfiddle.net/wPaJI1
it is . for .NET 5 & 6
https://dotnetfiddle.net/3fLj9J

It looks like it is related to https://github.com/dotnet/runtime/issues/46033
ICU for da has timeSeparator{"."}
https://github.com/unicode-org/icu/blob/main/icu4c/source/data/locales/da.txt
Is it a bug in the ICU then?

I have created an ICU bug https://unicode-org.atlassian.net/browse/ICU-21828


Refactoring Done For Kind Documentation #39

Fixes Issue #39
Signed-off-by: Tanisha Banik<EMAIL_ADDRESS>

Thanks, @26tanishabanik, for refactoring.
But we have all the filenames in lowercase in the rest of the docs repo.
We have creating a slice as a single topic. Installing the KubeSlice Controller, Preparing the Kind clusters for registration, registering the clusters are all single topics.
I understand it's a good amount of rework. But it will be better to have all these folders as a single topic under getting started with Kind clusters.
I am open for discussion; pleased let me know your thoughts.
Apologies for getting back on this late as we were busy with a major release.

Thanks, @26tanishabanik, for refactoring.
But we have all the filenames in lowercase in the rest of the docs repo.
We have creating a slice as a single topic. Installing the KubeSlice Controller, Preparing the Kind clusters for registration, registering the clusters are all single topics.
I understand it's a good amount of rework. But it will be better to have all these folders as a single topic under getting started with Kind clusters.
I am open for discussion; pleased let me know your thoughts.
Apologies for getting back on this late as we were busy with a major release.

Hey @veenamj-avesha, Thanks for your valuable feedback.
The idea behind the refactoring was to make it more like the Getting started with Cloud Clusters setup, hence I had refactored it that way, as mentioned here #39

Hello @veenamj-avesha & @26tanishabanik , the idea behind this documentation was to have two separate sections in the sidebar & documentation

Getting Started with Kind Clusters
--> Subtopic 1
--> Subtopic 2
--> Subtopic 3 etc
Getting Started with Cloud Clusters
--> Subtopic 1
--> Subtopic 2
--> Subtopic 3 etc.

I don't think the suggested change actually helps with that.

Hello @veenamj-avesha & @26tanishabanik , the idea behind this documentation was to have two separate sections in the sidebar & documentation

Getting Started with Kind Clusters
--> Subtopic 1
--> Subtopic 2
--> Subtopic 3 etc
Getting Started with Cloud Clusters
--> Subtopic 1
--> Subtopic 2
--> Subtopic 3 etc.

I don't think the suggested change actually helps with that.

Hey @divya-mohan0209 , The cloud setup is already there, and I tried to replicate that for kind clusters as well.
Can you tell me, what I missed?


Landing page for signing up for the email list

User story

As a user
I want / need a landing to sign up
So that I can receive your-daily-board email

closes it because https://github.com/iheziqi/your-daily-board/commit/f1850c75bfed7fecce457be197618fa23bd05019 has finished this issue.


Force django-compressor version

This commit is inspired by work in #122. We don't specify an upper bound for
django-compressor in Oscar 1.0. compressor 2.0 was released, which dropped
support for Django 1.7, which means our tests fail.
As this is a bit of an artefact, I prefer to specify the compressor version in
the testing requirements specific to the affected combination of Django and
Oscar versions instead of globally as done in #122.
This commit forces the version of compressor. That's good enough, given that
we're about to drop Django 1.7 support as well with Oscar 1.2.
Thanks go to @fghaas for the excellent analysis.

I was trying to be too clever. #122 will be good enough :D


API Audit Logs

Describe the New Feature
The API should log details for each request received.  This will help to locate error logs when users report problems and  track system activity.
Acceptance Testing
The current tests for the API handler can be updated to make sure there is an entry in the audit log database table and that values are set appropriately for the test request.
Time Estimate
8h
Relevant Deadlines
NONE
Assignee

[X] @hahnd

Labels

[X] API
[X] High

Projects and Milestone

[X] wrfcloud
[X] Version 0.1

New Feature Checklist

[x] AuditEntry class to store log entry properties
[x] AuditDao class (Data access object) to handle DynamoDB transactions
[x] DynamoDB table definition
[x] Save method to save a log entry to the audit table
[x] Read method to read a log entry from the audit table based on reference ID
[x] Unit tests will sufficient code coverage

Branch name: feature_<Issue Number>/api-audit-log

[x] Complete the development and test your changes.
[x] Add/update log messages for easier debugging.
[x] Add/update tests.
[x] Add/update documentation.
[x] Push local changes to GitHub.
[x] Submit a pull request to merge into develop.

Pull request: feature <Issue Number> <Description>

[ ] Define the pull request metadata, as permissions allow.
Select: Reviewer(s), Project, and Development issue
Select: Milestone as the next official version
[ ] Iterate until the reviewer(s) accept and merge your changes.
[ ] Delete your fork or branch.
[ ] Close this issue.

@hahnd FYI, I created a new "component: API" label and added that along with the "priority: high" label. At least that's how I interpreted the content you added under the "Labels" section of the issue template.
I'd recommend you add new labels, as needed, as you go to help keep the issues organized.


PowerShell MSI uninstallation issues

[ ] Leaves old entry under Start menu
[ ] Leaves empty older version folder on disk

Steps to reproduce

Install an older version of PowerShell (say 6.0.0-alpha16) using MSI
Install latest version of PowerShell (6.0.0-alpha17) using MSI
Uninstall older version of PowerShell using Progams and Features in Control Panel
Search for PowerShell in Start menu
Look under C:\Program FIles\PowerShell path

Expected behavior

above should have only 1 entry
above should only show latest version of PowerShell

Actual behavior

shows multiple entries for PowerShell (see attached image)

shows multiple version folder under the path (see attached image)

Could be dup/related to #2881


Do not swallow non-expected exceptions in CHECK_THROW

The problem is that you have the same error message when:

No exception have been thrown, which is what we want to check
An other exception than expected has been thrown, which means there is an unexpected failure

When an other exception occurs it means an other problem has been detected, and it should not be dissimulated behind a wrong message. Remove the statement will restablish the correct message error: Failure in MyTest: Unhandled exception: test crashed
Thanks

I think I agree with this in premise; the existing behavior is not very informative. Two things:

These changes need tests.
Would it be better to keep the catch(...) but report a new, unique message? The expectation of a CHECK_THROW is that it will catch exceptions -- even the wrong ones -- and continue running the rest of the test case.

The expectation is that it will catch all exceptions and continue running the rest (...)

It is a point of view, why not. And anyway we can use the REQUIRE macro if required.
I let you chose, I will make the change

Closing soon due to lack of activity.


How to create android project with weex_sdk:0.26.0

Hi, I want to ask how to create android project with weex_sdk:0.26.0?
Now I use weex_sdk:0.16.0, and it can't build 64bit apk, so I have to upgrade to weex_sdk:0.26.0.
But show error:
error : can't find symbol
symbol:   class IWXDebugProxy
position:  com.taobao.weex.common
Any information could help me solve that problem?
Thanks!

I copy the https://github.com/apache/incubator-weex-playground and change the uri to local asset solve the problem.

解决了吗
我也遇到这个问题