Auto rename of the path in Android Studio on moving a file

Use case
In Android Studio when we Move or Drag and Drop a file to a different folder, the path of the referenced file changes to
C:\Users\user_name\Desktop\project\app\lib\main.dart. As a result,

Hot Reload doesn't work for the code in that particular file.
If the code is opened on a different PC it'll show an error as the path is relative to the system.

I have personally faced this issue and recently saw another user facing the same issue  #68945.
Proposal
This used to work fine before. Not sure when it changed. So, it'd be great if the path be renamed as package:app\lib\main.dart instead of C:\Users\user_name\Desktop\project\app\lib\main.dart

Hi @melwinlobo18
Looks like a duplicate of https://github.com/flutter/flutter-intellij/issues/4740
Following the indication of jetbrains' Flutter plugin, the correct way to address the problem is to open an issue in the dedicated repository.
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Closed groups with request-to-join feature

In #324 there was a mention of closed groups. This issue it to discuss that. I guess it needs a "request to join" feature too. Would probably also depend on having admins in practise (see #356).
A fancy version would be to enable an online conversation between the prospective new user and the admins of the group (would depend on #539 being implemented).

Seems to be similar to #894, closing this in favor of the newer issue.


upload distribution to private nexus

I'd like to publish a python package with pybuilder to a private repository.
Following command works (username, password and url in ~/.pypirc):

twine upload -r nexus --config-file ~/.pypirc target/dist/cm_fubar-0.1.0/dist/cm_fubar-0.1.0-py3-none-any.whl

[distutils]
index-servers =
    nexus
[nexus]
repository:https://nexus/repository/pypi/
username:fubar
password:fupass

How do I get the same result with pybuilder using the dist plugin?
With following snippet I get prompted to enter a password.
from pybuilder.core import use_plugin, init

use_plugin("python.core")
use_plugin("python.unittest")
use_plugin("python.install_dependencies")
use_plugin("python.flake8")
use_plugin("python.coverage")
use_plugin("python.distutils")

name = "cm_fubar"
default_task = "publish"
version = "0.1.0"

@init
def set_properties(project):
    project.set_property("dir_source_unittest_python", "src/test/python")
    project.set_property("distutils_upload_repository", "https://nexus/repository/pypi/")

    project.set_property("distutils_commands", ['sdist', 'bdist_wheel', 'upload'])

When I enter a password it terminates with following error:
running clean
removing 'build/lib' (and everything under it)
removing 'build/bdist.linux-x86_64' (and everything under it)
removing 'build/scripts-3.6' (and everything under it)
removing 'build'
running upload
error: No dist file created in earlier command

Using following option seems to work but looks hideous:
project.set_property("distutils_commands", ['sdist', 'bdist_wheel'])
    project.set_property('publish_command', 'twine upload -r nexus --config-file ~/.pypirc target/dist/cm_fubar-%s/dist/cm_fubar-%s-py3-none-any.whl' % (version, version))

How is this done properly?

Hi, @reimarstier.
Check please #421. Maybe it's Your situation.
If no - write and I'll have look.
Thanks.

Yeah the upload task works:
@init
def set_properties(project):
    project.set_property("dir_source_unittest_python", "src/test/python")
    project.set_property("distutils_upload_repository", "https://nexus/repository/pypi/")

Thanks :-)


MNT: rerender

Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #87.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.

[ ] Bump the build number if needed

Fixes #87

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.


Add capability to create recurrent task

Describe the solution you'd like
Everything is in the title

#67


Enable dp

fixes https://github.com/kubevirt/kubevirt/issues/1185

@vladikr Discussions on the mailing list indicated 1.9.X is a critical path in CI. I think that's already well tested?

The patch looks good.
I suggest letting the discussion on the mailing list play out a bit further before merging. If we can get away with it, I'd rather we drop 1.9/3.9 support.

I believe the general consensus is that we are not going to maintain compatibility with Kubernetes 1.9. If that's the case, this PR should be closed as it is exclusively about maintaining functionality in older versions.

@stu-gott I think you can close it now.


Page is scrolling by default

The view is 100px larger than 100% even if the page does not need that space.

Window is now always exactly 100% viewport height (at least on "normal" devices)

This fix was reverted with commit https://github.com/ImisDevelopers/1_011_a_infektionsfall_uebermittellung/commit/aa778f7e4de99daea3430a5c16295d87400ed699
So im not sure if I should reimplement it

