Auto update always installs in 'C:\Program Files (x86)' even though VS Code was installed in different drive.

VSCode Version: 1.0
OS Version: Windows 10 Pro 64 bit

Due to limited space in my SSD 256GB C: drive I installed VS Code on D: drive instead. But today VS Code informed me there is a new 1.3 version and asked whether I would like to update.... I clicked Yes.
To my surprise, the installer installs the latest version into 'C:\Program Files (x86)' instead of overwriting my current installation folder.
Steps to Reproduce:

Install VSCode 1.0 into D: or E: drive... as long as it is not C: drive.
Run VSCode, and wait for it to offer to update itself to latest version. Click Yes.
The latest version (1.3 as of this writing) will be installed in 'C:\Program Files (x86)' and the old 1.0 version will be left orphaned in D: or E:

This is strange, it should just work. What happens if you install in C:\ but in another folder?

I am not able to find the installer for older versions of vscode... the website always download the latest version... so I could not reproduce this problem for now... right now I am on version 1.3.1.
I guess I will have to wait for newer version to come out before I can test again?
Currently I have VSCode installed in C:\Misc Programs\Microsoft VS Code.

Feel free to try to reproduce with our Insider release. There is a new release every day there.

I installed the Insider release to a different location on my C: drive and when I updated the next day, nothing seemed to install on my Program Files (x86) folder.

 I will close this.

Thanks!


[Package Request]: Input Leap

How can we help?
I would like someone else to build the manifest.
Please read and ensure the following

[x] The installer meets the above requirements

Please provide the following information
Download Page Url: https://github.com/input-leap/input-leap/releases/tag/v3.0.2
Publisher: https://github.com/input-leap
Package Name: InputLeap
Description: Open-source KVM software (successor to Barrier, successor to Synergy)
Package Version: v3.0.2
Installer Url: https://github.com/input-leap/input-leap/releases/download/v3.0.2/InputLeap_3.0.2_windows_qt6.exe

Oh shucks, it's been added since I last looked!  My apologies.
https://github.com/microsoft/winget-pkgs/pull/181393 🥳


Define what is new and released in 7.0 and 7.1.0

Please define what's new and improved in version 7.0 and what was added in 7.1.0
All I managed to find is a topic in google-groups that contains some information about what's new. https://groups.google.com/forum/#!topic/testng-users/elein1RwVTo
Changelog in repository is not user-friendly and doesn't reflect divide changes that were made in 7.1.0 and 7.0
TestNG Version
7.0/7.1.0
Expected behavior
Actual behavior

@KroArtem - There was an email sent to the group explaining what all was added to 7.0.0.
Refer here : https://groups.google.com/forum/#!topic/testng-users/HKujuefBhXA

Changelog in repository is not user-friendly and doesn't reflect divide changes that were made in 7.1.0 and 7.0

Can you please me understand what this means ? The change log clearly lists out all of the github issues that were fixed in every release. What more is being expected here ?
ping @juherr @cbeust

@krmahadevan , thanks for the link! I was a bit naive and just opened the website: no changelog.
Then I've opened github releases and there were no changes too: https://github.com/cbeust/testng/releases/tag/7.0.0
After that I've googled what's new in testng 7.0 and found the link from my original post.
Lastly I've opened https://github.com/cbeust/testng/blob/master/CHANGES.txt and it's not clear when changes in 7.0 finished and 7.1 changes started. (as there is no divider like it was for 6.14.3 and previous releases).
I do understand you have not so many contributors to support website/write news/articles but for people who are not working very tightly with testng it's not clear whether I need to fix deprecations after moving to 7.0 and what other good things could be used.

@KroArtem

Lastly I've opened https://github.com/cbeust/testng/blob/master/CHANGES.txt and it's not clear when changes in 7.0 finished and 7.1 changes started. (as there is no divider like it was for 6.14.3 and previous releases).

I have now fixed it. Please check now here

I do understand you have not so many contributors to support website/write news/articles

Thanks for the understanding.

but for people who are not working very tightly with testng it's not clear whether I need to fix deprecations after moving to 7.0 and what other good things could be used.

So what do you suggest we do? We are open to suggestions. The release notes like the earlier link I shared is one of the ways. What other ways can you suggest.
@cbeust / @juherr
Can you please help with doing this : https://help.github.com/en/github/administering-a-repository/automation-for-release-forms-with-query-parameters

@krmahadevan , a message on the site/google groups is ok as you've done for 7.0 release
The only problem is that I didn't find those message via google.

@KroArtem - I have now added a link to the release notes into the README.md file on the repository itself. See here
If you are fine with this, we can perhaps close this issue.
Thanks for calling out an important aspect :) Appreciate it.

@krmahadevan , one more thing, it seems like 7.1.0 is already released or is it an RC or beta? If it's a release then one more announcement in google-groups is needed. :)
Otherwise this issue can be closed, thanks for your quick answers.

@KroArtem - No its not an official release "yet". It should get into a beta release. For minor releases I am not sure if a google groups announcement detailing all the features in it would be done. But if its done, I will add the release notes back to the repository. If not, the changes.txt will be updated properly on a per version basis.
Closing this issue for now.


add dual stack ipam test

add an unit test to validate dual stack ip assignment on the secondary interface
Signed-off-by: Periyasamy Palanisamy<EMAIL_ADDRESS>

/release-note-none

/lgtm
/approve
Looks good, thanks


(question) Custom patching the ExoPlayer aar

I need to add a custom patch to
https://github.com/martijn00/ExoPlayerXamarin/blob/develop/ExoPlayer/Jars/exoplayer-2.8.1.aar
I was wondering do you build this yourself or is it from a release? (I thought the aars for ExoPlayer were separed into core and extensions? Rather than a combined aar)
What's best way to support custom variations in your option? No API changes I'm just testing a bug fix to a PR I have with ExoPlayer library itself

Exoplayer is indeed split up. The .aar file is just a forwarder to the different dependencies, to not break compatibility. I get the files from Bintray.
You need to compile the fix yourself, and make a new build with my source code and hook that up into your project.

No worries, appreciated

On 13 Jun 2018, at 7:06 am, Martijn van Dijk<EMAIL_ADDRESS>wrote:
Exoplayer is indeed split up. The .aar file is just a forwarder to the different dependencies, to not break compatibility. I get the files from Bintray.
You need to compile the fix yourself, and make a new build with my source code and hook that up into your project.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Update meta description

In pages/index.tsx the current meta description on line 12 is <meta name="description" content="Generated by create next app" />
This should be updated to <meta name="description" content="Learn the basics about web accessibility in a clear and easy to understand way" />

hello ,i would like to work on this issue can you assign this to me @EmmaDawsonDev

Sure, go ahead :) If you're taking part in hacktoberfest then just wait until October 1st before making the pull request.

Yes, I'm taking part in hackoberfest


フロントで画像が表示されない不具合の訂正 Fixes #84

関連するIssue
Fixes #84
修正の程度

[ ] 破壊的で刷新的な新機能
[ ] 軽微な新機能
[x] バグ修正
[ ] 軽微な修正

変更点

[ ] post.generated_images.map((image) => image.url)に変更

Codecov Report

Merging #85 into develop will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff            @@
##           develop      #85   +/-   ##
========================================
  Coverage    95.31%   95.31%
========================================
  Files           16       16
  Lines          598      598
========================================
  Hits           570      570
  Misses          28       28

Flag
Coverage Δ

#unittests
95.31% <100.00%> (ø)

Impacted Files
Coverage Δ

api/src/app/database/models.py
100.00% <100.00%> (ø)

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 c77f048...37a505a. Read the comment docs.


BIGTOP-2616: refresh juju hadoop-processing bundle

We've made a number of improvements to the hadoop-processing bundle that are ready for review and inclusion upstream:

