Notification system (RENOP)

This is a Draft PR for the notification framework.
TODO:

Decide how the querying of SESSION_NOTICE table will be implemented.
OPTIONS:
A. Notifications should be able to be triggered at any moment. Therefore, it would make sense to have interval polling          which constantly checks for new notifications.  This is not in the PR but I have this working locally. Although this code is out of date, here is an example of how it might work https://github.com/project-chip/zap/commit/57d9486034af18b16d203a9e9c432212fdb6348e
B. If notifications are not able to be triggered at any moment and are specific for importing and exporting .zap files then there could be a function which queries the SESSION_NOTICE table after importing. This way there would be no need for polling. Basically, the notifications would only be queried when creating a session...
C. Both A and B

Add notification page to the front end

Test

This is a Draft PR for the notification framework.
TODO:

Decide how the querying of SESSION_NOTICE table will be implemented.
OPTIONS:
A. Notifications should be able to be triggered at any moment. Therefore, it would make sense to have interval polling          which constantly checks for new notifications.  This is not in the PR but I have this working locally. Although this code is out of date, here is an example of how it might work 57d9486
B. If notifications are not able to be triggered at any moment and are specific for importing and exporting .zap files then there could be a function at the end of importing a file which queries the SESSION_NOTICE table. This way there would be no need for polling. Basically, the notifications would only be queried when creating a session...
C. Both A and B
Add notification page to the front end
Test

This whole triggering the notification table makes it complicated in my opinion. How about we just introduce an additional pane along with our menu bar

In here we could have another icon for notifications. If a user clicks on this then we can show all the notifications for that session. This can simply show the results of "getNotification". To make it better if we want to alert the user regarding notifications then this notification icon can be turned to red until the user presses this once. Once they press it then it can go back to say yellow. If a new notification enters the session notice table again then turn this back to red until the user presses on it again.
For when do we turn the notification icon to red? => I would say every time there is a new entry to the session_notice table for that session.
My understanding is this should not require any kind of polling mechanism. Just the UI reflecting on the state of the backend.

This is a Draft PR for the notification framework.
TODO:

Decide how the querying of SESSION_NOTICE table will be implemented.
OPTIONS:
A. Notifications should be able to be triggered at any moment. Therefore, it would make sense to have interval polling          which constantly checks for new notifications.  This is not in the PR but I have this working locally. Although this code is out of date, here is an example of how it might work 57d9486
B. If notifications are not able to be triggered at any moment and are specific for importing and exporting .zap files then there could be a function at the end of importing a file which queries the SESSION_NOTICE table. This way there would be no need for polling. Basically, the notifications would only be queried when creating a session...
C. Both A and B
Add notification page to the front end
Test

This whole triggering the notification table makes it complicated in my opinion. How about we just introduce an additional pane along with our menu bar  In here we could have another icon for notifications. If a user clicks on this then we can show all the notifications for that session. This can simply show the results of "getNotification". To make it better if we want to alert the user regarding notifications then this notification icon can be turned to red until the user presses this once. Once they press it then it can go back to say yellow. If a new notification enters the session notice table again then turn this back to red until the user presses on it again. For when do we turn the notification icon to red? => I would say every time there is a new entry to the session_notice table for that session. My understanding is this should not require any kind of polling mechanism. Just the UI reflecting on the state of the backend.

That is an interesting idea. It would keep the user from being bombarded with notifications especially if they just upgraded their extremely old .zap file.
Re: "For when do we turn the notification icon to red? => I would say every time there is a new entry to the session_notice table for that session. My understanding is this should not require any kind of polling mechanism. Just the UI reflecting on the state of the backend." How would the front end know if a new notification was added to the table without polling? Unless it only queries during the creation of a session or in other words at fixed moments, there would need to be an interval polling mechanism.
Case 1: POLLING (This is how the DIRTY FLAG works)
1.)  The back end then creates a new entry in the table pointing at that sessionID
3.) Since the back end periodically polls that table, it will know to communicate to the front end that there is a new notification.
Case 2: NOT POLLING
1.) User imports old .zap file with lots of upgrades which create notifications in the table
2.) After importing, a query is called to get all of the notifications that were created.
3.) The front end displays them somehow someway
Basically, as far as I can tell, if the user can cause a change that requires an addition to the SESSION_NOTICE table at any random moment then we will need a polling mechanism. If not, then we can put a query in a line of code after all possible notifications have been created.

This is a Draft PR for the notification framework.
TODO:

Decide how the querying of SESSION_NOTICE table will be implemented.
OPTIONS:
A. Notifications should be able to be triggered at any moment. Therefore, it would make sense to have interval polling          which constantly checks for new notifications.  This is not in the PR but I have this working locally. Although this code is out of date, here is an example of how it might work 57d9486
B. If notifications are not able to be triggered at any moment and are specific for importing and exporting .zap files then there could be a function at the end of importing a file which queries the SESSION_NOTICE table. This way there would be no need for polling. Basically, the notifications would only be queried when creating a session...
C. Both A and B
Add notification page to the front end
Test

This whole triggering the notification table makes it complicated in my opinion. How about we just introduce an additional pane along with our menu bar  In here we could have another icon for notifications. If a user clicks on this then we can show all the notifications for that session. This can simply show the results of "getNotification". To make it better if we want to alert the user regarding notifications then this notification icon can be turned to red until the user presses this once. Once they press it then it can go back to say yellow. If a new notification enters the session notice table again then turn this back to red until the user presses on it again. For when do we turn the notification icon to red? => I would say every time there is a new entry to the session_notice table for that session. My understanding is this should not require any kind of polling mechanism. Just the UI reflecting on the state of the backend.