For me, the only page still scrolling (even though it wouldn't be necessary) is the patient registration. I don't know how other browsers/displays handle that though. In my opinion we can leave it like that for now. What do you think @lordpomeroy ?


Use saturating_sub instead of - for unsigned ints

This fixes a panic if the operation with the unsigned ints would result in a negative number

Codecov Report

Merging #1530 (7b855d0) into main (3675a51) will decrease coverage by 0.02%.
The diff coverage is 100.00%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1530      +/-   ##
==========================================
- Coverage   68.74%   68.73%   -0.02%
==========================================
  Files         120      120
  Lines       13094    13094
==========================================
- Hits         9002     9000       -2
- Misses       4092     4094       +2

Hey @rumpl  , the formatting check is failing in the CI. Can you run cargo fmt, and push again. Also if possible, can you amend the current commit instead of adding a new one for formatting.
I am also curious if we should do a similar saturating operation for other additions or subtractions related to such cgroups values. What do you think?

Hey, I created a new PR that only fixes formatting, the failures are unrelated to the changes I made here, the PR: #1532

I am also curious if we should do a similar saturating operation for other additions or subtractions related to such cgroups values. What do you think?

I looked briefly but didn't see any other code where there are subtractions with unsigned ints

@rumpl May I ask you to rebase from the latest main branch?

@utam0k done :+1:

Thanks a lot!


Using Microsoft Telnet in Windows Terminal display and inputs bug

Environment
Windows build number: 10.0.18363.1082
Windows Terminal version (if applicable):1.2.2381.0

Microsoft Telnet

Steps to reproduce

Using Microsoft Telnet in Windows Terminal, if the output lines more then the window size, the scroll bcak context display is wrong。

And then, if changing the window size smaller, input will be failed too.

Expected behavior
1.the scroll bcak context display shuld be correct.
2.input  shuld be ok.

Actual behavior

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #6056 for more discussion.
/dup #6056


Migrate the code from TXTDirect and add the base files

What this PR does / why we need it:
Migrates the code from TXTDirect and adds the base files using Reposeed
Which issue this PR fixes:
fixes #1

/lgtm


error:Could not find the requested service node_exporter.service: host

运行ansible-playbook start.yml
时，报：
Ansible FAILED! => playbook: start.yml; TASK: start node_exporter by systemd; message: {"changed": false, "msg": "Could not find the requested service node_exporter.service: host"}
我的处女(男？)提就献给你们了

Default process_supervision in inventory.ini is systemd:
# process supervision, [systemd, supervise]
process_supervision = systemd

see https://github.com/pingcap/docs-cn/blob/master/op-guide/ansible-deployment.md#如何调整进程监管方式从-supervise-到-systemd.
You need to run deploy.yml before start.yml if you're deploying a new cluster.

已经是 process_supervision = systemd ，如上图
已经 执行过ansible-playbook deploy.yml，如下图

解决了。
解决步骤：
ansible-playbook stop.yml
ansible-playbook deploy.yml -D
ansible-playbook start.yml
谢谢。

What's your Linux OS version? Could you provide the contents of your inventory.ini?

1,
lsb_release -a
LSB Version:    :core-4.1-amd64:core-4.1-noarch
Distributor ID: CentOS
Description:    CentOS Linux release 7.4.1708 (Core)
Release:        7.4.1708
Codename:       Core
2,
TiDB Cluster Part
[tidb_servers]
<IP_ADDRESS>
<IP_ADDRESS>
[tikv_servers]
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
[pd_servers]
<IP_ADDRESS>
<IP_ADDRESS>
[spark_master]
[spark_slaves]
Monitoring Part
prometheus and pushgateway servers
[monitoring_servers]
<IP_ADDRESS>
[grafana_servers]
<IP_ADDRESS>
node_exporter servers
[monitored_servers]
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
Binlog Part
[pump_servers:children]
tidb_servers
Group variables
[pd_servers:vars]
location_labels = ["zone","rack","host"]
Global variables
[all:vars]
deploy_dir = /data/home/tidb/deploy
Connection
ssh via normal user
ansible_user = tidb
ssh via root:
ansible_user = root
ansible_become = true
ansible_become_user = tidb
cluster_name = test-cluster
tidb_version = v1.0.8
deployment methods, [binary, docker]
deployment_method = binary
process supervision, [systemd, supervise]
process_supervision = systemd
timezone of deployment region
timezone = Asia/Shanghai
set_timezone = True
enable_firewalld = False
check NTP service
enable_ntpd = True
machine_benchmark = True
set_hostname = False
binlog trigger
enable_binlog = False
zookeeper address of kafka cluster, example:
zookeeper_addrs = "<IP_ADDRESS>:2181,<IP_ADDRESS>:2181,<IP_ADDRESS>:2181"
zookeeper_addrs = "<IP_ADDRESS>:2181,<IP_ADDRESS>:2181,<IP_ADDRESS>:2181,<IP_ADDRESS>:2181,<IP_ADDRESS>:2181"
KV mode
deploy_without_tidb = False

OK. It seems that there's no error in inventory.ini.


Block pulling Windows images on non-Windows daemons

- What I did
fixes #28892
Block pulling Windows images on Linux daemons.
- How I did it
If the listed OS of an image's config is Windows, but the current daemon platform is not Windows, fail to download the image.
- How to verify it
Pull microsoft/nanoserver on a Linux daemon. See test that checks this.
- Description for the changelog

Block pulling of Windows images on a non-windows daemon.
Signed-off-by: Darren Stahl<EMAIL_ADDRESS>/cc @jhowardmsft @jstarks

Instead of downloading the config before starting to download the layers (which will add a noticeable delay), how running p.config.DownloadManager.Download in a goroutine and aborting it by canceling the context if the config turns out to be incompatible?

@aaronlehmann That can't be done on Windows, as some filenames in Linux images are not valid in NTFS resulting in a failure mid download. I'm not sure if it can be done in the Linux case, since the Linux daemon is not aware of foreign layers, the failure is occurring during download, rather than when attempting to run the resulting image. I can try it on Linux pulling a Windows image, but even if it works, it would be diverging the handling between platforms.

If the problem is foreign layers, those are easy to detect before downloading the layers. We could abort the pull if the platform is Linux and any of the descriptors in the manifest has a media type indiciating a foreign layer. That wouldn't require downloading the image config before starting the layer downloads.

The problem isn't only the foreign layers. It just happens that all Windows images have at least one foreign layer, since Windows images must be based off one of the two base images, both of which contain foreign layers. Downloading both the image config and the layers at the same time is a race between which would fail first, and produce a different error depending on which download wins.
I initially avoided this solution (reading image config before layer download), due to the expected performance impact, and did what you are suggesting (checking the layer descriptor before attempting to download a foreign layer). See https://github.com/docker/docker/pull/28903. It was suggested there to fail earlier by doing the same checks that Windows already does on Linux. Both of these solve the same problem, but have different drawbacks.

ping @aaronlehmann @stevvooe any way to get this PR, or https://github.com/docker/docker/issues/28903, moving again?

My preference here is for something like this (untested, only meant to illustrate the idea):
https://github.com/aaronlehmann/docker/tree/block-wrong-os
This runs the download manager in a separate goroutine, so the pullSchema2 function can abort the pull as soon as the config is downloaded, if that config specifies the wrong platform. This doesn't require fully downloading the config before starting the layer downloads on Linux.
The NTFS issue wouldn't be a factor because Windows daemons always download and check the config first. The foreign layer issue on Linux could be solved by adding a check for foreign layers in the loop over mfst.Layers at the top of pullSchema2, before any of these downloads start. This will let us fail even faster than when trying to download a layer.

@darrenstahlmsft
WDYT about @aaronlehmann 's comment?

ping @darrenstahlmsft

also ping @stevvooe PTAL

Updated to be similar to the commit by @aaronlehmann except that in the case of an error downloading the layer, the config download is not cancelled so that the resulting error message takes priority over the layer download failure.
I think that lets us remove the serialization of the Windows config as well. I've left that for a follow-up PR though.

I see that TestEventsPluginOps timed out on both janky and experimental, so I suspect this is causing some problem with pulling plugins.

This looks like the right approach to me. Moving to code review.
Let me know if I can be of any help in tracking down the plugin test issue. Also pinging @dmcgowan who converted plugins to use the pull_v2 code.

Fixed the plugin error, but now it's failing on TestDaemonNoSpaceLeftOnDeviceError, which still seems related. I'll take a look at that tomorrow.

Ah, I think I see the problem that is causing TestDaemonNoSpaceLeftOnDeviceError to hang.
receiveConfig may get an error from the layer downloads on errChan, and afterwards the select below receiveConfig will wait for activity on downloadsDone or errChan, but neither will happen, because the downloading goroutine has already returned and its message on errChan was swallowed up by receiveConfig.
One way to fix this would be to use separate error channels for layer downloads and the config retrieval.

Good catch @aaronlehmann. Fixed the hang.

LGTM ping @anusha-ragunathan @vdemeester


implement observer pattern to refresh category subtree upon global category tree refresh

#411
@lauraluiz please, review
Changes consist of wrapper class that enables thread-safe exchanging of contained category tree.
Observer pattern implementation enables registering and notifying interested listeners (in that case category sub-trees) upon refresh events. The refreshed object notifies its listener which rebuilds it's subtree based on fresh global category tree.
Because of split interfaces projects based on sunrise would need to adjust its guice configuration the same way it was done in this PR.

@lauraluiz tests added

Had to rework all category tree approach in general and dependant category trees are not singleton anymore: https://github.com/commercetools/commercetools-sunrise-java/pull/590


Add ffmpeg fix RuntimeWarning

Didn't test but I assume this should fix this problem.

Description

Motivation and Context

How has this been tested?

Screenshots (if appropriate)
Types of changes

Changes visible to users:

[ ] Bug fix (prefix: fix - non-breaking change which fixes an issue)
[ ] New feature (prefix: feat - non-breaking change which adds functionality)
[ ] Breaking change (prefix: feat!! or fix!! - fix or feature that would cause existing functionality to not work as expected)

Internal changes:

[ ] Refactor (prefix: refactor - non-breaking change which only improves the design or structure of existing code, and making no changes to its external behaviour)
[ ] Tests (prefix: test - additions and improvements to unit tests and the smoke tests)
[ ] Infrastructure (prefix: chore - examples include GitHub Actions, issue templates)

Checklist

[ ] My code follows the code style of this project and passes yarn run lint.
[ ] My change requires a change to the documentation.
[ ] My change works!

I assume so too. Thanks!


fix(dbm-services): 操作db对象需要加上反引号，防止sql异常

关联研发信息
dev_branch: fix/opreation_db_object_with_backtick/#2665
target_branch: v1.3.0


Exception [42P01] SQLSTATE[42P01]: Undefined table

Im using the docker-compose example, and get following errors trying to access the web-page:
Exception [42P01] SQLSTATE[42P01]: Undefined table: 7 ERROR:  relation "awl_db_revision" does not exist
LINE 1: ...ECT schema_major, schema_minor, schema_patch FROM awl_db_rev...
                                                             ^
At line 94 of /usr/share/awl/inc/AwlDatabase.php
================= Stack Trace ===================
/usr/share/davical/htdocs/index.php[10] include()
/usr/share/davical/htdocs/always.php[311] AwlQuery->Exec()
/usr/share/awl/inc/AwlQuery.php[585] AwlQuery->Execute()
/usr/share/awl/inc/AwlQuery.php[396] AwlDatabase->query()
/usr/share/awl/inc/AwlDatabase.php[94] PDO->query()

docker-compose:
version: '3'
services:
  postgres:
    image: postgres:alpine
    ports:
      - '5432:5432'
    environment:
      POSTGRES_PASSWORD: 'postgres'
      POSTGRES_USER: 'postgres'
  davical:
    image: fintechstudios/davical
    build: .
    ports:
      - '4080:80'
    depends_on:
      - postgres
    environment:
      PGHOST: 'postgres'
      PGPASSWORD: 'davical'
      # the following is only needed to run database migrations
      RUN_MIGRATIONS_AT_STARTUP: 'true'
      ROOT_PGUSER: 'postgres'
      ROOT_PGPASSWORD: 'postgres'
      DAVICAL_ADMIN_PASS: 'admin'
      DBA_PGUSER: 'davical_dba'
      DBA_PGPASSWORD: 'davical'

Ah, you're right. Looks like DAViCal 1.1.10 isn't compatible with Postgre 15, which has been published since this image was last updated. You should be able to mitigate this by locking to Postgres 13 (or 14, but that is apparently not officially supported) in the docker-compose.yml. I'll address this in the docs.


prep_for_subm.sh to allow user input of security ports

(mangelajo note: we could even look into doing this from the operator if possible -if we can get the cloud credentials from openshift., otherwise at least subctl)
Currently the SubM ports are hard coded (4500 and 500):
https://github.com/submariner-io/submariner/blob/02e8a4fbece5ae88c9cdcf9ad33c27168b591a6e/tools/openshift/ocp-ipi-aws/ocp-ipi-aws-prep/ec2-resources.tf#L33
https://github.com/submariner-io/submariner/blob/02e8a4fbece5ae88c9cdcf9ad33c27168b591a6e/tools/openshift/ocp-ipi-aws/ocp-ipi-aws-prep/ec2-resources.tf#L40

This issue is referred to in the Quickstart VSphere/AWS guide on website. Once this issue is resolved, the corresponding section has to be updated accordingly.

Still relevant (at least as long as we use this script to configure AWS ports, etc.).


Info panel and smart ordering

Searching in the info panel is a very helpful feature. However, the number of results can be overwhelming, and there is no option to sort them by relevance.

We need to sort the result in the following prioriyn (everything is case insensitive !):

parameter name has an exact match
parameter name starts with
parameter name contains
value contains

@lpatiny Do we only search parameters or even values?
in the current version we search matches in the two


Seperate segmented algorithms for none_of, any_of and all_of

Seperate segmented algorithms for none_of, any_of and all_of
Replace tag_invoke with tag_fallback_invoke
Any background context you want to provide?
Issue #5156
Issue #5204

Can one of the admins verify this patch?


UX: List tagging concept design for recipe containers

Name your app, add a tag for the app to the containers in it
Right now we can't really group the containers of a recipe together - they won't necessarily be part of a pod because the container that serves the model may be involved in multiple different applications.
So the idea here was to mock up something like a tagging system and the containers of a related recipe could be tagged and we could group them by tag?

closing as addressed in other issues


installation: rewrite the code

This PR effectively rewrites the operator/ codebase. Over the past few weeks, I have been looking into refactoring the codebase to both simplify it dramatically, given its new reduced requirements, and allow it to be structured in a way that allows us to evolve our installation strategy. Namely, an increasingly converging behavior with Helm, migration paths to helm, etc. I have spent considerable time attempting to refactor the codebase to do so, and what I have ultimately concluded is that the way the codebase is currently structured is (somewhat subtly, at first glance) extremely problematic.
Aside from usual issues around tech debt and an organically evolving codebase, both of which impact the codebase heavily, there is a systemic issues in how data flows through the system. We have a variety of critical objects:

IstioOperator with values/meshConfig as a Struct
Values translated to a Values, MeshConfig translated to a MeshConfig
All of the above translated to map[string]any
All of the above translated to structpb.Struct
All of the above translated to JSON
All of the above translated to YAML

Through a simple install, we transition between these states an incredible amount of times. In one case, we wanted to translate to an IstioOperatorSpec into an IstioOperator; to do so, we converted to yaml, to a map, back to yaml, then to a Go template, then unmarshalled back into an IstioOperator. While that case is clearly an easy fix, there are many other cases where the structure of the codebase requires us to do constantly move back and forth.
My original attempts at cleaning up the codebase were to simply cleanup the discrepancies with values and meshConfig not being typed. I did two different prototypes of this, one keeping IstioOperator as a proto and another one just using standard Go structs. Both of these were not able to be completed. The root of the problem is we are really inherintly dealing with unstructured data. Most of the codebase is doing things like "merge these two maps", "set values.foo.bar=1", etc -- these are extremely hard to do with structured data. We currently do this with a custom-made library, tpath, which is incredibly complicated to handle all the edge cases of the structured data. Many times we avoid this by translating between various type formats (as discussed above), but this introduces even more complexity, as we have all these alternative paths to manipulate data.
This PR instead treats a map[string]any as the core data structure, wrapped in a values.Map type. Not-coincidentally, this is also how the Helm codebase is structured (originally, I had directly used most of Helm's libraries. However, for backwards compatibility we have different --set semantics unfortunately).
Beyond that, we now have clearly devised installation phases:

Merge all inputs into a single unified configuration
For each component, render the chart. Explicitly apply postprocessing steps (overlays) independently
for manifest generate: print and exit.
for install: apply to the cluster.

This structure should be more conducive to future feature work. For instance, if we want to perform a helm migration tooling, we can easily insert logic after the 'merge all inputs'.
Overall, the intent of this PR is to have no user facing behavioral changes, with two minor exceptions:

istioctl manifest generate --component - filters to one component. Can already be done by just only enabling that component, does not exist on istioctl install
istioctl manifest generate -o <dir> - output files to a dir instead of a file. It hasn't worked since at least 1.18, so I am pretty confident there is no usage

These were excluded just to clean up the code mostly
Fixes https://github.com/istio/istio/issues/52469

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

/test all

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test unit-tests-arm64

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test unit-tests-arm64

gencheck_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test gencheck

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test unit-tests-arm64

gencheck_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test gencheck

integ-basic-arm64_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-basic-arm64

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test unit-tests-arm64

gencheck_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test gencheck

integ-basic-arm64_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-basic-arm64

integ-pilot_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-pilot

integ-distroless_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-distroless

integ-helm_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-helm

integ-ambient_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-ambient

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-sigs/prow repository. I understand the commands that are listed here.

/test all

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test unit-tests-arm64

gencheck_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test gencheck

integ-basic-arm64_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-basic-arm64

integ-pilot_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-pilot

integ-distroless_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-distroless

integ-helm_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-helm

integ-ambient_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-ambient

lint_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test lint

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-basic-arm64

integ-pilot_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-pilot

integ-distroless_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-distroless

integ-helm_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-helm

integ-ambient_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-ambient

lint_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test lint

gencheck_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test gencheck

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-basic-arm64

integ-pilot_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-pilot

integ-distroless_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-distroless

integ-helm_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-helm

integ-ambient_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-ambient

lint_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test lint

gencheck_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test gencheck

integ-pilot-istiodremote-mc_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-istiodremote-mc

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-basic-arm64

integ-pilot_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-pilot

integ-distroless_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-distroless

integ-helm_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-helm

integ-ambient_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-ambient

lint_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test lint

gencheck_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test gencheck

integ-pilot-istiodremote-mc_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-multicluster

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-basic-arm64

integ-pilot_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-pilot

integ-distroless_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-distroless

integ-helm_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-helm

integ-ambient_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-ambient

lint_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test lint

gencheck_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test gencheck

integ-pilot-istiodremote-mc_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-multicluster

integ-telemetry-mc_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-telemetry-mc

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-pilot

integ-distroless_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-distroless

integ-ambient_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-ambient

lint_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test lint

gencheck_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test gencheck

integ-pilot-istiodremote-mc_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-multicluster

integ-telemetry-mc_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-telemetry-mc

integ-security-multicluster_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-security-multicluster

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-pilot

lint_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test lint

gencheck_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test gencheck

integ-pilot-istiodremote-mc_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-multicluster

integ-telemetry-mc_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-telemetry-mc

integ-security-multicluster_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-security-multicluster

integ-ambient_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-ambient

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-sigs/prow repository. I understand the commands that are listed here.

/test all

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-pilot

lint_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test lint

integ-pilot-istiodremote-mc_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-multicluster

integ-telemetry-mc_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-telemetry-mc

integ-security-multicluster_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-security-multicluster

integ-ambient_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-ambient

gencheck_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test gencheck

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-pilot

integ-pilot-istiodremote-mc_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-multicluster

integ-telemetry-mc_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-telemetry-mc

integ-security-multicluster_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-security-multicluster

integ-ambient_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-ambient

gencheck_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test gencheck

lint_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test lint

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-pilot

integ-pilot-istiodremote-mc_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-multicluster

integ-telemetry-mc_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-telemetry-mc

integ-security-multicluster_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-security-multicluster

gencheck_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test gencheck

lint_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test lint

integ-ambient_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-ambient

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-pilot

integ-pilot-istiodremote-mc_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-multicluster

gencheck_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test gencheck

lint_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test lint

integ-ambient_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-istiodremote

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-pilot

integ-pilot-istiodremote-mc_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-multicluster

gencheck_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test gencheck

lint_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test lint

integ-ambient_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-istiodremote

integ-cni_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-cni

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-pilot

integ-pilot-istiodremote-mc_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-istiodremote-mc

gencheck_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test gencheck

lint_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test lint

integ-ambient_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-istiodremote

integ-cni_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-cni

integ-pilot-multicluster_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-multicluster

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
8be5fa890f8ac3fe913926eee27dd03e22dbb31e
link
true
/test integ-pilot

integ-pilot-istiodremote-mc_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-istiodremote-mc

gencheck_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test gencheck

lint_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test lint

integ-ambient_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-istiodremote

integ-cni_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-cni

integ-pilot-multicluster_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-multicluster

integ-security_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-security

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
343d3184748ec880c60e120265d0598475f2feb5
link
true
/test integ-pilot-istiodremote-mc

gencheck_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test gencheck

lint_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test lint

integ-ambient_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-istiodremote

integ-cni_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-cni

integ-pilot-multicluster_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-multicluster

integ-security_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-security

integ-pilot_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test gencheck

lint_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test lint

integ-ambient_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-istiodremote

integ-cni_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-cni

integ-pilot-multicluster_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-multicluster

integ-security_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-security

integ-pilot_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot

integ-pilot-istiodremote-mc_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-istiodremote-mc

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test lint

integ-ambient_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-istiodremote

integ-cni_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-cni

integ-pilot-multicluster_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-multicluster

integ-security_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-security

integ-pilot_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot

integ-pilot-istiodremote-mc_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-istiodremote-mc

gencheck_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test gencheck

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-istiodremote

integ-cni_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-cni

integ-pilot-multicluster_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-multicluster

integ-security_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-security

integ-pilot_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot

integ-pilot-istiodremote-mc_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-istiodremote-mc

gencheck_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test gencheck

lint_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test lint

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-istiodremote

integ-cni_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-cni

integ-pilot-multicluster_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-multicluster

integ-security_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-security

integ-pilot_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot

integ-pilot-istiodremote-mc_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-istiodremote-mc

gencheck_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test gencheck

lint_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test lint

unit-tests-arm64_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test unit-tests-arm64

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-ambient

integ-cni_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-cni

integ-pilot-multicluster_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-multicluster

integ-security_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-security

integ-pilot-istiodremote-mc_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-istiodremote-mc

gencheck_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test gencheck

lint_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test lint

unit-tests-arm64_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test unit-tests-arm64

integ-pilot_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test integ-pilot

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-ambient

integ-pilot-multicluster_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-multicluster

integ-security_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-security

integ-pilot-istiodremote-mc_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-pilot-istiodremote-mc

gencheck_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test gencheck

lint_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test lint

unit-tests-arm64_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test unit-tests-arm64

integ-pilot_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test integ-pilot

integ-cni_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test integ-cni

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security_istio
7da22f2093e024ffcae88ae45aaf187ce3395c60
link
true
/test integ-security

gencheck_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test gencheck

lint_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test lint

unit-tests-arm64_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test unit-tests-arm64

integ-pilot_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test integ-pilot

integ-cni_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test integ-cni

integ-pilot-istiodremote-mc_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test integ-pilot-istiodremote-mc

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test gencheck

lint_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test lint

unit-tests-arm64_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test unit-tests-arm64

integ-pilot_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test integ-pilot

integ-cni_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test integ-cni

integ-pilot-istiodremote-mc_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test integ-pilot-istiodremote-mc

integ-security_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test integ-security

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-sigs/prow repository. I understand the commands that are listed here.

/test all

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test integ-pilot

integ-cni_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test integ-cni

integ-pilot-istiodremote-mc_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test integ-pilot-istiodremote-mc

integ-security_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test integ-security

lint_istio
36cc6d003ea252af4e7c8acd6c7b726156b6c84a
link
true
/test lint

unit-tests-arm64_istio
36cc6d003ea252af4e7c8acd6c7b726156b6c84a
link
true
/test unit-tests-arm64

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test integ-security

lint_istio
36cc6d003ea252af4e7c8acd6c7b726156b6c84a
link
true
/test lint

unit-tests-arm64_istio
36cc6d003ea252af4e7c8acd6c7b726156b6c84a
link
true
/test unit-tests-arm64

integ-pilot-istiodremote-mc_istio
36cc6d003ea252af4e7c8acd6c7b726156b6c84a
link
true
/test integ-pilot-istiodremote-mc

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security_istio
8cc2898e43e5953df66253c1738c098857ad65a8
link
true
/test integ-security

lint_istio
36cc6d003ea252af4e7c8acd6c7b726156b6c84a
link
true
/test lint

unit-tests-arm64_istio
36cc6d003ea252af4e7c8acd6c7b726156b6c84a
link
true
/test unit-tests-arm64

integ-pilot-istiodremote-mc_istio
36cc6d003ea252af4e7c8acd6c7b726156b6c84a
link
true
/test integ-pilot-istiodremote-mc

integ-security-multicluster_istio
36cc6d003ea252af4e7c8acd6c7b726156b6c84a
link
true
/test integ-security-multicluster

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
36cc6d003ea252af4e7c8acd6c7b726156b6c84a
link
true
/test lint

unit-tests-arm64_istio
36cc6d003ea252af4e7c8acd6c7b726156b6c84a
link
true
/test unit-tests-arm64

integ-pilot-istiodremote-mc_istio
36cc6d003ea252af4e7c8acd6c7b726156b6c84a
link
true
/test integ-pilot-istiodremote-mc

integ-security-multicluster_istio
36cc6d003ea252af4e7c8acd6c7b726156b6c84a
link
true
/test integ-security-multicluster

integ-security_istio
36cc6d003ea252af4e7c8acd6c7b726156b6c84a
link
true
/test integ-security

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-sigs/prow repository. I understand the commands that are listed here.

/test all

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
36cc6d003ea252af4e7c8acd6c7b726156b6c84a
link
true
/test lint

unit-tests-arm64_istio
36cc6d003ea252af4e7c8acd6c7b726156b6c84a
link
true
/test unit-tests-arm64

integ-pilot-istiodremote-mc_istio
36cc6d003ea252af4e7c8acd6c7b726156b6c84a
link
true
/test integ-pilot-istiodremote-mc

integ-security_istio
36cc6d003ea252af4e7c8acd6c7b726156b6c84a
link
true
/test integ-security

integ-security-multicluster_istio
f00e94ae58f91c8a2153ee7690684eb74d663e89
link
true
/test integ-security-multicluster

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security_istio
36cc6d003ea252af4e7c8acd6c7b726156b6c84a
link
true
/test integ-security

integ-security-multicluster_istio
f00e94ae58f91c8a2153ee7690684eb74d663e89
link
true
/test integ-security-multicluster

integ-pilot-istiodremote-mc_istio
f00e94ae58f91c8a2153ee7690684eb74d663e89
link
true
/test integ-pilot-istiodremote-mc

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
f00e94ae58f91c8a2153ee7690684eb74d663e89
link
true
/test integ-security-multicluster

integ-pilot-istiodremote-mc_istio
f00e94ae58f91c8a2153ee7690684eb74d663e89
link
true
/test integ-pilot-istiodremote-mc

integ-security_istio
f00e94ae58f91c8a2153ee7690684eb74d663e89
link
true
/test integ-security

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-sigs/prow repository. I understand the commands that are listed here.

/test all

/test all

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
f00e94ae58f91c8a2153ee7690684eb74d663e89
link
true
/test integ-security-multicluster

integ-pilot-istiodremote-mc_istio
f00e94ae58f91c8a2153ee7690684eb74d663e89
link
true
/test integ-pilot-istiodremote-mc

integ-security_istio
f00e94ae58f91c8a2153ee7690684eb74d663e89
link
true
/test integ-security

lint_istio
4d333fdb5f86b00b95462bfa4399265813968d53
link
true
/test lint

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
f00e94ae58f91c8a2153ee7690684eb74d663e89
link
true
/test integ-security-multicluster

integ-pilot-istiodremote-mc_istio
f00e94ae58f91c8a2153ee7690684eb74d663e89
link
true
/test integ-pilot-istiodremote-mc

lint_istio
4d333fdb5f86b00b95462bfa4399265813968d53
link
true
/test lint

integ-security_istio
4d333fdb5f86b00b95462bfa4399265813968d53
link
true
/test integ-security

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
f00e94ae58f91c8a2153ee7690684eb74d663e89
link
true
/test integ-security-multicluster

lint_istio
4d333fdb5f86b00b95462bfa4399265813968d53
link
true
/test lint

integ-security_istio
4d333fdb5f86b00b95462bfa4399265813968d53
link
true
/test integ-security

integ-pilot-istiodremote-mc_istio
4d333fdb5f86b00b95462bfa4399265813968d53
link
true
/test integ-pilot-istiodremote-mc

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-sigs/prow repository. I understand the commands that are listed here.

/test all

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
4d333fdb5f86b00b95462bfa4399265813968d53
link
true
/test lint

integ-security_istio
4d333fdb5f86b00b95462bfa4399265813968d53
link
true
/test integ-security

integ-pilot-istiodremote-mc_istio
4d333fdb5f86b00b95462bfa4399265813968d53
link
true
/test integ-pilot-istiodremote-mc

gencheck_istio
6628f47be5f264f6997ca5f0cd9b3177e0e62ef4
link
true
/test gencheck

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-sigs/prow repository. I understand the commands that are listed here.

/test all

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security_istio
4d333fdb5f86b00b95462bfa4399265813968d53
link
true
/test integ-security

integ-pilot-istiodremote-mc_istio
4d333fdb5f86b00b95462bfa4399265813968d53
link
true
/test integ-pilot-istiodremote-mc

gencheck_istio
6628f47be5f264f6997ca5f0cd9b3177e0e62ef4
link
true
/test gencheck

lint_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test lint

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security_istio
4d333fdb5f86b00b95462bfa4399265813968d53
link
true
/test integ-security

integ-pilot-istiodremote-mc_istio
4d333fdb5f86b00b95462bfa4399265813968d53
link
true
/test integ-pilot-istiodremote-mc

lint_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test lint

integ-ipv6_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-ipv6

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security_istio
4d333fdb5f86b00b95462bfa4399265813968d53
link
true
/test integ-security

lint_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test lint

integ-ipv6_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-ipv6

integ-pilot-istiodremote-mc_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-pilot-istiodremote-mc

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security_istio
4d333fdb5f86b00b95462bfa4399265813968d53
link
true
/test integ-security

lint_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test lint

integ-ipv6_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-ipv6

integ-pilot-istiodremote-mc_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-pilot-istiodremote

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test lint

integ-ipv6_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-ipv6

integ-pilot-istiodremote-mc_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-pilot-istiodremote

integ-telemetry-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-telemetry-istiodremote

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test lint

integ-ipv6_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-ipv6

integ-pilot-istiodremote-mc_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-pilot-istiodremote

integ-telemetry-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-telemetry-istiodremote

integ-security-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-security-istiodremote

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-sigs/prow repository. I understand the commands that are listed here.

/retest

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-pilot-istiodremote-mc

integ-telemetry-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-telemetry-istiodremote

integ-security-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-security-istiodremote

integ-pilot-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-pilot-istiodremote

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-telemetry-istiodremote

integ-security-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-security-istiodremote

integ-pilot-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-pilot-istiodremote

integ-pilot-istiodremote-mc_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-pilot-istiodremote-mc

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-security-istiodremote

integ-pilot-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-pilot-istiodremote

integ-pilot-istiodremote-mc_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-pilot-istiodremote-mc

integ-telemetry-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-telemetry-istiodremote

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-pilot-istiodremote

integ-pilot-istiodremote-mc_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-pilot-istiodremote-mc

integ-telemetry-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-telemetry-istiodremote

integ-security-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-security-istiodremote

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-sigs/prow repository. I understand the commands that are listed here.

/test all

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-pilot-istiodremote-mc

integ-telemetry-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-telemetry-istiodremote

integ-security-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-security-istiodremote

integ-pilot-istiodremote_istio
e5d5aa5fa2123c41609a7695cb3f9e7e3ef58437
link
true
/test integ-pilot-istiodremote

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-telemetry-istiodremote

integ-security-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-security-istiodremote

integ-pilot-istiodremote_istio
e5d5aa5fa2123c41609a7695cb3f9e7e3ef58437
link
true
/test integ-pilot-istiodremote

integ-pilot-istiodremote-mc_istio
e5d5aa5fa2123c41609a7695cb3f9e7e3ef58437
link
true
/test integ-pilot-istiodremote-mc

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio
052565f5219792cb635071a9675ffa25777a643f
link
true
/test integ-security-istiodremote

integ-pilot-istiodremote_istio
e5d5aa5fa2123c41609a7695cb3f9e7e3ef58437
link
true
/test integ-pilot-istiodremote

integ-pilot-istiodremote-mc_istio
e5d5aa5fa2123c41609a7695cb3f9e7e3ef58437
link
true
/test integ-pilot-istiodremote-mc

integ-telemetry-istiodremote_istio
e5d5aa5fa2123c41609a7695cb3f9e7e3ef58437
link
true
/test integ-telemetry-istiodremote

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-sigs/prow repository. I understand the commands that are listed here.

/test all

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
e205dc55ca841e9d9005771f489eb13877824ada
link
true
/test integ-security-multicluster

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-sigs/prow repository. I understand the commands that are listed here.

/retest

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-sigs/prow repository.

However, for backwards compatibility we have different --set semantics unfortunately).

Maybe we should aim to change this. :/

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
4f98a71e76231c5d40ec732d358d7787a9b0feaa
link
true
/test lint

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
33f5434447c79905b42664a21d09f584cd1fd9a3
link
true
/test integ-security-multicluster

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-sigs/prow repository. I understand the commands that are listed here.

/retest

However, for backwards compatibility we have different --set semantics unfortunately).

