Frequent gRPC StatusCode.UNAVAILABLE errors

Using the current codebase from master branch (e1fbb6b), with GRPC, we sometimes (0.5% of requests, approximately) see the following exception:
 AbortionError(code=StatusCode.UNAVAILABLE, details="{"created":"@1478255129.468798425","description":"Secure read failed","file":"src/core/lib/security/transport/secure_endpoint.c","file_line":157,"grpc_status":14,"referenced_errors":[{"created":"@1478255129.468756939","description":"EOF","file":"src/core/lib/iomgr/tcp_posix.c","file_line":235}]}"))

Retrying this seem to always succeed.
Should application code have to care about this kind of error and retry? Or is this a bug in google-cloud-pubsub code?
Package versions installed:
gapic-google-logging-v2==0.10.1
gapic-google-pubsub-v1==0.10.1
google-api-python-client==1.5.4
google-cloud==0.20.0
google-cloud-bigquery==0.20.0
google-cloud-bigtable==0.20.0
google-cloud-core==0.20.0
google-cloud-datastore==0.20.1
google-cloud-dns==0.20.0
google-cloud-error-reporting==0.20.0
google-cloud-language==0.20.0
google-cloud-logging==0.20.0
google-cloud-monitoring==0.20.0
google-cloud-pubsub==0.20.0
google-cloud-resource-manager==0.20.0
google-cloud-storage==0.20.0
google-cloud-translate==0.20.0
google-cloud-vision==0.20.0
google-gax==0.14.1
googleapis-common-protos==1.3.5
grpc-google-iam-v1==0.10.1
grpc-google-logging-v2==0.10.1
grpc-google-pubsub-v1==0.10.1
grpcio==1.0.0

Note: Everything google-cloud* comes from git master.
This is on Python 2.7.3
Traceback:
  File "ospdatasubmit/pubsub.py", line 308, in _flush
    publish_response = self.pubsub_client.Publish(publish_request, self._publish_timeout)
  File "grpc/beta/_client_adaptations.py", line 305, in __call__
    self._request_serializer, self._response_deserializer)
  File "grpc/beta/_client_adaptations.py", line 203, in _blocking_unary_unary
    raise _abortion_error(rpc_error_call)

@forsberg As you can see from the stack trace, this comes from grpc.beta (the beta interface). We haven't used the beta interface for some time. How are you installing the library?

@nathanielmanistaatgoogle I can consistently reproduce an Unavailable error when a connection goes stale. Is there any way to avoid this, short of retrying on failures?

That library installation seems to have gone horribly wrong. We had an earlier version using the grpc.beta interface, and I guess installing this into the same virtualenv, something went wrong. Will investigate that on Monday.

@forsberg grpc 1.0 still supports the beta interface, but none of google-cloud-python (or its dependencies) use that interface any longer. So it'd be your google-cloud-python install that's b0rked rather than your grpc install.

@nathanielmanistaatgoogle See #2693 and #2699. What is the recommended way to deal with this for stale connections?

Small update: We have fixed our borked google-cloud-python install to actually use e1fbb6bc, but we're still seeing roughly the same number of UNAVAILABLE - retrying always works on first attempt.

@nathanielmanistaatgoogle Bump

@nathanielmanistaatgoogle Bump
/cc @geigerj This is the issue I was referring to about GAPIC retry strategies

@dhermes You can configure this on the GAPIC layer, see comment here for details. It actually looks like we already retry by default on UNAVAILABLE for Pub/Sub Publish, but you can override the default settings to extend the timeout on retry if that's the issue?

@geigerj I believe the correct link to "retry by default on UNAVAILABLE for Pub/Sub Publish" is this one, because the one you've provided no longer works.
The bug affects us too. When the connection is stale, we get exactly the same error as here (grpc._channel._Rendezvous but caused by PubSub publish action). Once we retry, it works.
We're using:
gapic-google-pubsub-v1==0.11.1
google-cloud-core==0.21.0
google-cloud-pubsub==0.21.0
google-gax==0.15.0
googleapis-common-protos==1.5.0
grpc-google-iam-v1==0.11.1
grpc-google-pubsub-v1==0.11.1

What seems strange is that the default retry you mentioned doesn't seem to work. And I have checked that the file publisher_client_config.json is present, with correct values. I get the unhandled exception much sooner than 60s, almost immediately (haven't measured it precisely).

Just wanted to add to the above, that disabling gRPC "fixed" the issue ($ export GOOGLE_CLOUD_DISABLE_GRPC=true) - there's no need for manual retrying and there are no errors with stale connections.

@dhermes: does that code of yours hit a particular host? If so, are you able to reproduce the problem against any other host? If you're able to hit that host with unauthenticated RPCs, are you able to reproduce the defect in the absence of authentication? If you are able observe the traffic at a low level (with Wireshark or something like it) is there anything obviously the matter? Obviously the expected behavior is that if you hold a grpc.Channel and don't use it for a matter of minutes it should still be able to make RPCs. They may take slightly longer if the underlying TCP connection has been taken down, but they shouldn't fail and then immediately succeed when reattempted.

@dhermes: when I run this code of yours I get StatusCode.PERMISSION_DENIED, so there's more to the reproduction of the problem than merely running that, right? Something has to happen server-side? Possibly something else has to happen locally?

I think I'm seeing a similar issue.
My goal is to have a connection to speech.googleapis.com always open so that whenever a user wants to say something, they can enter a 'y' through terminal and then speak instantly. Otherwise, establishing the connection seems to take about 4 seconds on our architecture.
However, it seems that the connection closes after a while. Would this issue be the cause?
I have taken google's streaming python example code and modified it for my purposes.
def main():
    # Open channel to Google Speech and keep it open indefinitely.
    with cloud_speech.beta_create_Speech_stub(
            make_channel('speech.googleapis.com', 443)) as service:
        answer = ""
        while True:

            # If we're not retrying from a failed attempt,
            # wait for the user to send 'y' to start recording
            if answer != "retry":
                answer = raw_input("Do you want to record? y/n: ")
            #  pass through raw_input block
            #  in an attempt to retry the streaming
            #  request.
            else:
                answer = "y"

            if answer == "y":
                print("Recieved the Y")

                # For streaming audio from the microphone, there are three threads.
                # First, a thread that collects audio data as it comes in
                with record_audio(RATE, CHUNK) as buffered_audio_data:
                    # Second, a thread that sends requests with that data
                    requests = request_stream(buffered_audio_data, RATE)
                    # Third, a thread that listens for transcription responses
                    recognize_stream = service.StreamingRecognize(
                        requests, DEADLINE_SECS)

                    try:
                        listen_print_loop(recognize_stream)
                        recognize_stream.cancel()

                    except face.CancellationError:
                        pass
                    except face.AbortionError:
                        print("ABORTION ERROR RECEIVED")
                        answer = "retry"

@dakrawczyk I think you might be running into the 1 minute limit for streaming.
See: https://cloud.google.com/speech/limits#content
You said...

establishing the connection seems to take about 4 seconds on our architecture.

Do you know if that connection overhead is on the google-cloud-python side or has something to do with your architecture?

@daspecster I don't think it's the 1 minute limit for streaming, I do know what you're talking about, but I'm not actually streaming until the user enters 'y' and the record/request/response streams are started and used. My understanding is that I'm only just creating the channel to begin with and that doesn't count against the 1 minute timeout. Also I only end up streaming for about 10 seconds at a time.
I am building an embedded system using a samsung artik710 running debian.
When I run
     with cloud_speech.beta_create_Speech_stub(
            make_channel('speech.googleapis.com', 443)) as service:

on my MacBook it is basically instant.
When it runs on my embedded architecture it takes about 4 seconds.

Ok, good to know!
I just realized that your code is actually not using this library. You're using the gRPC library directly.
I don't know that this is the best issue to discuss as it might be kind of drawn out.
If you want you can ping me on https://googlecloud-community.slack.com. I've spent some time in Speech so I might be able to help get you going.

@dakrawczyk Hello! Looks like you're using the sample that I wrote, so I'm here to take blame / responsibility ^_^;
From the symptoms you describe (error happens in time span > streaming limits, re-starting the stream a lot, some auth thing mentioned above), my guess is that the access token is expiring.
The make_channel function grabs an access token the first time it's run (ie when it creates the channel), but doesn't refresh it, so if you keep it open for long enough, soon enough the access token's validity period expires. I imagine each time you start a new stream, grpc is re-sending the auth headers, so eventually you'll start getting auth errors.
If that's the case, you might be able to fix this by modifying make_channel so that it calls get_access_token() on the fly, instead of just getting it upon channel creation.
Let me know how that works. I haven't looked at the google-cloud-python code, but perhaps it's a similar issue?

Also - the sample has since been updated to use the google-auth package, which should also fix that issue.

@jerjou Thank you! Trying this out now :]

@jerjou I've updated to the newer sample code that uses the google-auth package.
I am still under the impression that the channel closes after a certain amount of time, probably due to the validity expiring.
Here is the error I receive when trying to send/receive data from the channel after some time and the channel has closed.
Traceback (most recent call last):
  File "transcribe_streaming.py", line 323, in <module>
    main()
  File "transcribe_streaming.py", line 310, in main
    listen_print_loop(recognize_stream)
  File "transcribe_streaming.py", line 239, in listen_print_loop
    for resp in recognize_stream:
  File "/usr/local/lib/python2.7/site-packages/grpc/_channel.py", line 344, in next
    return self._next()
  File "/usr/local/lib/python2.7/site-packages/grpc/_channel.py", line 335, in _next
    raise self
grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with (StatusCode.UNAVAILABLE, {"created":"@1482091441.761674000","description":"Secure read failed","file":"src/core/lib/security/transport/secure_endpoint.c","file_line":157,"grpc_status":14,"referenced_errors":[{"created":"@1482091441.761631000","description":"EOF","file":"src/core/lib/iomgr/tcp_posix.c","file_line":235}]})>

A couple of questions:

Is there a way for me to poll the status of the channel and if I detect that it has closed, reopen it?
Or/Also a way to keep the channel open indefinitely?

I can't reopen the channel when the user wants to record because it has a few second delay and that's not the experience we're going for.

How do I join https://googlecloud-community.slack.com? Is it a closed group?

Slack: https://gcp-slack.appspot.com/

@jerjou thanks. I just joined.

Hey guys, read this thread an still didn't came up a solution..
when trying
GOOGLE_CLOUD_DISABLE_GRPC=true

getting connection timeout because it's trying to localhost:8499
what am I am missing??

@ohadperry, some of the emulators run on 84xx ports. I'm not sure what your system configuration is though.

@daspecster hi. I understand that it supposed to connect to an emulator.
My question is how to get it connect to my project's production pub sub?
I don't care whether it's RPC or https

By default, it shouldn't try to connect to the emulator. My guess is that there's probably something in your configuration/environment that's redirecting it.
You could check if the PUBSUB_EMULATOR_HOST environment variable is set. If so then you'll want to unset it.

@daspecster thanks unset my PUBSUB_EMULATOR_HOST from my environment variables worked!!
Any comments as to what the rpc network shouldn't work? RPC should increase The push / pull rate , shouldn't ? if yes, then i'm really interested in why it's not working for me.

