fix based on comment

In estimator function, I retrieve the result externally rather than passing an index. However, I'm concerned this might lead to increased memory usage. Is this an issue?

@ddkang Could you please review the modification

I don't actually understand what this PR does. Can you link to the comment and describe the change in more detail?


Fix typo in Sopot station

There are 5 visible commits, but after merging my previous PR there should be only last one.


Iconify cookies

Hello,
I was wondering whether there is a way to allow users to tell whether they want to allow iconify cookies or not.
After all, for GDPR they should be able to control this behaviour!

What cookies are you talking about?

I'm talking about these ones: https://www.iconify.eu/pages/cookies-privacy.php#:~:text=Iconify uses cookies to recognize,provide information concerning personal identification.

Is this website connected to the Iconify service? You can actually visit the official Iconify website using this link: https://iconify.design/
Regardless, I'd also like to provide users with the option to decline these cookies.

What cookies are you talking about?

To clarify, they are not actually cookies but this information is stored in the Local Storage (this is perhaps why you cannot see it on nuxt website

I think Iconify has nothing to do with cookies. Talking about localStorage, since v1.0 it should no longer uses that approach.

I´m using nuxt UI 2.20.0which references nuxt/icon 1.10.1. It is set in my localstorage. Also on fresh-install, also after clear everything.
In code i did not find andything regarding that, so it must be set via what?

Do you mean these? This is up to Iconify - you could open an issue to Iconify to see if they could have an option to disable it
Either way, it's not related to this issue. Please open a new issue with context.

Oh, i thought the topic was about

I was wondering whether there is a way to allow users to tell whether they want to allow iconify cookies or not.

Will open a Issue on iconify, come back with a new Issue here when its implemented to set this option.
Thanks!

Oh, i thought the topic was about

I was wondering whether there is a way to allow users to tell whether they want to allow iconify cookies or not.

Will open a Issue on iconify, come back with a new Issue here when its implemented to set this option.
Thanks!

It was exactly the point of the issue indeed, I guess I was not clear enough.
Anyway, if it has to be handled by iconify, it's right move the discussion there.
Although, this topic is an issue for this package itself as well: these laws prescribe the downstream dependencies to also be responsible for the actions of the upstream ones they choose.

Those are not cookies, but storage used for caching icon data loaded from API.
You can disable it by disabling cache disableCache('all'): https://iconify.design/docs/icon-components/vue/disable-cache.html

Removed localStorage caching from new version of component.
This functionality has outlived its purpose. It was added long time ago when API was slower and less reliable, but today it is not needed because:

API is now fast with multiple servers all over the world (users are connected to closest server)
There is redundancy built in with 2 backup API servers in case main API fails (actually same servers, just split in 2 sub-networks, so if main server fails, one of backup domains will point to a working server)

Published @iconify/vue version 4.3.0-dev.1 without storage, can be installed as @iconify/vue@next. I'll be testing it more in various projects to make sure there are no issues, expecting to release a stable version right after new year.


nested flat-routes not entirely BC behavior or documentation unclear?

I had:

foo.bar/route.tsx
foo.bar.$stuff.some/route.tsx
foo.bar.$stuff.more/route.tsx

Changing to

foo.bar/route.tsx
foo.bar.$stuff+/some/route.tsx
foo.bar.$stuff+/more/route.tsx

The route foo.bar/route.tsx was previously considered layout, now becomes separate route. The nested folder flat-route looked to me like something that does not force me to make to many nested levels, because as per logic documented the first and the second should be equivalent.

I could solve the issue, it was some confusion regarding the semantics in the documentation.


Migrate code to use IstioOperator API in istio/api

See the corresponding API change:
https://github.com/istio/api/pull/1223

@ostromart: 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.

@ostromart: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

mandiff_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test mandiff_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test mandiff_operator

lint_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test lint_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test mandiff_operator

lint_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test lint_operator

test_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test test_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test mandiff_operator

lint_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test lint_operator

test_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test test_operator

mesh_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test mesh_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test mandiff_operator

lint_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test lint_operator

test_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test test_operator

mesh_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test mesh_operator

gencheck_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test gencheck_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test mandiff_operator

lint_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test lint_operator

test_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test test_operator

mesh_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test mesh_operator

gencheck_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test gencheck_operator

e2e_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test e2e_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test mandiff_operator

test_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test test_operator

mesh_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test mesh_operator

gencheck_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test gencheck_operator

e2e_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test e2e_operator

lint_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test lint_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test mandiff_operator

test_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test test_operator

mesh_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test mesh_operator

e2e_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test e2e_operator

lint_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test lint_operator

gencheck_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test gencheck_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test mandiff_operator

test_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test test_operator

e2e_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test e2e_operator

lint_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test lint_operator

gencheck_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test gencheck_operator

mesh_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test mesh_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test mandiff_operator

test_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test test_operator

lint_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test lint_operator

gencheck_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test gencheck_operator

mesh_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test mesh_operator

e2e_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test e2e_operator

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.

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

Test name
Commit
Details
Rerun command

test_operator
fc632a5370a1695cd08e929cea024fe548332391
link
/test test_operator

lint_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test lint_operator

gencheck_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test gencheck_operator

mesh_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test mesh_operator

e2e_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test e2e_operator

mandiff_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test mandiff_operator

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.

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

Test name
Commit
Details
Rerun command

lint_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test lint_operator

gencheck_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test gencheck_operator

mesh_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test mesh_operator

e2e_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test e2e_operator

mandiff_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test mandiff_operator

test_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test test_operator

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.

@ostromart: 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.

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

Test name
Commit
Details
Rerun command

lint_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test lint_operator

gencheck_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test gencheck_operator

e2e_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test e2e_operator

mandiff_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test mandiff_operator

test_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test test_operator

mesh_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test mesh_operator

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.

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

Test name
Commit
Details
Rerun command

gencheck_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test gencheck_operator

e2e_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test e2e_operator

mandiff_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test mandiff_operator

test_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test test_operator

mesh_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test mesh_operator

lint_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test lint_operator

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.

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

Test name
Commit
Details
Rerun command

gencheck_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test gencheck_operator

e2e_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test e2e_operator

test_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test test_operator

mesh_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test mesh_operator

lint_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test lint_operator

mandiff_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test mandiff_operator

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.

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

Test name
Commit
Details
Rerun command

gencheck_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test gencheck_operator

e2e_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test e2e_operator

mesh_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test mesh_operator

lint_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test lint_operator

mandiff_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test mandiff_operator

test_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test test_operator

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.

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

Test name
Commit
Details
Rerun command

e2e_operator
280250653077c01b5ce48a7f39edbef1792079a5
link
/test e2e_operator

mesh_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test mesh_operator

lint_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test lint_operator

mandiff_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test mandiff_operator

test_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test test_operator

gencheck_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test gencheck_operator

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.

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

Test name
Commit
Details
Rerun command

mesh_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test mesh_operator

lint_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test lint_operator

mandiff_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test mandiff_operator

test_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test test_operator

gencheck_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test gencheck_operator

e2e_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test e2e_operator

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.

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

Test name
Commit
Details
Rerun command

mesh_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test mesh_operator

lint_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test lint_operator

test_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test test_operator

gencheck_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test gencheck_operator

e2e_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test e2e_operator

mandiff_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test mandiff_operator

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.

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

Test name
Commit
Details
Rerun command

lint_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test lint_operator

test_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test test_operator

gencheck_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test gencheck_operator

e2e_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test e2e_operator

mandiff_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test mandiff_operator

mesh_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test mesh_operator

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.

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

Test name
Commit
Details
Rerun command

lint_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test lint_operator

test_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test test_operator

e2e_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test e2e_operator

mandiff_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test mandiff_operator

mesh_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test mesh_operator

gencheck_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test gencheck_operator

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.

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

Test name
Commit
Details
Rerun command

test_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test test_operator

e2e_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test e2e_operator

mandiff_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test mandiff_operator

mesh_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test mesh_operator

gencheck_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test gencheck_operator

lint_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test lint_operator

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.

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

Test name
Commit
Details
Rerun command

e2e_operator
4a43b4aeb1e7398e441c6bc6e4c6eae50d8e28c0
link
/test e2e_operator

mandiff_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test mandiff_operator

mesh_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test mesh_operator

gencheck_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test gencheck_operator

lint_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test lint_operator

test_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test test_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test mandiff_operator

mesh_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test mesh_operator

gencheck_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test gencheck_operator

lint_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test lint_operator

test_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test test_operator

e2e_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test e2e_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test mandiff_operator

mesh_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test mesh_operator

gencheck_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test gencheck_operator

test_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test test_operator

e2e_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test e2e_operator

lint_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test lint_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test mandiff_operator

gencheck_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test gencheck_operator

test_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test test_operator

e2e_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test e2e_operator

lint_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test lint_operator

mesh_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test mesh_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test mandiff_operator

test_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test test_operator

e2e_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test e2e_operator

lint_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test lint_operator

mesh_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test mesh_operator

gencheck_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test gencheck_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test mandiff_operator

e2e_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test e2e_operator

lint_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test lint_operator

mesh_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test mesh_operator

gencheck_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test gencheck_operator

test_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test test_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
e7b6892f3661982ae4eb3c43b1057eeb4eb67587
link
/test mandiff_operator

lint_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test lint_operator

mesh_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test mesh_operator

gencheck_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test gencheck_operator

test_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test test_operator

e2e_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test e2e_operator

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.

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

Test name
Commit
Details
Rerun command

lint_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test lint_operator

mesh_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test mesh_operator

gencheck_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test gencheck_operator

test_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test test_operator

e2e_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test e2e_operator

mandiff_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test mandiff_operator

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.

@ostromart: 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.

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

Test name
Commit
Details
Rerun command

mesh_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test mesh_operator

gencheck_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test gencheck_operator

test_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test test_operator

e2e_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test e2e_operator

mandiff_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test mandiff_operator

lint_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test lint_operator

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.

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

Test name
Commit
Details
Rerun command

mesh_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test mesh_operator

test_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test test_operator

e2e_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test e2e_operator

mandiff_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test mandiff_operator

lint_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test lint_operator

gencheck_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test gencheck_operator

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.

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

Test name
Commit
Details
Rerun command

mesh_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test mesh_operator

test_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test test_operator

mandiff_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test mandiff_operator

lint_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test lint_operator

gencheck_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test gencheck_operator

e2e_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test e2e_operator

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.

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

Test name
Commit
Details
Rerun command

test_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test test_operator

mandiff_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test mandiff_operator

lint_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test lint_operator

gencheck_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test gencheck_operator

e2e_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test e2e_operator

mesh_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test mesh_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
e34e49028c561fd23febe988ac6a1c81d10b9e85
link
/test mandiff_operator

lint_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test lint_operator

gencheck_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test gencheck_operator

e2e_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test e2e_operator

mesh_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test mesh_operator

test_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test test_operator

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.

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

Test name
Commit
Details
Rerun command

lint_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test lint_operator

gencheck_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test gencheck_operator

e2e_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test e2e_operator

mesh_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test mesh_operator

test_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test test_operator

mandiff_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test mandiff_operator

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.

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

Test name
Commit
Details
Rerun command

lint_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test lint_operator

gencheck_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test gencheck_operator

e2e_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test e2e_operator

mesh_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test mesh_operator

test_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test test_operator

mandiff_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test mandiff_operator

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.

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

Test name
Commit
Details
Rerun command

lint_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test lint_operator

gencheck_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test gencheck_operator

e2e_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test e2e_operator

test_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test test_operator

mandiff_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test mandiff_operator

mesh_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test mesh_operator

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.

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

Test name
Commit
Details
Rerun command

lint_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test lint_operator

gencheck_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test gencheck_operator

e2e_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test e2e_operator

mandiff_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test mandiff_operator

mesh_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test mesh_operator

test_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test test_operator

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.

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

Test name
Commit
Details
Rerun command

gencheck_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test gencheck_operator

e2e_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test e2e_operator

mandiff_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test mandiff_operator

mesh_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test mesh_operator

test_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test test_operator

lint_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test lint_operator

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.

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

Test name
Commit
Details
Rerun command

e2e_operator
9929214c53c487c6ac846ca5779c51db8907a38a
link
/test e2e_operator

mandiff_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test mandiff_operator

mesh_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test mesh_operator

test_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test test_operator

lint_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test lint_operator

gencheck_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test gencheck_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test mandiff_operator

mesh_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test mesh_operator

test_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test test_operator

lint_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test lint_operator

gencheck_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test gencheck_operator

e2e_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test e2e_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test mandiff_operator

mesh_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test mesh_operator

test_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test test_operator

lint_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test lint_operator

e2e_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test e2e_operator

gencheck_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test gencheck_operator

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.

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

Test name
Commit
Details
Rerun command

mesh_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test mesh_operator

test_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test test_operator

lint_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test lint_operator

e2e_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test e2e_operator

gencheck_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test gencheck_operator

mandiff_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test mandiff_operator

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.

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

Test name
Commit
Details
Rerun command

mesh_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test mesh_operator

test_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test test_operator

e2e_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test e2e_operator

gencheck_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test gencheck_operator

mandiff_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test mandiff_operator

lint_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test lint_operator

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.

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

Test name
Commit
Details
Rerun command

mesh_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test mesh_operator

test_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test test_operator

gencheck_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test gencheck_operator

mandiff_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test mandiff_operator

lint_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test lint_operator

e2e_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test e2e_operator

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.

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

Test name
Commit
Details
Rerun command

mesh_operator
05b262711794d30b1ff193b0d3d6542f455a7aed
link
/test mesh_operator

gencheck_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test gencheck_operator

mandiff_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test mandiff_operator

lint_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test lint_operator

e2e_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test e2e_operator

test_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test test_operator

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.

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

Test name
Commit
Details
Rerun command

gencheck_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test gencheck_operator

mandiff_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test mandiff_operator

lint_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test lint_operator

e2e_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test e2e_operator

test_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test test_operator

mesh_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test mesh_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test mandiff_operator

lint_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test lint_operator

e2e_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test e2e_operator

test_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test test_operator

mesh_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test mesh_operator

gencheck_operator
449ad1462b3195e6dbca52c9dda460ae7bf3fb96
link
/test gencheck_operator

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.

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

Test name
Commit
Details
Rerun command

lint_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test lint_operator

e2e_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test e2e_operator

test_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test test_operator

mesh_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test mesh_operator

gencheck_operator
449ad1462b3195e6dbca52c9dda460ae7bf3fb96
link
/test gencheck_operator

mandiff_operator
449ad1462b3195e6dbca52c9dda460ae7bf3fb96
link
/test mandiff_operator

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.

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

Test name
Commit
Details
Rerun command

lint_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test lint_operator

test_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test test_operator

gencheck_operator
449ad1462b3195e6dbca52c9dda460ae7bf3fb96
link
/test gencheck_operator

mandiff_operator
449ad1462b3195e6dbca52c9dda460ae7bf3fb96
link
/test mandiff_operator

e2e_operator
449ad1462b3195e6dbca52c9dda460ae7bf3fb96
link
/test e2e_operator

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.

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

Test name
Commit
Details
Rerun command

lint_operator
0ff0f91e1d36236954917c6849d9a94c60eb94b6
link
/test lint_operator

gencheck_operator
449ad1462b3195e6dbca52c9dda460ae7bf3fb96
link
/test gencheck_operator

mandiff_operator
449ad1462b3195e6dbca52c9dda460ae7bf3fb96
link
/test mandiff_operator

e2e_operator
449ad1462b3195e6dbca52c9dda460ae7bf3fb96
link
/test e2e_operator

test_operator
449ad1462b3195e6dbca52c9dda460ae7bf3fb96
link
/test test_operator

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.

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

Test name
Commit
Details
Rerun command

gencheck_operator
449ad1462b3195e6dbca52c9dda460ae7bf3fb96
link
/test gencheck_operator

e2e_operator
449ad1462b3195e6dbca52c9dda460ae7bf3fb96
link
/test e2e_operator

test_operator
449ad1462b3195e6dbca52c9dda460ae7bf3fb96
link
/test test_operator

mandiff_operator
2c5e6e96369a91611e3f7e89c3b48d063e77cbe0
link
/test mandiff_operator

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.

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

Test name
Commit
Details
Rerun command

gencheck_operator
449ad1462b3195e6dbca52c9dda460ae7bf3fb96
link
/test gencheck_operator

test_operator
449ad1462b3195e6dbca52c9dda460ae7bf3fb96
link
/test test_operator

mandiff_operator
2c5e6e96369a91611e3f7e89c3b48d063e77cbe0
link
/test mandiff_operator

e2e_operator
2c5e6e96369a91611e3f7e89c3b48d063e77cbe0
link
/test e2e_operator

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.

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

Test name
Commit
Details
Rerun command

test_operator
449ad1462b3195e6dbca52c9dda460ae7bf3fb96
link
/test test_operator

mandiff_operator
2c5e6e96369a91611e3f7e89c3b48d063e77cbe0
link
/test mandiff_operator

e2e_operator
2c5e6e96369a91611e3f7e89c3b48d063e77cbe0
link
/test e2e_operator

gencheck_operator
2c5e6e96369a91611e3f7e89c3b48d063e77cbe0
link
/test gencheck_operator

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.

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

Test name
Commit
Details
Rerun command

test_operator
449ad1462b3195e6dbca52c9dda460ae7bf3fb96
link
/test test_operator

e2e_operator
2c5e6e96369a91611e3f7e89c3b48d063e77cbe0
link
/test e2e_operator

gencheck_operator
2c5e6e96369a91611e3f7e89c3b48d063e77cbe0
link
/test gencheck_operator

mandiff_operator
19629e820ccde79144ddf554854d6d93119da63b
link
/test mandiff_operator

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.

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

Test name
Commit
Details
Rerun command

test_operator
449ad1462b3195e6dbca52c9dda460ae7bf3fb96
link
/test test_operator

e2e_operator
2c5e6e96369a91611e3f7e89c3b48d063e77cbe0
link
/test e2e_operator

mandiff_operator
19629e820ccde79144ddf554854d6d93119da63b
link
/test mandiff_operator

gencheck_operator
19629e820ccde79144ddf554854d6d93119da63b
link
/test gencheck_operator

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.

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

Test name
Commit
Details
Rerun command

test_operator
449ad1462b3195e6dbca52c9dda460ae7bf3fb96
link
/test test_operator

mandiff_operator
19629e820ccde79144ddf554854d6d93119da63b
link
/test mandiff_operator

gencheck_operator
19629e820ccde79144ddf554854d6d93119da63b
link
/test gencheck_operator

e2e_operator
19629e820ccde79144ddf554854d6d93119da63b
link
/test e2e_operator

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.

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

Test name
Commit
Details
Rerun command

gencheck_operator
19629e820ccde79144ddf554854d6d93119da63b
link
/test gencheck_operator

e2e_operator
19629e820ccde79144ddf554854d6d93119da63b
link
/test e2e_operator

mandiff_operator
fe3c0170f2c538c0259aecbaea1bfb16a5ec9a75
link
/test mandiff_operator

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.

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

Test name
Commit
Details
Rerun command

e2e_operator
19629e820ccde79144ddf554854d6d93119da63b
link
/test e2e_operator

mandiff_operator
fe3c0170f2c538c0259aecbaea1bfb16a5ec9a75
link
/test mandiff_operator

test_operator
fe3c0170f2c538c0259aecbaea1bfb16a5ec9a75
link
/test test_operator

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.

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

Test name
Commit
Details
Rerun command

mandiff_operator
fe3c0170f2c538c0259aecbaea1bfb16a5ec9a75
link
/test mandiff_operator

test_operator
fe3c0170f2c538c0259aecbaea1bfb16a5ec9a75
link
/test test_operator

e2e_operator
fe3c0170f2c538c0259aecbaea1bfb16a5ec9a75
link
/test e2e_operator

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.

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

Test name
Commit
Details
Rerun command

e2e_operator
fe3c0170f2c538c0259aecbaea1bfb16a5ec9a75
link
/test e2e_operator

test_operator
ec4b56354898442be5c46a847dedd4f49225f3d4
link
/test test_operator

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.

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

Test name
Commit
Details
Rerun command

e2e_operator
fe3c0170f2c538c0259aecbaea1bfb16a5ec9a75
link
/test e2e_operator

test_operator
80d21119a64c131c9a6f3493a963050e4a4f68d2
link
/test test_operator

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.

@ostromart: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
1fce1aacb00eb98b86893f939f38b5801e174093
link
/test e2e_operator

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

/retest

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

Test name
Commit
Details
Rerun command

e2e_operator
1fce1aacb00eb98b86893f939f38b5801e174093
link
/test e2e_operator

gencheck_operator
c37865d339fe00edfd82207dced7f1cdcc6aedd5
link
/test gencheck_operator

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.

@ostromart: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
86e6fbc04b4a608d5cee90443b9e56bd03681fe8
link
/test e2e_operator

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.

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

Test name
Commit
Details
Rerun command

e2e_operator
86e6fbc04b4a608d5cee90443b9e56bd03681fe8
link
/test e2e_operator

test_operator
a7093e57723472fbcc1b1e2b7d90592a724c2677
link
/test test_operator

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.

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

Test name
Commit
Details
Rerun command

test_operator
a7093e57723472fbcc1b1e2b7d90592a724c2677
link
/test test_operator

e2e_operator
a7093e57723472fbcc1b1e2b7d90592a724c2677
link
/test e2e_operator

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.

@ostromart: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
ee71ef15bbbf2d7d139a1995424fc308697355be
link
/test e2e_operator

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.

@ostromart: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
88880a18289f06cee1bd7fe441867bfc2ac21976
link
/test e2e_operator

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.

@ostromart: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
b707f51441f153430a455e8cb8dcfced6b40153c
link
/test e2e_operator

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.

@ostromart: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
62d6d364ace8d898c712af9ef16470502ef1fcec
link
/test e2e_operator

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.

@ostromart: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
ffd072ab89395456fd786df3c48b30e0baaf798d
link
/test e2e_operator

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.

@ostromart: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
43a3caeff0b6122ba1d1d93ab2dbb641718dc75f
link
/test e2e_operator

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.

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

Test name
Commit
Details
Rerun command

e2e_operator
43a3caeff0b6122ba1d1d93ab2dbb641718dc75f
link
/test e2e_operator

test_operator
43a3caeff0b6122ba1d1d93ab2dbb641718dc75f
link
/test test_operator

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.

@ostromart: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
b8f1bfa8eeb4543347193c069719262fb6b784d2
link
/test e2e_operator

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.

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

Test name
Commit
Details
Rerun command

e2e_operator
b8f1bfa8eeb4543347193c069719262fb6b784d2
link
/test e2e_operator

gencheck_operator
736eaf8a179419ec1425987367e04350a41c4a45
link
/test gencheck_operator

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.

we should block the master from merging other PRs before we merge this one.

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

Test name
Commit
Details
Rerun command

e2e_operator
b8f1bfa8eeb4543347193c069719262fb6b784d2
link
/test e2e_operator

gencheck_operator
736eaf8a179419ec1425987367e04350a41c4a45
link
/test gencheck_operator

test_operator
736eaf8a179419ec1425987367e04350a41c4a45
link
/test test_operator

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.

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

Test name
Commit
Details
Rerun command

gencheck_operator
736eaf8a179419ec1425987367e04350a41c4a45
link
/test gencheck_operator

test_operator
736eaf8a179419ec1425987367e04350a41c4a45
link
/test test_operator

e2e_operator
736eaf8a179419ec1425987367e04350a41c4a45
link
/test e2e_operator

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.

@ostromart: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
3dcf01123927fc379116a319da84204ccc359925
link
/test e2e_operator

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.

@ostromart: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
f061a7a1ffef422ed50d897a9499a25bdd1b93f4
link
/test e2e_operator

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.


570 shortcodes and moretags

This is @newkind's commits from #570 relating to get_preview, <!-- more --> tags and shortcodes. I'm moving it into its own PR for discussion and testing

@newkind can you explain how the <!-- more --> tag implementation you setup here differs from the previous? It'd be very helpful to see an example of how a prior usage would have failed with the existing code so I can evaluate the new one

Sure :)
So WordPress (and Timber) allows you to set the custom label for the read more button ie. Read More. However when using WP Core native the_content you can also define the label on a per post basis by doing <!--more I'm important! Read Me!--> in the post content.
If WordPress (and now Timber) will find such modified tag in the post content, they will display I'm important! Read Me! as a button label instead of Read More, but only for that one post.
Sample :

