Parse from String to Uuid

Hi,
How would I parse a string 907b0976-00be-4465-9e00-a8f0d571979a to a Uuid object using the library? I could only find the parse(String) but it returns a byte.
Regards,

There is no object. You parse it to a byte array and then do what you need with it. I don't provide any helper features for a uuid, since you can only get limited data from it anyway.

Ah, thanks. Are there any plans on creating an uuid object?

You are the first to request one, what information would you like in a UUID Object if I were to add one?
The only info it can provide is Version (1,4,5) and maybe Variant but no one really sets variants and uses random numbers for that too.
The rest is all random bits from the RNG source at time of creation.

I was more thinking on a specific value object, like datetime for instance, in the line of the following api's
Java UUID: https://docs.oracle.com/javase/7/docs/api/java/util/UUID.html or
C# Guid: https://docs.microsoft.com/en-us/dotnet/api/system.guid?view=net-5.0

ok, I think thats doable and a valid usecase. Give me a bit to add that. Currently focused on null safety stuff, But I can get our some of this stuff for you soon. I will most likely create new functions to do this, so that I don't break backwards compatibility for now.

made the changes in 3.0.0-nullsafety.1, please give it a try and open a new ticket if its broken or other requests. It has a new UuidValue object, and appropriate functions.

Thanks a lot. I'm going to give it a go.

Why not merge Uuid and UuidValue as one Object? I see no point in creating an additional Object? Image Uuid.v4() would simply initialise the internal String uuid. You could work with static functions to do methods like Uuid.parse()...

Understandable.
Only want to clarify the second point. I mean Uuid.v4() as an initializer rather than a function that can change whenever. Uuid would still be constant.
Anyway, thanks for the explanation!


Boldface not working on competition pages

This is bold
does not result in boldface fonts.

@madclam
Do you have a specific example?
You can see in this competition main page that "classification tasks" is in bold:
https://www.codabench.org/competitions/870/
Your problem may be that the markdown is not interpreted because it is mixed with HTML:

#879

I close this issue to keep track of this in the new issue


Deleting last task from calendar kills app

The last task on a calendar is not cleared away and thus can be deleted again. The second deletion kills the app.
This happened on a Nexus 10. Phones don't have this problem.

We fixed this with version 1.1.1


Added --all-namespaces argument

Added --all-namespaces argument so that user does not have to have spawn multiple instance to watch multiple namespace

Thanks for your contribution :)
I haven't been using this myself, as I left the company I wrote this for a while ago but I'm returning next month. Maybe I'll able to maintain this again.
Tag v2.1.0 is now up on Docker Hub and also latest is updated.

Good to hear that. Thanks for updating the docker image as well.
I will try to contribute as currently I am trying to implement this to my kubernetes as well.


Optimize slice memory allocations at different places:

Avoid unwanted memory allocations by setting capacity for slices
as length whenever length is known to create accurate size array to
back it. It is already handled in many places in the code and missed
in few. Hence, this commit fixes it.
Signed-off-by: Aliasgar Ginwala<EMAIL_ADDRESS>[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ X] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ X] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

Hi @noah8713. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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.

/ok-to-test

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

Test name
Commit
Details
Rerun command

release-notes_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-notes_istio

release-test_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-notes_istio

release-test_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-test_istio

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-notes_istio

release-test_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-test_istio

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

lint_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-notes_istio

release-test_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-test_istio

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

lint_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test lint_istio

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-notes_istio

release-test_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-test_istio

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

lint_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test lint_istio

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

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-notes_istio

release-test_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-test_istio

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

lint_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test lint_istio

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

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-notes_istio

release-test_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-test_istio

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

lint_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test lint_istio

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

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-ipv6-k8s-tests_istio

unit-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-notes_istio

release-test_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-test_istio

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

lint_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test lint_istio

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

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-ipv6-k8s-tests_istio

unit-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test unit-tests_istio

integ-operator-controller-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-operator-controller-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-notes_istio

release-test_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-test_istio

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

lint_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test lint_istio

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

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-ipv6-k8s-tests_istio

unit-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test unit-tests_istio

integ-operator-controller-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-operator-controller-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-notes_istio

release-test_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-test_istio

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

lint_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test lint_istio

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

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-ipv6-k8s-tests_istio

unit-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test unit-tests_istio

integ-operator-controller-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-operator-controller-tests_istio

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

analyze-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-notes_istio

release-test_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-test_istio

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

lint_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test lint_istio

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

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-ipv6-k8s-tests_istio

unit-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test unit-tests_istio

integ-operator-controller-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-operator-controller-tests_istio

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

analyze-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test analyze-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-notes_istio

release-test_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-test_istio

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

lint_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test lint_istio

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

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-ipv6-k8s-tests_istio

unit-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test unit-tests_istio

integ-operator-controller-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-operator-controller-tests_istio

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

analyze-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test analyze-tests_istio

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

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

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

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

Test name
Commit
Details
Rerun command

release-test_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-test_istio

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

lint_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test lint_istio

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

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-ipv6-k8s-tests_istio

unit-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test unit-tests_istio

integ-operator-controller-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-operator-controller-tests_istio

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

analyze-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test analyze-tests_istio

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

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

release-notes_istio
2b9c3fabcaf7cc4b1a820d2509bc25231efc4356
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

release-test_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-test_istio

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

lint_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test lint_istio

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

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-ipv6-k8s-tests_istio

integ-operator-controller-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-operator-controller-tests_istio

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

analyze-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test analyze-tests_istio

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

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

release-notes_istio
2b9c3fabcaf7cc4b1a820d2509bc25231efc4356
link
/test release-notes_istio

unit-tests_istio
2b9c3fabcaf7cc4b1a820d2509bc25231efc4356
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-test_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-test_istio

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

lint_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test lint_istio

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

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-ipv6-k8s-tests_istio

integ-operator-controller-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-operator-controller-tests_istio

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

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

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

release-notes_istio
2b9c3fabcaf7cc4b1a820d2509bc25231efc4356
link
/test release-notes_istio

unit-tests_istio
2b9c3fabcaf7cc4b1a820d2509bc25231efc4356
link
/test unit-tests_istio

analyze-tests_istio
2b9c3fabcaf7cc4b1a820d2509bc25231efc4356
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

release-test_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-test_istio

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

lint_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test lint_istio

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

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-ipv6-k8s-tests_istio

integ-operator-controller-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-operator-controller-tests_istio

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

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

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