gRPC may increase performance depending on your application.
google-cloud defaults to using gRPC. So unless there was an error during installation, I would guess that it's using PubSub over gRPC already.
grpc-google-cloud-pubsub-v1==0.14.0
grpcio==1.0.4

If you have those two libraries installed then I think you're probably all set.
You can check after you instantiate your Client with something like...
client = pubsub.Client()
print(client._use_gax)

If _use_gax is True then the library is using gRPC.

@daspecster , yes I know. I meant i'm getting gRPC StatusCode.UNAVAILABLE errors when using the gRPC here are my pips
grpc-google-iam-v1==0.10.1
grpc-google-pubsub-v1==0.10.1
grpcio==1.0.1

Those are fairly old. You might want to try updating them, but I can't say that updating will solve the UNAVAILABLE issue. Mostly I think you'll want to code in retries on that event.

The exception thrown is fairly internal. Could the cloud-pubsub library catch the error and throw something more descriptive. Also can the retries be documented?

Upgraded my stack to google-cloud-pubsub==0.22.0. Error is still present, traceback/error message is slightly different. Here's a fresh one:
ERROR 2017-02-22 08:16:31,484
Traceback (most recent call last):
  File "/opt/ospdatasubmit/virtualenvs/ospsubmit.opera.com/v1/local/lib/python2.7/site-packages/ospgcptools/pubsub/__init__.py", line 327, in flush
    self.pubsub_topic.publish(data)
  File "/opt/ospdatasubmit/virtualenvs/ospsubmit.opera.com/v1/local/lib/python2.7/site-packages/google/cloud/pubsub/topic.py", line 253, in publish
    message_ids = api.topic_publish(self.full_name, [message_data])
  File "/opt/ospdatasubmit/virtualenvs/ospsubmit.opera.com/v1/local/lib/python2.7/site-packages/google/cloud/pubsub/_gax.py", line 173, in topic_publish
    options=options)
  File "/opt/ospdatasubmit/virtualenvs/ospsubmit.opera.com/v1/local/lib/python2.7/site-packages/google/cloud/gapic/pubsub/v1/publisher_client.py", line 290, in publish
    return self._publish(request, options)
  File "/opt/ospdatasubmit/virtualenvs/ospsubmit.opera.com/v1/local/lib/python2.7/site-packages/google/gax/api_callable.py", line 442, in inner
    return api_caller(api_call, this_settings, request)
  File "/opt/ospdatasubmit/virtualenvs/ospsubmit.opera.com/v1/local/lib/python2.7/site-packages/google/gax/api_callable.py", line 70, in inner
    return a_func(request, **kwargs)
  File "/opt/ospdatasubmit/virtualenvs/ospsubmit.opera.com/v1/local/lib/python2.7/site-packages/google/gax/api_callable.py", line 395, in inner
    gax.errors.create_error('RPC failed', cause=exception))
  File "/opt/ospdatasubmit/virtualenvs/ospsubmit.opera.com/v1/local/lib/python2.7/site-packages/google/gax/api_callable.py", line 391, in inner
    return a_func(*args, **kwargs)
  File "/opt/ospdatasubmit/virtualenvs/ospsubmit.opera.com/v1/local/lib/python2.7/site-packages/google/gax/retry.py", line 67, in inner
    return a_func(*updated_args, **kwargs)
  File "/opt/ospdatasubmit/virtualenvs/ospsubmit.opera.com/v1/local/lib/python2.7/site-packages/grpc/_channel.py", line 511, in __call__
    return _end_unary_response_blocking(state, False, deadline)
  File "/opt/ospdatasubmit/virtualenvs/ospsubmit.opera.com/v1/local/lib/python2.7/site-packages/grpc/_channel.py", line 459, in _end_unary_response_blocking
    raise _Rendezvous(state, None, None, deadline)
GaxError: GaxError(RPC failed, caused by <_Rendezvous of RPC that terminated with (StatusCode.UNAVAILABLE, {"created":"@1487751391.483882744","description":"Endpoint read failed","file":"src/core/ext/transport/chttp2/transport/chttp2_transport.c","file_line":1851,"grpc_status":14,"occurred_during_write":0,"referenced_errors":[{"created":"@1487751391.483832140","description":"Secure read failed","file":"src/core/lib/security/transport/secure_endpoint.c","file_line":166,"referenced_errors":[{"created":"@1487751391.483828339","description":"Socket closed","fd":67,"file":"src/core/lib/iomgr/tcp_posix.c","file_line":249,"target_address":"ipv6:[2a00:1450:400e:807::200a]:443"}]}]})>)

Some package versions:
pip freeze|egrep 'grpc|pubsub|google-cloud-core|grep protobuf'
gapic-google-cloud-pubsub-v1==0.14.1
google-cloud-core==0.22.1
google-cloud-pubsub==0.22.0
grpc-google-cloud-pubsub-v1==0.14.0
grpc-google-iam-v1==0.11.1
grpc-google-pubsub-v1==0.10.1
grpcio==1.1.0

Timestamp in UTC if some googler wants to look on the other side. Let me know if there's something I can add to my logs to aid in debugging.
In most cases, an immediate retry will fix the problem. Sometimes we have to retry 2 or 3 times (we give up after 3 times and drop the message).

Also seeing this issue. Retrying within in our own code seems to workaround the issue. we also only retry a max of 3 times. Usually second try fixes it.
We were on 0.18 and just upped to 0.23.
We run python 3.6
$ pip freeze|egrep 'grpc|pubsub|google-cloud-core|grep protobuf'
gapic-google-cloud-pubsub-v1==0.15.0
google-cloud-core==0.23.1
google-cloud-pubsub==0.23.0
grpc-google-cloud-logging-v2==0.90.0
grpc-google-iam-v1==0.11.1
grpcio==1.1.3
proto-google-cloud-pubsub-v1==0.15.1

Traceback (most recent call last):
  File "/opt/app/psutils.py", line 129, in _pub_topic
    return topic.publish(bytes(json.dumps(data), 'utf-8'))
  File "/home/pythonapp/.pyenv/versions/3.6.0/envs/venv/lib/python3.6/site-packages/google/cloud/pubsub/topic.py", line 255, in publish
    message_ids = api.topic_publish(self.full_name, [message_data])
  File "/home/pythonapp/.pyenv/versions/3.6.0/envs/venv/lib/python3.6/site-packages/google/cloud/pubsub/_gax.py", line 174, in topic_publish
    options=options)
  File "/home/pythonapp/.pyenv/versions/3.6.0/envs/venv/lib/python3.6/site-packages/google/cloud/gapic/pubsub/v1/publisher_client.py", line 320, in publish
    return self._publish(request, options)
  File "/home/pythonapp/.pyenv/versions/3.6.0/envs/venv/lib/python3.6/site-packages/google/gax/api_callable.py", line 419, in inner
    return api_caller(api_call, this_settings, request)
  File "/home/pythonapp/.pyenv/versions/3.6.0/envs/venv/lib/python3.6/site-packages/google/gax/api_callable.py", line 67, in inner
    return a_func(request, **kwargs)
  File "/home/pythonapp/.pyenv/versions/3.6.0/envs/venv/lib/python3.6/site-packages/google/gax/api_callable.py", line 372, in inner
    gax.errors.create_error('RPC failed', cause=exception))
  File "/home/pythonapp/.pyenv/versions/3.6.0/envs/venv/lib/python3.6/site-packages/future/utils/__init__.py", line 419, in raise_with_traceback
    raise exc.with_traceback(traceback)
  File "/home/pythonapp/.pyenv/versions/3.6.0/envs/venv/lib/python3.6/site-packages/google/gax/api_callable.py", line 368, in inner
    return a_func(*args, **kwargs)
  File "/home/pythonapp/.pyenv/versions/3.6.0/envs/venv/lib/python3.6/site-packages/google/gax/retry.py", line 68, in inner
    return a_func(*updated_args, **kwargs)
  File "/home/pythonapp/.pyenv/versions/3.6.0/envs/venv/lib/python3.6/site-packages/grpc/_channel.py", line 507, in __call__
    return _end_unary_response_blocking(state, False, deadline)
  File "/home/pythonapp/.pyenv/versions/3.6.0/envs/venv/lib/python3.6/site-packages/grpc/_channel.py", line 455, in _end_unary_response_blocking
    raise _Rendezvous(state, None, None, deadline)
google.gax.errors.GaxError: GaxError(RPC failed, caused by <_Rendezvous of RPC that terminated with (StatusCode.UNAVAILABLE, {"created":"@1488959268.808794184","description":"Endpoint read failed","file":"src/core/ext/transport/chttp2/transport/chttp2_transport.c","file_line":1851,"grpc_status":14,"occurred_during_write":0,"referenced_errors":[{"created":"@1488959268.808696874","description":"Secure read failed","file":"src/core/lib/security/transport/secure_endpoint.c","file_line":166,"referenced_errors":[{"created":"@1488959268.808693234","description":"Socket closed","fd":55,"file":"src/core/lib/iomgr/tcp_posix.c","file_line":249,"target_address":"ipv4:<IP_ADDRESS>:443"}]}]})>)

I really think my problem is related to this, we have a node.js connecting to a python server using gRpc and we frequently receive this: Critical: gRPC server raised an error.  Error: {"created":"@1489090385.752311821","description":"Endpoint read failed","file":"../src/core/ext/transport/chttp2/transport/chttp2_transport.c","file_line":1851,"grpc_status":14,"occurred_during_write":0,"referenced_errors":[{"created":"@1489090385.752305292","description":"TCP Read failed","file":"../src/core/lib/iomgr/tcp_uv.c","file_line":170}]} { Error: {"created":"@1489090385.752311821","description":"Endpoint read failed","file":"../src/core/ext/transport/chttp2/transport/chttp2_transport.c","file_line":1851,"grpc_status":14,"occurred_during_write":0,"referenced_errors":[{"created":"@1489090385.752305292","description":"TCP Read failed","file":"../src/core/lib/iomgr/tcp_uv.c","file_line":170}]}     at /app/node_modules/grpc/src/node/src/client.js:434:17   cause:     { Error: {"created":"@1489090385.752311821","description":"Endpoint read failed","file":"../src/core/ext/transport/chttp2/transport/chttp2_transport.c","file_line":1851,"grpc_status":14,"occurred_during_write":0,"referenced_errors":[{"created":"@1489090385.752305292","description":"TCP Read failed","file":"../src/core/lib/iomgr/tcp_uv.c","file_line":170}]}        at /app/node_modules/grpc/src/node/src/client.js:434:17 code: 14, metadata: Metadata { _internal_repr: {} } },   isOperational: true,   code: 14,   metadata: Metadata { _internal_repr: {} } }
Sometimes, the same request on the same server works without any problem.

@barroca This looks like a Node.js failure?