Can those be detailed? (can be in this PR, in the linked issue, or in a new issue) - it may not matter that they are different/we may never really need to fix is, but I want to capture exactly how our semantics differ from Helm, as usually those differences confuse people.

Beyond that, we now have clearly devised installation phases:

Merge all inputs into a single unified configuration

Are we at the point yet where this could be emitted to a single yaml and supplied to a regular helm install istio -f unified-values.yaml, or is this still compatible only with istioctl semantics?

For each component, render the chart. Explicitly apply postprocessing steps (overlays) independently

I'm still going thru the PR - what postprocessing steps do we need to apply that helm wouldn't apply for us?

Can those be detailed? (can be in this PR, in the linked issue, or in a new issue) - it may not matter that they are different/we may never really need to fix is, but I want to capture exactly how our semantics differ from Helm, as usually those differences confuse people and create quirks it's best to be aware of.

The tl;dr: its all about lists. Helm supports foo[0].bar=baz. Istioctl supports that but also foo.[0].bar=baz and containers.[name:discovery].bar=baz. The former is obvious, the latter is like a "find the item that has that k-v pair"

Are we at the point yet where this could be emitted to a single yaml and supplied to a regular helm install istio -f unified-values.yaml, or is this still compatible only with istioctl semantics?

We are at the point where we call Helm's engine.Render(chart, values). However, we then postprocess the result (this is for the stuff under components.k8s, if that is not set then nothing to be done), add our labels (used for pruning), then apply ourselves.
The structure of the code makes it much simpler to modify this now though. I didn't want to make such large changes in any already large PR.

