Not able to view the emualtor on the web browser

Hi,
Please help and support.
I am getting below error while running the emulator in web container.
Jwks remote fetch is failed.
realm="http://localhost:8080/android.emulation.control.EmulatorController/getStatus", error="invalid_token"
Low level gRPC error: {"message":"Http response at 400 or 500 level, http status code: 401","stack":"Error: Http response at 400 or 500 level, http status code: 401\n at new k (http://localhost:8081/static/js/main.9d8095e4.js:2:742097)\n at Gt (http://localhost:8081/static/js/main.9d8095e4.js:2:765119)\n at Ct. (http://localhost:8081/static/js/main.9d8095e4.js:2:764803)\n at ze (http://localhost:8081/static/js/main.9d8095e4.js:2:751021)\n at Ve (http://localhost:8081/static/js/main.9d8095e4.js:2:750827)\n at xt (http://localhost:8081/static/js/main.9d8095e4.js:2:758352)\n at Pt (http://localhost:8081/static/js/main.9d8095e4.js:2:759133)\n at r.W (http://localhost:8081/static/js/main.9d8095e4.js:2:760075)\n at r.R (http://localhost:8081/static/js/main.9d8095e4.js:2:760054)","code":16,"metadata":{}}
Please find the below information.
We are able to list the services using below command.
grpcurl -plaintext localhost:8554 list
We are using the below scripts to run the emulator over container.
https://github.com/google/android-emulator-container-scripts
We are fallowing below steps.

git clone https://github.com/google/android-emulator-container-scripts.git
cd android-emulator-container-script
source ./configure.sh
emu-docker licenses
emu-docker create /path/to/emulator.zip /path/to/system-image.zip
/create_web_container.sh
docker-compose -f js/docker/docker-compose-build.yaml -f js/docker/development.yaml up

Expected Result:
8.Emulator should run without any issue over web browser.
Point your browser to localhost.
Actual Result:
8. Not able to view the emulator on the web browser.
Error Facing:
We are able to print the token also.
Below is the trace logs.

Getting below error:
Jwt is missing
Below is the response header:
Access-Control-Allow-Origin                    :           http://localhost
Access-Control-Expose-Headers            :            custom-header-1,grpc-status,grpc-message
Connection                                              :            close
Content-Length                                        :            0
Content-Type                                           :            application/grpc-web-text+proto
Date                                                         :            Wed, 24 Jul 2024 13:49:36 GMT
Grpc-Message                                         :            Jwks remote fetch is failed
Grpc-Status                                             :            16
Server                                                      :            envoy
Www-Authenticate                                   :            Bearer realm="http://localhost:8080/android.emulation.control.EmulatorController/getStatus", error="invalid_token"
Below is the request header:
Accept                                           :       application/grpc-web-text
Accept-Encoding                         :       gzip, deflate, br, zstd
Accept-Language                        :       en-US,en;q=0.9
Authorization                                :       Bearer "TOKEN KEY"
Connection                                   :       keep-alive
Content-Length                            :       8
Content-Type                               :       application/grpc-web-text
Dnt                                                 :      1
Host                                              :       localhost:8080
Origin                                           :        http://localhost
Referer                                        :        http://localhost/
Sec-Ch-Ua                                  :        "Not/A)Brand";v="8", "Chromium";v="126", "Microsoft Edge";v="126"
Sec-Ch-Ua-Mobile                     :       ?0
Sec-Ch-Ua-Platform                  :       "Linux"
Sec-Fetch-Dest                          :       empty
Sec-Fetch-Mode                        :       cors
Sec-Fetch-Site                           :       same-site
User-Agent                                 :      Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>
X-Grpc-Web                               :      1
X-User-Agent                             :       grpc-web-javascript/0.1
General Information:
Request URL                      :        http://localhost:8080/android.emulation.control.EmulatorController/getStatus
Request Method                 :       POST
Status Code                        :       401 Unauthorized
Remote Address                :      [::1]:8080
Referrer Policy                   :        strict-origin-when-cross-origin
We are able to print the token below:
if (isSignedIn) {
firebase.auth().currentUser.getIdToken().then(function (token) {
auth.setToken(Bearer ${token});
console.log("Token in authHeader:", token);
});
}
/**

Called by the EmulatorWebClient to obtain the authentication
headers

@memberof TokenAuthService
@returns The authentication header for the web call
@see EmulatorWebClient
*/
authHeader = () => {
console.log("Token in authHeader:", this.token );
return { Authorization: this.token };
};
}

Please let me know if you need some more information.
Thank for the support, much appreciated.

cc @RyanTheOptimist

Hi @RyanTheOptimist
We are trying the below steps.
Inside the Envoy Container:
Check DNS Resolution:
Command :        # nslookup googleapis.com
Output:              # Server:		<IP_ADDRESS>
Address:	<IP_ADDRESS>#53
** server can't find googleapis.com: NXDOMAIN

Hi @RyanTheOptimist,
We are trying the below steps.
**Inside the Envoy Container:

Check DNS Resolution:**
Command :     # nslookup googleapis.com
Output:            # Server:    <IP_ADDRESS>
                            Address:       <IP_ADDRESS>#53
                            ** server can't find googleapis.com: NXDOMAIN

2. Verify JWKS Fetch within the Envoy container:
Command :  # curl -H "Authorization: Bearer Token Key" http://localhost:8080/android.emulation.control/getStatus
Output: Jwks remote fetch is failed

Sorry, I'm not sure that I understand. What does this have to do with Envoy?

Hi @RyanTheOptimist,
Thanks for the reply. Could you please check.
We are seeing below error in envoy proxy.
Jwks remote fetch is failed.
Is this any configuration do we need to do in envoy.yaml file (please find the below link for the same)?.
https://github.com/google/android-emulator-container-scripts/blob/master/js/docker/envoy.yaml
I have given all the above information.
Please check and help.

Can you explain at a high level what you are trying to do, and where Envoy fits is? I have no idea what android-emulator-container-scripts is, but it sounds like that might be the source of your problem?

Hi @RyanTheOptimist,
Thank you for the reply. Please let me know if you need any more information.
We are trying to access emulator on the web browser.
android-emulator-container-scripts is repository also contains an example that demonstrates how you can use docker to make the emulator accessible through the web. This is done by composing the following set of docker containers:

Envoy, an edge and service proxy: The proxy is responsible for the following:

Offer TLS (https) using a self signed certificate
Redirect traffic on port 80 (http) to port 443 (https)
Act as a gRPC proxy for the emulator.
Verifying tokens to permit access to the emulator gRPC endpoint.
Redirect other requests to the Nginx component which hosts a React application.

Nginx, a webserver hosting a compiled React App

Firebase. We use firebase for authentication and authorization. Firebase will hand out JWT tokens that allow access to the emulator. If you use firebase you must configure your project properly!

The emulator with a gRPC endpoint and a WebRTC video bridge.

Thanks for the context. There are a lot of components in that setup. Which of the errors you are seeing makes you think Envoy is behaving incorrectly.

Thank you.
We are trying the below steps.
Inside the Envoy(proxy) Container:
1. Check DNS Resolution: We are not able to access googleapis.com.
Command :     # nslookup googleapis.com
Output:            # Server:    <IP_ADDRESS>
Address:       <IP_ADDRESS>#53
**** server can't find googleapis.com: NXDOMAIN** --------------> ERROR
2. Verify JWKS Fetch within the Envoy(proxy) container: We are not able to access http://localhost:8080/android.emulation.control/getStatus.
Command :  # curl -H "Authorization: Bearer Token Key" http://localhost:8080/android.emulation.control/getStatus
Output: Jwks remote fetch is failed ------------------->ERROR
We are using the below configuration.
https://github.com/google/android-emulator-container-scripts/blob/master/js/docker/envoy.yaml
Please check whether is this related to you or other teams. Please forward.

If you are unable to resolve googleapis.com that sounds like a problem in the setup and does not sound like an Envoy problem.

OK Thank you,
Will check this out.

We solved below issue.

Check DNS Resolution: We are not able to access googleapis.com.
Command : # nslookup googleapis.com
Output: # Server:    <IP_ADDRESS>
Address:   <IP_ADDRESS>#53
**** server can't find googleapis.com: NXDOMAIN** --------------> ERROR

But still we are facing below issue.Please help

Verify JWKS Fetch within the Envoy(proxy) container: We are not able to access http://localhost:8080/android.emulation.control/getStatus.
Command : # curl -H "Authorization: Bearer Token Key" http://localhost:8080/android.emulation.control/getStatus
Output: Jwks remote fetch is failed ------------------->ERROR

We are using the below configuration.
https://github.com/google/android-emulator-container-scripts/blob/master/js/docker/envoy.yaml

As an Envoy maintainer, I don't know anything about this android emultor setup you are working with and so I have no idea what your problem might be in your setup. Do you have logging output from Envoy that you can look at? In you earlier message you said that Firebase hands out JWT tokens. If the problem you're having is getting tokens, I wonder if the problem might be there.

I am seeing the issue similar to below.
https://github.com/envoyproxy/envoy/issues/15854.

@qiwzhang

