install kiali.yaml  throw error

kubernetes v1.19.0
istio-1.7.2/samples/addons/kiali.yaml
kubectl apply -f kiali.yaml

Warning: apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
customresourcedefinition.apiextensions.k8s.io/monitoringdashboards.monitoring.kiali.io created
serviceaccount/kiali created
configmap/kiali created
clusterrole.rbac.authorization.k8s.io/kiali-viewer created
clusterrole.rbac.authorization.k8s.io/kiali created
clusterrolebinding.rbac.authorization.k8s.io/kiali created
service/kiali created
deployment.apps/kiali created
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"

Bug description
[ ] Docs
[x] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version --short and helm version if you used Helm)
How was Istio installed?
Environment where bug was observed (cloud vendor, OS, etc)

Warning: apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition

Just wonder how you applied istio CRDs, because istio CRDs are also using apiextensions.k8s.io/v1beta1 API version?

The error above is from Kiali's CRD, from the samples that are linked to in the documentation.

Warning: apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition

Just wonder how you applied istio CRDs, because istio CRDs are also using apiextensions.k8s.io/v1beta1 API version?

this from version 1.7.2  ,
directory:  istio-1.7.2/samples/addons/kiali.yaml

I mean kiali CRD and istio CRDs share the same apiextensions.k8s.io/v1beta1 API version, if the kiali CRD can't be applied into your cluster, then how istio crds are applied?

I also meet the same problem. It caused by the CRD says the version is "monitoring.kiali.io/v1beta1", but the CR require "monitoring.kiali.io/v1alpha1"
CRD:
apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
metadata:
  name: monitoringdashboards.monitoring.kiali.io
spec:
  group: monitoring.kiali.io
  names:
    kind: MonitoringDashboard
    listKind: MonitoringDashboardList
    plural: monitoringdashboards
    singular: monitoringdashboard
  scope: Namespaced
  versions:
  - name: v1alpha1
    served: true
    storage: true

CR: envoy MonitoringDashboard
apiVersion: "monitoring.kiali.io/v1alpha1"         #<<< mismatched
kind: MonitoringDashboard
metadata:
  name: envoy
  labels:
    helm.sh/chart: kiali-server-1.22.0

Warning: apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition

Just wonder how you applied istio CRDs, because istio CRDs are also using apiextensions.k8s.io/v1beta1 API version?

@morvencao I think it's just a deprecation warning for upgrading  apiextensions.k8s.io/v1beta1 to apiextensions.k8s.io/v1  Reverted PR https://github.com/istio/istio/pull/26285
Noticed the same yesterday
https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/27578/integ-operator-controller-tests_istio/8827
@tangbao203 This is reproducible with 1.7.2 but not sure if there is any critical issue with the warnings because the Kiali pod is running.
$ kubectl get pods -n istio-system
NAME                                    READY   STATUS    RESTARTS   AGE
istio-ingressgateway-56b8d79bfc-hh2fl   1/1     Running   0          2m25s
istiod-5d884bcc7-rc5gk                  1/1     Running   0          3m17s
kiali-7d5cb68b45-stfz4                  1/1     Running   0          67s

And I'm able to see the dashboard.
$ istioctl dashboard kiali
http://localhost:20001/kiali

As per the instruction added by @ericvn in this PR https://github.com/istio/istio.io/pull/7976
I tried running the same command again and got the following.
[istio-1.7.2]$ kubectl apply -f samples/addons/kiali.yaml

Warning: apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition

customresourcedefinition.apiextensions.k8s.io/monitoringdashboards.monitoring.kiali.io unchanged
serviceaccount/kiali unchanged
configmap/kiali unchanged
clusterrole.rbac.authorization.k8s.io/kiali-viewer unchanged
clusterrole.rbac.authorization.k8s.io/kiali unchanged
clusterrolebinding.rbac.authorization.k8s.io/kiali unchanged
service/kiali unchanged
deployment.apps/kiali unchanged
monitoringdashboard.monitoring.kiali.io/envoy created
monitoringdashboard.monitoring.kiali.io/go created
monitoringdashboard.monitoring.kiali.io/kiali created
monitoringdashboard.monitoring.kiali.io/micrometer-1.0.6-jvm-pool created
monitoringdashboard.monitoring.kiali.io/micrometer-1.0.6-jvm created
monitoringdashboard.monitoring.kiali.io/micrometer-1.1-jvm created
monitoringdashboard.monitoring.kiali.io/microprofile-1.1 created
monitoringdashboard.monitoring.kiali.io/microprofile-x.y created
monitoringdashboard.monitoring.kiali.io/nodejs created
monitoringdashboard.monitoring.kiali.io/quarkus created
monitoringdashboard.monitoring.kiali.io/springboot-jvm-pool created
monitoringdashboard.monitoring.kiali.io/springboot-jvm created
monitoringdashboard.monitoring.kiali.io/springboot-tomcat created
monitoringdashboard.monitoring.kiali.io/thorntail created
monitoringdashboard.monitoring.kiali.io/tomcat created
monitoringdashboard.monitoring.kiali.io/vertx-client created
monitoringdashboard.monitoring.kiali.io/vertx-eventbus created
monitoringdashboard.monitoring.kiali.io/vertx-jvm created
monitoringdashboard.monitoring.kiali.io/vertx-pool created
monitoringdashboard.monitoring.kiali.io/vertx-server created

