Attach build number to setup packages

@Microsoft/fsharp-compiler

Looks good, pending build completion.

Scenario meets the bar for consideration.

@OmarTawfik @brettfo Does merging this into master imply we are pulling in other changes that are not yet in the product?

@natidea no. this commit will be cherry picked into preview 5.


TaoBench reporting does not adjust for duration

When shortening duration of the taobench benchmark, if the experiment time is shorter than 5 mins  it reports samples from the warmup period.

Addressed in 0ea0fab


Incident bucket

Changes
Introduce incident events.
TBD: schema and README updates
Partially-fixes: #59
Signed-off-by: Andrea Frittoli<EMAIL_ADDRESS>Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has the primer doc been updated if a design decision is involved
[ ] Have the JSON schemas been updated if the specification changed
[ ] Has spec version and event versions been updated according to the versioning policy
[x] Meets the CDEvents contributor standards

Reference hackmd: https://hackmd.io/h8DBfgwLQuKR7JyUPy0Xow

About the naming of the new bucket. I believe it should be without an 's' in the end. So "Continuous Operation" instead of "Continuous Operations"

About the naming of the new bucket. I believe it should be without an 's' in the end. So "Continuous Operation" instead of "Continuous Operations"

Could you elaborate on why we should remove the "s"? As far as I can see from searching the internet, the practice is commonly referred to as "continuous operations" with the "s". One example https://www.gartner.com/en/information-technology/glossary/continuous-operations

About the naming of the new bucket. I believe it should be without an 's' in the end. So "Continuous Operation" instead of "Continuous Operations"

Could you elaborate on why we should remove the "s"? As far as I can see from searching the internet, the practice is commonly referred to as "continuous operations" with the "s". One example https://www.gartner.com/en/information-technology/glossary/continuous-operations

Well, I actually mostly use the term "continuous operations" myself, but when I google on "continuous operations" and compare it to "continuous operation", the singular version is much more common it seems. And our other buckets are named in singular.
We still have the possibility to change things like this before we reach 1.0, but it will probably hurt a bit if we do so I'd like us to make conscious decisions on names like these.
Let's bring it to our workgroup meeting later today and set it there.

Merging as discussed in the working group.


Issue 60/resolvers and mocking

These patches allow to specify both resolvers and mocks options in a call to apolloServer. It is motivated by the need to define a resolveType function for mocking union types.
Related issues:
#60
https://github.com/apollostack/apollo-starter-kit/issues/9

Coverage increased (+0.006%) to 97.33% when pulling e83226aa3ed9c77179f11dbd60439144ddc50dbe on diegonc:issue-60/resolvers-and-mocking into 24c8abbfd94f90d08347a4566a2fbefb0c8f7d61 on apollostack:master.

This looks great, thanks a lot!
In case you're interested, there's the slightly more challenging feature of default mocks for interfaces that could also use a PR (https://github.com/apollostack/graphql-tools/issues/34#issuecomment-216963165). Do you want to take a stab at it? I've written down exactly what needs to be done, and I think it wouldn't be hard for you since you already did this PR!
After that, I think the mocks would support every language feature in GraphQL!

Here's the comment that explains what needs to be done for Interfaces.
https://github.com/apollostack/graphql-tools/issues/34#issuecomment-221422670


#0: Update to gcc-12.x, take 2

Update to gcc-12.x, this is an update to https://github.com/tenstorrent/tt-metal/pull/12332
a few compile time limits needed relaxing
One grayskull test appears non-deterministic. See https://github.com/tenstorrent/tt-metal/issues/12931
Ticket:
N/A
Problem description:
gcc 10 is old
What's changed:
Update from gcc-10 to gcc-12
updated binaries in sfpi component
The earlier update failed due to a benign misconfiguration in the gcc-10 port that was no longer benign in gcc-12. That is addressed in this PR.
Checklist:

[x] Post commit CI passes
[x] Blackhole Post commit (if applicable)
[x] Model regression CI testing passes (if applicable)
[ ] New/Existing tests provide coverage for changes

Could you run device perf and see if anything needs to be adjusted? I think some models needed to be updated when gcc 12 went in before
https://github.com/tenstorrent/tt-metal/actions/workflows/perf-device-models.yaml

Could you run device perf and see if anything needs to be adjusted? I think some models needed to be updated when gcc 12 went in before https://github.com/tenstorrent/tt-metal/actions/workflows/perf-device-models.yaml

Seems there are fails -- this GS one might be the above-mentioned ND maybe?

Could you run device perf and see if anything needs to be adjusted? I think some models needed to be updated when gcc 12 went in before https://github.com/tenstorrent/tt-metal/actions/workflows/perf-device-models.yaml

Seems there are fails -- this GS one might be the above-mentioned ND maybe?

The Bert one is unrelated and also fails on main. this won't cause the pipeline to fail though. It's the resnet perf threshold that needs to be updated causing it to fail.


Fails to install with older versions of npm

The '^' specifier used in package.json is not available on versions of the semver module (used by npm) bundled with older versions of node (for example, 0.8.3). This will cause npm installs to fail with the following error:
npm ERR! Error: No compatible version found<EMAIL_ADDRESS>

Versions of npm which are unable to handle the '^ver' notation are likely malfunction in other ways as well.  Considering that, I would suggest either upgrading npm or locking the version to 0.10.0.

@mudukutore that sounds good. Are you able to test and submit a pull request?

Yes, will do.


Do not stringify (double quote) non string values.

The transformation {"name" : "some text", "age" : 12}
results in {"name" : "some text", "age" : "12"}
See, that the age value 12 is now a string and not an integer anymore.

Hello,
Can someone fix this please ? :)

+1
I tried to use the tool fro transforming ARM templates for Azure.
Arguments in ARMs are strongly typed -- so any transforms fail the template -- i.e. sort of useless for areas that require non-strings ....
how about an arg in the "xpath" that types it with string as the default?
"path1/path2@int": 1200


Create ru_ru.json

The necessary information such as Stone wand, iron wand or infinity wand is not displayed in the key "construction and.description.and": "%1$s

What do you mean with "the necessary information is not displayed in the key"? Is the placeholder not being filled in correctly?

Okay, I can see the issue:


Allow for running initialization scripts

Applies to mssql-server-linux, issue #11, adding functionality to mount initialization scripts and execute them when the container is started.
When a container is started for the first time, it will execute any files with extensions .sh or .sql that are found in /docker-entrypoint-initdb.d. Files will be executed in alphabetical order. You can easily populate your SQL Server services by mounting scripts into that directory and provide custom images with contributed data.

Looks like this may also help resolve issue #2 and #49

@shanegenschaw - Thanks for submitting this PR.  Our plan is to add this functionality to a hopefully near future release of SQL Server.  The current thinking is that we would have the sqlservr process execute these SQL scripts on startup as opposed to a .sh with sqlcmd.  That way we can have a universal solution for SQL on Linux and on Windows.  The sqlservr process could look for an env variable which contained either a directory path to a set of files or a json formatted list of full paths to files.  What do you think about that approach?