That is a 3 year old closed issue, the solution to which was to add SSL certificates to the config. It sounds like this is not, in fact, and Envoy bug. If you have any logging or other evidence to the contrary, please provide it.  In any case, that is an access log not a debug log. https://www.envoyproxy.io/docs/envoy/latest/start/quick-start/run-envoy#envoy-logging

Hi @RyanTheOptimist,
Thank you for the help.
Please find below information. Please let me know for more information.
[2024-08-02 20:03:28.975][18][debug][connection] [./source/common/network/connection_impl.h:98] [C48] current connecting state: false
[2024-08-02 20:03:28.975][18][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:157] Called Filter : setDecoderFilterCallbacks
[2024-08-02 20:03:28.975][18][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:53] Called Filter : decodeHeaders
[2024-08-02 20:03:28.975][18][debug][jwt] [source/extensions/filters/http/jwt_authn/matcher.cc:71] Prefix requirement '/android.emulation.control' matched.
[2024-08-02 20:03:28.975][18][debug][jwt] [source/extensions/filters/http/jwt_authn/extractor.cc:254] extract authorizationBearer
[2024-08-02 20:03:28.975][18][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:151] firebase_jwt: JWT authentication starts (allow_failed=false), tokens size=1
[2024-08-02 20:03:28.975][18][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:162] firebase_jwt: startVerify: tokens size 1
[2024-08-02 20:03:28.975][18][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:180] firebase_jwt: Parse Jwt TOKENKEY
[2024-08-02 20:03:28.976][18][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:191] firebase_jwt: Verifying JWT token of issuer https://securetoken.google.com/android-emulator-webrtc-demo
[2024-08-02 20:03:28.976][18][debug][filter] [source/extensions/filters/http/common/jwks_fetcher.cc:60] fetch pubkey from [uri =<EMAIL_ADDRESS>start
[2024-08-02 20:03:28.976][18][debug][router] [source/common/router/router.cc:478] [C0][S5192912370530432761] cluster 'jwks_cluster' match for URL<EMAIL_ADDRESS>[2024-08-02 20:03:28.976][18][debug][router] [source/common/router/router.cc:686] [C0][S5192912370530432761] router decoding headers:
':path'<EMAIL_ADDRESS>':authority', 'www.googleapis.com'
':method', 'GET'
':scheme', 'http'
'x-envoy-internal', 'true'
'x-forwarded-for', '<IP_ADDRESS>'
'x-envoy-expected-rq-timeout-ms', '60000'
[2024-08-02 20:04:10.580][40][debug][pool] [source/common/http/conn_pool_base.cc:78] queueing stream due to no available connections (ready=0 busy=0 connecting=1)
[2024-08-02 20:04:10.580][40][debug][pool] [source/common/conn_pool/conn_pool_base.cc:291] trying to create new connection
[2024-08-02 20:04:10.580][40][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:97] Called Filter : decodeHeaders Stop
[2024-08-02 20:04:10.580][40][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:141] Called Filter : decodeData
[2024-08-02 20:04:10.580][40][debug][http] [source/common/http/conn_manager_impl.cc:1101] [C50][S539922902071072759] request end stream
[2024-08-02 20:04:10.580][40][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:141] Called Filter : decodeData
[2024-08-02 20:04:10.580][40][debug][http] [source/common/http/conn_manager_impl.cc:375] [C52] new stream
[2024-08-02 20:04:10.580][40][debug][http] [source/common/http/conn_manager_impl.cc:1118] [C52][S7308188479879091829] request headers complete (end_stream=false):
':authority', 'localhost:8080'
':path', '/android.emulation.control.EmulatorController/getLogcat'
':method', 'POST'
'connection', 'keep-alive'
'content-length', '8'
'sec-ch-ua', '"Not/A)Brand";v="8", "Chromium";v="126", "Microsoft Edge";v="126"'
'x-user-agent', 'grpc-web-javascript/0.1'
'dnt', '1'
'sec-ch-ua-mobile', '?0'
'authorization', 'Bearer TOKENKEY'
'user-agent', 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>'
'content-type', 'application/grpc-web-text'
'accept', 'application/grpc-web-text'
'x-grpc-web', '1'
'sec-ch-ua-platform', '"Linux"'
'origin', 'http://localhost:8081'
'sec-fetch-site', 'same-site'
'sec-fetch-mode', 'cors'
'sec-fetch-dest', 'empty'
'referer', 'http://localhost:8081/'
'accept-encoding', 'gzip, deflate, br, zstd'
'accept-language', 'en-US,en;q=0.9'
[2024-08-02 20:04:10.580][40][debug][connection] [./source/common/network/connection_impl.h:98] [C52] current connecting state: false
[2024-08-02 20:04:10.580][40][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:157] Called Filter : setDecoderFilterCallbacks
[2024-08-02 20:04:10.580][40][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:53] Called Filter : decodeHeaders
[2024-08-02 20:04:10.580][40][debug][jwt] [source/extensions/filters/http/jwt_authn/matcher.cc:71] Prefix requirement '/android.emulation.control' matched.
[2024-08-02 20:04:10.580][40][debug][jwt] [source/extensions/filters/http/jwt_authn/extractor.cc:254] extract authorizationBearer
[2024-08-02 20:04:10.580][40][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:151] firebase_jwt: JWT authentication starts (allow_failed=false), tokens size=1
[2024-08-02 20:04:10.580][40][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:162] firebase_jwt: startVerify: tokens size 1
[2024-08-02 20:04:10.580][40][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:180] firebase_jwt: Parse Jwt TOKENKEY
[2024-08-02 20:04:10.580][40][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:191] firebase_jwt: Verifying JWT token of issuer https://securetoken.google.com/android-emulator-webrtc-demo
[2024-08-02 20:04:10.580][40][debug][filter] [source/extensions/filters/http/common/jwks_fetcher.cc:60] fetch pubkey from [uri =<EMAIL_ADDRESS>start
[2024-08-02 20:04:10.580][40][debug][router] [source/common/router/router.cc:478] [C0][S6523411824307427240] cluster 'jwks_cluster' match for URL<EMAIL_ADDRESS>[2024-08-02 20:04:10.580][40][debug][router] [source/common/router/router.cc:686] [C0][S6523411824307427240] router decoding headers:
':path'<EMAIL_ADDRESS>':authority', 'www.googleapis.com'
':method', 'GET'
':scheme', 'http'
'x-envoy-internal', 'true'
'x-forwarded-for', '<IP_ADDRESS>'
'x-envoy-expected-rq-timeout-ms', '60000'
[2024-08-02 20:04:10.580][40][debug][pool] [source/common/http/conn_pool_base.cc:78] queueing stream due to no available connections (ready=0 busy=0 connecting=1)
[2024-08-02 20:04:10.580][40][debug][pool] [source/common/conn_pool/conn_pool_base.cc:291] trying to create new connection
[2024-08-02 20:04:10.580][40][debug][pool] [source/common/conn_pool/conn_pool_base.cc:145] creating a new connection (connecting=1)
[2024-08-02 20:04:10.581][40][debug][connection] [./source/common/network/connection_impl.h:98] [C66] current connecting state: true
[2024-08-02 20:04:10.581][40][debug][client] [source/common/http/codec_client.cc:57] [C66] connecting
[2024-08-02 20:04:10.581][40][debug][connection] [source/common/network/connection_impl.cc:941] [C66] connecting to <IP_ADDRESS>:443
[2024-08-02 20:04:10.581][40][debug][connection] [source/common/network/connection_impl.cc:960] [C66] connection in progress
[2024-08-02 20:04:10.581][40][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:97] Called Filter : decodeHeaders Stop
[2024-08-02 20:04:10.581][40][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:141] Called Filter : decodeData
[2024-08-02 20:04:10.581][40][debug][http] [source/common/http/conn_manager_impl.cc:1101] [C52][S7308188479879091829] request end stream
[2024-08-02 20:04:10.581][40][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:141] Called Filter : decodeData
[2024-08-02 20:04:10.956][23][debug][pool] [source/common/conn_pool/conn_pool_base.cc:793] [C55] connect timeout
[2024-08-02 20:04:10.956][23][debug][connection] [source/common/network/connection_impl.cc:139] [C55] closing data_to_write=0 type=1
[2024-08-02 20:04:10.956][23][debug][connection] [source/common/network/connection_impl.cc:250] [C55] closing socket: 1
[2024-08-02 20:04:10.956][23][debug][client] [source/common/http/codec_client.cc:107] [C55] disconnect. resetting 0 pending requests
[2024-08-02 20:04:10.956][23][debug][pool] [source/common/conn_pool/conn_pool_base.cc:484] [C55] client disconnected, failure reason:
[2024-08-02 20:04:10.957][23][debug][router] [source/common/router/router.cc:1279] [C0][S5586241757682015922] upstream reset: reset reason: connection failure, transport failure reason:
[2024-08-02 20:04:10.957][23][debug][http] [source/common/http/async_client_impl.cc:123] async http request response headers (end_stream=false):
':status', '503'
'content-length', '91'
'content-type', 'text/plain'
[2024-08-02 20:04:10.957][23][debug][filter] [source/extensions/filters/http/common/jwks_fetcher.cc:103] onSuccess: fetch pubkey [uri =<EMAIL_ADDRESS>response status code 503
[2024-08-02 20:04:10.957][23][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:374] firebase_jwt: JWT token verification completed with: Jwks remote fetch is failed
[2024-08-02 20:04:10.957][23][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:378] status is: Jwks remote fetch is failed
[2024-08-02 20:04:10.957][23][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:109] Jwt authentication completed with: Jwks remote fetch is failed
[2024-08-02 20:04:10.957][23][debug][http] [source/common/http/filter_manager.cc:996] [C54][S1057157605582823657] Sending local reply with details jwt_authn_access_denied{Jwks_remote_fetch_is_failed}
[2024-08-02 20:04:10.957][23][debug][http] [source/common/http/conn_manager_impl.cc:1773] [C54][S1057157605582823657] encoding headers via codec (end_stream=false):
':status', '401'
'www-authenticate', 'Bearer realm="http://localhost:8080/android.emulation.control.EmulatorController/getLogcat", error="invalid_token"'
'content-length', '0'
'content-type', 'application/grpc-web-text+proto'
'grpc-message', 'Jwks remote fetch is failed'
'grpc-status', '16'
'access-control-allow-origin', 'http://localhost:8081'
'access-control-expose-headers', 'custom-header-1,grpc-status,grpc-message'
'date', 'Fri, 02 Aug 2024 20:04:10 GMT'
'server', 'envoy'

As far as I can tell, everything looks fine from Envoy's perspective. It looks like the firebase request received a 503 response which sounds like something is not working well there. Again as far as I can tell there is no evidence of Envoy misbehaving.

Thank you @RyanTheOptimist for your valuable time and input.
Will check this out.

Hi @RyanTheOptimist,
We could see below debug logs which are causing the issue.
Line 32690: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][connection] [./source/common/network/connection_impl.h:98] [C2] current connecting state: false
Line 32691: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:157] Called Filter : setDecoderFilterCallbacks
Line 32692: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:53] Called Filter : decodeHeaders
Line 32693: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][jwt] [source/extensions/filters/http/jwt_authn/matcher.cc:71] Prefix requirement '/android.emulation.control' matched.

