Bear 2.0/Beta support request

Hey Drgrib, thank you so much for constantly updating this alfred-workflow and keeping it up for all of us to use. Its an amazing addition! Recently, i've been granted the use of Bear 2.0/private beta key and noticed that the workflow doesn't convert work for it.
On the surface I figured it would be an easy fix by going into the .go files and replacing the DBpath with the new SQL database used to store the notes, and replacing the xcallback urls found in the workflow scripts with the newer versions.
Everything seemed to be working and the scripts were in fact working with bear 2.0, but i ran into a problem with the sql database, and despite changing dbpaths, I haven't been able to get the alfred workflow to find all the new notes created with bear 2.0
Below I've attached some screenshots of where i got the sql file path from and the new xcallback urls.
Hoping to see whether you could help out with the new sql database update, because I'm not a coder and its been frustrating me.

Note: The new xcallback urls just add a "2" at the back of "bear"
Note: The new SQL Database uses 5 tags instead of 7

Thanks for the heads up on this. Unfortunately, without sitting down with the new database myself and debugging, it is unlikely I'll figure out what needs to be changed. I can tell you upfront, it almost certainly isn't going small fix because I'll need to build in backwards compatibility for people still using the old version. If I had to guess, it will probably take me weekend to work through.
If you can tell me how to get access to the beta, it would probably be best if I work on this before it is released.

Thanks for your reply! The beta is currently still in its private beta phase and is most likely going to remain so till they publicly release it somewhere near start of 2024. This is the official forum to apply for the beta key, however it might take some time to get a reply.
If you would like, I could forward you the email which granted me the access to the private beta, along with the download link for it. If that's something you're interested in, please reply with your email attached so I can get it done swiftly!

Thanks for offering. After thinking about it, I think I should probably just wait for the public release. My development time outside of work is pretty limited and the database structure could change before release and even be changed to match exactly what it is now.

FYI - I was missing my BearSearch in Beta 2 (it's been taking a while!), so I upgraded the workflow.  I'm not familiar with Alfred Workflows, but was able to see the mirror of the project in the workflow folder.
I cloned the repo, made changes, built the project and copied over the workflow used by Bear.
I had to change:

callback url (from 'bear' to 'bear2')
the location to the folder for Bear2 Application Data
some sql calls - table and index name changes.

Working fine for me - I use it solely for search:
https://github.com/dgdosen/alfred-bear

Also - from looking at the Bear V2 beta forums, the V2 locations are all temporary.  The real launch of V2 will just use the V1 locations.
So - this is a hack 😄 for people using B2 only.

That's what I suspected, which is why I didn't attempt to bake any of these locations into the workflow permanently. Thanks for the reference code in case they do actually change them.

If you only want ver2.0 in use:

Simply add "2" in all script after "bear", i.e., open "bear2://x-callback-url/create?{query}&show_window=yes&new_window=no&edit=no"
cd /Applications and delete the original Bear.app (Do not use App Cleanr & Unistaller or others)
Move Bear.app (2.0 version) into /Applications
Empty trash

Hey!  Just did a quick run with the pre-release beta.  (This uses the correct paths as the public version).  Looks like the new database does not include the Z_7TAGS table.

Thanks for the heads up. I'll debug this as soon as the new version goes live since I am a daily user of the workflow myself.

According to the beta forums, the new version should be up tomorrow 🥳

According to the beta forums, the new version should be up tomorrow 🥳

Can confirm the v2 is now live

I will merge in #54 either tonight or tomorrow morning when I have an open time window to debug if necessary. Based on testing comments on the request, I anticipate that is should just work.

Appreciate your time and effort 🙏

@drgrib thanks so much for updating! FYI, the download link in the new README is giving me this error
<Error>
NoSuchKey
<Message>The specified key does not exist.</Message>
<Key>130618635/33ba4883-f270-49cb-816e-bc233acbe239</Key>
<RequestId>DVTF2VG2ZV42KBSK</RequestId>
<HostId>sapgtNlYqwMDCXl5wD5w+fj8t4lIdkgDt9BqFDCWBCw90iEfnL3xjqnCtgYuZxjdIUf03EzlGG8=</HostId>
</Error>

I just updated the release workflow file to fix an issue that caused tags to disappear. My guess is you were trying to download during the window where I removed the old binary. Please give it another try. If it is still a problem, please open a new issue.
Anyone who downloaded the file before 6 minutes ago will also want to redownload it for the fix.
Enjoy the new Bear with Alfred support everyone :)

@drgrib working now! Thanks so much! I've really been missing this plugin while using the Bear beta

Amazing. Thanks so much! Anyway to change setting so the note text is not a header?

@chrisbarrettm I honestly have no idea what you are talking about. Please open a new issue and post a screenshot of what you are referring to.


Add retry to iptables command for xtables lock contention.

fix https://github.com/istio/istio/issues/31936. To verify this, I tested the change with this commit https://github.com/bianpengyuan/istio/commit/11a99106126237555a7e9484b25393eb94c0efce, which proves retry logic is indeed triggered.

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

/test all

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
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.

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

Test name
Commit
Details
Rerun command

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

integ-operator-controller-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
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.

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

Test name
Commit
Details
Rerun command

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

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

integ-distroless-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
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.

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

Test name
Commit
Details
Rerun command

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

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

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

integ-ipv6-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
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.

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

Test name
Commit
Details
Rerun command

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

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

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

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

integ-helm-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-helm-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.

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

Test name
Commit
Details
Rerun command

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

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

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

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

integ-helm-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-pilot-multicluster-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.

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

Test name
Commit
Details
Rerun command

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

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

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

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

integ-helm-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-pilot-multicluster-tests_istio

integ-cni-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-cni-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.

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

Test name
Commit
Details
Rerun command

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

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

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

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

integ-helm-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-pilot-multicluster-tests_istio

integ-cni-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
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.

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

Test name
Commit
Details
Rerun command

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

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

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

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

integ-helm-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-pilot-multicluster-tests_istio

integ-cni-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-cni-k8s-tests_istio

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

integ-telemetry-mc-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-telemetry-mc-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.

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

Test name
Commit
Details
Rerun command

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

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

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

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

integ-helm-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-pilot-multicluster-tests_istio