I'm still going thru the PR - what postprocessing steps do we need to apply that helm wouldn't apply for us?

These are all conveniently in postprocess.go :slightly_smiling_face:. But its all components.k8s. This is basically patching semantics. There are structured patches (like components.k8s.affinity=..., where the input is literally a corev1.Affinity we merge in), and there are raw patches where users pass some path like a.[key1:value1].b.[:value2] and do a opaque patching operation.
The former could be done by supporting the same set of 19 (patch types currently available) helm values in all charts with the same semantics and translating to those. The latter, I don't see how it could be done in a helm template.
What I expect to have to do if we needed to have a single helm call that spits out the entire resulting manifest we want is to use a https://helm.sh/docs/topics/advanced/#post-rendering. In theory this could support a workflow as follows:
istioctl migrate-to-helm -f istio-operator.yaml # makes a values.yaml, and postrender.sh
# postrender.sh is `istioctl postrender <contents of istio-operator.yaml we need to apply the postrender steps>`
helm install -f values.yaml --post-renderer postrender.sh

How we would expose that to users is very much TBD, not suggesting we do ^ necessarily

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
6d8f83c68277d9c5235c2b1ad4c17e7efef6a157
link
true
/test gencheck

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
6d8f83c68277d9c5235c2b1ad4c17e7efef6a157
link
true
/test gencheck