Line 32728: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][jwt] [source/extensions/filters/http/jwt_authn/extractor.cc:254] extract authorizationBearer
Line 32729: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][filter] [source/extensions/filters/http/common/jwks_fetcher.cc:60] fetch pubkey from [uri =<EMAIL_ADDRESS>start
Line 32730: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:151] firebase_jwt: JWT authentication starts (allow_failed=false), tokens size=1
Line 32731: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:162] firebase_jwt: startVerify: tokens size 1
Line 32732: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:180] firebase_jwt: Parse Jwt eyJhbGciOiJSUzI1NiIsImtpZCI6IjFkYmUwNmI1ZDdjMmE3YzA0NDU2MzA2MWZmMGZlYTM3NzQwYjg2YmMiLCJ0eXAiOiJKV1QifQ.eyJuYW1lIjoiU2hyaWRoYXIgc2FraGFyZSIsInBpY3R1cmUiOiJodHRwczovL2xoMy5nb29nbGV1c2VyY29udGVudC5jb20vYS9BQ2c4b2NKWHBwVVBDZGtoVUFJUVBkaWczV28tT01QVEN1QUU1a2ZnamEyM2c3ZGIxS289czk2LWMiLCJpc3MiOiJodHRwczovL3NlY3VyZXRva2VuLmdvb2dsZS5jb20vYW5kcm9pZC1lbXVsYXRvci13ZWJydGMtZGVtbyIsImF1ZCI6ImFuZHJvaWQtZW11bGF0b3Itd2VicnRjLWRlbW8iLCJhdXRoX3RpbWUiOjE3MTk4Mjc2NDQsInVzZXJfaWQiOiJRVkswZFVtbllTUjdqbFhUcHhNaGNXeFhNZUQyIiwic3ViIjoiUVZLMGRVbW5ZU1I3amxYVHB4TWhjV3hYTWVEMiIsImlhdCI6MTcyMjg0NzAzNSwiZXhwIjoxNzIyODUwNjM1LCJlbWFpbCI6InNha2hhcmVzcmkzMzNAZ21haWwuY29tIiwiZW1haWxfdmVyaWZpZWQiOnRydWUsImZpcmViYXNlIjp7ImlkZW50aXRpZXMiOnsiZ29vZ2xlLmNvbSI6WyIxMTc2MjAyODE5NTUzMTk0NDI4NDEiXSwiZW1haWwiOlsic2FraGFyZXNyaTMzM0BnbWFpbC5jb20iXX0sInNpZ25faW5fcHJvdmlkZXIiOiJnb29nbGUuY29tIn19.FX-LFiKS_TphlsDdTXUEv21kgeIWPRFMSvxbAKUZ00W6m_qPSb5igKxH8wBpmtjKQ1P3F23bRkjGJlCkPl54J6Br5mQNMhAeBG0rNxcXkILzGE4AVQ1WEs4KY58B3FUjgrjc-2cB5UNFRXtg_g2EQcVj7MLbCZ7D-Za4kfjQKzE5PiFzTn3f7-wGocaJt6MvAXLesdSIkMMA3kenJIu-FX7GbGKeUA7JGlJH0v8HV5JVyEEz3nAoKTRNv_NaQ3UZd50hXIcjiv2a292vLBlEYdz7qxx8hVFHt2NlUJ_xofWFWpDqe6nF52mm-u8Oa7E0VDoWvfZf_GMJak4OJ8nJ8A
Line 32733: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:191] firebase_jwt: Verifying JWT token of issuer https://securetoken.google.com/android-emulator-webrtc-demo
Line 32734: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][filter] [source/extensions/filters/http/common/jwks_fetcher.cc:60] fetch pubkey from [uri =<EMAIL_ADDRESS>start
Line 32735: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][router] [source/common/router/router.cc:478] [C0][S896017666614266671] cluster 'jwks_cluster' match for URL<EMAIL_ADDRESS>Line 32736: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][router] [source/common/router/router.cc:478] [C0][S9714648410712570137] cluster 'jwks_cluster' match for URL<EMAIL_ADDRESS>Line 32737: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][upstream] [source/common/upstream/cluster_manager_impl.cc:1659] no healthy host for HTTP connection pool
Line 32738: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][upstream] [source/common/upstream/cluster_manager_impl.cc:1659] no healthy host for HTTP connection pool
Line 32739: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][http] [source/common/http/async_client_impl.cc:123] async http request response headers (end_stream=false):
Line 32740: front-envoy_1  |':status', '503'
Line 32741: front-envoy_1  |'content-length', '19'
Line 32742: front-envoy_1  |'content-type', 'text/plain'
Line 32743: front-envoy_1  |
Line 32744: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][http] [source/common/http/async_client_impl.cc:123] async http request response headers (end_stream=false):
Line 32745: front-envoy_1  |':status', '503'
Line 32746: front-envoy_1  |'content-length', '19'
Line 32747: front-envoy_1  |'content-type', 'text/plain'
Line 32748: front-envoy_1  |
Line 32749: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][filter] [source/extensions/filters/http/common/jwks_fetcher.cc:103] onSuccess: fetch pubkey [uri =<EMAIL_ADDRESS>response status code 503
Line 32750: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][filter] [source/extensions/filters/http/common/jwks_fetcher.cc:103] onSuccess: fetch pubkey [uri =<EMAIL_ADDRESS>response status code 503
Line 32751: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:374] firebase_jwt: JWT token verification completed with: Jwks remote fetch is failed
Line 32752: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:378] status is: Jwks remote fetch is failed
Line 32753: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:374] firebase_jwt: JWT token verification completed with: Jwks remote fetch is failed
Line 32754: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:109] Jwt authentication completed with: Jwks remote fetch is failed
Line 32755: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][jwt] [source/extensions/filters/http/jwt_authn/authenticator.cc:378] status is: Jwks remote fetch is failed
Line 32756: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][http] [source/common/http/filter_manager.cc:946] [C3][S14334833592518600504] Preparing local reply with details jwt_authn_access_denied{Jwks_remote_fetch_is_failed}
Line 32757: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:109] Jwt authentication completed with: Jwks remote fetch is failed
Line 32758: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][http] [source/common/http/filter_manager.cc:946] [C2][S10075817475605624797] Preparing local reply with details jwt_authn_access_denied{Jwks_remote_fetch_is_failed}
Line 32759: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:97] Called Filter : decodeHeaders Stop
Line 32760: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][http] [source/common/http/filter_manager.cc:988] [C3][S14334833592518600504] Executing sending local reply.
Line 32761: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:97] Called Filter : decodeHeaders Stop
Line 32762: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][http] [source/common/http/filter_manager.cc:988] [C2][S10075817475605624797] Executing sending local reply.