integ-cni-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-cni-k8s-tests_istio

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

integ-telemetry-mc-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
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.

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

Test name
Commit
Details
Rerun command

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

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

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

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

integ-helm-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-pilot-multicluster-tests_istio

integ-cni-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-cni-k8s-tests_istio

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

integ-telemetry-mc-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-telemetry-mc-k8s-tests_istio

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

integ-telemetry-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
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.

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

Test name
Commit
Details
Rerun command

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

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

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

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

integ-helm-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-pilot-multicluster-tests_istio

integ-cni-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-cni-k8s-tests_istio

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

integ-telemetry-mc-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-telemetry-mc-k8s-tests_istio

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

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

integ-security-multicluster-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-security-multicluster-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 all

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

Test name
Commit
Details
Rerun command

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

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

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

integ-helm-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-pilot-multicluster-tests_istio

integ-cni-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-cni-k8s-tests_istio

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

integ-telemetry-mc-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-telemetry-mc-k8s-tests_istio

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

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

integ-security-multicluster-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-security-multicluster-tests_istio

unit-tests_istio
2c846b25f9538b6d7b9c73923321e5db94d4954a
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.

@bianpengyuan: PR needs rebase.

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

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

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-pilot-multicluster-tests_istio

integ-cni-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-cni-k8s-tests_istio

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

integ-telemetry-mc-k8s-tests_istio
e1546f23ae8ab23e6f526e21f57e1a9cd57980f9
link
/test integ-telemetry-mc-k8s-tests_istio

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

unit-tests_istio
3858e6cab26bfb509a3ff951b75e7c4afdbde7cb
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
4152839df052db644dab975608026c9992cad13b
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test unit-tests_istio

release-test_istio
4152839df052db644dab975608026c9992cad13b
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test unit-tests_istio

release-test_istio
4152839df052db644dab975608026c9992cad13b
link
/test release-test_istio

integ-cni-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-cni-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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test unit-tests_istio

release-test_istio
4152839df052db644dab975608026c9992cad13b
link
/test release-test_istio

integ-cni-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test unit-tests_istio

release-test_istio
4152839df052db644dab975608026c9992cad13b
link
/test release-test_istio

integ-cni-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
4152839df052db644dab975608026c9992cad13b
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test unit-tests_istio

release-test_istio
4152839df052db644dab975608026c9992cad13b
link
/test release-test_istio

integ-cni-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-operator-controller-tests_istio

lint_istio
4152839df052db644dab975608026c9992cad13b
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test unit-tests_istio

release-test_istio
4152839df052db644dab975608026c9992cad13b
link
/test release-test_istio

integ-cni-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-operator-controller-tests_istio

lint_istio
4152839df052db644dab975608026c9992cad13b
link
/test lint_istio

integ-distroless-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test unit-tests_istio

release-test_istio
4152839df052db644dab975608026c9992cad13b
link
/test release-test_istio

integ-cni-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-operator-controller-tests_istio

lint_istio
4152839df052db644dab975608026c9992cad13b
link
/test lint_istio

integ-distroless-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test unit-tests_istio

release-test_istio
4152839df052db644dab975608026c9992cad13b
link
/test release-test_istio

integ-cni-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-operator-controller-tests_istio

lint_istio
4152839df052db644dab975608026c9992cad13b
link
/test lint_istio

integ-distroless-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-multicluster-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-multicluster-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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test unit-tests_istio

release-test_istio
4152839df052db644dab975608026c9992cad13b
link
/test release-test_istio

integ-cni-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-operator-controller-tests_istio

lint_istio
4152839df052db644dab975608026c9992cad13b
link
/test lint_istio

integ-distroless-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-multicluster-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test unit-tests_istio

release-test_istio
4152839df052db644dab975608026c9992cad13b
link
/test release-test_istio

integ-cni-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-operator-controller-tests_istio

lint_istio
4152839df052db644dab975608026c9992cad13b
link
/test lint_istio

integ-distroless-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-multicluster-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-helm-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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test unit-tests_istio

release-test_istio
4152839df052db644dab975608026c9992cad13b
link
/test release-test_istio

integ-cni-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-operator-controller-tests_istio

lint_istio
4152839df052db644dab975608026c9992cad13b
link
/test lint_istio

integ-distroless-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-multicluster-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test unit-tests_istio

release-test_istio
4152839df052db644dab975608026c9992cad13b
link
/test release-test_istio

integ-cni-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-operator-controller-tests_istio

lint_istio
4152839df052db644dab975608026c9992cad13b
link
/test lint_istio

integ-distroless-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-multicluster-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-security-multicluster-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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test unit-tests_istio

release-test_istio
4152839df052db644dab975608026c9992cad13b
link
/test release-test_istio

integ-cni-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-operator-controller-tests_istio

lint_istio
4152839df052db644dab975608026c9992cad13b
link
/test lint_istio

integ-distroless-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-multicluster-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-security-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test unit-tests_istio

release-test_istio
4152839df052db644dab975608026c9992cad13b
link
/test release-test_istio

integ-cni-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-operator-controller-tests_istio

lint_istio
4152839df052db644dab975608026c9992cad13b
link
/test lint_istio

integ-distroless-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-multicluster-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-security-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-telemetry-mc-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.

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

Test name
Commit
Details
Rerun command

integ-cni-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-k8s-tests_istio

integ-distroless-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-multicluster-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-security-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-telemetry-mc-k8s-tests_istio

integ-operator-controller-tests_istio
fbae30971db2523a3360840df4c98138e6365391
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.

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

Test name
Commit
Details
Rerun command

integ-cni-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-multicluster-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-security-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-telemetry-mc-k8s-tests_istio

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

integ-distroless-k8s-tests_istio
fbae30971db2523a3360840df4c98138e6365391
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.

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

Test name
Commit
Details
Rerun command

integ-cni-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-k8s-tests_istio

integ-ipv6-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-multicluster-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-telemetry-mc-k8s-tests_istio

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

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

integ-multicluster-k8s-tests_istio
fbae30971db2523a3360840df4c98138e6365391
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.

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

Test name
Commit
Details
Rerun command

integ-cni-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-k8s-tests_istio

integ-pilot-multicluster-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-telemetry-k8s-tests_istio