ganglia/rsyslog have been updated from trusty to xenial
add new machine constraints since aws now defaults to an 8gb root disk (we want 32g at a minimum)
ensure applications are actually ready before running tests
ensure the proper amulet test harness is included in the bundle tests

This looks good to me.  The tests are more specific, and are all passing for deployments on AWS and Azure, as evinced by http://cwr.vapour.ws/bundle_hadoop_processing/aba491a0c58843e0ab60d7c5291bf135/report.html
:+1:


refusing to allow a GitHub App to create or update workflow without workflows permission

origin	***github.com/IceCodeNew/v2ray-core (fetch)
origin	***github.com/IceCodeNew/v2ray-core (push)
tmp_upstream	https://github.com/v2fly/v2ray-core.git (fetch)
tmp_upstream	https://github.com/v2fly/v2ray-core.git (push)
To https://github.com/IceCodeNew/v2ray-core
 ! [remote rejected]   tmp_upstream/master -> master (refusing to allow a GitHub App to create or update workflow `.github/workflows/dlc.yml` without `workflows` permission)
error: failed to push some refs to '***github.com/IceCodeNew/v2ray-core'

https://pastebin.com/mi0LD3w8

You can create a personal access token with workflows permission.


Sort variable names by frequency

I was wondering how uglify-es was able to compete with Butternut by only mangling variable names. For example, Preact:

minified
zipped
time

butternut
8152
3398
20ms

uglify-es
8074
3355
167ms

uglify-es (mangle only)
8456
3381
45ms

Butternut's unzipped output is closer to that of Uglify with default settings than with just mangling, yet in this case the zipped output is actually smaller than Butternut's (normally it's the other way around, but it's often close).
Turns out that Uglify is doing something fiendishly clever — it's computing the frequency of characters that end up in the output, and assigning the most common ones first. So instead of a, b, c etc you might have o, a, n and so on.
We could possibly do something similar. Since Butternut isn't 'generating' code, perhaps the way to do it would be to replace variable names with some cryptic Unicode (e.g. instead of a, b, c we do ⊂0⊃, ⊂1⊃, ⊂2⊃) then at the end of the process tally up all the characters that aren't enclosed in ⊂...⊃ and replace the variable names with a regex.
Obviously we'd need to ensure we were using characters that weren't in the code in the first place.

Just curious - which version of node were used to produce those timings?
My results are very different with latest butternut 27639ce506848565c3bf42d061aed42519c2f425
node 6.9.0:
$ /usr/bin/time node690 bin/squash test/fixture/input/preact.js | wc -c
        0.22 real         0.23 user         0.02 sys
    8151

$ /usr/bin/time node690 node_modules/uglify-es/bin/uglifyjs -cm -- test/fixture/input/preact.js | wc -c
        0.46 real         0.54 user         0.03 sys
    8075

$ /usr/bin/time node690 node_modules/uglify-es/bin/uglifyjs -m -- test/fixture/input/preact.js | wc -c
        0.26 real         0.28 user         0.02 sys
    8457

node 7.7.3:
$ /usr/bin/time node773 bin/squash test/fixture/input/preact.js | wc -c
        0.19 real         0.21 user         0.02 sys
    8151

$ /usr/bin/time node773 node_modules/uglify-es/bin/uglifyjs -cm -- test/fixture/input/preact.js | wc -c
        0.46 real         0.51 user         0.02 sys
    8075

$ /usr/bin/time node773 node_modules/uglify-es/bin/uglifyjs -m -- test/fixture/input/preact.js | wc -c
        0.25 real         0.26 user         0.02 sys
    8457

7.8.0. This is using Benchmark.js which is probably somewhat misleading as everything gets warmed up, whereas minifiers usually run cold. I intend to replace the current benchmarks with more realistic ones that run each minifier once in a fresh process.

My timings from the command line are pretty cold. :-)
Here's the preact numbers from my previous bench in https://github.com/Rich-Harris/butternut/pull/44
preact.js (20.5 kB) without sourcemap:
  ✓ babili             :  8.41 kB /  3.47 kB in 377ms
  ✓ butternut          :  8.15 kB /   3.4 kB in 29ms
  ✓ closure            :  7.89 kB /  3.35 kB in 2.4s
  ✓ uglify             :  8.07 kB /  3.35 kB in 119ms
  ✓ uglify-mangle-only :  8.46 kB /  3.38 kB in 31ms
  ✓ uglify-es          :  8.07 kB /  3.35 kB in 144ms

@Rich-Harris You'll get a kick out of this:
Running Closure produced three.min.js through Uglify saves additional 1744 bytes uncompressed, 2860 gzipped
https://github.com/mrdoob/three.js/issues/11003
Props to @mishoo on the Uglify mangling algorithm.

That's wild! Is that mostly due to the mangling, or is it hard to know?

Hmm. I thought it was primarily due to mangling, but that's not the case.
Rather than building it this time, I grabbed the file from a CDN:
original size, not gzipped:
$ wc -c three.min.js
  510005 three.min.js

original gzipped:
$ cat three.min.js | gzip | wc -c
  129119

uglified with compress=false, mangle=false, gzipped:
$ cat three.min.js | bin/uglifyjs | gzip | wc -c
  127298

Very strange! 1821 bytes were saved without compress and without mangle - just eliminating whitespace and perhaps making numbers more compact? That doesn't make much sense - unless there's a ton of copyright comments that were stripped.
Let's call 127298 the baseline.
uglified with compress=false, mangle=true, gzipped:
$ cat three.min.js | bin/uglifyjs -m | gzip | wc -c
  126549

mangle savings: 749 bytes from the baseline
uglified with compress=true, mangle=false, gzipped:
$ cat three.min.js | bin/uglifyjs -c | gzip | wc -c
  127243

compress savings: 55 bytes from the baseline
uglified with compress=true, mangle=true, gzipped:
$ cat three.min.js | bin/uglifyjs -cm | gzip | wc -c
  126369

compress+mangle savings: 929 bytes from the baseline
So mangle did have some effect, but not to the extent I thought.


fix: internal sACK flag not set correctly for client socket

Bug Description
Selective ACK is used for TCP retransmission. In the current implementation, sACK option will be enabled by default for a client TCP socket. However, the remote_has_sack is not correctly set when the server sends a SYN-ACK packet back. Since remote_has_sack is false by default, client TCP sockets will not send sACK when packet loss happens.
However, when the sACK-permitted option is set in the initial SYN packet, the server will (typically) only expect sACK for fast retransmission. Since no sACK is received, the server (as a sender) will wait until retransmission timer expires. This will trigger congestion control, and users will observe an inconsistent download speed even if the network link is relatively stable.
Solution
Set remote_has_sack correctly in SynSent state. Listen state is not affected by this bug.

can you add a test?

@Dirbaio Corresponding test has been added.


Introducing less-variables for css colours.

Relating to #1057 .
Maybe we could normalize some colors to reduce the amount of the variables.
There are a lot of near neighbour colors.

Moving to variables is a great change. Unfortunately, the names don't tell me what I'm supposed to be using them for. I'd like to see names more like color-error than color-valencia. If we're going to name these, then we need to make it clear what the colors get used for.

:grin:
Yes, that is a good point, you're absolutly right. :) I will change this.
My intention was that a single color could used for multiple purposes.
F.ex. @color-shuttle-gray is used on 4 different purposes, as background for buttons, border color for form control, background in the progress bar.. I wanted to reduce the amount of variables, but this is meaningless.

Will do it like this:
http://sachagreif.com/sass-color-variables/

I would rather that we name them like @pyronicide suggests, and if they happen to be used for multiple purposes, say color-success and color-active, then declare two names and give them the same value. In this specific case I'm thinking of the button colours, and active tab/link colours. It's not very descriptive for their purpose to call them border_color and link_color, in my opinion