Line 32790: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][http] [source/common/http/conn_manager_impl.cc:1865] [C2][S10075817475605624797] Codec completed encoding stream.
Line 32791: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][http] [source/common/http/conn_manager_impl.cc:234] [C2][S10075817475605624797] doEndStream() resetting stream
Line 32792: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][http] [source/common/http/conn_manager_impl.cc:234] [C3][S14334833592518600504] doEndStream() resetting stream
Line 32793: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][http] [source/common/http/conn_manager_impl.cc:1829] [C2][S10075817475605624797] stream reset: reset reason: local reset, response details: -
Line 32794: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][http] [source/common/http/conn_manager_impl.cc:1829] [C3][S14334833592518600504] stream reset: reset reason: local reset, response details: -
Line 32795: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:46] Called Filter : onDestroy
Line 32796: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][jwt] [source/extensions/filters/http/jwt_authn/filter.cc:46] Called Filter : onDestroy
Line 32797: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][connection] [source/common/network/connection_impl.cc:139] [C2] closing data_to_write=485 type=2
Line 32798: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][connection] [source/common/network/connection_impl.cc:139] [C3] closing data_to_write=482 type=2
Line 32799: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][connection] [source/common/network/connection_impl_base.cc:47] [C2] setting delayed close timer with timeout 1000 ms
Line 32800: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][connection] [source/common/network/connection_impl_base.cc:47] [C3] setting delayed close timer with timeout 1000 ms
Line 32801: front-envoy_1  |[2024-08-05 08:54:42.206][28][debug][connection] [source/common/network/connection_impl.cc:139] [C3] closing data_to_write=482 type=2
Line 32802: front-envoy_1  |[2024-08-05 08:54:42.206][24][debug][connection] [source/common/network/connection_impl.cc:139] [C2] closing data_to_write=485 type=2
Line 32803: front-envoy_1  |[2024-08-05 08:54:42.207][24][debug][connection] [source/common/network/connection_impl.cc:720] [C2] write flush complete
Line 32804: front-envoy_1  |[2024-08-05 08:54:42.207][28][debug][connection] [source/common/network/connection_impl.cc:720] [C3] write flush complete
Line 32805: front-envoy_1  |[2024-08-05 08:54:42.207][40][debug][conn_handler] [source/extensions/listener_managers/listener_manager/active_tcp_listener.cc:155] [C5] new connection from <IP_ADDRESS>:45040
Line 32806: front-envoy_1  |[2024-08-05 08:54:42.207][24][debug][connection] [source/common/network/connection_impl.cc:590] [C2] remote early close
Line 32807: front-envoy_1  |[2024-08-05 08:54:42.207][24][debug][connection] [source/common/network/connection_impl.cc:250] [C2] closing socket: 0
Line 32808: front-envoy_1  |[2024-08-05 08:54:42.208][24][debug][conn_handler] [source/extensions/listener_managers/listener_manager/active_stream_listener_base.cc:121] [C2] adding to cleanup list
Line 32809: front-envoy_1  |[2024-08-05 08:54:42.208][28][debug][connection] [source/common/network/connection_impl.cc:590] [C3] remote early close
Line 32810: front-envoy_1  |[2024-08-05 08:54:42.208][28][debug][connection] [source/common/network/connection_impl.cc:250] [C3] closing socket: 0
Line 32811: front-envoy_1  |[2024-08-05 08:54:42.208][28][debug][conn_handler] [source/extensions/listener_managers/listener_manager/active_stream_listener_base.cc:121] [C3] adding to cleanup list
Line 32812: front-envoy_1  |[2024-08-05 08:54:42.208][40][debug][http] [source/common/http/conn_manager_impl.cc:375] [C5] new stream
Line 32813: front-envoy_1  |[2024-08-05 08:54:42.208][40][debug][http] [source/common/http/conn_manager_impl.cc:1118] [C5][S17646489445735697307] request headers complete (end_stream=false):

Yes, it looks like the jwks_cluster is inaccessible. is that server up and running? Is there a connectivity problem reaching it?
[source/common/upstream/cluster_manager_impl.cc:1659] no healthy host for HTTP connection pool

Yes @RyanTheOptimist. Thank you very much for your reply and much appreciated.
Mostly Jwt issuer is not configured properly, or it might be that firebase json application file is not providing key to validate the signature.
I am also checking the below points.
is that server up and running? Is there a connectivity problem reaching it?

Please find the below issue.
https://github.com/envoyproxy/envoy/issues/9417