integ-helm-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
4152839df052db644dab975608026c9992cad13b
link
/test integ-telemetry-mc-k8s-tests_istio

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

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

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

integ-ipv6-k8s-tests_istio
fbae30971db2523a3360840df4c98138e6365391
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.

LGTM but put a hold to allow @mandarjog or @luksa to take a look if they are interested

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

Test name
Commit
Details
Rerun command

lint_istio
a576589c1a5fcb4382ecd4f10d77cb1b89721858
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.

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

Test name
Commit
Details
Rerun command

lint_istio
a576589c1a5fcb4382ecd4f10d77cb1b89721858
link
/test lint_istio

gencheck_istio
a576589c1a5fcb4382ecd4f10d77cb1b89721858
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.

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

Test name
Commit
Details
Rerun command

lint_istio
85088ff6a3ee755c8084a59c23f7de694815d859
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.


Remember Value Panel "Content viewer settings"

Is your feature request related to a problem? Please describe.
There are many JSON-text fields in my databases and I LOVE the auto-format feature in the Value Panel/Content Viewer Settings. However, I wish that the panel remembered which columns I marked as JSON or guessed that the content of the column is JSON text. When I close the table and reopen it, the formatting persists. But when I close DBeaver completely and reopen it, the formatting is gone and I have to reapply JSON formatting again.
Describe the solution you'd like
When I click one of the formats in the Content viewer settings dropdown, it should remain selected for that connection/table/column across a program restart.
Additional context

#10149


feat(content-block-mixed): introducing content-block-mixed

Description
Introducing web-components version
Changelog
New

Content Block Mixed storybook story and component;

Hey @guilhermelMoraes , looks like there are some lint errors, can you fix?

@jeffchew Most of these errors are happening in files that I didn't change. Should I fix them here?


Add a link to NuGet warning properties doc to the restore warnings and error page

@mishra14 commented on Thu Sep 28 2017
NuGet warnings and errors page: https://docs.microsoft.com/en-us/nuget/reference/errors-and-warnings
The page lists out all the restore warnings and errors correctly. But I do not see a link to warning properties except the compiler option page, which is not very helpful to the users.
Can we please have a similar page for NuGet warning properties which merges the following specs -
https://github.com/NuGet/Home/wiki/[Spec]-Transitive-Warning-Properties
https://github.com/NuGet/Home/wiki/Improved-NuGet-warnings

@mishra14 commented on Thu Sep 28 2017
Assign both PMs for better visibility :)

@nkolev92 commented on Thu Apr 16 2020
Issue moved to NuGet/docs.microsoft.com-nuget #1999 via ZenHub

duplicate of #1999


Programatically quieting logging to std*

Hi,
Once again, mockserver is great.
My ultimate goal for this issue is to programatically set mockserver to log only to log files, not to std*, because travis is complaining that test logs are too long (hard to argue with them...). I'm purposely not using any config files. I'm using Logback as the slf4j implementation.
 Here's what I've tried:
@BeforeClass
	public static void setUpClass() {
		//TODO TEST shut off logging. this doesn't work.
		((ch.qos.logback.classic.Logger) org.slf4j.LoggerFactory
				.getLogger(org.slf4j.Logger.ROOT_LOGGER_NAME))
				.setLevel(ch.qos.logback.classic.Level.OFF);
		((ch.qos.logback.classic.Logger) org.slf4j.LoggerFactory
				.getLogger("org.mockserver"))
				.setLevel(ch.qos.logback.classic.Level.OFF);
		mockClientAndServer = ClientAndServer.startClientAndServer(TestCommon.findFreePort());
	}

Logger binding resolution looks like this:
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/*snip*/jars/logback/logback-classic-1.1.2.jar!/org/slf
4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/*snip*/jars/mockserver/mockserver-netty-3.10.4-jar-wit
h-dependencies.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]

I would expect that to shut off everything, but nothing happens. Could you explain the proper invocation?
Thanks.

I think to fix your problem you need to slightly change your code as follows:
import org.junit.BeforeClass;
import org.junit.Test;
import org.mockserver.integration.ClientAndServer;
import org.mockserver.mock.action.ExpectationCallback;
import org.mockserver.model.HttpRequest;
import org.mockserver.model.HttpResponse;

import static org.mockserver.model.HttpRequest.request;
import static org.mockserver.model.HttpResponse.response;

/**
 * @author jamesdbloom
 */
public class LoggingTest {

    private static ClientAndServer mockClientAndServer;

    @BeforeClass
    public static void setUpClass() {
        //TODO TEST shut off logging. this doesn't work.
        ((ch.qos.logback.classic.Logger) org.slf4j.LoggerFactory
                .getLogger(org.slf4j.Logger.ROOT_LOGGER_NAME))
                .setLevel(ch.qos.logback.classic.Level.OFF);
        ((ch.qos.logback.classic.Logger) org.slf4j.LoggerFactory
                .getLogger("org.mockserver"))
                .setLevel(ch.qos.logback.classic.Level.OFF);
        // EXTRA TWO LINES NEEDED BELOW
        ((ch.qos.logback.classic.Logger) org.slf4j.LoggerFactory
                .getLogger("org.mockserver.mockserver"))
                .setLevel(ch.qos.logback.classic.Level.OFF);
        ((ch.qos.logback.classic.Logger) org.slf4j.LoggerFactory
                .getLogger("org.mockserver.proxy"))
                .setLevel(ch.qos.logback.classic.Level.OFF);
        mockClientAndServer = ClientAndServer.startClientAndServer(1080);
    }

    @Test
    public void doSomething() {
        mockClientAndServer.when(request()).callback(httpRequest -> response());
    }
}

This was because for some reason the logback configuration in MockServer for the jar-with-dependencies, the docker container, or the homebrew versions are as follows:
<logger name="org.mockserver" level="${mockserver.logLevel:-WARN}"/>
<logger name="org.mockserver.proxy" level="${mockserver.logLevel:-WARN}"/>
<logger name="org.mockserver.mockserver" level="${mockserver.logLevel:-WARN}"/>

I have updated the configuration to avoid the need for the extra two line, as follows:
<logger name="org.mockserver" level="${mockserver.logLevel:-WARN}"/>