unit-tests_istio
2b9c3fabcaf7cc4b1a820d2509bc25231efc4356
link
/test unit-tests_istio

analyze-tests_istio
2b9c3fabcaf7cc4b1a820d2509bc25231efc4356
link
/test analyze-tests_istio

release-notes_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

release-test_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test release-test_istio

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

lint_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test lint_istio

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

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-ipv6-k8s-tests_istio

integ-operator-controller-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-operator-controller-tests_istio

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

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

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

unit-tests_istio
2b9c3fabcaf7cc4b1a820d2509bc25231efc4356
link
/test unit-tests_istio

release-notes_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-notes_istio

analyze-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

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

lint_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test lint_istio

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

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-ipv6-k8s-tests_istio

integ-operator-controller-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-operator-controller-tests_istio

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

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

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

unit-tests_istio
2b9c3fabcaf7cc4b1a820d2509bc25231efc4356
link
/test unit-tests_istio

release-notes_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-notes_istio

analyze-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test analyze-tests_istio

release-test_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

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

lint_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test lint_istio

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

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-ipv6-k8s-tests_istio

integ-operator-controller-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-operator-controller-tests_istio

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

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

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

release-notes_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-notes_istio

analyze-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test analyze-tests_istio

release-test_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-test_istio

unit-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

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

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

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test integ-ipv6-k8s-tests_istio

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

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

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

release-notes_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-notes_istio

analyze-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test analyze-tests_istio

release-test_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-test_istio

unit-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test unit-tests_istio

lint_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test lint_istio

integ-operator-controller-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test integ-operator-controller-tests_istio

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

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

Test name
Commit
Details
Rerun command

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

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

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

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

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

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

release-notes_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-notes_istio

analyze-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test analyze-tests_istio

release-test_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-test_istio

unit-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test unit-tests_istio

lint_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test lint_istio

integ-operator-controller-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

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

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

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

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

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

release-notes_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-notes_istio

analyze-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test analyze-tests_istio

release-test_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-test_istio

unit-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test unit-tests_istio

lint_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test lint_istio

integ-operator-controller-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test integ-ipv6-k8s-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

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

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

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

release-notes_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-notes_istio

analyze-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test analyze-tests_istio

release-test_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-test_istio

unit-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test unit-tests_istio

lint_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test lint_istio

integ-operator-controller-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test integ-ipv6-k8s-tests_istio

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

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

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

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

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

release-notes_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-notes_istio

analyze-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test analyze-tests_istio

release-test_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-test_istio

unit-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test unit-tests_istio

lint_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test lint_istio

integ-operator-controller-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test integ-ipv6-k8s-tests_istio

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

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

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

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
a49fa98c320708ef7acc549b7d2170690c5f00de
link
/test gencheck_istio

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

release-notes_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-notes_istio

analyze-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test analyze-tests_istio

release-test_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-test_istio

unit-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test unit-tests_istio

lint_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test lint_istio

integ-operator-controller-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test integ-ipv6-k8s-tests_istio

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

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

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

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

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

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

Test name
Commit
Details
Rerun command

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

release-notes_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-notes_istio

analyze-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test analyze-tests_istio

release-test_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-test_istio

unit-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test unit-tests_istio

lint_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test lint_istio

integ-operator-controller-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test integ-ipv6-k8s-tests_istio

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

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

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

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

gencheck_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-notes_istio

analyze-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test analyze-tests_istio

release-test_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-test_istio

unit-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test unit-tests_istio

lint_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test lint_istio

integ-operator-controller-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test integ-ipv6-k8s-tests_istio

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

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

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

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

gencheck_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test gencheck_istio

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

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test analyze-tests_istio

release-test_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test release-test_istio

unit-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test unit-tests_istio

lint_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test lint_istio

integ-operator-controller-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test integ-ipv6-k8s-tests_istio

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

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

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

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

gencheck_istio
f23624bd5c4d19745b7e22a344b81f06ef7a6a7e
link
/test gencheck_istio

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

release-notes_istio
b33b6ce4f99a2cd31e26cae51f334afc8f1991ca
link
/test release-notes_istio

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

@googlebot I signed it!

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

Test name
Commit
Details
Rerun command

release-notes_istio
c47b8ec9f8e1414384ed61efd71e3bcc7dc0b1a6
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
c47b8ec9f8e1414384ed61efd71e3bcc7dc0b1a6
link
/test release-notes_istio

integ-operator-controller-tests_istio
c47b8ec9f8e1414384ed61efd71e3bcc7dc0b1a6
link
/test integ-operator-controller-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-operator-controller-tests_istio
c47b8ec9f8e1414384ed61efd71e3bcc7dc0b1a6
link
/test integ-operator-controller-tests_istio

release-notes_istio
4dce681374024abfe64be6b76d8eec856bbc3b6e
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

integ-operator-controller-tests_istio
c47b8ec9f8e1414384ed61efd71e3bcc7dc0b1a6
link
/test integ-operator-controller-tests_istio

release-notes_istio
4dce681374024abfe64be6b76d8eec856bbc3b6e
link
/test release-notes_istio

integ-distroless-k8s-tests_istio
4dce681374024abfe64be6b76d8eec856bbc3b6e
link
/test integ-distroless-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
4dce681374024abfe64be6b76d8eec856bbc3b6e
link
/test integ-distroless-k8s-tests_istio

release-notes_istio
1489ee272fca6ef403761842c24238040365bbe6
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
4dce681374024abfe64be6b76d8eec856bbc3b6e
link
/test integ-distroless-k8s-tests_istio

release-notes_istio
19ae31019247eae5ea7bfd0f9a6f789bd28ed30a
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
072c7378e6e5d70e3caab213f9f7aea27c03a2ea
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
3858f643d806a67f7afc4ac63b6a7a8b95990b00
link
/test release-notes_istio

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

@ramaraochavali @howardjohn : PTAL on revised version

Gentle reminder/Ping! PTAL @hzxuzhonghu @howardjohn @ramaraochavali

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
46766e6f84afea9e7f7ed8ec083cf68714fd8016
link
/test integ-pilot-k8s-tests_istio

release-notes_istio
46766e6f84afea9e7f7ed8ec083cf68714fd8016
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
46766e6f84afea9e7f7ed8ec083cf68714fd8016
link
/test release-notes_istio

integ-pilot-k8s-tests_istio
46766e6f84afea9e7f7ed8ec083cf68714fd8016
link
/test integ-pilot-k8s-tests_istio

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

/test integ-pilot-k8s-tests_istio


Deploy to Heroku Button

