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

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test release-test_istio

unit-tests_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test unit-tests_istio

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

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

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

analyze-tests_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test analyze-tests_istio

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

lint_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test lint_istio

gencheck_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test gencheck_istio

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

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

integ-helm-tests_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test integ-helm-tests_istio

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test release-test_istio

unit-tests_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test unit-tests_istio

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

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

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

analyze-tests_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test analyze-tests_istio

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

lint_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test lint_istio

gencheck_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test gencheck_istio

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

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

integ-helm-tests_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test integ-helm-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test release-test_istio

unit-tests_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test unit-tests_istio

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

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

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

analyze-tests_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test analyze-tests_istio

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

lint_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test lint_istio

gencheck_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test gencheck_istio

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

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

integ-helm-tests_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test integ-helm-tests_istio

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

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

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test release-test_istio

unit-tests_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test unit-tests_istio

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

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

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

analyze-tests_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test analyze-tests_istio

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

lint_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test lint_istio

gencheck_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test gencheck_istio

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

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

integ-helm-tests_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test integ-helm-tests_istio

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

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

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

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test release-test_istio

unit-tests_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test unit-tests_istio

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

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

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

analyze-tests_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test analyze-tests_istio

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

lint_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test lint_istio

gencheck_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test gencheck_istio

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

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

integ-helm-tests_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test integ-helm-tests_istio

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

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

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

release-notes_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test release-test_istio

unit-tests_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test unit-tests_istio

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

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

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

analyze-tests_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test analyze-tests_istio

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

lint_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test lint_istio

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

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

integ-helm-tests_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test integ-helm-tests_istio

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

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

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

gencheck_istio
922d284242116a367eb2baaf6787521986bdfda1
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

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

release-test_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test release-test_istio

unit-tests_istio
e0278b379f28d57ca141f2156d00e15426200a3e
link
/test unit-tests_istio

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

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

gencheck_istio
064c0625bf1ea18154e0e452e7b86e4a4b59f532
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

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

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

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

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

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

Test name
Commit
Details
Rerun command

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

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

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

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

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

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

Test name
Commit
Details
Rerun command

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

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

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

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

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

/retest

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

Test name
Commit
Details
Rerun command

gencheck_istio
d84df8a4279de06d84e5194357c21b10221c0490
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
d84df8a4279de06d84e5194357c21b10221c0490
link
/test gencheck_istio

lint_istio
d84df8a4279de06d84e5194357c21b10221c0490
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
d84df8a4279de06d84e5194357c21b10221c0490
link
/test gencheck_istio

lint_istio
d84df8a4279de06d84e5194357c21b10221c0490
link
/test lint_istio

unit-tests_istio
d84df8a4279de06d84e5194357c21b10221c0490
link
/test unit-tests_istio

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

@howardjohn @hzxuzhonghu The istio/api version has been bumped, this PR is ready for a final review

@howardjohn @linsun @nrjpoddar can we get final sign off on this? need one more approval

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

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
50895cef9988561f80fd566e86531e45ab514223
link
/test integ-pilot-multicluster-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
50895cef9988561f80fd566e86531e45ab514223
link
/test integ-pilot-multicluster-tests_istio

unit-tests_istio
50895cef9988561f80fd566e86531e45ab514223
link
/test unit-tests_istio

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

DiscoveryNamespaces (namespaces I watch) and "namespaces in the mesh" are
distinct concerns and should not be mixed. Typically the former is a
superset of the latter, as we want to reach pods outside the mesh but in
the cluster.
On Thu, Feb 25, 2021 at 6:16 AM Harvey Xia<EMAIL_ADDRESS>wrote:

@harveyxia commented on this pull request.
In pilot/pkg/serviceregistry/kube/controller/filter/discoverynamespaces.go
https://github.com/istio/istio/pull/29802#discussion_r582866080:

+// limitations under the License.

+package filter
+
+import (

metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"
"k8s.io/apimachinery/pkg/labels"
"k8s.io/apimachinery/pkg/util/sets"
v1 "k8s.io/client-go/listers/core/v1"

"istio.io/pkg/log"
+)

+const (

// PilotDiscoveryLabelName is the name of the label used to indicate a namespace for discovery
PilotDiscoveryLabelName = "istio-discovery"

@l8huang https://github.com/l8huang The original motivation for this
implementation was primarily for performance improvement (filtering out
irrelevant services, pods, and endpoints) , so we kept the
DiscoveryNamespacesFilter scoped to the main service registry controller.
With some refactoring (making DiscoveryNamespacesFilter self contained
and exposing methods for registering handlers for meshConfig and namespace
events) it can be extended for use with other components.
However, before we do any implementation, we should determine whether this
feature is the right abstraction for enabling multiple istiod deployments
(which is an orthogonal concern to performance), or if there are other
designs / existing components that would be better suited for this use
case. @howardjohn https://github.com/howardjohn @costinm
https://github.com/costinm any thoughts?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/29802#discussion_r582866080, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXKVBCRPNXBQTRCRGX3TAZLTNANCNFSM4VNLTZMA
.


[full-ci] update web assets to v7.0.0-rc.6

This PR updates ownCloud Web to v7.0.0-rc.6. Which is the first version of ownCloud Web running on vue3 in compat mode.
@dschmidt could you please push fixes for the settings ui into this branch?

Haha @JammingBen already forgot about the admin-settings config again 🙈  thank you!

That was the plan, will do so in a minute


Create Binary Search C++(STL)

issue #179

pull request merged, now please close the issue, you can also contribute to other repo's-https://github.com/avinash201199/Hacktoberfest-Guide
Note- only 2 pr per day on a single repo is accepted.


prepare doc preview s3-prefix for future change

This patch is correct but somewhat confusing. Right now we are using the $OWNER/$REPO scheme at the start of the s3-prefix:
https://github.com/pytorch/vision/blob/2b25d67925df9741ba2a75a07bc3046302969e87/.github/workflows/docs.yml#L68
However, the CloudFront setup currently swallows a leading pytorch/. Thus, our docs are currently served under https://docs-preview.pytorch.org/$REPO/$PR/index.html, e.g. https://docs-preview.pytorch.org/vision/7453/index.html.
We want to get rid of this configuration in the future. To avoid disruption, this after this PR we will additionally upload to the future location and after a grace period disable the old path.
This means that right now we need to upload with s3-prefix: pytorch/pytorch/vision/ to counteract the CloudFront configuration. After the grace period we can go back to the current pytorch/vision/ since that already uses the $OWNER/$REPO scheme we want. Meaning, after we change the CloudFront configuration, our current setup will upload to https://docs-preview.pytorch.org/$OWNER/$REPO/$PR/index.html
cc @seemethere

Doc preview can now be accessed through

https://docs-preview.pytorch.org/vision/7459/index.html
https://docs-preview.pytorch.org/pytorch/vision/7459/index.html

with the former what the bot currently links to and the former what it will link to in the future.


Investigate home page, collection view,single token, user profile - loading times

Figure out what is causing the lengthy loading times.
On single token there are 2 loads
-initial page load (3-10 seconds)
-purchase section with the selector (10-20 seconds)
test this collection both logged out and logged in to a wallet
https://rair.market/collection/0x2105/0xfc3666266d129504dd6c713f9bce107747ae4aee/0/0

The serial number picker is causing the majority of the load time
some amount of load time for querying the videos but thats okay

Different than Jira - one master ticket with multiple sub branches attached.

Some improvements. Need to add benchmarking for ms to load the full workflow.

Use lighthouse tooling. Run once a week on rair.market (kube) and rairprotocol.xyz (single vm)
Millisecond to load. Homepage. Doodles first page. Doodle scroll to 500 images. User profile page.
| Home |Doodles Init |Doodles 500 | User Profile
10/18
10/25
11/2


Tidy Up README/CONTRIBUTING

Description
Currently, the README is not up to the Catppuccin Aesthetic™ as it just includes the auto-generated userstyles list. We should include a short description of what this repository is.
We should also flesh out the Contributing section to highlight the process of adding/PR'ing a userstyle into the repository. I'm personally hoping that a well-formatted PR template should do most of the work here.
Acceptance Criteria

[ ] Short description of what the repository is
[ ] Mention to enable csp-patching for the Stylus extension
[ ] Contributing section which highlights how the repository is architected + link to Pull Request template.

I'd like to note that we always show the csp-patching line anyway regardless
and it'd it better if we just remove it from the yaml and schema rather than setting it to true.


Question on site license/open source

Sandy shared information about the Benefit Tool at a partnership meeting that included some developers.

The good news: The session was a smash success. Super high level of interest. 🎉
The question: A developer did follow up with some interest but in looking at our GitHub he said one of the pieces of code that we're using is not open source but requires a small site license. @MattF-NSIDC I'm wondering if you could clarify this (no rush) - Sandy and I don't understand the implications here.

Sorry, 'bug fixes' may not be the best place for this, just want to be sure it's captured somewhere

An excellent observation. Last I checked, I believe it was when starting the prototype, Highcharts permitted non-commercial use without applying for a license, but that seems to have changed since then. I don't know if this applies to the version we're currently running or not, but my guess is the changed license applies retroactively or something. The only non-commercial free license option is now an "Educational license" which requires an application and lasts 1 year. We should move off of this software IMO.
Highcharts is only used for rendering the Sankey diagrams, so replacing it won't touch very much code.

Thanks for this - very clear and now it does belong in the bugs category!

We got a new site license for Highcharts covering usaon.org and nsidc.org, so this is not as urgent anymore


Copilot completions are inserted before the point where suggestion begin.

Using Emacs 29.4 on Void Linux with Evil, and installed copilot.el with Elpaca couple hours ago.
Not sure how to describe this behavior in words, so here is the video of what is going on.
Please do change the title if there are better ways to express this.
https://github.com/user-attachments/assets/3c5ee180-26b2-41ae-8c89-8d86d97c93c8
As you can see, when I type the whole "completion candidate" myself, the last character is inserted not at the end of the completion (where it should be), but where the completion candidate was presented originally.
In the first example, I invoked copilot-accept-completion by pressing <tab>. It seems to work fine on simple cases, but I've seen the previous character getting "eaten" and spat out at the end of the completion from time to time. I cannot reproduce this reliably, though.
This package was working fine before, and it seems today's reinstallation has introduced this behavior.
Here is the relevant section in my configuration file: https://github.com/RangHo/dotfiles/blob/main/emacs/.config/emacs/config.org#github-copilot
If you need any more info, please do let me know!

Simple reproducible flow:

Wait for a suggestion to appear
Type first few characters of the suggestion
Hit tab

Now the suggestion gets completed, but the typed characters appear at the end of the completion.

I can confirm that @akurth's method does reproduce the bug!
I was about to run git-bisect; thank you for finding the problematic commit!

I confirm this behavior with the latest commit. This is after using copilot-accept-completion-by-word a couple of times to try to complete the sentences word by word.
https://github.com/user-attachments/assets/eff4f752-a508-4965-9b92-f387fa31103b

Hey, can you test https://github.com/copilot-emacs/copilot.el/pull/354?

Just finished some preliminary testing, but it seems to be working fine for now.
I'll let you know if I find some oddities while I use your patch for work!

Never mind, I just found some weird behavior. Check the video below:
https://github.com/user-attachments/assets/59790427-9fe4-4002-bc3c-ca390029b9ed
Here, I press RET to fill out the type declaration for rightItem. The Svelte language server (+ TypeScript language server) inserts an appropriate import statement when I try to use an unknown type Snippet. Then, when I insert a semicolon, the point moves back to where the suggestion started (which is no longer the correct location due to the automatic import feature) and inserts the semicolon, deleting everything I typed.

I confirmed that this issue is not present in b7bff7b934837744688fd74191ecffb83b3bcc05:
https://github.com/user-attachments/assets/7af8d273-51ea-4c61-9db9-cd58b68a1b7e
For now I'll stick with the older version. Let me know if you need more information. I'll get you some more data once I'm done with work later today.

Fixed it for me, thank you! :)