Post 1
In condimentum facilisis porta. Sed nec diam eu diam mattis viverra. Nulla. Read More

Post 2
In condimentum facilisis porta. Sed nec diam eu diam mattis viverra. Nulla. I'm important! Read Me!

Post 3
In condimentum facilisis porta. Sed nec diam eu diam mattis viverra. Nulla. Read More

Post 4
In condimentum facilisis porta. Sed nec diam eu diam mattis viverra. Nulla. Read More

I was just looking at this too. I think the following would be a test for this feature (which is new to me!).
// content with <!--more --> tag with custom read more defined
$post->post_content = 'this is super dooper<!--moreMy read more--> trooper long words';
$preview = $post->get_preview(2, false);
$this->assertRegExp('/this is super dooper <a href="http:\/\/example.org\/\?p=\d+" class="read-more">My read more<\/a>/', $preview);

I've also been looking at the do_shortcode additions on lines 228 and 232. The first one – happening within the test for the  tag – I think will work. The second one however will not I think work because TimberHelper::trim_words($this->get_content(), $len, false) will already execute the short code (within TimberPost::get_content() because the_content filter gets applied). But trim_words also strips all tags but p a span b i br so most shortcode output (e.g. caption, gallery etc) will get stripped out.


Allow for the package to work with a different systematic grid