lint_istio
6d8f83c68277d9c5235c2b1ad4c17e7efef6a157
link
true
/test lint

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
6d8f83c68277d9c5235c2b1ad4c17e7efef6a157
link
true
/test lint

gencheck_istio
3890733249a1bede504bb7222b5caeff7dc48f10
link
true
/test gencheck

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
e0c1e09a1d22fb9a64812c1fdede49991079bbe4
link
true
/test gencheck

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
e0c1e09a1d22fb9a64812c1fdede49991079bbe4
link
true
/test gencheck

lint_istio
242d88410056269e0cf68cbf81cc838b32679f7b
link
true
/test lint

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
242d88410056269e0cf68cbf81cc838b32679f7b
link
true
/test lint

gencheck_istio
242d88410056269e0cf68cbf81cc838b32679f7b
link
true
/test gencheck

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
242d88410056269e0cf68cbf81cc838b32679f7b
link
true
/test gencheck

lint_istio
e1f5ae81c5c71e558697d2f33cf4a1b27ce93595
link
true
/test lint

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-sigs/prow repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
e1f5ae81c5c71e558697d2f33cf4a1b27ce93595
link
true
/test lint

gencheck_istio
e1f5ae81c5c71e558697d2f33cf4a1b27ce93595
link
true
/test gencheck

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-sigs/prow repository. I understand the commands that are listed here.

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-sigs/prow repository.

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
33e0f2ed194aa4356f996c0b053e5da35853d3e2
link
true
/test unit-tests-arm64

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-sigs/prow repository. I understand the commands that are listed here.