@RangHo so I cooked up a fix here: https://github.com/copilot-emacs/copilot.el/pull/357. But at this point this looks hacky. I'd appreciate some help with this :sweat_smile:

Hello all,
I recently installed copilot through Melpa on my Emacs 29.3. I am facing the same issue mentioned by @akurth here. I checked @aasseman issue #357 , but did not find a solution there (maybe I did not look correctly, would appreciate if there is a hack code I can temporarily add). Please let me know what I can do to fix this. Thanks!

Hello all, I recently installed copilot through Melpa on my Emacs 29.3. I am facing the same issue mentioned by @akurth here. I checked @aasseman issue #357 , but did not find a solution there (maybe I did not look correctly, would appreciate if there is a hack code I can temporarily add). Please let me know what I can do to fix this. Thanks!

I can't reproduce that one anymore since #354 . Maybe there is some subtlety I'm not getting about the scenario. Can you post a video of the behavior while running #357 ?


python3Packages.spacy: 2.2.3 -> 2.2.4

Motivation for this change
Changelog:
https://github.com/explosion/spaCy/releases/tag/v2.2.4
Tested with the standard example from the spaCy main page.
Things done

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

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

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

@grahamcofborg eval

@GrahamcOfBorg build python3Packages.spacy


retriable: factory config for host

Coverage decreased (-0.07%) to 86.027% when pulling 044278195a07e499d32c5095c2ae656baf8d0ddb on dissoupov into be51bbd574400575e7fabee3506c0fbdb72efc89 on main.


Add new ARO regions to pipelines

Which issue this PR addresses:
Work items per region:

australiacentral
australiacentral2
swedencentral

What this PR does / why we need it:
Part of the new region rollout process.
Test plan for issue:
N/A : This is a pipeline change.
Is there any documentation that needs to be updated for this PR?
Yes - see process documentation and work items above.

Thanks for catching that.  Fixed commit and updated documentation.


error output from screen_recorder 0.2.0 which is not able to import

Because video_cap_com_test depends on screen_recorder >=0.1.0 which requires Flutter SDK version >=3.4.0-34.1.pre, version solving failed.
pub get failed (1; Because video_cap_com_test depends on screen_recorder >=0.1.0 which requires Flutter SDK version >=3.4.0-34.1.pre, version solving failed.)
exit code 1

@ueman  I want to import the latest version of screen_recorder (0.2.0) into my project so that when I make a pub get in my project. Then this happen to my terminal response:
Because video_cap_com_test depends on screen_recorder >=0.1.0 which requires Flutter SDK version >=3.4.0-34.1.pre, version solving failed. pub get failed (1; Because video_cap_com_test depends on screen_recorder >=0.1.0 which requires Flutter SDK version >=3.4.0-34.1.pre, version solving failed.) exit code 1
So how can I use screen_recorder package of the latest version.

@ueman I want to import the latest version of screen_recorder (0.2.0) into my project so that when I make a pub get in my project. Then this happen to my terminal response: Because video_cap_com_test depends on screen_recorder >=0.1.0 which requires Flutter SDK version >=3.4.0-34.1.pre, version solving failed. pub get failed (1; Because video_cap_com_test depends on screen_recorder >=0.1.0 which requires Flutter SDK version >=3.4.0-34.1.pre, version solving failed.) exit code 1 So how can I use screen_recorder package of the latest version.

I'm fixed it by change the flutter channel from stable to beta version. It seems that this package haven't support for the stable version.

@ueman I want to import the latest version of screen_recorder (0.2.0) into my project so that when I make a pub get in my project. Then this happen to my terminal response: Because video_cap_com_test depends on screen_recorder >=0.1.0 which requires Flutter SDK version >=3.4.0-34.1.pre, version solving failed. pub get failed (1; Because video_cap_com_test depends on screen_recorder >=0.1.0 which requires Flutter SDK version >=3.4.0-34.1.pre, version solving failed.) exit code 1 So how can I use screen_recorder package of the latest version.

I'm fixed it by change the flutter channel from stable to beta version. It seems that this package haven't support for the stable version.

Ahh yeah this is what I'm meaning to say that I want use in the stable version.


docs: service accounts documentation

CC @pmuir @craicoverflow

Merged to early. Will add changes to master


Update the config to be able to set the value by shard

What changed?
Update the config to be able to set the value by shard

Why?
replication speed should be configurable by shard

How did you test it?

Potential risks

Coverage decreased (-0.5%) to 66.997% when pulling ed7396ad7bfc08218584fd597a7995494ff0b9bc on replication_batch_size into ea62bcc1426b2dd966de23e72ff715088915bdf3 on master.


Include support for adding, listing, and removing files as Solution Items

Include support for adding, listing, and removing files as Solution Items

slnx add file Directory.Packages.props

slnx list files

slnx list all

slnx remove file Directory.Packages.props

This feature is now part of the below release:
VijayAnand.Slnx - v0.3.0


[NT-1371] Add-on Reward Selection and Continue Button