That is an interesting idea. It would keep the user from being bombarded with notifications especially if they just upgraded their extremely old .zap file.
Re: "For when do we turn the notification icon to red? => I would say every time there is a new entry to the session_notice table for that session. My understanding is this should not require any kind of polling mechanism. Just the UI reflecting on the state of the backend." How would the front end know if a new notification was added to the table without polling? Unless it only queries during the creation of a session or in other words at fixed moments, there would need to be an interval polling mechanism.
Case 1: POLLING (This is how the DIRTY FLAG works) 1.)  The back end then creates a new entry in the table pointing at that sessionID 3.) Since the back end periodically polls that table, it will know to communicate to the front end that there is a new notification.
Case 2: NOT POLLING 1.) User imports old .zap file with lots of upgrades which create notifications in the table 2.) After importing, a query is called to get all of the notifications that were created. 3.) The front end displays them somehow someway
Basically, as far as I can tell, if the user can cause a change that requires an addition to the SESSION_NOTICE table at any random moment then we will need a polling mechanism. If not, then we can put a query in a line of code after all possible notifications have been created.

For turning the colors of the notification icon, I was hoping there is some form of server push notification to the client which can just do this. Can we use the web socket to throw a push notification(from the backend/server) when there is a new entry in the session_notice table? The browser/ui can update when it gets this notification. I am not thinking of this as a polling mechanism but just an open connection for client and server to interact using the web socket. However, yes we do need a polling mechanism on the client or an open connection between client and server to update tell the user there are new notifications.

For turning the colors of the notification icon, I was hoping there is some form of server push notification to the client which can just do this. Can we use the web socket to throw a push notification(from the backend/server) when there is a new entry in the session_notice table? The browser/ui can update when it gets this notification. I am not thinking of this as a polling mechanism but just an open connection for client and server to interact using the web socket. However, yes we do need a polling mechanism on the client or an open connection between client and server to update tell the user there are new notifications.

We already have the web socket notification scheme setup since it was necessary for Studio integration.
For the flow of the DIRTY FLAG, it was necessary due to how Studio/Eclipse's dirty flag worked internally.
For the notification, I like @brdandu 's idea of a notification icon / window for listing all notifications. e.g. similar to social media event history.
For init features like opening .zap, the notification can be pushed during some init phase and rest can be all async'ed based. We should use DB "TRIGGER" / API wrapper to watch / trigger operations to the DB if polling was only required for this reason.

For turning the colors of the notification icon, I was hoping there is some form of server push notification to the client which can just do this. Can we use the web socket to throw a push notification(from the backend/server) when there is a new entry in the session_notice table? The browser/ui can update when it gets this notification. I am not thinking of this as a polling mechanism but just an open connection for client and server to interact using the web socket. However, yes we do need a polling mechanism on the client or an open connection between client and server to update tell the user there are new notifications.

We already have the web socket notification scheme setup since it was necessary for Studio integration. For the flow of the DIRTY FLAG, it was necessary due to how Studio/Eclipse's dirty flag worked internally. For the notification, I like @brdandu 's idea of a notification icon / window for listing all notifications. e.g. similar to social media event history. For init features like opening .zap, the notification can be pushed during some init phase and rest can be all async'ed based. We should use DB "TRIGGER" / API wrapper to watch / trigger operations to the DB if polling was only required for this reason.

Triggering a change to the database works for changing the SESSION_NOTICE table but how would the front end know that the SESSION_NOTICE table was changed without constantly checking it?
We could have a DB trigger execute a function which communicated with the front end but this has not been implemented before while using an interval for polling the DB is already implemented.
As far as I can tell, the difference between the DIRTY FLAG and other notifications you mention is that the DIRTY FLAG can be changed at any moment rather than at a fixed moment.  This is why I have used it as a model for this project.  My assumption is we want a system where a notification can be created and used at any moment.


zos: fix build errors and test failures

Enables libuv to build on z/OS:

Removed -q cflags
Set C_STANDARD to C11

https://github.com/libuv/libuv/discussions/4134

Disabled tests and code that requires ifaddr.h

https://github.com/libuv/libuv/pull/4244/commits/c42641155c61a721e165fafeb2c019fca158f2fd

Static link uv_run_tests_a to zoslib
pwritev/preadv undefined

https://github.com/libuv/libuv/pull/4244/commits/a7af8fc933dee322ed83bcf1aedc256e4b51ea04

Resolves test failures:

spawn_inherit_streams

https://github.com/libuv/libuv/pull/4244/commits/04ca6537de4a8e1f58e161b13310feb9588cecef
https://github.com/libuv/libuv/pull/4244/commits/a2e5d87a833c900e503fa3cae67d2359f9ed1512

get_passwd2

https://github.com/libuv/libuv/pull/4244/commits/1e5ec9c89ae5f212cb644436f4c1ae714304bbe6

fs_read_bufs

https://github.com/libuv/libuv/pull/4244/commits/09c84810cd82badbaf3d0762127465c1fc1869be

test-thread-priority

https://github.com/libuv/libuv/pull/4244/commits/619e8824a1084c26f1f7a81e30beea1d5181643e

https://github.com/libuv/libuv/blob/v1.x/CONTRIBUTING.md#COMMIT and please squash into logical commits (maybe they already are, I can't tell.)
Some of the commit logs contain links to IBM's internal github instance. Not useful, please remove.

@bnoordhuis Fixed

@laijonathan can you rebase and fix the merge conflict? Cheers.

@laijonathan can you rebase on top of v1.x instead of merge? Those Windows CI failures almost certainly mean you're missing some relevant changes. Another data point: automatic rebase doesn't work because of merge conflicts, so yeah.

@bnoordhuis Rebased

The MSVC 16 CI is still failing for some reason.  I suspect it has something to do with setting the C standard to C11 as MSVC 17 is passing.  C11 support was introduced in MSVC 16.8.
https://devblogs.microsoft.com/cppblog/c11-and-c17-standard-support-arriving-in-msvc/
@bnoordhuis Any thoughts?


Can keras model be trained without label?

Suppose I want to train a model to optimize a loss, but without a limited target, how can i train the model?

You still need an output, but in your loss function you can ignore the y_true. Then generate dummy values for the y values in the training call.

Thanks, that's a good idea！

@ericwu09 or @Epiphqny , can you provide a sample code for the suggestion made?

@bhalajin just write your own loss function which does not use y_true, and set any value to y_true will make no difference

For instance:
def dummy_loss(y_true, y_pred):     return y_pred