This means in future once I release that change in the next week or so you can go back to your original implementation as follows:
import org.junit.BeforeClass;
import org.junit.Test;
import org.mockserver.integration.ClientAndServer;
import org.mockserver.mock.action.ExpectationCallback;
import org.mockserver.model.HttpRequest;
import org.mockserver.model.HttpResponse;

import static org.mockserver.model.HttpRequest.request;
import static org.mockserver.model.HttpResponse.response;

/**
 * @author jamesdbloom
 */
public class LoggingTest {

    private static ClientAndServer mockClientAndServer;

    @BeforeClass
    public static void setUpClass() {
        //TODO TEST shut off logging. this doesn't work.
        ((ch.qos.logback.classic.Logger) org.slf4j.LoggerFactory
                .getLogger(org.slf4j.Logger.ROOT_LOGGER_NAME))
                .setLevel(ch.qos.logback.classic.Level.OFF);
        ((ch.qos.logback.classic.Logger) org.slf4j.LoggerFactory
                .getLogger("org.mockserver"))
                .setLevel(ch.qos.logback.classic.Level.OFF);
        mockClientAndServer = ClientAndServer.startClientAndServer(1080);
    }

    @Test
    public void doSomething() {
        mockClientAndServer.when(request()).callback(httpRequest -> response());
    }
}

I think this issue should now be fixed / resolved so I am closing it.  Please re-open if you have further problems.

That does the trick, thanks very much.

Thanks. This worked for me .


⚠ Spryr has degraded performance

In adf86be, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 503
Response time: 3828 ms

Resolved: Spryr performance has improved in 87c4906 after 13 minutes.


[BEAM-8324] Restrict the upper bound for dill due to incompatibility between versions 0.3.0 and <IP_ADDRESS>.

R: @markflyhigh

This is cherry pick of https://github.com/apache/beam/pull/9695


Add "Label" field to CustomFormModelField

This will be populated with value from Model.KeysResult.clusters[i] for a given Model field.

Full discussion in email thread: "RE: Exposing KeysResult in FR .NET API"


CI: GitHub Action

PS:

The GitHub action using nightly-2023-04-11 in .github/actions/setup/action.yml, that is composite action, can change in the workflow .github/workflows/build.yml
Dockerfile using nightly version, it is not identical with nightly-2023-04-11
Demo docker image in https://hub.docker.com/repository/docker/bxb100/lockbud

TODO:

[ ] change Dockerfile using rust-toolchain.toml
[ ] add qemu to cross-compile docker image
[ ] add usage workflow

@bxb100 Thanks a lot! I will look into it.


aria-label to 2 form controls

aria-label="select a color"

Would love to get this in once the index.jade is edited

ARIA has poor browser support (no browser fully supports it). What about using a <label> and accessibly (visually) hiding it if needed?

I think aria-label has good support across screen readers but +1 to not using aria if you can avoid it and sticking with the invisible label approach. Here's a good article on how to do it: http://webaim.org/techniques/css/invisiblecontent/ You've got to be careful because completely removing the label (like setting it to display: none or width: 0 height: 0) will cause screen readers to ignore it. That article recommends doing something like:
.hidden
{position:absolute;
left:-10000px;
top:auto;
width:1px;
height:1px;}

The article I linked to recommends also setting overflow: hidden but I'd advise against that as recently it was reported to me that this was causing screen readers to ignore the element.

I do something similar and also set position:relative on the parent. Otherwise VoiceOver (SwitchControl) on iOS will draw really weird focus outlines that go way off the screen.
.visually-hidden { /*https://developer.yahoo.com/blogs/ydn/clip-hidden-content-better-accessibility-53456.html*/
    position: absolute !important;
    clip: rect(1px 1px 1px 1px); /* IE6, IE7 */
    clip: rect(1px, 1px, 1px, 1px);
    padding:0 !important;
    border:0 !important;
    height: 1px !important;
    width: 1px !important;
    overflow: hidden;
}
body:hover .visually-hidden a, body:hover .visually-hidden input, body:hover .visually-hidden button { display: none !important; }

http://a11yproject.com/posts/how-to-hide-content/

Closing due to inactivity, will be addressed


[WIP] Creating torrents

This adds support for creating torrents.

[x] Basic dialog with torrent generation
[ ] Option to add torrent to session
[ ] Input validation
[ ] Documentation

This looks nice!

Translated new text to French.

Feature tested. It works flawlessly


overload operator __unm and __sub to support module chaining

By overloading __unm__ and __sub__ of nn.Module and __sub__ of nngraph.Node, graph construction is easier and human readable.
For example,
h1 = nn.Linear(20, 10)()
h2 = nn.Linear(10, 1)(nn.Tanh()(nn.Linear(10, 10)(nn.Tanh()(h1))))
mlp = nn.gModule({h1}, {h2})

can be written as
h1 = - nn.Linear(20,10)
h2 = h1
     - nn.Tanh()
     - nn.Linear(10,10)
     - nn.Tanh()
     - nn.Linear(10, 1)
mlp = nn.gModule({h1}, {h2})

In the original syntax, as the graph getting bigger and more complicated, the increasing amount of nested parentheses may be confusing too. In this case, module chaining is clearer and easier to debug since we can see the data flow at a glance.
For example
input = nn.Identity()()
L1 = nn.Tanh()(nn.Linear(10, 20)(input))
L2 = nn.Tanh()(nn.Linear(30, 60)(nn.JoinTable(1)({input, L1})))
L3 = nn.Tanh()(nn.Linear(80, 160)(nn.JoinTable(1)({L1, L2})))
g = nn.gModule({input},{L3})

can be written as
input = - nn.Identity()
L1 =  input
     - nn.Linear(10, 20)
     - nn.Tanh()
L2 =  { input, L1 }
     -  nn.JoinTable(1)
     -  nn.Linear(30,60)
     -  nn.Tanh()
L3 = { L1,L2 }
     - nn.JoinTable(1)
     - nn.Linear(80,160)
     - nn.Tanh()
g = nn.gModule({input},{L3})

i like it, but can you also add the examples in the main README?

Thank you!


[tlul,lint] Tell Verilator to split a process to avoid an UNOPTFLAT

This fixes the "non-vendored half" of #21716.

Thanks for the review, @andreaskurth.  I've updated it to be (I think) more precise now. Does this make a bit more sense?