@ivalaginja Which sections of the code would need to be modified to account for this?
Are these all in margmodule.py or would marginalisation.py also have to change to allow for this?
How can we make the package generic enough to pull out and put in our own systematic grid? While keeping the same switches for the time, inc, msmpr, etc.

@hrwakeford I believe you collected the main steps required for this in #23 - is this what you mean?

@hrwakeford I believe you collected the main steps required for this in #23 - is this what you mean?


use collapse-after for dependencies category

bump release-drafter.yml
You can see it in action here: https://github.com/release-drafter/release-drafter/releases/tag/v5.19.0

Aha, you beat me to it! Thanks so much @jetersen!

@rnorth your welcome

Checking the last release notes under dependencies https://github.com/testcontainers/testcontainers-java/releases/tag/1.17.0
Seems like someone manually removed the newline inside the details.
I know we tested this on release-drafter and made sure it produced the correct draft: https://github.com/release-drafter/release-drafter/blob/bb54ed7b74715dd4fe3d0a5c76fb1c570f6fc7b6/lib/releases.js#L264-L273
Example:
<details>
<summary>9 changes</summary>

* Bump minimist from 1.2.5 to 1.2.6 (#1116) @dependabot
* Bump lint-staged from 12.3.6 to 12.3.7 (#1104) @dependabot
* Bump eslint-plugin-unicorn from 41.0.0 to 41.0.1 (#1105) @dependabot
* Bump node from `8c62619` to `d1d5dc5` (#1106) @dependabot
* Bump probot from 12.2.1 to 12.2.2 (#1097) @dependabot
* Bump node from 17.6.0-alpine to 17.7.1-alpine (#1100) @dependabot
* Bump eslint from 8.10.0 to 8.11.0 (#1099) @dependabot
* Bump prettier from 2.5.1 to 2.6.0 (#1102) @dependabot
* Bump lint-staged from 12.3.5 to 12.3.6 (#1103) @dependabot
</details>

Good thing that feature is requested for release drafter 😅

We have a very specific process to merge dependabot PRs:
https://www.testcontainers.org/contributing/#combining-dependabot-prs
This means, we have to manually inline the actual dependabot PRs that were included in the combined PR. It's probably too specific to us for release-draft to take care of it 🙂

@kiview make an easy workaround we could add inside release drafter was a HTML comment to help you insert correctly into the details block? 😉

Oh yes, I would love this @jetersen 😍


space param should either be documented or default to ' '

space param isn't in the readme, so by default output is uglified. The few times I've used this plugin I've been using editor plugins to pretty print the output. It was only today when looking at the code I realised there's a space param.
Personally I think the default should be 2 spaces, rather than an 0 length string. The whole point of this plugin is to see what meta data is being generated, and you can't do that without pretty printing the output. I can't think of any circumstances in which pretty printed output would be detrimental.

I will have a look into it. But I use it for generating my website, so I haven't thought about. I will document it.


even shorter

✌
shorter and using a syntax feature already introduced in [...iterable]

This raises the compatibility a bit. Even the latest Edge preview doesn't support object spread according to https://kangax.github.io/compat-table/es2016plus/
Transpilation turns it into:
var _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; };

function fromEntries(iterable) {
  return [...iterable].reduce((obj, [key, val]) => _extends({}, obj, { [key]: val }), {});
}

Thanks for the PR. :) I don't want to require support for object destructuring because that's still not in Edge :/


⚠ Fortnite has degraded performance

In 1f7f9e7, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 4041 ms

Resolved: Fortnite performance has improved in e6a9c98.


Is this project active?

Seeing that the last active issue is from late September.

Hi yes this project is actively used in different places however the angular AOT plugin and @ngtools ships with its own template inlining feature. When I first created this project, I was not a maintainer of the webpack org. Since joining the webpack core team, this repo has been neglected a bit but I am open to PRs and features.

I'm not up-to-date with angular-cli and @ngtools, so here I'm asking: what would be the alternative path to not use this loader anymore? Of course, still remaining with angular 2, webpack 2, typescript 2, ...
Thanks

angular2-template-loader is great for JiT builds along with awesome-typescript-loader, also great for testing, but JiT builds are no longer acceptable production solutions given their longer than reasonable render times. For AoT, @ngtools/webpack is used in place of the combination of awesome-typescript-loader and angular2-template-loader, and the AoTPlugin (shipped within @ngtools/webpack) takes care of your ngc compilation (ngc is a wrapper around tsc that a) transpiles your typescript, and b) does the Ahead-Of-Time compilation that is the namesake of AoT.
For example, here's my loader configuration for JiT builds and AoT builds:
exports.ts_JiT = {
  test: /\.ts$/,
  loaders: [
    'awesome-typescript-loader',
    'angular2-template-loader'
  ],
  exclude: [ /\.(spec|e2e|async)\.ts$/ ]
};

exports.ts_AoT = {
  test: /\.ts$/,
  loader: '@ngtools/webpack'
};

And my plugin configuration for the AoTPlugin:
exports.aot = new AotPlugin({
  tsConfigPath: path.resolve('./tsconfig-aot.json'),
  mainPath: path.resolve('./src/main.ts'),
  entryModule: path.resolve('./src/app/app.module') + '#AppModule'
});

Should be noted though that apparently @ngtools/webpack can also handle JiT builds, I'm just used to this particular toolchain and it's been good to me. :) Much respect, @TheLarkInn.

Hi @nikolasleblanc and thanks for your info!
My bad for not being clear: @TheLarkInn is doing a great job, was just asking him what is he suggesting, given the current "work overload" and progress in angular-cli .
Also, I'm aware of JIT Vs AOT, and before some recent issues I had with awesome-typescript-loader and some I'm now having with angular2-template-loader, my team was happy bundling both a dev JIT build as well as an AOT production build, the latter also with angular-router-loader and lazy-loading (also waiting on next angular 4 to see some more improvements on tree shaking).
Now, it's a couple of days that we're stuck with this weird issues, in particular #50 and others similar listed here.
Back to your experience, if I got it right: angular-cli and/or @ngtools/webpack can take the place of awesome-typescript-loader + angular2-template-loader, both for JIT and AOT builds.
Q1: Is that right?
Q2: What happens to lazy-loading in that case?
Thanks for your help

Back to your experience, if I got it right: angular-cli and/or @ngtools/webpack can take the place of awesome-typescript-loader + angular2-template-loader, both for JIT and AOT builds.

Yup. Just, personally, I stick to angular2-template-loader and awesome-typescript-loader for my JiT stuff, which is really just for e2e and testing since they compile faster.

Q2: What happens to lazy-loading in that case?

Pretty sure you can bring in angular-router-loader as part of your JiT build, and @ngtools/webpack handles lazy loaded routes for you when building AoT. See https://www.npmjs.com/package/@ngtools/webpack#features.

Recognizing the use of loadChildren in the router, and bundling those modules separately so that any dependencies of those modules are not going to be loaded as part of your main bundle. These separate bundles will be pulled out of the critical path of your application, making your total application bundle much smaller and loading it much more performant.

Re your issue #50, I commented there.

Oh and I wasn't suggesting your were giving the LarkInn any grief, I just felt it was time for me to give him some props. :)


Added Action/Func Delegates In C#

Added action/func delegates and unit test files as well.
Please review it.

closed


Missing CONTRIBUTION.md File

The repository currently lacks a CONTRIBUTING.md file, which is an important resource for guiding potential contributors on how to engage with the project effectively. A CONTRIBUTING.md file outlines the contribution guidelines, coding standards, and procedures for submitting pull requests, thus streamlining the contribution process and ensuring consistency across contributions.
Could you please assign this issue to me under GSSOC 24.

Duplicate issue. Already raised #9


Can't see the Result file in eval.ai's my submissions

Thank you for hosting this competition.
I have a question about the problem on eval.ai.
Currently, in My Submissions on eval.ai, I cannot see the Result file. When I open it, it looks like this.

"

On the leaderboard, I can see the result of the submission file with the highest score, but I cannot see the other files.
Can you please make it possible to see the other results as well?
Thank you in advance.

Hi, thanks for reporting. It looks like this is a limitation of evalAI. The result file isn't working.
As a workaround, I'll just update the script to print the metrics such that you can see the results in the stdout file

@lg-zhang
Thanks for the reply.
I understood about the limitations of eval.ai, and I would appreciate it if you could let me know when you are able to see the scores in the stdout file.
Thank you very much.

@lg-zhang
Thank you for your response.
I was just able to check the score in the Stdout file in My Submmitons!
Please close this issue. Please keep us posted.


Fixes sentry issues #239916469 & #229385444

https://sentry.io/en-marche-i7/en-marchefr/issues/239916469/
https://sentry.io/en-marche-i7/en-marchefr/issues/229385444/

Awesome, never had the time to dig in this! Thanks!


Update NVCC: 10.1.243 -> 11.0.221

Try to skip the CUDA toolkit shipped with ubuntu:latest and go straight for a newer one, hoping that we can avoid having to work-around some compiler bugs.

[ ] run locally and see if that version of the CUDA toolkit already helps us, or if we need an even newer one

Related to https://github.com/nlohmann/json/issues/2676

Fixed! :) (I also removed the duplicate wget that I added on the way)

PATH is now also set and local test was successful :tada:

Very cool! I'll merge this. Then we can add a step to the ubuntu.yml.


HIKVision NVR POE

Hi,
Is it possible to manage NVR POE settings from node-red \ HIK SDK?
For example NVR DS-7608NI-I2.
It needs to switch off several cameras if you at home \ switch on if away.

Good work, Thank you,

Hi,
i'm currently busy on opdating another my node, so i cannot touch this at this time.
You can use the hikvisionUltimateXML node to accomplish your needs, by passing the XML string to control POE ports (but i'm not sure if you can control POE ports from APIs). You need the hikvision API documentation as well.

Hi
i searched on all PDF files of ISAPI i found on internet, but none tells how to toggle POE power.
If you ever find one, please point me on that!


Cannot send files in Excel format

Hello team, I cannot send files in Excel format with HTTP Payloads, only txt format files can be sent.
Please help me.
Thanks for your help in advance.
(https://user-images.githubusercontent.com/63716916/96272998-81808180-0fd7-11eb-8f65-490c6e1a169d.png)

Can you see what the error log says for why there was a problem?

I get 500 error, if I send the request to "data" in "attachments" in double quotes, ie as a string, I send it as a string, but since I want to send it in excel format, I have to send a part of the data as an array. However, I also share the log:
[web.1:1710] [2020-10-20T15:40:55.585] INFO -- : Started POST "/api/v1/send/message" for <IP_ADDRESS> at 2020-10-20 15:40:55 +0300
[web.1:1710] [2020-10-20T15:40:55.642] INFO -- : NoMethodError

Is there more of the logs you can share? also I think you need to base64 encode the attachment but it doesn't appear to be readily documented.

When I encode it as Base64 and send it, I cannot open excel from the incoming mail. I added it in the screenshot.
(https://user-images.githubusercontent.com/63716916/96709924-05ee4e00-13a4-11eb-82f1-66f17c00fab6.png)

It was necessary to send the data in javada attachments with the Base64.encodeBase64String (data) function, not the Base64.encodeBase64 (data) function. The problem was solved when I sent it with Base64.encodeBase64String function. Thank you for your interest.


MAINT: TST: Make tests NumPy 1.8 compatible

In #9190 and #8259 , the tests involve the usage of np.moveaxis and np.testing.assert_warns which are introduced in NumPy 1.11 but we still support 1.8.
And for some reason it has not failed in the original PRs but started to fail recently. I have converted to 1.8.2 compatible syntax without changing the logic.

squashing and merging this since all PRs are failing on this and the change is clear enough to track what changed.


Add ldp papers

Type of change

[x] Add new papers (Please tell us why you think this paper is awesome!)
[ ] Fix the category of an existing paper/papers (Please tell us the reasons)
[ ] Add a new tool/primitive/application with a new markdown page (Thank you! Also, please tell us more about this awesome thing!)

Description

Please include a summary of the change and the relevant motivation.

Add a new SIGMOD '18 paper:  Privacy at Scale: Local Differential Privacy in Practice. A tutorial on LDP with typical applications.
Add a new CCS '21 paper:  AHEAD: Adaptive Hierarchical Decomposition for Range Query under Local Differential Privacy. A highly accurate LDP protocol for both one- and multi-dimensional range query problems.
Add a new CCS '18 paper:  CALM: Consistent Adaptive Local Marginal for Marginal Release under Local Differential Privacy. A highly accurate LDP protocol for marginal release problems.
Add a new VLDB '20 paper:  Answering multi-dimensional range queries under local differential privacy. A highly efficient  LDP protocol for multi-dimensional range query problems.

The catalog has been updated. Could you please reorganize these papers?


Request for Documentation: Index Advice

We're having a lively discussion on the merits of adding an index to the deleted_at column on a very large table in MySQL, which is undergoing a migration to add acts_as_paranoid.
This table is going to have very few records ever deleted, thus the advice at https://stackoverflow.com/questions/26525068/does-laravels-soft-delete-need-index-on-mysql/26530488#26530488 seems to indicate that this is not a good candidate for having such as index. Given a table that has > 20% deleted, it sounds like an index MIGHT be a good idea?
I'd be interested in the advice of more experienced data engineers on this question. Ever more helpful to future users would be a note in the README discussing when this column should be indexed, and when to avoid doing so.

I think the main advice should be to actually measure what happens with your actual database containing your actual data.
Telling people what to do in the README is presuming too much knowledge of users' production systems.
Maybe we can point people with such practical questions to stackoverflow?


Fix server hang on dispose ...

because listenerTaskEvent.Set() is called before the event's WaitOne in ExecuteServerListener.
The latest revision fixed my GUI lockup. However now my unit tests hang because of the aforementioned issue. The change here fixed it.
There may be a better way to accomplish this, if so I'm open to suggestions. Please just let me know.
Thanks,
Gabe

Looks good to me.

The new version should be available now


Typo

LGTM

LGTM

Very stale. Closing. Thanks! Please open a new PR if there is still a relevant change.


Monitor lost/offline network encoders

If a network encoder is configured and not found, it was previously ignored, unless the user navigated to the source details page, which would trigger an IsFunctioning() call.  It will now be checked for every 15 seconds, and if it starts responding, will be enabled and the scheduler kicked off.  This capability was created for the embedded platform (checking every second), but was never implemented in the standard server.

It is a good idea to make the duration a property instead of hardcoding it.
On Friday, November 27, 2015, Christopher Piper<EMAIL_ADDRESS>wrote:

If a network encoder is configured and not found, it was previously
ignored, unless the user navigated to the source details page, which would
trigger an IsFunctioning() call. It will now be checked for every 15
seconds, and if it starts responding, will be enabled and the scheduler
kicked off. This capability was created for the embedded platform (checking
every second), but was never implemented in the standard server.
You can view, comment on, or merge this pull request online at:
https://github.com/google/sagetv/pull/56
Commit Summary

Monitor lost network encoders

File Changes

M java/sage/NetworkCaptureDevice.java
https://github.com/google/sagetv/pull/56/files#diff-0 (4)

Patch Links:

https://github.com/google/sagetv/pull/56.patch
https://github.com/google/sagetv/pull/56.diff

—
Reply to this email directly or view it on GitHub
https://github.com/google/sagetv/pull/56.

--
-Mike

That's possible - the 1000 msec duration was already in there hard coded on servers it was workign on (which actually I don't think there are any that are running v9, and embedded) - I just felt that was a little excessive, but didn't want to change the existing behavior.  While properties are great, you also want to avoid bloating up the .properties file with things that are unlikely to ever need to be changed by an end user.


Update Sheet Database

Resolves: #115
Assists: #62

Sheet deletion is failing for some reason (DELETE FROM); with Unimplemented

DROP TABLE didn't throw but also didn't work...

Codecov Report

Merging #117 (eb1f408) into main (748c249) will decrease coverage by 0.17%.
The diff coverage is 61.40%.

@@            Coverage Diff             @@
##             main     #117      +/-   ##
==========================================
- Coverage   83.95%   83.78%   -0.18%
==========================================
  Files         123      123
  Lines        4033     4058      +25
==========================================
+ Hits         3386     3400      +14
- Misses        647      658      +11

Impacted Files
Coverage Δ

src/data/value/convert.rs
84.61% <0.00%> (-15.39%)
:arrow_down:

src/data/value/mod.rs
61.79% <ø> (ø)

src/storages/sheet_storage/alter_table.rs
0.00% <0.00%> (ø)

src/storages/sheet_storage/auto_increment.rs
66.66% <33.33%> (-19.05%)
:arrow_down:

src/data/value/cast.rs
75.33% <38.09%> (-2.93%)
:arrow_down:

src/storages/sheet_storage/store_mut.rs
93.33% <75.00%> (-3.04%)
:arrow_down:

src/storages/sheet_storage/mod.rs
80.00% <100.00%> (ø)

src/storages/sheet_storage/store.rs
80.39% <100.00%> (+1.66%)
:arrow_up:

src/store/store_mut.rs
0.00% <0.00%> (ø)

src/store/auto_increment.rs
0.00% <0.00%> (ø)

... and 3 more

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 748c249...eb1f408. Read the comment docs.


Properties window of services doesn't work

Describe the bug
When trying to open the properties window of a service, it does not function properly. Some "ghost" window is opened, but that's it.
To Reproduce
Steps to reproduce the behavior:

Go to the services tab
Right click a service
Click "Properties"
Observe the windows opened by Process Hacker

Expected behavior
A properties window should have popped up.
Screenshots
Here is an image of the "ghost" windows opened by Process Hacker. Note that nothing happens when I click said windows.

Version info

OS: Windows 10, 1809 (17763.1879) (LTSC)
Process Hacker Version: 3.0.3993 (4cf0bfa)

Additional Info
Process Hacker is running as administrator, but this isn't achieved by using Process Hacker's own experimental "Enable start as admin" option.

What language are you using for Windows? I haven't been able to reproduce this using English versions.

What language are you using for Windows? I haven't been able to reproduce this using English versions.

I am using the Dutch language on Windows.

I ran into a similar issue after moving these windows with multiple monitors and switching to a single monitor. To reproduce change the value of Advanced Settings HandlePropertiesWindowPosition for example to -2000,-2000, I fixed it by manually editing Advanced Settings *Position to positives values (like 200,200).

I ran into a similar issue after moving these windows with multiple monitors and switching to a single monitor. To reproduce change the value of Advanced Settings HandlePropertiesWindowPosition for example to -2000,-2000, I fixed it by manually editing Advanced Settings *Position to positives values (like 200,200).

This was exactly what happened to me, I used to use two monitors but recently switched to using just a single one. This fixed it for me, thanks a lot!


Shorthand for binding properties

It would be very convenient to be able to write this:
:product="product"
like this:
:product
I think it would make a lot of sense as people are already familiar with this shorthand in ES6 objects, and it would save a lot of characters for people who use props a lot!

See #2877


[feature] use config file to store resonite location

So. I store resonite on my D:/ drive, since it is fast and means im not eating storage
I was hoping this tool could be setup to be an one-click and update unless something goes wrong
so maybe have an optional ResoniteModUpdater.cfg file next to it that just has an line for Resonite location?

for the time being you can probably create a ResoniteModUpdater.bat which just runs the mod updater with whatever path you want, that way it can be single click too


unit tests failing: IndyPayments.ParseGetPaymentSourcesAsync cannot parse response

I'm currently trying to update from AgentFramework.* namespace to Hyperledger.Aries.* namespaces. I'm filing this issue because while trying to do that, I also have failing unit tests, and I don't know if that's a current known problem or if I've somehow broken something.
On MacOS with tip on 3a915cae803, 11 of the unit tests for Hyperledger.Aries.sln fail.
I am also using libsovtoken @ 1813b3d8b and indy-sdk@  e7bbfdcb2.
An example failure is:
Hyperledger.Indy.InvalidStructureException : A value being processed is not valid.
Stack trace:
   at Hyperledger.Aries.Payments.SovrinToken.SovrinPaymentService.RefreshBalanceAsync(IAgentContext agentContext, PaymentAddressRecord paymentAddress) in /Users/jallen/work/sovrin/aries-framework-dotnet/src/Hyperledger.Aries.Payments.SovrinToken/SovrinPaymentService.cs:line 117
   at Hyperledger.Aries.Tests.Payments.TransferTests.MintSovrinTokens() in /Users/jallen/work/sovrin/aries-framework-dotnet/test/Hyperledger.Aries.Tests/Payments/TransferTests.cs:line 33
--- End of stack trace from previous location where exception was thrown ---
Hyperledger.Indy.InvalidStructureException : A value being processed is not valid.

The unit test runner we have in CI uses libindy 1.12.0 and libsovtoken 1.0.3, as defined in this docker file at https://github.com/streetcred-id/docker image streetcred/dotnet-indy:1.12.1
I believe latest versions are libindy 1.13.0 and 1.0.5 for libsovtoken and libsovtokenfees. I try to update these occasionally, to make sure we're following on latest updates. The dependency for compatibility also includes running the correct version of indy-plenum. A lot of these streams move fast, so it's hard to follow them every time they release a version, so we only do periodic updates.
I wouldn't be too worried about this specific unit test, unless you are using sovrin tokens for your work.
Let's keep this issue open. It seems some structure changed between the indy node you're running and the sovtoken fees library.

@jeffallen I have updated (#62) the test images to latest indy node, indy sdk and sovtoken versions.
indy-node 1.12.0, indy-sdk 1.14.2, and sovtoken 1.0.5. I haven't been able to reproduce the exception above. All unit tests seem to pass.
Are you still experiencing this issue?

I do not have my dotnet build environment working anymore. Closing.


Update AWS Getting Started guide with additional explanations

Description of changes:
Revise https://github.com/awslabs/karpenter/tree/main/docs/aws for a more launch ready doc.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Just a quick note on the PR name. These ultimately land in our patch note, so we typically try to make them informative and framed in a linguistic way that sounds good for notes, e.g. (Updated AWS Getting Started guide to include ...)

ok thanks this is still very much a WIP :)

Is this still WIP?

Thanks for the feedback everyone! I pushed an update, and responded to comments.
If I marked it as resolved, then I accepted the suggestion.


Add spatial plot function for 10X Visium data

Function spatial defined in plotting.plot_library.
Besides, the following modifications are applied accordingly:

Add _plot_circles function in plotting.plot_utils to make scatter plot with point circle size being data-specific.
Add marker_size and scale_factor arguments to function scatter function in plotting.plot_library:

spatial function sets marker_size and scale_factor based on the spatial image to use as the background.
Use _plot_circles instead of matplotlib.pyplot.scatter for spatial plots.
For general scatter plots, both arguments are None.

@bli25 Changes have been made.
In spatial function definition, I commented that alpha is used for blending the attribute layers, while alpha_img for the background spatial image. Are these the appropriate wording?


Is this repo deprecated?

There is no activity in this repo.
What would be better resource for building NMT models?

Perhaps this tutorial: https://www.tensorflow.org/tutorials/text/nmt_with_attention

This implementation is too old. You can implement NMT with tf 2.0 easily. As @mommi84 mentioned, nmt_with_attention is an excellent tutorial.
If you want a Transformer model, you can find it in my repo: transformers-keras

Thanks @luozhouyang.
I will definitelty have a look at the nmt_with_attention tutorial.
Actually at first I was thinking to use the model from that tutorial. However, was not sure how that will trade as this repo seems to be authoritative and many publications have cited this repo.
I will look into the tutorial and would a comparison.

You're welcome, @nashid. 😅
I think the reason this repo seems authoritative is simply that it had been pioneering in the sequence-to-sequence era. It could be that today the accuracy you obtain will be higher than the new models', but likely not in the long term once tf 2.0 reaches the plateau of productivity.


Boids example

Description
For the release <IP_ADDRESS> a set of examples are being developed to check how easy it is to use atta.
The changelog in the comments will list all the changes when developing this project, mainly bug fixes and code refactoring.
The repository for this project can be found here: https://github.com/brenocq-atta/boids
Tasks

[x] Boids workings
[x] Movable obstacles
[x] Show force field in the background
[x] Inspect selected boid (plot data)
[ ] Plot boid view radius
[ ] Improve boid algorithm
[ ] Update published web build on commit

Atta changelog

Scripts now are being loaded properly
cmp::getPrototypeFactory(cmp::Entity) renamed to cmp::getFactory(cmp::Entity)
Fix crash when material name is ""
Now scr::ProjectScript::onLoad is called only after the components are deserialized from the .atta file
Now it is possible to use literal ""_sid without being in the atta scope


Python 3.11 compatibility

Hi, thanks for creating this package! I have a project that depends on it, and it appears that it cannot work with python 3.11 apparently because it seems like docstring-inheritance doesn't work with python 3.11. See here
Is the any reason that setup.cfg can't be updated to include python 3.11? I'm happy to PR it

I've just released the version 1.0.1 with python 3.11 support.

Thanks!


Update install packagecontroller doc

Description of changes:

Update curated packages doc with previous release details.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherry-pick release-0.10


Wrong URL links in Component Object Model(COM) Docs

🛑 IMPORTANT: You can get your feedback addressed faster if you use the comment section for the article in which you encountered a problem.
Link to article:
Tell us where exactly a problem occurs.
https://docs.microsoft.com/en-us/windows/desktop/com/functions-odt
Problem:
What's wrong with the article?
The URL link of function OleCreate is Wrong

@ginami Can you take a look at this issue?


Updated and revised README.md, together with an example screenshot.

Saw this on Hacker News and thought together with some other peers at the discussion that it would be better for this project to have a screenshot inside the README.md.
I also revised some wordings here and there.

Yes! I'm going to try to work on this when I have some downtime o/

I'm gonna rerun the software and update the screenshot as well

Sounds like a plan. Feel free to ping me with any questions you may have.

Hey @flipbit03! I ended up cherry picking some of your commit and merged it into the README. I added a new screenshot too. I also implemented the first cut of log tailing so if that interests you, I hope it works well!
Thanks again for your patch and I hope you can contribute again in the future!