📲 What
Adds the continue CTA button to RewardAddOnSelectionViewController.
🤔 Why
This button includes messaging that surfaces the total quantity of selected add-ons and allows backers to skip the selection of add-ons altogether.
Note: Navigation via the continue button will be in an upcoming PR.
🛠 How
Added the functionality to track selected add-on rewards along with their respective selected quantities. This will be needed for upcoming work where we will pass these values through to PledgeViewController in order to create backings with add-ons.
👀 See

Before 🐛
After 🦋
Selected Add-Ons ➕

♿ Accessibility

[X] Tap targets use minimum of 44x44 pts dimensions

✅ Acceptance criteria

[ ] Navigate to the add-on selection view. Observe that increasing/decreasing selections updates the title of the continue button.
[ ] Scrolling up and down should not affect the selections.

Note: When selecting only 1 add-on the button title currently incorrectly has a pluralized title. This will correct itself when translations are in.

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: Danger


🔥 Extract CLI to new oauth-tty gem

backwards compatible

Codecov Report

Merging #275 (6c2e65f) into main (ba94eac) will decrease coverage by 0.35%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #275      +/-   ##
==========================================
- Coverage   79.07%   78.71%   -0.36%
==========================================
  Files          47       40       -7
  Lines        1405     1156     -249
==========================================
- Hits         1111      910     -201
+ Misses        294      246      -48

Impacted Files
Coverage Δ

lib/oauth/request_proxy/base.rb
83.33% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[2.4.0] [npm] Unexpected token error when running in dev

Version
v2.4.0
Reproduction link
https://i-cannot-share-private-repos.com/
Steps to reproduce

Upgrade a codebase to Nuxt 2.4.0.
Run nuxt to build for dev.

What is expected ?
It compiles and builds the web site.
What is actually happening?
It throws an error:
ERROR  in ./.nuxt/router.js                                                                         friendly-errors 12:33:55