Tell me if I've got this wrong, but wouldn't it be a better idea to return y_true rather than y_pred? Surely using the predicted value as its own loss would just cause it to minimize its predictions, and by returning y_true couldn't you input the loss yourself directly when fitting?

@nwoodruff149 Only y_pred is based on your network; y_true has no relation with your network. Therefore, minimizing y_true is meaningless, as it is constant.

Silly question: how does my loss function know which is y_true or y_pred? Or in other words, how y_true and y_pred pass in?
Are they key words in Keras? Or are their positions fixed?


G4mespeed + fixed speed + block event separator = crash

Hello there, SpaceWalker. With the latest version of G4mespeed, I turned the tps to 0.156, set animation to fixed speed, then pressed m to reset the tickspeed, and boom, minecraft crashed.
[11:51:54] [Render thread/ERROR]: Unreported exception thrown!
java.lang.NullPointerException: Cannot invoke "net.minecraft.class_2338.method_10263()" because "$$0" is null
	at net.minecraft.class_1923.method_37232(class_1923.java:61) ~[client-intermediary.jar:?]
	at net.minecraft.class_1937.tickMovingBlocks_bes(class_1937.java:1151) ~[client-intermediary.jar:?]
	at net.minecraft.class_310.tickFixedSpeed_bes(class_310.java:3166) ~[client-intermediary.jar:?]
	at net.minecraft.class_310.handler$zzl000$block-event-separator$tickFixedSpeed(class_310.java:3107) ~[client-intermediary.jar:?]
	at net.minecraft.class_310.method_1574(class_310.java:1941) ~[client-intermediary.jar:?]
	at net.minecraft.class_310.method_1523(class_310.java:1150) ~[client-intermediary.jar:?]
	at net.minecraft.class_310.method_1514(class_310.java:781) ~[client-intermediary.jar:?]
	at net.minecraft.client.main.Main.method_44604(Main.java:244) ~[Fabric%201.19.3.jar:?]
	at net.minecraft.client.main.Main.main(Main.java:51) ~[Fabric%201.19.3.jar:?]
	at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:462) ~[fabric-loader-0.14.19.jar:?]
	at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74) ~[fabric-loader-0.14.19.jar:?]
	at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23) ~[fabric-loader-0.14.19.jar:?]

Thanks for the report! I've been having trouble figuring out what the issue is, when I stumbled upon a very similar issue with Lithium. Do you happen to be running Lithium? If so, can you try removing it and see if the issue persists?

I do happen to have Lithium, I will attempt to remove it, and try again. Keep in mind, I can still use block event separator fine, even with Lithium installed. Only when I turn fixed speed on in G4mespeed does it crash.

Lithium allows certain block entities to sleep by temporarily replacing their block entity ticker with a dummy ticker. The dummy ticker does not return a non-null position, because it doesn't have a reference to the block entity.

Adding a null check here should work around it: https://github.com/SpaceWalkerRS/block-event-separator/blob/337f9ce425306629c21e7431059b11b05a12027c/src/main/java/block/event/separator/mixin/client/LevelMixin.java#LL53C2-L53C2
if (pos==null)     continue

Thanks for the report! I've been having trouble figuring out what the issue is, when I stumbled upon a very similar issue with Lithium. Do you happen to be running Lithium? If so, can you try removing it and see if the issue persists?

Oh yeah, forgot about this. I removed Lithium, and was not able to reproduce the bug anymore.


HasMany pairs to wrong ManyToOne relationships

When having multiple HasMany(...) configurations on an entity map, the RelationshipPairingVisitor sometimes matches the OneToMany mappings to the wrong ManyToOne mappings if the referencing property of the ManyToOne mapping doesn't use "default naming" (the target entity name).
This issue arises from the PairOneToManys implementation on the RelationshippairingVisitor. The implementation orders the mappings by name and then selects the first ManyToOneMapping which targets the entity containing the HasMany(...) configurations. Depending on the namings, this results in the wrong mappings set to the OtherSide properties.
Especially when using custom IHasManyConvention for the foreign key conventions, receiving the wrong mappings results in creating faulty and very confusing database schemas.
I have written a test reproducing the described behaviour. If required, I can also provide a sample project.

see here for the mentioned test. I can create a PR if you like.

Is this the same as https://github.com/jagregory/fluent-nhibernate/pull/313? If so, the fix should arrive until the weekend

Yes you're right. I didn't see #313. Sorry for the duplicate.

No worries


Add extra addresses for listeners configuration to support dual stack in Istio

Please provide a description of this PR:
Add extra addresses for listeners configuration to support dual stack in Istio, this PR is for issue#40394
This PR just focus on normal k8s service in service mesh, and add the additional addresses for specified listener of service. There fore, it does not include below:

No code change for service entry
No code change for statefulsets/headless services with TCP ports, and empty service address field (There is another PR for this: https://github.com/istio/istio/pull/40409)
No code change for gateway listener configuration

Below snapshots are test results and the attach contains the whole configdump file exclude eds via curl localhost:15000/config_dump
Inbound listener additional addresses:

Outbound listener additional addresses:

Application/Service listener additional addresses:

Config dump:
extra_addresses_configdump.log
Note: I did not add any test case and I will add necessary test case after all the business code changes are available for reviewers.

@zhlsunshine: 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
d214261e3841ad9f226be17611ddfa32bd68eb28
link
true
/test unit-tests-arm64

unit-tests_istio
d214261e3841ad9f226be17611ddfa32bd68eb28
link
true
/test unit-tests

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

cc @adams-shaun can you help us review this?

@zhlsunshine: 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_istio
d214261e3841ad9f226be17611ddfa32bd68eb28
link
true
/test unit-tests

unit-tests-arm64_istio
9b1a340d06471c23fcd3af960f38d1850f864c19
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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_istio
9b1a340d06471c23fcd3af960f38d1850f864c19
link
true
/test unit-tests

unit-tests-arm64_istio
5bba66c5f91b560b91cd49896d762edfdca6f8dc
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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
5bba66c5f91b560b91cd49896d762edfdca6f8dc
link
true
/test unit-tests-arm64

unit-tests_istio
5bba66c5f91b560b91cd49896d762edfdca6f8dc
link
true
/test unit-tests

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

@zhlsunshine: 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_istio
5bba66c5f91b560b91cd49896d762edfdca6f8dc
link
true
/test unit-tests

unit-tests-arm64_istio
291f353a4b7066f60be1434b26a8da43892fb38a
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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
291f353a4b7066f60be1434b26a8da43892fb38a
link
true
/test unit-tests-arm64

unit-tests_istio
291f353a4b7066f60be1434b26a8da43892fb38a
link
true
/test unit-tests

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

cc @hzxuzhonghu @ramaraochavali

@zhlsunshine: 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_istio
291f353a4b7066f60be1434b26a8da43892fb38a
link
true
/test unit-tests

lint_istio
67c70edd566aaf13192fe53a31bb4bcfd13edb34
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/test-infra repository. I understand the commands that are listed here.

Hi @howardjohn, could you please help to approve this PR if it's okay?  Thanks! ^_^

Do we have integration test which has dual nics?

Hi @hzxuzhonghu , that's a good question,  in fact @jacob-delgado is focusing on building the integration test environment for dual stack.

Hi @howardjohn & @hzxuzhonghu, I refactored the code, so the duplicated code for adding extra addresses to a listener have been eliminated, then merged getDualStackWildcard and getDualStackLocalHost into getDualStackWildcardAndLocalHost, so many if statements have also been eliminated. I think the code is more brief than before. and I also added dual-stack proxy for unit tests. And @jacob-delgado also is working on making the integration test ready.
Hope you know this, and could help to review and approve this PR. Thanks!

BTW,  here is the newest configdump file for this change.
newest_extra_addresses_configdump.txt

Put up a PR to do similar testing for dual-stack clusters similar to how it's done for ipv6 (https://github.com/istio/test-infra/pull/4278). But we still need to create a specific test for this based on this set of changes.

/test integ-ds_istio

@zhlsunshine: 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-basic-arm64_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-basic-arm64

integ-ds_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-ds

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

@zhlsunshine: 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
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-basic-arm64

integ-ds_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-ds

integ-ipv6_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-basic-arm64

integ-ds_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-ds

integ-ipv6_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-ipv6

integ-distroless_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-distroless

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

@zhlsunshine: 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
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-basic-arm64

integ-ds_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-ds

integ-ipv6_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-ipv6

integ-distroless_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-distroless

integ-security-istiodremote_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-basic-arm64

integ-ds_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-ds

integ-ipv6_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-ipv6

integ-distroless_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-distroless

integ-security-istiodremote_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-security-istiodremote

integ-security_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-basic-arm64

integ-ds_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-ds

integ-ipv6_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-ipv6

integ-distroless_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-distroless

integ-security-istiodremote_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-security-istiodremote

integ-security_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-security

integ-security-multicluster_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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-ds_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-ds

integ-ipv6_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-ipv6

integ-distroless_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-distroless

integ-security-istiodremote_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-security-istiodremote

integ-security_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-security

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

integ-basic-arm64_istio
5e6324c72a4db1ef73593413c4060016a24eace6
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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-ds_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-ds

integ-distroless_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-distroless

integ-security-istiodremote_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-security-istiodremote

integ-security_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-security

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

integ-basic-arm64_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-basic-arm64

integ-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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-ds_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-ds

integ-security-istiodremote_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-security-istiodremote

integ-security_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-security

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

integ-basic-arm64_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-basic-arm64

integ-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-distroless_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-distroless

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

@zhlsunshine: 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-ds_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-ds

integ-security_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-security

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

integ-basic-arm64_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-basic-arm64

integ-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-distroless_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-distroless

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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-ds_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-ds

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

integ-basic-arm64_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-basic-arm64

integ-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-distroless_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-distroless

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

integ-security_istio
5e6324c72a4db1ef73593413c4060016a24eace6
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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-ds_istio
f3b2c058f3f6f5146d4cc692a2a714f831d08b28
link
true
/test integ-ds

integ-basic-arm64_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-basic-arm64

integ-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-distroless_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-distroless

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

integ-security_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security

integ-security-multicluster_istio
5e6324c72a4db1ef73593413c4060016a24eace6
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-basic-arm64

integ-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-distroless_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-distroless

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

integ-security_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security

integ-security-multicluster_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-multicluster

integ-ds_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ds

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

@zhlsunshine: 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
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-basic-arm64

integ-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-distroless_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-distroless

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

integ-security_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security

integ-security-multicluster_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-multicluster

integ-ds_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ds

unit-tests-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-distroless_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-distroless

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

integ-security_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security

integ-security-multicluster_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-multicluster

integ-ds_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ds

unit-tests-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-distroless_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-distroless

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

integ-security_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security

integ-security-multicluster_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-multicluster

integ-ds_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ds

unit-tests-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-basic-arm64

analyze-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test analyze-tests

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

@zhlsunshine: 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-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-distroless_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-distroless

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-multicluster

integ-ds_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ds

unit-tests-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-basic-arm64

analyze-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test analyze-tests

integ-security_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-distroless_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-distroless

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-multicluster

integ-ds_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ds

unit-tests-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-basic-arm64

analyze-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test analyze-tests

integ-security_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-security

lint_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-distroless_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-distroless

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-multicluster

integ-ds_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ds

unit-tests-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-basic-arm64

analyze-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test analyze-tests

integ-security_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-security

lint_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test lint

integ-helm_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-helm

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

@zhlsunshine: 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-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-distroless_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-distroless

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-multicluster

integ-ds_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ds

unit-tests-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-basic-arm64

analyze-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test analyze-tests

integ-security_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-security

lint_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test lint

integ-helm_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-helm

unit-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests

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

@zhlsunshine: 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-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-distroless_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-distroless

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-multicluster

integ-ds_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ds

unit-tests-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-basic-arm64

analyze-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test analyze-tests

integ-security_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-security

lint_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test lint

integ-helm_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-helm

unit-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests

integ-operator-controller_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-operator-controller

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

@zhlsunshine: 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-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-distroless_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-distroless

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-multicluster

integ-ds_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ds

unit-tests-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-basic-arm64

analyze-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test analyze-tests

integ-security_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-security

lint_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test lint

integ-helm_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-helm

unit-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests

integ-operator-controller_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-operator-controller

gencheck_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test gencheck

integ-cni_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-distroless_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-distroless

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-multicluster

integ-ds_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ds

unit-tests-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-basic-arm64

analyze-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test analyze-tests

integ-security_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-security

lint_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test lint

integ-helm_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-helm

unit-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests

integ-operator-controller_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-operator-controller

gencheck_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test gencheck

integ-cni_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-cni

integ-pilot-multicluster_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-multicluster

integ-ds_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ds

unit-tests-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-basic-arm64

analyze-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test analyze-tests

integ-security_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-security

lint_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test lint

integ-helm_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-helm

unit-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests

integ-operator-controller_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-operator-controller

gencheck_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test gencheck

integ-cni_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-cni

integ-pilot-multicluster_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-pilot-multicluster

integ-distroless_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-distroless

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

@zhlsunshine: 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-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-multicluster

integ-ds_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ds

unit-tests-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-basic-arm64

analyze-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test analyze-tests

integ-security_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-security

lint_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test lint

integ-helm_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-helm

unit-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests

integ-operator-controller_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-operator-controller

gencheck_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test gencheck

integ-cni_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-cni

integ-pilot-multicluster_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-pilot-multicluster

integ-distroless_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-distroless

integ-telemetry_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-telemetry

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

@zhlsunshine: 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-pilot-istiodremote_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-multicluster

integ-ds_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ds

unit-tests-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-basic-arm64

analyze-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test analyze-tests

integ-security_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-security

lint_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test lint

integ-helm_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-helm

unit-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests

integ-operator-controller_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-operator-controller

gencheck_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test gencheck

integ-cni_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-cni

integ-pilot-multicluster_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-pilot-multicluster

integ-distroless_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-distroless

integ-telemetry_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-telemetry

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

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

integ-pilot-istiodremote-mc_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-multicluster

integ-ds_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ds

unit-tests-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-basic-arm64

analyze-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test analyze-tests

integ-security_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-security

lint_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test lint

integ-helm_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-helm

unit-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests

integ-operator-controller_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-operator-controller

gencheck_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test gencheck

integ-cni_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-cni

integ-pilot-multicluster_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-pilot-multicluster

integ-distroless_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-distroless

integ-telemetry_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-telemetry

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

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

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

integ-pilot_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

integ-ds_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ds

unit-tests-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-basic-arm64

analyze-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test analyze-tests

integ-security_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-security

lint_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test lint

integ-helm_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-helm

unit-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests

integ-operator-controller_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-operator-controller

gencheck_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test gencheck

integ-cni_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-cni

integ-pilot-multicluster_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-pilot-multicluster

integ-distroless_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-distroless

integ-telemetry_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-telemetry

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

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

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

integ-pilot_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-pilot

integ-telemetry-mc_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-telemetry-mc

integ-security-multicluster_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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-ipv6_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-ipv6

integ-security-istiodremote_istio
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

unit-tests-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-basic-arm64

analyze-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test analyze-tests

integ-security_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-security

lint_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test lint

integ-helm_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-helm

unit-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests

integ-operator-controller_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-operator-controller

gencheck_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test gencheck

integ-cni_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-cni

integ-pilot-multicluster_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-pilot-multicluster

integ-distroless_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-distroless

integ-telemetry_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-telemetry

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

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

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

integ-pilot_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-pilot

integ-telemetry-mc_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-telemetry-mc

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

integ-ds_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-ds

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

@zhlsunshine: 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
5e6324c72a4db1ef73593413c4060016a24eace6
link
true
/test integ-security-istiodremote

unit-tests-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-basic-arm64

analyze-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test analyze-tests

integ-security_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-security

lint_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test lint

integ-helm_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-helm

unit-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests

integ-operator-controller_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-operator-controller

gencheck_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test gencheck

integ-cni_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-cni

integ-pilot-multicluster_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-pilot-multicluster

integ-distroless_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-distroless

integ-telemetry_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-telemetry

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

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

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

integ-pilot_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-pilot

integ-telemetry-mc_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-telemetry-mc

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

integ-ds_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-ds

integ-ipv6_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-basic-arm64

analyze-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test analyze-tests

integ-security_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-security

lint_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test lint

integ-helm_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-helm

unit-tests_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test unit-tests

integ-operator-controller_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-operator-controller

gencheck_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test gencheck

integ-cni_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-cni

integ-pilot-multicluster_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-pilot-multicluster

integ-distroless_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-distroless

integ-telemetry_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-telemetry

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

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

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

integ-pilot_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-pilot

integ-telemetry-mc_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-telemetry-mc

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

integ-ds_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-ds

integ-ipv6_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
link
true
/test integ-ipv6

integ-security-istiodremote_istio
a0ecd79eec8a7e80bb55d22c3e2889a874f4ae77
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/test-infra repository. I understand the commands that are listed here.

Hi @howardjohn, besides the unit test, the integration test for dual stack integ-ds_istio has been added as well, could you please help to review and approve this PR? Thanks! ^_^

There is a integ tests with a cluster running dual stack, but everything running inthe cluster is single stack so I don't think we actually have any tests coverage?

There is a integ tests with a cluster running dual stack, but everything running inthe cluster is single stack so I don't think we actually have any tests coverage?

Yeah, @howardjohn,  correct, there is still no dual stack test coverage, however, we can make sure that all dual stack code change would not impact ipv4/ipv6 only use case with inte-ds_istio job. There would be dual stack test cases be added with new flag istio.test.enableDualStack in later

@zhlsunshine: 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
1ca87d36341c37cfdee83ed9170e58877dafb122
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/test-infra repository. I understand the commands that are listed here.

@zhlsunshine: 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
1ca87d36341c37cfdee83ed9170e58877dafb122
link
true
/test unit-tests-arm64

unit-tests_istio
1ca87d36341c37cfdee83ed9170e58877dafb122
link
true
/test unit-tests

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

Hi @howardjohn, according to above comments, I did some changes as below:

Added a struct named WildcardAndLocalHost to hold the wildcard and localhost addresses. And there is no model proxy for this struct, because it may be re-used by other external services, such as service entry.
GetWildcardAddresses() and GetLocalHostAddresses() are used to separated when using in different places, and no matter which ip family is, the first address of service can bind to listener, the rest can be added in additional addresses.
Fixed a bug for bench_test when creating a node proxy based on the current implementation.
Hope you know this, and thank you so much for your review and comments for this PR! ^_^

Hi @howardjohn, according to above comments, I did some changes as below:

Added a struct named WildcardAndLocalHost to hold the wildcard and localhost addresses. And there is no model proxy for this struct, because it may be re-used by other external services, such as service entry.
GetWildcardAddresses() and GetLocalHostAddresses() are used to separated when using in different places, and no matter which ip family is, the first address of service can bind to listener, the rest can be added in additional addresses.
Fixed a bug for bench_test when creating a node proxy based on the current implementation.

Here is the newest configdump file:
the_newest_extra_addresses_configdump.txt
Hope you know this, and thank you so much for your reviewing and commenting for this PR! ^_^

/test benchmark

Benchmarks show some troubling results: https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/40634/benchmark_istio/1572678114784317440
maybe due to adding ipDiscovery call? Might be worth breaking that out so we can analyze the main PR in isolation.

Benchmarks show some troubling results: https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/40634/benchmark_istio/1572678114784317440
maybe due to adding ipDiscovery call? Might be worth breaking that out so we can analyze the main PR in isolation.

It seems that the job is passed,  I think ipDiscovery should be called once the proxy node is created and it should be required in later.

Hi @ramaraochavali, I think your above comments have mentioned that Wildcards() and Localhosts() may be moved into proxy struct. However, to import a new struct now named HostAddresses is not only for normal service whose pods hold the injected proxy, but also some other service, such as service entry which has no any injected proxy.

It seems that the job is passed, I think ipDiscovery should be called once the proxy node is created and it should be required in later.

Its a benchmark, its not pass/fail. It shows 2x cost on almost all tests

No, look at the logs. It shows a diff for each benchmark
On Thu, Sep 22, 2022 at 9:19 AM Steve Zhang @.***>
wrote:

It seems that the job is passed, I think ipDiscovery should be called once
the proxy node is created and it should be required in later.
Its a benchmark, its not pass/fail. It shows 2x cost on almost all tests
Hi @howardjohn https://github.com/howardjohn, do you mean the Duration
for this benchmark? Based on below snapshot, it seems that it has been
almost 20m since Aug 1th.
[image: image]
https://user-images.githubusercontent.com/4101246/191799388-b4ab840e-60c2-4770-8178-b024a9e90285.png
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/40634#issuecomment-1255257325, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXMT5CG4LBJ3HSKZCPDV7SBHLANCNFSM57POM2AA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @howardjohn, I compared the 2 bench tests<PHONE_NUMBER>784317440 for this PR and<PHONE_NUMBER>097564160 for PR#41120 ) log, I noticed that there are some downloading job before the bench test begin in former.
Besides that, the big differences are focusing on BenchmarkStats in istio.io/istio/pilot/cmd/pilot-agent/status
It took 2x costs at the beginning of the bench test but less at the end in former, it's opposite for the latter.

This is<PHONE_NUMBER>784317440 for this PR:

This is<PHONE_NUMBER>097564160 for PR#41120:

/test benchmark

Generally, looks good. But i am concerned with the hacking into so many places, can we reduce

Hi @hzxuzhonghu, I understand your worries, however, all these places are required to be changed for generating the necessary configuration.

Hi @howardjohn, thanks for your comparison above, then I see no. and I also checked the comparison between1557747988594429952 by ramaraochavali at Aug 11 23:17:51 and<PHONE_NUMBER>097564160 by howardjohn at Sep 23 00:37:35.
As you commented here: https://github.com/istio/istio/pull/40634#issuecomment-1254226823, I think you are correct that ipDiscovery called in pilot/pkg/xds/bench_test.go causes such huge increase in config size.
Moreover, I also checked the comparison between<PHONE_NUMBER>097564160 by howardjohn at Sep 23 00:37:35 and<PHONE_NUMBER>842235904	by zhlsunshine at Sep 23 09:58:00, there is no huge increase for them.
According to current analysis, this PR does not cause the increasing in configuration size if it drops the bech_test's DiscoverIPMode calling. However, in fact, it confused me that DiscoverIPMode calling causes such huge increase in configuration size. You know it just sets the IP mode and GlobalUnicastIP of the proxy.

Hi @howardjohn, thanks for your comparison above, then I see now. and I also checked the comparison between1557747988594429952 by ramaraochavali at Aug 11 23:17:51 and<PHONE_NUMBER>097564160 by howardjohn at Sep 23 00:37:35.
As you commented here: https://github.com/istio/istio/pull/40634#issuecomment-1254226823, I think you are correct that DiscoverIPMode called in pilot/pkg/xds/bench_test.go causes such huge increase in config size.
Moreover, I also checked the comparison between<PHONE_NUMBER>097564160 by howardjohn at Sep 23 00:37:35 and<PHONE_NUMBER>842235904	by zhlsunshine at Sep 23 09:58:00, there is no huge increase for them.
According to current analysis, this PR does not cause the increasing in configuration size if it drops the bech_test's DiscoverIPMode calling. However, in fact, it confused me that DiscoverIPMode calling causes such huge increase in configuration size. You know it just sets the IP mode and GlobalUnicastIP of the proxy.

/test benchmark

One question, when user specify Bind explicitly, will we add additional Bind now?

Hi @hzxuzhonghu, what do you mean specify Bind explicitly?  the additional bind is added when istio service has more than one addresses.

Not sure this is right in this case

Not sure this is right in this case

Hi @hzxuzhonghu, as discussed here: https://github.com/istio/istio/issues/40394, a listener supports multiple addresses is a good idea for dual stack. Moreover, it also can be used for other scenario, such as tcp headless service you mentioned. I think it's still valid based on current code change. Any idea?

@zhlsunshine: 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
e27ee981b3da69c8674d117b0a08699a00d943e7
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/test-infra repository. I understand the commands that are listed here.

/test integ-security-multicluster

Hi @hzxuzhonghu, re-submitted, maintain 2 maps to fetch host addresses according to proxy’s IP mode. Thanks for your comments! ^_^


Doc feature jsservice

Added JS Service docs.

I suggest using 2 spaces to indent the example code.


JPEG Quality doesn't work

When I try to edit the JPEG quality it doesnt do anything, no matter if the input is a jpeg or png. It outputs fine but the quality is the same

Hi @ElijahZAwesome this appears to be working for me, when calling image.quality(100, function(image){write}) I get very different results when using a quaility of 5, 50, or 100.

See attached results

Yeah, im sorry about that lol, turns out you have to export as JP_E_G and not JPG, I didn't realize that... sorry lol


SQLSTATE error

Problem
SQLSTATE errors might occur in cases, when pgbackweb tables conflict with existing db tables.
I believe this is the same issue as in #4 .
Suggestion
Consider making pgbackweb table names unique by using postfixes or with help of some other methods.

Why not to use a separate db for pg back web?


fix(reviews): admin review deletion fix

Gives admins the ability to delete reviews for listings they do not own.
Closes #AMLOS-540
Description
As a Mall Admin, I cannot delete any reviews that are not created by me.
Acceptance Criteria
Users can delete and edit only their reviews
Org stewards can delete reviews for listings they are stewards of.
Mall admins (site stewards) can delete reviews for any listing.
How To Test
Pull this branch
log in as (user below) and check that mallrats review can/cannot be deleted as expected.
Bigbrother: Can Delete
Wsmith: Cannot Delete
Obrien: Can Delete
Johnson: Cannot Delete
Rutherford: Can Delete

Admins can delete reviews again.
👍

works as expected :+1:


Exporting tasks for specific task IDs exports all task annotations instead

Hello,
I have set up a Label Studio project, where I have set up a choices annotation in the xml configuration file which can be either Yes or No. I want to export a COCO dataset which will contain the annotations only for the tasks that have been labeled as Yes. My code is the following:
# Get project
project = ls.get_project(id=id)

# Get labeled tasks
labeled_tasks = project.get_labeled_tasks()

# Filter tasks based on "Yes"
filtered_task_ids = []
for task in labeled_tasks:
    task_annotations = task["annotations"][0]["result"]

    filtered_annotation = [annotation["value"]["choices"][0] for annotation in task_annotations if annotation["type"] == "choices"]

    if filtered_annotation == ["Yes"]:
        filtered_task_ids.append(task["id"])

project.export_tasks(ids=filtered_task_ids, export_type="COCO", export_location=download_path, download_all_tasks=False)

In my example project, filtered_task_ids contains 2 IDs, while the project contains 95 tasks. While I would expect that the generated COCO file will contain the annotations only for these 2 tasks, it contains the annotations for all 95.
Am I missing the intended behavior of the ids argument or is there an issue with either my code or with export_tasks()?

Hi @CharalamposGeorgiadis - thanks for your report! We'll take a look and get back to you.


Does not download by torrent or magnet link windows 10 and ubuntu 20.04

Add a file to download(a torrent file or a magnet link). There is no progress. I thought to put the transmission instead, but no. When adding the same links and files, the transmission starts downloading immediately.


Go dep config TOML vs. YAML #devexp

Hi team,
From a user/developer experience point of view I was wondering why TOML was chosen over YAML for configuration?
From a technical perspective:

YAML is standardised and has been stable on v1.2 since 2007
The TOML v0.4.0 readme explicitly states: "Be warned, this spec is still changing a lot. Until it's marked as 1.0, you should assume that it is unstable and act accordingly."
You already read glide.yml files and therefore already have YAML as a dependency. Given this, you could drop the TOML dependency.

Personally:

For developers of any level, I've found people seem to understand YAML a lot faster.

Take for example these two dep files converted between the two:
TOML
required = ["github.com/user/thing/cmd/thing"]

ignored = ["github.com/user/project/pkgX", "bitbucket.org/user/project/pkgA/pkgY"]

[metadata]
codename = "foo"

[[constraint]]
  name = "github.com/user/project"
  version = "1.0.0"

  [metadata]
  property1 = "value1"
  property2 = 10

[[constraint]]
  name = "github.com/user/project2"
  branch = "dev"
  source = "github.com/myfork/project2"

[[override]]
  name = "github.com/x/y"
  version = "2.4.0"

  [metadata]
  propertyX = "valueX"

YAML*
required:
  - github.com/user/thing/cmd/thing

ignored:
  - github.com/user/project/pkgX
  - bitbucket.org/user/project/pkgA/pkgY

metadata:
  codename: foo

constraint:
  - name: github.com/user/project
    version: 1.0.0
    metadata:
      property1: value1
      property2: 10

  - name: github.com/user/project2
    branch: dev
    source: github.com/myfork/project2

override:
  - name: github.com/x/y
    version: 2.4.0
    metadata:
      propertyX: valueX

*I'm actually not sure if my TOML to YAML conversion below is correct, an online TOML to JSON parser couldn't seem to understand the example which I was using to try and decipher where [[ constraints ]] sit.

I was wondering why TOML was chosen over YAML for configuration?

#119

Unfortunate, nonetheless, thanks.

@MatthewHartstonge it's a question that we can revisit when it comes time to transition into the toolchain. the crucial property that TOML afforded us, that YAML does not, is the ability to append new [[constraint]] rules to the TOML file.
This obviates the need for a highly complex comment-preserving implementation, while still allowing us to provide strong default guidance on initial constraints for new dependencies. That's good UX on its own, which is one goal, but it's also very important for the broader ecosystem of Go software, because of how these constraints end up interacting: if too many people define unnecessarily narrow constraints, it can make the entire ecosystem prone to some circles of dependency hell.

Can you paste a examples, or paste a link to previous discussions that include examples, thx


Major Issues - Substitution has random results

I'm using the Node Package with SendGrids template API. I'm sending custom data to my template using the substitution methods. But I'm getting random results i.e. I'm sending out 5 emails using the same data (I see the correct data is being sent via console.logs) but 3 out of the 5 emails are delivered without the data. i.e. when you open them the template is blank.
I have talked with SendGrid support and they have no idea and now suggested I open a ticket on here. Why no idea. Looks like SendGrid support and the developer team are not connected...
Support ticket [SendGrid Support] Re: #1001185
I'm on Node v.4.7.0
Here is my code - https://gist.github.com/AlmogRnD/c97f0a88e51a5c4c89a400145592735c
Attached gif showing the issue

That was the issue, fixed thanks


Question about the Image_And_Icons_Manipulations tutorial

There is some confusing part about loading bitmaps in this (drawing-raw-image-data-using-native-canvas) section of the tutorial.
First, we load it using useResource:
// ImageBitmap
private val sample = useResource("sample.png", ::loadImageBitmap)

Second, we do it again using bitmapFromByteArray and ImageBitmap.getBytes:
fun main() {

    // ...

    // ImageBitmap
    val bitmap = remember { bitmapFromByteArray(sample.getBytes(), sample.width, sample.height) }

    // ...
}

fun bitmapFromByteArray(pixels: ByteArray, width: Int, height: Int): ImageBitmap {
    val bitmap = Bitmap()
    bitmap.allocPixels(ImageInfo.makeS32(width, height, ColorAlphaType.PREMUL))
    bitmap.installPixels(bitmap.imageInfo, pixels, (width * 4).toLong())
    return bitmap.asImageBitmap()
}

// creating byte array from BufferedImage
private fun ImageBitmap.getBytes(): ByteArray {
    val buffer = IntArray(width * height)
    readPixels(buffer)

    val pixels = ByteArray(width * height * 4)

    var index = 0
    for (y in 0 until height) {
        for (x in 0 until width) {
            val pixel = buffer[y * width + x]
            pixels[index++] = ((pixel and 0xFF)).toByte() // Blue component
            pixels[index++] = (((pixel shr 8) and 0xFF)).toByte() // Green component
            pixels[index++] = (((pixel shr 16) and 0xFF)).toByte() // Red component
            pixels[index++] = (((pixel shr 24) and 0xFF)).toByte() // Alpha component
        }
    }

    return pixels
}

Can't it all be simplified to:
private val sample = useResource("sample.png", ::loadImageBitmap)

@OptIn(ExperimentalComposeUiApi::class)
fun main() = singleWindowApplication {
    val bitmap = remember { sample }
    Canvas(
        modifier = Modifier.fillMaxSize()
    ) {
        drawIntoCanvas { canvas ->
            canvas.drawImage(bitmap, Offset.Zero, Paint())
        }
    }
}

P.S. Thanks for the fantastic library!

Actually this tutorial shows multiple things: how to draw an image on canvas, how to convert an image to a pixel array, and how to convert a pixel array to an image. Originally, the main goal was to show how to draw an image if we only have a pixel array.
But let's keep things simple, and remove converting part, because it isn't directly related to Compose for Desktop, rather to common Compose or Skija.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


build(deps): bump Erlang to 25.3

Release notes https://www.erlang.org/patches/otp-25.3

Thanks!
Related conversation with upstream:

https://github.com/esl/packages/issues/15#issuecomment-1514426078

@jeffwidman Can you take a look at the updated PR? I can revert the comment if needed
I'd like to use a PPA as the comment highlighted but https://github.com/esl/packages/issues/15 still applies

ping @deivid-rodriguez @abdulapopoola @JamieMagee  to hear what your thoughts are.
It is unclear to me if @jeffwidman is back in the team or not so I'd appreciate your inputs as well


Fixes #214 Adds Overt test cases for of() and removes SEGMENTS_UNDERFLOW in Prefix

Removes SEGMENTS_UNDERFLOW check for InterledgerAddressPrefix as this cannot be reached.
Adds explicit test cases for InterledgerAddress#of and InterledgerAddressPrefix#of.
Update error message if a corner case slips through the checks and ask users to report a bug.

Signed-off-by: sudheesh001<EMAIL_ADDRESS>

Codecov Report

Merging #218 into master will increase coverage by 0.08%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #218      +/-   ##
============================================
+ Coverage     74.21%   74.29%   +0.08%
  Complexity      390      390
============================================
  Files           112      112
  Lines          1745     1743       -2
  Branches        155      154       -1
============================================
  Hits           1295     1295
+ Misses          381      380       -1
+ Partials         69       68       -1

Impacted Files
Coverage Δ
Complexity Δ

...org/interledger/core/InterledgerAddressPrefix.java
97.14% <ø> (+2.69%)
12 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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

Great! Thanks for the review. I made the changes and this patch should be ready now.


typo: fix misspells in code and comments

Ⅰ. Describe what this PR did
fix misspells in code and comments
Ⅱ. Does this pull request fix one issue?

NONE
Ⅲ. Describe how you did it
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks a lot for your work. Actually this is a vendor package and we have no plan to main the code of this part. I am afraid we cannot merge this. @idealhack

I see, but why there are different folders for vendor packages?

This is a good question. Lots of things have been discussed before, like:
https://github.com/alibaba/pouch/issues/1344
https://github.com/alibaba/pouch/issues/428
https://github.com/alibaba/pouch/issues/750
I think we do need to take into vendor the latest version into consideration. WDYT? @rudyfly

@allencloud This is not flaky case. The pouchd cannot remove the running task. We are still investigating the issue.

I'll keep this open for now. Feel free to close it when you open new ones for the ci and dependency issues.

Could you help to vendor the latest libnetwork package with govendor tool? @idealhack
I think this is what we wish to finish. We encourage you to finish it very much and feel free to tell us if you have any problem when doing this.

@allencloud OK, I'll give it a try.

Since #1344 is open, let's resolve the dependency issue in that thread.
Feel free to close this one when you open new ones for the ci issue.

Thanks @idealhack
While I do not think this issue could help. And I am closing it.