Queueing a Series of State Updates

Page: https://id.react.dev/learn/queueing-a-series-of-state-updates
Assignee: @milhamm

Sorry, I didn't noticed it was taken

@milhamm It was taken but not confirmed with a Draft PR by @mrevanzak yet. I think you can still take it.

Ah sure thing, thanks

sorry i forgot. so i cant contribute on this anymore?

I'm open to hand it over to you if you want @mrevanzak
What do you think? @mhaidarhanif

@mrevanzak @milhamm Depends on you two.
Some options:

If @milhamm want to give it back over to @mrevanzak , then @mrevanzak can take it back
If want to compare, you can both open a PR, then we'll compare it later which one to use based on the progress speed and result quality.

I'm willing to take the first option. @mrevanzak you can start to create a draft PR. I will close mine in the mean time
Thanks for the suggestion @mhaidarhanif

thanks sir @milhamm

No worries, sorry for accidentally taking your part


ALVR only lists audio inputs as sources to stream

ALVR doesn't give me the option to select any of my audio outputs and only finds inputs.

Can you please give more information about your setup?

Im running manjaro with a 1080 and amd r5 5600x

I'm experiencing the same on Arch Linux with ALVR 19.0.0_dev00+nightly.2022.08.16-1.
Instead of sending the default output device audio (PC speakers in my case) to my Quest 2 speakers, it sends the default input device audio (microphone in my case). Basically, the HMD speakers just play whatever the microphone hears instead of the desktop audio.

Id sugest installing pavucontrol and via its gui heading to the recording tab and manualy selecing the one you want for alvr.
It will remember this even if you shut down alvr, just gotta do it each reboot


can you put this on npm?

never published to npm, and quite busy nowadays
if someone know how to do it fast - you're welcome to join - i'll give all permissions to project if any needed

The process is simple and have free time today and tomorrow. If you grant me access to the repo so I can clone your push up to npm

Thanks so much, if you get a chance following these instructions in the command or create an accounton npm. I want to make sure you get credit for the library and add you as a collaborator on npm.
I will also update the readme to have npm instructions. Thanks again!
npm set init.author.name "Your Name"
npm set init.author.email<EMAIL_ADDRESS>npm set init.author.url "http://yourblog.com"

npm adduser

thanx forinstructions, done
Username: garmoshka-mo


.ovpn12 files

Added new step to create an .ovpn12 file that can be stored on iOS keychain
This step is more secure method and does not require the end-user to keep entering passwords, or storing the client private cert where it can be easily tampered based on documentation located:
https://openvpn.net/faq/how-do-i-use-a-client-certificate-and-private-key-from-the-ios-keychain/
Someone can improve upon this by adding a parameter (possibly -i|--iOS) and then generating the original .ovpn file to not contain the client private certificate.

Will let other most active users comment on this as I am not at all familiar with IOS devices.
If their feedback is positive then ill gladly merge it.
@orazioedoardo @devZer0 @Giraffe1966  any takes on this?

Yeah, I see that this is more secure because the private parts of the config are not in the .ovpn file, though it's a bit less convenient since the user need to copy two files, both the .ovpn and the .ovpn12 and instruct the user on how to use them. Also your script doesn't do the whole job:

the .ovpn12 file is root owned in the ovpn folder so you should chown and chmod it to allow the user to read it.
you need to strip cert and key sections (or just don't add them) in the .ovpn otherwise you defeat initial purpose.
probably you should use expect to type the export password and the private key password non-interactively.

By the way I wouldn't make this the default, I would add a one time dialog after the first client creation with some text like "TIP: If you have an iOS device you can pass -i|--iOS to [...]"

No need to use expect for the password, you can use the -passin env:PASSWD and -passout env:PASSWD options to openssl to do this non-interactively. Also, don't use sudo for openssl as this is run as root and this would break on systems without sudo installed.

Thanks for the feedback.  I will be sure to incorporate it.

you need to strip cert and key sections (or just don't add them) in the .ovpn otherwise you defeat initial purpose.

By the way I wouldn't make this the default, I would add a one time dialog after the first client creation with some text like "TIP: If you have an iOS device you can pass -i|--iOS to [...]"

I am a bit new at this, so trying to figure out how to use the -i|--iOS filter correctly to create this and strip out the cert and key sections.  I will do some testing and upload something that works!

Updated.

@orazioedoardo , @Giraffe1966  what is your take on this? is it good to be merged?
thanks a lot for keeping the boat moving! =)

@IcedComputer please apply the changes and suggestions mentioned by @Giraffe1966 and ill merge your PR

Thanks @IcedComputer , Merging.


Draggable Product Images Enhancement Completed #4772

Issue Reference
Link: https://github.com/bagisto/bagisto/issues/4772

Marking this as a draft some little work is needed on this.


Train dataset?

Thank you very much for this wonderful repo.
I am doing research works on OMR, and tried the command:
python3 main.py <input directory path> <output directory path>
it works fine. But when I executed this:
python3 train.py
got error with:
ValueError: With n_samples=0, test_size=0.2 and train_size=None, the resulting train set will be empty. Adjust any of the aforementioned parameters.
So I found the dataset directory missed in the project:
dataset_path = 'train_data/data'
Can you commit it again?
Thanks!

The dataset is uploaded to Google Drive because its size is large. So, please, download it and place it in the mentioned directory.


backend error referencing inner function

For:
shared void run() {
    void bar(Integer a = 98, Integer* bs) {
    }
    value barRef = bar;
}

you get:
$ ceylon compile simple
source/simple/run.ceylon:4: warning: declaration is never used: value 'barRef' has no local references
    value barRef = bar;
          ^
source/simple/run.ceylon:4: error: Ceylon backend error: cannot find symbol
    value barRef = bar;
                   ^
  symbol: method bar$a()
Note: Created module simple/1.0.0
ceylon compile: There was 1 error

FTR, this only happens with both a defaulted parameter and a variadic parameter, and only for an inner function.


Added ability to install latest version

Hi Jeff!
I've processed your feedback on #3 and while I was at it, I also updated all other module names to their FQCN equivalents.
Met vriendelijke groet,
Jeff ;-)

And ofcourse @tuxpeople, thanks for your work!