Flashing sealed P8

I'm wondering if there are any instructions about how to flash a stock P8 using OTA only (without opening it)? If there's some information about the steps it would be useful to include that in the documentation somewhere.

Hypnos is not compatible with the factory-installed bootloader in P8, so the only way to install it is to open up the P8 and replace the running software using a SWD programmer. After this, it should be possible to perform OTA-updates if you're using the most recent build (but not the most recent release).

Other projects have been able to swap booloaders like ATCwatch. See details for wasp-os: https://wasp-os.readthedocs.io/en/latest/install.html#daflasher-for-android


Allow any strategy in local adapter

From discussion in https://github.com/paulcsmith/bamboo/pull/71/files#r53177410, we want to allow any strategy in the local adapter.
Closes https://github.com/paulcsmith/bamboo/issues/79

@stevedomin Had just a couple comments

Fixed.
What do you think of adding a default for handle_config to AdapterBehaviour?

@stevedomin I'm not against it, but I'm not sure how much value it provides. If the default is def handle_config(config), do: config then I don't think it's worth it at this point.
Also, thanks for the PR :) I'll merge it in as soon as CI passes


Research basic API for querying elements of a scene together

When a user is querying a scene, what is the best way to allow them to access the different pieces of the group?
[sc-48296]

This is a non-sprint task


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter acme for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.acme
   -