I think there are two different issues here. One is the Warning: message which appears when your cluster is running k8s 1.19 (I believe you don't see it on 1.18), and it isn't a Kiali only thing, as you'll see it during a normal Istio install. As far as I can tell, it's a warning, and things work normally.
The second issue is that one must run the Kiali apply twice (for me, that's most of the time). I'm not sure if there is something ordering wise that we can do to get the CRD created before it's used on the first pass.

I think there are two different issues here. One is the Warning: message which appears when your cluster is running k8s 1.19 (I believe you don't see it on 1.18), and it isn't a Kiali only thing, as you'll see it during a normal Istio install. As far as I can tell, it's a warning, and things work normally.

Right, there was some work to update the API version https://github.com/istio/istio/pull/26285 but due to some issues on GKE it was reverted.

I got a similar problem
 k apply -f kiali.yaml
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"

Related https://github.com/istio/istio/issues/27417

This is a duplicate of https://github.com/istio/istio/issues/27417

maybe you can create crd firest .  i had the same error, when i created the crd first , it all is ok

Same issue on EKS.
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T14:58:59Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"18+", GitVersion:"v1.18.9-eks-d1db3c", GitCommit:"d1db3c46e55f95d6a7d3e5578689371318f95ff9", GitTreeState:"clean", BuildDate:"2020-10-20T22:18:07Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

unable to recognize "./samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"

Same issue on EKS.
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T14:58:59Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"18+", GitVersion:"v1.18.9-eks-d1db3c", GitCommit:"d1db3c46e55f95d6a7d3e5578689371318f95ff9", GitTreeState:"clean", BuildDate:"2020-10-20T22:18:07Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

unable to recognize "./samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"

maybe you can create crd firest . i had the same error, when i created the crd first , it all is ok

This worked for me as well.

maybe you can create crd firest . i had the same error, when i created the crd first , it all is ok

This worked for me as well.

istio-1.10.2 on standalone k8s cluster:
.kiali.io/v1alpha1"
unable to recognize "samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring

I try command “kubectl apply -f https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml” twice, the first time it failed, and the 2nd time it is successful, so I think we need to apply CRD first and then wait several seconds, and then apply the left.
$ kubectl apply -f https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml
customresourcedefinition.apiextensions.k8s.io/monitoringdashboards.monitoring.kiali.io created
serviceaccount/kiali created
configmap/kiali created
clusterrole.rbac.authorization.k8s.io/kiali-viewer created
clusterrole.rbac.authorization.k8s.io/kiali created
clusterrolebinding.rbac.authorization.k8s.io/kiali created
role.rbac.authorization.k8s.io/kiali-controlplane created
rolebinding.rbac.authorization.k8s.io/kiali-controlplane created
service/kiali created
deployment.apps/kiali created
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"

# several seconds later, I tried again.
$ kubectl apply -f https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml
customresourcedefinition.apiextensions.k8s.io/monitoringdashboards.monitoring.kiali.io unchanged
serviceaccount/kiali unchanged
configmap/kiali unchanged
clusterrole.rbac.authorization.k8s.io/kiali-viewer unchanged
clusterrole.rbac.authorization.k8s.io/kiali unchanged
clusterrolebinding.rbac.authorization.k8s.io/kiali unchanged
role.rbac.authorization.k8s.io/kiali-controlplane unchanged
rolebinding.rbac.authorization.k8s.io/kiali-controlplane unchanged
service/kiali unchanged
deployment.apps/kiali unchanged
monitoringdashboard.monitoring.kiali.io/envoy created
monitoringdashboard.monitoring.kiali.io/go created
monitoringdashboard.monitoring.kiali.io/kiali created
monitoringdashboard.monitoring.kiali.io/micrometer-1.0.6-jvm-pool created
monitoringdashboard.monitoring.kiali.io/micrometer-1.0.6-jvm created
monitoringdashboard.monitoring.kiali.io/micrometer-1.1-jvm created
monitoringdashboard.monitoring.kiali.io/microprofile-1.1 created
monitoringdashboard.monitoring.kiali.io/microprofile-x.y created
monitoringdashboard.monitoring.kiali.io/nodejs created
monitoringdashboard.monitoring.kiali.io/quarkus created
monitoringdashboard.monitoring.kiali.io/springboot-jvm-pool created
monitoringdashboard.monitoring.kiali.io/springboot-jvm created
monitoringdashboard.monitoring.kiali.io/springboot-tomcat created
monitoringdashboard.monitoring.kiali.io/thorntail created
monitoringdashboard.monitoring.kiali.io/tomcat created
monitoringdashboard.monitoring.kiali.io/vertx-client created
monitoringdashboard.monitoring.kiali.io/vertx-eventbus created
monitoringdashboard.monitoring.kiali.io/vertx-jvm created
monitoringdashboard.monitoring.kiali.io/vertx-pool created
monitoringdashboard.monitoring.kiali.io/vertx-server created

I think on master branch the monitoringdashboard stuff is removed so this
shouldn't be a problem in the near future
On Sun, Jul 11, 2021 at 6:20 PM Peng Tan @.***> wrote:

I try command “kubectl apply -f
https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml”
twice, the first time it failed, and the 2nd time it is successful, so I
think we need to apply CRD first and then wait several seconds, and then
apply the left.
$ kubectl apply -f https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml
customresourcedefinition.apiextensions.k8s.io/monitoringdashboards.monitoring.kiali.io created
serviceaccount/kiali created
configmap/kiali created
clusterrole.rbac.authorization.k8s.io/kiali-viewer created
clusterrole.rbac.authorization.k8s.io/kiali created
clusterrolebinding.rbac.authorization.k8s.io/kiali created
role.rbac.authorization.k8s.io/kiali-controlplane created
rolebinding.rbac.authorization.k8s.io/kiali-controlplane created
service/kiali created
deployment.apps/kiali created
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
several seconds later, I tried again.
$ kubectl apply -f https://raw.githubusercontent.com/istio/istio/release-1.10/samples/addons/kiali.yaml
customresourcedefinition.apiextensions.k8s.io/monitoringdashboards.monitoring.kiali.io unchanged
serviceaccount/kiali unchanged
configmap/kiali unchanged
clusterrole.rbac.authorization.k8s.io/kiali-viewer unchanged
clusterrole.rbac.authorization.k8s.io/kiali unchanged
clusterrolebinding.rbac.authorization.k8s.io/kiali unchanged
role.rbac.authorization.k8s.io/kiali-controlplane unchanged
rolebinding.rbac.authorization.k8s.io/kiali-controlplane unchanged
service/kiali unchanged
deployment.apps/kiali unchanged
monitoringdashboard.monitoring.kiali.io/envoy created
monitoringdashboard.monitoring.kiali.io/go created
monitoringdashboard.monitoring.kiali.io/kiali created
monitoringdashboard.monitoring.kiali.io/micrometer-1.0.6-jvm-pool created
monitoringdashboard.monitoring.kiali.io/micrometer-1.0.6-jvm created
monitoringdashboard.monitoring.kiali.io/micrometer-1.1-jvm created
monitoringdashboard.monitoring.kiali.io/microprofile-1.1 created
monitoringdashboard.monitoring.kiali.io/microprofile-x.y created
monitoringdashboard.monitoring.kiali.io/nodejs created
monitoringdashboard.monitoring.kiali.io/quarkus created
monitoringdashboard.monitoring.kiali.io/springboot-jvm-pool created
monitoringdashboard.monitoring.kiali.io/springboot-jvm created
monitoringdashboard.monitoring.kiali.io/springboot-tomcat created
monitoringdashboard.monitoring.kiali.io/thorntail created
monitoringdashboard.monitoring.kiali.io/tomcat created
monitoringdashboard.monitoring.kiali.io/vertx-client created
monitoringdashboard.monitoring.kiali.io/vertx-eventbus created
monitoringdashboard.monitoring.kiali.io/vertx-jvm created
monitoringdashboard.monitoring.kiali.io/vertx-pool created
monitoringdashboard.monitoring.kiali.io/vertx-server created
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/27577#issuecomment-877902997, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXLNPJFGBRHLCNHV7CTTXI7PBANCNFSM4R4ERUYQ
.

I had the same problem and I resolved it when I tried to apply addon again :)


composer create-project simplicity

Do you mind putting it up on packagist?
Would be alot easier to init a project by using the familiar way =)
TY!

Solved: https://github.com/francescomalatesta/laravel-api-boilerplate-jwt/commit/00e458738cdecd54b88d8b03464ed6d09ad31bb2


SemaphoreFullException in DbConnectionPool.PutNewObject

Microsoft.Data.SqlClient version: 1.1.3
.NET target: netcoreapp2.2
Environment: Azure Functions App
SQL Server version: Azure SQL Database
Operating System: Windows
Describe the bug
I am intermittently seeing a large number of SemaphoreFullExceptions and SqlException since yesterday when connecting to Azure SQL Databases from Azure Functions App. Completely restarting the functions app fixes the problem (for a while) until it reappears after a few hours.
Exception message:  Adding the specified count to the semaphore would cause it to exceed its maximum count.
Stack trace:
**System.Threading.SemaphoreFullException**:
   at System.Threading.Semaphore.Release (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at **Microsoft.Data.ProviderBase.DbConnectionPool.PutNewObject** (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.ProviderBase.DbConnectionPool.DeactivateObject (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.ProviderBase.DbConnectionPool.PutObject (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.ProviderBase.DbConnectionInternal.CloseConnection (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.SqlClient.SqlConnection.CloseInnerConnection (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.SqlClient.SqlConnection.Close (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)

Sometimes these are accompanied with the following exception:
Inner exception **Microsoft.Data.SqlClient.SqlException** handled at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw:
   at **Microsoft.Data.ProviderBase.DbConnectionPool.CheckPoolBlockingPeriod** (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.ProviderBase.DbConnectionPool.WaitForPendingOpen (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)

Hi @saikatguha couple of things to start with:
1- Can you test your application with the latest version of M.D.S v<IP_ADDRESS> or the preview release  Version=2.1.0-preview1.20235.1
2- Since netcore2.2 EOL was on December 23, 2019 can you test the application with netcore3.1 or netcore2.1 please, to see if the same issue comes up?
3- is it possible to provide us a repro to start with?

The original bug is intermittent, so it will take some time to repro, or conclude if it is resolved.
I switched dotnet framework to version netcoreapp3.1 but still on M.D.S package version 1.1.3.
So far I don't see a repro yet, but will wait a few weeks to definitively conclude.
I am unable to use M.D.S package version 2.0.0 due to some dependency issues.
If I don't post a repro by October 1, 2020 please close this bug as resolved. Thanks!

@saikatguha Thanks for the response I will tag the issue as Waiting for client responses so we can come back here every week and check the status until October first. Hopefully the issue is resolved.

Moving to netcoreapp3.1 has not fixed the problem.
Adding the specified count to the semaphore would cause it to exceed its maximum count.
System.Threading.SemaphoreFullException:
   at System.Threading.Semaphore.ReleaseCore (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Threading.Semaphore.Release (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Data.ProviderBase.DbConnectionPool.PutNewObject (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.ProviderBase.DbConnectionPool.DeactivateObject (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.ProviderBase.DbConnectionPool.PutObject (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.ProviderBase.DbConnectionInternal.CloseConnection (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.SqlClient.SqlConnection.CloseInnerConnection (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.SqlClient.SqlConnection.Close (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)

Perhaps related or maybe unrelated, I am also occasionally seeing large bursts of the following exceptions, during which time no queries can be executed, even though there is no issue with credentials.
A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - The handle is invalid.) The handle is invalid.
Microsoft.Data.SqlClient.SqlException:
   at Microsoft.Data.ProviderBase.DbConnectionPool.CheckPoolBlockingPeriod (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at Microsoft.Data.ProviderBase.DbConnectionPool.WaitForPendingOpen (Microsoft.Data.SqlClient, Version=1.13.20136.2, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
Inner exception System.ComponentModel.Win32Exception handled at Microsoft.Data.ProviderBase.DbConnectionPool.CheckPoolBlockingPeriod:

@saikatguha can you provide a sample repro of your application please?

using (var connection = new SqlConnection(_connectionString)) {
    var command = GetSqlCommand(connection, query, parameters);
    if (command.Connection.State == ConnectionState.Closed) {
        await command.Connection.OpenAsync();
    }
    if (timeout != null) {
        command.CommandTimeout = timeout.Value;
    }

    using (var reader = await command.ExecuteReaderAsync()) {
        while (await reader.ReadAsync()) {
            ...
        }
     }

    return result;
}

Connection string is:
Server=tcp:****.database.windows.net,1433;Initial Catalog=****;Persist Security Info=False;User ID=****;Password=****;MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;

@saikatguha is possible to have
GetSqlcommand function, query and parameters as well?

        private SqlCommand GetSqlCommand(SqlConnection connection, string query, IDictionary<string, object> parameters) {
            var command = new SqlCommand(query, connection) {
                CommandTimeout = _defaults.Value.Timeout
            };
            if (parameters != null) {
                foreach (var item in parameters) {
                    if (item.Value == null) {
                        command.Parameters.Add(new<EMAIL_ADDRESS>DBNull.Value));
                    } else if (item.Value is SqlParameter p) {
                        command.Parameters.Add(p);
                    } else {
                        command.Parameters.Add(new<EMAIL_ADDRESS>item.Value));
                    }
                }
            }
            return command;
        }

I am not logging the query/parameters currently. After instrumenting, will take some time to repro to get a trace. How essential is the query? The exception above throws on the call to OpenAsync() before the query is executed.

I am not logging the query/parameters currently. After instrumenting, will take some time to repro to get a trace. How essential is the query? The exception above throws on the call to OpenAsync() before the query is executed.

That will help to understand the situation better.
However, what I can see now, although you are disposing the connection, the command is not disposed. I am not sure if that leaves some resources open (finalizer and subsequently GC is not called on them). Since you are calling the connection from SqlCommand, my guess is that prevents the connection from closing and if a connection is not closed it wont be added to the pool and a new connection will be created. There is a maximum number of concurrent entries in DbConnectionPool  semaphore. The pool is automatically cleared after a fatal error happens and the loop goes on. One easy possible test for this theory is wrapping your SqlCommand in a using statement and see if the error comes up, or simply call connection.OpenAsync directly or check the state from the connection directly.

I will dispose SqlCommand and report back if the error reoccurs. As before, might take a few weeks to repro. If I don't post by November 1, feel free to close as resolved. Thanks!

@saikatguha, I am following up to see if the issue has been fixed by suggested solution before closing it.

I've haven't seen a repro since disposing SqlCommand. Please close as resolved. Thanks!


mlc_llm/serve/engine.py", line 101, in _convert_model_info     assert isinstance(chat_config.conv_template, Conversation) AssertionError

I am getting this error .
python -m mlc_llm.serve.server --model dist/phi-2-q4f16_1-MLC  --model-lib-path dist/prebuilt/phi-2/phi-2-q4f16_1-metal.so  --device "metal"  --host <IP_ADDRESS>  --port 8000
I am running this command and installing the libraries python3 -m pip install --pre -U -f https://mlc.ai/wheels mlc-llm-nightly mlc-ai-nightly using this command.

This is because the format of conv_template in mlc-chat-config.json is now changed, introduced in PR #1965 . You need to re-generate your mlc-chat-config.json using the python -m mlc_llm gen_config ... command

Hey also I wanted to deploy this test api on hugging face spaces . I tried to do it using python client.But there was an error of device_type = none. Umm so as I was hosting on a docker. So I am not sure is this the right way to host the mlc compiled models .I have also raised a bug it's very latest.It would be helpful if I can get a advice on this.


Items Found Error Bug

i'm getting this weird bug where it detects that there's items available but there aren't and then it spams Could not get item details {"code":0,"message":"Token Validation Failed"} and then tries to buy items and then gives me an error, here's the whole log :
C:\Users\user\Desktop\roblox-limiteds-sniper-free-main\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Connection.js:61
        _Callback_error.set(this, new Errors_js_1.ProtocolError());
                                  ^

ProtocolError: Protocol error (Page.navigate): Invalid parameters Failed to deserialize params.url - BINDINGS: mandatory field missing at position 50
    at new Callback (C:\Users\user\Desktop\roblox-limiteds-sniper-free-main\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Connection.js:61:35)
    at CallbackRegistry.create (C:\Users\user\Desktop\roblox-limiteds-sniper-free-main\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Connection.js:106:26)
    at Connection._rawSend (C:\Users\user\Desktop\roblox-limiteds-sniper-free-main\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Connection.js:216:26)
    at CDPSessionImpl.send (C:\Users\user\Desktop\roblox-limiteds-sniper-free-main\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Connection.js:425:78)
    at navigate (C:\Users\user\Desktop\roblox-limiteds-sniper-free-main\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Frame.js:230:47)
    at Frame.goto (C:\Users\user\Desktop\roblox-limiteds-sniper-free-main\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Frame.js:208:13)
    at CDPPage.goto (C:\Users\user\Desktop\roblox-limiteds-sniper-free-main\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Page.js:438:91)
    at C:\Users\user\Desktop\roblox-limiteds-sniper-free-main\utils\roblox.js:17:20
    at Generator.next (<anonymous>)
    at fulfilled (C:\Users\user\Desktop\roblox-limiteds-sniper-free-main\utils\roblox.js:5:58)

Node.js v19.9.0

Probably because of your .env, but can you check the new version?

Discontinued


Check "in-memory" usage instead of HANA

To improve the speed of the app creation we should check whether we can use an "in-memory" version of the app instead of using the deployment with HANA. This should reduce the deployment time by 5 minutes.

We will stick to the usage of a HANA database.


[php]: attempt to perform arithmetic on a nil value

I'm on NeoVim Nightly, installed the latest PHP grammar from nvim-treesitter and it's up to date, same for nvim-treesitter-context.
When I navigate in the first context, it works as intended, but when I get into another context (like a method) it throws this error and the context doesn't change, I can only disable it.

Error executing vim.schedule lua callback: ...r/opt/nvim-treesitter-context/lua/treesitter-context.lua:571: attempt to perform arithmetic on a nil value
stack traceback:
        ...r/opt/nvim-treesitter-context/lua/treesitter-context.lua:571: in function 'highlight_contexts'
        ...r/opt/nvim-treesitter-context/lua/treesitter-context.lua:662: in function 'open'
        ...r/opt/nvim-treesitter-context/lua/treesitter-context.lua:706: in function 'fn'
        ...r/opt/nvim-treesitter-context/lua/treesitter-context.lua:473: in function ''
        vim/_editor.lua: in function ''
        vim/_editor.lua: in function <vim/_editor.lua:0>

I've tried to reproduce this error only on Lua and it doesn't happen.

With the latest update it seems to work again


[Feat]: The website lack dark mode feature.

Description
The dark mode feature look cool and enhance the look of website. Please assign me this under gssoc-ext and hactoberfest-accepted.
Regards
Screenshots

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I'm a GSSoC'24-Extd contributor
[X] I'm a Hacktoberfest'24 contributor
[X] I am willing to work on this issue (optional)

Hey @ChampGupta, dark mode is a very good feature, but we have not decided to add the dark mode feature, we will let you know if it is needed in the future. Thank you for raising the issue.

Actually, I need to reach a total of 128 stars to get the Starstruck x2 badge achievement on my GitHub. Can you please help by Star our repository? ⭐

I have starred it.


Feed-in and power consumption at the same time?

I just updated from the old chestnut version to this, the installation is very nice.
One thing that I don't understand, it seems my inverter seems to both consume and feed-in engergy at the same time.
I cannot figure it out, does anyone know what this is?

As you have 3 phases they are independent of each other and if you have your H3 set with balance it will output equally across all it's phases - if one of your phases has a higher load than the amount of feed-in then you will see a grid consumption on that phase.
Often your energy supply will be using net-metering so in the above example you are feed in (0+1.283+0)=1.283, and consuming (1.008+0+0.312)=1.32 so with net-metering your meter would see (1.32-1.283=0.037 import)
You can't import and export on the same phase at the same time.

As you have 3 phases they are independent of each other and if you have your H3 set with balance it will output equally across all it's phases - if one of your phases has a higher load than the amount of feed-in then you will see a grid consumption on that phase.
Often your energy supply will be using net-metering so in the above example you are feed in (0+1.283+0)=1.283, and consuming (1.008+0+0.312)=1.32 so with net-metering your meter would see (1.32-1.283=0.037 import)
You can't import and export on the same phase at the same time.

thanks for this explanation. My provider also uses a net meter, so all three phases are summed up. Is there a different way to set up the fox meter maybe for it to run more efficient? Consuming on one phase and feeding in on the other does not seem very efficient to me. I personally don’t care if it’s balanced or not.


Add a data retention policy (e.g. for feedback from logs)

We should have a data retention policy (and remove data that is old) for our feedback page.
e.g. something like this:
https://privacydoc.corp.google.com/privacy/policy/retention_and_deletion.html?cl=head

Our FAQ says we will remove all data within 3 months.
--Will
On Sat, Apr 25, 2015 at 6:56 PM, iislucas<EMAIL_ADDRESS>wrote:

We should have a data retention policy (and remove data that is old) for
our feedback page.
e.g. something like this:
https://privacydoc.corp.google.com/privacy/policy/retention_and_deletion.html?cl=head
—
Reply to this email directly or view it on GitHub
https://github.com/uProxy/uproxy/issues/1431.

Good! Then I'll just have to make sure our AppEngine actually does that. :)
@lucyhe offhand, do you know?


Interoperability with FastDDS

I'm trying to test interoperability with FastDDS on Windows 11. You already test interop with CycloneDDS, right?
My test so far goes like this:

Download the FastDDS Shapes Demo app.

This requires filling out a form, but is pretty easy.

Run the contained bin/ShapesDemo.exe.
In the GUI, click "Publish" and accept the default settings to create a red square publisher.
Run the test programs below.

My Dust DDS test program is as follows, using version 0.4.0:
use dust_dds::{
    domain::domain_participant_factory::DomainParticipantFactory,
    infrastructure::{error::DdsResult, qos::QosKind},
};
use std::{thread, time::Duration};

fn main() -> DdsResult<()> {
    let participant = DomainParticipantFactory::get_instance().create_participant(
        0,
        QosKind::Default,
        None,
        &[],
    )?;
    loop {
        println!(
            "{:?}",
            participant
                .get_discovered_topics()?
                .into_iter()
                .map(|topic_handle| participant.get_discovered_topic_data(topic_handle).unwrap())
                .collect::<Vec<_>>()
        );
        thread::sleep(Duration::from_secs(1));
    }
}

The result is empty:
[]
[]
...

For comparison, I tried the same thing using RustDDS:
use std::{thread, time::Duration};
use anyhow::Result;
use rustdds::DomainParticipant;

fn main() -> Result<()> {
    let participant = DomainParticipant::new(0)?;
    loop {
        println!("{:?}", participant.discovered_topics());
        thread::sleep(Duration::from_secs(1));
    }
}

and I get the following output:
[]
[]
[]
[DiscoveredTopicData { updated_time: 2023-09-19T20:28:12.684058600Z, topic_data: TopicBuiltinTopicData { key: None, name: "Square", type_name: "ShapeType", durability: Some(Volatile), deadline: Some(Deadline(Duration { seconds:<PHONE_NUMBER>, fraction:<PHONE_NUMBER> })), latency_budget: Some(LatencyBudget { duration: Duration { seconds: 0, fraction: 0 } }), liveliness: Some(Automatic { lease_duration: Duration { seconds:<PHONE_NUMBER>, fraction:<PHONE_NUMBER> } }), reliability: Some(Reliable { max_blocking_time: Duration { seconds: 0, fraction: 429496730 } }), lifespan: Some(Lifespan { duration: Duration { seconds:<PHONE_NUMBER>, fraction:<PHONE_NUMBER> } }), destination_order: Some(ByReceptionTimestamp), presentation: Some(Presentation { access_scope: Instance, coherent_access: false, ordered_access: false }), history: None, resource_limits: None, ownership: Some(Shared) } }]
...

So I'm wondering if there's an incompatibility or if I'm just using the Dust DDS API wrong?

We have looked into this and it looks indeed like a compatibility issue. We will investigate further and try to solve over the coming days.

Thanks for doing that! Unfortunately, I'm still unsuccessful.
I've set my version to the latest commit:
dust_dds = { git = "https://github.com/s2e-systems/dust-dds.git", rev = "e558f816c056d3043fe2a35b96f492327b80aa3a" }

Then I ran cargo update, cargo clean, and then reran the above programs back to back. I got the same results as before.
Have you tried running that code with the actual FastDDS ShapesDemo, or only the new interoperability tests?

A quick status update on this issue. We investigated a bit further and found the root cause for the behavior.
In DustDDS we are only using topic information publisher by a built-in Topics Announcer for find_topic(). However, neither CycloneDDS nor FastDDS send Topic information from a built-in Topics Announcer but instead use the topic information sent by the discovery of the readers and writers. This is understandable since there is a 1-to-1 relationship between a Reader/Writer and a Topic so it makes sense to include also these topics in the list of discovered topics. Our plan is to add this within the next week.

Hi @samcarey, took a little longer than we had foreseen but we have implemented a fix for this issue. I didn't have the chance to replicate your use case but I modified the test to find topics from FastDDS and that is working well. I hope this fixes the issue for your usage but if not, as usual don't hesitate in reopening this issue.


add originKey in helper

When using BindingHelper(proto: V, key: string): void, it will map state, mutation... key is same as property name. I can't use another property  name which is difference between the key. So it should change like this:
BindingHelper(proto: V, key: string, originKey?: string): void

My target code is:
// decorator wrapper
export function decorator<D extends BindingHelper, T> (helper: D, keyMap: T) {
    type KeyType = keyof T

    function decoratorFactory(originKey?: undefined): (target, key: KeyType) => any
    function decoratorFactory (originKey: KeyType): (target, key: string) => any
    function decoratorFactory (originKey): any {
        if (typeof originKey === 'string') {
            return function (target, key: string) {
                return helper(target, key, originKey)
            }
        } else {
            return function (target, key: KeyType) {
                return helper(target, key)
            }
        }
    }

    return decoratorFactory
}

// store
// ... some code
// ... some code
export let Store = {
    state: decorator(namespace(storeName, State), keymirror(state)),
    getter: decorator(namespace(storeName, Getter), keymirror(getters)),
    mutation: decorator(namespace(storeName, Mutation), keymirror(mutations)),
    action: decorator(namespace(storeName, Action), keymirror(actions)),
}
//...

// in component

import { Store as M1Store } from 'store/modules/m1'
import { Store as M2Store } from 'store/modules/m2'

@Component()
export default class Foo extends Vue {
    @M1Store.state('size') m1Size
    @M2Store.state('sise') m2Size

    @M1Store.mutation()
    changeLayoutSize: (size: number) => void
}

Sorry, I really not sure what is this change for...
You said:

I can't use another property name which is difference between the key

But you actually can do that, See https://github.com/ktsn/vuex-class/blob/master/test/bindings.ts#L24-L25
If I'm misunderstanding you, could you describe more details about this change?

@ktsn I want to write a wrapper for vuex-class. In your example, if I want to use a module store, I should write code like this:
import Vue from 'vue'
import Component from 'vue-class-component'
import {
  State,
  namespace
} from 'vuex-class'

const ModuleState = namespace('path/to/module', State)

@Component
export class MyComp extends Vue {
  @ModuleState('foo') moduleFoo

  // If the argument is omitted, use the property name
  // for each state/getter/action/mutation type
  @ModuleState foo

  created () {
    this.moduleFoo // -> store.state[''path/to/module/foo']
    this.foo // -> store.state[''path/to/module/foo']
  }
}

If many component use this store, I have to write const ModuleState = namespace('path/to/module', State) again an again.  If I also use Getter, Action, Mutation, it will be more worse. So I write a wrapper to deal with. It will look like below, and keys will get type check.
import Vue from 'vue'
import Component from 'vue-class-component'
import { Store } from 'path/to/module'

@Component
class Foo extends Vue {
    @Store.state()
    foo

    @Store.state('foo')
    foo2

    @Store.action()
    hello

    created () {
        this.foo // store.state['module/foo']
        this.foo2 // store.state['module/foo']
        this.hello // store.action['module/hello']
    }
}

Now, I can't do this: @Store.state('foo') foo2 ,  because my wrapper is use BindingHelper function, and helper can't change the property name if I use function helper (proto: Vue, key: string): void.

Here is my example: https://github.com/Allenice/vuex-example/blob/master/src/store/utils/vuexUtil.ts#L30

Thanks, I found another way to write a wrapper.
export function decorator<D extends BindingHelper, T>(helper: D, keyMap: T) {
    type KeyType = keyof T
    type Decorator = (target, key: string) => any

    function decoratorWrapper(target, key: KeyType): void
    function decoratorWrapper(originKey: KeyType): Decorator
    function decoratorWrapper(a: any | KeyType, b?: KeyType): Decorator | void {
        if (typeof b === 'string') {
            const target = a
            const key = b
            return helper(target, key)
        }

        const originKey = a
        return helper(originKey)
    }

    return decoratorWrapper
}


Memory leak in Share Activity

Summary:
The location listener in share activity is leaking memory.
Steps to reproduce:
Leak canary logs
Expected behavior:
No memory leaks
Device and Android version:
Redmi Note 5 7.1.2
Commons app version:
Latest master
Screen-shots:

Would you like to work on the issue?
It would be great, if someone else could pick it up. :)

I'll take this up alongside failed uploads.

This can be closed I guess?


Money mask Placeholder

I am using v-mask="'money'" for currency/money and it works correctly, but the input text shows 'money' instead of the desired placeholder, how can i avoid this default 'money' placeholder to show?

Can you give me a fiddle with the problem? The placeholder is working fine here:
<input v-mask="'money'" placeholder="PLACEHOLDER" class="mdl-textfield__input" type="text" id="sample4">


Enhance multiline string diff output

CHECK_EQUAL_STR, WARN_EQUAL_STR, REQUIRE_EQUAL_STR printed the full content of both strings if there was a mismatch. This is changed using the new string diffing technique introduced in PR #275 for text waves. The new output will only contain the first difference in both strings and some context around.
The new output look like this:
String mismatch (case insensitive):
str1: 0:0:0> a
str2: 0:0:0> b
: is false. Assertion "WARN_EQUAL_STR(a, b)" failed in line 13, procedure "Various.ipf"

Close #104

I am not sure if referencing issues and PRs in commit messages is useful as these references will be outdated whenever the project moves to another platform.

My 2 cents: As long as the references to issues/PRs are in addition to a good commit message I'm okay with them. But the references must never replace a good commit message. The git forges are transient, git itself not.


Eliminate the elusive ThetaJoin.

Also,

have Coalesce push Take/Drop later, rather than earlier
add an optimize transformation to finalize QScript (which pulls Take/Drop earlier)
implement Mergable for ProjectBucket
fix conversions of Take and Drop from LP

Current coverage is 64.87% (diff: 47.87%)

No coverage report found for master at eabcdd5.

Powered by Codecov. Last update eabcdd5...34e909f

@sellout aside from question about if we're calling optimize anywhere, LGTM. I'll merge once that's addressed.

@sellout I got a "fatal: Not possible to fast-forward, aborting." Can you merge in master?

Done.


sessionDescriptionHandler.remoteMediaStream.getVideoTracks() not fully populated

Describe the bug
session.sessionDescriptionHandler.remoteMediaStream is not populated with all the video streams. When a session is re-invited with more than one video stream, only the last video stream is active, and only the last video stream is added to session.sessionDescriptionHandler.remoteMediaStream as a track.
Logs

To Reproduce (if possible)

Re-invte the session with more then one video stream, and attach a handler for addtrack to the PeerConnection.
console.log(session.sessionDescriptionHandler.remoteMediaStream.getVideoTracks());

Expected behavior
session.sessionDescriptionHandler.remoteMediaStream.getVideoTracks() should be populated with all the video tacks in that session.
Observed behavior
Only the last video track in the SDP is included in the array. Others are stopped.

Correct. But this is not a bug. The SessionDescriptionHandler included with the project only supports up to one audio and/or on video track - there is only ever at most one audio track and/or one video track associated with the remoteMediaStream (the last track added). I'm going to update the documentation to make this more clear.
The session description handler architecture exists to allow users to write their own and this enhancement can be dealt with in that fashion without making any changes to the current library. Regardless, a session description handler which supports multiple audio/video tracks is an enhancement request and would be interested in looking at a pull request, but otherwise this is low on the list of things to do (at least the to do list I'm working on).

Thanks, In the end I made use of my own code to overcome this.


Validation test examples

Validation test examples

Added Orders, Results and Demographics folders in /examples/Test/ to organize messages

Moved integration and e2e tests sample files to new folders

Added test validation scenarios for Orders that came out of research (files with suffix _0_initial_message)
Added resulting Hl7 and FHIR messages at each step of the Orders flow (files with suffix _1_hl7_translation, _2_fhir_transformation, _3_hl7_translation_final)

Issue
#559

I know we'll need to regenerate these after the ORM mapping issue is fixed, but for now these look great to me!

Right. The plan is to keep them up to date as mapping changes


Sheetsee Upgrade

So, this upgrades sheetsee and simplifies some of the functionality in the showdata() function, but at the cost of losing the color-changing on selection of markers. The map also no longer "clusters" nearby markers together, but I believe that's because of a change in sheetsee.js, not in hack-spots specifically.
Two bugs I came across: highlightLastMarker() was highlighting the oldest marker instead of the newest, and the latest version of sheetsee.js on npm double-renders tables (resulting in an empty table) if you don't pass its pagination option.
I also standardized the indentation style around four spaces; sorry if that's not preferred, but it had been a mix of spaces and tabs and this at least is consistent.

Should I file a bug against https://github.com/jlord/sheetsee-tables for the double-rendering issue, @jlord?

Sorry about the delay on this!
re: indents, no worries, the fix is appreciated, I had a confused editor and never updated this, so it needed it!
I ran into the clustering problem myself when I tried to update the sheetsee. It's definitely a bummer because the clustering was useful. But I'm willing to live without it for a bit until I can figure out what's up there.
I noticed though that the zoom doesn't work, any thoughts on that?
I'll go ahead and open an issue on sheetsee-tables, that definitely needs to get fixed!

With zoom, it was unclear to me what the behavior was supposed to be. The version of the map I'd seen had the clustering, which sort of handled zoom automatically?
Right now it's defaulting to zoom level 0 on map load (and reset) and then not zooming at all on interaction with the table (obviously). I think it should zoom to the pin when you click on a table row, but not zoom when you click on a pin. Is there built-in functionality in sheetsee or the mapbox API to zoom to a "see all pins on this layer" level, which would make sense for initial load and reset? I couldn't find it from a cursory search.

I found the correct zoom method map.setView([lat, long], zoom) so I'll merge this then add that in :+1:
Thanks so much for your work! It's super helpful. Hopefully I'll get the rest of it updated sometime soon!


npm package vulnerabilities

There are 162 npm package vulnerabilities: 5 low, 77 moderate, 55 high, 25 critical.
Some of these have to do with XSS and command injection.
I'd recommend running npm audit fix to fix most of these, and if possible review the breaking changes and updating those too.

Good catch. We'll investigate if we're actually using this package, or some other version of it.
Thanks for the heads-up


How to upload a task from a video with annotations?

Use case:

There is a video file with an object that needs to be annotated with a bbox
Person A and Person B both have independent local CVAT instances
Person A creates a task from the video file and makes annotations
Person A dumped the annotations into a file (e.g. in COCO format)
Person B imports the annotations to their instance for review and corrections

There is a way of importing annotations along with a video through CLI/REST, although the annotations have frame_XXX references, and the upload only works with a set of images.
Is there a way of creating a task via CLI using a video file and the dumped annotations?
So far I managed to split video into images first and then upload as image sequence. But then zoom always resets in the UI, since it interprets the task as per-image, which actually is not true. And I cannot guarantee that my image sequence is the same as it was at the other person instance.

Hi, What you need is probably backup/restore of a task.
Please, refer to user guide: https://openvinotoolkit.github.io/cvat/docs/manual/advanced/backup/
You can disable "Reset zoom" (enabled by default for images):

There is related bug #4289, but generally it works

Thank you for response! How do I enable backup on my instance? I don't the menu item
Server version: 1.7
Core version: 3.17.0
Canvas version: 2.8.0
UI version: 1.25.0

@evekeen
Why can't you build it? Usually we publish docker images when releases come.

@bsekachev its just tricky to set everything up on Mac with Apple processor in order to build.
BTW when I tried the feature on cvat.org, the image quality went significantly down after re-import. Is there a setting about keeping the image quality somewhere?

@evekeen
I am not sure I understand what kind of re-import you are talking about. Could you please clarify the scenario? If it is true, it might be a bug,  because I don't expect image quality degradation after any kind of import.

@bsekachev the scenario is following:

Backup a task
Import the task from the backup on the same instance
Compare image quality of 2 tasks

In the imported task quality is significantly worse

@evekeen Are you able to provide a couple of screenshots with these images? If image quality is actually worse, better to submit a new issue with the scenario you provided and these screenshot, because as I told before, I suspect it is just a bug

@bsekachev I've created an issue: https://github.com/openvinotoolkit/cvat/issues/4377


Intregrate text from the project Clément is currently writing

Description
I currently writing a document explaining the main ideas behind the vivarium. Once I will have finished it (by the end of this week) we should integrate part of this text and figures in the README.
Steps to Reproduce
Environment (Optional)

OS:
Browser:
Python Version:
Package Version:

Screenshots (Optional)

Updated readme in dev branch.


Update templates for resourcedocsgen

Updates the templates to pull in the fix from https://github.com/pulumi/pulumi/pull/9563.

I think we're good @t0yv0!
http://pulumi-docs-origin-pr-7487-49f0b244.s3-website.us-west-2.amazonaws.com/registry/packages/azure-native/api-docs/machinelearningservices/liststorageaccountkeys/


upgrade failure

Hello,
Simply, upgrade failed and I deleted  the "tmpbcbio-install" directory and retried, but the problem still persists.
bcbio_nextgen.py upgrade -u stable --tools --data
Upgrading bcbio
Traceback (most recent call last):
File "/isilon/RnD/tool-data/bcbio/anaconda/bin/conda", line 12, in
from conda.cli import main
ModuleNotFoundError: No module named 'conda'
Traceback (most recent call last):
File "/isilon/RnD/tools/bcbio/bin/bcbio_nextgen.py", line 221, in
install.upgrade_bcbio(kwargs["args"])
File "/isilon/RnD/tool-data/bcbio/anaconda/lib/python3.7/site-packages/bcbio/install.py", line 69, in upgrade_bcbio
_update_conda_packages()
File "/isilon/RnD/tool-data/bcbio/anaconda/lib/python3.7/site-packages/bcbio/install.py", line 277, in _update_conda_packages
channels = _get_conda_channels(conda_bin)
File "/isilon/RnD/tool-data/bcbio/anaconda/lib/python3.7/site-packages/bcbio/install.py", line 262, in _get_conda_channels
config = yaml.safe_load(subprocess.check_output([conda_bin, "config", "--show"]))
File "/isilon/RnD/tool-data/bcbio/anaconda/lib/python3.7/subprocess.py", line 395, in check_output
**kwargs).stdout
File "/isilon/RnD/tool-data/bcbio/anaconda/lib/python3.7/subprocess.py", line 487, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['/isilon/RnD/tool-data/bcbio/anaconda/bin/conda', 'config', '--show']' returned non-zero exit status 1.

Hi Segun,
Sorry about that, we are having some problems with upgrading and installing right now, I've been trying to fix them the past few days but I'm still working on it.

OK thanks.  I can see the conda module is there, but it's broken not finding it.  Hope to hear the problem gets resolved soon.

Thanks so much for this report, hopefully we have these issues fixed although they will require a reinstall of the code and tools to easily fix a broken system. More details on the issues we found and how to fix are here:
https://github.com/bcbio/bcbio-nextgen/issues/2889#issuecomment-515842898

Thank you. I had to reinstall and upgrade, but the pipeline is back to alive now.

Thanks for following up!

Would this now be okay to try?
When trying this a few days ago, it broke the bcbio with errors and thus I am somehow nervous to give another shot. I want to add ericscript database for hg38 to perform fusion detection.
bcbio_nextgen.py upgrade -u stable --data --datatarget ericscript --genomes hg38

You should be fine with updating in this way, although a couple of thoughts:

I'm not sure how well ericscript works with hg38, and @roryk might have a better recommendation for fusion detection.
You don't need a code update if you want to add new data targets and can just do:

bcbio_nextgen.py upgrade --data --datatarget ericscript --genomes hg38

Hope this helps

The only approach that worked for us with hg38 was Kallisto/Pizzly (mostly because Star doesn't handle hg38 well).

Hi everyone,
I have on my list of things to do to add STAR support for hg38 by stripping off the ALTs when we make the index, that way we can still use the fusion callers that rely on the STAR output for GRCh37. At the same time I'll be implementing support for the arriba caller, which crushed everything else in the DREAM challenge.

Thanks Rory and Brad.  I understand you guys have a lot of things on the table, but any ETA on arriba?
RE ericscript with hg38, gdc.sh (?) failed and thus downloaded the hg38 database manually from ericscript website to put in the genomes directory and then updated the tool-data in galaxy. I am about to check the ericscript result, but it did finish in a couple of days.  The bottlenect is in the blat program that may be parallelized in the R script (the wrapper).

Hi Segun,
I'm aiming to have support for GRCh37 this week-- hg38 is going to take a little bit longer since we need to support STAR in order to use arriba, and STAR won't work on hg38 with the alt alleles.

Thank you!
GRCh37 would be sufficient. 👍


engine/schema: fix build error in #5642

Description
This PR fixes build error after #5642 is merged.

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[x] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

@blueorangutan package

@weizhouapache a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 1661


Feature Request: Add N2K Autopilot page to KIP demo template

Feature Request: Add N2K Autopilot page to KIP demo template
Thanks

Combining issues: Other demo ideas:
Feature Request: Add engine monitoring gauges page to KIP demo template
Feature Request: Add barograph page to KIP demo template

So the problem with this, is currently the demo config is pulling data from http://demo.signalk.org which does not have engine or barometer data at this time. Also the autopilot needs some server support as well I think. Not sure how to address that. Have any ideas?

And... the AP needs a code fix. Coming soon!


dapr 1.11 invoking dapr 1.12 got error

In what area(s)?
/area runtime
What version of Dapr?
1.11.x
1.12.x
Expected Behavior
dapr 1.11 sidecar can invoking dapr 1.12 sidecar successfully
Actual Behavior
After upgraded dapr version into 1.12 in AKS cluster, I just restart some applications (it's be injected dapr 1.12), but don't restart others (still keep dapr 1.11).
When un-restarted application send invocation to restarted application ,I got x509 error like this

Steps to Reproduce the Problem
follow up above description

seems related to mTLS
CC @JoshVanL

We also noticed this issue. I got the error in the kubernetes cluster I run with kind in my locale. The reason is that when we upgrade dapr to version 1.12.2 with helm, the tls cert under dapr-trust-bundle is also updated and does not use the old one. When I upgrade to version 1.11, it uses the old tls cert, this secret does not update. Until this time, we normally did not have a problem with upgrades, it always used the old cert, but this secret to be updated with 1.12.


Update to VS2019 and Windows 10 SDK for _winsdk solution and sample

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


How to quit/exit/shutdown sphinx-autobuild on Windows?

CTRL+C, CTRL+Q, CTRL+X, ESC... nothing works besides closing the console window.

Ctl-C works for me on Win10 (1709) in powershell console.

Closing since this is an old issue without enough information to provide support.


Scheduler for sending deadline remainders

Feature Idea
->This is one of the biggest features of this application. The user adds tasks and maintains all his tasks in the application, but there should be a way for the user to get the details regarding his upcoming deadlines. This allows the user to keep track of his deadlines more easier than ever.
How to do
->Run a scheduler everyday at 12:00AM in the application which loops through all the users and also their tasks. Whenever there is a task whose deadline is due in coming 7 days, a table with list of tasks and their details needs to be sent out to respective users.

This feature us completed. Used a scheduler library of Python which calls a function to send remainders everyday at 12:00AM.
Below is how the mail looks like:


Test client fails when WSGI application is a generator

Here is the test that proves it:
from falcon.testing import TestClient

def another_dummy_wsgi_app(environ, start_response):
    start_response('200 OK', [('Content-Type', 'text/plain')])

    yield 'It works!'

def test_falcon_testing_client():
    client = TestClient(another_dummy_wsgi_app)

    client.simulate_get('/nevermind')

Here is the link for convenience.

Btw, just to clarify, I've tested this myself, and this applies to all recent (or probably even all) Falcon versions, including the 2.0 beta, 1.4.1 etc.
Interesting find @tribals !


OriginCaCertificate references invalid TLS CertRequest Property Subjects

What happened?
The example for OriginCaCertificate references an invalid TLS CertRequest property Subjects whereas the property is Subject.
Example
Example in the registry
var exampleCertRequest = new Tls.CertRequest("exampleCertRequest", new()
    {
        PrivateKeyPem = examplePrivateKey.PrivateKeyPem,
        Subjects = new[]
        {
            new Tls.Inputs.CertRequestSubjectArgs
            {
                CommonName = "",
                Organization = "Terraform Test",
            },
        },
    });

Working example (c#)
var exampleCertRequest = new Tls.CertRequest("exampleCertRequest", new()
    {
        PrivateKeyPem = examplePrivateKey.PrivateKeyPem,
        Subject = new Tls.Inputs.CertRequestSubjectArgs
        {
            CommonName = "example.com",
            Organization = "ACME Examples, Inc",
        },
    });

Output of pulumi about
n/a
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Also!!!! the broken examples references Terraform :/

Hey @phillipedwards. Both issues have since been fixed, but we haven't had a release to publish them. I'll kick off a patch release now.


I can’t get the cookie

Hi,
I can get to the login page, enter my credential, then it asks for a token I can provide, but in the end I don’t get the cookie:
$ ./openfortivpn-webview vpngw.foo.com:443/HMS --extra-ca-certs /etc/openfortivpn/cert/ca.pem
qt.webenginecontext:

GL Type: desktop
Surface Type: OpenGL
Surface Profile: CompatibilityProfile
Surface Version: 4.6
QSG RHI Backend: OpenGL
Using Supported QSG Backend: yes
Using Software Dynamic GL: no
Using Multithreaded OpenGL: yes

Init Parameters:
  *  application-name openfortivpn-webview
  *  browser-subprocess-path /usr/lib/qt6/libexec/QtWebEngineProcess
  *  create-default-gl-context
  *  disable-features ConsolidatedMovementXY,InstalledApp,BackgroundFetch,WebOTP,WebPayments,WebUSB,PictureInPicture
  *  disable-setuid-sandbox
  *  disable-speech-api
  *  enable-features NetworkServiceInProcess,TracingServiceInProcess
  *  enable-threaded-compositing
  *  in-process-gpu
  *  use-gl desktop

webview: "https://vpngw.foo.com:443/HMS/remote/saml/start"
webview: "https://vpngw.foo.com/HMS/remote/saml/start"
webview: "https://vpngw.foo.com/remote/login?lang=en"
js: Refused to apply style from 'https://vpngw.foo.com/css/main-blue.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
js: Uncaught TypeError: Cannot read properties of null (reading 'style')
webview: "https://vpngw.foo.com/remote/login?&err=sslvpn_login_permission_denied&lang=en"
js: Refused to apply style from 'https://vpngw.foo.com/css/main-blue.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
js: Uncaught TypeError: Cannot read properties of null (reading 'style')

Any idea of what I’ve done wrong?
PS: I have a Windows 10 host with FortiClient from which I got the CAs, is there any other info I’d need to get from there?

The application does nothing more than starting a browser and monitor all the cookies until it finds one named SVPN_COOKIE. You could really just browse to https://vpngw.foo.com:443/HMS/remote/saml/start with any browser.
Is the page loading? Could it be that HMS is the realm (openfortivpn-webview vpngw.foo.com:443 --realm=HMS) rather than a path?

Is the page loading? Could it be that HMS is the realm (openfortivpn-webview vpngw.foo.com:443 --realm=HMS) rather than a path?

I don’t know whats the realm means in this context, I’ll that and tell you.

As I mentioned in my previous message there really isn't much I can do here, the application is just a browser that monitors the cookies until it finds one named SVPN_COOKIE.
You can also try to do some remote debugging to see what is going on: pass --remote-debugging-port=9222 --remote-allow-origins=http://localhost:9222 to the application and then visit http://localhost:9222 with a Chromium based browser to inspect the page.


Make test databases obvious that they're test databases

We received 3 reports of publicly accessible databases today, all referencing databases found in https://github.com/plotly/falcon-sql-client/blob/master/sample-storage/connections.yaml .  I'm not sure why this is happening today but I suspect we've been indexed by a vulnerability search engine.
In order to stop people from reporting this issue, I've added it to our policy and scope document but not everyone will read that. Therefore I suggest doing all these things if possible:

[x] Add a comment to connections.yaml noting that these are all test databases that are intentionally public (see PR #232).
[ ] Buy a "plotly testing" domain and Add all these sites to the test.plotly.host domain rather than using the default AWS DNS entries. (Please don't add them to plot.ly since that actually is a security risk.)
[ ] Change table names and/or column names to include "testing"
[ ] If the site has a configurable header, add "Testing" to the header

@tarzzz @chriddyp Can someone please deal with this soon?

We now own plotly.host, including test.plotly.host. DNS entries for the databases could be added under there.


How to get Gke node reboot and shutdown logs using journald Systemd service unit

What happened:
i have implemented the journald configuration in my splunk but still i could not see node reboot logs.
I want to know that my gke node got restarted or not by checking the logs in splunk and i am not sure which systemd service unit holds that data
What you expected to happen:
i want to see logs to be reflected wn ever reboot happen on that gke node
How to reproduce it (as minimally and precisely as possible):
i have gke cluster and have node running on os Container-optimized os and jst login to gke node and reboot that gke and in splunk we should get some logs stating gke node rebooted.
Anything else we need to know?:
configuration using to get journal configuration:
source.journald.conf: |-
This fluentd conf file contains configurations for reading logs from systemd journal.
@id journald-all
@type systemd
@Label @concat
tag journald.journal:all
path "/var/log/journal"
matches []
read_from_head true
@type local
persistent true
path /var/log/splunkd-fluentd-journald-all.pos.json
field_map {"MESSAGE": "log", "_SYSTEMD_UNIT": "source"}
field_map_strict true
Environment:
Kubernetes version (use kubectl version): 1.15.12-gke.2
Ruby version (use ruby --version):
OS (e.g: cat /etc/os-release): Container-Optimized OS (cos)

This doesn't seem to be a bug with fluent-plugin-systemd?
If you have a general support question about how your Google Cloud servers behave on reboot I sugest contacting their support channels, or perhaps ask on serverfault or whatever...
If you have a bug to report please feel free to re-open this issue with some more information :)


Serval incorrectly checks if a build exists for translation engine endpoints

When certain translation engine endpoints are called, Serval will check if the engine was built and fail if it hasn't. Serval should not be performing this check. It is the responsibility of the engine to determine if it is in an invalid state. There are valid cases where an engine might be able to respond to these requests even when it hasn't been built. These checks should be performed by the appropriate engine.

I was the one that encouraged the check, because it corresponds with the existing engines. I also agree with you that it should be tested machine. If we live host, no language left behind, we will not need to build the engine at all. It could also be that a engine reference is the build of a different engine, which would also not need to be built a new.

This will be implemented in #45.

I would like to keep this open until it is fixed, so it isn't overlooked.

I believe this still has yet to be addressed, but I'd like to clarify exactly waht behavior we're expecting.
There are three instances I see of Serval checking to see if there's an active build before doing some processing:

In StartBuildAsync :

if (await _buildService.GetActiveAsync(id) is not null)
            return Conflict();

-> 409

In GetCurrentBuild:

Build? build = await _buildService.GetActiveAsync(id, cancellationToken);
if (build == null)
            return NoContent();

-> 204

In CancelBuildAsync:

if (await _buildService.GetActiveAsync(id) == null)
            return NotFound();

-> 404

Were all of these an issue in your eyes, @ddaspit ? (1 and 3 are my code, but 2 is yours). I understand the basic idea: let the engine say for itself if it can't manage an action. At the same time, Serval is itself keeping track of engine builds (thus, the DB structure), and it's not as though any of these are so much actions that the engine is taking (like translate or get-word-graph) as they are CRUD ops. Unless some engines will be able to simultaneously have multiple builds (which would challenge an assumption that the Machine code is built around), I don't know that this is inappropriate. It could be that you had something else in mind entirely when you wrote up the issue. Let me know.

@ddaspit Just wondering if you had any thoughts on the above? Not pressing, but I didn't want to ignore this issue.

The engine will have more accurate information on the whether a build is active. Also, an engine might have other conditions for not allowing a build. For these reasons, we want it to be the responsibility of the engine to decide if a build can start or not. Serval should not need to worry about making these decisions, so these checks should be removed and performed by the engine.


[bug] Could we add numColumns to react-native-draggable-flatlist?

We all know that adding  numColumns to flatlist could make flatlist have more columns than 1.
Could I add this prop to react-native-draggable-flatlist?

sorry, that's out of scope


Write missing Javadoc.

The only thing that Checkstyle currently reports is some missing Javadoc. Writing it seems like a decent idea.

This has been done.


Tooltips flashing vers. 2.37

In the latest version (2.37) the tooltips flashes very briefly.
This makes it very difficult to read and translate properly.

Strange, that's not happening here.
I run the installed version (msi) and debug via VS.
Apparently, this is an issue with .NET 6: https://github.com/dotnet/wpf/issues/6289

I see same issue, so I hope a fix will come for .NET 6.

.NET 6.0.5 fixes this issue apparently
https://github.com/dotnet/wpf/issues/6289 -> https://github.com/dotnet/wpf/issues/6220 -> https://devblogs.microsoft.com/dotnet/may-2022-updates/


[bug] route provisioner failure

Reported by @mathieu-benoit
Error: failed to provision: resource 'route.default#hello-world.route': failed to provision: init template failed: failed to execute template: template: :5:38: executing "" at <.SourceWorkload>: can't evaluate field SourceWorkload in type *templateprov.Data

I think the score file was https://github.com/score-spec/sample-score-app/blob/8562b6cbb6b5c5bbc826e713a41bc849696a0466/score.yaml

I couldn't reproduce this when using the branch version of https://github.com/score-spec/score-compose/pull/99. I think the bug occurred due to using an older version of score-compose with the provisioners file from the branch.


[sync materialized view]set replication_num failed when create mv

Steps to reproduce the behavior (Required)
CREATE TABLE `t1` (
                                            `k1` date,
                                            `k2` int,
                                            `k3` int
                                        ) ENGINE=OLAP
                                        DUPLICATE KEY(`k1`)
                                        COMMENT "OLAP"
                                        DISTRIBUTED BY HASH(`k1`) BUCKETS 3;
CREATE MATERIALIZED VIEW mv1
                             DISTRIBUTED BY HASH(k1) BUCKETS 10
                             REFRESH ASYNC
                             PROPERTIES('replication_num' = '1')
                             AS SELECT k1,k2 from t1;
SHOW CREATE MATERIALIZED VIEW mv1;

Expected behavior (Required)
"replication_num" = "1"
Real behavior (Required)
"replication_num" = "3"
StarRocks version (Required)

You can get the StarRocks version by executing SQL select current_version()

+----------------------------+
| current_version()          |
+----------------------------+
| BRANCH-2.4-RELEASE 9744f36 |
+----------------------------+

LGTM


Auto Sign feature?

Is it planned to add auto sign transactions? It does get annoying to sign every single one manuelly.

We are looking at ways to implement more automatic ways of interacting with apps, it's not completed yet though. There was a little discussion about it in issue #1035.

will Anchor have a whitelist like Scatter for auto sign in the near future?


Updates to enable "swift test" in Linux

This update is to enable the use of “swift test” in Linux

Is there a way to do this without moving all of our tests into another directory?

That's why I am making links to the test files whenever possible.

On Aug 12, 2016, at 5:23 PM, Tony Parker<EMAIL_ADDRESS>wrote:
Is there a way to do this without moving all of our tests into another directory?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

But then we also have things like TestNSBundle, which looks like it just moved into a different location?
I'm a bit confused about what the goal is here. Is swift test really ready to support our test scenarios? Bundle, for example, requires a specific layout of the resulting app.

Also, we need to maintain the ability to run tests on Mac using our Xcode project.

Yes that's why I copied TestNSBundle (and couple other files) and commented out the parts which give compilation errors.
Sent from my iPhone

On Aug 12, 2016, at 6:14 PM, Tony Parker<EMAIL_ADDRESS>wrote:
But then we also have things like TestNSBundle, which looks like it just moved into a different location?
I'm a bit confused about what the goal is here. Is swift test really ready to support our test scenarios? Bundle, for example, requires a specific layout of the resulting app.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

The current TestFoundation folder I believe is for testing using Xcode in MacOS
That should still work
So TestFoundation folder for MacOS and Tests for Linux or command line swift test in general
And files in Tests are links to files in TestFoundation
Sent from my iPhone

On Aug 12, 2016, at 6:15 PM, Tony Parker<EMAIL_ADDRESS>wrote:
Also, we need to maintain the ability to run tests on Mac using our Xcode project.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I don't want to have copies of our test files in two different locations in the repo. I also don't want to put a bunch of stub files in another directory so swift test can work. What we need is the ability to tell swift test (via configuration) where the test files actually are. If it doesn't have that capability, then we should block adoption on that. I also don't want stub structs with "hello world" in them (why do we need that?).
Even after we did all of this, what's the concrete benefit of using swift test vs our existing infrastructure? We should have a clear net positive from reworking our infrastructure around it, but right now I don't see what it is, exactly. We don't use swift build to build, so swift test would not be smart enough to rebuild the dependencies as required. Our current scripts do that, at least.

Using swift test will make it easy for developers to test the framework in Linux. This solution can get improved later. And I can remove the "hello world" line.
Sent from my iPhone

On Aug 13, 2016, at 11:30 AM, Tony Parker<EMAIL_ADDRESS>wrote:
I don't want to have copies of our test files in two different locations in the repo. I also don't want to put a bunch of stub files in another directory so swift test can work. What we need is the ability to tell swift test (via configuration) where the test files actually are. If it doesn't have that capability, then we should block adoption on that. I also don't want stub structs with "hello world" in them (why do we need that?).
Even after we did all of this, what's the concrete benefit of using swift test vs our existing infrastructure? We should have a clear net positive from reworking our infrastructure around it, but right now I don't see what it is, exactly. We don't use swift build to build, so swift test would not be smart enough to rebuild the dependencies as required. Our current scripts do that, at least.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@amraboelela I see you're continuing with the same approach, for example copying more files into another subdirectory. I want to be clear: I won't merge this without addressing some of the concerns I listed above.

Let's have a further discussion about this on the mailing list. Once we have a direction, we'll re-open the PR and figure out the right patch.


Restructure the project: More crates for better code reuse

Our old project layout was fine so far, but had it's weaknesses. With this new
layout we have the following elements:

server/src/lib.rs: (private) library that contains all the old server code
server/server.rs: server executable that uses said library
server/examples/*.rs: Different executables testing server code
src/lib.rs: API library for public use (helps communicating with our server)
src/client/main.rs: CLI client for our server

I moved many files around but didn't really change anything. That means that
the code is not really prepared for code reuse or anything. Many things need
to move around, before the actual new structure is ready.
Some things needed to be tweaked in order to function properly: The logger won't
cut of parts of the file path (not every path begins with src/ anymore), the
.gitignore got some new entries and check-style will check all .rs files
now (I hope that won't break travis...)

Everything looks good, I really really hope I did not miss anything. Merging...


Blazor unbelievably slow to build and reconnect

Describe the bug
When building a Blazor Server Side project of any significant size the time it takes to make a change to a .razor component is unbelievably slow.
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Using .net core 3.0 Visual Studio 2019
Create a Blazor Server Side project with a couple of references to other projects in the solution (Model, Data etc..)
Add say 20 razor components
Add Ignore Linker code to project
Ctrl + F5 to start project
Change a single html element in one of the components

Expected behavior
I've seen 4 seconds quoted as reasonable time for change to take effect
Actual behavior
It can take up to 30 seconds for project to rebuild and be able to resume
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
My machine is running an Intel Core i7 processor
Include the output of dotnet --info
Microsoft.NETCore.App 3.0.0-rc1-19456-20 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.0.0-rc1-19456-20 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

@redowl3 Thanks for contacting us.
Can you run dotnet build /bl from the command-line and attach the generated msbuild.binlog file?
@pranavkm Do we have recompilation for Blazor server-side? (We don't, don't we?).

4. Add Ignore Linker code to project

We don't understand what you mean by this.

Hi, thanks for the response.
Will run dotnet build /bl and get back to you.
Add Ignore Linker code to project file meant
 <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'">     <BlazorLinkOnBuild>false</BlazorLinkOnBuild>   </PropertyGroup>

false

This is only applicable to blazor wasm.

ok thanks, was suggested on Gitter channel

binlog.txt
Hopefully what was needed?

@redowl3 Not quite.
You need to run dotnet build /bl from the command line and it will generate a file msbuild.binlog in the same folder.
Also, just to clarify, does it take a long time to build the app or are you trying to change/update the app while it is running?

msbuild.txt
Renamed to allow it to upload.
Yes, trying to change/update the app while running.  I've tried it using the default server side project and it takes a couple of seconds, trying it with a reasonable sized solution seems to be the issue.
Thanks

Not sure if this is relevant, but noticed that VS is busy processing tasks when I press save (even though nothing has changed) at one point it had 12 tasks on the go although a couple were paused.

@redowl3 That can definitely be causing issues.
From what I see on the binlog the build (which seems to be a clean build) takes about 18 seconds. If you add to that a few additional seconds that it takes for the app to be torn down and the new app to launch, I think you get your 30 seconds.
My belief is that something might be breaking your incremental compilation. I tried to repro this creating a huge amount of components on a new app (like 40 or so) and it doesn't repro for me.
I would look at other processes that might be running at the same time and slowing down your build. I'm doing this from a laptop.
I'm closing this issue as this doesn't seem to be an issue in the general case, but an issue with your environment.

Do you have any more information on breaking your incremental compilation?
Also did you add a project references to the project?

@redowl3 You can capture the builds as visual studio makes them following the steps in https://github.com/dotnet/project-system/blob/master/docs/design-time-builds.md#visual-studio-2017-or-later
Then you can use the timeline view on MSBuild structured log viewer to see where the time is being spent on the build.

@redowl3 these might not amount to much, but perhaps a couple of things you could do here:
a) The AccountableUK.Web project references the Microsoft.AspNetCore.Blazor package which is meant for Blazor WASM. If you're attempting to build a server-side project, I'd start by removing this reference from your project. Having it causes the Component's analyzer to run twice for each compile, which would definitely slow things down.
b) This is a shot in the dark, but in an earlier preview release the compiler had an issue with analyzers. It looks like you are using an SDK \ compiler that should have addressed the issue, but perhaps you could give the workaround a try:
In your project file, add the following:
<PropertyGroup>
    <DisableImplicitAspNetCoreAnalyzers>true</DisableImplicitAspNetCoreAnalyzers>
</PropertyGroup>

c) Could you try doing two consecutive rebuilds of your Web project? Command line should be fine to start with.

Hi, thanks for further information - I can't see where Microsoft.AspNetCore.Blazor is being directly referenced?


Factor out finding permissions and command line flags

Factoring out these two features is useful because they will need to be called in many different circumstances. This will be useful for transitioning to a Gradle-based build system. For more details on the final scope of this project, read this comment. There are a lot of changes that need to be made to move towards a Gradle-based build system, so I have broken these changes into smaller, more understandable steps.
We are working on this PR with @m4gr3d, as explained here

Note: There will also have to be a corresponding PR for master for this to be merged.

Thanks!


Docker does not allow to mount root volume, even if not bound to host

Aufs is buggy, so in order to avoid using it we want to mount the entire root filesystem of a countainer,
using -v  /
This is not allowed - docker returns "Can not mount root"
Not clear why this choice was made and why is it not allowed to do non-bound mounts of volumes.

If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
For more information about reporting issues, see CONTRIBUTING.md.
You don't have to include this information if this is a feature request
(This is an automated, informational response)

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

@Stan-Kladko What issue are you having with AUFS?
Also, you can mount the host's rootfs, just not to the container's root.
docker run -v /:/host will work.