I would rather leave it using the normal module names (and not the FQCN) at this time, as I'm still maintaining my roles without FQCNs (I'll make that transition across the board someday, but not yet).

Fair enough, makes sense, it still works without FQCNs :)

Hmm, looks like this would also require the addition of jmespath (e.g. pip3 install jmespath)?

Ah yes, there's a lot of modules that require that, it actually surprises me that it isn't already a dependency to Ansible itself :)
Would adding a task to the molecule playbooks to install it be sufficient?


Revert "DUPLO-14966: POC of TF acceptance tests with mock data"

Reverts duplocloud/terraform-provider-duplocloud#399

Task linked: DUPLO-14966 POC: TF acceptance testing


config migrate tools read the docker image tag from the paictl version

Now the config migrate tool would read the image tag from the paictl version.
No need to update the script for each release.

Coverage remained the same at 53.314% when pulling 4d56e7d9274788a4a91d0f2a0d36b4fe4ce65ea0 on hao/fix_config_tool into 04124223d11c3f15228b32590c30db0638ab4804 on master.

Coverage remained the same at 53.314% when pulling 4d56e7d9274788a4a91d0f2a0d36b4fe4ce65ea0 on hao/fix_config_tool into 04124223d11c3f15228b32590c30db0638ab4804 on master.


re2: set branch to main

RE2 renamed the master branch in main.
This is only relevant for Dunfell since RE2 is part of meta-oe since Kirkstone.

Thanks


x86 extraction fails with struct.error: required argument is not an integer

Full log: https://gist.github.com/torarnv/8b9515847459ea7247bb35b0198b761a
Ends with:
ObjC Fixer >> Processing Selector References :: [\]                                                                                Traceback (most recent call last):
  File "/opt/homebrew/bin/dyldex", line 277, in <module>
    main()
  File "/opt/homebrew/bin/dyldex", line 272, in main
    _extractImage(args.dyld_path, dyldCtx, imageMap[targetPaths[0]], outputPath)
  File "/opt/homebrew/bin/dyldex", line 138, in _extractImage
    objc_fixer.fixObjC(extractionCtx)
  File "/opt/homebrew/lib/python3.11/site-packages/DyldExtractor/converter/objc_fixer.py", line 1519, in fixObjC
    _ObjCFixer(extractionCtx).run()
  File "/opt/homebrew/lib/python3.11/site-packages/DyldExtractor/converter/objc_fixer.py", line 447, in run
    self._processSections()
  File "/opt/homebrew/lib/python3.11/site-packages/DyldExtractor/converter/objc_fixer.py", line 678, in _processSections
    struct.pack("<Q", newPtr)
struct.error: required argument is not an integer

macOS 13.6 /System/Volumes/Preboot/Cryptexes/OS/System/Library/dyld/dyld_shared_cache_x86_64 on M2 MPB

Sorry, x86_64 extraction is not supported.

Ah, I see. Perhaps this should be mentioned in the README, or detected at runtime and error out early with a clear message rather than the failures?


Automated cherry pick of #3691: Reduce permission of antrea-agent service account

Cherry pick of #3691 on release-1.5.
#3691: Reduce permission of antrea-agent service account
For details on the cherry pick process, see the cherry pick requests page.

Codecov Report

Merging #3749 (6e83158) into release-1.5 (e4bb9a2) will decrease coverage by 8.69%.
The diff coverage is 82.35%.

@@               Coverage Diff               @@
##           release-1.5    #3749      +/-   ##
===============================================
- Coverage        50.15%   41.46%   -8.70%
===============================================
  Files              304      200     -104
  Lines            25854    24156    -1698
===============================================
- Hits             12967    10016    -2951
- Misses           11211    13109    +1898
+ Partials          1676     1031     -645

Flag
Coverage Δ

kind-e2e-tests
?

unit-tests
41.46% <82.35%> (?)

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

Impacted Files
Coverage Δ

pkg/antctl/antctl.go
66.66% <ø> (ø)

...g/agent/controller/serviceexternalip/controller.go
33.17% <82.35%> (-46.26%)
:arrow_down:

pkg/ovs/openflow/default.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/util/runtime/runtime.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/agent/nodeportlocal/k8s/annotations.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/ovs/openflow/logs.go
9.52% <0.00%> (-90.48%)
:arrow_down:

pkg/apis/controlplane/register.go
0.00% <0.00%> (-90.00%)
:arrow_down:

pkg/agent/controller/networkpolicy/reject.go
0.00% <0.00%> (-81.35%)
:arrow_down:

pkg/agent/client.go
0.00% <0.00%> (-77.42%)
:arrow_down:

pkg/ovs/ovsconfig/ovs_client_linux.go
0.00% <0.00%> (-76.93%)
:arrow_down:

... and 314 more

/test-all

/skip-networkpolicy
/skip-conformance
manually verified above tests.


Refactor: File-scoped namespaces, remove unused usings, and implement primary constructors

This pull request focuses on improving code quality and maintainability by:

Converting all namespaces to file-scoped, reducing clutter and enhancing readability.
Removing unused using directives to clean up the code and eliminate unnecessary dependencies.
Applying primary constructors for more concise and efficient object initialization.
Correcting minor typos found across the codebase.

These changes streamline the project structure without introducing any breaking changes or altering functionality, making the codebase easier to navigate and maintain.

Hello @joseharriaga ,
I recently submitted this pull request that contains a large number of changes (around 830 files) to convert namespaces to file-scoped namespaces. I believe these changes are valuable and help improve the structure of the code.
Given that the project is under continuous development, there is a high risk of conflicts if this PR is not reviewed soon. Since these changes do not affect the core logic, I would appreciate it if you could review the PR at your earliest convenience.
If there are any issues or concerns with the changes, I’m happy to address them promptly.


CMS Page Wizard assumes that TextPlugin exists

When filling in the "Contents" field in the CMS Page wizard, a TextPlugin is automatically created, but it may not be installed. I think we should find a more general solution

Assigning a blocker tag because I think it might break things for no obvious reasons. We can enable the field only if TextPlugin is available in plugin_pool or let user provide a custom text plugin


Aux1 Source Select?

Is it possible to send an Aux1 source select command to an ATEM switcher? I didn't see an obvious choice.