Hi @RyanTheOptimist ,
We could see below error. The log entries provided show that there are issues with the connections between Envoy and an upstream service. Here's a breakdown of the key parts:
front-envoy_1  | [2024-08-11 07:40:51.848][9][debug][main] [source/server/server.cc:265] flushing stats
front-envoy_1  | [2024-08-11 07:40:51.941][9][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:354] dns resolution for googleapis.com started
front-envoy_1  | [2024-08-11 07:40:51.941][9][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:354] dns resolution for emulator started
front-envoy_1  | [2024-08-11 07:40:51.941][9][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:354] dns resolution for nginx started
front-envoy_1  | [2024-08-11 07:40:51.948][9][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:275] dns resolution for googleapis.com completed with status 0
front-envoy_1  | [2024-08-11 07:40:51.948][9][debug][upstream] [source/common/upstream/upstream_impl.cc:457] transport socket match, socket default selected for host with address <IP_ADDRESS>:443
front-envoy_1  | [2024-08-11 07:40:51.948][9][debug][upstream] [source/extensions/clusters/strict_dns/strict_dns_cluster.cc:177] DNS refresh rate reset for googleapis.com, refresh rate 5000 ms
front-envoy_1  | [2024-08-11 07:40:51.948][9][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:275] dns resolution for emulator completed with status 0
front-envoy_1  | [2024-08-11 07:40:51.948][9][debug][upstream] [source/common/upstream/upstream_impl.cc:457] transport socket match, socket default selected for host with address <IP_ADDRESS>:8554
front-envoy_1  | [2024-08-11 07:40:51.948][9][debug][upstream] [source/extensions/clusters/strict_dns/strict_dns_cluster.cc:177] DNS refresh rate reset for emulator, refresh rate 5000 ms
front-envoy_1  | [2024-08-11 07:40:51.948][9][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:275] dns resolution for nginx completed with status 0
front-envoy_1  | [2024-08-11 07:40:51.948][9][debug][upstream] [source/common/upstream/upstream_impl.cc:457] transport socket match, socket default selected for host with address <IP_ADDRESS>:80
front-envoy_1  | [2024-08-11 07:40:51.948][9][debug][upstream] [source/extensions/clusters/strict_dns/strict_dns_cluster.cc:177] DNS refresh rate reset for nginx, refresh rate 5000 ms
front-envoy_1  | [2024-08-11 07:40:52.602][17][debug][router] [source/common/router/router.cc:1017] [C0][S2875841160146224442] upstream timeout
front-envoy_1  | [2024-08-11 07:40:52.606][29][debug][router] [source/common/router/router.cc:1017] [C0][S1108520338596185421] upstream timeout
front-envoy_1  | [2024-08-11 07:40:52.606][35][debug][router] [source/common/router/router.cc:1017] [C0][S6429685303994950634] upstream timeout
front-envoy_1  | [2024-08-11 07:40:52.616][17][debug][pool] [source/common/conn_pool/conn_pool_base.cc:659] cancelling pending stream
front-envoy_1  | [2024-08-11 07:40:52.616][29][debug][pool] [source/common/conn_pool/conn_pool_base.cc:659] cancelling pending stream
front-envoy_1  | [2024-08-11 07:40:52.616][17][debug][router] [source/common/router/upstream_request.cc:541] [C0][S2875841160146224442] canceled pool request
front-envoy_1  | [2024-08-11 07:40:52.616][35][debug][pool] [source/common/conn_pool/conn_pool_base.cc:659] cancelling pending stream
front-envoy_1  | [2024-08-11 07:40:52.616][29][debug][router] [source/common/router/upstream_request.cc:541] [C0][S1108520338596185421] canceled pool request
front-envoy_1  | [2024-08-11 07:40:52.616][35][debug][router] [source/common/router/upstream_request.cc:541] [C0][S6429685303994950634] canceled pool request
front-envoy_1  | [2024-08-11 07:40:52.616][17][debug][http] [source/common/http/async_client_impl.cc:123] async http request response headers (end_stream=false):
front-envoy_1  | ':status', '504'
front-envoy_1  | 'content-length', '24'
front-envoy_1  | 'content-type', 'text/plain'
front-envoy_1  |
front-envoy_1  | [2024-08-11 07:40:52.616][35][debug][http] [source/common/http/async_client_impl.cc:123] async http request response headers (end_stream=false):
front-envoy_1  | ':status', '504'
front-envoy_1  | 'content-length', '24'
front-envoy_1  | 'content-type', 'text/plain'
front-envoy_1  |
front-envoy_1  | [2024-08-11 07:40:52.616][29][debug][http] [source/common/http/async_client_impl.cc:123] async http request response headers (end_stream=false):
front-envoy_1  | ':status', '504'
front-envoy_1  | 'content-length', '24'
front-envoy_1  | 'content-type', 'text/plain'
front-envoy_1  |
front-envoy_1  | [2024-08-11 07:40:52.622][35][debug][filter] [source/extensions/filters/http/common/jwks_fetcher.cc:103] onSuccess: fetch pubkey [uri =<EMAIL_ADDRESS>response status code 504

Please check and help.It could be related to envoy.

HI @RyanTheOptimist,
Please check the below logs and any help will be great.
front-envoy_1  | [2024-08-12 13:21:14.116][9][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:354] dns resolution for googleapis.com started
front-envoy_1  | [2024-08-12 13:21:14.116][9][trace][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:317] Setting DNS resolution timer for 4061 milliseconds
front-envoy_1  | [2024-08-12 13:21:14.492][20][trace][misc] [source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x3562fed47780 for 300000ms, min is 300000ms
front-envoy_1  | [2024-08-12 13:21:14.492][20][trace][connection] [source/common/network/connection_impl.cc:423] [C2] raising connection event 2
front-envoy_1  | [2024-08-12 13:21:14.493][20][debug][conn_handler] [source/extensions/listener_managers/listener_manager/active_tcp_listener.cc:155] [C2] new connection from <IP_ADDRESS>:56652
front-envoy_1  | [2024-08-12 13:21:14.493][20][trace][connection] [source/common/network/connection_impl.cc:568] [C2] socket event: 3
front-envoy_1  | [2024-08-12 13:21:14.493][20][trace][connection] [source/common/network/connection_impl.cc:679] [C2] write ready
front-envoy_1  | [2024-08-12 13:21:14.493][20][trace][connection] [source/common/network/connection_impl.cc:608] [C2] read ready. dispatch_buffered_data=0
front-envoy_1  | [2024-08-12 13:21:14.493][20][trace][connection] [source/common/network/raw_buffer_socket.cc:24] [C2] read returns: 1985
front-envoy_1  | [2024-08-12 13:21:14.493][20][trace][connection] [source/common/network/raw_buffer_socket.cc:38] [C2] read error: Resource temporarily unavailable


[FEATURE REQ] com.azure.json.JsonWriter.writeMapField write null value to the Map field

Here is an example of auto-generated toJson method in one of our data models by using the autorest tool:
    /**
     * {@inheritDoc}
     */
    @Override
    public JsonWriter toJson(JsonWriter jsonWriter) throws IOException {
        jsonWriter.writeStartObject();
        jsonWriter.writeStringField("name", this.name);
        jsonWriter.writeStringField("time",
            this.time == null ? null : DateTimeFormatter.ISO_OFFSET_DATE_TIME.format(this.time));
        jsonWriter.writeNumberField("ver", this.version);
        jsonWriter.writeNumberField("sampleRate", this.sampleRate);
        jsonWriter.writeStringField("seq", this.sequence);
        jsonWriter.writeStringField("iKey", this.instrumentationKey);
        jsonWriter.writeMapField("tags", this.tags, (writer, element) -> writer.writeString(element)); // this line will write attribute with null value
        jsonWriter.writeJsonField("data", this.data);
        return jsonWriter.writeEndObject();
    }

jsonWriter.writeMapField("tags", this.tags, (writer, element) -> writer.writeString(element));  will write attributes with null values.
For azure-monitor-opentelemetry-exporter, we don't want to produce attributes with null values in the json payload. The main reason is because of cost, our customers are paying for the payload.
This would require a workaround for now. Instead of calling jsonWriter.writeMapField, this is what i used and recommended by @alzimmermsft
public static <T> void writeMap(Map<String, T> map, String fieldName, JsonWriter jsonWriter, Consumer<T> writeValueCallback) throws IOException {
        if (map == null) {
            return;
        }
        jsonWriter.writeFieldName(fieldName);
        jsonWriter.writeStartObject();
        for (Map.Entry<String, T> entry : map.entrySet()) {
            T value = entry.getValue();
            if (value == null) {
                continue;
            }
            jsonWriter.writeFieldName(entry.getKey());
            writeValueCallback.accept(entry.getValue());
        }
        jsonWriter.writeEndObject();
    }

I've tested it and it worked. This requires modification each time we use autorest tool to update data models. Ideally, if azure-json can handle this by default, it will be super helpful.
cc @trask @alzimmermsft

@alzimmermsft

This has been fixed with the new release of azure-json which provides new APIs for better managing writeArray and writeMap helpers in JsonWriter.
JsonWriter.writeMapField(String fieldName, Map<String, T> map, WriteValueCallback<JsonWriter, T> callback) will now always write a JSON null when the value of the map entry is null. There is a new overload with an additional parameter boolean skipNullValues which will skip serializing the map key-value pair into a JSON fieldname-value when the value is null.


Patches/Infos referenced from Github Security Advisories are not processed as additional info

Is your feature request related to a problem? Please describe.
Informations referenced from Github Security Advisories are not processed.
An example with CVE-2020-27663. A GitHub security advisory is referenced in Links section but not additional information has been processed.
Describe the solution you'd like
Adding the ability to fetch additional informations about vulnerabilities from Github Security Advisories / recognize commit links from GitHub
Additional context
Willing to contribute, issue mostly for tracking purposes.

Thanks Ewen!
That's a good point thanks for filing this and sure, please go ahead to help out and let us know if you need any help with this.


bump to latest node-abi (Node 12/Electron 5)

https://github.com/lgeiger/node-abi/pull/62 adds support for detecting Electron 5 and Node 12

Is this change (and https://github.com/prebuild/prebuild/pull/248) intended to prevent npm dedupe?

If this is only needed in one of the projects, feel free to close the other. I wasn't aware that it wasn't unnecessary to update both here...

Both use ^2 so the node-abi update should float in automatically, unless you have some other module that depends on node-abi with a more restrictive semver range?

@vweevers let me test out a PR on a downstream project and see if I encounter an issue 🤘

Looks like these PRs are unnecessary: https://github.com/atom/node-keytar/pull/181
Thanks for the extra insight @vweevers and apologies for the noise!

No worries! Glad it works out.


[SPARK-32594][SQL] Fix serialization of dates inserted to Hive tables

What changes were proposed in this pull request?
Fix DaysWritable by overriding parent's method def get(doesTimeMatter: Boolean): Date from DateWritable instead of Date get() because the former one uses the first one. The bug occurs because HiveOutputWriter.write() call def get(doesTimeMatter: Boolean): Date transitively with default implementation from the parent class  DateWritable which doesn't respect date rebases and uses not initialized daysSinceEpoch (0 which 1970-01-01).
Why are the changes needed?
The changes fix the bug:
spark-sql> CREATE TABLE table1 (d date);
spark-sql> INSERT INTO table1 VALUES (date '2020-08-11');
spark-sql> SELECT * FROM table1;
1970-01-01

The expected result of the last SQL statement must be 2020-08-11 but got 1970-01-01.
Does this PR introduce any user-facing change?
Yes. After the fix, INSERT work correctly:
spark-sql> SELECT * FROM table1;
2020-08-11

How was this patch tested?
Add new test to HiveSerDeReadWriteSuite

Test build #127347 has started for PR 29409 at commit 713f6ee.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31966/
Test PASSed.

Test build #127347 has finished for PR 29409 at commit 713f6ee.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127347/
Test PASSed.

Merged to master and branch-3.0.


Agent.tools should clone the tools array

Here is my code snippet:
tools.append(GoogleSearchTool)
tools.append(ShellTool)
tools.append(GitHubTool)

agent_po = Agent(name="agent-po",
            tools=tools)

agent_arch = Agent(name="agent-architect",
            tools=tools)

agent_dev = Agent(name="agent-developer",
            tools=tools)

But when I tried to get them to communicate I got:
👤 User: say hello to the developer

SendMessage(
{"chain_of_thought":"User has requested to send a greeting to the developer. The task at hand simply involves conveying a friendly message from the user to the developer. The appropriate response would be to acknowledge the user's greeting and deliver it to the developer.","recipient":"agent-developer","message":"Hello from the user!"})
)
Error: 1 validation error for SendMessage recipient Input should be 'agent-architect' [type=enum, input_value='agent-developer', input_type=str]

After much debugging I identified this was because they shared the same tools array. The Agent was updating it to add the  SendMessage function and this resulted in the above error.
I will submit a pull request for Agent.init()
self.tools = tools[:] if tools is not None else []
Hopefully this will save others some time...

Thank you


Don't bundle htmlhint with this extension, use local version installed in project

All the other linter extensions like eslint, tslint etc. do not bundle the linter with the extension, because projects can depend on specific versions of a linter (config file schemas can change, etc). If you bundle the linter, it is also impossible to update the linter if you have not released an update for the extension yet.
Please look for htmlhint in the node_modules folder in the currently opened project (relative to where .htmlhintrc is located) and if it can't be found, use a globally installed version, and if it still can't be found, print an error message.

@egamma, @dbaeumer - Any precedent around this?  I know that tslint/eslint is picking up the linter from local project's node_modules directory.  I explicitly didn't do that as I didn't want the user to have install a module to get the benefit of the linter.  Also wasn't always sure that, for html, there would be a project structure and/or a node-Modules folder.
Anyway, if there's precedent in other linters let me know.

The current problem is the best example: There has just recently been a fix in HTMLHint that enables it to work with Angular 2 templates. This extension is now stuck at the old version :/

@mike-kaufman the rule should alwys be to prefer local installed libraries over bundled libraries. So in your case if you bundle htmlhint the loading sequence should be:

use htmlhint from the workspace folder
use global installed htmlhint
use bundled htmlhint

(Would be nice if this project came back to life at some point...)

Just to get things moving again, I've made a quick pull request https://github.com/Microsoft/vscode-htmlhint/pull/15 to use latest htmlhint - not ideal but angular2 files are now looking good @felixfbecker

The right fix here is illustrated in the tslint extension for vs code:  https://github.com/Microsoft/vscode-tslint/blob/master/tslint-server/src/server.ts#L268-L297.

@mike-kaufman yeah, that looks good. Would you like me to put together another PR with that?

I would appreciate it, but I would replace the existsSync with its async counterpart 😉

@stevedenman  - if you want to code up a fix, that'd be great.  It should be fairly straightforward.  The only thing I'm not sure about is if we can rely on the embedded version of htmlhint if there isn't one in the user's project.  If we can't do this, then we'll impact existing users when they're upgraded, as they'll have to npm install htmlhint.

I would replace the existsSync with its async counterpart

You could do this, but I'm not clear on the benefit.  I think this code only runs when the extension is initialized, and I think this part of the extension runs in an isolated process, so the impact of doing the file read synchronously should be minimal.   I'm not 100% certain though, so LMK if I'm missing something.
Thanks!

What is the disadavantage? The method is async and returns a promise anyway

What is the disadavantage? The method is async and returns a promise anyway

In the cited tslint example above, only disadvantage is you'd have to restructure the (working) example, but that's minor.  Other sync io in the htmlhint extension (where it's looking for config files), you'd have to account for the validation call chain running asynchronously - I'm not sure if that will "just work".
As I said in #9, I'll happily take a PR if you feel strongly about the removing sync io.  If it isn't obvious already, I haven't had lots of time to put into this extension. ;)  I'm happy to answer questions & publish updates to the PR, but I'd love to encourage the community to take an active role here. :)

@stevedenman - FYI I've got a change on my machine that fixes the issue so we'll use either the project-specific htmlhint, the global one, or the embedded one. I should have an updated module published in the next day.

OK, this should be fixed with the extension version 0.3.0 that is now on the gallery.  Please let me know if there are any issuses.


unable to use createTuyau with next.js

Type error: Type 'OmitWithTag<typeof import("C:/dev/turbo/my-turborepo/apps/web/app/page"), "default" | "m │ etadata" | "config" | "generateStaticParams" | "revalidate" | "dynamic" | "dynamicParams" | "fetchCache" | │  ... 6 more ... | "experimental_ppr", "">' does not satisfy the constraint '{ [x: string]: never; }'. │   Property 'tuyau' is incompatible with index signature. │     Type 'TuyauRpcClient<ApiDefinition>' is not assignable to type 'never'. │ │   10 | │   11 | // Check that the entry is a valid entry │ > 12 | checkFields<Diff<{ │      |             ^ │   13 |   default: Function │   14 |   config?: {} │   15 |   generateStaticParams?: Function
page.tsx
`
import { ApiDefinition } from "backend-sdk/api";
import { createTuyau } from "@tuyau/client";
...
export const tuyau = createTuyau<{ definition: ApiDefinition }>({
baseUrl: "http://localhost:3333",
});
`
when i run pnpm run build this type error pops up. the client can be used, is type safe and works fine however.

Please format code properly and provide a minimal reproduction. Also we have a guide for using Tuyau in next https://tuyau.julr.dev/docs/next-js


HTTP -> HTTPS redirection is faulty on shadered.org

When you visit http://shadered.org, you get a 403 Forbidden error. However, https://shadered.org/ works fine. This hints at an issue in the web server configuration.
PS: You should also make https://www.shadered.org redirect to https://shadered.org (rather than serving the same pages under both subdomains) to avoid potential issues with duplicate content in search engines.
See also https://github.com/dfranx/THEMEed/issues/1.

Thank you for reporting this. Both http://shadered.org and www.shadered.org should now redirect to https://shadered.org . Though, now I have a problem with api.shadered.org subdomain (which SHADERed app uses to communicate with the web server). It serves content from shadered.org instead of shadered.org/api. I'll leave this open until I fix that issue.

Should be completely working now!


Stellar::Base::VERSION is returning error

hash["stellar_base_version"] = Stellar::Base::VERSION is returning error  `version': uninitialized constant Stellar::Base (NameError).  I note a missing line in ./lib/stellar-base.rb that I think should read:  require_relative './stellar/base/version'.  without this line the Base::VERSION is not linked.  adding this line seems to fix the problem.  This missing line is seen in all version ruby-stellar-base that I've looked at so far from very old 0.1.4 to 0.10.0

Already merged https://github.com/stellar/ruby-stellar-base/pull/22  fix for issuer#21 missing VERSION #22 so I guess we can close this


More friendly API discovery methods

For instance,
api.MethodByName("SayHello").
    Get().  // or HTTPMethod("GET")
    Path("/hello").
    Scopes("one", "two").
    ClientIDs("some-client-id").
    Desc("A method that says hello")

Also, api.MethodByName should panic if no such method exists.

@adg to comment based on our conversation today.

Honestly I think the builder pattern makes the most sense in this context.

We discussed this with @campoy today. Francesc, do you want to post that snipper here?

Taken from the go-endpoints README.md:
import "github.com/GoogleCloudPlatform/go-endpoints/endpoints"

func init() {
  greetService := &GreetingService{}
  api, err := endpoints.RegisterService(greetService,
    "greeting", "v1", "Greetings API", true)
  if err != nil {
    log.Fatalf("Register service: %v", err)
  }

  register := func(orig, name, method, path, desc string) {
      m := api.MethodByName(orig)
      if m == nil {
          log.Fatalf("Missing method %s", orig)
      }
      i := m.Info()
      i.Name, i.HTTPMethod, i.Path, i.Desc = name, method, path, desc
  }

  register("List", "greets.list", "GET", "greetings", "List most recent greetings.")
  register("Add", "greets.add", "PUT", "greetings", "Add a greeting.")
  register("Count", "greets.count", "GET", "greetings/count", "Count all greetings.")
  endpoints.HandleHTTP()
}

Should we close this for now, @crhym3 ?

Yeah, forgot to close it. Thanks everyone for comments and suggestions!


Live share in windows 7

Issue Type: Feature Request
I am not able to start live share on my laptop that has windows 7. I can't understand what's the problem. Please let me know about this.
VS Code version: Code 1.50.1 (d2e414d9e4239a252d1ab117bd7067f125afd80a, 2020-10-13T15:06:15.712Z)
OS version: Windows_NT x64 6.1.7601

Please open an issue on https://github.com/MicrosoftDocs/live-share


Question: Asynchronous I/O (asyncio) compatibility

I'm wondering about using this plugin with the asyncio support in SQLAlchemy.
Given the +asyncpg in the connection strings in all the examples, I'm assuming that there would need to be modifications made to this project to support it, but maybe I'm wrong. It might just be helpful to document [lack of] support for it (if only in this issue).

Thanks for your interest. Asyncio is not supported in this library, and there are no specific plans to support it.
This library depends on boto3/botocore, which is an officially supported, extremely high quality dependency. Until botocore adds support for asyncio, this library will not be in a position to support it (third-party forks of boto3 that add asyncio are not a suitable substitute).
In general I'm not sure that asyncio has high utility - it would be helpful if people could provide examples of concrete advantages that it brought to their application (in the form of benchmarks of asyncio vs. traditional worker pool architectures).

Thanks, Andrey!
I think that covers the question, and this issue can serve to answer it for anyone else who's searching for the same thing.


add Brian to Contributors.md

added myself to the contributors file

That's Awesome @BrianSpencerDev 🔥🔥
Congrats on making your first contributions Brian 🥳🥳


The 'this' keyword is equivalent to 'undefined' at the top level of an ES module, and has been rewritten

I got this error message when run "father build":
"The 'this' keyword is equivalent to 'undefined' at the top level of an ES module, and has been rewritten"
Context

Father Version: 2.29.2
Node Version: 12.16.1
Platform: MAC OS Catalina 10.15.4

same problem, import @ant-design/icon

经过测试，用require就行了，比如：
const { PlusCircleFilled } = require('@ant-design/icons');

同样的问题 导入immutable.js
Build cjs with rollup
The 'this' keyword is equivalent to 'undefined' at the top level of an ES module, and has been rewritten
Error when using sourcemap for reporting an error: Can't resolve original location of error.
✖  error     Error: 'OrderedSet' is not exported by node_modules/_immutable<EMAIL_ADDRESS>at error (/Users/lambda/code/my-draft-js/node_modules/_rollup@1.27.8@rollup/dist/rollup.js:5363:30)

@Topgt +1

how to fix ?

how to fix ?

how to fix ?

https://rollupjs.org/guide/en/#error-this-is-undefined

father 4 已发布，可尝试升级到最新版：https://github.com/umijs/father/blob/master/docs/guide/migrate.md
旧版本不再维护，感谢支持


How to start voxel SDK programming with BCB6 in Win7 win32 environment

1 . I use OPT8241-CDK-EVM   , Self-development program
2. I need to install software and steps .
3. Examples of programs BCB6 ?

Could you please see the wiki page? https://github.com/3dtof/voxelsdk/wiki
~ Prasad Bhat
On 19-Apr-2016 7:56 AM, "AtiiTed"<EMAIL_ADDRESS>wrote:

1 . I use OPT8241-CDK-EVM , Self-development program
2. I need to install software and steps .
3. Examples of programs BCB6 ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/3dtof/voxelsdk/issues/70

I have question about "Build from source on Windows" , i use voxel.lib and 3dtof.lib development BCB6 program,  I think comfirm CMake ,Git ,Doxygen,GarphViz and SWIG sofeware need to install ?
https://github.com/3dtof/voxelsdk/wiki/Build-from-source-on-Windows

Sorry, I'm afraid we don't support BCB6 - you're on your own there.


related posts refactor/tests

What is this
This is a fairly large refactor of Related Posts, motivated by a desire to simplify some of the logic in def related_posts (in v1/models/base.py) and spiraled into having to update other things, such as ref.py. A couple things of note:

There is a new field on CFGOVPage -- related_posts_categories, derived from a new model RelatedPostsCategory. It's the same as CFGOVPageCategory in code and behavior. It's meant to be used in place of specific_categories on a page with a Related Posts module, but I will follow up with @sarahsimpson09 to see if this is workable.

The motivation behind making it a model, as opposed to a list in a Wagtail block, is that it should be easy to update these categories on the back-end, without relying on the publishing flow to see the changes.  Other work in this PR would've necessitated re-publishing many of the pages if not for this migration,  which isn't really an option given that we rely heavily on date_published for determining which content to display first or at all.

How to test

Pull down the branch, grab the latest production db and import it, run migrations
After running migrations, run python cfgov/manage.py runscript update_categories to fill in the new related_posts_categories with data from specific_categories, which we will want to remove eventually
Check a few pages with related posts modules, e.g. http://localhost:8000/about-us/blog/what-do-if-youre-wrongfully-billed-medicare-costs/ to confirm they look like what's on www (https://www.consumerfinance.gov/about-us/blog/what-do-if-youre-wrongfully-billed-medicare-costs/)

TODO

Update old, failing tests
Actually write the new tests

There are a couple things I need to do still, + update tests, but I'd love to get feedback on this approach in the meantime.

The motivation behind making it a model, as opposed to a list in a Wagtail block, is that it should be easy to update these categories on the back-end, without relying on the publishing flow to see the changes.

I don't love the idea of disconnecting this field from the Related Posts block, and I don't fully understand the motivation you gave. Could you elaborate a little?

@Scotchester Sure - basically, there's no way to reference another model inside the Related Posts Block -- on the face of it, it looks like you can do it in a ChoiceBlock, but you'll eventually run into issues with Django not being able to serialize those values (https://docs.djangoproject.com/en/1.8/topics/migrations/#migration-serializing) when it comes time to migrations. As far as I can tell, the InlinePanel is the only way to model this relation -- http://docs.wagtail.io/en/v1.9/reference/pages/panels.html#inline-panels, which is not something you can define inside a StructBlock.

After talking to @chosak I'm going to do a little bit more exploratory work so that it doesn't have to be outside the Related Posts block, but it will result in a lot more changes since it would involve removing ref.py altogether.

Closing for now

Back in the sheer days, we used Elasticsearch's "more like this" to provide related content. I wonder if we can sidestep this complexity by getting serious about indexing wagtail content in ES, and going that direction.
https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-mlt-query.html

@richaagarwal I don't see an issue with reducing some of ref.py but not all of it. Different things in there have been added at different times for different reasons, and are not all related. If you can pull some stuff out of there to aid in your refactor of Related Posts, in a way that doesn't break anything else, but leave the rest of ref.py to be addressed later, I don't have a problem with that.
Perhaps you can elaborate on what you mean by "I think that will cause a lot of confusion"?


Codecov is broken

{'detail': ErrorDetail(string='Unable to locate build via Azure API. Project is likely private, please upload with the Codecov repository upload token to resolve issue.', code='not_found')}

Not broken anymore, closing.


[Feature] Create EigenDecomposition for Complex FieldMatirx

Can you please create EigenDecomposition's for  `FieldMatirx
Can you also introduce a constructor for
public OrderedComplexEigenDecomposition(final FieldMatrix<Complex> matrix, ...)

parameter?
Complex eigenvalues can be sorted descending by their "absolute value" for example.

See #248


JSDoc and TypeScript for ModelManager.addModelFiles is inconsistent with code

Describe the bug
The JsDoc says:
    /**
     * Add a set of Concerto files to the model manager.
     * @param {string[]} modelFiles - An array of Concerto files as
     * strings.
...

And the typescript signature says:
    addModelFiles(modelFiles: string[], fileNames?: string[], disableValidation?: boolean, systemModelTable?: boolean): any[];

But that API call supports both model files as strings or as ModelFile objects.

@jeromesimeon is this issue open ?


For anybody whos having a black screen

I read some of the post in the Issues tab and fixed the black screen problem. The "game" (i suppose) is in this zip file. I swear to god i didnt put any virus in here because im literally 13 yrs old. Thank you for coming by!
(Just go to the NonEuclidean folder, double click on the only exe file in there and play!)
NonEuclidean-master(fixed).zip

Yes im 13 irl and im a student so pls dont question me ty

Fork the repo, redo your changes in the fork, and submit your changes as a pull request. That way, the issue can be properly resolved.

And yes, what I described is basic GitHubbing. It's OK though, we all were new to this at some point ;-)

Sorry that i replied late but im suprised you are still here! Thank you for you advice!

here you go @ehx-v1! Thank you for telling me how to ACTUALLY fix this issue!
https://github.com/HackerPoet/NonEuclidean/pull/65


Update CUDA layer to 12.1

Related to: https://issues.redhat.com/browse/RHOAIENG-4344
Description
This pull request implements a significant update to the CUDA layer, transitioning from version 11.8.0 to 12.1.1.
The choice of version 12.1.1 was made due to its compatibility with both TensorFlow and PyTorch packages:

For PyTorch:
The latest available version of PyTorch, 2.2.0, is compatible with CUDA version 12.1 This compatibility ensures smooth integration with PyTorch functionalities.
Reference: https://pytorch.org/get-started/previous-versions/#linux-and-windows

For TensorFlow:
The compatible version of TensorFlow with CUDA 12.1 is version 2.15.0, ensuring seamless operation and support for TensorFlow GPU-accelerated tasks.
Reference: https://www.tensorflow.org/install/source#gpu

How Has This Been Tested?
Need first to merge this PR that updates the the above mentioned python packages.
Merge criteria:

[ ] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work

/retest-required

seems like the notebook are empty.
podman run -it -p 8888:8888 quay.io/opendatahub/workbench-images:cuda-jupyter-tensorflow-ubi9-python-3.9-pr-454

Need to double check this.

Maybe perhaps , it was my system issue
on the cluster, it work as required
(app-root) nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Mon_Apr__3_17:16:06_PDT_2023
Cuda compilation tools, release 12.1, V12.1.105
Build cuda_12.1.r12.1/compiler.32688072_0


Unstyled lists are not recognized by iOS/Voiceover

Describe the bug
Unstyled lists are not recognized by iOS/VoiceOver. The Unstyled List example is implemented with list-style-type:none. list-style-type:none can make it difficult for screen reader users to differentiate list items from one another by preventing the announcement of the word "bullet" before each list item.
How to reproduce
https://clarity.design/documentation/lists
Steps to reproduce the behavior:

Using an iPhone or iPad with Safari and VoiceOver, read the list in the Unstyled Lists example.
Observe that the screen reader does not announce to the user that they are reading a list.
Observe that the word "bullet" is NOT announced by the screen reader before each list item is announced

Expected behavior
Use overflow:hidden to hide the list bullets as seen at http://chrislane.info/examples/listWithHiddenBullets.html
Versions
App

Angular: [e.g. 6]
Node: [e.g. 8.10.0]
Clarity: [e.g. 0.12.5]

Device:

Type: [e.g. MacBook]
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional notes
Update the documentation to warn Clarity consumers to avoid implementing complex list items, since Mac OS X/Safari/VoiceOver does not announce the bullets for complex list items even when "list-style: none" is not in use.

This is definitely an issue (not just merely a BP), but I've made it low, because while confusing, it doesn't mislead significantly or prevent navigation as some of the other tickets do


Folders in Database Tasks Tab are collapsing in case of task deletion

When grouping is enabled for DB tasks, then folders in Database Tasks Tab are collapsing in case of task deletion:

(transferred from the EE bug tracker)

Duplicate of #10789


Docker container Failed error

Script failed to run: Docker code runner got container error: [Docker code script is in inconsistent state, expected pong but didn't got any response, exit error: Container exit with error. container name: [demistoserver_pyexec-ae9cdf1d-d970-4ef4-8684-35dd857a395c-demistopython<IP_ADDRESS>99--83] error: [exit status 1] stderr: [/usr/local/bin/python: can't find 'main' module in '/tmp/pyrunner/_script_docker_python_loop.py'
] (2619) (2610)] (2611) (2603)

If export pack integration to demisto, above error displayed

Closing the issue in content-docs repository
The correct repository for issues like this is the content repository
There is already an open issue there https://github.com/demisto/content/issues/19123


Fix issue 2696: remove some invalid test cases. Because no Nacos server now.

Describe what this PR does / why we need it
Remove some invalid test cases which depend on Nacos server. Because no Nacos server now.
Does this pull request fix one issue?
Fixes #2696
Describe how you did it
Describe how to verify it
run mvnw test
Special notes for reviews

It's not the problem you did, I solved it in #2871


Adds append for unpartitioned hive tables using the execution api.

Adds the ability to append to an unpartitioned hive table. Since Hadoop doesn't allow for writing to a directory that already exists we instead write to a temporary folder, munge the file names and then copy them across.

Once the Hdfs.mkdirs line is fixed, and the tmpDir deletion is protected inside the execution equivalent of a finally block, I am happy: :+1:

Getting tmpDir protected took quite a bit of effort.
@SamRoberts what do you think of this approach. Unfortunately, I ended up adding another nested method :(.

:+1:


net/frr: Add logging...

... to help with https://forum.opnsense.org/index.php?topic=14312.0

I'm not sure how this helps: it prints something if all is well.

"Tue Gutes und sprich darüber..."
At least the system will tell then that it is going through that code path. During CARP failover it is chatty anyway - one more line does not hurt. And it took me some time to find that devd configuration error with the laggX_vlanX devices...

currently not mergeable


GlobalMessagePipe.SetProvider does not work with IL2CPP

Calling GlobalMessagePipe.SetProvider (provider) during IL2CPP Build results in an InvalidOperationException.

Unity 2021.1.16f1
Windows 10 64bit

Sample Code
using MessagePipe;
using UnityEngine;

public class Installer
{
    [RuntimeInitializeOnLoadMethod]
    private static void Initialize()
    {
        var builder = new BuiltinContainerBuilder();
        builder.AddMessagePipe();
        builder.AddMessageBroker<int>();

        var provider = builder.BuildServiceProvider();
        GlobalMessagePipe.SetProvider(provider);
    }
}

InvalidOperationException: Sequence contains no elements
  at System.Linq.Enumerable.First[TSource] (System.Collections.Generic.IEnumerable`1[T] source) [0x00000] in <00000000000000000000000000000000>:0
  at MessagePipe.ServiceProviderType..ctor (System.Type type) [0x00000] in <00000000000000000000000000000000>:0
  at MessagePipe.BuiltinContainerBuilderServiceProvider+<>c__DisplayClass2_1.<.ctor>b__1 () [0x00000] in <00000000000000000000000000000000>:0
  at System.Func`1[TResult].Invoke () [0x00000] in <00000000000000000000000000000000>:0
  at System.Lazy`1[T].CreateValue () [0x00000] in <00000000000000000000000000000000>:0
  at System.Lazy`1[T].LazyInitValue () [0x00000] in <00000000000000000000000000000000>:0
  at MessagePipe.BuiltinContainerBuilderServiceProvider.GetService (System.Type serviceType, System.Int32 depth) [0x00000] in <00000000000000000000000000000000>:0
  at MessagePipe.DependencyInjectionShims.GetRequiredService[T] (System.IServiceProvider provider) [0x00000] in <00000000000000000000000000000000>:0
  at MessagePipe.GlobalMessagePipe.SetProvider (System.IServiceProvider provider) [0x00000] in <00000000000000000000000000000000>:0

What is your stripping level?

I've tested.
Low - OK
Medium - NG
High - NG
It should be fix, thanks!

Probably Low...

Oh, it's weird.......
Anyway, I have released 1.3.1.
This is all working in my test environment, even with IL2CPP at Stripping Level High.

I confirmed the correct operation on 1.3.1.
Thank you for your prompt correction!


Attaching NSG to specified vnets?

The documentation states "This Terraform module deploys a Network Security Group (NSG) in Azure and optionally attach it to the specified vnets."
I do not see a way to specify a vnet. This functionality doesn't seem to be implemented in the module.

The module has predefined rules for azurerm_network_security_group. Please take a look at the examples in package: https://github.com/Azure/terraform-azurerm-network-security-group/tree/master/modules


BIG CHANGES: Added new structures, fixed Classes.

🚀 Added large changes to src/structures. Created new structs (base, guildchannel, storechannel, newschannel, channel). Updated other structs to extend guildchannel and channel correctly. no methods have been added yet, but all the properties should be there. fixed issue with permission overwrites where permission overwrites was
//original:
Array<Overwrites>
//updated to
Map<string, Overwrites> = new Map()

just double check the props and tell me if I am missing anything.

Wait I'll update it forget to change textchannel props.

Please use new Map<string, Overwrites>()


New option to exclude spans faster than a latency threshold

Similar to slowQueryThresholdMs, another beneficial optional setting would be a flag to omit spans that are faster than some latency threshold (i.e: excludeSpansBelowQueryThreshold=100ms). This can be implemented identically to the existing flag, but will reduce the number of spans produced by the Driver.
This change will have significant performance benefits on systems that produce high numbers of JDBC spans. It will also keep spans whose latencies are small (fast requests) enough to be considered non-negligible.
I think I have a solution in mind, and if you all are ok, I can spin up a PR!

@naveedyahyazadeh PR is welcome

Done, see PR #112 @malafeev

Thank you for merging. Might I also bother you to release a new minor version release?

@naveedyahyazadeh 0.2.14 is released

Thank you for the swift responses and action!


Converting config from fos_user doesn't work

I tried this xml with the web-ui-converter:
https://raw.githubusercontent.com/FriendsOfSymfony/FOSUserBundle/master/Resources/config/validation.xml
Didn't work unfortunately. Any hint?

Hi Matthias!
This appears to be a validator mapping. Unfortunately, this tool only
supports service container config files. Sorry!
On Oct 13, 2017 1:56 PM, "Matthias Krieft"<EMAIL_ADDRESS>wrote:
I tried this xml with the web-ui-converter:
https://raw.githubusercontent.com/FriendsOfSymfony/FOSUserBundle/master/
Resources/config/validation.xml
Didn't work unfortunately. Any hint?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rosstuck/TuckConverterBundle/issues/17, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAI9ToEefpxMFPiIjgsm-gpuxmGZqVN8ks5sr0_SgaJpZM4P4YLm
.

Ah ok, thx anyway for the quick response! :-)


Tree shaking

When using DateObject alone (import { DateObject } from 'react-multi-date-picker';), css styles also get added.
I think the it happens because Calendar is exported as default, thus being imported even with other things.
https://github.com/shahabyazdi/react-multi-date-picker/blob/7f11b5056f18d4ab303433afa171475a0dac8440/src/index.js#L6
And I guess the css is not the only "unwanted" thing being imported, but a lot of other components are imported too.
Current workaround:
✅ import DateObject from 'react-date-object'; // 20.4k (gzipped: 6.3k)
❌ import { DateObject } from 'react-multi-date-picker'; // 67.9k (gzipped: 20.8k)

Hi shahriar.
I will work on it.

This is not an issue with tree-shaking but rather intended behavior due to style injection in PostCSS. I implemented style injection so users would not have to manually import styles every time they want to use the DatePicker or the Calendar. If I remove the style injection, We have to ask users to import the styles manually every time they want to use the date picker or calendar, Even if I decide to do so, it should be done in the next major version. I will keep this issue open for more consideration. Until then, please import the date object from its own library. Thank you for the feedback!


Clean hostnames in collectd and ELK

Some hostnames are set in collectd by hand (i.e. DICE CDH slave4).
Remove custom name and use FQDN (i.e. dice.cdh5.s4.internal) or hostname (i.e. 109-231-126-222)

set FQDNlookup to true in collectd template


"" when the sender name has a ":"

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
latest
Where did you get the app from?
None
Android version
10
Device model
samsung
Steps to reproduce
Howdy,
If the sender, has in it's client the name as "email: john" and send's an email to me, and i see it in K9, K9 translated the sendername to "unknown server",
If you need any further indo let me know, i saved the messaged.

Expected behavior
Display name as it is
Actual behavior
wrong displayed information
Logs
sdfg

Hum, K9 is coding the header, the real, is indeed in quoted printable
From: =?utf-8?Q?Email:_Dire=C3=A7=C3=A3o?=<EMAIL_ADDRESS>

This is an invalid encoding. The display name needs to be an RFC 5322 phrase. A : is only allowed in a quoted string or in encoded form in an RFC 2047 encoded word.
Did you use K-9 Mail to create this email? Or did some other email client create this header?

In my tests K-9 Mail encoded names containing : correctly.
Closing this issue because no further information was provided.