Yes, that is a good approach and was also my intention. border_color would also be meaningless.
I will take a look on which places in the less-file it makes sense to introduce meaningful variables.
Here it makes sense:
.has-error .help-block,
.has-error .control-label,
.has-error .radio,
.has-error .checkbox,
.has-error .radio-inline,
.has-error .checkbox-inline {
  color: @color-error;
}

But what should I do here, could be @color-page-background?:
.modal-content {
  background-color: @color-ebony-clay;
}

And colors that do not have an associated function, like a simple border? There I would use the color name.
.form-control {
  background: @color-white-smoke;
  border-color: @color-shuttle-grey;
  color: @color-mortar;
}

else we end up in single variables for each meaning. Which would make this approach a little bit of sensless??
.form-control {
  background: @color-form-background;
  border-color: @color-form-border;
  color: @color-form-text;
}

That sounds good.
The main purpose here is also to make it configurable. Take a look at how the name the variables in bootstrap: https://github.com/twbs/bootstrap/blob/master/less/variables.less
I think colours that we use multiple places makes sense to make configurable. An example is #f6f6f6. We could name e.g. form-control background @input-bg and btn-default colour @btn-default-color. This way it would be easy to see which colours are used where and configure it.
Does that make sense?
And again inspired by bootstrap we could keep these in a separate stylesheet, e.g. variables.less.

@aldipower What's the status of this?

Closing for now. We can re-open, when we get more time to work on this.


User / Groups search control panel / sharing panel improvements #4551

When searching for users (Users Control Panel, Page sharing, etc.) it takes some time for the results to return from the server (LDAP). The problem is that there is no visual feedback for the end-user to show this, also the form is not blocked and the user can click multiple time on the search button, stressing the server.
users-loading.webm

This is partially addressed also in #4572
I won't be able to look at this at least in 10 days, sorry about that.

@erral @tedw87 ok, so we have https://github.com/plone/volto/pull/4572 and this one, which one goes first, and does they collide at some point?

I talked to @jackahl about the GSOC, and he was going to try not to collide with my changes.I haven't checked this PR though, and I can't say... I need to take some time to checK

@erral @tedw87 @robgietema @jackahl Please guide me on this one whenever you can, it would be great to have both for 17 final.

I have checked this PR, and it applies cleanly on top of mine, as it is complementary, it adds the "loading" spinner while the search is done or the users/groups are loaded.
So I would say to merge first #4572 and right after that, this one the #5053.
@avoinea
@tedw87
@sneridagh


The software stops when have a empty tissue image when I tried to process hundreds of images

I don't think it is a real issue, but when I process lots of images using for loop in python, one blank image with empty tissue will stop the whole process. Can you modified the code and let it do nothing on that image, but keep processing other images? Thank you!
Here is the error message:
~/staintools/tissue_masks/luminosity_threshold_tissue_locator.py", line 27, in get_tissue_mask
raise TissueMaskException("Empty tissue mask computed")
staintools.miscellaneous.exceptions.TissueMaskException: Empty tissue mask computed

Just use a try catch block inside your loop perhaps? That should let the program keep running and allow you to handle the error as you see appropriate?

When I tried to normalize some image patches. I got the same error.
staintools.miscellaneous.exceptions.TissueMaskException: Empty tissue mask computed
The exception is thrown from the code below:
`
Check it's not empty
    if mask.sum() == 0:
        raise TissueMaskException("Empty tissue mask computed")

`
I noticed that these three lines do not exist in previous version. Are these really necessary?

Yes I think so. If we found no tissue in that image there is certainly no point to try and stain normalize and it can helpful to have such images pointed out to you. Just catch the exception and handle how you like (probably just skip and make a note that that patch is all background).


Changing Auth 'parameters.json' and 'template.yml' fails