@twright-msft - your approach sounds fantastic. Good idea to have a universal & consistent solution across platforms. Thanks for your consideration!

OK cool.  We'll get 'er done then.  We'll close out this PR since it will be implemented in a different but conceptually similar way.  Thanks for contributing and keep the suggestions/PRs coming!

@twright-msft Was this ever done? Not able to find any docs about it. For now I'm trying to run an entrypoint.sh but that doesn't work since you have to call /opt/mssql/bin/sqlservr first to start up sql server and that never returns. ex:
#!/bin/sh

/opt/mssql/bin/sqlservr
# the above never returns so the script below doesn't get run... :(
/opt/mssql-tools/bin/sqlcmd -S localhost -U sa -P ${SA_PASSWORD} -i /setup.sql

Take a look at this example:
https://github.com/twright-msft/mssql-node-docker-demo-app

Any luck on having a better solution?

Our plan is to add this functionality to a hopefully near future release of SQL Server.

Any chance this can be in 2022? 😊

Something to look at...
https://github.com/tracker1/mssql-docker-enhanced

Thank you but I am looking for official Microsoft support

Mysql, MariaDb, Postgress, even Oracle has the classic
    volumes:
     - ./my/database:/docker-entrypoint-initdb.d

@shanegenschaw your approach was good. No body uses windows for docker :(

+1, it's been five years, let's be realistic and not let the perfect be the enemy of the good. Can this please get re-opened and merged?


Angular 7 Breakpoints are not hit

Issue Type: Bug

I start up my backend in ASP.NET Core 2.2 (no issues)
I type in NG Serve (no issues)
I then use open debugger and select the "Launch Chrome against localhost with sourcemaps"
Browser opens fine, but no breakpoints in application are hit.

I suspect this has something to do with WebPack but am not sure.
Here's the launch.json
`{
"version": "0.2.0",
"configurations": [
{
"name": "Launch Chrome against localhost, with sourcemaps",
"type": "chrome",
"request": "launch",
"url": "http://localhost:8080/dashboard",
"sourceMaps": true,
"webRoot": "${workspaceFolder}/somepath/src/app"
},
]
}`
I am able to set break points in Chrome where the TS SourceMaps work as expected.
Expected Results: Breakpoints should be hit in Visual Studio Code.
Actual Results: Once browser opens, the breakpoints all become greyed out.
VS Code version: Code 1.35.0 (553cfb2c2205db5f15f3ee8395bbd5cf066d357d, 2019-06-04T01:17:12.481Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (12 x 3696)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.84GB (22.23GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (7)

Extension
Author (truncated)
Version

csharp
ms-
1.19.1

powershell
ms-
2019.5.0

debugger-for-chrome
msj
4.11.3

csharp2ts
raf
0.0.22

markdown-preview-enhanced
shd
0.4.1

vscode-scss-formatter
sib
1.4.1

markdown-all-in-one
yzh
2.3.1

Do any of the debugging tips on https://github.com/microsoft/vscode-chrome-debug#the-scripts-command help? How did you pick that webRoot?

.scripts command not found in Debug console.
"sourceMaps": true,
"webRoot": "${workspaceFolder}/UI/projectname/src/app"
When I set a breakpoint, the breakpoint window shows the path and is enabled.  Those paths all contain the webRoot as shown above, but as soon as debug starts those breakpoints are disabled.

.scripts command not found in Debug console.

Are you sure you typed it correctly?

How could I not type .scripts correctly? Debug console gave me the error.

Sorry, I just have to ask the obvious question because I am not sure what the problem would be. What error exactly do you see when you type .scripts?

Also you can set "trace": true in your launch config and upload the log here. It writes the log path to the debug console.


nixos-rebuild no longer works

nixos-rebuild runs nix --extra-experimental-features 'nix-command flakes' build. I would expect nix-monitored to remove --extra-experimental-features and run nom build but it didn't.
I think it was broken by https://github.com/ners/nix-monitored/commit/f4abdaf9c69044492b27d70be7315575ce300384

Thanks for reporting the issue! Can you check if it was fixed in https://github.com/ners/nix-monitored/commit/42716246502d3aef15f598f9af27479665df13d7?

I'm trying to check but I can't rebuild my system at all. How might I bypass the nix-monitored binary?

nix-monitored can also be bypassed by setting the environment variable NIX_MONITOR=disable, in which case it will pass all the args untouched to the underlying Nix package.


adding the FQDN for  example.

adding the FQDN for  example.

/assign @tengqm

@fqsghostcloud @tengqm sorry to hold this one up, but every time I see a URL that we don't control and would need to monitor to keep up-to-date, I worry. Does this information add sufficient value to warrant the risk of the link changing without us knowing about the change? Also, it's not the FQDN of the individual private docker registry -- it can't be, because that's known only to the owners of the registry.
Can you explain why we need this change? Thanks!
/assign

@Bradamant3 I think this is okay. They are just specifying the value to use for DockerHub, which is commonly used. I've seen another PR for this, so I think there's a need.
/lgtm
/approve


InformerConfiguration doesn't properly inherit parent configuration if configuration is overridden

The InformerConfiguration needs to be notified of the configuration override somehow.

Should we also propagate the label selector of the parent reconciler by default or not?

A potential problem is also that, right now, we cannot specify that a dependent should watch all the namespaces even if its parent doesn't. The reason is that we inherit the parent's configuration if no configuration is set on the dependent. However, the default configuration is to watch all namespaces, signified by an empty namespaces field on the annotation. Therefore, if the annotation is left with the default value to signify the associated informer / dependent should watch all namespaces but the parent sets a non-empty set of namespaces then the child configuration will be overridden. We would therefore need a marker value for dependents / informers to say they want to explicit watch all namespaces regardless of the parent configuration.


Getting (OAuth2.Error) :closed when calling OAuth2.Client.get_token!/4

I've implemented the OAuth2 flow similar to the example. I'm connecting to Microsoft's Azure OAuth2 provider. My auth flow works in the development environment, but when I try to deploy it to our production environment with SSL, I get the following error when I reach the get_token portion of the code in which I try to request for an access_token.
Request: GET /auth/callback?code=<omitted>&session_state=<omitted>
** (exit) an exception was raised:
    ** (OAuth2.Error) :closed
        (oauth2) lib/oauth2/client.ex:248: OAuth2.Client.get_token!/4
        (arrow_directory) web/controllers/auth_controller.ex:33: ArrowDirectory.AuthController.callback/2
        (arrow_directory) web/controllers/auth_controller.ex:1: ArrowDirectory.AuthController.action/2
        (arrow_directory) web/controllers/auth_controller.ex:1: ArrowDirectory.AuthController.phoenix_controller_pipeline/2
        (arrow_directory) lib/arrow_directory/endpoint.ex:1: ArrowDirectory.Endpoint.instrument/4
        (arrow_directory) lib/phoenix/router.ex:261: ArrowDirectory.Router.dispatch/2
        (arrow_directory) web/router.ex:1: ArrowDirectory.Router.do_call/2
        (arrow_directory) lib/arrow_directory/endpoint.ex:1: ArrowDirectory.Endpoint.phoenix_pipeline/1
        (arrow_directory) lib/plug/debugger.ex:123: ArrowDirectory.Endpoint."call (overridable 3)"/2
        (arrow_directory) lib/arrow_directory/endpoint.ex:1: ArrowDirectory.Endpoint.call/2
        (plug) lib/plug/adapters/cowboy/handler.ex:15: Plug.Adapters.Cowboy.Handler.upgrade/4
        (cowboy) /opt/app/deps/cowboy/src/cowboy_protocol.erl:442: :cowboy_protocol.execute/4

What would cause the :closed exception?

Hi @albertchan,
This looks like the connection is being closed for some reason. This is coming from the underlying HTTP client (hackney). Most likely it is returning {:error, :closed} when the request was made.
Since you are using get_token! you are getting an exception for this. If you remove the ! you should get {:error, :closed} instead.
You can start debugging this in 2 ways:

Turn on debugging in the OAuth2 app:

config :oauth2, debug: true

Enable tracing in hackney:

:hackney_trace.enable(:max, :io)


Conflict with autoCreateSubnetworks

I was following the documentation once again to deploy an environment and ran into this issue when trying to deploy cloud foundry:
Error applying plan:

2 error(s) occurred:

* google_compute_subnetwork.cf-compilation-subnet-1: Error creating subnetwork: googleapi: Error 400: Invalid value for field 'resource.ipCidrRange': '<IP_ADDRESS>/16'. Extended subnetworks in auto subnet mode networks cannot overlap with <IP_ADDRESS>/9., invalid
* google_compute_address.cf-tcp: Quota 'STATIC_ADDRESSES' exceeded.  Limit: 1.0

The one I want to focus on is the first one that has a conflict with the auto subnet range <IP_ADDRESS>/9.
These are the ranges, and  yes they would conflict:
<IP_ADDRESS>/9 - auto assign
<IP_ADDRESS> - <IP_ADDRESS>
<IP_ADDRESS>/16 - compilation_subnet
<IP_ADDRESS> - <IP_ADDRESS>
To get around this I just changed the compilation range to be <IP_ADDRESS>/16.
Hash is current master
https://github.com/cloudfoundry-incubator/bosh-google-cpi-release/blob/7bcae95f5a070bbc12ced2faf58f83d023e1ac95/docs/cloudfoundry/cloudfoundry.tf#L48
Google Network reference - Last updated Oct 18, 2017
https://cloud.google.com/compute/docs/reference/latest/networks

Property name
Value
Description

autoCreateSubnetworks
boolean
When set to true, the network is created in "auto subnet mode". When set to false, the network is in "custom subnet mode". In "auto subnet mode", a newly created network is assigned the default CIDR of <IP_ADDRESS>/9 and it automatically creates one subnetwork per region.

Thank you for checking this out and digging in @cxhercules ! Really great bug report/doc.
I've fixed/merged this as #236 which disables the auto networks. It's possible as we get more GCP regions that it would become an issue in the future.
I'll work on getting develop released so this doesn't trip anyone else up.

Thanks I will close pull request I put in then thanks!

@johnsonj Although as you said this would be issue in future, also thinking the api would still complain since the range for compilation systems is still within auto subnet range. I think declaring those outside auto subnet range would fix this for now. Let me know what you think.

The referenced fix (#236) disabled the auto creation of subnets so it can't conflict. You may need to delete your infrastructure and re-create it for the change to apply. You could also manually delete the auto created subnets.
autoCreateSubnetworks is nice for convenience/the default network. It's an anti pattern when you're manually defining subnets as we are in the CPI documentation. It's very easy to create subnets if you're creating a network in terraform.

I gotcha ok then thank you!


Passive tense

Dear,
I wanted you to know it is harder to study a text full of passive tense sentences:
Why write: "Contains data involving something that belongs to or that can be viewed by the whole organization"
If you can keep it light and simple as in: "Contains data involving something that belongs to or that the whole organization can be view"
can be viewed by... why not write X can view. This is used troughout a lot of your course texts and burdens the reader.

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

ID: 69b90e8a-7ab9-41f4-5d3c-3dc2b3877640
Version Independent ID: 4cbd5681-f4cb-0053-12e4-196955dce01e
Content: Introduction to entities (Developer Guide for Dynamics 365 Customer Engagement (on-premises))
Content Source: ce/customerengagement/on-premises/developer/introduction-entities.md
Product: d365ce-op
GitHub Login: @JimDaly
Microsoft Alias: jdaly

@Stepnwolf78
Thank you for your feedback. Agree active language is best.

Hi Jim,Indeed, using active tense in texts keeps them readable.Sincerely,PieterjanVan: Jim Daly @.>Verstuurd: vrijdag 16 september 2022 21:51Aan: MicrosoftDocs/dynamics-365-customer-engagement @.>CC: Stepnwolf78 @.>; Mention @.>Onderwerp: Re: [MicrosoftDocs/dynamics-365-customer-engagement] Passive tense (#2387)
@Stepnwolf78
Thank you for your feedback. Agree active language is best.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


ocamlPackages.*: huge update because everything is linked, send help

Update a bunch of packages in ocamlPackages.

If we merge https://github.com/NixOS/nixpkgs/pull/162383 we can probably drop a bunch of tezos packages and then we can merge this.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 165661 run on x86_64-linux 1

1 package failed to build and are new build failure:

ligo: log was empty

Result of nixpkgs-review pr 165661 run on x86_64-linux 1

56 packages built:

acgtk
beluga
comby
coqPackages.coq-elpi
coqPackages.graph-theory
coqPackages.hierarchy-builder
coqPackages.mathcomp-analysis
coqPackages.serapi
coqPackages.trakt
csvtool
dune-release
easycrypt
eff
flitter
flow
framac
fstar
haxe (haxe_4_2)
hxcpp (haxePackages.hxcpp)
haxePackages.hxcs
haxePackages.hxjava
haxePackages.hxnodejs_4
haxe_4_0
haxe_4_1
jackline
libbap
ligo
liquidsoap
ocaml-crunch
ocaml-top
ocamlformat (ocamlformat_0_21_0)
ocamlformat_0_11_0
ocamlformat_0_12
ocamlformat_0_13_0
ocamlformat_0_14_0
ocamlformat_0_14_1
ocamlformat_0_14_2
ocamlformat_0_14_3
ocamlformat_0_15_0
ocamlformat_0_15_1
ocamlformat_0_16_0
ocamlformat_0_17_0
ocamlformat_0_18_0
ocamlformat_0_19_0
ocamlformat_0_20_0
ocamlformat_0_20_1
opam-installer
patdiff
python310Packages.bap
python39Packages.bap
reason
satysfi
soupault
stog
wayland-proxy-virtwl
why3

This PR got a bit out of hand, I started updating ringo and then had to fix more packages which lead me to have to fix more packages.
I'm not sure how to handle such a large PR as this honestly and I'm not sure each commit builds on it's own or if that is even possible.
We might be able to slice it for updates related to cstruct and updates related to cmdliner but some of the packages most likely needs both changes.
cc @vbgl and @sternenseemann since you're the maintainers of most of the updated packages.

Closing as (most) packages are up-to-date now.


Blank page during sign-in

Description
Blank screen after hitting cancel or back on Accepting the terms.
Steps to reproduce

Go to GC Forms
Sign in
Don't accept terms
Hit back

Details

Browser: Edge
Operating system: Mac
Environment: Staging
Language: French
Viewport: Desktop

Expected behaviour
Back to sign in maybe?
Screenshots or videos

Does this happen outside of edge?

Sign in
Enter security code
Land on acceptable use page
Press browser back button

I'm seeing the session expired screen
https://github.com/cds-snc/platform-forms-client/assets/62242/a8c50ed6-cabf-4aad-a562-9a6c670d5d3c

I only saw it on Edge, haven't been able to replicate in Chrome.
Though on the "Know your responsibilities" page you can click on "Forms" in the top nav or on the GC Forms logo and get a blank page also, in both Edge and Chrome.


changed default validator order to go by voting power highest to lowest

Sorting by voting power tend to increase top validators voting power.
Would be super cool to display validators like https://pod.kujira.app/phoenix-1


About the Weight Initialization in PL

Hi,
I am tring to use BERT for a project. The pretrained BERT model is part of my model. I am wondering how will PL initialize the model weights. Will it overwrite the pretrained BERT weights?
Thanks.

lightning doesn’t do any magic like this under the hood. you control all the weights and what gets initiated

I see. So where should I do the weight initialization step? In the __init__ of pl.LightningModule

This is up to you and you should follow standard PyTorch guidelines.
Normally it's done in init


#155 Update reference sequence numbering diagram

See #155

Here's the sole change:
https://hgvs-nomenclature--156.org.readthedocs.build/156/background/numbering/#figure
Compare with
https://hgvs-nomenclature.org/background/numbering/#figure

Good catch @ahwagner !


Feature/263541 landing page

## WHAT
[FE] Update Landing page
## WHY
https://c5qcgij075a.sg.larksuite.com/base/KMusbYyPXamBwYs0tQNl9ZREgld?table=tblqPvBWouRYz76w&view=vewGXMNZGI
## NOTES

This MR is solid and tailors the right problem

:tada: This PR is included in version 1.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Unable to import bulk Box/Case Diemensions from Database

Unable to import bulk Box/Case Diemensions from Database

I am unsure of what you are talking about?
Are we dealing with online database?


Observe kernel limit of 1024 items for readv/writev calls

This commit takes into account the kernel maximum of 1024 iov
items passed to a readv/writev call.
man 2 readv:

To deal with the fact that IOV_MAX was so low on early versions of
Linux, the glibc wrapper functions for readv() and writev() did some
extra work if they detected that the underlying kernel system call
failed because this limit was exceeded.

Starting with glibc version 2.9,
the wrapper functions provide this behavior only if the library
detects that the system is running a Linux kernel older than version
2.6.18 (an arbitrarily selected kernel version).  And since glibc
2.20 (which requires a minimum Linux kernel version of 2.6.32), the
glibc wrapper functions always just directly invoke the system calls.

This should be libc::IOV_MAX instead of a magic number.

@sifkarov  what are your thoughts on @asomers' comment?

@carllerche I can't remember my original rationale but I agree with @asomers on second thought.
After a quick glance it doesn't look like libc exposes the constant, but I'm not familiar with that crate's structure off hand. I'll have to dive a bit deeper and possibly land something there first?

@asomers Do you have thoughts on how to get MAX_VALUE?

POSIX says that IOV_MAX may be variable, and should be checked at runtime.  The correct way to do that is to use sysconf.  With Nix, you would do it like this:
https://play.rust-lang.org/?gist=e3d4fb15c73b371fced35c29548279d3&version=stable&mode=debug
However, for certain operating systems, IOV_MAX is hard-coded.  This is the case for FreeBSD and Linux; I haven't checked any of the others.  For those operating systems, the value is defined in limits.h, and should be added to libc.


Great plugin but I have a feature suggestion

Thank you for making this plugin . the auto layout option is great but sadly it ignores and changes the entire arrangement of cards within a group prior to card changes and only propagates new cards in a vertical direction .
it there a way it could do auto layout of cards on the group level and not for all the cards on canvas ?
also is there a way we could collab to make it do this ? :
https://www.reddit.com/r/ObsidianMD/comments/1ekmfa5/obsidian_canvas_is_pretty_awesome_but_it_can_be/
https://github.com/user-attachments/assets/d432f85c-b357-4064-877a-163adf780405
https://github.com/user-attachments/assets/3a1acdf1-89f6-47e2-b476-aa55c61ed460

I'm open to PR's. This isn't something I have a need for or have time to work on.

that's alright , thanks for replying.


Fix background of MenuFlyout in white high contrast

Description

Swap out the brush we use for high contrast for MenuFlyout background to a brush that adheres more to the background of the app.
Motivation and Context

Fixes #2432
How Has This Been Tested?

Tested manually
Screenshots (if appropriate):

High contrast 1

High contrast 2

High contrast black

High contrast white

/azp run


Implement the embedded_hal_async::delay::DelayUs trait

This trait as added in one of the alpha releases, and we never implemented it. This trait will need to be implemented in order to use future versions of embassy.

This trait has been around since the 0.1 release of the eha, but didn't really need to implement it as embassy-time offers an impl based on the time driver impls. If we were to implement this we should impl on the following

Systimer (alarms only)
TIMG timers
Xtensa internal CPU timers (maybe)
Anything else that has a configurable time period + interrupt? Maybe something in the RTC domain

Once https://github.com/esp-rs/esp-hal/issues/1063 is solved we can revisit this issue.

This trait is implemented for SYSTIMER directly, and is additionally implemented for OneShotTimer; since the timer::timg module still does not contain an asynch module of its own, I'm just going to close this as "completed".


[Bug] Misleading preview of API actions' data field in entity explorer

Description
In the entity explorer under API actions, the {{Api1.data}} field's value shows a small preview icon. When the mouse is hovered over it, we get a preview of the value. This preview is incorrect. It shows the whole action response instead of just the body.
Steps to reproduce the behaviour:

Create an API action (for example, to http://httpbin.org/get)
Save and run this action.
Expand this API action in the entity explorer and find the {{Api1.data}} entry.
Hover the mouse over the little preview icon near this entry in the entity explorer.
Compare this body with what {{Api1.data}} renders as, in a label widget.

Screenshot:

Important Details

Version: Cloud
OS: macOS
Browser: Firefox

@sharat87 great catch!


Travis and Gh-pages needed for the repo

Anyone with experience in python notebooks that can help to configure the repo to serve https://github.com/ypriverol/CompProt2019-paper/blob/master/source/transform_poll.ipynb as python notebooks using travis.
ping @bittremieux

What exactly do you want to do? If you just want to make an exploratory analysis of the data available the notebook will work just fine. I'm not sure what Travis has to do with that?

I would like to have a way that the current Jupyter note get publish in the repo (gh-pages for example) for other users. In the future, if you do a PR and I accept that PR, I would like to update the report automatically. The report would be for non-developer users.
Is that possible?

I found the way. Now results can be checked here. https://ypriverol.github.io/CompProt2019-paper/ I'm now working in the notebook !!!!


.setList not setting date input nor a number input

Hello all,,
I'm having an issue with the setList function whereby its not setting the values for a number field nor a date field,
<input type="number" name="pet_treat" value="" class="form-control" />
<input type="date" name="pet_birthday" value="" class="form-control" />

setList(
  [
    {
      "pet_treat": "2",
      "pet_birthday": "18-05-2020",
    }
   ]
)

end up getting the error:
jquery.min.js?ver=3.6.1:2 Uncaught TypeError: Cannot read properties of undefined (reading 'set')
it works if I change the inputs to type="text, select and checkbox is working fine, just for some reason date and number field.
Any advice?
Cheer

@MrJoshFisher I am facing a similar problem, did you find a solution?

@ #112 For future developers who run into this problem. I did not set the type property on the input which caused the issue.

@MrJoshFisher I am facing a similar problem, did you find a solution?
Edit: I am facing the exact same problem

No I didn't, I ended up using a different library entirely which was the basic jquery repeater library.

Now I'm currently facing the same problem, is there already any solution for this?

Now I'm currently facing the same problem, is there already any solution for this?

Afraid not I ended up using a different library

Actually input type date and number is missing in the bundle file, so we can solve the issue by adding simple codes in 3 places.
nu = function (a) {                 var b = {},                     c = x(a, b);                 return (                     (c.getType = function () {                         return "number";                     }),                     c                 );             },             dt= function (a) {                 var b = {},                     c = x(a, b);                 return (                     (c.getType = function () {                         return "date";                     }),                     c                 );             }, in variable declation section
        `number:nu,
         date:dt` in function A  variable assignment

: f.is('input[type="number"]')                             ? i("number", f)                             : f.is('input[type="date"]')                             ? i("date", f)
and i("number", 'input[type="number"]'),                           i("date", 'input[type="date"]'),
in return of function A

I have made a simple change and that works

This fixed the issue for me. Thank you.

i am using NPM so updating the source file is not preferable, I ended up using type="text" in HTML then change the type to "number" in the show function
HTML:
<div data-repeater-list="rewards">
    <div data-repeater-item>
        <input name="quantity" type="text" min="1" value="1" class="form-control"/>
    </div>
</div>

JS:
$('#repeater').repeater({
    initEmpty: false,
    show: function () {
        $(this).slideDown();
        this.querySelector('input[name$="[quantity]"]').setAttribute('type', 'number');
    },
    hide: function (deleteElement) {
        $(this).slideUp(deleteElement);
    },
});


Config file and env var for istioctl --istioNamespace, --xds-address, and --cert-dir

Resolves https://github.com/istio/istio/issues/23868
This was discussed on the UX meeting.  It turned out to be easier than I thought.  Looking for feedback.
Users can export environment variables export ISTIOCTL_ISTIONAMESPACE=my-istio-system or create ~/.istioctl/config.yaml with this format:
# istioctl default values

# Note that these values can be overridden by exporting ISTIOCTL_<name>
# For example
#   export ISTIOCTL_XDS_ADDRESS=localhost:15010

# Uncomment to test with local instance of discovery
# XDS_ADDRESS: localhost:15012

# Uncomment to test with local INSECURE instance of discovery
# xds_address: localhost:15010

# Uncomment to use a different Istio namespace
#istioNamespace: another-namespace

# Note that cert_dir doesn't take shell variables such as $HOME or ~; it must be a literal absolute path
cert_dir: /Users/snible/go/src/istio.io/istio/tools/certs/msd-istioctl

Currently only those three variable are exposed in this way, but I am happy to discuss others.

@esnible: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
0a2ac2649e9b89ab8b760f33ea0e47d92edd200c
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
0a2ac2649e9b89ab8b760f33ea0e47d92edd200c
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
0a2ac2649e9b89ab8b760f33ea0e47d92edd200c
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest
flaky mcflake

Do we want to add something to update the config via the CLI?

@liamawhite Something like istioctl config set istioNamespace istio-system?
And istioctl config list, and istioctl config get <key>?
I suspect it wouldn't be hard to implement.

Yes 🙂

@esnible: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
ab770269a018279c7c946a0474de05c5b5fcb641
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
ab770269a018279c7c946a0474de05c5b5fcb641
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
ab770269a018279c7c946a0474de05c5b5fcb641
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
ab770269a018279c7c946a0474de05c5b5fcb641
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
ab770269a018279c7c946a0474de05c5b5fcb641
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@esnible: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-telemetry-k8s-tests_istio

unit-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-telemetry-k8s-tests_istio

unit-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Adding hold to address comments from UX meeting.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
023b7e4426c9462f7964c242384394abf7a975ae
link
/test integ-telemetry-k8s-tests_istio

unit-tests_istio
1abdff66243dde5be22d803fc9378c67711d53cd
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
1abdff66243dde5be22d803fc9378c67711d53cd
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
1abdff66243dde5be22d803fc9378c67711d53cd
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
1abdff66243dde5be22d803fc9378c67711d53cd
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1abdff66243dde5be22d803fc9378c67711d53cd
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
1abdff66243dde5be22d803fc9378c67711d53cd
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
1abdff66243dde5be22d803fc9378c67711d53cd
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1abdff66243dde5be22d803fc9378c67711d53cd
link
/test integ-telemetry-k8s-tests_istio

lint_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
1abdff66243dde5be22d803fc9378c67711d53cd
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1abdff66243dde5be22d803fc9378c67711d53cd
link
/test integ-telemetry-k8s-tests_istio

lint_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test lint_istio

unit-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
1abdff66243dde5be22d803fc9378c67711d53cd
link
/test integ-telemetry-k8s-tests_istio

lint_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test lint_istio

unit-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
1abdff66243dde5be22d803fc9378c67711d53cd
link
/test integ-telemetry-k8s-tests_istio

lint_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test lint_istio

unit-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test release-test_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test lint_istio

unit-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test integ-telemetry-k8s-tests_istio

lint_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test integ-telemetry-k8s-tests_istio

lint_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test lint_istio

unit-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test integ-telemetry-k8s-tests_istio

lint_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test lint_istio

unit-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test integ-telemetry-k8s-tests_istio

lint_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test lint_istio

unit-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test release-test_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test lint_istio

unit-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test integ-telemetry-k8s-tests_istio

unit-tests_istio
c9db08c830ed1aa22e85c2f3d21bf8ffc4161270
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
e3b4abb29809a29b0ee6a62e7a45675ea5fd8f71
link
/test integ-telemetry-k8s-tests_istio

unit-tests_istio
c9db08c830ed1aa22e85c2f3d21bf8ffc4161270
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
c9db08c830ed1aa22e85c2f3d21bf8ffc4161270
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
c9db08c830ed1aa22e85c2f3d21bf8ffc4161270
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
c9db08c830ed1aa22e85c2f3d21bf8ffc4161270
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
c9db08c830ed1aa22e85c2f3d21bf8ffc4161270
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
c9db08c830ed1aa22e85c2f3d21bf8ffc4161270
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
df622af8d31f8ca6b612a7ba5ae9223a549aba32
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
df622af8d31f8ca6b612a7ba5ae9223a549aba32
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
df622af8d31f8ca6b612a7ba5ae9223a549aba32
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
df622af8d31f8ca6b612a7ba5ae9223a549aba32
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
df622af8d31f8ca6b612a7ba5ae9223a549aba32
link
/test integ-telemetry-k8s-tests_istio

lint_istio
5a83eb2ebb05917552972e39f01e5c581b8d96ee
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
3be82d7e554e24c2f3b340b579dd44d9942d0ca8
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
3be82d7e554e24c2f3b340b579dd44d9942d0ca8
link
/test gencheck_istio

release-notes_istio
11d05fad76577ecbbc4cbc87e4d6f730dbdd79d8
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
11d05fad76577ecbbc4cbc87e4d6f730dbdd79d8
link
/test release-notes_istio

unit-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
11d05fad76577ecbbc4cbc87e4d6f730dbdd79d8
link
/test release-notes_istio

unit-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test unit-tests_istio

integ-mixer-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-mixer-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
11d05fad76577ecbbc4cbc87e4d6f730dbdd79d8
link
/test release-notes_istio

unit-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test unit-tests_istio

integ-mixer-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-mixer-k8s-tests_istio

integ-operator-controller-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-operator-controller-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
11d05fad76577ecbbc4cbc87e4d6f730dbdd79d8
link
/test release-notes_istio

unit-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test unit-tests_istio

integ-mixer-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-mixer-k8s-tests_istio

integ-operator-controller-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-operator-controller-tests_istio

integ-galley-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-galley-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
11d05fad76577ecbbc4cbc87e4d6f730dbdd79d8
link
/test release-notes_istio

unit-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test unit-tests_istio

integ-mixer-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-mixer-k8s-tests_istio

integ-operator-controller-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-operator-controller-tests_istio

integ-galley-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-galley-k8s-tests_istio

gencheck_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
11d05fad76577ecbbc4cbc87e4d6f730dbdd79d8
link
/test release-notes_istio

unit-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test unit-tests_istio

integ-mixer-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-mixer-k8s-tests_istio

integ-operator-controller-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-operator-controller-tests_istio

integ-galley-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-galley-k8s-tests_istio

gencheck_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test gencheck_istio

integ-security-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
11d05fad76577ecbbc4cbc87e4d6f730dbdd79d8
link
/test release-notes_istio

unit-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test unit-tests_istio

integ-mixer-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-mixer-k8s-tests_istio

integ-operator-controller-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-operator-controller-tests_istio

integ-galley-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-galley-k8s-tests_istio

gencheck_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test gencheck_istio

integ-security-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-security-k8s-tests_istio

lint_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test unit-tests_istio

integ-mixer-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-mixer-k8s-tests_istio

integ-operator-controller-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-operator-controller-tests_istio

integ-galley-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-galley-k8s-tests_istio

gencheck_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test gencheck_istio

integ-security-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-security-k8s-tests_istio

lint_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test lint_istio

release-notes_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test unit-tests_istio

integ-mixer-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-mixer-k8s-tests_istio

integ-operator-controller-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-operator-controller-tests_istio

integ-galley-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-galley-k8s-tests_istio

gencheck_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test gencheck_istio

integ-security-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-security-k8s-tests_istio

lint_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test lint_istio

release-notes_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test release-notes_istio

integ-ipv6-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-ipv6-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test unit-tests_istio

integ-mixer-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-mixer-k8s-tests_istio

integ-operator-controller-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-operator-controller-tests_istio

integ-galley-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-galley-k8s-tests_istio

gencheck_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test gencheck_istio

integ-security-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-security-k8s-tests_istio

lint_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test lint_istio

release-notes_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test release-notes_istio

integ-ipv6-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-ipv6-k8s-tests_istio

release-test_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test release-test_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test unit-tests_istio

integ-mixer-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-mixer-k8s-tests_istio

integ-operator-controller-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-operator-controller-tests_istio

integ-galley-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-galley-k8s-tests_istio

gencheck_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test gencheck_istio

integ-security-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-security-k8s-tests_istio

lint_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test lint_istio

release-notes_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test release-notes_istio

integ-ipv6-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-ipv6-k8s-tests_istio

release-test_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test unit-tests_istio

integ-mixer-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-mixer-k8s-tests_istio

integ-operator-controller-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-operator-controller-tests_istio

integ-galley-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-galley-k8s-tests_istio

gencheck_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test gencheck_istio

integ-security-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-security-k8s-tests_istio

lint_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test lint_istio

release-notes_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test release-notes_istio

integ-ipv6-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-ipv6-k8s-tests_istio

release-test_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test unit-tests_istio

integ-mixer-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-mixer-k8s-tests_istio

integ-operator-controller-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-operator-controller-tests_istio

integ-galley-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-galley-k8s-tests_istio

gencheck_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test gencheck_istio

integ-security-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-security-k8s-tests_istio

lint_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test lint_istio

release-notes_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test release-notes_istio

integ-ipv6-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-ipv6-k8s-tests_istio

release-test_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test unit-tests_istio

integ-mixer-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-mixer-k8s-tests_istio

integ-operator-controller-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-operator-controller-tests_istio

integ-galley-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-galley-k8s-tests_istio

gencheck_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test gencheck_istio

integ-security-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-security-k8s-tests_istio

lint_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test lint_istio

release-notes_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test release-notes_istio

integ-ipv6-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-ipv6-k8s-tests_istio

release-test_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test unit-tests_istio

integ-mixer-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-mixer-k8s-tests_istio

integ-operator-controller-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-operator-controller-tests_istio

integ-galley-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-galley-k8s-tests_istio

gencheck_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test gencheck_istio

integ-security-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-security-k8s-tests_istio

lint_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test lint_istio

integ-ipv6-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-ipv6-k8s-tests_istio

release-test_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
a94469cd6c3306e0b5eff4691fab8a97ffdd40cb
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-mixer-k8s-tests_istio

integ-operator-controller-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-operator-controller-tests_istio

integ-galley-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-ipv6-k8s-tests_istio

release-test_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
0c856b3a49c38a76fa34f0c9efc573ce75d36afa
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
a94469cd6c3306e0b5eff4691fab8a97ffdd40cb
link
/test release-notes_istio

unit-tests_istio
a94469cd6c3306e0b5eff4691fab8a97ffdd40cb
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
a94469cd6c3306e0b5eff4691fab8a97ffdd40cb
link
/test release-notes_istio

unit-tests_istio
a94469cd6c3306e0b5eff4691fab8a97ffdd40cb
link
/test unit-tests_istio

integ-security-k8s-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test integ-security-k8s-tests_istio

unit-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test integ-security-k8s-tests_istio

unit-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test integ-security-k8s-tests_istio

unit-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-k8s-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test integ-security-k8s-tests_istio

integ-multicluster-k8s-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@esnible: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test integ-security-k8s-tests_istio

unit-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
cd75c995b331b623eae3819c6ebaf22a0693fc0b
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-multicluster-k8s-tests_istio


Measurement Value Distributions is not informative enough

The numerical range of measurement values hugely varies depending on the units used, and even within one unit it varies a lot due to mistakenly recorded outliners. So this graph becomes hard or impossible to read - small values aren't shown - there's basically no place to hover to get the result.
Here, for example

Is it possible to add the tabular view including column with counts, so the user can sort by count,
or add the option to show the N most frequently used units in a graph? - this might not work perfectly as there might be results measured in thousand/ml and million/ml, for example, for the same measurement, and values will be 1000 times different

Add a tabular view to the data source release measurement concept report.  Similar to what appears o the network measurement report.  (#/cdm/DATA_SOURCE/DATA_SOURCE_RELEASE/measurement/CONCEPT_ID)

A table is now available on the report to make this easier to interpret.


Incorrect date on photo upload

I uploaded a photo for this bench: https://openbenches.org/bench/18350
The image date was 16th March 2020, however it says "8th Dec 2002"!

Interesting! The EXIF reports two different dates.
  'exif:DateTime' => '2020:03:16 12:50:49',
  'exif:DateTimeDigitized' => '2002:12:08 12:00:00',
  'exif:DateTimeOriginal' => '2020:03:16 12:50:49',

See https://openbenches.org/image/e03670a800432471ceb90650371d4d4f06dada3b/exif
Did you upload from your phone directly?

No. I copied the photo from my old phone as part of a larger backup (not in 2002 though!), and uploaded it from my laptop yesterday.

Interesting. The code is at:
https://github.com/openbenches/openbenches.org/blob/313804a98472973b00b6e50220c130f0b572a2f9/www/functions.php#L325
I think I need to reverse that. Start by using the GPSDateStamp, and use the DateTimeDigitized at the end.
Thanks for flagging this up. I'll update the database this weekend, and look at updating the code.


RxJava support/extension

Hi :)
Do you plan to add some support to RxJava in near future?

Coroutines has a flow/rxjava adapter library, would this fit your use case or do we need more support?
https://kotlin.github.io/kotlinx.coroutines/kotlinx-coroutines-rx2/kotlinx.coroutines.rx2/kotlinx.coroutines.flow.-flow/as-observable.html

Closing due to inactivity. Let me know if anything extra is needed


Need better infrastructure for detecting unintentional breaking changes to analyzer

The analyzer package has a lot of clients that are widely used in open source, and several of them import code from package:analyzer/src/....  As a result, we occasionally make changes to the analyzer that don't break the officially-supported analyzer API, but in practice break an important client.  To make sure that we don't publish a version of the analyzer that would cause a widespread ecosystem breakage, we need a way to detect these "de facto" breaking changes early so we can revert them.
In the past, our best signal for detecting these breaking changes has been to notice them when we roll the analyzer into the Google internal codebase, however that roll process has been becoming more atomic, so that signal is becoming less reliable.  It would be really nice to have a strong signal for detecting such breakages that doesn't rely on any internal infrastructure.

If we believed that is was possible for the analyzer to publish an API that clients wouldn't need to circumvent, then it seems to me that we'd have enough information to know what is and is not a breaking change. I don't know whether that's a reasonable scenario, but might be worth considering.

See #42163 for a specific example of the kind of unintentional breaking change that I hope we could avoid with better testing

One possible way we could address this using testing would be to set up a bot with a list of "known important" packages.  For each published version of each of those packages, it does the following:

Check whether the package's analyzer dependency includes the bleeding edge version of the analyzer.  If it doesn't, skip it.
Download the package into a temporary directory.
Modify the package's pubspec, adding a dependency override to point to the bleeding edge analyzer.
Run pub get
Run some sanity checks (e.g. analyze the package, run pub run test if the package supports it)

It might be too slow a process to run on every single commit, but we could certainly run it on a regular basis.

If we believed that is was possible for the analyzer to publish an API that clients wouldn't need to circumvent, then it seems to me that we'd have enough information to know what is and is not a breaking change. I don't know whether that's a reasonable scenario, but might be worth considering.

Agreed, if we had confidence that were feasible, it would sure be nice.  My personal feeling is that it isn't feasible, based on several observations:

We've been talking about trying to get the analyzer's API into a "1.0" state for years and we still seem pretty far from achieving it (at least measured by the number of client packages that import from lib/src).  Granted, a 1.0 state is not necessarily the same thing as "no clients have to import from lib/src" but I think it's reasonable to assume that the effort to achieve the two goals is in the same ballpack of difficulty.
In our past efforts to get to a 1.0 state and get clients to stop importing from lib/src, it hasn't simply been a matter of moving the analyzer APIs that are actually used out of lib/src; we've often found tht the client packages are using the analyzer in the "wrong" way (or, at least, in a way that we think is a bad idea and don't want to support as an official part of the public API), and that it takes a lot of coding work to get the clients to use the analyzer in the "right" way.
Even if we can get into a state where clients aren't importing from lib/src, it's possible that a client will be relying on a behavior that doesn't obviously manifest in the analyzer's public API signatures (e.g. expecting a specific error message when handling invalid code).  It would be nice if we had a way to notice breakages caused by these assumptions too.

That's not to say that we shouldn't continue trying to move toward a 1.0 state and to reduce the amount of imports of lib/src; those are good ideals and we should keep working toward them.  But IMHO it will take a long time to reach them (if ever), and I think a testing based solution would be really helpful in the meantime.


bookinfo example ,reviews CrashLoopBackOff

i find this at 0.6.0 release.
kubectl version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.4", GitCommit:"bee2d1505c4fe820744d26d41ecd3fdd4a3d6546", GitTreeState:"clean", BuildDate:"2018-03-12T16:29:47Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2017-12-15T20:55:30Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}

pods inof
NAME                              READY     STATUS             RESTARTS   AGE
details-v1-6f7fd69b94-9hkjf       2/2       Running            2          19h
productpage-v1-79cbdcffcd-kw4l2   2/2       Running            2          19h
ratings-v1-b7d64b98-bj2jg         2/2       Running            2          19h
reviews-v1-68b9b796bb-4mmxq       1/2       CrashLoopBackOff   239        19h
reviews-v2-77c8bbbb9d-zwhm5       1/2       Error              239        19h
reviews-v3-bfd8b47cd-lcn5k        1/2       CrashLoopBackOff   239        19h

istio info
NAME                   DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
deploy/istio-ca        1         1         1            1           19h
deploy/istio-ingress   1         1         1            1           19h
deploy/istio-mixer     1         1         1            1           19h
deploy/istio-pilot     1         1         1            1           19h

NAME                          DESIRED   CURRENT   READY     AGE
rs/istio-ca-59f6dcb7d9        1         1         1         19h
rs/istio-ingress-779649ff5b   1         1         1         19h
rs/istio-mixer-7f4fd7dff      1         1         1         19h
rs/istio-pilot-5f5f76ddc8     1         1         1         19h

NAME                   DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
deploy/istio-ca        1         1         1            1           19h
deploy/istio-ingress   1         1         1            1           19h
deploy/istio-mixer     1         1         1            1           19h
deploy/istio-pilot     1         1         1            1           19h

NAME                          DESIRED   CURRENT   READY     AGE
rs/istio-ca-59f6dcb7d9        1         1         1         19h
rs/istio-ingress-779649ff5b   1         1         1         19h
rs/istio-mixer-7f4fd7dff      1         1         1         19h
rs/istio-pilot-5f5f76ddc8     1         1         1         19h

NAME                                READY     STATUS    RESTARTS   AGE
po/istio-ca-59f6dcb7d9-n8mrz        1/1       Running   1          19h
po/istio-ingress-779649ff5b-687k4   1/1       Running   1          19h
po/istio-mixer-7f4fd7dff-lrd6m      3/3       Running   3          19h
po/istio-pilot-5f5f76ddc8-jxljk     2/2       Running   2          19h

NAME                TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)                                                            AGE
svc/istio-ingress   LoadBalancer   <IP_ADDRESS>    <pending>     80:30564/TCP,443:30401/TCP                                         19h
svc/istio-mixer     ClusterIP      <IP_ADDRESS>   <none>        9091/TCP,15004/TCP,9093/TCP,9094/TCP,9102/TCP,9125/UDP,42422/TCP   19h
svc/istio-pilot     ClusterIP      <IP_ADDRESS>    <none>        15003/TCP,8080/TCP,9093/TCP,443/TCP                                19h

kubectl logs deployment/reviews-v1 istio-proxy
[2018-03-23 05:06:48.845][13][info][upstream] external/envoy/source/server/lds_api.cc:60] lds: add/update listener 'http_<IP_ADDRESS>_9093'
[2018-03-23 05:06:48.845][13][info][upstream] external/envoy/source/server/lds_api.cc:60] lds: add/update listener 'tcp_<IP_ADDRESS>_15004'
[2018-03-23 05:06:48.846][13][info][upstream] external/envoy/source/server/lds_api.cc:60] lds: add/update listener 'tcp_<IP_ADDRESS>_42422'
[2018-03-23 05:06:48.846][13][info][upstream] external/envoy/source/server/lds_api.cc:60] lds: add/update listener 'tcp_<IP_ADDRESS>_9091'
[2018-03-23 05:06:48.846][13][info][upstream] external/envoy/source/server/lds_api.cc:60] lds: add/update listener 'tcp_<IP_ADDRESS>_9094'
[2018-03-23 05:06:48.846][13][info][upstream] external/envoy/source/server/lds_api.cc:60] lds: add/update listener 'tcp_<IP_ADDRESS>_9102'
[2018-03-23 05:06:48.846][13][info][upstream] external/envoy/source/server/lds_api.cc:60] lds: add/update listener 'tcp_<IP_ADDRESS>_443'
[2018-03-23 05:06:48.849][13][warning][upstream] external/envoy/source/server/lds_subscription.cc:68] lds: fetch failure: route: unknown cluster 'in.9080'
[2018-03-23 05:06:49.714][13][info][upstream] external/envoy/source/common/upstream/cluster_manager_impl.cc:356] add/update cluster in.9080