Hello,
Would you be willing to consider adding a Deploy to Heroku button in your README? It would sure make browser-based deploying so much easier.
Details:
https://devcenter.heroku.com/articles/heroku-button

Done. @megashub can you please verify that it actually works?

Wow. That was fast! Thank you!! :)
Hmm. The build fails though. Here's some of the log output:
node-icu-charset-detector.target.mk:92: recipe for target 'Release/obj.target/node-icu-charset-detector/node-icu-charset-detector.o' failed
make: *** [Release/obj.target/node-icu-charset-detector/node-icu-charset-detector.o] Error 1
make: Leaving directory '/tmp/build_5a4a441f9e3a5907f6d8b02173a30eb3/crisu83-hubot-twitch-f0eb23d/node_modules/node-icu-charset-detector/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/tmp/build_5a4a441f9e3a5907f6d8b02173a30eb3/crisu83-hubot-twitch-f0eb23d/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)
Heroku has a free tier (which is what I'm using). Might be faster to troubleshoot by test deploying into your own free account. Thoughts?

Yes, of course it's not working. This adapter is not a standalone project that you can run. Instead, you need to create your own Hubot and configure it to use this adapter in order to use it. You can check Acolyte (my Twitch bot) for an example.


Fix reqd

I think the script should be initialized with a shell declaration.
Eg:
#!bin/bash

Did it! :-D


Fix postake seed update range

According to Ouroboros Genesis (top of pg. 13 & pg. 22, fig. 7), the correct range for updating the next epoch seed is the first 2*(R/3) slots. Currently, we update the see in between slot R/3 and slot 2*(R/3), but not for the first R/3 slots. Furthermore (according to pg.22, fig. 7), the correct way to calculate the vrf seed (ηep) is η_ep <- H(η_ep-1 || ep || v). Currently, we initialized the vrf seed at the beginning of each epoch to η_ep <- ∅ and then update it during the seed update range using η_ep <- H(η_ep' || v_sl) (where v_sl is the vrf evaluation for the current slot). Instead, we should do the following to match roughly what the paper does: initialize at the beginning of each epoch to η_ep <- H(η_ep' || ep) and use the same logic for updating the seed.

#2843 fixes the seed update range. The change to the vrf seed initialization needs to happen in another PR before this issue is fully closed.

@es92 @imeckler and @nholland94 to sit down (or stand up, lie down, etc. as they like) and think through this.

I will make this get merged https://github.com/CodaProtocol/coda/pull/3097


chore(userspace/falco): fix punctuation typo in output message when loading plugins

Signed-off-by: Aldo Lacuku<EMAIL_ADDRESS>

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area rules

/area tests

/area proposals

What this PR does / why we need it:
Fix punctuation typo in output message when loading plugins.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

Welcome @alacuku! It looks like this is your first PR to falcosecurity/falco 🎉

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: alacuku
To complete the pull request process, please assign mstemm after the PR has been reviewed.
You can assign the PR to them by writing /assign @mstemm in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/ok-to-test

LGTM label has been added.  Git tree hash: 551bef1c431f38e5a9f7dfa2d22b3fa99aeed7ef

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alacuku, jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/milestone 0.32.0
Closing and reopening to trigger the CI
/close

@leogr: Closed this PR.

In response to this:

/milestone 0.32.0
Closing and reopening to trigger the CI
/close

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.

/reopen

@leogr: Reopened this PR.

In response to this:

/reopen

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.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alacuku, jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Run continuous WorkQueue couch views compaction on the agents

Impact of the new feature
WMAgent
Is your feature request related to a problem? Please describe.
Yes, even though the workqueue and workqueue_inbox databases are quite small in the agents, e.g.:
[cmsdataops@cmsgwms-submit8 current]$ ls -lh install/couchdb/database/
-rw-r--r-- 1 xxx 1.2G Feb  4 08:14 workqueue.couch
-rw-r--r-- 1 xxx  91M Feb  4 08:03 workqueue_inbox.couch

their couchdb views never stop growing, reaching numbers like the following:
[cmsdataops@cmsgwms-submit8 current]$ ls -lh install/couchdb/database/.workqueue_design/mrview/2f77345c5cf5065ec0f98a614222c8b2.view
-rw-r--r-- 1 xxx 58G Feb  4 08:14 install/couchdb/database/.workqueue_design/mrview/2f77345c5cf5065ec0f98a614222c8b2.view

and
[cmsdataops@cmsgwms-submit8 current]$ ls -lh install/couchdb/database/.workqueue_inbox_design/mrview/2f77345c5cf5065ec0f98a614222c8b2.view
-rw-r--r-- 1 xxx 5.5G Feb  4 07:58 install/couchdb/database/.workqueue_inbox_design/mrview/2f77345c5cf5065ec0f98a614222c8b2.view

Describe the solution you'd like
We should enable continuous compaction for those 2 database views. The agents already have a cron entry for the database compaction, but we should create it for their views as well.
Examples of cron entries for the views are can be seen from submit{6,7,8}. We basically have to append the Couchapp name (design doc) to the compact POST request, something like
... workqueue/_compact/WorkQueue' > /dev/null

Describe alternatives you've considered
none
Additional context
none

This has been implemented in WMCore 1.3.3 series through the CouchDB compaction_daemon, which is continuously monitoring and triggering database and view compaction based on the data fragmentation.


Remove cd

Type of change

[ ] Refactor
[ ] New feature
[x] Bug fix
[ ] Optimization
[ ] Documentation Update

Description
This subcommand should have been removed previously
Related Tickets & Documents

Related Issue #
Closes #

Checklist before requesting a review

[x] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.

ah,  no merge perms


new release

could you tag a new release with italian translations?

Done. Tag to 0.3.2 has been pushed and the new version has also been uploaded to PyPi.


An internal error occurred during: "Register Watchers"

!ENTRY org.eclipse.core.jobs 4 2 2021-07-15 15:06:32.003
!MESSAGE An internal error occurred during: "Register Watchers".
!STACK 0
java.lang.NullPointerException: Cannot invoke "org.eclipse.jdt.ls.core.internal.preferences.PreferenceManager.getPreferences()" because "manager" is null
at org.eclipse.jdt.ls.core.internal.ProjectUtils.isVisibleProject(ProjectUtils.java:290)
at org.eclipse.jdt.ls.core.internal.managers.StandardProjectsManager.registerWatchers(StandardProjectsManager.java:418)
at org.eclipse.jdt.ls.core.internal.managers.StandardProjectsManager$1.run(StandardProjectsManager.java:112)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
My project  blocking in refreshing:

java environment:
openjdk version "16.0.1" 2021-04-20
OpenJDK Runtime Environment Zulu16.30+15-CA (build 16.0.1+9)
OpenJDK 64-Bit Server VM Zulu16.30+15-CA (build 16.0.1+9, mixed mode, sharing)

this can be repeatedly, but not for this reason.
I will create a new issue.

this can be repeatedly, but not for this reason.
I will create a new issue.

This extension is not responsible for importing projects.
Please open the issue in https://github.com/redhat-developer/vscode-java/issues.
Thanks.


Question about experiment setting

Hello! @ShirleyMaxx
VirtualMarker is nice work. I have a question about the experiment setting about 3dpw in table 2. Most of the prior works use the mixed datasets to train and then test on 3dpw test set, while virtualmarker is first trained on mixed datasets and then finetuned on 3dpw train set. Do you have the results for virtualmarker trained on mixed datasets which include 3dpw train set instead of fine-tuning for a second stage?

Hi, thanks for your interest. As you said, we report the results by finetuning on the 3DPW dataset for faster training, as MeshTransformer does. We haven't tried to train on mixed datasets which include 3DPW train set. Empirically, if training on mixed datasets, increasing the proportion of 3DPW train set by resampling may be needed for higher 3DPW performance.


Ability to adjust horizon for max brightness and min color temp

I was wondering if you could consider allowing adjustment of the horizon for max brightness and min color temp. Right now it is at sunrise and sunset without the ability to configure it. I would like to both have a cooler color temp at sunset, getting warmer into the evening and also not have peak light brightness right at sunrise. I have a proposal for enabling this functionality below. Two configurable settings would need to be added.
brightness_horizon_offset: percent above horizon where max brightness will be reached; default 0.
color_temp_horizon_offset: percent below horizon where min color temp will be reached; default 0.
I have one option of a working implementation with the code below.
 def calc_brightness_pct(self, percent: float, is_sleep: bool) -> float:
    """Calculate the brightness in %."""
    if is_sleep:
        return self.sleep_brightness
    if percent > (0 + brightness_horizon_offset):
        return self.max_brightness
    delta_brightness = self.max_brightness - self.min_brightness
    return (delta_brightness * (1 + percent) / (1 + brightness_horizon_offset)) + self.min_brightness

def calc_color_temp_kelvin(self, percent: float, is_sleep: bool) -> float:
    """Calculate the color temperature in Kelvin."""
    if is_sleep:
        return self.sleep_color_temp
    if percent > (0 - color_temp_horizon_offset):
        delta = self.max_color_temp - self.min_color_temp
        return (delta * (percent + color_temp_horizon_offset) / (1 + color_temp_horizon_offset)) + self.min_color_temp
    return self.min_color_temp`

Check out the new brightness_mode feature introduced in 1.19.0: https://github.com/basnijholt/adaptive-lighting/blob/104664d3588442730f7ea9e811dd1986aca0c2e8/README.md#custom-brightness-ramps-using-brightness_mode-with-linear-and-tanh
This should give you enough control to separate brightness and color.
Some more examples:
Notice the values of brightness_mode_time_light and brightness_mode_time_dark in the text box.

Check out this new webapp to visualize the parameters https://basnijholt.github.io/adaptive-lighting/

https://github.com/basnijholt/adaptive-lighting/assets/6897215/68908f7d-fbf1-4991-98ce-3f2af6df996f

New brightness control is great! Thanks!

I am glad you like it 😄


Display PVC capacity usage using kubectl

Feature Description

One-line feature description (can be used as a release note): Display PVC capacity usage using kubectl top
Primary contact (assignee): @vkamra
Responsible SIGs: storage
Design proposal link (community repo):
Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
@jingxu97
Approver (likely from SIG/area to which feature belongs): sig-instrumentation-feature-requests
Feature target (which target equals to which milestone):

Alpha release target (x.y)
Beta release target (x.y)
Stable release target (x.y)

Is there a design doc for this? The idea for kubectl top was to expose metrics available in master metric API. How would it work for PVCs?
I think this feature has to be approved by someone from @kubernetes/sig-instrumentation-feature-requests.

@vkamra any updates about the feature status?

@idvoretskyi @fgrzadkowski - doc has the proposal.
PVC metrics are now available in the kubelet summary API (added in 1.8).  @verult is working on adding these into the metrics exposed by heapster.
This would allow us to implement kubetl top pvc to display PVC resource usage in the cluster.

We discussed status in storage-sig - the heapster changes are being worked on but kubectl changes (not designed/discussed yet) are not currently planned for 1.9. @verult @jingxu97 - can you also update?

I would very much prefer if we can not keep extending heapster, and instead maybe use the metrics-server for these purposes.
Also somewhat relevant: https://github.com/kubernetes/kubernetes/issues/55489

@vkamra This should NOT be added to heapster. As @brancz suggested it should be added to master metric API and metric server if needed. We need to move kubectl to using it anyway. It seems that the proposal hasn't been approved. I'd suggest to wait with the implementation for the approval. Also, as suggested earlier - please include @kubernetes/sig-instrumentation-feature-requests in this discussion.

@brancz @fgrzadkowski - that makes sense to me.
Going to let @verult and @jingxu97 comment here as well because I believe they've had more recent discussions about this with members from the instrumentation sig and I might have mis-spoke about extending heapster.
Also added sig-instrumentation as approver.

Yes we synced up with @DirectXMan12 recently and the consensus is that anything kubectl top consumes should go into the metric-server.
I'm still working on adding logic in Heapster because it's required to expose PVCStats to StackDriver  (because metric-server doesn't support sinks like Heapster does).

@verult is this feature in for 1.10? If so, we also need docs information (here. If not, can you please target next or 1.11? Thanks! cc @idvoretskyi

@Bradamant3 AFAIK there's no work being done for this release, so if anyone has permissions to change the milestone please move it to 1.11. I also may not be able to look at this feature for 1.11, unfortunately.

@verult @vkamra
Any plans for this in 1.11?
If so, can you please ensure the feature is up-to-date with the appropriate:

Description
Milestone
Assignee(s)
Labels:

stage/{alpha,beta,stable}
sig/*
kind/feature

cc @idvoretskyi

This feature current has no milestone, so we'd like to check in and see if there are any plans for this in Kubernetes 1.12.
If so, please ensure that this issue is up-to-date with ALL of the following information:

One-line feature description (can be used as a release note):
Primary contact (assignee):
Responsible SIGs:
Design proposal link (community repo):
Link to e2e and/or unit tests:
Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
Approver (likely from SIG/area to which feature belongs):
Feature target (which target equals to which milestone):

Alpha release target (x.y)
Beta release target (x.y)
Stable release target (x.y)

Set the following:

Description
Assignee(s)
Labels:

stage/{alpha,beta,stable}
sig/*
kind/feature

Once this feature is appropriately updated, please explicitly ping @justaugustus, @kacole2, @robertsandoval, @rajendar38 to note that it is ready to be included in the Features Tracking Spreadsheet for Kubernetes 1.12.

Please note that Features Freeze is tomorrow, July 31st, after which any incomplete Feature issues will require an Exception request to be accepted into the milestone.
In addition, please be aware of the following relevant deadlines:

Docs deadline (open placeholder PRs): 8/21
Test case freeze: 8/28

Please make sure all PRs for features have relevant release notes included as well.
Happy shipping!
P.S. This was sent via automation

AFAIK there are no plans for this in 1.12. Unfortunately I don't have edit access to the Feature Description up top

Thanks for the update, @verult! I've edited the description.

/remove-lifecycle stale

Hi @verult
This enhancement has been tracked before, so we'd like to check in and see if there are any plans for this to graduate stages in Kubernetes 1.13. This release is targeted to be more ‘stable’ and will have an aggressive timeline. Please only include this enhancement if there is a high level of confidence it will meet the following deadlines:
Docs (open placeholder PRs): 11/8
Code Slush: 11/9
Code Freeze Begins: 11/15
Docs Complete and Reviewed: 11/27
Please take a moment to update the milestones on your original post for future tracking and ping @kacole2 if it needs to be included in the 1.13 Enhancements Tracking Sheet
Thanks!

Bump. This would be super useful.

Has this been continued somewhere? It would be super useful

How do you folks currently see the usage of pvc?

I think the plan is to rely on plugins for this: https://github.com/yashbhutwala/kubectl-df-pv


use maybes for unsafe operations

Certain Ramda functions are unsafe. Take this quartet, for example:
R.head :: [a] -> a | Undefined  -- unsafe
R.last :: [a] -> a | Undefined  -- unsafe
R.tail :: [a] -> [a]            -- safe, but misleading
R.init :: [a] -> [a]            -- safe, but misleading

I suggest the following types:
R.head :: [a] -> Maybe a
R.last :: [a] -> Maybe a
R.tail :: [a] -> Maybe [a]
R.init :: [a] -> Maybe [a]

We could also provide the unsafe versions:
R.unsafeHead :: [a] -> a | Undefined
R.unsafeLast :: [a] -> a | Undefined
R.unsafeTail :: [a] -> [a]
R.unsafeInit :: [a] -> [a]

We'd also provide the following function which takes a default value as its first argument:
R.fromMaybe :: a -> Maybe a -> a

Let's consider a simple example: taking the first element of a [String] of unknown length and converting it to upper-case.
// Naive solution (will throw if list is empty)
R.toUpper(R.head(list))

// Pre-emptive check
R.ifElse(R.isEmpty, R.always('<default>'), R.pipe(R.head, R.toUpperCase))(list)

// Maybe
R.fromMaybe('<default>', R.map(R.toUpperCase, R.head(list)))

It's cleaner and less error-prone to map over a maybe than to rely on checking for the empty list whenever one uses a member of this quartet.
These types are used by purescript-arrays. I'd like to Ramda do the same.

These list functions are available in Sanctuary, a JavaScript library for manipulating values without null checks. Sanctuary plays nicely with Ramda, and takes advantage of R.map's dynamic dispatch.

Sanctuary looks pretty nice

Very nice!

@austbot i intend a PR to add Just and Nothing to R, i just haven't had time. See also: #1749
Then you could just:
const safeHead = (xs) => xs.length === 0 ? Nothing() : Just(R.head);
in your example: why [ ] for the head of the empty list? also, n will be a function, and you are not using a in the body of the function. Probably meant R.nth(0, a)? And if you have undefined values in your list that you want for some reason, the test may or may not be what you intend. IOW, you may be better off checking the length of the list rather than grab the element at index 0.

i'm sorry you did, it makes my comment a non sequitur


review of series of papers looping over papers and questions

A first attempt to iterate over files in a folder and questions from a question list, answering the questions one by one and for each file in the folder. Results are gathered in a csv file.
For the list of questions, a standard name "questions.txt" is used, for the results a standard name "result.tsv" is used.

additional commit to prevent merging conflicts

Hi @ChrisCleaner, I will merge this branch with main. It turns out that merging main into this branch is cumbersome because of additional changes in querier that I made in the meantime. If things don't work well, I will make an additional PR


Improve COPY FROM .. RETURN SUMMARY output

Importing a file that contains thousands of lines that cannot be imported using COPY .. FROM .. RETURN SUMMARY outputs the errors like:
errors: {
  "<error-message>": {
    "count": n,
    "line_numbers": [ ... ]
  }
}

Having thousands of line numbers within line_numbers currently kills the admin ui. But even in crash, where it is output (eventually, depending on your terminal), it is barely helpful because you end up scrolling a long time until you see the error.
I think we should trim the line_numbers to a maximum. Maybe 50, or 100?

I think we should trim the line_numbers to a maximum. Maybe 50, or 100?

Yep valid points, agree. Maybe 50 is already enough?

can/should we indicate somehow that this is an limited output? or is the gap count vs number of line_numbers plus documentation enough?

can/should we indicate somehow that this is an limited output? or is the gap count vs number of line_numbers plus documentation enough?

I think changing the response format in shape is problematic because of BWC. But we can extend the documentation


Missing extension: iconv

Hi,
would it be possible to add the iconv-extension to the docker image? With :latest I get
Error: Call to undefined function iconv()

Thank you!

Closing this myself as it doesn't seem practical to add every user-requested extension. A solution by configuration would be preferable.


Add 1:1 spec tests; fix spec as a result

@domenic
The first commit matches the current spec, and passes all the A+ tests.
The second commit makes the required tweaks to the JS to pass the new "finally" tests.
The third commit updates the spec text to match the now-passing JS.
tl;dr: the approach of [[Type]] being "Finally" didn't work well after all, because PromiseReactionJob didn't know whether the promise was resolved or rejected. This approach uses the Fulfill/Reject reactions to convey that knowledge, building up callback functions in PerformPromiseFinally rather than deferring that logic til a later tick.
Check out the branch and run npm test to run both the A+ tests and the "finally" tests.

As for subclassing friendliness, with then and catch, then(null, x) has identical semantics to .catch(x), so it seems appropriate to have the latter delegate to the former - but .finally(x) has much more complex semantics. Since it's using SpeciesConstructor, it seems like it'd be subclassing-friendly as-is?

I think that the simpler semantics that async function uses isn't an option here, because this one has to be subclassing-friendly, but async function does not. In other words, specifically to support subclassing, it has to use SpeciesConstructor, otherwise MyPromise.resolve().finally() would produce a Promise instead of a MyPromise, no?

As for subclassing friendliness, with then and catch, then(null, x) has identical semantics to .catch(x), so it seems appropriate to have the latter delegate to the former - but .finally(x) has much more complex semantics.

Sure, but they can still be expressed in terms of .then()

Since it's using SpeciesConstructor, it seems like it'd be subclassing-friendly as-is?

No, SpeciesConstructor is kind of a red herring (and a historical design mistake IMO). It generally doesn't have anything to do with well-behaved subclasses, just strange ones that do weird things.
The real question is: if you override then() to have different behavior, will finally() also impact that behavior? E.g. consider
class PlusOnePromise extends Promise {
  then(f, r) {
    return super.then(x => f(x + 1), x => r(x + 1));
  }
}

If you use these things with .then or .catch, they will inherit the plus-oneing. But if you use them with .finally, they will not. That's what we mean by not being subclassing friendly.

I think that the simpler semantics that async function uses isn't an option here, because this one has to be subclassing-friendly, but async function does not. In other words, specifically to support subclassing, it has to use SpeciesConstructor, otherwise MyPromise.resolve().finally() would produce a Promise instead of a MyPromise, no?

I'm specifically talking about whether we should check this.constructor, or just go ahead and use NewPromiseCapability regardless. SpeciesConstructor is again unrelated.

I can certainly delegate into .then but I think it makes for much more awkward spec language around the finally semantics, which is why I wrote it with PerformPromiseFinally in the beginning.
In general, I also don't like that .catch delegates to .then - i'd prefer that someone has to override .catch explicitly to change its behavior - and i'd prefer the same with .finally if possible.
I'm still not sure I understand what you mean by "check this.constructor" - if it delegates to .then, it's using SpeciesConstructor; in my current PR, it uses SpeciesConstructor - are you suggesting that this one promise method should not use SpeciesConstructor, and should call NewPromiseCapability with the this.constructor value? That seems like it'd be a big deviation from how the other Promise.prototype methods work - I think that because .then and .catch use SpeciesConstructor, this must too.

I think it makes for much more awkward spec language around the finally semantics,

Hmm, I'm curious how?

In general, I also don't like that .catch delegates to .then - i'd prefer that someone has to override .catch explicitly to change its behavior - and i'd prefer the same with .finally if possible.

I think we should strive for consistency.

I'm still not sure I understand what you mean by "check this.constructor"

You are using PromiseResolve, which checks the .constructor property. You could instead just do NewPromiseCapability() + [[Resolve]], like async/await does. I'm not sure which is better.
Again, SpeciesConstructor is unrelated... I'm really unclear why you keep bringing it up?

I think we should strive for consistency.
If that's the case (that every promise prototype method delegates to .then when possible) then I'd prefer to get this merged, and prepare another PR that modifies the spec steps to do that so we can compare the two (since what's in master isn't correct anyways).

Re constructor stuff, maybe we're not on the same page :-) maybe we could set up a call to clarify? i can ping you offline.

If that's the case (that every promise prototype method delegates to .then when possible) then I'd prefer to get this merged, and prepare another PR that modifies the spec steps to do that so we can compare the two (since what's in master isn't correct anyways).

That makes sense.

Re constructor stuff, maybe we're not on the same page :-) maybe we could set up a call to clarify? i can ping you offline.

Sure!

Per discussion:

moved the constructor check from PromiseResolve back up to Promise.resolve
Since ".finally calls into .then" would observably expose more functions to the user, we're going to stick with the current approach (modulo editorial tweaks to the "create a function" language) for now.
add an agenda item to discuss the constructor check at the next meeting


insert closed at in state tables

This PR implements closed_at field at state tables:
account_signers
accounts
claimable_balances
liquidity_pools
offers
trustlines

@cayod, @chowbao found a much simpler way to fetch closed_at from the ChangeCompactor itself. He made the changes in #208 so I'm closing this PR


Feature request: Easy method / description for overriding policy assignments.

Description

We need to be able to override some of the policy created and assigned by the Enterprise Scale module. Normally this is done by creating override files in the /lib folder I believe.
Describe the solution you'd like

A method or code update to allow us to easily override policy parameters, assignments and effects.
In the YAML Scheme Reference, it does mention a field called 'archetypes_config_overrides' - is this where it could be done?
As an example, the 'Configure backup on virtual machines without a given tag to a new recovery services vault with a default policy' isn't deployed with the name of the tag we'd need to stop it creating Recovery Vaults everywhere!
Another example: The 'Management port access from the Internet should be blocked' policy doesn't like complex NSG rules i.e. those that have a list of ports including port ranges. Until the issue is identified, we'd like to be able to put that policy in audit mode.
Describe any alternatives you've considered

Additional context

You can use a custom lib folder by updating the code post bootstrap. For vNext we will likely provide a mechanism for this.
I'm not sure there is a way to turn on or off policy assignments using variables, so you would need a custom lib for that.
Closing this for now, since we'll provide better support in vNext and there is a workaround to add your own lib folder and update the .tf files post bootstrap.

Gents. It's not clear 'how' to add a lib folder and therefore put the overrides in.
I'm aware of how to add extra Terraform code in post-bootstrap, but not how to do the work with the lib folder considering that the module is only downloaded upon each init stage.
Can you please provide guidance?

You need to use library_path variable like in this example: https://github.com/Azure/terraform-azurerm-caf-enterprise-scale/wiki/[Examples]-Deploy-Custom-Landing-Zone-Archetypes#maintf
It is quite possible I am missing something here?


Noticed a bug when opening a new connection and closing the inventory tab immediately

Bug description

I went to pop open a new server connection this evening and closed the inventory tab while it was connecting.
It left the ssh screen width the same as if the tab was open and only assumed the full width of my display once I opened that tray back up and closed it again.
This was on my iPad.  I did not try it on my Mac.
From mrelcee on Discord

Hello @mrelcee 👋
Thank you so much for your report!
When you say « and closed the inventory tab » : hiding it you mean?

Correct

I will try to reproduce today

More a cosmetic issue.   The ssh screen opened the same width as it would have with that inventory tab open, flush to the left.

I wanted to follow up on this.   Have you determined what causes this issue?
Thanks

Hello @mrelcee
No I don’t have found the root cause nor I’m not able to reproduce it on my LAN and WAN servers.
I need to try with a high latency server but didn’t found yet the time to find one.


Samples argument for vcf2bam

@ajo2995 Could we get more info on the --samples argument in scripts/gg-wrapper-bam2vcf.pl? It sounds like a flat text file with assembly names? Is that right? Is there an example available?

Is it list_of_assemblies.txt ?

yes, but I'm sure you've tried that by now...

It might be a good idea to increase the window size to 1000000 so the vcf-concat command line doesn't exceed some limit (there will be thousands otherwise)


cost related to doing the sentinel attack ?

hi is there anywhere i can get input as to caculating what cost a setup like what you have build here for approx 100 servers
i have run sysmon and can see that my servers individually generate an approx abount of data pr day. This is easy to multiply and I can also look at the cost calculator in terms of GB sent to sentinel.
But what about the ksql queries, will i not get additional cost if i set these to run at 5,10,15 min interval, and will this cost not go up as I apply more of the ksql queries ?

Added costs paragraph on wiki home page


New package: rsteube.Carapace v0.23.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.4 schema?

Resolves https://github.com/microsoft/winget-pkgs/issues/99770

Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service agree

Bot seems to be stuck?


Specify an Index for ES

Apologies if I missed this, but I've been trying to figure out how to specify an elasticsearch index value in the .yaml file. Is there an environment variable for that?

By default the Fluentd <> Elasticsearch template uses Logstash format, this is enabled here:
https://github.com/fluent/fluentd-kubernetes-daemonset/blob/master/docker-image/v0.12/elasticsearch/conf/fluent.conf#L12
You can change that altering the configuration file and setting logstah format to false and adding something like:
index_name fluentd
type_name fluentd

change your index and type names as required

question answered. closing.

the ref page is off =(


Activating Open Collective

Hi, I'm making updates for Open Collective. Either you or another core contributor signed this repository up for Open Collective. This pull request adds financial contributors from your Open Collective https://opencollective.com/CollapsibleTableSectionViewController ❤
What it does:

adds a badge to show the latest number of financial contributors
adds a banner displaying contributors to the project on GitHub
adds a banner displaying all individuals contributing financially on Open Collective
adds a section displaying all organizations contributing financially on Open Collective, with their logo and a link to their website

P.S: As with any pull request, feel free to comment or suggest changes.
Thank you for your great contribution to the Open Source community. You are awesome! 🙌
And welcome to the Open Collective community! 😊
Come chat with us in the #opensource channel on https://slack.opencollective.com - great place to ask questions and share best practices with other Open Source sustainers!

Codecov Report

Merging #67 into master will decrease coverage by 0.55%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #67      +/-   ##
==========================================
- Coverage   92.59%   92.03%   -0.56%
==========================================
  Files           2        2
  Lines         135      113      -22
==========================================
- Hits          125      104      -21
+ Misses         10        9       -1

Impacted Files
Coverage Δ

...roller/CollapsibleTableSectionViewController.swift
95.23% <0.00%> (-0.87%)
:arrow_down:

...ionViewController/CollapsibleTableViewHeader.swift
88.00% <0.00%> (+0.06%)
:arrow_up:

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 86645bc...b009da9. Read the comment docs.


Errors prevented startup

Hello and thanks for your work on bootstrap 3 with less for meteor. i recently removed twbs:bootstrap from my meteor app so that i could add in your bootstrap package that uses less.  after following the steps i read on stackoverflow (although i couldn't get past the -sed step), when my app runs it gives the following error:
=> Errors prevented startup:

   While processing files with huttonr:bootstrap3 (for target web.browser):
   native: Unexpected token /
   at Object.parse (native)
   at plugin/bootstrap3.js:140:25
   at BootstrapCompiler.processFilesForTarget (plugin/bootstrap3.js:342:9)

=> Your application has errors. Waiting for file change.

Not sure if this is an issue with your package or with my setup, but hoping you can help. sorry if something stupid, I'm still new with Meteor and Bootstrap.

The stackoverflow article you referenced is very old and is not applicable to current Meteor versions.
I don't mind assisting.  What version of Meteor are you running and what OS?

@dayjimenez
Is this still an issue for you?


Thunderbolt 3 drivers

there are some patches inside your ACPI folder，eg.SSDT-TB-DSB0.aml
SSDT-TB-DSB1.aml
SSDT-TB-DSB2-XHC2.aml
SSDT-TB-DSB2.aml
SSDT-TB-DSB3.aml
SSDT-TB-DSB4.aml
SSDT-TB-DSB5.aml
SSDT-TB-DSB6.aml
SSDT-TB3.aml
which is about Thunderbolt 3，and other drivers is required？

honestly I didn't test thunderbolt 3


#default_wait_time is deprecated, please use #default_max_wait_time

After upgrading to the latest Capybara I get a deprecation warning caused by Capybara webkit:
DEPRECATED: #default_wait_time is deprecated, please use #default_max_wait_time instead
I traced it to the file lib/capybara/webkit/driver.rb line 338. Should be a simple fix, but if we fix it we would probably need to lock to the latest Capybara. I'll leave it to the maintainers to decide how to proceed.
(A simple workaround to suppress the warning is to manually add a ":wait" option to any calls that work on a modal)

Fixed by #842. Will be included in capybara-webkit 1.7.1.


Expose programmatic test suite (like A+ test suite)

I'm willing to work on this, just ain't sure if this should be part of this repo. Should I just start to work on this here, so you could just publish this from here?

I was not aware of especially, need to dig into it more, to udnerstand what is its job.
I've asked about this on aplus-tests repo here, but they have said it's not their job to support finally test suite. That's why I have asked here later.
My goal is to have some complete A+ test suite with finally in it, or a test suite focused solely on the finally, so it can be reused in implementations willing to support this feature.

@Andarist Have you considered making the test262 tests for Promise.prototype.finally available "programmatically"? cc @rwaldron @leobalter @jugglinmike

I think test262 is probably the best bet if you’re trying for spec compatibility.

@littledan not really, had no idea there are tests for this. Seems like a broader topic though, it would be cool to have many of those tests converted, so they could have been used by passing a custom implementation (would be good to use adapter approach for this ofc).
I could try to work on this, we'd have to establish first how this could have been achieved and later could be implemented in parts (converting only some at a time).

They don’t need conversion; test262 tests can be ran via test262-harness with a custom prelude, against any implementation.

Good to know! Looking on it, it seems that https://github.com/bterlson/test262-harness is the way to go.

@Andarist I'm looking forward to hearing how you find things. Maybe we need better documentation for how to use test262-harness, or more infrastructure to run the appropriate subset of tests.

@Andarist I'm looking forward to hearing how you find things

Ain't sure how to answer that 😅 I just search through things I had some exposure to. Like in this case - I knew there is extensive A+ promises test, so I've asked there about this, later I came here, because it's a spec repo and I've noticed it has some tests that Im interested in. I knew about test262 but thought it's more focused on syntax and stuff, didnt know it has builtins tests, so I haven't really look that way when searching for this.
Cross referencing repos would certainly help! But at the same time it's really easy to miss those.
I havent yet started setting up test262-harness but it seems it should be quite straight forward, its docs are OK. Main README of test262 also mentions harnesses etc so I don't think you can do any better there.

If you think of any way to make the docs clearer through this process, or run into any pain points, feel free to file a bug or PR at the appropriate place.


Make CTA boxes more obviously clickable, especially on mobile.

          On mobile, there's no real indication that you can click on these three cards. With a mouse, you get a pointing hand cursor on hoover, but there's obviously no such indication on mobile.

Originally posted by @SebastiaanZ in https://github.com/EuroPython/website/pull/235#discussion_r1120282034

@hypha Is this still an issue?

I think this has not changed from the time the issue was raised (by @Vaibhavs10 and @SebastiaanZ) in the original comment. So I imagine it is still an issue.  But I also think it might be a good idea to ask people who are experienced in accessibility to weigh in (@ADubhlaoich comes to mind).

In the wider scope of UX interactions this feels closely related to #697, too.
I will review the current state of the website for recommendations (And maybe open a PR myself, since things are quiet now post-conference).


Bump Iceberg version

Description
Iceberg has already released 1.4.0, 1.4.1, 1.4.2 and 1.5.0. Meanwhile, Gluten only supports the Iceberg 1.3.1 version, which could support bumping the released version.

cc @liujiayi771.

The current implementation has compatibility issues with the latest version of Iceberg that need to be resolved.

The current implementation has compatibility issues with the latest version of Iceberg that need to be resolved.

Hi, @liujiayi771 Can you explain some detail of compatibility issues? We are currently using both iceberg 1.3 & 1.4, and we look forward to resolve these issues.

@j7nhai We have already upgraded the Iceberg version of Spark 3.4 to 1.4.3. The compatibility issues mentioned above might have been partially resolved. I don't remember the specific details, but you can try upgrading the version. If the end-to-end tests and unit tests can pass, it should be fine.


[Fix #7261] Do not insert empty lines in FrozenStringLiteralComment

FrozenStringLiteralComment should only be concerned about inserting/removing the magic comment as necessary but not about its spacing. So it should never insert empty lines.
The spacing is the responsibility of EmptyLineAfterMagicComment.
This closes #7261.
The change itself was pretty straightforward but I was surprised how much impact it had on other specs, especially on cli_autocorrect_spec.rb although the examples there mostly did not care at all about how FrozenStringLiteralComment works. By adding a lot of --onlys I tried to restrict these examples to the cops they really need (if possible) such that they will not be affected by similar changes in the future.

The changes look ok to me. I'll wait until you agree with @Drenmi on the final cleanup of the code.

@buehmann Can you rebase?


Handle windows line endings when copying content from hb/docs

Handle Windows line endings when copying content from handbook/docs.

this still isn't fixing the issue unfortunately - this is what I had tried locally, but the particular file in question isn't collapsing the --- as we'd expect

Has the file in question been fixed to have the expected --- at the start?

Has the file in question been fixed to have the expected --- at the start?

yes.
Although, looking in detail, it may be where I've mixed the line endings with my own editing:
---$
originalPath: marketing/webinars.md$
updated: 2023-01-31 13:45:55 +0700$
---$
---^M$
navTitle: Marketing^M$
---^M$

Unix line endings (\n or LF) as $ and Windows line endings (\r\n or CRLF) as ^M$.

I've just merged https://github.com/flowforge/handbook/pull/206 to fix the file in git.

Can confirm that has fixed it for me locally. A clean checkout of handbook + this branch builds correctly.


FR: cleanup on startup

Plugin managers like lazy.nvim are also able to automatically uninstall unused plugins. This is particularly useful when working on multiple machines, and you want to keep your installed tools in sync as well.
Currently, ensure_installed only ensures that a tool that is listed, but not installed, is being automatically installed. However, tools that are installed but not listed are not automatically uninstalled.

Anything that does this would need to be opt-in. I often install things using the :Mason menu. Eventually I may add it to my list of things to automatically install, or I may delete it.
This seems like a reasonable request. I can see it as a user command or api call. This can be called by the user whenever the user wants it to run including startup.

The current main has a new command: MasonToolsClean. Try it out. Let me know if it works for you. Currently no documentation.

Thank you very much! I just gave it a try and so far everything seems to work.
Only thing I noticed was that as opposed to MasonToolsInstall, there are apparently no notifications to inform you about the cleanup (yet).

It's using vim.notify to print the messages.


fix: Fixed issue with multiple grants in aws_s3_bucket_acl

Description
It is ain't much but it's honest work it fixes issue with grant property failing the terraform plan.
Issue reported & described in details here: #162
Fixes #162
Motivation and Context

It is required to enable terraform plan to complete while using grant property.
Breaking Changes

None.
How Has This Been Tested?

[ ] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[ ] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

This PR is included in version 3.2.2 :tada:

Thank you for this fix, @m4t22 !


Predefine selected value using external API

Hi,
I'm trying to use the multiselect as an autocomplete and I encounter blockages on edit.
Here is the context :
I'm using an external API to fetch addresses and I only store few data in my database like street, postcode, citycode, location (lat, lon) ...
I got no problems on create because it's a fresh form but I don't know how to predefine the selected address on update since my database is not formatted like the API response.
There is any possibility to display the selected label without linking it with an existing option value of the multiselect ?
Thanks a lot for your help
Mathieu

Found the response => https://github.com/vueform/multiselect/issues/143