Which Category is your question related to?
Auth
Amplify CLI Version
4.32.0
What AWS Services are you utilizing?
AWS Cognito
Provide additional details e.g. code snippets
Hi, I am adding Auth with amplify auth add. The default Auth created by Amplify uses case sensitive username. For example, if email is used as username alias<EMAIL_ADDRESS>and<EMAIL_ADDRESS>would be treated as two different usernames, which is not what most people wanted (This has been brought up before #4185 and remains unresolved).
With the old version of Amplify CLI, we can modify the Auth Cloudformation Template directly by adding UsernameConfiguration to enable case insensitivity. (As mentioned in #3494)
  UsernameConfiguration:
    CaseSensitive: false

However, with the new CLI that creates two files parameters.json and xxx-cloudformation-template.yml, I am confused as to where to add this.
In parameters.json, I had tried "usernameConfiguration": {"CaseSensitive": false} or "usernameConfiguration": "{\n  \"CaseSensitive\": false \n}".
In xxx-cloudformation-template.yml, I added
Parameters:
  (...skip)
  usernameConfiguration:
    Type: String

Resources:
  (...skip)
  UserPool:
    (...skip)
    Properties:
      UsernameConfiguration: !Ref usernameConfiguration

but I received the error Property validation failure: [Value UsernameConfiguration} does not match type {Object}] when I do amplify push. I would appreciate any helps to resolve this. Thanks.

Sorry, I had a brain fart.
Basically, simply add it to xxx-cloudformation-template.yml solves it. No need to touch parameters.json
Parameters:
  (...skip)
  usernameConfiguration:
    Type: String

Resources:
  (...skip)
  UserPool:
    (...skip)
    Properties:
      UsernameConfiguration:
        CaseSensitive: false

@xitanggg, I just updated yaml, but amplify push failed with the following error. I selected Email with amplify auth add and the default configuration option. Any idea what the issue could be? I didn't find any official aws documentation related to updating the template before the amplify push.
CREATE_FAILED               UpdateRolesWithIDPFunctionRole AWS::IAM::Role             Thu Nov 19 2020 17:31:37 GMT-0500 (Eastern Standard Time) Resource creation cancelled                                                                                UPDATE_FAILED               DeploymentBucket               AWS::S3::Bucket            Thu Nov 19 2020 17:31:37 GMT-0500 (Eastern Standard Time) Resource update cancelled                                                                                CREATE_FAILED               authcognitoui0e05feaf          AWS::CloudFormation::Stack Thu Nov 19 2020 17:31:37 GMT-0500 (Eastern Standard Time) Parameters: [usernameConfiguration] must have values

Which yml file you changed? It should be the one under amplify/backend/auth/{YourAuthResource}/ and it is called {YourAuthResource}-cloudformation-template.yml?

Thanks for the quick response. With trial and error found that the below code is what is needed in the template file to do the magic. Meanning...no need to mention usernameConfiguration: Type: String under Parameters.
Properties:   <<skip>>   UsernameConfiguration:     CaseSensitive: false


Adjusting brightness

Where/how can I adjust brightness? game is too bright even on moody.

This works, but now that I set night to be night now I have issue of days being too dark.


character issue when converting (adding this: þÿ)

Thanks for this package.
I am gonna to make pdf from html(text is Franch)
some text is correct but some text is unexpected...
for example some þÿ is adding.
Is there clear resolution for this?

wait till utf-8 is implemented. There are already solutions like PR #1448, #1433

Duplicate of #12
UTF-8 Solution coming soon


Variables in Kotlin: Android Basics with Compose

When typing in the example code, println(count) does not work because there is no space between printing & (count).

Println* & (count). Not printing. Autocorrected.

Hi @Nat9144
Thank you for writing in with your issue.
Please provide a screenshot of the code you typed and the error message being displayed.
I was not able to understand the problem from just the description provided.
I looked forward to your response.
Hope you are enjoying the course!
Regards.

Closing this issue as there has not been any additional feedback as requested.


dart test doesn't recognize the --define or '-D' flag

even if #44562 is closed, it seems actually not possible to define environment variables fort the dart test command ?

The flag should be named --define or -D, not --dart-define (that's Flutter's name, Dart itself doesn't need to say that).
Have you tried dart -Dfoo=bar test?

yes also tried with -D but the result is Could not find an option with short name "-D".

the workaround seems to be :
export DART_VM_OPTIONS='-Dfoo=bar' && \                                                              1 ↵ ✹ ✚ ✭
          dart test

cc @natebosch @grouma

dart -Dfoo=true test will do what you are hoping.
Importantly pass the -D after dart, not after test in the command.

dart test -Dfoo=true should also be valid, as that support has been added for other commands (see dart run and the various dart compile commands).


Support using local server instead of creating one

When used with other front-end frameworks that already provide a local server (React, Next, Hugo, etc.) it would be great if live preview could have an option to just preview the site at a given URL instead of generating one. This is a more "true" preview of the site.

FWIW, this can be achieved with the Simple Browser: Show command.

This is handled by simple browser so there is no need for it

Not sure if I'm misunderstanding, but Simple Browser lacks a large amount of the functionality that live preview has, making it virtually unusable for anything other than toy development. Most notably, it doesn't have a debugger or any way to view console.log() output. I'd recommend reopening this issue.


Utils compare

Pull request
Please confirm that this pull request has done the following:

[x] Tests added
[x] Documentation added (where applicable)
[x] Example added (either to an existing notebook or as a new notebook, where applicable)
[x] Description in CHANGELOG.rst added

To explain this pull request - this is a selection of useful functions that were either used to investigate the data or will be used in future pull requests. They don't have an obvious application within the existing codebase but notebooks demonstrating their use will come in the next few PRs.


mDNS lookup fails

I have envoy setup between two machines servers on my local wifi network. The server side is using Avahi for mDNS and all of the normal tools (ping, ssh,etc) on my client machine can find it just fine.  Envoy, however, can't find it using a hostname, but has no problems with the direct ip.  Also, having my hello client directly talk to the server-side envoy without going through the client side envoy works fine.  Here's my server and client side config, plus the log from the client-side envoy.
Client config:
#envoy-hello-client.yaml
static_resources:
  listeners:
  - address:
      socket_address:
        address: <IP_ADDRESS>
        port_value: 9911
    filter_chains:
    - filters:
      - name: envoy.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.config.filter.network.http_connection_manager.v2.HttpConnectionManager
          codec_type: auto
          stat_prefix: ingress_http
          access_log:
          - name: envoy.file_access_log
            typed_config:
              "@type": type.googleapis.com/envoy.config.accesslog.v2.FileAccessLog
              path: "/dev/stdout"
          route_config:
            name: local_route
            virtual_hosts:
            - name: backend
              domains:
              - ["*"]
              routes:
              - match:
                  prefix: "/"
                  grpc: {}
                route:
                  cluster: hello_grpc_client
          http_filters:
          - name: envoy.router
            typed_config: {}
  clusters:
  - name: hello_grpc_client
    connect_timeout: 0.250s
    type: strict_dns
    lb_policy: round_robin
    http2_protocol_options: {}
    load_assignment:
      cluster_name: hello_grpc_client_cluster
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                #address: <IP_ADDRESS>  <- This works
                address: g19sbc.local  # <- This fails
                port_value: 8811

admin:
  access_log_path: "/tmp/envoy_hello_server.log"
  address:
    socket_address:
      address: <IP_ADDRESS>
      port_value: 9991

Server config:
# envoy-hello-server.yaml
static_resources:
  listeners:
  - address:
      socket_address:
        address: <IP_ADDRESS>
        port_value: 8811
    filter_chains:
    - filters:
      - name: envoy.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.config.filter.network.http_connection_manager.v2.HttpConnectionManager
          codec_type: auto
          stat_prefix: ingress_http
          access_log:
          - name: envoy.file_access_log
            typed_config:
              "@type": type.googleapis.com/envoy.config.accesslog.v2.FileAccessLog
              path: "/dev/stdout"
          route_config:
            name: local_route
            virtual_hosts:
            - name: backend
              domains:
              - ["*"]
              routes:
              - match:
                  prefix: "/"
                  grpc: {}
                route:
                  cluster: hello_grpc_service
          http_filters:
          - name: envoy.router
            typed_config: {}
  clusters:
  - name: hello_grpc_service
    connect_timeout: 0.250s
    type: strict_dns
    lb_policy: round_robin
    http2_protocol_options: {}
    load_assignment:
      cluster_name: hello_grpc_service_cluster
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: <IP_ADDRESS>
                port_value: 8081

admin:
  access_log_path: "/tmp/envoy_hello_server.log"
  address:
    socket_address:
      address: <IP_ADDRESS>
      port_value: 8881

Client envoy log
getenvoy run standard:1.15.0 -- --config-path envoy-hello-client.yaml -l trace
2020-07-21T16:08:31.910756Z	info	Envoy command: [/home/adam/.getenvoy/builds/standard/1.15.0/linux_glibc/bin/envoy --config-path envoy-hello-client.yaml -l trace]
[2020-07-21 09:08:32.042][3498][warning][runtime] [external/envoy/source/common/runtime/runtime_features.cc:20] Unable to use runtime singleton for feature envoy.reloadable_features.activate_fds_next_event_loop
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:295] initializing epoch 0 (base id=0, hot restart version=11.104)
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:297] statically linked extensions:
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.transport_sockets.downstream: envoy.transport_sockets.alts, envoy.transport_sockets.quic, envoy.transport_sockets.raw_buffer, envoy.transport_sockets.tap, envoy.transport_sockets.tls, raw_buffer, tls
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.grpc_credentials: envoy.grpc_credentials.aws_iam, envoy.grpc_credentials.default, envoy.grpc_credentials.file_based_metadata
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.stats_sinks: envoy.dog_statsd, envoy.metrics_service, envoy.stat_sinks.dog_statsd, envoy.stat_sinks.hystrix, envoy.stat_sinks.metrics_service, envoy.stat_sinks.statsd, envoy.statsd
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.compression.decompressor: envoy.compression.gzip.decompressor
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.upstreams: envoy.filters.connection_pools.http.generic, envoy.filters.connection_pools.http.http, envoy.filters.connection_pools.http.tcp
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.access_loggers: envoy.access_loggers.file, envoy.access_loggers.http_grpc, envoy.access_loggers.tcp_grpc, envoy.file_access_log, envoy.http_grpc_access_log, envoy.tcp_grpc_access_log
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.dubbo_proxy.protocols: dubbo
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.dubbo_proxy.route_matchers: default
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.filters.udp_listener: envoy.filters.udp.dns_filter, envoy.filters.udp_listener.udp_proxy
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.filters.listener: envoy.filters.listener.http_inspector, envoy.filters.listener.original_dst, envoy.filters.listener.original_src, envoy.filters.listener.proxy_protocol, envoy.filters.listener.tls_inspector, envoy.listener.http_inspector, envoy.listener.original_dst, envoy.listener.original_src, envoy.listener.proxy_protocol, envoy.listener.tls_inspector
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.clusters: envoy.cluster.eds, envoy.cluster.logical_dns, envoy.cluster.original_dst, envoy.cluster.static, envoy.cluster.strict_dns, envoy.clusters.aggregate, envoy.clusters.dynamic_forward_proxy, envoy.clusters.redis
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.thrift_proxy.protocols: auto, binary, binary/non-strict, compact, twitter
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.thrift_proxy.filters: envoy.filters.thrift.rate_limit, envoy.filters.thrift.router
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.retry_host_predicates: envoy.retry_host_predicates.omit_canary_hosts, envoy.retry_host_predicates.omit_host_metadata, envoy.retry_host_predicates.previous_hosts
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.dubbo_proxy.serializers: dubbo.hessian2
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.thrift_proxy.transports: auto, framed, header, unframed
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.tracers: envoy.dynamic.ot, envoy.lightstep, envoy.tracers.datadog, envoy.tracers.dynamic_ot, envoy.tracers.lightstep, envoy.tracers.opencensus, envoy.tracers.xray, envoy.tracers.zipkin, envoy.zipkin
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.health_checkers: envoy.health_checkers.redis
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.compression.compressor: envoy.compression.gzip.compressor
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.filters.network: envoy.client_ssl_auth, envoy.echo, envoy.ext_authz, envoy.filters.network.client_ssl_auth, envoy.filters.network.direct_response, envoy.filters.network.dubbo_proxy, envoy.filters.network.echo, envoy.filters.network.ext_authz, envoy.filters.network.http_connection_manager, envoy.filters.network.kafka_broker, envoy.filters.network.local_ratelimit, envoy.filters.network.mongo_proxy, envoy.filters.network.mysql_proxy, envoy.filters.network.postgres_proxy, envoy.filters.network.ratelimit, envoy.filters.network.rbac, envoy.filters.network.redis_proxy, envoy.filters.network.rocketmq_proxy, envoy.filters.network.sni_cluster, envoy.filters.network.sni_dynamic_forward_proxy, envoy.filters.network.tcp_proxy, envoy.filters.network.thrift_proxy, envoy.filters.network.zookeeper_proxy, envoy.http_connection_manager, envoy.mongo_proxy, envoy.ratelimit, envoy.redis_proxy, envoy.tcp_proxy
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.resource_monitors: envoy.resource_monitors.fixed_heap, envoy.resource_monitors.injected_resource
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.udp_listeners: raw_udp_listener
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   http_cache_factory: envoy.extensions.http.cache.simple
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.resolvers: envoy.ip
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.retry_priorities: envoy.retry_priorities.previous_priorities
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.filters.http: envoy.buffer, envoy.cors, envoy.csrf, envoy.ext_authz, envoy.fault, envoy.filters.http.adaptive_concurrency, envoy.filters.http.admission_control, envoy.filters.http.aws_lambda, envoy.filters.http.aws_request_signing, envoy.filters.http.buffer, envoy.filters.http.cache, envoy.filters.http.compressor, envoy.filters.http.cors, envoy.filters.http.csrf, envoy.filters.http.decompressor, envoy.filters.http.dynamic_forward_proxy, envoy.filters.http.dynamo, envoy.filters.http.ext_authz, envoy.filters.http.fault, envoy.filters.http.grpc_http1_bridge, envoy.filters.http.grpc_http1_reverse_bridge, envoy.filters.http.grpc_json_transcoder, envoy.filters.http.grpc_stats, envoy.filters.http.grpc_web, envoy.filters.http.gzip, envoy.filters.http.header_to_metadata, envoy.filters.http.health_check, envoy.filters.http.ip_tagging, envoy.filters.http.jwt_authn, envoy.filters.http.lua, envoy.filters.http.on_demand, envoy.filters.http.original_src, envoy.filters.http.ratelimit, envoy.filters.http.rbac, envoy.filters.http.router, envoy.filters.http.squash, envoy.filters.http.tap, envoy.grpc_http1_bridge, envoy.grpc_json_transcoder, envoy.grpc_web, envoy.gzip, envoy.health_check, envoy.http_dynamo_filter, envoy.ip_tagging, envoy.lua, envoy.rate_limit, envoy.router, envoy.squash
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.transport_sockets.upstream: envoy.transport_sockets.alts, envoy.transport_sockets.quic, envoy.transport_sockets.raw_buffer, envoy.transport_sockets.tap, envoy.transport_sockets.tls, raw_buffer, tls
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.internal_redirect_predicates: envoy.internal_redirect_predicates.allow_listed_routes, envoy.internal_redirect_predicates.previous_routes, envoy.internal_redirect_predicates.safe_cross_scheme
[2020-07-21 09:08:32.042][3498][info][main] [external/envoy/source/server/server.cc:299]   envoy.dubbo_proxy.filters: envoy.filters.dubbo.router
[2020-07-21 09:08:32.048][3498][info][main] [external/envoy/source/server/server.cc:315] HTTP header map info:
[2020-07-21 09:08:32.048][3498][info][main] [external/envoy/source/server/server.cc:318]   request header map: 496 bytes: :authority,:method,:path,:protocol,:scheme,accept,accept-encoding,access-control-request-method,authorization,cache-control,connection,content-encoding,content-length,content-type,expect,grpc-accept-encoding,grpc-timeout,keep-alive,origin,proxy-connection,referer,te,transfer-encoding,upgrade,user-agent,via,x-client-trace-id,x-envoy-attempt-count,x-envoy-decorator-operation,x-envoy-downstream-service-cluster,x-envoy-downstream-service-node,x-envoy-expected-rq-timeout-ms,x-envoy-external-address,x-envoy-force-trace,x-envoy-hedge-on-per-try-timeout,x-envoy-internal,x-envoy-ip-tags,x-envoy-max-retries,x-envoy-original-path,x-envoy-original-url,x-envoy-retriable-header-names,x-envoy-retriable-status-codes,x-envoy-retry-grpc-on,x-envoy-retry-on,x-envoy-upstream-alt-stat-name,x-envoy-upstream-rq-per-try-timeout-ms,x-envoy-upstream-rq-timeout-alt-response,x-envoy-upstream-rq-timeout-ms,x-forwarded-client-cert,x-forwarded-for,x-forwarded-proto,x-ot-span-context,x-request-id
[2020-07-21 09:08:32.048][3498][info][main] [external/envoy/source/server/server.cc:318]   request trailer map: 72 bytes:
[2020-07-21 09:08:32.048][3498][info][main] [external/envoy/source/server/server.cc:318]   response header map: 352 bytes: :status,access-control-allow-credentials,access-control-allow-headers,access-control-allow-methods,access-control-allow-origin,access-control-expose-headers,access-control-max-age,cache-control,connection,content-encoding,content-length,content-type,date,etag,grpc-message,grpc-status,keep-alive,location,proxy-connection,referer,server,transfer-encoding,upgrade,vary,via,x-envoy-attempt-count,x-envoy-decorator-operation,x-envoy-degraded,x-envoy-immediate-health-check-fail,x-envoy-ratelimited,x-envoy-upstream-canary,x-envoy-upstream-healthchecked-cluster,x-envoy-upstream-service-time,x-request-id
[2020-07-21 09:08:32.048][3498][info][main] [external/envoy/source/server/server.cc:318]   response trailer map: 96 bytes: grpc-message,grpc-status
[2020-07-21 09:08:32.049][3498][info][main] [external/envoy/source/server/server.cc:389] admin address: <IP_ADDRESS>:9991
[2020-07-21 09:08:32.049][3498][debug][main] [external/envoy/source/server/overload_manager_impl.cc:184] No overload action is configured for envoy.overload_actions.shrink_heap.
[2020-07-21 09:08:32.049][3498][debug][main] [external/envoy/source/server/overload_manager_impl.cc:184] No overload action is configured for envoy.overload_actions.stop_accepting_connections.
[2020-07-21 09:08:32.049][3498][debug][main] [external/envoy/source/server/overload_manager_impl.cc:184] No overload action is configured for envoy.overload_actions.stop_accepting_connections.
[2020-07-21 09:08:32.049][3498][debug][main] [external/envoy/source/server/overload_manager_impl.cc:184] No overload action is configured for envoy.overload_actions.stop_accepting_connections.
[2020-07-21 09:08:32.049][3498][debug][main] [external/envoy/source/server/overload_manager_impl.cc:184] No overload action is configured for envoy.overload_actions.stop_accepting_connections.
[2020-07-21 09:08:32.049][3498][info][main] [external/envoy/source/server/server.cc:555] runtime: layers:
  - name: base
    static_layer:
      {}
  - name: admin
    admin_layer:
      {}