might be, we are creating a client in other language to isolate it.
I've just needed to share my frustration and see if someone had the same problem. Anyway, it's very strange since it is an intermittent error with no pattern,  it sometimes happens between seconds, sometimes between minutes. :(

@barroca  I had the same problem. In my case, If my Node.js run for a while without any request, this error will occur and making request again will get normal response.
Really need help
{ Error: {"created":"@1490271131.819044969","description":"Endpoint read failed","file":"../src/core/ext/transport/chttp2/transport/chttp2_transport.c","file_line":1851,"grpc_status":14,"occurred_during_write":0,"referenced_errors":[{"created":"@1490271131.819031343","description":"Socket closed","fd":16,"file":"../src/core/lib/iomgr/tcp_posix.c","file_line":249,"target_address":"ipv4:<IP_ADDRESS>:8980"}]} 2017-03-23T12:12:11.842630309Z     at /usr/local/wongnai/node_modules/grpc/src/node/src/client.js:434:17 2017-03-23T12:12:11.842638153Z   cause:  2017-03-23T12:12:11.842643446Z    { Error: {"created":"@1490271131.819044969","description":"Endpoint read failed","file":"../src/core/ext/transport/chttp2/transport/chttp2_transport.c","file_line":1851,"grpc_status":14,"occurred_during_write":0,"referenced_errors":[{"created":"@1490271131.819031343","description":"Socket closed","fd":16,"file":"../src/core/lib/iomgr/tcp_posix.c","file_line":249,"target_address":"ipv4:<IP_ADDRESS>:8980"}]} 2017-03-23T12:12:11.842652712Z        at /usr/local/wongnai/node_modules/grpc/src/node/src/client.js:434:17 code: 14, metadata: Metadata { _internal_repr: {} } }, isOperational: true, code: 14, metadata: Metadata { _internal_repr: {} } }

I confirm the intermittent errors when working with bigtable API

python 3.5.2
google-cloud==0.23.0
(storm) ➜  storm git:(develop) ✗ vi requirements/base.txt
(storm) ➜  storm git:(develop) ✗ pip freeze G google
21:gapic-google-cloud-datastore-v1==0.15.3
22:gapic-google-cloud-error-reporting-v1beta1==0.15.3
23:gapic-google-cloud-logging-v2==0.91.3
24:gapic-google-cloud-pubsub-v1==0.15.3
25:gapic-google-cloud-spanner-admin-database-v1==0.15.3
26:gapic-google-cloud-spanner-admin-instance-v1==0.15.3
27:gapic-google-cloud-spanner-v1==0.15.3
28:gapic-google-cloud-speech-v1beta1==0.15.3
29:gapic-google-cloud-vision-v1==0.90.3
31:google-auth==0.10.0
32:google-auth-httplib2==0.0.2
33:google-cloud==0.23.0
34:google-cloud-bigquery==0.23.0
35:google-cloud-bigtable==0.23.1
36:google-cloud-core==0.23.1
37:google-cloud-datastore==0.23.0
38:google-cloud-dns==0.23.0
39:google-cloud-error-reporting==0.23.2
40:google-cloud-language==0.23.1
41:google-cloud-logging==0.23.1
42:google-cloud-monitoring==0.23.0
43:google-cloud-pubsub==0.23.0
44:google-cloud-resource-manager==0.23.0
45:google-cloud-runtimeconfig==0.23.0
46:google-cloud-spanner==0.23.1
47:google-cloud-speech==0.23.0
48:google-cloud-storage==0.23.1
49:google-cloud-translate==0.23.0
50:google-cloud-vision==0.23.3
51:google-gax==0.15.8
52:googleapis-common-protos==1.5.2
55:grpc-google-iam-v1==0.11.1
80:proto-google-cloud-datastore-v1==0.90.3
81:proto-google-cloud-error-reporting-v1beta1==0.15.3
82:proto-google-cloud-logging-v2==0.91.3
83:proto-google-cloud-pubsub-v1==0.15.3
84:proto-google-cloud-spanner-admin-database-v1==0.15.3
85:proto-google-cloud-spanner-admin-instance-v1==0.15.3
86:proto-google-cloud-spanner-v1==0.15.3
87:proto-google-cloud-speech-v1beta1==0.15.3
88:proto-google-cloud-vision-v1==0.90.3
(storm) ➜  storm git:(develop) ✗ pip freeze G grpc
55:grpc-google-iam-v1==0.11.1
56:grpcio==1.2.1
(storm) ➜  storm git:(develop) ✗

@nathanielmanistaatgoogle Can you weigh in / can we all have a pow-wow about this?

I have same error with:
Client:

<EMAIL_ADDRESS>python 3.6
Server:
<EMAIL_ADDRESS>node 6.9

Client error message:
  File "/home/project/venv/lib/python3.6/site-packages/grpc/_channel.py", line 455, in _end_unary_response_blocking
    raise _Rendezvous(state, None, None, deadline)
grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with (StatusCode.UNAVAILABLE, Endpoint read failed)>

I updated to<EMAIL_ADDRESS>and I'm waiting to see if the error occurs again.
Notes: I'm not sure if Endpoint read failed is same as Secure read failed. I think I had both error from time to time.

@dhermes: my apologies for the silence; this is now properly being recognized as a problem in gRPC Core affecting all Core-using languages and will be fixed in Core. In the meantime I don't know that the options are any good: if your RPC is idempotent you can make application-level retries until it succeeds, but if it isn't idempotent you may have to awkwardly work around the issue in a problem-specific way.
So... yay that it's now properly being recognized as a defect. Boo to the rest. Yes to a sync if you'd still like one.

Thanks @nathanielmanistaatgoogle, is there a tracking issue somewhere?

@dhermes: there is now; please add any details (pretty please a deterministic reproduction?).

@nathanielmanistaatgoogle I already gave a deterministic reproduction. I am happy to chat with you off the thread about how to set up the credentials needed for this or we could work together (I'll need your expertise) to create a gRPC service that doesn't require auth to accomplish the same goal.

@lukesneeringer @dhermes The issue that @nathanielmanistaatgoogle referenced (https://github.com/grpc/grpc/issues/11043) was fixed on June 8. Is this still an issue?

@bjwatson Checking right now

The example still fails:
Listing all instances:
Traceback (most recent call last):
  File "bt_unavailable.py", line 30, in <module>
    main()
  File "bt_unavailable.py", line 26, in main
    list_em(client)
  File "bt_unavailable.py", line 8, in list_em
    instances, failed_locations = client.list_instances()
  File ".../google/cloud/bigtable/client.py", line 375, in list_instances
    response = self._instance_stub.ListInstances(request_pb)
  File ".../grpc/_channel.py", line 507, in __call__
    return _end_unary_response_blocking(state, call, False, deadline)
  File ".../grpc/_channel.py", line 455, in _end_unary_response_blocking
    raise _Rendezvous(state, None, None, deadline)
grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with (StatusCode.UNAVAILABLE, Endpoint read failed)>

This fails in Python 2.7 with grpcio==1.4.0

@nathanielmanistaatgoogle, looks like the gRPC fix was insufficient for this issue. Do you have any insight into what else might be going wrong?
FYI @lukesneeringer

Hello! :-)
First, a mea culpa; I have not done as good of a job at keeping up with issues as I should have. If you are getting this (I admit it) cut and paste, it is likely because your issue sat for too long.
In this case, I have been in the process of making a radical update to the PubSub library (#3637) to add significant performance improvements and a new surface, which we hope to launch soon. As such, I am clearing out issues on the old library. It is my sincere goal to do a better job of being on top of issues in the future.
As the preceding paragraph implies, I am closing this issue. If the revamped library does not solve your issue, however, please feel free to reopen.
Thanks!

@lukesneeringer from my recollection, this wasn't Pub/Sub-specific?

That's correct, I even reproduced it with bigtable 12 days ago.

Yeah, I was firing through everything with an api: pubsub label. Thanks for reopening.

I am removing all the "api: X" labels from this issue since issue automation is coming. The grpc label is the appropriate tracking.
Although really this should just be moved to grpc.

Reproduced the Bigtable issue with google-cloud-bigtable==0.26.0 during:
def write_row(key, column_id):
    """
    Utility method for writing a row to BigTable.
    Note that we don't actually store values - the column ids are where we actually store values,
    so the value is always just an empty string.
    :param key: Key of the row to write
    :param column_id: This is the actual value we want stored.
    :return: None
    """
    row = db.table.row(key)
    row.set_cell(conf.column_family_id, column_id, '')
    row.commit()

The error looks like:
_Rendezvous: <_Rendezvous of RPC that terminated with (StatusCode.UNAVAILABLE, Endpoint read failed)>
at _end_unary_response_blocking (/env/local/lib/python2.7/site-packages/grpc/_channel.py:455)
at __call__ (/env/local/lib/python2.7/site-packages/grpc/_channel.py:507)
at commit (/env/local/lib/python2.7/site-packages/google/cloud/bigtable/row.py:417)

Hi guys,
I'm also facing this issue but with PubSub subscription.
We've started a subscription for one topic yesterday and all is working fine.
However, today we saw this exception on the console.
I'm using the following packages:

google-auth==1.1.1
google-cloud-bigquery==0.27.0
google-cloud-core==0.27.1
google-cloud-logging==1.3.0
google-cloud-pubsub==0.28.3
google-cloud-storage==1.4.0
google-gax==0.15.15
google-resumable-media==0.2.3
googleapis-common-protos==1.5.3
grpc-google-iam-v1==0.11.3
proto-google-cloud-logging-v2==0.91.3

and I'm running on a Linux Machine (Ubuntu 16.04.3 LTS)
Exception:

Exception in thread Consumer helper: consume bidirectional stream:
Traceback (most recent call last):
File "/home/user/anaconda3/lib/python3.6/threading.py", line 916, in _bootstrap_inner
self.run()
File "/home/user/anaconda3/lib/python3.6/threading.py", line 864, in run
self._target(*self._args, **self._kwargs)
File "/home/user/anaconda3/lib/python3.6/site-packages/google/cloud/pubsub_v1/subscriber/_consumer.py", line 248, in _blocking_consume
self._policy.on_exception(exc)
File "/home/user/anaconda3/lib/python3.6/site-packages/google/cloud/pubsub_v1/subscriber/policy/thread.py", line 135, in on_exception
raise exception
File "/home/user/anaconda3/lib/python3.6/site-packages/google/cloud/pubsub_v1/subscriber/_consumer.py", line 234, in _blocking_consume
for response in response_generator:
File "/home/user/anaconda3/lib/python3.6/site-packages/grpc/_channel.py", line 348, in next
return self._next()
File "/home/user/anaconda3/lib/python3.6/site-packages/grpc/_channel.py", line 342, in _next
raise self
grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with (StatusCode.UNAVAILABLE, OS Error)>

I just got  this error while running a job on Google ML Engine.
Traceback (most recent call last): File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main "__main__", fname, loader, pkg_name) File "/usr/lib/python2.7/runpy.py", line 72, in _run_code exec code in run_globals File "/root/.local/lib/python2.7/site-packages/object_detection/train.py", line 198, in <module> tf.app.run() File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/platform/app.py", line 44, in run _sys.exit(main(_sys.argv[:1] + flags_passthrough)) File "/root/.local/lib/python2.7/site-packages/object_detection/train.py", line 194, in main worker_job_name, is_chief, FLAGS.train_dir) File "/root/.local/lib/python2.7/site-packages/object_detection/trainer.py", line 296, in train saver=saver) File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/slim/python/slim/learning.py", line 793, in train train_step_kwargs) File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/slim/python/slim/learning.py", line 546, in train_step if sess.run(train_step_kwargs['should_log']): File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 767, in run run_metadata_ptr) File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 965, in _run feed_dict_string, options, run_metadata) File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 1015, in _do_run target_list, options, run_metadata) File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 1035, in _do_call raise type(e)(node_def, op, message) UnavailableError: {"created":"@1507348685.699643392","description":"EOF","file":"external/grpc/src/core/lib/iomgr/tcp_posix.c","file_line":235,"grpc_status":14}

Honestly not sure how to solve other than retry the job.

Hi, i'm getting this error on PubSub consumer. I manage to get a "not so pretty" workaround.
using a policy like this that replicates code for deadline_exceeded on google.cloud.pubsub_v1.subscriber.policy.thread.Policy.on_exception.
`
from google.cloud.pubsub_v1.subscriber.policy.thread import Policy
import grpc
class UnavailableHackPolicy(Policy):
def on_exception(self, exception):
"""
There is issue on grpc channel that launch an UNAVAILABLE exception now and then. Until
that issue is fixed we need to protect our consumer thread from broke.
https://github.com/GoogleCloudPlatform/google-cloud-python/issues/2683
"""
unavailable = grpc.StatusCode.UNAVAILABLE
if getattr(exception, 'code', lambda: None)() in [unavailable]:
print("¡OrbitalHack! - {}".format(exception))
return
return super(exception)
`
On receive message function i have a code like
subscriber = pubsub.SubscriberClient(policy_class=UnavailableHackPolicy) subscription_path = subscriber.subscription_path(project, subscription_name) subscriber.subscribe(subscription_path, callback=callback, flow_control=flow_control)
Problem is that when the resource it is trully UNAVAILABLE we will be not aware.

I might be getting a similar problem on spanner trying to read ranges with index.  I will need to test if it's my code or not.


Removed calls to no longer available logging function

Github Issue (if applicable): #XXX
Trello Link (if applicable):
Forum Link (if applicable):
Explanation of Bugfix/Feature/Enhancement:
Hi.
This is my first PR, so any feedback is welcomed.
Today I discovered your extension and was trying out pacing feature. It looked great, but when I tried to deemphasize category - nothing happened.
Those are logs from Chrome:
app.youneedabudget.com-1509830371531.log
As it turned out the function ynab.utilities.ConsoleUtilities.logWithColor is no longer accessible.
My commit removes those calls, allowing pacing feature to work.
I don't have any experience with JS, so that might be not a proper solution. In that case I can open an issue.
Recommended Release Notes:

Thanks for the PR.

Thank you for your feedback

Also @jprzepiorski if you'd like I can invite you to our team's Slack. Just send me your email address and I'll invite you.


make sure the depth/elevation level closest to surface is the first r…

…ow in the output file
@Bobfrat

cool, were you able to test the different scenarios?

testing positive depth values now..

@Bobfrat all is working as expected


error: jsonrpc error: Networking or low-level protocol error: Invalid Url: Invalid URL: invalid format

What version are you using?
soroban-cli 0.6.0
What did you do?
./quickstart.sh standalone
./initialize.sh standalone

What did you expect to see?
Success
What did you see instead?
Problem is while wrapping the token
Wrap the Stellar asset
error: jsonrpc error: Networking or low-level protocol error: Invalid Url: Invalid URL: invalid format

If I run all this manually:
soroban lab token wrap --network standalone --identity token-admin --asset "EXT:GDT2NORMZF6S2T4PT4OBJJ43OPD3GPRNTJG3WVVFB356TUHWZQMU6C3U

I get the exact error:
error: jsonrpc error: Networking or low-level protocol error: Invalid Url: Invalid URL: invalid format

This happens when exploring with different network settings.
The initialize.sh script checks if "soroban config network" has a network configuration for "standalone".
However, it does not checks if the configuration has the same settings as the network we are going to use.
I propose that in order to avoid this problem: Either:

Check that the configuration is correct (I don't know how to do it)
Allways add the network to the cli client

I think this issue may have become obsolete after everything was updated per latest soroban Preview8 release, I tried replicating issue with latest commit on main(e885f0eb6f7b0fea61be4f95a4b2c43a2b2a6990):
in one terminal:
soroban-example-dapp$ make build-docker
soroban-example-dapp$ ./quickstart.sh standalone

in second terminal:
soroban-example-dapp$ soroban version
soroban 0.7.0 (75f45cf7d844184514d8662586670a7ae0911ea1)
soroban-env 0.0.15 (cf83838ae8a07a00224f0a5a3500eb7969bac7cf)
soroban-env interface version 32
stellar-xdr 0.0.15 (4655b635c698bb3bbc628bdba456df627c42ee3a)
xdr next (7356dc237ee0db5626561c129fb3fa4beaabbac6)
soroban-example-dapp$ mkdir .soroban
soroban-example-dapp$ ./initialize.sh standalone

Using standalone network
Add the standalone network to cli client
Create the token-admin identity
Fund token-admin account from friendbot
Wrap the Stellar asset
SUCCESS
Token wrapped succesfully with TOKEN_ID: d777567161812381f6150bd3b15839dbd2ebee40cfeefea889074431337c50f1
Build the crowdfund contract
cargo fmt --all
cargo build --target wasm32-unknown-unknown --release
  Downloaded soroban-env-guest v0.0.15
  Downloaded 1 crate (4.9 KB) in 0.40s
   Compiling proc-macro2 v1.0.47
   Compiling unicode-ident v1.0.5
   Compiling quote v1.0.21
   Compiling syn v1.0.105
   Compiling serde_derive v1.0.149
   Compiling serde v1.0.149
   Compiling serde_json v1.0.89
   Compiling ryu v1.0.11
   Compiling itoa v1.0.4
   Compiling autocfg v1.1.0
   Compiling ident_case v1.0.1
   Compiling fnv v1.0.7
   Compiling strsim v0.10.0
   Compiling typenum v1.16.0
   Compiling version_check v0.9.4
   Compiling thiserror v1.0.37
   Compiling either v1.8.0
   Compiling generic-array v0.14.6
   Compiling itertools v0.10.5
   Compiling libc v0.2.138
   Compiling num-traits v0.2.15
   Compiling indexmap v1.9.2
   Compiling num-integer v0.1.45
   Compiling hashbrown v0.12.3
   Compiling prettyplease v0.1.21
   Compiling num-bigint v0.4.3
   Compiling cfg-if v1.0.0
   Compiling static_assertions v1.1.0
   Compiling ethnum v1.3.2
   Compiling base64 v0.13.1
   Compiling cpufeatures v0.2.5
   Compiling wasmparser v0.88.0
   Compiling crypto-common v0.1.6
   Compiling block-buffer v0.10.3
   Compiling digest v0.10.6
   Compiling sha2 v0.10.6
   Compiling darling_core v0.14.2
   Compiling thiserror-impl v1.0.37
   Compiling bytes-lit v0.0.4
   Compiling darling_macro v0.14.2
   Compiling darling v0.14.2
   Compiling serde_with_macros v2.1.0
   Compiling serde_with v2.1.0
   Compiling hex v0.4.3
   Compiling crate-git-revision v0.0.4
   Compiling stellar-xdr v0.0.15
   Compiling soroban-env-common v0.0.15
   Compiling soroban-spec v0.7.0
   Compiling soroban-env-macros v0.0.15
   Compiling soroban-env-guest v0.0.15
   Compiling soroban-sdk-macros v0.7.0
   Compiling soroban-sdk v0.7.0
   Compiling soroban-crowdfund-contract v0.0.0 (/Users/sreuland/dev/soroban-example-dapp/contracts/crowdfund)
    Finished release [optimized] target(s) in 19.68s
cd target/wasm32-unknown-unknown/release/ && \
		for i in *.wasm ; do \
			ls -l "$i"; \
		done
-rwxr-xr-x  1 sreuland  staff  5116 Apr 13 12:56 soroban_crowdfund_contract.wasm
Deploy the crowdfund contract
SUCCESS
SUCCESS
Contract deployed succesfully with ID: 090aa2b0013bec3b4c8979e351a7228667a70566864ea367fc5512b3e244448d
Initialize the crowdfund contract
SUCCESS

Done

I tried using the cli as built in the soroban-preview docker also:
soroban-example-dapp$  docker exec soroban-preview ./initialize.sh standalone

had same success/done result.

Hello @sreuland
I should have close this issue.
This was fixed in https://github.com/stellar/soroban-example-dapp/commit/ce021f7646e5e76439eb915bf7c9bfe953d54032#diff-e6bd26c7c0a9d375dc1979dcdc185178b4e3bbb6c3fe2deed9aab6825a7b959f
The problem here was if

Use ./initialize.sh with standalone in URL_1
Use ./initialize.sh with standalone in URL_2

I fixed this commenting the lines that were checking if soroban-cli had or not a network configuration
#if !(soroban config network ls | grep "$NETWORK" 2>&1 >/dev/null); then
# Always set a net configuration
  echo Add the $NETWORK network to cli client
  soroban config network add "$NETWORK" \
    --rpc-url "$SOROBAN_RPC_URL" \
    --network-passphrase "$SOROBAN_NETWORK_PASSPHRASE"
#fi

Now the network is being configured every time. So always has the correct URL configuration


ruby-modules: improve cross-compilation support

Description of changes
This PR contains fixes for cross-compilation in Ruby infrastructure. In particular,

bundler{App,Env} were using host ruby to execute gen-bin-stubs.rb, same for rsync if copyGemFiles was set.
buildRubyGem output contained Ruby-generated binstubs that referenced ruby from nativeBuildInputs.

For example,
nix build --impure --expr 'let
  pkgs = import ./. {
    localSystem.system = "aarch64-linux";
    crossSystem.config = "x86_64-unknown-linux-gnu";
  };
in
pkgs.doing'

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

I’m really confused here, is this PR somehow blacklisted? Is Ruby ecosystem so dead that we don’t review changes anymore (e.g. #258705 also took a long time to merge)? Am I the only one actually using it (given that nobody complained about that issue before)? Do I have to sell my soul to the devil to get this PR reviewed? It’s been 6 months (that’s a NixOS full release cycle) with zero feedback from maintainers and requested reviewers. 😢

@tie Hello!
Sorry for the late reply, and thank you for your work on improving cross-compilation support for Ruby packages :smile:
Your changes looks good, but unfortunately I don't have a computer powerful enough to test your changes (cross-compilation + ~2500 rebuilds) and check that everything's OK on my end.
As your PR targets the staging branch, I think we can merge and check that the builds are OK on Hydra during the next staging-next cycle?

Thank you, yes, that sounds good.

@ofborg build pkgsCross.gnu64.bundler

I’m not really sure if puppet-bolt is a good test case without #316023.

Those changes are pretty simple and just correct that we use the correct binaries in shebangs, nothing compiler/linker related. I think we can safely merge this in the next days.

Bisect says 30971173aba3105b42b9cc7976f1c6c9e018b56c ruby-modules: improve cross-compilation support broek weechat build in staging:
$ nix build --no-link -f. weechat -L
...
weechat> [ 53%] Built target doc-quickstart-pl
weechat> [ 53%] Built target doc-quickstart-ru
weechat> No such file or directory - /nix/store/m15q42klamlbf7czyk1bscjfnwsjr2ay-ruby3.1-pygments.rb-2.4.0/lib/ruby/gems/3.1.0/gems/pygments.rb-2.4.0/lib/pygments/mentos.py
weechat>   Use --trace to show backtrace

Probably due to unpatched shebang in the store:
$ head -n1 /nix/store/m15q42klamlbf7czyk1bscjfnwsjr2ay-ruby3.1-pygments.rb-2.4.0/lib/ruby/gems/3.1.0/gems/pygments.rb-2.4.0/lib/pygments/mentos.py
#!/usr/bin/env python3


file extension not recognized if "file.1.zip"

Had the following interaction:
$ tzar extract thetvdb_<IP_ADDRESS>.zip .
No command found for that file extension.
$ mv thetvdb_<IP_ADDRESS>.zip thetvdb_6000.zip
$ tzar extract thetvdb_6000.zip .
Running: unzip thetvdb_6000.zip -d .

Hey, thanks for the heads up. I had a hunch that I'd have problems with multiple suffixes.
Fixed here: https://github.com/DanielVZ96/tzar/commit/282cdfaf00646c896a53a7f039c06191dd12ab00


Update version for insiders

Codecov Report

Merging #15138 (956e81e) into main (bcf2bdb) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##            main   #15138   +/-   ##
======================================
  Coverage     65%      65%
======================================
  Files        561      561
  Lines      26516    26516
  Branches    3797     3797
======================================
  Hits       17262    17262
  Misses      8554     8554
  Partials     700      700

Codecov Report

Merging #15138 (956e81e) into main (bcf2bdb) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##            main   #15138   +/-   ##
======================================
  Coverage     65%      65%
======================================
  Files        561      561
  Lines      26516    26516
  Branches    3797     3797
======================================
  Hits       17262    17262
  Misses      8554     8554
  Partials     700      700


QH-139 Added match description to ELO graph tooltip.

This is awesome dude, Recent Games is obsolete now


Silence harmless warning

Description of change
Firefox warnExpected color but found ‘0’. to create Text instances.
Because, run context.shadowColor = '0' in updateText(), but it should be css color, '0' is not valid css color.
I silenced it.
Pre-Merge Checklist

[x] Lint process passed (npm run lint)
[x] Tests passed (npm run test)

Codecov Report

Merging #7042 (8e15160) into dev (5dd1b37) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               dev     #7042   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           17        17
  Lines          704       704
=========================================
  Hits           704       704

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5dd1b37...8e15160. Read the comment docs.

Thank you @ayamada!


create symfony project in cloned repository

I have cloned the repository and then tried to create the symfony project in the same folder....

InvalidArgumentException
1/should I create the symfony project in another folder?
2/should I clone the repository after creating the symfony project?

Go into the small-data directory before generating the project. This should create a subfolder which is also called small-data.

Thanks Pieter !


Handling ALL chrome://settings with Puppeteer

Since page.goto(chrome://settings) doesn't work (navigate method requires a scheme), how can we modify chrome://settings?Specifically, I want to allow sites to play protected content via chrome://settings/content/protectedContent
Short answer: we can use flags
Long answer: not all chrome://settings are handled by flags; hence, certain settings must be modified manually BUT puppeteer doesn't allow manual browsing to chrome://settings
I've already tried asking on SO but it looks like it's impossible to handle all chrome://settings through Puppeteer..if it's true and I'm not wrong,please take this as a feature request.

same feature I need as well

I need to navigate to chrome://newtab, but I haven't found a way to use headless: false together

Did anyone manage to get this right?


feat: create new b2b actor from integration event

Description
Create new b2b actors when market participant raise 'ActorActivated' integration event.

[ ] new integration event command mapper for event
[ ] new command for a new b2b actor
[ ] new command handle which persist the new actor

Following PR's:

Refactor Actor table

IdentificationNumber => ActorNumber
B2CId => ExternalActorId

Rename our integration event subscription from sbtsub-edi-balance-fixing-completed
if needed, Ensure we correctly use actor

References
https://app.zenhub.com/workspaces/mosaic-60a6105157304f00119be86e/issues/gh/energinet-datahub/team-phoenix/86

Codecov Report

Merging #581 (529b0dc) into main (21978a1) will decrease coverage by 37.20%.
Report is 250 commits behind head on main.
The diff coverage is 18.44%.

@@             Coverage Diff             @@
##             main     #581       +/-   ##
===========================================
- Coverage   83.07%   45.88%   -37.20%
===========================================
  Files         456      293      -163
  Lines       10418     5745     -4673
===========================================
- Hits         8655     2636     -6019
- Misses       1438     3018     +1580
+ Partials      325       91      -234

Files
Coverage Δ

source/Application/Actors/CreateActorHandler.cs
0.00% <ø> (-85.72%)
:arrow_down:

...tion/Configuration/Authentication/Authenticated.cs
0.00% <ø> (-100.00%)
:arrow_down:

...n/Configuration/Authentication/NotAuthenticated.cs
0.00% <ø> (-100.00%)
:arrow_down:

...n/Configuration/Commands/CommandSchedulerFacade.cs
0.00% <ø> (-100.00%)
:arrow_down:

...Configuration/Commands/Commands/InternalCommand.cs
0.00% <ø> (-100.00%)
:arrow_down:

...e/Application/Configuration/Queries/QueryResult.cs
0.00% <ø> (ø)

...lication/Configuration/TimeEvents/ADayHasPassed.cs
0.00% <ø> (-100.00%)
:arrow_down:

...Configuration/TimeEvents/TenSecondsHasHasPassed.cs
0.00% <ø> (-75.00%)
:arrow_down:

...tgoingMessages/Common/OutgoingMessageExtensions.cs
0.00% <ø> (ø)

...ion/OutgoingMessages/Common/Xml/DocumentDetails.cs
100.00% <ø> (ø)

... and 41 more

... and 453 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Added e2e tests for every backend

This PR should add e2e tests for every backend.

These changes have been published! View these changes here.

I don't know how to fix the conflict on tutorial_steps. I will create a new PR


"What's new in Wagtail link" in the admin site does not go where it should

Issue Summary
In the admin site, I click on "Help" -> "What's new in Wagtail".
The link is https://guide.wagtail.org/en-6.1.x/releases/new-in-wagtail-6-1/ that redirects to https://guide.wagtail.org/en-latest/.
Steps to Reproduce

Start a new project with wagtail start myproject
cd myproject
Run ./manage.py migrate
Create a user ./manage.py createsuperuser
Run ./manage.py runserver
Go to http://localhost:8000/admin/.
Navigate  "Help" -> "What's new in Wagtail"

It takes me to https://guide.wagtail.org/en-latest/ (link itself is https://guide.wagtail.org/en-6.1.x/releases/new-in-wagtail-6-1/) which is not the page that I should be taken to.
Technical details

Python version: 3.11.9
Django version: 4.2.13
Wagtail version: 6.1.2
Browser version: Firefox 126

Working on this
Not sure if this is a problem on https://guide.wagtail.org/ or the Wagtail link is incorrect, so I can't say what's needed.

Hey, @tm-kn I'm new to wagtail, if this issue is open for contribution, I would like to take it. If you agree !!

meanwhile i will try to reproduce this

@angad-singhh I think this can only be fixed by someone who has admin access to the guide.wagtail.org site.
@thibaudcolas, please can you investigate?

The link is set here:
https://github.com/wagtail/wagtail/blob/747d70e0656b86e3e8c8d123ecae82fa61cd1438/wagtail/templatetags/wagtailcore_tags.py#L99-L104
Which means it's https://guide.wagtail.org/en-6.1.x/releases/new-in-wagtail-6-1/ (note the final slash), but the guide website still uses en-latest for 6.1 (the en-6.1.x variant isn't going to be made until a newer version is out i.e. 6.2.x). The page actually exists at https://guide.wagtail.org/en-latest/releases/new-in-wagtail-6-1/.
On the guide website, I see that we have a redirect for this, but the source URL is set to https://guide.wagtail.org/en-6.1.x/releases/new-in-wagtail-6-1 (without the slash). You can see that this link correctly redirects to https://guide.wagtail.org/en-latest/releases/new-in-wagtail-6-1/.
But we can't update the redirect's source URL to end with a slash due to how Wagtail's redirects work:
https://github.com/wagtail/wagtail/blob/a81cabce058236696e11867e260a771b99417a5e/wagtail/contrib/redirects/models.py#L148-L154

The logic to use the version number in the link was added in #11182 but I see that it was also in 6.0, so I'm curious how we handled this for 6.0 (if we did at all). Do you know @thibaudcolas?

For now I’ve created the v6.2 version of the site in the CMS so the link works without a redirect. Will spend more time investigating later in the release cycle.

This looks like it's still an issue in 6.3, had a client raise it today. "What's new" link in the help menu links to https://guide.wagtail.org/en-6.3.x/releases/new-in-wagtail-6-3/, which says "Draft". https://guide.wagtail.org/en-latest/releases/new-in-wagtail-6-3/ appears to have the correct content.

Thanks for the report @jams2, I've updated the page.
To prevent this in the future, we need to ensure when an A.B release happens, the page at https://guide.wagtail.org/en-A.B.x/releases/new-in-wagtail-A-B/ must be available and showing the right content. What this entails:

Adding A.B.x to WAGTAIL_GUIDE_VERSIONS in the guide website (e.g. https://github.com/wagtail/guide/commit/b9476248d5db4a4d760d3574f5db25638719c44c).
Creating a new "locale" on the guide website for A.B.x from the latest version.
Creating a new page under https://guide.wagtail.org/en-latest/releases/ for the release, "New in Wagtail A.B"
Translate the new page to the en-A.B.x locale.
Ensure both https://guide.wagtail.org/en-latest/releases/new-in-wagtail-A-B/ and https://guide.wagtail.org/en-A.B.x/releases/new-in-wagtail-A-B/ are up to date.

Alternatively, we can skip step 1, 2, and 4 by changing the following:
https://github.com/wagtail/wagtail/blob/9889bddcb8823369f7a26c6b6f4a3eb6784d5985/wagtail/templatetags/wagtailcore_tags.py#L103-L104
to:
     if release == "final":
-        return f"https://guide.wagtail.org/en-{major}.{minor}.x/releases/new-in-wagtail-{major}-{minor}/"
+        return f"https://guide.wagtail.org/en-latest/releases/new-in-wagtail-{major}-{minor}/"

which would avoid the issue we had for 6.3. The problem is that this approach would land the user on the "latest" version of the guide, so if they navigated to other pages they might see content that is not applicable to their Wagtail installation.


kom/update-readme-file Fix wrong readme repo names

Fix wrong repository names in readme file and removed travis.
Necessity

[ ] Has the problem that is being solved here been clearly explained?
[ ] If applicable, have various options for solving this problem been considered?
[ ] For core PRs, does this need to be in core, or could it be in an extension?
[ ] Are we willing to maintain this for years / potentially forever?

Confirmed

[ ] Frontend changes: tested on a local Flarum installation.
[ ] Backend changes: tests are green (run composer test).
[ ] Core developer confirmed locally this works as intended.
[ ] Tests have been added, or are not appropriate here.

Required changes:

[ ] Related documentation PR: (Remove if irrelevant)
[ ] Related core extension PRs: (Remove if irrelevant)

These should still be links to flarum/core, as that's our main code repo. flarum/flarum is purely a project template and Flarum can be used without it.

Sure I understand that. But when you see the badges in a repository you expect it to be the data from the actively selected repository and not from another one (even if it is the central one in that case).

Thanks for the PR!
@davwheat 's correct 👼🏼 the badges should point to the core repository, this is only a skeleton and we'd rather have data from the main framework.

Given the previous stated reasons and information provided I'm going to go ahead and close this PR.
We do thank you for your eagerness to help and interest in Flarum, to find all the ways you can help please read https://docs.flarum.org/#help-the-flarum-project


RuntimeError: Trying to backward through the graph a second time, but the buffers have already been freed

When using the PyTorch DeepExplainer on a network comprising several sequential Conv1d and BatchNorm1d layers, shap_values throws the above error:
File "train.py", line 423, in <module>
    shap_values = explainer.shap_values(to_explain)
  File "/users/florianst/.local/lib/python3.6/site-packages/shap/explainers/deep/__init__.py", line 119, in shap_values
    return self.explainer.shap_values(X, ranked_outputs, output_rank_order)
  File "/users/florianst/.local/lib/python3.6/site-packages/shap/explainers/deep/deep_pytorch.py", line 161, in shap_values
    sample_phis = self.gradient(feature_ind, joint_x)
  File "/users/florianst/.local/lib/python3.6/site-packages/shap/explainers/deep/deep_pytorch.py", line 106, in gradient
    grads = [torch.autograd.grad(selected, x)[0].cpu().numpy() for x in X]
  File "/users/florianst/.local/lib/python3.6/site-packages/shap/explainers/deep/deep_pytorch.py", line 106, in <listcomp>
    grads = [torch.autograd.grad(selected, x)[0].cpu().numpy() for x in X]
  File "/users/florianst/.local/lib/python3.6/site-packages/torch/autograd/__init__.py", line 145, in grad
    inputs, allow_unused)
RuntimeError: Trying to backward through the graph a second time, but the buffers have already been freed. Specify retain_graph=True when calling backward the first time.

Hi @florianst , this was fixed in https://github.com/slundberg/shap/pull/684 (for the DeepExplainer) and https://github.com/slundberg/shap/pull/705 (for the GradientExplainer).
These haven't been released yet, but using the master branch of shap should prevent these errors from popping up.

Reinstalling shap from the master branch solved this, thanks!


Select data from specific sensor?

Hi, congratulations for the amazing work!!
I was wondering if would be possible to filter the dataset according to a specific sensor. For example: according to the paper, the tracks were collected using 6 cameras and 3 LiDAR sensors, right? Would it be possible to select only the data captured by one of those cameras and one of those LiDAR sensors?
I noticed that the tracks.json files indicate the source type of that data. For example, considering the track.json file of a VRU track, we have:

source_type: Which sensor(s) are responsible for current object detection, 0 => Lidar, 1 => lidar+camera, 2 => camera

However, would it be possible to select, for example, a specific camera? Let's say, camera 1, camera 2, camera 3, etc.
Thank you in advance.

Thank you for the quick response.
Yes, I can provide more details about my application. Here it is: my research group and I are developing a VRU-safety-based ecosystem for smart cities — i.e., a system that detects VRUs and warns nearby autonomous vehicles to prevent collisions. As we are at the beginning of the project, we want to start with a simple and limited scenario: an urban intersection equipped with just a few infrastructure sensors (one camera and one LiDAR). That's why I would like to filter the data to gather information captured by just one of the cameras.
I am interested in the IMPTC dataset because, besides the bounding boxes for VRUs and vehicles, it also provides VRU trajectories — which is a future focus of our research — as well as various contextual information (e.g., weather and segmentation map data).

Thank you for your help.
If both cameras monitor a single corner of the intersection, then yes, this would help me a lot! How could I filter the data to select this reduced set? Would it be by using the source_type attribute - which I mentioned earlier? Or it must be another way?

The official uploaded data does not allow for filtering for this. The 'source_type' attribute only describes which sensor modalities contribute to the current 3D object detection; it does not distinguish between specific camera or lidar sensors.
We are internally checking the effort to extend the attribute and context in the way of your request, but this needs a little more time.
I can give you an update soon.

Understood.
Thank you very much.

Hi Matheus,
Reproducing the dataset and including the requested data is a fairly complex and time-consuming process. Therefore, we could not do this anymore. The dataset is a context-enriched dataset for trajectory prediction starting at the trajectory level. Your request is more related to the sensor data and object detection level.

Hi, @mh-kav-institute.
I see.
But that's ok, no problems. Thank you for your help.


Ppc64le Support

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

I think it is unlikely the project will support ppc64le officially. As per prior discussion at https://github.com/search?q=repo%3Aenvoyproxy%2Fenvoy+Ppc64le+ci&type=issues without a CI environment it isn't maintainable. Introducing a new and different Lua dependency is really not ideal particularly after we finally removed Moonjit


App greys out

related: #96
Many users have noticed that the app greys out. We're not entirely clear why it happens.
One thing we should try is the keep-alive setting for the Shiny server, see

https://tickets.dominodatalab.com/hc/en-us/articles/14794822159124-Shiny-App-shows-a-gray-screen-after-sometime-or-timeouts
https://docs.posit.co/shiny-server/#application-timeouts

Might become low-priority if we can enable cookies to eliminate re-logging in...

@dtenenba I think you were taking a look at this. Any progress?

It would be good if we could assemble some of the reports of this issue and see if we have enough information to reproduce this consistently.
In the meantime we could look into the timeouts thing.

Try reproducing with multiple users at once

Can't seem to reproduce. @tefirman to add tag later.


Python 3.9 support

sans specifies a maximum python version below 3.9. Could this be bumped up or removed, so that the library can be used with the latest python version?

I'll run a few tests tomorrow to see about bumping dependencies / requirements
for now pip install has both  --python-version and --ignore-requires-python CLI flags you can use

Partially resolved with https://github.com/Zephyrkul/sans/commit/79dd00ad238b2a58f6730d8266cfb7ce0f279f9b (3.10+ wasn't supported), fully resolved with https://github.com/Zephyrkul/sans/commit/8cbc43f434f443df58ff308ad92c893191ccb1f9.
Closing.


⚠ Homepage (omg.lol) has degraded performance

In 127b2c3, Homepage (omg.lol) (https://8bit.lol/) experienced degraded performance:

HTTP code: 0
Response time: 0 ms

Resolved: Homepage (omg.lol) performance has improved in 7ed82d9 after 1 hour, 55 minutes.


Move the TSModelCausalLMForOPTLLM path

Type of Change
due to codellama also use ipex.optimize_transformers, the torchscript int8 loading class needed for code evaluation repo used, so move the class to this path.
Description
detail description
JIRA ticket: xxx
Expected Behavior & Potential Risk
the expected behavior that triggered by this PR
How has this PR been tested?
how to reproduce the test (including hardware information)
Dependency Change?
any library dependency introduced or removed

PR is ready to merge, this PR just move the class path, but the coverage decrease -0.131%. @VincyZhang


a question for function getUVError

The following function is defined in file detector/mapper.py. Why u and v are both equal to 0.05 * bbox_height?
def getUVError(box):
    u = 0.05*box[3]
    v = 0.05*box[3]
    if u>13:
        u = 13
    elif u<2:
        u = 2
    if v>10:
        v = 10
    elif v<2:
        v = 2
    return u,v

It appears to be an oversight in the implementation. In practice, using either bbox_height or bbox_width should yield similar results.


Post merge adjustments, release prep

@coderanger Thoughts?

:+1: Looks good!

flag provided but not defined: -f :( not backwards compatible.

Looks like build -f was added in https://github.com/docker/docker/blob/master/CHANGELOG.md#150-2015-02-10.

Current is 1.7.1, I would say 1.5.0 is not an unreasonable expectation.

I agree, I haven't had the need to upgrade. I will update the CHANGELOG.


fix(doc): Fix markdown for API design doc

/check-enforcer evaluate

@pakrym Does the check-enforcer require a code-owner approval (even for merging into feature branches)? The tool has been stuck "in-progress", so I am trying to figure out what checks are missing for us.

Please ping the "Engineering System" channel on Teams, they own the check-enforcer.

check-enforcer is not turning green because there are no other ci checks setup and running for your changes. Given this is only a md file change we can ignore this but we should get a ci job setup for changes under iot when code starts to change.


PCRE_CONFIG_PARENS_LIMIT is an unsigned long

See #9 for details. This was detected by -fstack-protector-strong, thanks stack smashing protection!

Thanks!


This window is not supported for the selected project

Are you sure the Data Sources is supported by Windows Forms App? "This window is not supported for the selected project" is showing in Data Sources window.

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

ID: d0568679-0027-5e02-88f6-2e27ec1aa733
Version Independent ID: b86cf53c-2b52-7bab-c45e-b6a935194d18
Content: Create a Windows Form to search data - Visual Studio
Content Source: docs/data-tools/create-a-windows-form-to-search-data.md
Product: visual-studio-windows
Technology: vs-data-tools
GitHub Login: @ghogen
Microsoft Alias: ghogen

@tazhanzhou The article should say, as other pages do, that this scenario is only supported for .NET Framework WIndows Forms projects (project template name "Windows Forms App (.NET Framework)" not "Windows Forms App". If you are using .NET Core Windows Forms (e.g. 3.1 or 5), then it is not supported. I will update the article to make this limitation clear.

@ghogen -- Gordon, thank you for updating this documentation.
@tazhanzhou -- Ta, this issue will be auto-closed when Gordon's update is ready for publish.  This documentation update should be live by tomorrow.


PSP Removal

It seems the current charm expects a manual intervention if RBAC is enabled. The RBAC manifest is deployed in the integration tests here and resolved.


SVG image as Logo

Hi,
I have logo uri with file extension .svg. Google Pass link is generated but it is giving error when I open link in browser.
My logo object for one of the google pass request is mentioned below. I am using .svg file link instead of .png or .jpg file.
Can we use .svg extension file as a logo? If yes please provide solution here.
"Logo": {
"SourceUri": {
"Uri": "https:/xxxxx/imagename.svg",
"Description": "Test Description"
}
}

Hello,
I apologize, but this repository is being archived and replaced by google-pay/wallet-samples going forward. If you still have a question, please open a new issue in that repository.
Thank you!


Log the Ids of items being indexed

This adds some more specific logging to make it clearer what items are being added to the index to assist in troubleshooting reindex issues.
We could implement toString() for each of these classes, but this is a simple enough change.

Looks good.


Added New Methods

-Added support for .webm downloads
-Added, Convert YT Video to mp3

To clarify,
Advanced features may include support for

Download small sections of the video/music
Using sponsorblock api to download video/music
Download whole play lists of music and videos
etc.


Bug: OpenSauced not CamelCased on User Profile

Describe the bug
Currently, OpenSauced is all lowercase on the "Invite to OpenSauced" button on the user profile.

Steps to reproduce

Go to https://app.opensauced.pizza/u/AlonsoGuevara
See it twice on the page of a user not part of OpenSauced.

Please assign me

is this issue still open?

@shubham-singh-748  Yes I am working on it

@BekahHW
I think you mean PascelCase.
https://miro.medium.com/v2/resize:fit:1400/1*PSDlLqeuDgeqClF-LLqPPw.png


This codebase is no longer working

The sample project no longer works. It would be nice to get a workable example that will operate with the current released version of Blazor WebAssembly. Though, I must admit at this point, I don't feel Microsoft has a good handle on this solution.

@SpireTechnical
It works for me with Core v5.04. I made some minor changes to adapt it to my application and to the latest Blazor hosted Webassembly template.
The only main change I made is rather than using
[Authorize]
[ApiController]
I used:
[Authorize(AuthenticationSchemes = JwtBearerDefaults.AuthenticationScheme)]
[ApiController]
If you have a specific error or issue let me know.


Update doc to add whitelist ips info

PTAL

OK. Good suggestion.

PTAL

:+1:

Nice one @stuartmoore1023 👍


[WIP] Swipe to action v1

*Started on top of Kyles Skeleton commit
Adds support for simple swipe to actions
why simple?

no custom views
only one action

What's going on?
Created a SwipeController. The SwipeController manages the gesture of the cell itself and the state of the swipe. It helps calculate new states and fire the correct action. When actions are sent into a cell instance, a SwipeController and swipe view are created.
SwipeView - a simple view that mimics the action view from UITableViewCell.
The movement is handled with a UIPanGestureRecognizer added to the cell itself.
-- video

FYI, attached GIF does not seem to be loading.

I was thinking about the "only one action" bit – I think you'll need multiple, at least for GA, because comp & void requires two actions. Right? cc @connorcimowsky

I was thinking about the "only one action" bit – I think you'll need multiple, at least for GA, because comp & void requires two actions. Right? cc @connorcimowsky

Chatted with Connor offline, he said there only needs to be one

If the plan for a more complete implementation is to support custom UIView / Blueprint Action appearances, the underlying swipe view will need to communicate a few things to the ContentView that holds the pan gesture.

How many actions there are
Preferred size for each view

The ContentView's locked position (see attache screenshot in reminders) is calculated based on these two properties.
If the complete implementation returns one UIView, containing all actions views, the apply function would need to bind the action to the respective action view.

Overall looks good – left some notes to clean up in a follow up.

Fwiw, I'm now noticing this auto layout issue in the console when scrolling the main demo app list:
2020-05-02 14:24:20.015508-0700 Demo[91896:4120979] [LayoutConstraints] Unable to simultaneously satisfy constraints.
	Probably at least one of the constraints in the following list is one you don't want.
	Try this:
		(1) look at each constraint and try to figure out which you don't expect;
		(2) find the code that added the unwanted constraint or constraints and fix it.
(
    "<NSLayoutConstraint:0x600002b05270 'UISV-canvas-connection' UILayoutGuide:0x600003134620'UIViewLayoutMarginsGuide'.leading <= UILabel:0x7faeaad10b30'Delete'.leading   (active)>",
    "<NSLayoutConstraint:0x600002b052c0 'UISV-canvas-connection' UILayoutGuide:0x600003134620'UIViewLayoutMarginsGuide'.centerX == UILabel:0x7faeaad10b30'Delete'.centerX   (active)>",
    "<NSLayoutConstraint:0x600002b04e60 'UIView-Encapsulated-Layout-Width' UIStackView:0x7faeaad08740.width == 0   (active)>",
    "<NSLayoutConstraint:0x600002b04fa0 'UIView-leftMargin-guide-constraint' H:|-(16)-[UILayoutGuide:0x600003134620'UIViewLayoutMarginsGuide'](LTR)   (active, names: '|':UIStackView:0x7faeaad08740 )>",
    "<NSLayoutConstraint:0x600002b05040 'UIView-rightMargin-guide-constraint' H:[UILayoutGuide:0x600003134620'UIViewLayoutMarginsGuide']-(16)-|(LTR)   (active, names: '|':UIStackView:0x7faeaad08740 )>"
)

Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x600002b05270 'UISV-canvas-connection' UILayoutGuide:0x600003134620'UIViewLayoutMarginsGuide'.leading <= UILabel:0x7faeaad10b30'Delete'.leading   (active)>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful.

The Delete in there leads me to believe it's related to this.

Hmm might be because of the stack view, those use AL internally. My refactor completely changes how the buttons are laid out (to support multiple buttons) so it should fix this. I’ll double check, but I don’t think we need to bother looking into it

Cool, makes sense! Sorry for the weekend ping, was working on another side project that means I need to do some list layout refactoring, and ran into it so wanted to post.

No worries! Wasn’t really even a ping, just happened to be browsing my email 😄

On May 2, 2020, at 2:44 PM, Kyle Van Essen<EMAIL_ADDRESS>wrote:

Cool, makes sense! Sorry for the weekend ping, was working on another side project that means I need to do some list layout refactoring, and ran into it so wanted to post.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.


[FLINK-32271] Report RECOMMENDED_PARALLELISM as an autoscaler metric V2

What is the purpose of the change
It is beneficial to report the recommended parallelism and overlay it with the current parallelism on the same chart when auto scaler is running in advisor mode.
Brief change log

Added a new RECOMMENDED_PARALLELISM entry to ScalingMetric
And the latest recommended parallelisms are now being reported as evaluated scaling metric
Recommended parallelisms follow the logic below:

RECOMMENDED_PARALLELISM will be set to PARALLELISM while the metric window is filling up
RECOMMENDED_PARALLELISM may change according to the evaluated scaling metrics
PARALLELISM will be set to RECOMMENDED_PARALLELISM after scaling if scaling is enabled
RECOMMENDED_PARALLELISM will set to null during a scaling operation, while metric collection is not possible
RECOMMENDED_PARALLELISM will be set again to the changed PARALLELISM while the metric window is filling up

Verifying this change

Added unit test for recommended parallelisms
Manual by checking the actual metrics being reported

TODO

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): ( no)
The public API, i.e., is any changes to the CustomResourceDescriptors: ( no)
Core observer or reconciler logic that is regularly executed: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (docs)

@mxm @gyfora this is my second attempt on adding the RECOMMENDED_PARALLELISM let me know what you think


Unsolved Reference When Editing Flutter Plugin Androd Native Code

Steps to reproduce

create flutter plugin project
flutter create --template=plugin --platforms=android example_flutter_plugin
open native code in Android studio
${home}/example_flutter_plugin/android/build.gradle

Actual results
Unsolved reference FlutterPlugin, io, etc

Logs
I alread follow step in this section https://docs.flutter.dev/packages-and-plugins/developing-packages#step-2b-add-android-platform-code-kt-java, but still I got error plugin
Flutter Doctor output
`[✓] Flutter (Channel stable, 3.19.5, on macOS 14.4.1 23E224 darwin-arm64, locale en-ID)
• Flutter version 3.19.5 on channel stable at /Users/taufikfadlurahmanfajari/fvm/versions/3.19.5
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 300451adae (5 weeks ago), 2024-03-27 21:54:07 -0500
• Engine revision e76c956498
• Dart version 3.3.3
• DevTools version 2.31.1
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
• Android SDK at /Users/taufikfadlurahmanfajari/Library/Android/sdk
• Platform android-34, build-tools 34.0.0
• Java binary at: /Applications/Android Studio Preview.app/Contents/jbr/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11609105)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 15E204a
• CocoaPods version 1.15.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2023.2)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
[✓] Connected device (4 available)
• SM G973F (mobile)                    • RR8M20LAB5L               • android-arm64  • Android 12 (API 31)
• Taufik Fadlurahman’s iPhone (mobile) • 00008110-00124CA40230A01E • ios            • iOS 17.4.1 21E236
• macOS (desktop)                      • macos                     • darwin-arm64   • macOS 14.4.1 23E224 darwin-arm64
• Chrome (web)                         • chrome                    • web-javascript • Google Chrome 124.0.6367.119
! Error: Browsing on the local area network for Taufik’s iPhone. Ensure the device is unlocked and attached with a cable or associated with the same local area network as this Mac.
The device must be opted into Developer Mode to connect wirelessly. (code -27)
[✓] Network resources
• All expected network resources are available.
`

there is duplicate issue here https://github.com/flutter/flutter/issues/115811, but in my computer, it cannot resolved

Please see https://github.com/flutter/flutter/issues/115811#issuecomment-1323366326. As noted in section 2b of the documentation you linked to, editing the native code of a plugin should be done in the example app project.


chore: add support for multiple protocols

Changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1610  👈 (View in Graphite)
#1609
#1608
#1607
#1606
#1604
#1603
#1602
#1601
#1600
main

How to use the Graphite Merge Queue
Add the label merge-queue to this PR to add it to the merge queue.
You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has required the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.


[603][620]Fix java-kotlin conversion issue

Overview
This PR addresses Java-Kotlin conversion issues(#603, #620) with refactoring and adds a unit test.
Issues

https://github.com/permissions-dispatcher/PermissionsDispatcher/issues/603
https://github.com/permissions-dispatcher/PermissionsDispatcher/issues/620

Let me merge.


Weird stack behavior. Scene disappears right after pushing it, but then reappears after next push.

Version
Tell us which versions you are using:
"^4.0.0-beta.31"

Code:
            <Scene
              key="referral"
              type="replace"
              component={ReferralPage}
              title="Free Points"
              titleStyle={styles.title}
              renderLeftButton={() => <View />}
              onLeft={() => {}}
              renderRightButton={customRightCloseButton}
              rightButtonStyle={styles.navIconButton}
              navigationBarStyle={styles.mainNavigationBar}
              back={false}
            />

const customRightCloseButton = ({ rightCallback }) => (
  <TouchableOpacity onPress={Actions.pop} style={styles.closeButton}>
    <IonIcon name="ios-close" size={30} color="white" />
  </TouchableOpacity>
)

Expected behaviour
Screen opens first time and stays open until close pressed
Actual behaviour
Screen opens, closes, and then when I reopen, both come up and the stack is messed up so Actions.pop() does nothing.

Probably navigation hierarchy is wrong. Please refer to Example project - you need to use LightboxNavigator for popups.


reduce netlify build times for PRs

The only branch that needs the "full production build" (the docs.postbuild script in package-scripts.js) is the mochajs.org branch, which is what mochajs.org is built from.  This script takes up most of the build time, and we want to reduce the build minutes on netlify, because we're using too many.
I think it's relatively safe to disable.  It's been a source of flake, and the problems are usually (but not always) corrected by a cache clear.
In its place, we'd need something to essentially just rename docs/_site to docs/_dist, as docs/_dist is ultimately what gets deployed.
What do we think? @mochajs/core @Munter

Some of the production build creates significant performance improvements for our visitors, so I wouldn't want to disable them for the master branch. We could probably skip them for branches that don't work on the build system

I've tried to optimize build time at #4264 , but I couldn't reduce time effectively.
I think we can run Netlify builds when the only PR has changes under docs.

@outsideris can #4264 be closed?
this should have been closed via #4358


Add option for using the bun js runtime in SSR

Addresses #548.
This adds a --runtime option which  can either be node or bun. The default is node.

Hey sweet, nice addition, thanks! 🤙


heading scaling

Hello,
the headline does not scale on mobile devices.

Hi,
Thank you for reporting this! This problem comes from the original HTML template. I will fix it in the next release.

thanks, that works great.


⚠ Samsung has degraded performance

In 9970066, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2192 ms

Resolved: Samsung performance has improved in 6baca77.


Don't prefix talk in breadcrumbs with 'Talk:'

Looks weird when it says "Home / Talks / Talk: Leveraging Laravel". I think it's intuitive that everything under "Talks /" is going to be a talk title :)

Haha yah I think that's back from when we had versions. Good catch.


emoji: Fix keypad emoji, overriding broken codes from server's list.

The Zulip emoji database has codepoint sequences for these emoji that
aren't actually valid emoji sequences according to the Unicode spec.
Some browsers accept the forms we've been using, but others don't.
In particular, newer Chrome versions don't, since about 2019.
We discussed fixing the server's data here in 2019:
https://chat.zulip.org/#narrow/stream/3-backend/topic/unicode.20emojis/near/758828
but never did, and then didn't come back to this.  Hopefully it
will get fixed sometime, but first let's just work around it here.
Fixes: #3517

Diagnosing this issue today caused me to look back at an earlier related report #3395. That one turns out to have a very similar fix, so I've just added that on to this PR:

emoji: Fix :a:, :b:, :o:, :p: to have emoji-style presentation.
This causes them to render (at least on Android) with bigger, colored
glyphs that look a lot like the glyphs we use in the webapp.
Without this, they render with text-style glyphs: transparent letter
on white background, which also means that in a light theme they're
completely invisible.
These are the only emoji we have in this range of letter characters.
There are some others like :ok: that are from neighboring characters
representing multiple letters, but those all seem to be doing fine
already.
Fixes: #3395

Thanks, @gnprice! Merged, after checking these on iOS and the office Android device.


overlay subnet has conflicts in the host while running in host mode

I'm testing an overlay network in docker 1.10.0-rc1 that was not working in 1.9.1 (I'm running kernel 13.3)
I run the following:
docker network create --driver overlay es-bridge

I confirm the creation of the network:
docker network ls
NETWORK ID          NAME                DRIVER
df89455cbc24        bridge              bridge
94df4ba9ba03        none                null
1c4b0953f828        host                host
4f0069ac54d2        es-bridge           overlay

Then add a busybox container to it:
docker run -itd --net=es-bridge busybox
3ab7ba1969c4084c9d0f0ed23525b05573405a21188fac67f890d6bdcc506807
docker: Error response from daemon: subnet sandbox join failed for "<IP_ADDRESS>/24": overlay subnet <IP_ADDRESS>/24 has conflicts in the host while running in host mode.

There are no other containers running on this node, and I've run the same container on several nodes and get the same result
docker version
Client:
 Version:      1.10.0-rc1
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   677c593
 Built:        Fri Jan 15 18:17:17 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.10.0-rc1
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   677c593
 Built:        Fri Jan 15 18:17:17 2016
 OS/Arch:      linux/amd64

docker info
Containers: 3
 Running: 0
 Paused: 0
 Stopped: 3
Images: 88
Server Version: 1.10.0-rc1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 104
 Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: overlay bridge null host
Kernel Version: 3.13.0-32-generic
Operating System: Ubuntu 14.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 31.41 GiB
Name: c2b1s2.tera4.terascope.io
ID: EP32:TWMN:LIX6:5B2E:X3AR:FJAH:OVSG:PMVF:XQVQ:FUQ2:6NKF:HNH6
WARNING: No swap limit support
Cluster store: zk://zk.host:2181
Cluster advertise: IP:2376

@rquinnlv its expected in kernels < 3.16, If there is an existing interface in the host that uses the same subnet allocated for the network.
Can you please use of the --subnet option while creating the overlay network and make sure the subnet that you are using doesnt overlay with any existing subnets in that host or other hosts (kernels < 3.16) that are part of the overlay network ?

@mrjana @thaJeztah we may have to enhance the docs to highlight this point clearly.

@mavenugo thanks, I'll add this to the milestone so that we should try and get our docs right before the release

tried again using a random --subnet parameter and it's working fine, thanks for the response.

thanks @rquinnlv. closing the issue.


Cannot read property 'skipped' of undefined

Hi,
During the build of my project I have this error : ##[error]Cannot read property 'skipped' of undefined
Do you any clue on the problem ?
Thanks.

This problem is almost certainly caused by an XML test report that does not contain any <testcase> elements.
The problematic line of code is here: https://github.com/ScaCap/action-surefire-report/blob/dec13d8b948a999c37d512123d1eb0e2d0629725/utils.js#L39

Discussion on #9 hints that this works on master.

Indeed, using 1.0.3 fixed the problem. Thanks.


swap to https

Hi,  I think there's been a recent change to quandl which requires https rather than http connections.  These simple changes to your code worked for me.  Thanks, Mark.

Does this eliminate anonymous downloading?

Tests failing on nightlies, I'll need to look into that separately though. This PR makes the package functional again. Thanks!

I don't believe so.
On Mon, Jun 29, 2015 at 10:23 PM, milktrader<EMAIL_ADDRESS>wrote:

Does this eliminate anonymous downloading?
—
Reply to this email directly or view it on GitHub
https://github.com/milktrader/Quandl.jl/pull/79#issuecomment-116634639.

It doesn't affect anonymous downloading.


infer_grn error: Error in as(groupings2, "data.frame") :    no method or default for coercing "NULL" to "data.frame"

Hi,
Thanks for this piece of software which looks very exciting. I have some multi-ome data that I would like to try this on and in preparing the scripts, I was using some publicly available data from 10X, but was running into problems early on. After processing my seurat object to have the required RNA and peak assays, I run initiate_grn and find_motifs as instructed on the Pando website, both of which complete.
However, I then move on to the infer_grn step and immediately get an error:
> seurat_object <- infer_grn(
+   seurat_object,
+   peak_to_gene_method = 'Signac',
+   method = 'glm'
+ )
Selecting candidate regulatory regions near genes
Error in as(groupings2, "data.frame") :
  no method or default for coercing "NULL" to "data.frame"

The traceback is as follows:
> traceback()
6: stop(gettextf("no method or default for coercing %s to %s", dQuote(thisClass),
       dQuote(Class)), domain = NA)
5: as(groupings2, "data.frame")
4: Matrix.utils::aggregate.Matrix(x = x, groupings = groups, fun = fun)
3: aggregate_matrix(t(peaks_near_gene), groups = colnames(peaks_near_gene),
       fun = "sum")
2: infer_grn.SeuratPlus(seurat_object, peak_to_gene_method = "Signac",
       method = "glm")
1: infer_grn(seurat_object, peak_to_gene_method = "Signac", method = "glm")

I have checked that I have the latest version of Pando installed.
I saw the previous issue #2 and tried the solution of adding the RNA assay to the peak object, but to no avail.
Is there any clear reason why I may be running into such an error? Many thanks in advance.

Inexplicably it is now working with my real dataonce I follow the advice of #2 by adding the RNA assay to an object with the chromatin data, but it would be good to know why this issue might sometimes happen!


iFrame support?

Hi,
Thanks for a great extension, am I right in assuming it doesn't support requests made from an iFrame?
I don't see them come through when I press record. The parent frames requests get recorded though.
Thanks

Hi @gilesbutler,
Yup, it doesn't support the IFrame requests as of now.

Ok thanks for letting me know @mukuljainx 👍

Are you planning on adding support at any point?

There is no plan as of now I will need to check if the chrome allows an extension to inject code in IFrame or not, if they do this will be picked after planned features for V2.

Ok great, thanks @mukuljainx

I need this


Why only some people are marked?

Why only some people are marked, others in a picture are not marked?

We annotated all the bounding-boxes. But because mask & key-point annotation is a quite time-consuming job, a few instances have no such annotation. (It doesn't affect the evaluation.) Our visualisation code shows instances with full annotations here.

The coco evaluation toolbox can tolerate case like this.
I can't remember precisely but the logic is something like for each gt, you find a prediction that has max iou with it, and consider it as a match.


Added an alphabetical sort button to developer's page.

Did you test this with pagination?

I didn't think to test this with pagination originally, but after moving the sort filter it's working on my end.

All good! this is why we do code reviews :smile:

How would this work with the back button? Maybe we should add the sorting parameter to the url as well.

@kmcnellis I'm on it!!


present common dimensions in a standard order

When I add connection_name as a common dimension, I can get different orderings of common dimensions across controls. Ideally it would always be the same, and would be the order in which I named them in spvars.

When you use tag_dimensions they can also show up in an unexpected order.
Given this setup:
variable "common_dimensions" {
  type        = list(string)
  default     = [ "connection_name", "region" ]
}

variable "tag_dimensions" {
  type        = list(string)
  description = "A list of tags to add as dimensions to each control."
  default     = [ "Name", "Project"]
}

I'm seeing rows like:
Cairo aws_mifflin us-west-2 Linux Test
where:
Cairo is the value of a Project tag
aws_mifflin is a connection name
us-west-2 is (obviously) a region
Linux Test is the value of a Name tag

@judell Are you seeing the same ordering errors when running steampipe check benchmark.ec2 (along with any other benchmarks you are testing in)?
I couldn't reproduce the ordering issue through the steampipe check command, but through steampipe dashboard I consistently had 2-3 controls with the additional dimensions in different orders.
I thought there may be an issue due to the lack of alias, so the connection name info would come under the ?column? column, but even adding an alias of connection_name in the locals definition didn't appear to fix it.


Fix inputs with show/hide password icon

Description

Remove password input wrapper
Create a prepend inner icon for inputs with type password
Fix show/hide icon selection when pressing tab
Fix the order of dialog actions tabindex

Changes
Screencast from 26-06-24 17:10:30.webm
Related Issues

https://github.com/threefoldtech/tfgrid-sdk-ts/issues/3016

Checklist

[ ] Tests included
[x] Build pass
[ ] Documentation
[x] Code format and docstrings
[x] Screenshots/Video attached (needed for UI changes)

@samaradel
PasswordInputWrapper component was created to avoid multiple define of showX variables. however this is not only the case but also to avoid defined v-slot:append-inner over and over.
Also it's not only used in profile manager but also in multiple solution/apps for example k8s and it's currently broken.

I would suggest extend usePasswordInput hook to get a ref from password input itself then use that ref in onMounted to append tabindex="-1" attribute in icon which should fix the issue in the entire app without any breaks.
Also Currently if we click on input then tab it will popup to the manual > Login > input again > the manual > So on...  won't focus any button which definitely not fixing this issue at all

@samaradel This solution is not generic to all password inputs so the issue still presented in a lot of inputs in application


Create new arrays

The _array KEY is useful for aggregating existing registers but I'd like to request functionality to create new arrays without first _adding all the individual registers.

Closed by https://github.com/stm32-rs/svdtools/pull/130


Kubernetes 1.25 support

Greetings,
Any idea when this CSI will support 1.24 or 1.25?
K8s 1.23 will be EoL soon.
Thanks!

@jpuskar Hi, we will add support for 1.25 on our next release (2.2.0)

I am pleased to announce that CSI Driver v2.3.1 is now GA.
What’s new in this release:
NFS-TreeQ is now supported for Kubernetes 1.23-1.25 and for RedHat OpenShift 4.8-4.11
NFS-TreeQ limitations are now optional within the StorageClass file