ERRORS:

[ ] :heavy_exclamation_mark: [E143] No main found in the package.json

WARNINGS:

[X] :eyes: [W040] "keywords" within package.json should contain "ioBroker"
[ ] :eyes: [W046] devDependency should not require a specific version. Use "~1.2.3" or "^1.2.3" syntax. Please update "@iobroker/dev-server:*"
[ ] :eyes: [W184] "common.main" is deprecated and ignored. Please remove from io-package.json. Use "main" at package.json instead.

:thumbsup: No suggestions found
Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Fri, 06 Sep 2024 19:32:13 GMT

@iobroker-bot recheck

Note: @iobroker/dev-server should not be a dependency all together...

This issue has been updated by ioBroker Check and Service Bot
The following isses have been fixed
[W040] "keywords" within package.json should contain "ioBroker"
:thumbsup:Thanks for fixing the issues.
The following issues are new and have been added
[E143] No main found in the package.json
RECHECK has been performed as requested.

@iobroker-bot recheck

This issue has been updated by ioBroker Check and Service Bot
The following isses have been fixed
[E143] No main found in the package.json
[W184] "common.main" is deprecated and ignored. Please remove from io-package.json. Use "main" at package.json instead.
:thumbsup:Thanks for fixing the issues.
RECHECK has been performed as requested.