[2020-07-21 09:08:32.049][3498][info][config] [external/envoy/source/server/configuration_impl.cc:103] loading tracing configuration
[2020-07-21 09:08:32.049][3498][info][config] [external/envoy/source/server/configuration_impl.cc:69] loading 0 static secret(s)
[2020-07-21 09:08:32.049][3498][info][config] [external/envoy/source/server/configuration_impl.cc:75] loading 1 cluster(s)
[2020-07-21 09:08:32.050][3504][debug][grpc] [external/envoy/source/common/grpc/google_async_client_impl.cc:49] completionThread running
[2020-07-21 09:08:32.051][3498][debug][upstream] [external/envoy/source/common/upstream/cluster_manager_impl.cc:982] adding TLS initial cluster hello_grpc_client
[2020-07-21 09:08:32.055][3498][trace][upstream] [external/envoy/source/common/upstream/strict_dns_cluster.cc:106] starting async DNS resolution for g19sbc.local
[2020-07-21 09:08:32.055][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 5000 milliseconds
[2020-07-21 09:08:32.055][3498][debug][upstream] [external/envoy/source/common/upstream/cluster_manager_impl.cc:79] cm init: adding: cluster=hello_grpc_client primary=1 secondary=0
[2020-07-21 09:08:32.055][3498][debug][upstream] [external/envoy/source/common/upstream/cluster_manager_impl.cc:127] maybe finish initialize state: 1
[2020-07-21 09:08:32.055][3498][debug][upstream] [external/envoy/source/common/upstream/cluster_manager_impl.cc:136] maybe finish initialize primary init clusters empty: false
[2020-07-21 09:08:32.055][3498][info][config] [external/envoy/source/server/configuration_impl.cc:79] loading 1 listener(s)
[2020-07-21 09:08:32.055][3498][debug][config] [external/envoy/source/server/configuration_impl.cc:81] listener #0:
[2020-07-21 09:08:32.055][3498][debug][config] [external/envoy/source/server/listener_manager_impl.cc:391] begin add/update listener: name=df3fe2f7-9683-4119-a63a-a6f4c232a4ae hash=8209399288220754610
[2020-07-21 09:08:32.055][3498][debug][config] [external/envoy/source/server/listener_manager_impl.cc:417] use full listener update path for listener name=df3fe2f7-9683-4119-a63a-a6f4c232a4ae hash=8209399288220754610
[2020-07-21 09:08:32.055][3498][debug][config] [external/envoy/source/server/listener_manager_impl.cc:95]   filter #0:
[2020-07-21 09:08:32.055][3498][debug][config] [external/envoy/source/server/listener_manager_impl.cc:96]     name: envoy.http_connection_manager
[2020-07-21 09:08:32.055][3498][debug][config] [external/envoy/source/server/listener_manager_impl.cc:103]   config: {
 "@type": "type.googleapis.com/envoy.config.filter.network.http_connection_manager.v2.HttpConnectionManager",
 "access_log": [
  {
   "typed_config": {
    "@type": "type.googleapis.com/envoy.config.accesslog.v2.FileAccessLog",
    "path": "/dev/stdout"
   },
   "name": "envoy.file_access_log"
  }
 ],
 "http_filters": [
  {
   "typed_config": {},
   "name": "envoy.router"
  }
 ],
 "route_config": {
  "name": "local_route",
  "virtual_hosts": [
   {
    "name": "backend",
    "routes": [
     {
      "match": {
       "prefix": "/",
       "grpc": {}
      },
      "route": {
       "cluster": "hello_grpc_client"
      }
     }
    ],
    "domains": [
     "*"
    ]
   }
  ]
 },
 "codec_type": "AUTO",
 "stat_prefix": "ingress_http"
}

[2020-07-21 09:08:32.060][3498][debug][config] [external/envoy/source/extensions/filters/network/http_connection_manager/config.cc:450]     http filter #0
[2020-07-21 09:08:32.060][3498][debug][config] [external/envoy/source/extensions/filters/network/http_connection_manager/config.cc:451]       name: envoy.router
[2020-07-21 09:08:32.060][3498][debug][config] [external/envoy/source/extensions/filters/network/http_connection_manager/config.cc:458]     config: {}

[2020-07-21 09:08:32.060][3498][warning][misc] [bazel-out/k8-opt/bin/external/envoy/source/extensions/common/_virtual_includes/utility_lib/extensions/common/utility.h:66] Using deprecated extension name 'envoy.router' for 'envoy.filters.http.router'. This name will be removed from Envoy soon. Please see https://www.envoyproxy.io/docs/envoy/latest/version_history/version_history for details.
[2020-07-21 09:08:32.061][3498][debug][config] [external/envoy/source/server/filter_chain_manager_impl.cc:215] new fc_contexts has 1 filter chains, including 1 newly built
[2020-07-21 09:08:32.061][3498][debug][init] [external/envoy/source/common/init/manager_impl.cc:20] added target Listener-init-target df3fe2f7-9683-4119-a63a-a6f4c232a4ae to init manager Server
[2020-07-21 09:08:32.061][3498][debug][config] [external/envoy/source/server/listener_impl.cc:103] Create listen socket for listener df3fe2f7-9683-4119-a63a-a6f4c232a4ae on address <IP_ADDRESS>:9911
[2020-07-21 09:08:32.061][3498][debug][config] [external/envoy/source/server/listener_impl.cc:93] Set listener df3fe2f7-9683-4119-a63a-a6f4c232a4ae socket factory local address to <IP_ADDRESS>:9911
[2020-07-21 09:08:32.061][3498][debug][config] [external/envoy/source/server/listener_impl.cc:614] add active listener: name=df3fe2f7-9683-4119-a63a-a6f4c232a4ae, hash=8209399288220754610, address=<IP_ADDRESS>:9911
[2020-07-21 09:08:32.061][3498][info][config] [external/envoy/source/server/configuration_impl.cc:129] loading stats sink configuration
[2020-07-21 09:08:32.061][3498][info][main] [external/envoy/source/server/server.cc:652] starting main dispatch loop
[2020-07-21 09:08:37.059][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 10000 milliseconds
[2020-07-21 09:08:37.061][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:08:37.061][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:08:42.094][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:08:42.094][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:08:47.061][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 20000 milliseconds
[2020-07-21 09:08:47.094][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:08:47.094][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:08:52.114][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:08:52.114][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:08:57.119][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:08:57.119][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:09:02.117][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:09:02.117][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:09:07.068][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 40000 milliseconds
[2020-07-21 09:09:07.122][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:09:07.122][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:09:12.122][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:09:12.122][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:09:17.127][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:09:17.127][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:09:22.130][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:09:22.130][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:09:27.132][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:09:27.132][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:09:32.135][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:09:32.135][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:09:37.139][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:09:37.139][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:09:42.137][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:09:42.137][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:09:47.069][3498][debug][upstream] [external/envoy/source/common/network/dns_impl.cc:156] DNS request timed out 4 times
[2020-07-21 09:09:47.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 5000 milliseconds
[2020-07-21 09:09:47.141][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:09:47.141][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.069][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 0 milliseconds
[2020-07-21 09:09:52.070][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 10000 milliseconds
[2020-07-21 09:09:52.146][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:09:52.146][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:09:57.148][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:09:57.148][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:10:02.141][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 20000 milliseconds
[2020-07-21 09:10:02.154][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:10:02.154][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:10:07.161][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:10:07.161][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:10:12.168][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:10:12.168][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:10:17.206][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:10:17.206][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:10:22.144][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 40000 milliseconds
[2020-07-21 09:10:22.211][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:10:22.211][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:10:27.215][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:10:27.215][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:10:32.223][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:10:32.223][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:10:37.225][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:10:37.225][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:10:42.248][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:10:42.248][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:10:47.251][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:10:47.251][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:10:52.257][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:10:52.257][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:10:57.268][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:10:57.268][3498][debug][main] [external/envoy/source/server/server.cc:199] Envoy is not fully initialized, skipping histogram merge and flushing stats
[2020-07-21 09:11:02.146][3498][debug][upstream] [external/envoy/source/common/network/dns_impl.cc:156] DNS request timed out 4 times
[2020-07-21 09:11:02.146][3498][trace][upstream] [external/envoy/source/common/upstream/strict_dns_cluster.cc:114] async DNS resolution complete for g19sbc.local
[2020-07-21 09:11:02.146][3498][debug][upstream] [external/envoy/source/common/upstream/strict_dns_cluster.cc:174] DNS refresh rate reset for g19sbc.local, (failure) refresh rate 5000 ms
[2020-07-21 09:11:02.146][3498][debug][upstream] [external/envoy/source/common/upstream/upstream_impl.cc:976] initializing Primary cluster hello_grpc_client completed
[2020-07-21 09:11:02.146][3498][debug][init] [external/envoy/source/common/init/manager_impl.cc:45] init manager Cluster hello_grpc_client contains no targets
[2020-07-21 09:11:02.146][3498][debug][init] [external/envoy/source/common/init/watcher_impl.cc:14] init manager Cluster hello_grpc_client initialized, notifying ClusterImplBase
[2020-07-21 09:11:02.146][3498][debug][upstream] [external/envoy/source/common/upstream/cluster_manager_impl.cc:107] cm init: init complete: cluster=hello_grpc_client primary=0 secondary=0
[2020-07-21 09:11:02.146][3498][debug][upstream] [external/envoy/source/common/upstream/cluster_manager_impl.cc:127] maybe finish initialize state: 1
[2020-07-21 09:11:02.146][3498][debug][upstream] [external/envoy/source/common/upstream/cluster_manager_impl.cc:136] maybe finish initialize primary init clusters empty: true
[2020-07-21 09:11:02.146][3498][debug][init] [external/envoy/source/common/init/manager_impl.cc:45] init manager RTDS contains no targets
[2020-07-21 09:11:02.146][3498][debug][init] [external/envoy/source/common/init/watcher_impl.cc:14] init manager RTDS initialized, notifying RDTS
[2020-07-21 09:11:02.146][3498][info][runtime] [external/envoy/source/common/runtime/runtime_impl.cc:524] RTDS has finished initialization
[2020-07-21 09:11:02.146][3498][debug][upstream] [external/envoy/source/common/upstream/cluster_manager_impl.cc:200] continue initializing secondary clusters
[2020-07-21 09:11:02.146][3498][debug][upstream] [external/envoy/source/common/upstream/cluster_manager_impl.cc:127] maybe finish initialize state: 2
[2020-07-21 09:11:02.146][3498][debug][upstream] [external/envoy/source/common/upstream/cluster_manager_impl.cc:136] maybe finish initialize primary init clusters empty: true
[2020-07-21 09:11:02.146][3498][debug][upstream] [external/envoy/source/common/upstream/cluster_manager_impl.cc:151] maybe finish initialize secondary init clusters empty: true
[2020-07-21 09:11:02.146][3498][debug][upstream] [external/envoy/source/common/upstream/cluster_manager_impl.cc:176] maybe finish initialize cds api ready: false
[2020-07-21 09:11:02.146][3498][info][upstream] [external/envoy/source/common/upstream/cluster_manager_impl.cc:182] cm init: all clusters initialized
[2020-07-21 09:11:02.146][3498][info][main] [external/envoy/source/server/server.cc:631] all clusters initialized. initializing init manager
[2020-07-21 09:11:02.146][3498][debug][init] [external/envoy/source/common/init/manager_impl.cc:49] init manager Server initializing
[2020-07-21 09:11:02.146][3498][debug][init] [external/envoy/source/common/init/target_impl.cc:15] init manager Server initializing target Listener-init-target df3fe2f7-9683-4119-a63a-a6f4c232a4ae
[2020-07-21 09:11:02.146][3498][debug][init] [external/envoy/source/common/init/manager_impl.cc:45] init manager Listener-local-init-manager df3fe2f7-9683-4119-a63a-a6f4c232a4ae<PHONE_NUMBER>220754610 contains no targets
[2020-07-21 09:11:02.146][3498][debug][init] [external/envoy/source/common/init/watcher_impl.cc:14] init manager Listener-local-init-manager df3fe2f7-9683-4119-a63a-a6f4c232a4ae<PHONE_NUMBER>220754610 initialized, notifying Listener-local-init-watcher df3fe2f7-9683-4119-a63a-a6f4c232a4ae
[2020-07-21 09:11:02.146][3498][debug][init] [external/envoy/source/common/init/watcher_impl.cc:14] target Listener-init-target df3fe2f7-9683-4119-a63a-a6f4c232a4ae initialized, notifying init manager Server
[2020-07-21 09:11:02.146][3498][debug][init] [external/envoy/source/common/init/watcher_impl.cc:14] init manager Server initialized, notifying RunHelper
[2020-07-21 09:11:02.146][3498][info][config] [external/envoy/source/server/listener_manager_impl.cc:844] all dependencies initialized. starting workers
[2020-07-21 09:11:02.146][3498][debug][config] [external/envoy/source/server/listener_manager_impl.cc:855] starting worker 0
[2020-07-21 09:11:02.146][3498][debug][config] [external/envoy/source/server/listener_manager_impl.cc:855] starting worker 1
[2020-07-21 09:11:02.147][3634][debug][main] [external/envoy/source/server/worker_impl.cc:125] worker entering dispatch loop
[2020-07-21 09:11:02.147][3498][debug][config] [external/envoy/source/server/listener_manager_impl.cc:855] starting worker 2
[2020-07-21 09:11:02.147][3634][debug][upstream] [external/envoy/source/common/upstream/cluster_manager_impl.cc:982] adding TLS initial cluster hello_grpc_client
[2020-07-21 09:11:02.147][3636][debug][grpc] [external/envoy/source/common/grpc/google_async_client_impl.cc:49] completionThread running
[2020-07-21 09:11:02.147][3498][debug][config] [external/envoy/source/server/listener_manager_impl.cc:855] starting worker 3
[2020-07-21 09:11:02.148][3635][debug][main] [external/envoy/source/server/worker_impl.cc:125] worker entering dispatch loop
[2020-07-21 09:11:02.151][3635][debug][upstream] [external/envoy/source/common/upstream/cluster_manager_impl.cc:982] adding TLS initial cluster hello_grpc_client
[2020-07-21 09:11:02.151][3638][debug][main] [external/envoy/source/server/worker_impl.cc:125] worker entering dispatch loop
[2020-07-21 09:11:02.151][3638][debug][upstream] [external/envoy/source/common/upstream/cluster_manager_impl.cc:982] adding TLS initial cluster hello_grpc_client
[2020-07-21 09:11:02.151][3640][debug][grpc] [external/envoy/source/common/grpc/google_async_client_impl.cc:49] completionThread running
[2020-07-21 09:11:02.151][3498][warning][main] [external/envoy/source/server/server.cc:537] there is no configured limit to the number of allowed active connections. Set a limit via the runtime key overload.global_downstream_max_connections
[2020-07-21 09:11:02.147][3637][debug][main] [external/envoy/source/server/worker_impl.cc:125] worker entering dispatch loop
[2020-07-21 09:11:02.152][3637][debug][upstream] [external/envoy/source/common/upstream/cluster_manager_impl.cc:982] adding TLS initial cluster hello_grpc_client
[2020-07-21 09:11:02.152][3641][debug][grpc] [external/envoy/source/common/grpc/google_async_client_impl.cc:49] completionThread running
[2020-07-21 09:11:02.152][3639][debug][grpc] [external/envoy/source/common/grpc/google_async_client_impl.cc:49] completionThread running
[2020-07-21 09:11:02.270][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:11:07.160][3498][trace][upstream] [external/envoy/source/common/upstream/strict_dns_cluster.cc:106] starting async DNS resolution for g19sbc.local
[2020-07-21 09:11:07.161][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 5000 milliseconds
[2020-07-21 09:11:07.281][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:11:12.164][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 10000 milliseconds
[2020-07-21 09:11:12.303][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:11:17.306][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:11:22.165][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 20000 milliseconds
[2020-07-21 09:11:22.311][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:11:27.310][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:11:32.313][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:11:37.319][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:11:42.168][3498][trace][upstream] [external/envoy/source/common/network/dns_impl.cc:196] Setting DNS resolution timer for 40000 milliseconds
[2020-07-21 09:11:42.324][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:11:47.327][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:11:52.333][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:11:57.339][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats
[2020-07-21 09:12:02.345][3498][debug][main] [external/envoy/source/server/server.cc:189] flushing stats

Envoy uses c-ares for DNS lookups and as far as I know c-ares does not support mDNS.


M3-5726: Update and Improve PayPal Payment Limits and Logic

Description 📝

Surface any API errors that happen when we make a payment with PayPal

Previously we just showed a generic error
This is important because the API may return something like { "errors": [ { "reason": "Maximum amount is $2000.00" } ] }

Makes Paypal and Google pay buttons use updated limit logic

Ask me for the link to this if you need to see it

Preview 📷
Before
https://user-images.githubusercontent.com/115251059/208533774-b2972e0a-cd31-4613-905f-416969e3c841.mov
After
https://user-images.githubusercontent.com/115251059/208533725-02db67e4-1579-43a3-b78f-2c53b3fc8fd7.mov
How to test 🧪

I recommend testing with local development or development environment
Test one-time payments in the make a payment drawer (/account/billing/make-payment)
Verify logic is correct with internal documentation (ask me for links)

LGTM! Thank you @bnussman-akamai for addressing the feedback.

Thanks for the help on this! @cpathipa 🚀


Table reservation Management - Page UI design

design Page UI
preferably 2 modes for table choosing:

Table asset + form for choosing time (like for Client)
Timeline, idea:

Tables as list elements
occupancy looks like Gantt Chart

beside above: section with options for managing

postponed to Sprint 4


Addresses pom.xml review comments

Summary of this pull request:

[Remove deprecated "configuration-as-code-support" dependency]
[ Bumped to LTS 2.138.1, which is the oldest LTS I can produce a successful build with]
[ Bumped JCasC to 1.22]

Passes unit tests and builds successfully on my local machine.
CC @martinda @casz

@BenjaminBeggs Can you present this PR to the EWS plugin directly?


[Front] Cleaning: Remove plan column from workspace table

Related task

Deploy plan:

Deploy front with sequelize model updated
Run the sql drop in prod


Include Github URL to TODO comment in issue

Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[x] If my change requires a change to the documentation, I have updated the documentation accordingly.
[x] I have added tests to cover my changes.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Describe changes

Include Github URL to TODO comment in issue

Let me know if you want to know something specific and I'll explain it :)


added a commented description to the has_many/has_one :through example of Schema

After some confusion about has_many/has_one :through I was requested to improve the has_many/has_one :through documentation. Hopefully the comment will prevent other people from having the same issue.

I moved the comment up and corrected the wording

Merged manually, thank you

:+1:


dop feedback lab

Step 7, add a note to tell the reader to move on to stop 8 while the workload runs.

Fixed by putting in comments in the readme about 10 second execution and using XEProfiler to confirm. Then can use possibly more uses with -n to get eligiblity.


metadata-scripts: improve script download testing

I improved the architecture in order to allow several startup-script
flavors: GCS download (authenticated and unauthenticated), URL download
and directly from metadata.
Note: Sometimes the shutdown-script messages are not printed. I noticed
it specially when there is no shutdown-script to execute (on this case,
it should print something like "shutdown-script: INFO No shutdown
scripts found in metadata.").

@adjackura Follow up of https://github.com/GoogleCloudPlatform/compute-image-tools/pull/471#discussion_r201855481 discussion

/ok-to-test

Please note #483 that is affecting this workflow (I see lots of failures because the shutdown-script text is not matched, but it doesn't happen all the time. I assume it's a daisy issue and the distribution is actually consistently printing that)


Can this be used in ROS 2?

Or what modifications do I need to make if I want to use it in ROS2

Good question. I haven't looked into ROS 2 control yet. Since the control algorithms are abstracted in a base class, these do not need to be touched. The ROS 1 integration is already a wrapper around them, so it might be comparably easy to make this ROS 2 compliant.
If you have the time to look into it, you can take a look at the cartesian_controllers library that already did the ROS 2 port.
A pull request would definitely appreciated. Unfortunately I would not have time to look into a ROS 2 port in the next months myself.

any update on this one?

I learned a bit more about ros2_control in the meantime and it should be relatively to port this package.
However, I am afraid that I will not have any time myself to do this before February.
If anyone is interested in doing this and to send in a pull request, that would be greatly appreciated.

agreed, since the code is nicely structured, this shouldn't be too difficult. Might give this a go, but currently busy doing other things as well. For reference https://github.com/lbr-stack/lbr_fri_ros2_stack/issues/163


[#5989] The credential type of ADLSTokenCredentialProvider is not equal to the credential type of ADLSTokenCredential

What changes were proposed in this pull request?
ADLSTokenCredentialProvider use the credential type from ADLSTokenCredential
Why are the changes needed?
Fix: #5989
Does this PR introduce any user-facing change?
no
How was this patch tested?
add test

@jerryshao @yuqi1129 @orenccl please help to review when you have time, thanks

What happen when they are not equals?

What happen when they are not equals?

Gravitino server support credential vending too, if not equal, the server side creates a credential with type A. On the client side, it couldn't deserialize the credential, because the service loader uses the credential type like B from credential.

What happen when they are not equals?

no bad effect, but we'd better keep it consistent to make the system simple

LGTM.

updating the PR to replace adls-sas-token with adls-token for the credential type of ADLSTokenCredential to keep with other credential types like s3-token, oss-token, gcs-token, please help to review again

Nice cleanup.

@FANNG1 can you please rebase the PR to fix the conflicts?

@FANNG1 can you please rebase the PR to fix the conflicts?

updated


if the path is not a directory raise an OSError

Checks if the path is a directory or not, if not raise an OSError, else continue.

Coverage decreased (-0.1%) to 73.211% when pulling 491213e413d398a4a4d9d7b7baed4c582f1c8c93 on jetbird:hotfix/oserror-when-path-is-no-dir into 1f121db3dbc508b07ff7169edf267db7ed97d657 on nficano:master.

@nficano Hey man I fixed the case when the path does not match a directory by raising an OSError. Check it :)


Random values out of normal range on most items - JBD BMS Bluetooth

Most of the entities suffer random out of range values on some updates44 - shown here a temperature log and also a SOC sample...
I note a similar issue raised for JK but the latest updates have not fixed this issue for me with the JDB.

Looks like the BLE connection is poor and data is scrambled. checksum verification is currently missing for JBD.
i'll have a look at this

I have the same issue, the signal is strong, yet from time to time data seems to be random
I might look at it and implement it.


docs: Hedera Custodian Library

https://github.com/hashgraph/hedera-custodians-library

resolved in 82e2a18