Module parse failed: Unexpected token (9:24)                                                         friendly-errors 12:33:55
You may need an appropriate loader to handle this file type.
|
| var _c67eeace = function _c67eeace() {
>   return interopDefault(import('../pages/about-us.vue'
|   /* webpackChunkName: "pages/about-us" */
|   ));
                                                                                friendly-errors 12:33:55
 @ ./.nuxt/index.js 8:0-43 64:19-31
 @ ./.nuxt/client.js
 @ multi eventsource-polyfill webpack-hot-middleware/client?reload=true&timeout=30000&ansiColors=&overlayStyles=&name=client&path=/__webpack_hmr/client ./.nuxt/client.js

Additional comments?
All I did was upgrade using npm install -D<EMAIL_ADDRESS>to get the latest version. Not sure if there are other changes I need to make (nothing was mentioned in the release notes).

This bug report is available on Nuxt community (#c8553)

@joeyzone You are a lifesaver! None of the previous steps worked for me either.

happy to help you.


Is there a way to delete this module completely?

Hey. I am moving my object recognition to a new AGX Xavier and currently don't need it in my Jetson nano. Is there a way to entirely delete this from my nano?

Hi @venugopalreddt, yes you can delete the following paths:

/usr/local/lib/libjetson-inference.so
/usr/local/lib/libjetson-utils.so
/usr/lib/python3.6/dist-packages/Jetson
/usr/lib/python3.6/dist-packages/jetson*
/usr/local/share/jetson-*
the related files under /usr/local/bin
the folder you clone the jetson-inference repo to


Suppress unsupported port name and missing containerPort with 1.3 sidecar

Resolves https://github.com/istio/istio/issues/17017

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

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio
5031a67a9d3919958cd7e5229cc0980bb5359a24
link
/test pilot-multicluster-e2e_istio

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

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

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio
ef53d13b0a97a9e39e1668fc888a8d78f8d58098
link
/test pilot-multicluster-e2e_istio

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

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

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio
ef53d13b0a97a9e39e1668fc888a8d78f8d58098
link
/test pilot-multicluster-e2e_istio

integ-mixer-k8s-tests_istio
ef53d13b0a97a9e39e1668fc888a8d78f8d58098
link
/test integ-mixer-k8s-tests_istio

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

@ayj @howardjohn Now uses standard Pilot methods for parsing version string.  New tests added for cases of pre-1.3, 1.3, with and without container Port and node port name.

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

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
7065d708395c8dffd3b9e98e1f8894ded1a86d01
link
/test integ-new-install-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
7065d708395c8dffd3b9e98e1f8894ded1a86d01
link
/test integ-new-install-k8s-tests_istio

integ-mixer-k8s-tests_istio
7065d708395c8dffd3b9e98e1f8894ded1a86d01
link
/test integ-mixer-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
7065d708395c8dffd3b9e98e1f8894ded1a86d01
link
/test integ-new-install-k8s-tests_istio

integ-mixer-k8s-tests_istio
7065d708395c8dffd3b9e98e1f8894ded1a86d01
link
/test integ-mixer-k8s-tests_istio

pilot-multicluster-e2e_istio
7065d708395c8dffd3b9e98e1f8894ded1a86d01
link
/test pilot-multicluster-e2e_istio

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

/retest

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

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
7065d708395c8dffd3b9e98e1f8894ded1a86d01
link
/test integ-mixer-k8s-tests_istio

pilot-multicluster-e2e_istio
7065d708395c8dffd3b9e98e1f8894ded1a86d01
link
/test pilot-multicluster-e2e_istio

integ-new-install-k8s-tests_istio
7065d708395c8dffd3b9e98e1f8894ded1a86d01
link
/test integ-new-install-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
f9206bc0732b65c203d1b0afb5c2be91938c575c
link
/test integ-new-install-k8s-tests_istio

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

/test integ-new-install-k8s-tests_istio

@ayj I have made the requested changes.  Can you re-review?

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

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
f9206bc0732b65c203d1b0afb5c2be91938c575c
link
/test integ-new-install-k8s-tests_istio

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

In response to a cherrypick label: new pull request created: #17086


[deprecation] com.google.firebase.iid FirebaseInstanceIdService

Launching lib/main.dart on Android SDK built for x86 in debug mode...
Initializing gradle...
Resolving dependencies...
Gradle task 'assembleStagDebug'...
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)

I don't actually see FirebaseInstanceIdService in this issue. But anyway, the deprecation warnings in these logs should be resolved with flutter/plugins#1885

@chenyang88
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/400. Any further collaboration will be done there.


Should tsc file.jsbuild a file with the "compilerOptions" in TypeScript's config. Or should it compile a file and ignore the config?

With Node v11.6.0, and TSC, 3.2.2, I am getting
node_modules/rxjs/internal/Observable.d.ts:82:59 - error TS2585: 'Promise' only refers to a type, but is being used as a value here. Do you need to change your target library? Try changing the `lib` compiler option to es2015 or later.

82     toPromise<T>(this: Observable<T>, PromiseCtor: typeof Promise): Promise<T>;
                                                             ~~~~~~~

Found 1 error.

When I run
type P = typeof Promise;

Using @types/node
This is a bug push up from rxjs https://github.com/ReactiveX/rxjs/issues/4448
You can see the issue documented at https://stackoverflow.com/questions/54014405/ts2585-promise-only-refers-to-a-type-but-is-being-used-as-a-value-here

The error message says you should be targeting lib: "es2015”.  Are you?  Note that lib and target are distinct because of polyfills (you can polyfill builtins but not syntax)

I have a sample repo with it, in that repo i'm doing es2018 for lib, but you can try es2015 same thing.

Just a hunch, have you tried using lowercase for es2018?  I know the docs show uppercase but I think that might be a mistake as I’ve always seen it lowercase in practice.  Otherwise I have no clue what’s wrong here, it seems bizarre.

It is lower case, no joy. It's also confirmed by the rxjs guys and the stackoverflow commenter. Nothing that uses promises works on node 11

So I tried to reproduce this using the exact tsconfig, dependencies, and sample code as in the SO question... and it seems to work fine on my end.  Node.js version is 11.6.0.
npm install typescript
npm install rxjs
npm install @types/node
npm install ts-node

D:\temp>npx tsc

D:\temp>type main.js
import { range } from 'rxjs';
import { map, filter } from 'rxjs/operators';
range(1, 200).pipe(filter(x => x % 2 === 1), map(x => x + x)).subscribe(x => console.log(x));

Did you pull down my repository run npm install and then try to tsc the file?

Yeah, that was before I tested it - that was just stating I understood why you mentioned the node version.

I don't know what else to say, I got the prob. Guy on SO and on RXJS question got the prob. Repo is simple works with the latest version of all tools. It's giving that error on running tsc on my box (running Linux).

This is the line that's problematic for you, this is working?
type P = typeof Promise;

It's the same thing - tsc by itself requires typescript installed globally, npx is when it's installed locally (in node_modules).

No idea, all I know is it's erroring with me and I'm not using any special layer so I'm trying to keep it simple and figure out why it's not erroring for you, and I'm thinking your npx is doing something.

tsc runme.tsc

Nope, here's the exact issue - you're telling tsc to transpile a single file.  In that case it ignores the tsconfig.json and just transpiles the file in a vacuum, using all defaults for the tsconfig fields.  Since there is no ///<reference> tag in the source for the es2015 you get the Promise error.

What you want to do is just run tsc.  You can include/exclude files as necessary by specifying them in the tsconfig (which is your project file).

This behavior, by the way, is documented:
https://www.typescriptlang.org/docs/handbook/tsconfig-json.html

When input files are specified on the command line, tsconfig.json files are ignored.

Nope, here's the exact issue - you're telling tsc to transpile a single file. In that case it ignores the tsconfig.json and just transpiles the file in a vacuum, using all defaults for the tsconfig fields. Since there is no /// tag in the source for the es2015 lib you get the Promise error.

Wow, even if documented that's extremely counter intuitive. I can't think of any program that ignores the configuration file when given an argument that isn't explicitly either conflicting with the configuration file, or demanding to override it. That's not a good user interface at all.

The use case here being

that a project needs Typescript so they install it.
they run tsc file.ts which they believe runs Typescript on the file.
they get an error
They google the error
The error is remedied by adding something to their typescript config.
They do that and run tsc file.ts again and get the same error

At the absolute least I would expect tsc to be verbose by default and tell us it's ignoring the configuartion file which specifies the values of lib needed.

It makes sense to me at least - you either tell it to compile a whole project file, or you pass one or more source files and specify the options on the command line.  Everything you can specify in tsconfig.json has a corresponding command-line option.
It would be probably be bad if it used the tsconfig when specifying files on the command line - since then if you used tsc in, say, a shell script, the behavior of the script would change depending on whether the CWD contained a tsconfig.

Essentially the tsconfig is a “build script” - you tell tsc to use that instead of specifying everything you want to do on the command line.  It’s not a “compiler preferences” file (admittedly the naming of “tsconfig” is a bit confusing in that regard), it’s a self-contained project in itself, like what .vcproj is for MSVC.

Basically: think of tsconfig.json as a makefile, and tsc as a make tool + compiler in one.

since then if you used tsc in, say, a shell script, the behavior of the script would change depending on whether the CWD contained a tsconfig.

Isn't that how everything works though?

make reads .Makefile in the current directory
npm reads package.json in the current directory
git reads .gitignore in the current directory

None of them forget about their config file when you provide an option. They simply override that option and use the config file to create the execution environment for the command. I understand what you're talking about but this is the only utility that works in this fashion -- where providing an argument means it forgets about the config file.
I want the config file to configure TSC for the project. Not to specify the exact item i'm wanting to compile.

Let me make it clear: What you’re essentially asking for is analogous to wanting gcc to honor options in a makefile even when invoked directly.  It just so happens that tsc combines these two functions into one program.

What you may be able to do is (not tested):
tsc --project ./tsconfig.json runme.ts

Let me make it clear: What you’re essentially asking for is analogous to wanting gcc to honor options in a makefile even when invoked directly. It just so happens that tsc combines these two functions into one program.

Not exactly, because GCC and make are separate; there is a distinction there so I would never expect gcc to accept a configuration file anyway. But tsc does with the --project command you've provided which makes it similar to make, and npm, and git.
 It doesn't forget it and act like compiler. It just builds instead baz. And it does it with the CFLAGS. The same applies btw if you want to run one specific rule or compile one file outside. For example if you run make foo.c inside of a build directory it will use the Makefile to build that one file.

Does it seem intuitive to you to say that the default for --project is ./tsconfig.json in all instances except when you provide it arguments? In which case if you want to use tsconfig.json you have to manually supply it?

Using the above analogy:
tsc file.ts is gcc.
tsc --project is make.
It just so happens that, for convenience, the specific case of tsc with no arguments implies --project.

I understand how things are, now that you've explained them and did immediately on my first response here. I just find that entirely unintuitive and I imagine I'm in the majority here. You've severed tsc into two modes, neither of which are apparent to the user and used those two modes to justify a different user interface. I wasn't aware that I was supposed to

think of tsc file.ts as a compiler
tsc as a make system
the file ./tsconfig.json as a default configuration for the make system, but also an acceptable and optional configuration file for the compiler environment via --project
think of tsc file.ts as an invocation of the compiler, rather than tsc file.ts as being a directive to build the file with the configuration file.

I'll just leave it off with this, because I'm honestly just trying to provide some guidance to build a better system. Ask some people who do NOT know the default behavior this question

"If tsc builds a project by reading from tsconfig.json, would you expect tsc file.ts to read from tsconfig.json to build that file with the configuration in tsconfig.json, or to ignore tsconfig.json and compile the file?

I’ll agree with you that the “project builder” should probably be a separate tool (tsmake or something), but practically speaking, since I assume it was a conscious design decision not to have two distinct tools, how would you make tsc fully scriptable like a command line compiler (without the risk of picking up stray config files) but still get the make-like functionality?  Given those constraints, I would probably set up things up the same way.

Wouldn't you want to follow the lead of most all the other tools (eslint, babel, etc) and have an explicit CLI opt-out for avoiding the config file? In other words, "gcc" usage is nowhere near the common case, and seems surprising to most users, so it seems like a poor choice of default.

Would you consider changing the title of the issue to better reflect the ongoing conversation, to provide a better summary and be more convenient to find? For an example, “Inconsistent tsc behavior with and without file parameters”. @EvanCarroll @weswigham

Another use case: we have a pre-commit hook which runs tsc for all changed files, and as soon we can't mix --project with files list we wrote a code to convert compilerOptions to CLI args. Everything works fine until today when we want to use paths compiler option, which cannot be passed via CLI 😞
Even without implicit using tsconfig.json for compiler options why we can't use --project arg and files list together?

Thanks for your help all. Problem solved here.

@DanielRosenwasser @RyanCavanaugh It is very disappointing this hasn't been taken further into consideration. This is how 98% of javascript developers expect tsc to behave and would make tsc consistent with every other node tool out there.

Please reopen; nonhumans closing issues is exceedingly user-hostile.

Allowing to override tsconfig.json by passing a file path with tsc --noEmit -p tsconfig.json would be really useful and would avoid having multiple config files. Please reopen. Thank you!

Allowing to override tsconfig.json by passing a file path with tsc --noEmit -p tsconfig.json would be really useful and would avoid having multiple config files. Please reopen. Thank you!

This is already supported!

Please reopen; nonhumans closing issues is exceedingly user-hostile.

I will close this myself to help.

This is the intended behavior because we don't want to break thousands of msbuild-based compilations where people are using .csproj settings for one compilation and tsconfig.json for something else. Even issuing a warning when a tsconfig.json is present has the potential to break these builds because people might have warnings-as-errors turned on.

people are using .csproj settings for one compilation and tsconfig.json for something else

You can add --no-project flag for them (it's joke, don't bear on me 🙂).

Even issuing a warning when a tsconfig.json is present has the potential to break these builds because people might have warnings-as-errors turned on.

What about allowing to pass a list of files along with --project to override files to compile? It seems that it shouldn't break case you've described above.
Also, what's about compiler options which cannot be passed via CLI such paths (see https://github.com/microsoft/TypeScript/issues/29241#issuecomment-459789340)?
@RyanCavanaugh

What about allowing to pass a list of files along with --project to override files to compile?

See also #27379. I think there's also another issue where people expect to be able to augment the file list in this manner.

Also, what's about compiler options which cannot be passed via CLI

I think allowing some way of specifying additional tsconfig files (probably in a "config only" mode) would be a very reasonable suggestion. I know some teams are effectively doing this by auto-generating tsconfig files in their build scripts; it'd be nice to make that kind of automation unnecessary.

What about allowing to pass a list of files along with --project to override files to compile? It seems that it shouldn't break case you've described above.
Also, what's about compiler options which cannot be passed via CLI such paths (see #29241 (comment))?

This is exactly what I was trying to do and it doesn't work for me. I will try the versions of a new update if you're saying this is supported already.


Add email anonymizer option in case is needed for GDPR

Since rsyslog had Apache License, Version 2.0 I put that too, not an expert on licenses but since is a modification of the original samples I think it should be there.

Hello Sergio,
thank you so much for this commit. I've looked it over and -- with your permission -- I would like to modify it a bit.
For example, the regexp for emails is not OK, as it will not catch all valid email addresses - the possible list is much wider.
I'd also like to limit the number of new environments added (as we already have several) and see if there's a better way to modify rsyslog.conf.
I'll leave the PR open but will pull your changes into a separate branch.

sure!
I think I had a very log regexp for emails long ago but could not find int (it was several lines).

OO, so this is the updated branch: https://github.com/bokysan/docker-postfix/pull/94.
Your comments are welcome.

Nice!, I've taken a fast look and looks good, there is even a bats test.


chore: bdd-spring-1576802103 to 0.0.1

chore: Promote bdd-spring-1576802103 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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


[TRI-1203] OpenAI background calls should use backgroundFetch without an extra subtask

Currently there's a nested subtask that actually does the fetch call. This should be changed so it does just the backgroundFetch call.
Note, this cannot be done until the Airtable PR is merged #9.
TRI-1203

This was cancelled because we should make subtask errors bubble up to parent tasks instead: #159


hssi: 100G: revert recent changes back to a known good config

Coverage increased (+0.01%) to 60.874% when pulling d2049a5382d255e00b3c0641006970653e14249f on tswhison/hssi_fix into<PHONE_NUMBER>49915d7497952ed7a69b55749b6575 on master.


[Teaser] Add support for multiple call to action (CTA)

Added the implementation for Title Types
Removed the "Don't add links to description"
Created unit tests for Title Types
Updated some unit tests
Implemented the exporter for CTAs

@vladbailescu, @andreeadracea - I made some improvements to the dialog labels / descriptions in https://github.com/Adobe-Marketing-Cloud/aem-core-wcm-components/pull/179/commits/29a4d61805cc734b324bd03f3833c6316b83d5ec

@richardhand That looks neat but it's a far stretch from what we can build at the moment. Also, no more feature creep please! ;)


Error while starting Settings Sync: No authentication provider 'microsoft' is currently registered.

VSCode Version: 1.49.0
OS Version: win10 1909

Steps to Reproduce:

at first, sign in and start syncing, it works fine
after changing password  of Microsoft account，error message shows up when I start syncing.

same issue: https://github.com/microsoft/vscode/issues/106321

Does this issue occur when all extensions are disabled?: Yes/No

Closing as a duplicate of https://github.com/microsoft/vscode/issues/106321


fixes bug 1317435 - reset cached on vidly cdn domains

Coverage increased (+0.03%) to 85.754% when pulling 566b748d8b4811a26bb1d61e1885bdcea2e5ab58 on peterbe:bug-1317435-reset-cached-on-vidly-cdn-domains into 244762a7acbf820174b4a21ca3c2e360ffbe4660 on mozilla:master.


Snippets dont work in VSC

Hi.
I have Mac OS X 10.14 and VSC 1.27.1 and snippets are not working.

sorry for the delay. I have not tested on Mac. Can you please post the error message which you get.

No error message. After install and restart VSC,VSC does not know any context with mui-modal-simple or something else.

I have samo new info. When I typing mui in js,ts,jsx,tsx file does not work.
But I have Quoka new js file with testing some code and in this file mui work, but anywhere not.

I found the issue. It is because vscode takes a considerable amount of time for loading the snippets.
You can follow the below steps

If you find "scanning" status in the status bar, then wait for that to complete. check the attached image

The other option is find the keyword by checking the "details" tab of the extension and type the keyword and press tab. Check the attached image.
eg., type "mui-badges"  without quotes and press tab to get the snippets for the badges


The method does not work correctly, the background is still not clickable.

Environment

Platforms

Versions

Android:
iOS:
react-native-modal:
react-native:
react:

Description

Reproducible Demo

Hello! If you can provide more description on the issue then I can take this one. Thanks

Closing as you haven't provided any repro steps let alone a description of the issue you are facing.


Preprocess argument for open_mfdataset and threading lock

Fixes #443
Fixes #444

Going to merge this shortly, unless anyone has a better name for preprocess

I have a question about this preprocess thing. Would it mean now that... basically xray will  load all data in memory? because of the preprocesing step, whereas before... or at least that's what I understood from the documentation, xray would access the data by a need only basis.

Nope, each dataset is loaded lazily when using open_mfdataset (via dask). As long as you stick to xray operations and don't actually manually load data into memory (e.g., by calling .load()) the data is only accessed and transformed by preprocess on a need only basis.

I need to get my head around this... I know that when you do list comprehension, this isn't lazy so basically it goes through the loop and evaluates for each iteration... so I thought that:
    if preprocess is not None:
        datasets = [preprocess(ds) for ds in datasets]

translates to forcing the application of the preprocess function to the dataset effectively loading it in memory... anyway, this is really cool, I'll definitely try it out :+1:


Playback pause on loading track

When connected with librespot the playback halts on loading a track.
I would guess that playback should continue if playing before. For now I have to press play again.
Maybe related to this:
Sometime the play state is wrong on loading iOS app (was closed before). Playback is active but the app shows play button, not pause. Pressing play solves this.
player.enableLoadingState is set so false for me.

Unfortunately not solved.
Do you need a stacktrace?

Yup, it should definitely start playing if it's not the first song to be loaded when connected, unless otherwise specified by the client.

Hmm okay.
Here is my stacktrace.
https://pastebin.com/RVRMhr9v
I start playback on my iPhone and then connected to librespot: playback halts on loading the first song.
While connected I could change between playlists/albums while playing.
Is it designed like this?
I think this was possible in one of the previous versions.

I had it in mind that way, but I realized it doesn't make much sense.

Wonderful.
Now it works like I would expect.
Thanks!


MM-21247 - Adding tooltip for plugins button

Summary
MM-21247 - Adding tooltip for plugins button
Ticket Link
https://mattermost.atlassian.net/browse/MM-21247

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-4818.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

@asaadmahmood Looks like this would be a good candidate to include cypress E2E tests. Could that be added to this PR so both can be approved together?

@prapti Not sure to include cypress test, we may need another dev to do that.

Test server destroyed


VSCode Extension 2.0

Based on PR #12 by @umutdural:

This pull request adds the initial version of the new VSCode extension that communicates with a server version of Caesar which can continuously verify files through the extension without using the CLI. The Caesar server also serves as a language server for the HeyVL ( which allows the display of HeyVL diagnostics in the editor).
The extension initially supports the verification of files with a Caesar: Verify command or it can verify files automatically on save.
User Interface:
Gutter Icons: Based on the verification result (Verified,Failed,Unknown), appropriate icons are displayed next to each (co)proc in the gutter.
Status Bar: A status bar displays the status of the server.
Inline Ghost Text for computed WP/WLP/ERT: Before each instruction if the line above is empty, the expectation of the program (w.r.t. the calculus chosen) after that instruction will be displayed as a ghost text (similar to comments).

All of the above functionalities can be toggled from the settings in VSCode.

Thanks @umutdural!


Current day not displaying correctly.

Could you figure out why the current day isn't showing correctly on the page?

Uncaught ReferenceError: require is not defined
at HTMLDocument. (script.js:3:17)
at j (jquery.min.js:2:29999)
at k (jquery.min.js:2:30313)
This would suggest the it has something to do with the local nodejs instance. Need to relook at the documentation for dayjs

FIxed it by removing Removed const dayjs = require('dayjs')


Inconsistency between dts status and Kconfig

Describe the bug
In the dts the systick is disabled, however, it's enabled via Kconfig options.
I'm not changing the systick status in my board dts. The dts systick status is taken from armv7-m.dtsi, and it appears as is in my build/zephyr/zephyr.dts file:
systick: timer@e000e010 {
			compatible = "arm,armv7m-systick";
			reg = < 0xe000e010 0x10 >;
			status = "disabled";

However,  CORTEX_M_SYSTICK is enabled by default because CPU_CORTEX_M_HAS_SYSTICK is also enabled. So this would mean that the SysTick is indeed enabled.
To Reproduce
I'm building a custom board, but any STM32L4 board should produce same results.
Expected behavior
I would imagine that for SysTick to be effectively enabled, it would have to be first enabled in the dts.
Impact
None so far.
Environment (please complete the following information):

OS: Linux
Toolchain (GCC, J-link)
Commit SHA: 6e8775ff84

@ioannisg I'm guessing this is just because CONFIG_CORTEX_M_SYSTICK does not depend on the node being enabled, right?
Seems like we could just set it to "okay" and add the appropriate Kconfig dependency. The driver Kconfig is default n so it wouldn't affect nRF as far as I can see.
Am I missing something?

@mbolivar-nordic , does it make sense to enable it directly at the armv7-m.dtsi level? For STM32 the LPTIM can be used as a Kernel tick, then it would have to be disabled, no?

@mbolivar CONFIG_CORTEX_M_SYSTICK indicates that the system timer is based on the SysTick.

Seems like we could just set it to "okay" in armv7-m.dtsi and add the appropriate Kconfig dependency. The driver Kconfig is default n so it wouldn't affect nRF as far as I can see.

What does it "mean" the SysTick having status "okay"? Does this mean the timer driver is actually used? If so, setting it as "okay" gives the wrong signal.

@mbolivar CONFIG_CORTEX_M_SYSTICK indicates that the system timer is based on the SysTick.

Yep, for sure.

What does it "mean" the SysTick having status "okay"? Does this mean the timer driver is actually used? If so, setting it as "okay" gives the wrong signal.

It just means the hardware is available for use. In general we're moving towards drivers being automatically enabled if the subsystem is turned on and the right devicetree nodes have status "okay".

In general we're moving towards drivers being automatically enabled if the subsystem is turned on and the right devicetree nodes have status "okay".

That's fair.

Seems like we could just set it to "okay" in armv7-m.dtsi and add the appropriate Kconfig dependency.

@mbolivar-nordic what would be the appropriate Kconfig dependency? You mean something like:
config CORTEX_M_SYSTICK
    bool
    depends on "some DTS-macro indicating it is "status okay"

??

depends on "some DTS-macro indicating it is "status okay"

Yep. I've got a PR adding some potential ones here if the existing kconfigfunctions aren't sufficient:
https://github.com/zephyrproject-rtos/zephyr/pull/24794

Aha, I misread this. Actually, it's meant to be default y if $(dt_<whatever>_enabled,<foo>), not depends on.

Aha, I misread this. Actually, it's meant to be default y if $(dt_<whatever>_enabled,<foo>), not depends on.

Then this is not so straightforward. That's because the SysTick DTS node is part of the SoC definition only, while the config CORTEX_M_SYSTICK is enabled at board level.
For your proposal to work we need to be setting the SysTick node to status = okay at the board DTS, for all boards (and only those boards) that are supposed to work with the SysTick.
@QSQCaito has a relevant comment about this.

In general we're moving towards drivers being automatically enabled if the subsystem is turned on and the right devicetree nodes have status "okay".

I'll wait until you make this work for Nordic and the RTC driver; then I 'll revisit this issue.

For your proposal to work we need to be setting the SysTick node to status = okay at the board DTS, for all boards (and only those boards) that are supposed to work with the SysTick.

Is that true?
Why can't we set a default to status 'okay' on the SoC level where the SoC expects most users to use systick, and then set it to status 'disabled' on a board specific basis if required?


URL item is not fully displayed

version 2.0.3

version 2.0.4

version 2.0.3  tabLayout + viewpager2 .    It can be used in version 2.0.4 ？

fixed in version 2.0.5


MySQL capture failing for mysql2 pool queries with promises

We're looking to switch our existing code that uses mysql2 to use X-Ray instrumentation. We have hit issues with using either the parent mysql2 module or mysql2/promise.
Our code is essentially one of these two scenarios (both fail):
With parent mysql2 module and .promise()
const rawMysql = require('mysql2');
const captureMySQL = require('aws-xray-sdk-mysql');

(async function() {
  const mysql = captureMySQL(rawMysql);

  const pool = mysql.createPool({
      // ... connection setting ...
  }).promise();

  await pool.query("SELECT ...");
})();

This fails with:
Error: You have tried to call .then(), .catch(), or invoked await on the result of query that is not a promise, which is a programming error

at mysql2/lib/commands/query.js:41:11 because the mysql2 Query class has a stubbed then method that throws this error.
In captureOperation in mysql_p.js the code tries to detect whether the command object is promise or event emitter based and this stubbed method confuses it into thinking it's actually a promise.
I'm not sure what can be done about this since there's no reliably better way to detect a promise.
With the mysql2/promise module
const rawMysql = require('mysql2/promise');
const captureMySQL = require('aws-xray-sdk-mysql');

(async function() {
  const mysql = captureMySQL(rawMysql);

  const pool = mysql.createPool({
      // ... connection setting ...
  });

  await pool.query("SELECT ...");
})();

This fails for a different reason in captureOperation where it tries to grab the connection config object using:
var config = this.config.connectionConfig || this.config

This is because the mysql2/promise module returns a PromisePool instance which delegates to the actual pool object holding the connection config object and there is no config property on the base object.
This does seem like something that could be addressed in the operation patching code by detecting and handling this scenario. Something like:
var config = this.pool ?
        this.pool.config.connectionConfig :
        (this.config.connectionConfig || this.config);

Has anyone else experienced this issue? I noticed that there is some support for mysql2 already so I'm wary that I'm doing something wrong having not used either library before. Alternatively it might be that it's our use of the pool object that is not covered by existing scenarios?

For the moment this workaround of patching the pool object works for me:
function patchPool(promisePool) {
    return {
        ...promisePool,
        config: promisePool.pool.config
    }
}

const pool = patchPool(mysql.createPool({
      // .. connection settings ...
}));

Hi @simoncollins
Apologies for missing on this issue. It seems like the usage of pool with promise may not be fully supported in the SDK, although there is support for mysql2. Thanks for providing the repro code and details. Allow me some time to debug it locally to understand better and I'll provide an update soon.

No worries, thanks @srprash - for now the workaround mentioned above is working for us so all good.

Bump to make sure it doesn't go stale.

Hi! I made a PR (#501) that should fix the first problem scenario you described (or at least prevent the error you got)


ability to set the alt text of images of Card components for the card

Summary
Would like the ability to set the alt text of images of Card components for the card.
Basic example
If you use the card from https://flowbite-svelte.com/components/card (code below) you're not able to set the alt tag.
Motivation
The alt tag will allow increased accessibility for cards using flow bite. You're able to manually add a div below the top of the card but it would be nice to have it included.

Duplication #398
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#attr-alt

If it's a duplicate we should close this.


API: Move to "/-/" as part of the build

sigh, to best support some exotic security configurations (BS "work" firewalls), move the contents of api.ldjam.com (and others) to the dash folder (public-ludumdare.com/-/). Do this as a build step though.
That also means the originals should move back in to /src/shrub/. That's not a bad change, as all the related code is there anyway.
It also-also means what's included in a subsite (jammer.bio) can be a subset of the full API (no auth required).
Paths are going to be weird though. :stuck_out_tongue:

/vx/ (experimental) and /v1/ (stable) structuring should be kept.

No, this can't be done.
After watching the server get flooded live, CloudFlare becomes unreliable for anything that isn't simple.
The API domains must not be hidden behind cloudflare.


getting issue while calling GoogleFit.authorize(options)

AUTH_DENIED cannot read propery of isAuthorized of undefined.

AUTH_DENIED cannot read propery of isAuthorized of undefined. please tell steps to implement authorization with google fit

AUTH_DENIED cannot read propery of isAuthorized of undefined. please tell steps to implement authorization with google fit

https://github.com/StasDoskalenko/react-native-google-fit/blob/master/docs/INSTALLATION.md#demo-walkthrough
This link should help you out now


conda support

Any chance that i can use anaconda to resolve trains dependency ?

@galprz do you mean let conda install the requirements for the trains package ?
or add trains to the conda environment.yml ?

If you want to make sure conda installs the requirements, then before installing TRAINS, you need to manually install the requirements:

git clone https://github.com/allegroai/trains.git
cd trains
conda install --yes --file requirements.txt

If you need to add TRAINS to the conda environment.yml, then add the following to the yaml file:

dependencies:
  - pip:
    - trains

Full details on combining pip/conda here:
https://conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#create-env-file-manually

tnx


would you pls tell about render performance ?

compare to tray C++ version

It's not quite an equal comparison since I've improved some implementation details in the Rust version, and have changed some other things. I can run some small benchmark scenes though and compare them.

Would you please commit benchmark code


CLOUD-556 Fix vars after update

Test name
Status

storage
passed

scaling
passed

init-deploy
passed

big-data
failed

recreate
passed

scaling-proxysql
passed

self-healing
passed

limits
passed

monitoring
failed

upgrade
failed

restore-to-encrypted-cluster
failed

monitoring-2-0
passed

self-healing-advanced
passed

affinity
passed

demand-backup
passed

operator-self-healing
passed

one-pod
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

scheduled-backup
passed

demand-backup-encrypted-with-tls
failed

upgrade-consistency
failed

Test name
Status

scaling
passed

scaling-proxysql
passed

upgrade
passed

storage
passed

big-data
failed

self-healing
passed

self-healing-advanced
passed

recreate
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

limits
passed

operator-self-healing
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

demand-backup
passed

scheduled-backup
passed

demand-backup-encrypted-with-tls
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

upgrade-consistency
passed

security-context
passed

PXC operator docker - perconalab/percona-xtradb-cluster-operator:PR-448-c0841f58

Test name
Status

scaling
passed

scaling-proxysql
passed

upgrade
passed

big-data
passed

storage
passed

upgrade-consistency
passed

self-healing
passed

security-context
passed

self-healing-advanced
passed

operator-self-healing
passed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
passed

demand-backup-encrypted-with-tls
passed


Add Creodias in docker image name

https://github.com/Open-EO/openeo-geotrellis-kubernetes/blob/29d4600ff46104da69500e829e38860ce9b56178/docker/Debian/Jenkinsfile#L6-L8
This docker image is called openeo-geotrellis, but it is for Creodias specifically, e.g.:
https://github.com/Open-EO/openeo-geotrellis-kubernetes/blob/29d4600ff46104da69500e829e38860ce9b56178/docker/Debian/Dockerfile#L34
Shouldn't we give it a name like openeo-geotrellis-creodias to avoid confusion?

This image is now called opene-geotrellis-kube.

I guess you mean openeo-geotrellis-kube  instead of actually opene-geotrellis-kube


Improve hyperparameter sampling in ACS model

The ACS model works well but it explores the posterior distribution of the high-level parameters (the two parameters of the gamma prior common to all bias ratios) very slowly.  Slow mixing of hyperparameters is a common problem in MCMC and basically arises in two ways, both related to the high correlation between parameters and hyperparameters:

In Gibbs sampling, the parameters are sampled randomly from a distribution parametrized by the hyperparameters and the hyperparameters are then re-sampled based on the parameters.  As the number of parameters increases, the law of large numbers washes out statistical fluctuations and tends to pin the hyperparameters to their values from the previous iteration.
In Metropolis-Hastings sampling the large correlations imply that step sizes must be very small lest the rejection rate become too large.

Possible solutions include:

Use variational Bayesian methods to replace sampling with optimization.  Specifically, sample parameters with MCMC but assume a parametric posterior on the hyperparameters and optimize it eg with stochastic gradients.  This will replace random walk exploration of the posterior with consistent (up to sampling noise) movement in the direction of the optimal posterior.
Improve our Gibbs sampling speed and just throw more CPU time at the issue.  The proposed auxiliary variable method in the db_ACS_model_docs branch aims to do this.
Try to model the correlation between parameters and hyperparameters, for example via Metropoolis-Hastings based not on an isotropic proposal distribution but on a Gaussian approximation to the joint conditional around its mode.  If the parameter-hyperparameter Hessian matrix is sparse (it is, and is explicitly invertible by the Sherman-Morrison-Woodbury formula) this is efficient.

I guess that it would take a week to prototype all three options.

After much math and much thought, the front runner is none of the above.  Using the auxiliary variable proposed method in the model docs, the conditionals on the bias ratios (the lambdas) are all gamma.  We can then integrate them out analytically from the joint conditional of the bias ratios and hyperparameters to define a 2D collapsed sampler on the hyperparameters.  The 2D collapsed conditional is well approximated by a Gaussian, which is easy to sample from.  Thus we ought to have very short autocorrelation times for the hyperparameters.
I will proceed to write up this as a new proposed method in the ACS model docs and then prototype in in Python.

Addressed in pull request #198.  Instead of using auxiliary variables, we marginalized out the original variables, leaving only hyperparameters and per-segment parameters, which are then sampled with adaptive Metropolis.
For posterity it is worth noting that if we ever make the model more complicated (eg put it in an HMM, mix it with copy ratio, cluster allele fractions etc) variational Bayes is still perfectly viable and would work nicely with the current marginalizing of latent variables.


Follow bots with Sandboxie

I wanted to make Follow bots with Fedoraware. For Follow bots I use Sandboxie. The problem is that inject a cheat into Follow bots, game freezes, after a while the freeze disappears and in the end nothing is injected.

followbot my ASS!

disgusting

locked because fedoraware followbots is an idea i dont want discussed here


[WIP] Comparing stack traces

Work in progress, not ready yet
Comparing stack traces
To compare stack traces of the matched jobs, you can use the switch --compare-traces. It will generate similar table like with the --compare switch, but instead of Xs, there will be numbers representing stack trace similarity in percentages.
By default, the referential build is the left-most one (or the first), but if you want to change it, you can with --set-referential <jobName:buildNumber> switch.
Example usage: --set-referential "jtreg~tier1-jp17-ojdk17~rpms-el8.x86_64-release.sdk-el8.x86_64.beaker-x11.shenandoah.legacy.lnxagent.jfroff:54"
There is also --cut-trace <head/tail:numberOfCharacters> argument for cutting the test outputs by the numbers specified (to not work with big traces). For example --cut-trace "head:5000" will take a substring of the length 5000 characters from the start of the trace (for EACH test output - it then concats them).

this is ok by me to merge. So depends on you

this is ok by me to merge. So depends on you

Ok, I will merge it.


aws: add volume_type params to allow specify root volume type

Thanks, @libhe no issue found in our nightly test runs, so merge it.


Plugins organization

We have a function called  plugins which is kinda useless. Should we create instead a function for each plugin? Right now it looks disorganized.

Refactor looks great! ❤


latent loss backward problem

Hi,
I notice that the err_g_lat is added to update the generator parameters, however, this loss is acquired when the x_fake is detached. I think it makes no contribution to update the parameters of the generator, can someone explain that?

I have the same question, can anyone could explain?


fixed typo

Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:

[ ] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[ ] Read the contribution guide
[ ] Commands include options for Linux, MacOS, and Windows within codetabs
[ ] New file and folder names are globally unique
[ ] Page references use shortcodes instead of markdown or URL links
[ ] Images use HTML style and have alternative text
[ ] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description

Issue reference

@fleckert,  thanks for your contribution. Can you please sign your commit (DCO check) so we can approve and merge? Thank you.


refactor(android): switch over to PagingData transformations

Should work fine after a5af23e3308c4488aaffd09876687642f0554c1f

Unfortunately switching between transform-using screens causes the data to be reloaded, presumably to
re-apply the transform which is kinda ass :/

Don't think this will ever really work


Change browser name programmatically / run test across multiple browsers in NUnit

Please do not submit this issue.

[X] I understand

This issue is not following the bug template. Please re-file and provide a self-contained reproduction, which we can run locally to reproduce your issue. Thanks for your understanding!

I've been evaluating Playwright.NET with the NUnit test runner, and am curious if there is a way to execute tests across multiple browsers?
Is there any way of running the tests across multiple browsers from within the C# tests? I've been looking at using the TestFixture attribute with the browser names, but there isn't any way (or at least not an obvious way) to set the browser name programmically from within the test.
(I know I can go up a level and run the tests multiple times and pass settings in, but was curious if there was a way of controlling this from within the C#)

We recommend the same browser per the whole test-execution. If you still need a different browser, you can launch it manually: https://playwright.dev/dotnet/docs/api/class-browsertype#browser-type-launch inside your test, using the Playwright class property.

Thank you @mxschmitt for the clarification :).


Access currentData() from constructor when 'args' is specified.

Given this in the calling template
{{#with itemIds=getItemIds}}
    {{> ItemList args onCheckClicked=getOnItemCheckClicked}}
{{/with}}

and this in the ItemList constructor
function ItemListConstructor(args) {
    assert(this.currentData().itemIds, 'Expecting itemIds to be defined');
    ...
}

the assert is throwing an exception.  If I remove the 'args' in the calling template, the assert no longer throws and I am able to get the itemIds value in the constructor.  Before I create a simple example, I wanted to know if this is expected behavior.
In both cases, I'm able to use the itemIds in the ItemView helpers.  The problem I'm having is just with the constructor.

Current data is not available in the constructor. It is only available after the component is created by Blaze, so in onCreated and onRendered. So in the constructor the object is just simple JavaScript object. There is a ticket #62 which is asking to change this behavior. That data or currentData should be simply waiting until the content is rendered. But in your case you are not using it in a reactive context, so currentData would still return null for you in the constructor.


Fix crate build on docs.rs

Use dynamic code-gen to build-around non-availabiltiy of some packages.

[X] I agree to follow the project's code of conduct.
[X] I added an entry to CHANGES.md if knowledge of this change could be valuable to users.

The documenation assumed GDAL 3.2 (the sys versions do not matter as cargo doc is cool enough to not link).  With this PR, this is now the latest (3.5), and can be upgraded by changing gdal-sys/build.rs.  Should be obvious to our-future-selves. :crossed_fingers:

Do we still need
[package.metadata.docs.rs]
rustc-args = ["--cfg", "docsrs"]

in Cargo.toml?

Closes #268

can we merge this?

I'm a bit behind on this, but do we know why the current approach isn't working? Was it a docs.rs bug?

@jdroenner  Yes, we should merge this and closes PR #241 if it builds on docs.rs.
@lnicola quick summary:  we rely on some cfg attributes to be set by docs.rs but they do not set it;  they only set an env. var. afaiu.  This PR gets around this by just using the env. variable directly.  The cond. compiling was required to prevent compiler from trying to look for gdal on the docs.rs machine.  Instead, we just dynamically create a wrapper function from the gdal-sys/build.rs that will either use libgdal to find the gdal version, or on docs.rs directly return the latest version that we've hardcoded.
I've checked this locally on the docs.rs docker images and it works.

Did we try to ask someone working on docs.rs why the cfg is no longer set? I'm surprised there aren't more crates running into this, and the workaround is TBH quite complex.

Well it's been open for a while (ref. https://github.com/georust/gdal/issues/268) and affects all crates depending on gdal.  We could always un-complicate it if docs.rs supports a cfg attribute.

Yeah, so I just re-discovered https://github.com/rust-lang/docs.rs/issues/1580. We might be able to use https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#host-config instead, but it's probably not worth the hassle of an unstable option.
bors d+

bors r+

https://github.com/rust-lang/docs.rs/issues/1580 just got fixed though.

I'm fine with whatever gets docs compiling on publish.


Upgrade to PEGjs 0.10…

…removing our dependency on loophole. (This was the weird eval thing. Newer versions of PEGjs no longer require usage of eval.
Also reintroduced the generated PEGjs file to improve startup time, giving us a second way to avoid eval. In theory we can move pegjs to devDependencies, but for now we can just try to load the compiled version and fall back to generating it manually from the .pegjs file if it isn't present.

Real fast though, what's the purpose of adding eslint as a devDependency? Was that already being used here and I've just missed it?

It probably wasn’t, but likely only because this used to all be CoffeeScript. eslint is a devDependency on the main repo.
The coding styles vary between repos. Older code tends to enforce absence of semicolons, whereas new JS that hasn't been decaffeinated tends to mandate semicolons. At some point we'll want to harmonize all this, so bringing eslint into the repo is an intermediate step.

Yeah I'm not against it at all. Just wondering if it was used much anywhere yet. But that sounds good to me. And totally agree we will need to find out what we prefer, likely setting up some sort of official styleguide, that we could all get behind and enforce via automated tools


Update flattentypes to work on declarations

Actually, this creates another error which I think is related:
  Def:
    Instances:
      base_module_inst0 : base_module
      ctr_module_inst0 : ctr_module
    Connections:
      base_module_inst0.baseIO.in0 <=> self.hier_baseIO_in0
      base_module_inst0.baseIO.out0 <=> self.hier_baseIO_out0
      ctr_module_inst0.ctr <=> self.hier_ctr

ERROR: {hier_module}.base_module_inst0.baseIO_in0 Is not connected

Perhaps the connection is not getting updated.

I added a warning in the flattentypes pass where it use to result in an error. I didn't add one to the instancegraph routine since that would lead to a double warning, perhaps this is okay since that's an internal method?

The original magma test now displays the warning as follows:
❯ pytest tests/test_type/test_tuple.py -k test_nested -s
/Users/lenny/miniconda3/lib/python3.7/site-packages/pysmt/walkers/generic.py:43: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
  if len(nodetypes) == 1 and isinstance(nodetypes[0], collections.Iterable):
===================================================================== test session starts ======================================================================
platform darwin -- Python 3.7.2, pytest-4.2.0, py-1.8.0, pluggy-0.9.0
rootdir: /Users/lenny/repos/magma, inifile: setup.cfg
plugins: parallel-0.0.9, cov-2.6.1, codestyle-1.4.0
collected 6 items / 5 deselected / 1 selected

tests/test_type/test_tuple.py /Users/lenny/repos/coreir/src/binary/coreir.cpp:188 Running Runningvpasses
/Users/lenny/repos/coreir/src/passes/transform/rungenerators.cpp:10 In Run Generators
/Users/lenny/repos/coreir/src/passes/transform/rungenerators.cpp:26 Done running generators
/Users/lenny/repos/coreir/src/passes/transform/flattentypes.cpp:102 Flatten type of generator or module with no definition, assumes definition follows the flatten types scheme, see https://github.com/rdaly525/coreir/issues/800 for more info
{global.base_module}.baseIO Is not a flattened type!
  Type is: {'in0':BitIn, 'out0':Bit}


Pass custom metadata filename to Image/Audio folders

This is a quick fix.
Now it requires to pass data via data_files parameters and include a required metadata file there and pass its filename as metadata_filename parameter.
For example, with the structure like:
data
   images_dir/
      im1.jpg
      im2.jpg
      ...
   metadata_dir/
      meta_file1.jsonl
      meta_file2.jsonl
      ...

to load data with metadata_file1.jsonl do:
ds = load_dataset("imagefolder", data_files=["data/images_dir/**", "data/metadata_dir/meta_file1.jsonl"], metadata_filename="meta_file1.jsonl")

Note that if you have multiple splits, metadata file should be specified in each of them in data_files, smth like:
data_files={
"train": ["data/train/**", "data/metadata_dir/meta_file1.jsonl"],
"test": ["data/train/**", "data/metadata_dir/meta_file1.jsonl"]
}

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

I'm not a big fan of this new param - I find assigning metadata files to splits via the split param cleaner. Also, assuming that the metadata filename is metadata.json/metadata.csv (I don't think we should allow other names), a user can do load_dataset("imagefolder", data_dir="data") to load a dataset with that structure.

@mariosasko  I don't really like this change in it's current state either but passing specific files with data_files also looks not quite user-friendly to me. The idea of providing specific parameter for metadata filename seems natural to me but I don't see a way for implementing it without some ugly changes in load.py (passing the param to factories and creating metadata patterns on the fly). Why don't you like this parameter?
For context: this PR emerged from the case where users wanted to use different metadata files with the same large set of images without copying directories on disk and it's not possible with data_files approach.


Add 'filter' kwarg to Attribute init

Rather than always having to define a filter function, why not add to _make.py
class Attribute(object):
    __slots__ = (
        "name", "default", "validator", "repr", "cmp", "hash", "init",
        "metadata", "type", "converter", "filter"
    )

    def __init__(self, name, default, validator, repr, cmp, hash, init
                 convert=None, metadata=None, type=None, converter=None, filter=False):
        # ...
        bound_setattr("type", type)
        bound_setattr("filter", filter)

and to _funcs.py (asdict for example):
def asdict(inst, recurse=True, filter=None, dict_factory=dict,
           retain_collection_types=False):
    attrs = fields(inst.__class__)
    rv = dict_factory()
    for a in attrs:
        v = getattr(inst, a.name)
        if a.filter:
            continue   # attribute takes precedent
        elif filter is not None and not filter(a, v):
            continue
        # ...

The purpose being to simplify serialization/deserialization to/from JSON or YAML, i.e.  json.dumps(attr.asdict(...))

Conceptually that's wrong though, filtering (or not) is a property of the serialization pipeline, not the actual class itself.
I can see the problem with nested classes though. The solution there is for more intelligent serialization libraries, not more fields in attrs :)

@smcveigh-phunware still a job for the serialization pipelines, not for the class

Yeah that looks like a separation of concerns violation to me.
If you want to define serialization metadata while defining your classes, we have metadata just for that. Then you could define a filter function that works on that data and you have what you want.
Shoehorning a functionality like this into attrs’ core APIs is too invasive and arbitrary.


HttpMaster added to Testing - Querying section

Could you mention that it's Windows only?

Superseded by #14