ATEMs can also be used like Videohubs, if you ever need another way!


{Compute} Update vm test with new versioned image aliases

Related command

az vm create / az vmss create
all comments that related to --image
Description

Update new versioned image aliases to Solve https://github.com/Azure/azure-cli/issues/25736
Modify testing scripts related to PR https://github.com/Azure/azure-cli/pull/25930
Testing Guide

History Notes

[vm] [Update] Update test scripts after image aliases were updated

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Compute

Closed and transferred to: https://github.com/Azure/azure-cli/pull/26039


Codecov uploader OOMs while searching for file network on large repositories

Describe the bug
Running the uploader on large repositories causes it to OOM while discovering the file network.
[2022-04-11T12:39:42.234Z] ['info']
     _____          _
    / ____|        | |
   | |     ___   __| | ___  ___ _____   __
   | |    / _ \ / _` |/ _ \/ __/ _ \ \ / /
   | |___| (_) | (_| |  __/ (_| (_) \ V /
    \_____\___/ \__,_|\___|\___\___/ \_/

  Codecov report uploader 0.1.20
[2022-04-11T12:39:42.240Z] ['info'] => Project root located at: /ephemeral/home/ubuntu/worker_workspace
[2022-04-11T12:39:42.242Z] ['info'] ->  Token found by environment variables
[2022-04-11T12:39:42.242Z] ['info'] ->  Token set by environment variables

<--- Last few GCs --->

[22463:0x7fe065602300]   168398 ms: Mark-sweep 4052.5 (4135.6) -> 4042.5 (4141.9) MB, 2926.0 / 0.0 ms  (average mu = 0.584, current mu = 0.255) allocation failure scavenge might not succeed
[22463:0x7fe065602300]   172823 ms: Mark-sweep 4060.3 (4143.6) -> 4049.4 (4148.6) MB, 4104.4 / 0.0 ms  (average mu = 0.367, current mu = 0.072) allocation failure scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory

I'm forced to used -X network to unblock.
To Reproduce

On a very large repository (I couldn't find any public one)
Run the uploader binary without any args or environment (I'm on Ubuntu 18):
./codecov

Expected behavior
Uploader should not OOM
Screenshots
n/a
Additional context
I did some digging and the problem seems to be exactly here: https://github.com/codecov/uploader/blob/2ad72d4c48aed30338c00e848d856c481beee7ba/src/helpers/files.ts#L238-L263
child_process.spawnSync has a maxBuffer of about 1MB (docs) so the call to git ls-files returns an error because the stdout is too large. The fallback to glob.sync consumes an enormous amount of memory, ultimately causing an OOM. Not sure why glob.sync uses so much memory.

Ok, I did a bit more digging and it seems what's destroying glob are bazel-* directories. They should certainly be ignored, but the ignore list is currently hardcoded.

Every time I think we have a way to add to the ignore list from the command line... 🤦♀

I took at stab at a partial fix here https://github.com/codecov/uploader/pull/729


Improve the text at the top of the home page

Received the latest home page text from the product team

I am sorry. There was a mistake. I send it to Microsoft repository wrongly.


Issues in find_best_move with numpy arrays

Hi!
I started using find_best_move in 2048.py as discussed in issue#52. There are some possible bugs (or perhaps functionalities I am not aware of) when using numpy 2d arrays with that function. I have tried to mention everything I tried to do about it and the fix which seems to work.
Prep:
import numpy as np
import random
import copy
import importlib.util
spec = importlib.util.spec_from_file_location("2048", "filepath\\2048.py")
aimain = importlib.util.module_from_spec(spec)
spec.loader.exec_module(aimain)

When this board-state crops up in the binary version running by itself.

MULTITHREAD is True

In this case, when the same board state is run through the find_best_move function and when it crops up in the normal execution of 2048.exe (or equivalent binary), we get different scores for the different moves, but the printed board seems the same. The one in the binary seems to be the correct version.

MULTITHREAD is False

In this case, the scores from the function are still inaccurate but now we do get a different board printed. The scores obtained seem to be correct for the board printed and hence I assume there might be some error in parsing a numpy 2d-list.

tolist()

Using the numpy method tolist() seems to have fixed the issue as far as I tested on some hand-coded examples with MULTITHREAD False.
I am not sure this arises because of some version mismatch. I am using 32-bit python 3.6 on Windows 10 with most libraries upgraded to the latest version. Used Visual Studio latest version for compiling the binary.

Thanks for the response!
I originally used a 32-bit VS command prompt to compile. Will recompile as a 64-bit version.
For the importlib part, I was trying to run this from a different directory initially and then did not change the import statements later on.

To run from a different directory, you can append to sys.path and then do
import.
On Mon, Jun 4, 2018 at 11:52 AM Stochastic13<EMAIL_ADDRESS>wrote:

Thanks for the response!
I originally used a 32-bit VS command prompt to compile. Will recompile as
a 64-bit version.
For the importlib part, I was trying to run this from a different
directory initially and then did not change the import statements later on.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/nneonneo/2048-ai/issues/53#issuecomment-394405150,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEmuSld8vKQfzlWm1l-erxLWjbKmMLVks5t5VevgaJpZM4UY07Z
.


Localization

I am looking for an example on localization. How can we manage different language text and audio files?
Thanks

Hello,
The Languages module and plugin provide localization by substrings of URLs automatically during the load process. For instance:
window.app.load('assets/sound/%LANG%/vo/help1.mp3');

will load "assets/sound/en/vo/help1.mp3", or "assets/sound/es/vo/help1.mp3" depending on the value of navigator.languages or what is set manually by calling app.languages.setLanguage('es')
Hope that helps!


Visually mismatching parent hex

I encountered a situation where the h3ToParent function returns a hexagon that does not visually seem to be the parent of the original hexagon.
import { h3ToGeoBoundary, h3ToParent } from "h3-js";

const hexAtRes12 = "8c393362a49d5ff";
const parentHexAtRes6 = h3ToParent("8c393362a49d5ff", 6); // "86393362fffffff"

const polygonRes12 = h3ToGeoBoundary(hexAtRes12, true);
const polygonRes6 = h3ToGeoBoundary(parentHexAtRes6, true);

When rendering these polygons with mapbox gl we get:

I expected the neighbor hex to the bottom left of the yellow hex to be the parent hex of the green hex at resolution 12.
There are also examples the other way around. The res 12 hex "8c39336212687ff" is visually a child of the above res 6 hex "86393362fffffff" but in reality, the h3ToParent function returns "863933627ffffff" as parent at res 6.
Is this behaviour to be expected? If so, how can it be explained?

This behavior is expected. Hexagons cannot perfectly contain their children, so at each remove from a given ancestor there will be a fixed percentage of the area of the descendants that is not within the bounds of the ancestor. I made a notebook to explain this with an interactive example: https://observablehq.com/@nrabinowitz/h3-hierarchical-non-containment

Oh, absolutely expected.
You can see the source of the situation here:

Each child layer approximately fits 7 child hexagons within it, rotating back and forth by approx 17 degrees, as I recall?
This is because you cannot subdivide a hexagon into hexagons like you can squares and triangles, and this is just one approximation of doing so.
This produces a fractal-looking result if you plot the outline of all of the children of a particular hexagon at greater and greater deltas between the parent and the (great-great---)-grandchildren.
For your example, it would look like this:


why  I can't  download the datasets?

Because the datasets are not provided.

so you mean that nobody can renew you experiments?How can I run your code?

Anyone can replicate the experiments as long as they have access to the BODMAS dataset. Ask the authors of the dataset for the data.
If you don't have access to the BODMAS dataset, you can still run the code with your own data.

if I download the datasets from others,how to change the code to run it?thanks

This information is described in the README. Take a look at the scripts provided in src/scripts/training/MalConv/. You need to change the filepaths that point out to the goodware and malware directories.

I find someone upload csv documents like these,these are all the BODMAS dataset samples?

These are the hashes of the executables from the BODMAS dataset, timestamp, and malware family (if malicious)

Could you please send mo the datasets?I can't find it anywhere and Idon't have my own datasets,thank you ,my email is<EMAIL_ADDRESS>

No, I can't. Check the following links:
https://whyisyoung.github.io/BODMAS/
https://github.com/iosifache/DikeDataset
https://practicalsecurityanalytics.com/pe-malware-machine-learning-dataset/
I close this issue as finding appropiate datasets is not related to my code.

In the file named test_end2end_detector.py,you set up the parameters  models/vanilla/MalConv/MalConv_maxlen_1000000_paddingvalue_256/test_set_gpu.out as goodware_subset_filepath,but I can't find it following the road


Fix incompatible function pointer type

libxml2 added const to xmlHashScanner in v2.9.8. Wrap the call in a version check and cast for the non-const case.

@shahmishal the other option is to update libxml2 on whatever CI jobs are currently failing with this. Not sure if that's an option, so have put this up just in case.

@swift-ci please test

@compnerd and @etcwilde if you have time 🙏

I think that we should go ahead and merge this for now.  If we update the CI builders, we can remove this, it will be a bit of technical debt that we are carrying around, but it won't break anything.


Update README.md - Fixed typo

Summary
Fixed typo in README

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


[Chatbot UI design]

Description
Allow users to choose from different color schemes or themes. For example, offer light mode, dark mode, or other visually appealing options
Instead of a plain close button, explore creative designs like " X " button
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

How do you want to enhance the chatbot as it is made using the interface Botpress @sheetal-81


Pin sphinx-autodoc-typehints version to avoid KeyError: 'argname'

Building the docs fails ever since the version of sphinx-autodoc-typehints increased from v1.12.0 to v1.13.0.
This PR temporarily pins this dependency's version to v1.12.0.
See https://github.com/theislab/scanpy/pull/1828#issuecomment-1005072811 and cc @Zethson

CC @flying-sheep since you are contributing to sphinx-autodoc-typehints. Something that we can fix upstream?

It’s all fixed upstream!

Superseded by #2102

thanks!


feat(TDI-41721) : support athenadb in jdbc component

What is the current behavior? (You can also link to an open issue here)
https://jira.talendforge.org/browse/TDI-41721
What is the new behavior?
Please check if the PR fulfills these requirements

[ ] The commit message follows Talend standard
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: success :star:
Sonar results

Pull request test result: failure :x:


doesnt work on RTX 2060

E5 2678v3 32GB RAM, RTX 2060
app runs, make calibration, when i click to image below - app crash witn no error.

If you run the .exe from a terminal (powershell or cmd) does it tell you anything?
Did you add your own photos to the app? If yes, try removing them and only use the default avatars

no, i did not add custom images. Terminal also shows nothing. AFter execute exe - and after rporgam window apperance - it release console terminal.

Sorry I don't know much about debugging things on Windows

Anyone ever get this to work with the RTX cards?  Mine does exactly what everyone described here.

It seems that all RTX graphics cards are not supported. RTX2060 cannot be used, and all RTX30XX graphics cards cannot be used.

Other people have successfully run it on RTX2060 after following the default installation instructions (i.e. not using any workarounds or patches). But I suppose it's possible that some dependency has changed.


fix: change conflicting method name

before_request was referencing the definition introduced in this commit
Closes #191

So I've made a change to something that will work in production but is not working with the spec.
I think I have to make an additional change to placeos-driver to have it function correctly in specs

OK I think this is good to merge now @tassja
was a little more complex than it should have been


vimPlugins.sql-nvim: Set a default libsqlite3.so

Motivation for this change
The plugin relies on sqlite to work
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

ping @teto

that fixes it for me. If you use this plugin for telescope/frecency, it would be nice to add sal-nvim as one of its buildinputs in vim-plugins/overrides.nix. Something I can also fix myself later.

do you mean dependecies instead of buildInputs?

that fixes it for me. If you use this plugin for telescope/frecency, it would be nice to add sal-nvim as one of its buildinputs in vim-plugins/overrides.nix. Something I can also fix myself later.

do you mean dependecies instead of buildInputs?

sry I was like "you should precisie it's not buildInputs" and I wrote buildInputs xD yes dependencies

@teto no worries, just wanted to be sure, I added the dependendy

works for me thnks


Cancelled queries should not in the "Replication statistics" tab

Leaving it here means it's specific to replication but, as far as I know, it's all the cancelled queries, with or without replication. It could stand on its own.

Commit a75e621 move this menu entry to upper level.