...

2018-03-23T05:10:40.134381Z     info    Received 404 status from pilot when retrieving availability zone: AvailabilityZone couldn't find the given cluster node
2018-03-23T05:11:10.135603Z     info    Received 404 status from pilot when retrieving availability zone: AvailabilityZone couldn't find the given cluster node
2018-03-23T05:11:40.136577Z     info    Received 404 status from pilot when retrieving availability zone: AvailabilityZone couldn't find the given cluster node
2018-03-23T05:12:10.137857Z     info    Received 404 status from pilot when retrieving availability zone: AvailabilityZone couldn't find the given cluster node
2018-03-23T05:12:10.137892Z     info    Availability zone not set, proxy will default to not using zone aware routing.
[2018-03-23 05:12:29.821][13][info][upstream] external/envoy/source/common/upstream/cluster_manager_impl.cc:356] add/update cluster in.9080
[2018-03-23 05:12:31.562][13][info][upstream] external/envoy/source/common/upstream/cluster_manager_impl.cc:391] removing cluster in.9080
[2018-03-23 05:22:41.934][13][info][upstream] external/envoy/source/common/upstream/cluster_manager_impl.cc:356] add/update cluster in.9080
[2018-03-23 05:22:43.139][13][info][upstream] external/envoy/source/common/upstream/cluster_manager_impl.cc:391] removing cluster in.9080

@s332401890 i believe you need to move this ticket to https://github.com/istio/issues/issues
by the way fyi i have exactly same issue

@s332401890 can you please re-try with 0.7?


Remove explicit FutureReturnValueIgnored from ErrorProne

By default, all ErrorProne Error patterns are checked. There is no
need to explicitly list FutureReturnValueIgnored as an error pattern.
Only error conditions that you do not wish to check for should be
explicitly listed (with the OFF setting).
Note that it is the opposite for Warning patterns. With the current
configuration you must list any warning patterns you wish to check.

I mistakenly thought the FutureReturnValueIgnored pattern was an ErrorProne error by default, but it is actually just a warning. But it is a warning we wish to check for, therefore the line cannot be removed. The PR will be close without implementation.