This issue has been updated by ioBroker Check and Service Bot
The following issues have been fixed
[W046] devDependency should not require a specific version. Use "~1.2.3" or "^1.2.3" syntax. Please update "@iobroker/dev-server:*"
:thumbsup:Thanks for fixing the issues.
The following issues are new and have been added
[W048] devDependency should not require a specific version. Use "~1.2.3" or "^1.2.3" syntax. Please update "@iobroker/dev-server:*"

Issue closed due to RECREATE request. Folloow up issue #129 has been created.
This issue can be closed.
your
ioBroker Check and Service Bot


Update requirements-test.txt

Codecov Report
Patch and project coverage have no change.

Comparison is base (16286b5) 68.27% compared to head (eddd11f) 68.27%.

:exclamation: Current head eddd11f differs from pull request most recent head b15c2ba. Consider uploading reports for the commit b15c2ba to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #366   +/-   ##
=======================================
  Coverage   68.27%   68.27%
=======================================
  Files          27       27
  Lines        3603     3603
=======================================
  Hits         2460     2460
  Misses       1143     1143

Flag
Coverage Δ

unittests
68.27% <ø> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Validate method modifies the input 'api' param inplace

The following code alters the contents of inputAPIDoc:

var SwaggerParser = require('swagger-parser');
var inputAPIDoc = {
    "swagger": "2.0",
    "info": {
        "version": "0.0.0",
        "title": "Simple API"
    },
    "paths": {
        "/": {
            "get": {
                "responses": {
                    "200": {
                        "description": "OK",
                        "schema": {
                            "$ref": "#/definitions/ScoredTopic"
                        }
                    },
                    "400": {
                        "description": "bad request",
                        "schema": {
                            "$ref": "#/definitions/badreq"
                        }
                    }
                }
            }
        }
    },
    "definitions": {
        "ScoredTopic": {
            "properties": {
                "topics": {
                    "type": "array",
                    "items": {
                        "$ref": "#/definitions/ScoredTopic"
                    }
                }
            }
        },
        "badreq": {
            "properties": {
                "topics": {
                    "type": "string",
                    "description": "details on why the error occured"
                }
            }
        }
    }

}
console.log(JSON.stringify(inputAPIDoc));
SwaggerParser.validate(inputAPIDoc, { dereference: { circular: false } }, function (err, api) {
    console.log("--------------------------");
    console.log(JSON.stringify(inputAPIDoc));
    if (err) {
        if (err.name === "ReferenceError" && err.message === "The API contains circular references") {
            console.log(err.message);
        }
        else {
            console.log(err);
        }
    }
    else {
        console.log("success");
    }
});

setTimeout(function () {
    console.log("**************************");
    console.log(JSON.stringify(inputAPIDoc));
}, 2000);

Output of the above code:
{"swagger":"2.0","info":{"version":"0.0.0","title":"Simple API"},"paths":{"/":{"get":{"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/ScoredTopic"}},"400":{"description":"bad request","schema":{"$ref":"#/definitions/badreq"}}}}}},"definitions":{"ScoredTopic":{"properties":{"topics":{"type":"array","items":{"$ref":"#/definitions/ScoredTopic"}}}},"badreq":{"properties":{"topics":{"type":"string","description":"details on why the error occured"}}}}}
--------------------------
{"swagger":"2.0","info":{"version":"0.0.0","title":"Simple API"},"paths":{"/":{"get":{"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/ScoredTopic"}},"400":{"description":"bad request","schema":{"properties":{"topics":{"type":"string","description":"details on why the error occured"}}}}}}}},"definitions":{"ScoredTopic":{"properties":{"topics":{"type":"array","items":{"$ref":"#/definitions/ScoredTopic"}}}},"badreq":{"properties":{"topics":{"type":"string","description":"details on why the error occured"}}}}}
The API contains circular references
**************************
{"swagger":"2.0","info":{"version":"0.0.0","title":"Simple API"},"paths":{"/":{"get":{"responses":{"200":{"description":"OK","schema":{"$ref":"#/definitions/ScoredTopic"}},"400":{"description":"bad request","schema":{"properties":{"topics":{"type":"string","description":"details on why the error occured"}}}}}}}},"definitions":{"ScoredTopic":{"properties":{"topics":{"type":"array","items":{"$ref":"#/definitions/ScoredTopic"}}}},"badreq":{"properties":{"topics":{"type":"string","description":"details on why the error occured"}}}}}

As we can see, the value of the var inputAPIDoc is altered on return from the validate call.
API documentation does not talk about this. Hence would be better if the same is clarified

Hi @akhilai, can you please point me to where is the api different. thanks

Hi @gracekarina, As you can see, the $ref at paths./.get.responses.400.schema is replaced by its definition in the input variable, i.e., inputAPIDoc. While this is expected value for the callback param 'api', I am not sure if it the intended behavior for swagger-parser to replace the contents of the input pram to the validate function itself.