Error from server (NotFound): podmetrics.metrics.k8s.io

when I use metrics-server for "kubectl top pod" ,the error message is Error from server (NotFound): podmetrics.metrics.k8s.io ; my k8s version is v1.11.3 and  use " kubectl get apiservice v1beta1.metrics.k8s.io -o yaml " message is "status:
conditions:

lastTransitionTime: 2018-09-20T07:50:02Z
message: all checks passed
reason: Passed
status: "True"
type: Available"
why? how did i do?

can you paste the result of kubectl top pods --v=10 into a gist and link it here?

I0928 08:15:16.631768    6540 loader.go:359] Config loaded from file /etc/kubernetes/admin.conf
I0928 08:15:16.633063    6540 loader.go:359] Config loaded from file /etc/kubernetes/admin.conf
I0928 08:15:16.635579    6540 loader.go:359] Config loaded from file /etc/kubernetes/admin.conf
I0928 08:15:16.636118    6540 round_trippers.go:386] curl -k -v -XGET  -H "Accept: application/json, /" -H "User-Agent: kubectl/v1.11.3 (linux/amd64) kubernetes/a452946" 'https://<IP_ADDRESS>:6443/api?timeout=32s'
I0928 08:15:16.654460    6540 round_trippers.go:405] GET https://<IP_ADDRESS>:6443/api?timeout=32s 200 OK in 18 milliseconds
I0928 08:15:16.654475    6540 round_trippers.go:411] Response Headers:
I0928 08:15:16.654481    6540 round_trippers.go:414]     Content-Type: application/json
I0928 08:15:16.654486    6540 round_trippers.go:414]     Content-Length: 134
I0928 08:15:16.654491    6540 round_trippers.go:414]     Date: Fri, 28 Sep 2018 00:15:16 GMT
I0928 08:15:16.654543    6540 request.go:897] Response Body: {"kind":"APIVersions","versions":["v1"],"serverAddressByClientCIDRs":[{"clientCIDR":"<IP_ADDRESS>/0","serverAddress":"<IP_ADDRESS>:6443"}]}
I0928 08:15:16.654756    6540 round_trippers.go:386] curl -k -v -XGET  -H "Accept: application/json, /" -H "User-Agent: kubectl/v1.11.3 (linux/amd64) kubernetes/a452946" 'https://<IP_ADDRESS>:6443/apis?timeout=32s'
I0928 08:15:16.656124    6540 round_trippers.go:405] GET https://<IP_ADDRESS>:6443/apis?timeout=32s 200 OK in 1 milliseconds
I0928 08:15:16.656147    6540 round_trippers.go:411] Response Headers:
I0928 08:15:16.656156    6540 round_trippers.go:414]     Content-Type: application/json
I0928 08:15:16.656164    6540 round_trippers.go:414]     Content-Length: 3609
I0928 08:15:16.656172    6540 round_trippers.go:414]     Date: Fri, 28 Sep 2018 00:15:16 GMT
I0928 08:15:16.656234    6540 request.go:897] Response Body: {"kind":"APIGroupList","apiVersion":"v1","groups":[{"name":"apiregistration.k8s.io","versions":[{"groupVersion":"apiregistration.k8s.io/v1","version":"v1"},{"groupVersion":"apiregistration.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"apiregistration.k8s.io/v1","version":"v1"}},{"name":"extensions","versions":[{"groupVersion":"extensions/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"extensions/v1beta1","version":"v1beta1"}},{"name":"apps","versions":[{"groupVersion":"apps/v1","version":"v1"},{"groupVersion":"apps/v1beta2","version":"v1beta2"},{"groupVersion":"apps/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"apps/v1","version":"v1"}},{"name":"events.k8s.io","versions":[{"groupVersion":"events.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"events.k8s.io/v1beta1","version":"v1beta1"}},{"name":"authentication.k8s.io","versions":[{"groupVersion":"authentication.k8s.io/v1","version":"v1"},{"groupVersion":"authentication.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"authentication.k8s.io/v1","version":"v1"}},{"name":"authorization.k8s.io","versions":[{"groupVersion":"authorization.k8s.io/v1","version":"v1"},{"groupVersion":"authorization.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"authorization.k8s.io/v1","version":"v1"}},{"name":"autoscaling","versions":[{"groupVersion":"autoscaling/v1","version":"v1"},{"groupVersion":"autoscaling/v2beta1","version":"v2beta1"}],"preferredVersion":{"groupVersion":"autoscaling/v1","version":"v1"}},{"name":"batch","versions":[{"groupVersion":"batch/v1","version":"v1"},{"groupVersion":"batch/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"batch/v1","version":"v1"}},{"name":"certificates.k8s.io","versions":[{"groupVersion":"certificates.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"certificates.k8s.io/v1beta1","version":"v1beta1"}},{"name":"networking.k8s.io","versions":[{"groupVersion":"networking.k8s.io/v1","version":"v1"}],"preferredVersion":{"groupVersion":"networking.k8s.io/v1","version":"v1"}},{"name":"policy","versions":[{"groupVersion":"policy/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"policy/v1beta1","version":"v1beta1"}},{"name":"rbac.authorization.k8s.io","versions":[{"groupVersion":"rbac.authorization.k8s.io/v1","version":"v1"},{"groupVersion":"rbac.authorization.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"rbac.authorization.k8s.io/v1","version":"v1"}},{"name":"storage.k8s.io","versions":[{"groupVersion":"storage.k8s.io/v1","version":"v1"},{"groupVersion":"storage.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"storage.k8s.io/v1","version":"v1"}},{"name":"admissionregistration.k8s.io","versions":[{"groupVersion":"admissionregistration.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"admissionregistration.k8s.io/v1beta1","version":"v1beta1"}},{"name":"apiextensions.k8s.io","versions":[{"groupVersion":"apiextensions.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"apiextensions.k8s.io/v1beta1","version":"v1beta1"}},{"name":"scheduling.k8s.io","versions":[{"groupVersion":"scheduling.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"scheduling.k8s.io/v1beta1","version":"v1beta1"}},{"name":"metrics.k8s.io","versions":[{"groupVersion":"metrics.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"metrics.k8s.io/v1beta1","version":"v1beta1"}}]}
I0928 08:15:16.656873    6540 round_trippers.go:386] curl -k -v -XGET  -H "Accept: application/json, /" -H "User-Agent: kubectl/v1.11.3 (linux/amd64) kubernetes/a452946" 'https://<IP_ADDRESS>:6443/apis/metrics.k8s.io/v1beta1/namespaces/default/pods'
I0928 08:15:16.660780    6540 round_trippers.go:405] GET https://<IP_ADDRESS>:6443/apis/metrics.k8s.io/v1beta1/namespaces/default/pods 200 OK in 3 milliseconds
I0928 08:15:16.660803    6540 round_trippers.go:411] Response Headers:
I0928 08:15:16.660812    6540 round_trippers.go:414]     Content-Type: application/json
I0928 08:15:16.660820    6540 round_trippers.go:414]     Date: Fri, 28 Sep 2018 00:15:16 GMT
I0928 08:15:16.660827    6540 round_trippers.go:414]     Content-Length: 154
I0928 08:15:16.660905    6540 request.go:897] Response Body: {"kind":"PodMetricsList","apiVersion":"metrics.k8s.io/v1beta1","metadata":{"selfLink":"/apis/metrics.k8s.io/v1beta1/namespaces/default/pods"},"items":[]}
I0928 08:15:16.662193    6540 round_trippers.go:386] curl -k -v -XGET  -H "Accept: application/json, /" -H "User-Agent: kubectl/v1.11.3 (linux/amd64) kubernetes/a452946" 'https://<IP_ADDRESS>:6443/api/v1/namespaces/default/pods'
I0928 08:15:16.664832    6540 round_trippers.go:405] GET https://<IP_ADDRESS>:6443/api/v1/namespaces/default/pods 200 OK in 2 milliseconds
I0928 08:15:16.664854    6540 round_trippers.go:411] Response Headers:
I0928 08:15:16.664863    6540 round_trippers.go:414]     Content-Type: application/json
I0928 08:15:16.664871    6540 round_trippers.go:414]     Content-Length: 2528
I0928 08:15:16.664879    6540 round_trippers.go:414]     Date: Fri, 28 Sep 2018 00:15:16 GMT
I0928 08:15:16.664924    6540 request.go:897] Response Body: {"kind":"PodList","apiVersion":"v1","metadata":{"selfLink":"/api/v1/namespaces/default/pods","resourceVersion":"2025259"},"items":[{"metadata":{"name":"nginx-deployment-67594d6bf6-j6f8t","generateName":"nginx-deployment-67594d6bf6-","namespace":"default","selfLink":"/api/v1/namespaces/default/pods/nginx-deployment-67594d6bf6-j6f8t","uid":"55c40a45-bca3-11e8-b127-5254005d94fe","resourceVersion":"2011573","creationTimestamp":"2018-09-20T07:03:53Z","labels":{"app":"nginx","pod-template-hash":"2315082692"},"ownerReferences":[{"apiVersion":"apps/v1","kind":"ReplicaSet","name":"nginx-deployment-67594d6bf6","uid":"55c20d7d-bca3-11e8-b127-5254005d94fe","controller":true,"blockOwnerDeletion":true}]},"spec":{"volumes":[{"name":"default-token-7c6q7","secret":{"secretName":"default-token-7c6q7","defaultMode":420}}],"containers":[{"name":"nginx","image":"nginx:1.7.9","ports":[{"containerPort":80,"protocol":"TCP"}],"resources":{},"volumeMounts":[{"name":"default-token-7c6q7","readOnly":true,"mountPath":"/var/run/secrets/kubernetes.io/serviceaccount"}],"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"File","imagePullPolicy":"IfNotPresent"}],"restartPolicy":"Always","terminationGracePeriodSeconds":30,"dnsPolicy":"ClusterFirst","serviceAccountName":"default","serviceAccount":"default","nodeName":"node1","securityContext":{},"schedulerName":"default-scheduler","tolerations":[{"key":"node.kubernetes.io/not-ready","operator":"Exists","effect":"NoExecute","tolerationSeconds":300},{"key":"node.kubernetes.io/unreachable","operator":"Exists","effect":"NoExecute","tolerationSeconds":300}]},"status":{"phase":"Running","conditions":[{"type":"Initialized","status":"True","lastProbeTime":null,"lastTransitionTime":"2018-09-20T07:02:52Z"},{"type":"Ready","status":"True","lastProbeTime":null,"lastTransitionTime":"2018-09-20T07:03:03Z"},{"type":"ContainersReady","status":"True","lastProbeTime":null,"lastTransitionTime":null},{"type":"PodScheduled","status":"True","lastProbeTime":null,"lastTransitionTime":"2018-09-20T07:03:53Z"}],"hostIP":"<IP_ADDRESS>","podIP":"<IP_ADDRESS>","startTime":"2018-09-20T07:02:52Z","containerStatuses":[{"name":"nginx","state":{"running":{"startedAt":"2018-09-20T07:03:03Z"}},"lastState":{},"ready":true,"restartCount":0,"image":"nginx:1.7.9","imageID":"docker-pullable://nginx@sha256:e3456c851a152494c3e4ff5fcc26f240206abac0c9d794affb40e0714846c451","containerID":"docker://e77ddbc67b85255da837eb7dadea9f77738771f8b8f37e31413346e1f2083876"}],"qosClass":"BestEffort"}}]}
W0928 08:15:16.673658    6540 top_pod.go:263] Metrics not available for pod default/nginx-deployment-67594d6bf6-j6f8t, age: 185h11m23.67363172s
F0928 08:15:16.673759    6540 helpers.go:119] error: Metrics not available for pod default/nginx-deployment-67594d6bf6-j6f8t, age: 185h11m23.67363172s

kubectl top pods is very brittle to missing metrics, and bad a reporting errors.  I suspect that's what's going on here, since it looks like we're getting a metrics response, just with no metrics in it.  Check the logs for metrics server.

I have the same exact issue. when I fire the command top pods --v=10 as follows
W1120 09:52:37.253254   16122 top_pod.go:192] Metrics not available for pod default/nginx-7587c6fdb6-t6ptl, age: 19h58m38.253245613s
F1120 09:52:37.253279   16122 helpers.go:119] error: Metrics not available for pod default/nginx-7587c6fdb6-t6ptl, age: 19h58m38.253245613s
I extracted the metrics server logs and here is what it says
-bash-4.2# kubectl -n kube-system logs $(kubectl get pods --namespace=kube-system -l k8s-app=metrics-server -o name)
I1120 17:49:34.291211       1 serving.go:273] Generated self-signed cert (apiserver.local.config/certificates/apiserver.crt, apiserver.local.config/certificates/apiserver.key)
W1120 17:50:04.800279       1 authentication.go:245] Unable to get configmap/extension-apiserver-authentication in kube-system.  Usually fixed by 'kubectl create rolebinding -n kube-system ROLE_NAME --role=extension-apiserver-authentication-reader --serviceaccount=YOUR_NS:YOUR_SA'
Error: Get https://<IP_ADDRESS>:443/api/v1/namespaces/kube-system/configmaps/extension-apiserver-authentication: dial tcp <IP_ADDRESS>:443: i/o timeout
Usage:
[flags]
Flags:
--alsologtostderr                                         log to standard error as well as files
--authentication-kubeconfig string                        kubeconfig file pointing at the 'core' kubernetes server with enough rights to create tokenaccessreviews.authentication.k8s.io.
--authentication-skip-lookup                              If false, the authentication-kubeconfig will be used to lookup missing authentication configuration from the cluster.
--authentication-token-webhook-cache-ttl duration         The duration to cache responses from the webhook token authenticator. (default 10s)
--authorization-kubeconfig string                         kubeconfig file pointing at the 'core' kubernetes server with enough rights to create  subjectaccessreviews.authorization.k8s.io.
--authorization-webhook-cache-authorized-ttl duration     The duration to cache 'authorized' responses from the webhook authorizer. (default 10s)
--authorization-webhook-cache-unauthorized-ttl duration   The duration to cache 'unauthorized' responses from the webhook authorizer. (default 10s)
--bind-address ip                                         The IP address on which to listen for the --secure-port port. The associated interface(s) must be reachable by the rest of the cluster, and by CLI/web clients. If blank, all interfaces will be used (<IP_ADDRESS> for all IPv4 interfaces and :: for all IPv6 interfaces). (default <IP_ADDRESS>)
--cert-dir string                                         The directory where the TLS certs are located. If --tls-cert-file and --tls-private-key-file are provided, this flag will be ignored. (default "apiserver.local.config/certificates")
--client-ca-file string                                   If set, any request presenting a client certificate signed by one of the authorities in the client-ca-file is authenticated with an identity corresponding to the CommonName of the client certificate.
--contention-profiling                                    Enable lock contention profiling, if profiling is enabled
--enable-swagger-ui                                       Enables swagger ui on the apiserver at /swagger-ui
-h, --help                                                    help for this command
--http2-max-streams-per-connection int                    The limit that the server gives to clients for the maximum number of streams in an HTTP/2 connection. Zero means to use golang's default.
--kubeconfig string                                       The path to the kubeconfig used to connect to the Kubernetes API server and the Kubelets (defaults to in-cluster config)
--kubelet-insecure-tls                                    Do not verify CA of serving certificates presented by Kubelets.  For testing purposes only.
--kubelet-port int                                        The port to use to connect to Kubelets (defaults to 10250) (default 10250)
--kubelet-preferred-address-types strings                 The priority of node address types to use when determining which address to use to connect to a particular node (default [Hostname,InternalDNS,InternalIP,ExternalDNS,ExternalIP])
--log-flush-frequency duration                            Maximum number of seconds between log flushes (default 5s)
--log_backtrace_at traceLocation                          when logging hits line file:N, emit a stack trace (default :0)
--log_dir string                                          If non-empty, write log files in this directory
--logtostderr                                             log to standard error instead of files (default true)
--metric-resolution duration                              The resolution at which metrics-server will retain metrics. (default 1m0s)
--profiling                                               Enable profiling via web interface host:port/debug/pprof/ (default true)
--requestheader-allowed-names strings                     List of client certificate common names to allow to provide usernames in headers specified by --requestheader-username-headers. If empty, any client certificate validated by the authorities in --requestheader-client-ca-file is allowed.
--requestheader-client-ca-file string                     Root certificate bundle to use to verify client certificates on incoming requests before trusting usernames in headers specified by --requestheader-username-headers. WARNING: generally do not depend on authorization being already done for incoming requests.
--requestheader-extra-headers-prefix strings              List of request header prefixes to inspect. X-Remote-Extra- is suggested. (default [x-remote-extra-])
--requestheader-group-headers strings                     List of request headers to inspect for groups. X-Remote-Group is suggested. (default [x-remote-group])
--requestheader-username-headers strings                  List of request headers to inspect for usernames. X-Remote-User is common. (default [x-remote-user])
--secure-port int                                         The port on which to serve HTTPS with authentication and authorization. If 0, don't serve HTTPS at all. (default 443)
--stderrthreshold severity                                logs at or above this threshold go to stderr (default 2)
--tls-cert-file string                                    File containing the default x509 Certificate for HTTPS. (CA cert, if any, concatenated after server cert). If HTTPS serving is enabled, and --tls-cert-file and --tls-private-key-file are not provided, a self-signed certificate and key are generated for the public address and saved to the directory specified by --cert-dir.
--tls-cipher-suites strings                               Comma-separated list of cipher suites for the server. If omitted, the default Go cipher suites will be use.  Possible values: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_RC4_128_SHA,TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_RC4_128_SHA,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_RC4_128_SHA
--tls-min-version string                                  Minimum TLS version supported. Possible values: VersionTLS10, VersionTLS11, VersionTLS12
--tls-private-key-file string                             File containing the default x509 private key matching --tls-cert-file.
--tls-sni-cert-key namedCertKey                           A pair of x509 certificate and private key file paths, optionally suffixed with a list of domain patterns which are fully qualified domain names, possibly with prefixed wildcard segments. If no domain patterns are provided, the names of the certificate are extracted. Non-wildcard matches trump over wildcard matches, explicit domain patterns trump over extracted names. For multiple key/certificate pairs, use the --tls-sni-cert-key multiple times. Examples: "example.crt,example.key" or "foo.crt,foo.key:*.foo.com,foo.com". (default [])
-v, --v Level                                                 log level for V logs
--vmodule moduleSpec                                      comma-separated list of pattern=N settings for file-filtered logging
panic: Get https://<IP_ADDRESS>:443/api/v1/namespaces/kube-system/configmaps/extension-apiserver-authentication: dial tcp <IP_ADDRESS>:443: i/o timeout
goroutine 1 [running]:
main.main()
/go/src/github.com/kubernetes-incubator/metrics-server/cmd/metrics-server/metrics-server.go:39 +0x13b

It looks like your metrics-serer is having trouble connecting to the Kube API server.  Make sure pods can contact the Kubernetes API server.

i have the same problem, please route me how to make sure the metrics-server connecting to kube API server.

i have the same problem.when i install master and node in the same node, metrics-server works well.but when i install master in a node and node in another, the metircs-server can't work.
apiserver logs:
Dec 25 20:32:44 controller212 kube-apiserver[11177]: E1225 20:32:44.467662   11177 controller.go:111] loading OpenAPI spec for "v1beta1.metrics.k8s.io" failed with: failed to retrieve openAPI spec, http error: ResponseCode: 503, Body: service unavailable

kubectl describe apiservice logs:
Name:         v1beta1.metrics.k8s.io
Namespace:
Labels:       addonmanager.kubernetes.io/mode=Reconcile
              kubernetes.io/cluster-service=true
Annotations:  kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"apiregistration.k8s.io/v1beta1","kind":"APIService","metadata":{"annotations":{},"labels":{"addonmanager.kubernetes.io/mode":"Reconcile"...
API Version:  apiregistration.k8s.io/v1
Kind:         APIService
Metadata:
  Creation Timestamp:  2018-12-25T11:58:26Z
  Resource Version:    587
  Self Link:           /apis/apiregistration.k8s.io/v1/apiservices/v1beta1.metrics.k8s.io
  UID:                 62df430e-083c-11e9-b033-52540068bc4e
Spec:
  Ca Bundle:                 <nil>
  Group:                     metrics.k8s.io
  Group Priority Minimum:    100
  Insecure Skip TLS Verify:  true
  Service:
    Name:            metrics-server
    Namespace:       kube-system
  Version:           v1beta1
  Version Priority:  100
Status:
  Conditions:
    Last Transition Time:  2018-12-25T11:58:26Z
    Message:               no response from https://<IP_ADDRESS>:443: Get https://<IP_ADDRESS>:443: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
    Reason:                FailedDiscoveryCheck
    Status:                False
    Type:                  Available
Events:                    <none>

and i have set --enable-aggregator-routing=true
in the master ,ping pod's ip is unreachable.
what should i do to resolve that?

Check your networking and firewall exception rules. One of the two could break down the communication between master and node.
In my case disabled firewall was a culprit so I enabled it and added the  exceptions and it worked.
Akshaya
On Dec 25, 2018, 4:10 AM, at 4:10 AM, Luzhenxing<EMAIL_ADDRESS>wrote:

i have the same problem.when i install master and node in the same
node, metrics-server works well.but when i install master in a node and
node in another, the metircs-server can't work.
apiserver logs:
Dec 25 20:32:44 controller212 kube-apiserver[11177]: E1225
20:32:44.467662   11177 controller.go:111] loading OpenAPI spec for
"v1beta1.metrics.k8s.io" failed with: failed to retrieve openAPI spec,
http error: ResponseCode: 503, Body: service unavailable

kubectl describe apiservice logs:
Name:         v1beta1.metrics.k8s.io
Namespace:
Labels:       addonmanager.kubernetes.io/mode=Reconcile
             kubernetes.io/cluster-service=true
Annotations:
kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"apiregistration.k8s.io/v1beta1","kind":"APIService","metadata":{"annotations":{},"labels":{"addonmanager.kubernetes.io/mode":"Reconcile"...
API Version:  apiregistration.k8s.io/v1
Kind:         APIService
Metadata:
 Creation Timestamp:  2018-12-25T11:58:26Z
 Resource Version:    587
Self Link:
/apis/apiregistration.k8s.io/v1/apiservices/v1beta1.metrics.k8s.io
 UID:                 62df430e-083c-11e9-b033-52540068bc4e
Spec:
 Ca Bundle:                 <nil>
 Group:                     metrics.k8s.io
 Group Priority Minimum:    100
 Insecure Skip TLS Verify:  true
 Service:
   Name:            metrics-server
   Namespace:       kube-system
 Version:           v1beta1
 Version Priority:  100
Status:
 Conditions:
   Last Transition Time:  2018-12-25T11:58:26Z
Message:               no response from https://<IP_ADDRESS>:443: Get
https://<IP_ADDRESS>:443: net/http: request canceled while waiting for
connection (Client.Timeout exceeded while awaiting headers)
   Reason:                FailedDiscoveryCheck
   Status:                False
   Type:                  Available
Events:                    <none>

and i have set --enable-aggregator-routing=true
in the master ,ping pod's ip is unreachable.
what should i do to resolve that?
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/kubernetes-incubator/metrics-server/issues/140#issuecomment-449845321

Check your networking and firewall exception rules. One of the two could break down the communication between master and node.
In my case disabled firewall was a culprit so I enabled it and added the  exceptions and it worked.
Akshaya
…

Can you please mention what exceptions did you add in the firewall ?

metrics-server is not working, too.
Here is my logs:
root@kube-master:~# kubectl get pods -n kube-system -o wide
NAME                                   READY   STATUS    RESTARTS   AGE   IP            NODE            NOMINATED NODE   READINESS GATES
coredns-86c58d9df4-29w6q               1/1     Running   0          18h   <IP_ADDRESS>    kube-worker-3   <none>           <none>
coredns-86c58d9df4-4vtw9               1/1     Running   0          18h   <IP_ADDRESS>    kube-worker-2   <none>           <none>
etcd-kube-master                       1/1     Running   0          18h   <IP_ADDRESS>    kube-master     <none>           <none>
kube-apiserver-kube-master             1/1     Running   0          18h   <IP_ADDRESS>    kube-master     <none>           <none>
kube-controller-manager-kube-master    1/1     Running   0          18h   <IP_ADDRESS>    kube-master     <none>           <none>
kube-flannel-ds-amd64-22fpg            1/1     Running   0          18h   <IP_ADDRESS>   kube-worker-3   <none>           <none>
kube-flannel-ds-amd64-hcbmp            1/1     Running   0          18h   <IP_ADDRESS>    kube-worker-1   <none>           <none>
kube-flannel-ds-amd64-m75cr            1/1     Running   0          18h   <IP_ADDRESS>    kube-worker-2   <none>           <none>
kube-flannel-ds-amd64-p4q67            1/1     Running   0          18h   <IP_ADDRESS>    kube-master     <none>           <none>
kube-proxy-2vvgv                       1/1     Running   0          18h   <IP_ADDRESS>    kube-master     <none>           <none>
kube-proxy-67bbz                       1/1     Running   0          18h   <IP_ADDRESS>    kube-worker-1   <none>           <none>
kube-proxy-m29cs                       1/1     Running   0          18h   <IP_ADDRESS>    kube-worker-2   <none>           <none>
kube-proxy-v5ws9                       1/1     Running   0          18h   <IP_ADDRESS>   kube-worker-3   <none>           <none>
kube-scheduler-kube-master             1/1     Running   0          18h   <IP_ADDRESS>    kube-master     <none>           <none>
kubernetes-dashboard-57df4db6b-9wzvv   1/1     Running   0          17h   <IP_ADDRESS>    kube-worker-1   <none>           <none>
metrics-server-fc6d4999b-hsmkp         1/1     Running   0          11m   <IP_ADDRESS>    kube-worker-2   <none>           <none>

root@kube-master:~# kubectl logs pod/metrics-server-fc6d4999b-hsmkp -n kube-system
I0314 04:21:04.809739       1 serving.go:273] Generated self-signed cert (apiserver.local.config/certificates/apiserver.crt, apiserver.local.config/certificates/apiserver.key)
[restful] 2019/03/14 04:21:05 log.go:33: [restful/swagger] listing is available at https://:443/swaggerapi
[restful] 2019/03/14 04:21:05 log.go:33: [restful/swagger] https://:443/swaggerui/ is mapped to folder /swagger-ui/
I0314 04:21:05.504136       1 serve.go:96] Serving securely on [::]:443
E0314 04:22:05.509729       1 manager.go:102] unable to fully collect metrics: [unable to fully scrape metrics from source kubelet_summary:kube-worker-2: unable to fetch metrics from Kubelet kube-worker-2 (kube-worker-2): Get https://kube-worker-2:10250/stats/summary/: x509: certificate is valid for kube-master, not kube-worker-2, unable to fully scrape metrics from source kubelet_summary:kube-worker-3: unable to fetch metrics from Kubelet kube-worker-3 (kube-worker-3): Get https://kube-worker-3:10250/stats/summary/: x509: certificate is valid for kube-master, not kube-worker-3, unable to fully scrape metrics from source kubelet_summary:kube-worker-1: unable to fetch metrics from Kubelet kube-worker-1 (kube-worker-1): Get https://kube-worker-1:10250/stats/summary/: x509: certificate is valid for kube-master, not kube-worker-1, unable to fully scrape metrics from source kubelet_summary:kube-master: unable to fetch metrics from Kubelet kube-master (kube-master): Get https://kube-master:10250/stats/summary/: x509: certificate signed by unknown authority]
E0314 04:23:05.511074       1 manager.go:102] unable to fully collect metrics: [unable to fully scrape metrics from source kubelet_summary:kube-worker-2: unable to fetch metrics from Kubelet kube-worker-2 (kube-worker-2): Get https://kube-worker-2:10250/stats/summary/: x509: certificate is valid for kube-master, not kube-worker-2, unable to fully scrape metrics from source kubelet_summary:kube-master: unable to fetch metrics from Kubelet kube-master (kube-master): Get https://kube-master:10250/stats/summary/: x509: certificate signed by unknown authority, unable to fully scrape metrics from source kubelet_summary:kube-worker-1: unable to fetch metrics from Kubelet kube-worker-1 (kube-worker-1): Get https://kube-worker-1:10250/stats/summary/: x509: certificate is valid for kube-master, not kube-worker-1, unable to fully scrape metrics from source kubelet_summary:kube-worker-3: unable to fetch metrics from Kubelet kube-worker-3 (kube-worker-3): Get https://kube-worker-3:10250/stats/summary/: x509: certificate is valid for kube-master, not kube-worker-3]
E0314 04:24:05.489510       1 manager.go:102] unable to fully collect metrics: [unable to fully scrape metrics from source kubelet_summary:kube-worker-2: unable to fetch metrics from Kubelet kube-worker-2 (kube-worker-2): Get https://kube-worker-2:10250/stats/summary/: x509: certificate is valid for kube-master, not kube-worker-2, unable to fully scrape metrics from source kubelet_summary:kube-worker-3: unable to fetch metrics from Kubelet kube-worker-3 (kube-worker-3): Get https://kube-worker-3:10250/stats/summary/: x509: certificate is valid for kube-master, not kube-worker-3, unable to fully scrape metrics from source kubelet_summary:kube-master: unable to fetch metrics from Kubelet kube-master (kube-master): Get https://kube-master:10250/stats/summary/: x509: certificate signed by unknown authority, unable to fully scrape metrics from source kubelet_summary:kube-worker-1: unable to fetch metrics from Kubelet kube-worker-1 (kube-worker-1): Get https://kube-worker-1:10250/stats/summary/: x509: certificate is valid for kube-master, not kube-worker-1]
E0314 04:25:05.512460       1 manager.go:102] unable to fully collect metrics: [unable to fully scrape metrics from source kubelet_summary:kube-worker-2: unable to fetch metrics from Kubelet kube-worker-2 (kube-worker-2): Get https://kube-worker-2:10250/stats/summary/: x509: certificate is valid for kube-master, not kube-worker-2, unable to fully scrape metrics from source kubelet_summary:kube-master: unable to fetch metrics from Kubelet kube-master (kube-master): Get https://kube-master:10250/stats/summary/: x509: certificate signed by unknown authority, unable to fully scrape metrics from source kubelet_summary:kube-worker-3: unable to fetch metrics from Kubelet kube-worker-3 (kube-worker-3): Get https://kube-worker-3:10250/stats/summary/: x509: certificate is valid for kube-master, not kube-worker-3, unable to fully scrape metrics from source kubelet_summary:kube-worker-1: unable to fetch metrics from Kubelet kube-worker-1 (kube-worker-1): Get https://kube-worker-1:10250/stats/summary/: x509: certificate is valid for kube-master, not kube-worker-1]

My cluster has 1 master & 3 workers, deployed using kubeadm.

I am having this issue too. when I try to curl from a pod I get a 403


got error when running the code

**/gnas-main/mmdet/models/roi_heads/nas_bbox_heads/cell_fc_bbox_head.py", line 50, in init
super().init(*args, init_cfg=init_cfg, kwargs)
TypeError: init() got an unexpected keyword argument 'num_cls_cells'
thanks for your contributions to open sourcing the code.
i just download this repo and change the dataset_root. Is this my problem or something else?

I also got the same error, how did you fix it please? Thanks

I got the same error.

The bug is fixed. Thank you.


Update concept-deep-learning-vs-machine-learning.md

I have updated the document and made a few improvements.

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/Microsoft/azure-docs/blob/master/articles/azure-portal-overview.md
Private repo URL: https://github.com/Microsoft/azure-docs-pr/blob/master/articles/azure-portal-overview.md
We have closed this pull request. Please resubmit the updates through the private repo. If you need perms to the private repo, see the contributor guide instructions

#sign-off


Consider rethinking dependencies and post install script

Semantic UI currently makes the assumption that the dev will npm install semantic-ui, go through the build process, and use the resulting files.
However, if the dev already has their own build solutions in place and wants to use semantic-ui's source files directly, this doesn't necessarily work very well.
For example, we use Webpack, alongside Gulp. Therefore, what I want to do is npm install semantic-ui --save-dev and then require the source files directly. However, the post-install script forces me to go through a build step I don't want. (yes, I could npm install --ignore-scripts, but then I'd have to every time).
Along the same lines, if I'm using my own frontend tooling, then much of what is listed as a peerDependencies and dependencies may conflict.
E.g., when I run npm install semantic-ui --ignore-scripts:
npm ERR! peerinvalid The package gulp-plumber does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>
I think those would be better served as devDependencies (or maybe optionalDependencies).
Thoughts?

We run separate parity repos semantic-ui-less and semantic-ui-css which provide the same structure without any of the build tools.

Thanks, I didn't realize those repos existed.
And I see now that it appears that all of the JS components have their own repo as well, so we should be able to pull directly from those.

Yes the build script for pushing those repos is quite hilarious.

Hah! well I'm glad you do it. Just what I was looking for. Thanks a ton.


Improvement of custom query examples

"Neurospace" example is extended with a nested query and multiple results returned by custom matching
A unit test example from test_custom_space is tweaked to support multiple matching results as well to be less misleading

I wonder why ci suddenly failed on the irrelevant change in a different place
---- atom::matcher::test::match_variable_with_unique_itself stdout ----
thread 'atom::matcher::test::match_variable_with_unique_itself' panicked at '(left == right some order)
  left: [{ $x = $x#3, $z <- (B $x#3) }]
 right: [{ $x = $x#1, $z <- (B $x#1) }]', src/atom/matcher.rs:1170:9

The test failure is very strange, as it's in a lib (Rust core) test, but neither this PR, nor https://github.com/trueagi-io/hyperon-experimental/pull/399 touches lib at all, and lib is the first thing to be built and tested.
When we got a spurious break in the past it was because of a tool chain upgrade, but that doesn't feel likely in this case.

Re-running tests with no changes whatsoever now succeeds.  I don't like intermittent bugs, but I think we just have to wait and see if this pops up again.


Add ability to update AWS resource tags for SM and PS syncs

Dependent on https://github.com/DopplerHQ/server/pull/7004
@nmanoogian I did not test this locally - I'd appreciate it if you gave it a quick check 🙏

@nmanoogian Could you merge this and release the Terraform provider when you get a chance please?


版本信息
System:
    OS: macOS 14.4.1
    CPU: (8) arm64 Apple M1
    Memory: 100.30 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Browsers:
    Chrome: 116.0.5845.187
    Safari: 17.4.1
  npmPackages:
    rspress: ^1.17.1 => 1.17.1

问题详情

复现链接
无
复现步骤
rspress.config.ts文件中配置sociallinks为图片链接时，比如{
icon: 'qq',
mode: 'img',
content: '/qq-group.png',
},
图片会非常小，导致二维码看不清。

https://github.com/web-infra-dev/rspress/blob/3a8251f61dc1332f47ac4027e83cd3f7b401c9b2/packages/theme-default/src/components/SocialLinks/LinkContent.tsx#L66-L90
看了下LinkContent 设置图片大小的值为w-[50px] h-[50px]
根据单一的需求去修改img的形式不是很友好。
这里感觉有必要扩充渲染dom形式 由使用者传入自定义内容。

@Timeless0911   Can LinkContent be extended like this, I'm not sure if it will affect other features. One more thing, I didn't find a unit test to test this pr

@h7ml I think for the image scenario, we only need to add a classname, such as rspress-social-links-img, so that users can customize its style?

@h7ml I think for the image scenario, we only need to add a classname, such as rspress-social-links-img, so that users can customize its style?

If you do this, will you pass classname directly to resolve it, or will there be a certain limited scope, such as using the style within the component?
I think it's better to expand to dom. There are no restrictions on this use

@h7ml  I agree with your idea, I wonder if 50px is too small for the img scene, maybe we can make it larger by default?

@h7ml I agree with your idea, I wonder if 50px is too small for the img scene, maybe we can make it larger by default?

Increasing the default size of the image in the LinkContent component from 50px to a larger size sounds like a good idea if you think 50px is too small. You can adjust the size as per your requirements.


Bind mount /oem in elemental-setup-initramfs

Bind /oem into /sysroot/oem when running elemental-setup-initramfs to enable running initramfs stages from config files in oem partition.

Codecov Report
Attention: 7 lines in your changes are missing coverage. Please review.

Comparison is base (2e18efa) 73.83% compared to head (c1a87f5) 73.85%.
Report is 2 commits behind head on main.

Files
Patch %
Lines

pkg/bootloader/grub.go
89.18%
3 Missing and 1 partial :warning:

pkg/action/upgrade.go
57.14%
2 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1912      +/-   ##
==========================================
+ Coverage   73.83%   73.85%   +0.02%
==========================================
  Files          71       71
  Lines        7773     7779       +6
==========================================
+ Hits         5739     5745       +6
- Misses       1612     1613       +1
+ Partials      422      421       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


No way to Ignore devDependencies?

This is a question as much as anything, and I'm hoping you're just going to tell me that I'm doing it wrong.
If I try to use flow check on even a very simple NPM library with just one dependency it's unusably slow (~13secs) because of all the devDependencies I'm using. If I add .*/node_modules* to the ignore section of .flowconfig than it becomes much faster (~1sec), but fails because it can't find the single non dev-dependency, showing this message:
/home/dominicc/git-dev/fell/src/Log.js:4:15,30: emitr
Required module not found

Adding entries to the include section to counter this doesn't seem to help, regardless of how I do it. Given that this isn't very sustainable either (you'd essentially have to maintain two dependency manifests), is there a better way of ignoring devDependencies to improve performance?

I have seen this as well, and hopefully someone else can chime in with their successful method of ignoring node_modules without hitting the missing package.json issue.
However, since performance is your problem, have you tried using the flow server instead of running flow check every time? If you just run flow, Flow will start a server, load and parse the files, and will then watch the file system, updating itself automatically. If you run flow again, it should be super fast.

However, since performance is your problem, have you tried using the flow server instead of running flow check every time?

I have, but that makes no difference for me at all (still ~13secs). I've tried running the server in both the background and foreground too, neither with any apparent effect.

That's really surprising. You start the server then just run flow (not flow check—that doesn't use the server)?

Ignore the last message. I'd misunderstood that have to run flow the second time, and not flow check! Now it's really fast even with the devDependencies in the mix. Would still be good to have an option to ignore these though for use on a CI machine, etc.

I am also having issues with this. I wish to ignore mode_modules for performance, but still be able to required npm packages.
Would be nice to be able to have flow not cover node_module/* but still recognize the existence of modules that are explicitly required or imported in code.

Glad it's not just me.
To provide some further justification for why this would be helpful in my case, consider that our developers will run the same npm test command as used on CI, so that developers never need to debug via CI, which would be hugely time consuming. Since running flow check doesn't benefit from a server running in the background, an npm test command that involves flow is slow for both developers and CI, but needn't be.

Some additional info.
I just remembered why I ignored node_modules in the first place. I use an in-browser IDE (cloud9) and my workspace has limited CPU/memory. I also use a lot of mode packages and this combo makes my environment run out of resources trying to run flow without ignoring node_modules first.
Maybe flow isn't suited for my use-case, but if you want to support these kind of scenarios, there needs to be a way to ignore node_modules but still be able to require a package.

Update for anyone having this problem and finding this issue.
It turns out flow handles these situations in a very nice way using Declarations (at least as far as my use case is concerned)
By ignoring node_modules and then adding a declaration of the required module, flow will OK it (as long as the declaration is consistent with the usage.) This is also nice in that it allows you to code to an abstraction.
An example would be:
src/test.js
/* @flow */

import { Foo } from 'foo';

export default class Bar {
    foo : Foo,
    constructor() {
        this.foo = new Foo();
    }
}

lib/foo.js
declare module foo {
    declare class Foo {
    }
}

.flowconfig
[ignore]
.*/node_modules/*.

[include]
.*/src/.*

[libs]
lib/

Another workaround:
Use a project structure like:
- package.json
- node_modules
+ libs
  + module1
    - package.json
    - node_modules
    - index.js
  - module2
  - .flowconfig

Manage your dev dependencies with the outer package.json and runtime deps with the inner package.json. Flow will ignore the dev dependencies since they are outside its scope.

@GGAlanSmithee
Note that the [include] .*/src/.*in your configuration has no effect. [ignore] takes precedence :(

@nevir I'm not sure I follow. How would [ignore] take precendence over [include] in my example? (As long as you don't have a node_modules folder in your src folder.)
I'm not sure how the config behaves as far as what takes precendence over what, but your second statement could be troublesome if [include] takes precendence. This could be solved by using the absolute path src/.* though, right?
Thinking about it, it might be best to just use absolute paths?
[ignore]
node_modules/.*

[include]
src/.*

[libs]
lib/.*

It's my understanding that every js file in your project is included by
default (I.e. in the same directory as, or a sub directory of,
.flowconfig). Adding a path to the [include]  also doesn't appear to
switch it into a white listing mode.
AFAIK the main use of [include]  is to let flow pick up files that are
outside of your project root
On Tue, Dec 29, 2015, 02:40 Alan Smithee<EMAIL_ADDRESS>wrote:

@nevir https://github.com/nevir I'm not sure I follow. How would
[ignore] take precendence over [include] in my example? (As long as you
don't have a node_modules folder in your src folder.)
I'm not sure how the config behaves as far as what takes precendence over
what, but your second statement could be troublesome if [include] takes
precendence. This could be solved by using the absolute path src/.*
though, right?
Thinking about it, it might be best to just use absolute paths?
[ignore]
node_modules/.*
[include]
src/.*
[libs]
lib/.*
—
Reply to this email directly or view it on GitHub
https://github.com/facebook/flow/issues/719#issuecomment-167763208.

Ignoring node_modules and declaring required modules works fine for me. However, using gulp-flowtype which basically runs flow on changed files automatically, flow always reports errors of missing package.json files for each declared module.
Do you know if there's a workaround for this?

Just piling on here with an example of a hacky workaround. I am auto-generating ignore rules based on my package.json. I added it to my project in this patch: https://github.com/mozilla/web-ext/pull/23/files
Because of npm module flattening these auto-generated ignore rules made the standalone flow check run twice as fast, so it seemed worth it. That's 3.5 seconds instead of 7 seconds which is a big deal for continuous integration.
I decided not to ignore all modules (and define interfaces) because I wanted to let Flow tell me when I'm missing an external module or using it wrong.

I think lazy-loading (https://github.com/facebook/flow/issues/1461) would address this better because if you opted out your test files (i.e. no @flow) then the dev-dependencies wouldn't be analyzed.

Version 0.22 should greatly improve this problem. As of that version, Flow does not parse non-@flow files, which should greatly improve cold start times for projects with large node_modules directories.
I'm going to try on my end to see, but I'd encourage everyone here to upgrade and try it out.

That sounds like it'll be a huge improvement!  I'm assuming it's still scanning all JS files under node_modules, though?

@nevir Yeah, we still check, because dependencies might be @flow—increasingly, I hope!

This is still a huge pain if you have a big node_modules directory, and not using an SSD. It is caused by the combination of these design decisions:

Flow includes node_modules dir by default
Ignores are processed AFTER includes. If you both include and ignore a file it will be ignored.

This leaves you with only ineffective solutions, since you have to explicitly blacklist modules you don't want, and cannot whitelist modules you do want.
I'm resorting to just generating a list of all node_modules using the linux ls -1 command, and including this whole list in the .flowconfig, while deleting the entries that I want.
Another, slightly more sophisticated solution to generate the ignore section with regexes is here: https://gist.github.com/lydell/ee05b5acbc1f51eea649926af956dc98

Closing in favor of https://github.com/facebook/flow/issues/869


4702 submenus should not close when mouse leaves

Still needs javascript to be global. If there is no previous table open, dropdowns doesn't work as wanted. Refresh page where no tables on screen, open beaker menu and select dropdown and hover away from it- submenu closes.

kick jenkins

kick jenkins


Title: Adding a image

Is your feature request related to a problem? Please describe.
I would like to add a image to the no project found page
Describe the solution you'd like.
I think adding an animated image would make the website more engaging
Describe alternatives you've considered.
i would like to work on this issue.
Add any other context or screenshots about the feature request here.

or  i can  create a custom text instead of that plain text there

@YadlaMani Thank you for providing your insight but it is not required as of now


Upgrade the default Amazon Corretto 8 update version to the latest

Description:
The default Amazon Corretto 8 update version defined within group_vars (e.g. [1]) is <IP_ADDRESS>. This needs to be updated to the latest (10/10/2019) update version <IP_ADDRESS>.
[1]: Default JDK in group_vars
OS, DB, other environment details and versions:
Ubuntu 18.04 LTS
Amazon Corretto 8

Fixed in https://github.com/wso2/ansible-is/pull/35. Hence, closing.


Warning in case of missing liquibase files instead of throwing an exception

Impact

[ ] Bug fix (non-breaking change which fixes expected existing functionality)
[x] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
This PR is adding support for to set up the option to whether thrown displays missing files as a warning or to keep throwing an exception as it does today based on a boolean flag set for the ChangeLog parser configuration (WARN_OR_ERROR_ON_MISSING_CHANGELOGS).
Fixes #2256
Things to be aware of

Changelog configuration added to the changelog parser to either determine to shows error as a warning or keep doing it as an exception.

Things to worry about

None

Additional Context

Nothing

The new code would definitely have to be behind an if statement based on a configurable flag. That way the standard behavior of throwing an exception can remain the default, but people can choose "just warn" instead if they want. You'd add that flag to liquibase.ChangeLogParserConfiguration with a descriptive name

The new code would definitely have to be behind an if statement based on a configurable flag. That way the standard behavior of throwing an exception can remain the default, but people can choose "just warn" instead if they want. You'd add that flag to liquibase.ChangeLogParserConfiguration with a descriptive name

Will give it a check this weekend

@nvoxland I've updated the PR based on your suggestions.
I tried to follow the IOException(FileUtil.getFileNotFoundMessage()) to lead me to locations that need change.
Please let me know if it needs enhancements ...

Hi @mhewedy,
Thanks for taking care of this change. I'm just curious about the state of this PR, is it in "Draft" state because you are expecting to commit some more changes or is it ready to review?
Thanks,
Daniel.

Hi @mhewedy, I have started reviewing your code and have left some comments/suggestions. Please let me know if you have any questions/concerns with any of them.
Thanks,
Daniel.

Hi @mhewedy, I have started reviewing your code and have left some comments/suggestions. Please let me know if you have any questions/concerns with any of them.
Thanks, Daniel.

Thansk... I will update the PR accordingly

Hi @mhewedy, I have started reviewing your code and have left some comments/suggestions. Please let me know if you have any questions/concerns with any of them.
Thanks, Daniel.

Thansk... I will update the PR accordingly

@filipelautert and @MalloD12 -
Here's what I found in my investigation of the functional test failures.

Test failures are for any Maven tests requiring a Pro license.

The test I debugged is: updateTests.updatePro (with @DataProvider(indices = {4}) to run only one Maven test case).
I stopped the test at a break point at line 121 to configure a database and populate the project.
The command I executed manually to better debug is:

mvn -X liquibase:update  -Dliquibase.propertyFile=./liquibase.properties -Dliquibase.changeLogFile=changelog.xml -Dliquibase.labels=community,pro >> mvn1039-log.txt

Looking at the logs, I can see that Liquibase Maven is not reading the license key from the provided liquibase.properties file.
[DEBUG] No configuration value for liquibase.licenseKey found
[DEBUG] No configuration value for liquibase.pro.licenseKey found

When I provide the license key in the <liquibaseProLicenseKey> property in the pom.xml file, the license is discovered, loaded and used; this makes the update pass where it failed with Pro validation errors using just the properties file.
[DEBUG] Found 'liquibase.licenseKey' configuration of 'license starting with ABwwGgQUPo'
    scoped value 'liquibase.licenseKey' of '*****'

This error is not happening with the master version of liquibase-maven-plugin. I believe the failures are related to this PR.
cc @suryaaki2

Hi @mhewedy, I just wanted to let you know I had to revert the changes we have made in the AbstractLiquibaseMojo because these changes were causing liquibase.properties files to not be set properly and it was making fail some of our functional tests suites which were executed using Liquibase MVN extension.
Changes are looking good to me. I'm going to approve this PR now but I'll move it to the code review state after doing some manual test here, so then other members of the team can review it too. I'll post my review comment afterwards.
Any comments/suggestions/feedback you might have are more than welcome. Again, thank you for your contribution! Hope we can release this change soon.

Thanks for letting me know.
Looking forward to see it merged.

Closed by mistake!

@filipelautert Any updates on this?

@filipelautert Any updates on this?

Hi @mhewedy yes, I am still working on this. On Friday after performing some manual testing with @nvoxland assistance we realised this configuration support wasn't working as expected for CreateProcedure, which would require some more changes/refactoring to do. Looking again at #2256 this configuration support seems more appropriate for include tag, and at the moment I'm working on removing current behaviour from CreateProcedure/CreateView, moving include tag logic at a higher level, plus some others refactoring. I'm expecting to push this commit today and I would very much appreciate you look at it and share any feedback/concerns you might have.
Thanks,
Daniel.

@filipelautert Any updates on this?

Hi @mhewedy yes, I am still working on this. On Friday after performing some manual testing with @nvoxland assistance we realised this configuration support wasn't working as expected for CreateProcedure, which would require some more changes/refactoring to do. Looking again at #2256 this configuration support seems more appropriate for include tag, and at the moment I'm working on removing current behaviour from CreateProcedure/CreateView, moving include tag logic at a higher level, plus some others refactoring. I'm expecting to push this commit today and I would very much appreciate you look at it and share any feedback/concerns you might have.
Thanks, Daniel.

Thanks for your update.

Hi @mhewedy,
I just want to let you know I have already pushed some changes and made some updates as I said earlier. I think these changes are good enough to fix #2256. Could you please review it and share any feedback/concerns you might have?  If there are any other change objects which might need to also follow the same logic, I think the best approach would be to address the required changes in a separate PR. If you are happy with this, as soon as all checks are green I can move to "code review" so others team members can also review this code.
Thanks,
Daniel.

So you remove the logic from everywhere and adding to DatabaseChangeLog. correct?
I see code much cleaner now and change is centralized in one place.
LGTM

So you remove the logic from everywhere and adding to DatabaseChangeLog. correct?
I see code much cleaner now and change is centralized in one place.
LGTM, Thanks!

Hi @mhewedy, yeah that is correct. Again, as I mentioned before if you guys realised later on you need this support in any other specific object, then I think the best would be to create a separate issue/PR for it.
Thanks,
Daniel.

Any updates on this?

Hi @mhewedy,
Thank you for following up on this. As you can see this PR has been approved for some members of the team, but as these changes are also impacting another of our projects we still need to get some more approval. I want to apologize for the delay this is taking. Last week has been pretty busy for some of our team members, I hope we can get their approval soon so then we can finally include this PR in one of our next releases.
Thanks,
Daniel.

Thanks for updates.
On Tue, 17 Jan 2023, 12:49 am Daniel Mallorga, @.***>
wrote:

Hi @mhewedy https://github.com/mhewedy,
Thank you for following up on this. As you can see this PR has been
approved for some members of the team, but as these changes are also
impacting another of our projects we still need to get some more approval.
I want to apologize for the delay this is taking. Last week has been pretty
busy for some of our team members, I hope we can get their approval soon so
then we can finally include this PR in one of our next releases.
Thanks,
Daniel.
—
Reply to this email directly, view it on GitHub
https://github.com/liquibase/liquibase/pull/3081#issuecomment-1384600445,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIJEYPP3YTTM7357L47XE3WSW65TANCNFSM54BGTWLA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hence this new property onMissingInclude is not exposed via SpringLiquibase, then the only option to configure in springboot project is to introduce liquibase.properties file, correct?

Hence this new property onMissingInclude is not exposed via SpringLiquibase, then the only option to configure in springboot project is to introduce liquibase.properties file, correct?

Hi @mhewedy, that's correct as far as I know that's the only way to set up this property.
Thanks, Daniel.

Thanks


Add degree of electrification

Description of the issue
This is needed for the factsheets.
Example of usage: "The degree of electrification of the heating and coling sector is about 50%".
It can refer to sectors, spatial regions, anything else?
@Ludee is this correct? This comes from your "fingerprints".
Ideas of solution
Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[ ] I already read the latest version of the workflow for this repository
[ ] The goal of this ontology is clear to me

I am aware that

[ ] every entry in the ontology should have a definition
[ ] classes should arise from concepts rather than from words

What exactly does this mean? The share of electrical energy in the energy consumption of this sector?

From oeo-dev-meeting 50:

Is it some kind of fraction value?
Conceptually similar to: RE-share is a process attribute that indicates the fraction of renewable energy related to the total energy of an energy generation or consumption process.
use case oemof: share of thermal energy produced from electrical sources (example)
input: https://www.iea.org/reports/electrification

"A degree of electrification is the fraction value / process attribute? of the electrical energy consumption on the total energy consumption."
idea: equivalent to RE-share: make a process attribute and relate to fraction value

relate to sectors, spatial regions --> axioms
object property "has degree of electrification"
related to auto-production/consumption --> tbd, even more shares to discuss
decision: continue discussion in issue

The notes say we should define it parallel to RE-share which is defined as:
RE-share is a process attribute that indicates the fraction of renewable energy related to the total energy of an energy generation or consumption process.
So what about:
When thinking about shares versus degrees I think, the first one is more a quantity value while the latter is more a process attribute.
So I propose:

~RE-share~ A degree of renewable energy is a process attribute that indicates the fraction of renewable energy related to the total energy of an energy generation or consumption process.
An degree of electrification is a process attribute that indicates the fraction of electrical energy related to the total energy of an energy generation or consumption process.

We then also add the respective quantity values:

An renewable energy share (RE-share) is a fraction value that quantifies a degree of renewable energy.
An electrical energy share is a fraction value that quantifies a degree of electrification.

@stap-m @ludee : What do you think about my proposals in the previous comment?

I agree to the idea of differenciation between quantity values and their "entity in reality", in this case process attribute. 👍
Yet, I think for users the suggested labels might be confusing, since they are not commonly used in the domain. Why not just naming the quantity values after the process attributes and add "value"? We can also work with alternative terms...

So you are proposing renewable energy share and renewable energy share value as labels?

And degree of electrification and degree of electrification value, resp.

I found out, that the term degree of electrification is also sometimes used as share of people who have access to electricity, e.g. here and here. So I would prefer using electrical energy share and electrical energy share value as this label more accurately describes what is meant with our concepts. Also the labels would be systematically in line with renewable energy share and _renewable energy share value. However, we might still use degree of electrification and degree of electrification value as alternative labels.

Ok. Is this ready for implementation then?

Ok. Is this ready for implementation then?

I think so. :rocket:


no function exports

This is just a thin wrapper, so other packages (or module) should provide more julia-like interfaces on top of SPTK.jl.


Add llama3.1-405b vLLM GKE support

Switched names to .patch.yaml for files that patch existing resources


Update OVM_L1ERC20Gateway.sol

Period added extra bit returning error then red x in view code field.
Contributing Agreement

[x] I have read and understood the Optimism Contributing Guide and Code of Conduct and am following those guidelines in this pull request.

Thanks for the contribution again :-)

Period added extra bit returning error then red x in view code field.

Could you elaborate on this? Not sure I understand.

Update OVM_L1ERC20Gateway.sol #285 showed an error(red x)when viewing the newly committed code.  This was because I included an extra bit in the form of a period where I should not have   withdrawer.
instead of                           withdrawer
✅

I think it should be ok to keep the period here.

I’m new to smart contracts and probably mistaken here lol, but from what I understand they are compiled into byte code, and from the screen shot I attached, I can see there are the 10 original bytes in withdraer.      My correction of withdrawer. of course contains 11.  Would this cause an error in recompiling and thus the red x now on the side of my contribution in the ethereum-optimism/contracts GitHub page?  If so I have offered a correction, because however small it may seem, it would feel great to have properly contributed thus having a green check indicating.  Thank you and your team for your time.  Any future discourse on the revolutionary OVM, I would feel very fortunate to participate.  Thank you again. On Wed, 3 Mar 2021 at 3:43 PM Kelvin wrote:
I think it should be ok to keep the period here.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/ethereum-optimism/contracts/pull/286#issuecomment-790081055",
"url": "https://github.com/ethereum-optimism/contracts/pull/286#issuecomment-790081055",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]


Spring Boot application hangs without any error when azure-keyvault-secrets-spring-boot-starter version upgraded from 2.1.6 to 2.1.8

Environment

Spring boot starter:

key vault spring boot starter

OS Type: Windows

Java version:

1.8

Summary
Spring Boot application hangs without any error when azure-keyvault-secrets-spring-boot-starter version upgraded from 2.1.6 to 2.1.8. Spring boot version is 2.1.10-RELEASE
Reproduce steps
Spring 2.1.10-RELEASE. Upgraded  azure-keyvault-secrets-spring-boot-starter version upgraded from 2.1.6 to 2.1.8. Same application is working in 2.1.6
Application.yml
azure:
keyvault:
uri:
client-id:
client-key:
tenant-id:
allow:
telemetry: false
Expected Results
Spring boot application up and running and get all secrets from Azure key vault
Actual Results
Spring boot app hangs

Thanks for reaching out. Could you please try again with our latest release 2.1.9?

Thanks for reaching out. Could you please try again with our latest release 2.1.9?

Hi Saragluna, Thank you for reply. Yes tried with 2.1.9  and same result

Could you help provide some more details, like the pom file of your project, for me to reproduce the issue?

I have the same issue appears to be in KeyVaultOperation.fillSecretsList()

    private void fillSecretsList() {
        try {
            this.rwLock.writeLock().lock();
            if (this.secretKeys == null || secretKeys.size() == 0) {
                this.propertyNames.clear();

                final PagedIterable<SecretProperties> secretProperties = keyVaultClient.listPropertiesOfSecrets();

               //Hangs here:
                secretProperties.forEach(s -> {
                    final String secretName = s.getName().replace(vaultUri + "/secrets/", "");
                    addSecretIfNotExist(secretName);
                });

                this.lastUpdateTime.set(System.currentTimeMillis());
            } else {
                for (final String secretKey : secretKeys) {
                    addSecretIfNotExist(secretKey);
                }
            }
            propertyNamesArr = propertyNames.toArray(new String[0]);
        } finally {
            this.rwLock.writeLock().unlock();
        }
    }

@jmax01
Thanks for your share. I will look into this.

hi @saragluna I'm having the same issue using:

Java -> 8
Spring Boot -> 2.1.2.RELEASE
Spring Azure Key Vault Secrets -> 2.1.10

I reported the issue here

Hi, @nandha2143, please update version to 2.2.5 or 2.3.2.

try
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-parent</artifactId>
        <version>2.1.7.RELEASE</version>
       <relativePath /> <!-- lookup parent from repository -->
</parent>

......

<properties>
        <java.version>1.8</java.version>
        <azure.version>2.1.6</azure.version>
 </properties>


CLUO updates node to be schedulable if pod is deleted

In a case where the CLUO update agent pod is killed or restarts on a node that is currently cordoned, it will mark the node as schedulable again. I am guessing it sees the annotations and thinks it just finished a reboot. Example below:
$ kubectl get nodes a.redacted.node
NAME                        STATUS                     AGE       VERSION
a.redacted.node             Ready,SchedulingDisabled   45d       v1.7.1+coreos.0
$ kubectl delete pod --namespace kube-system container-linux-update-agent-hc2qx
pod "container-linux-update-agent-hc2qx" deleted
$ kubectl get nodes a.redacted.node
NAME              STATUS    AGE       VERSION
a.redacted.node   Ready     45d       v1.7.1+coreos.0

When update-agent starts on a node, it unconditionally sets the node schedulable again.
It would be more correct to do this only if reboot-in-progress and reboot-needed were previously true, but  that opens up the possibility the program could crash between that checking annotations and marking the node schedulable again, potentially leaving nodes unschedulable.

It looks like #176 should solve this problem. It adds an annotation to the node if the agent was responsible for marking the node unschedulable, and the agent only marks it as schedulable again if it finds that annotation.
I'll update this bug again when a release is tagged with this fix.

v0.7.0 is released, which includes #176 and should fix this issue. See the release page for details - https://github.com/coreos/container-linux-update-operator/releases/tag/v0.7.0

Thanks for the work on this @sdemos!


Fix typo in wallet-connectors.md

What changed? Why?
"were" should be "where"
Notes to reviewers
n/a
How has it been tested?
Visually.

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1


Add DocService's docString to html view

Motivation:
Current DocService's html view doesn't contain JavaDoc string.
This is second part of adding docstring to DocService.
Modifications:
Render DocString to html view if it exists.
Result:
DocService's html output contains DocString.

This is an output example.

We currently use highlight.js to render json responses in debug page, and it seems that javascript rendering using it may produce more pleasing docstrings (@param etc would be highlighted).
What do you think about converting the raw docstrings into javadoc-ilke strings with the asterisks and using highlight.js to render?
Github renders docstring like this, I believe highlightjs would be the same.
/**
  * Basic unit of data within a ColumnFamily
  *
  * @param name, the name by which
  * @param value. The data associated
  */

Added DocString to classes and functions too.

@anuraaga , Actually, asterisks were already removed when Thrift generated json output. Thrift's json output doesn't contain asterisks. Of course, I agree highlighted doc string is better, but I'm not sure adding asterisks is good or not. I checked highlight.js, but it has no javadoc only grammar. If we want to highlight, we need to add asterisks to descriptions.

@trustin , Sorry to late. Updated it. And, it supports for functions and classes now.

Got it - anyways I think we can add this in a simple way for now and iterate on the look+feel. My feeling is that it might be worth round-tripping through add asterisks -> highlight -> remove asterisks (or maybe not) since the highlighting could help a lot, but it'd definitely need experimentation.
Mostly LGTM

@trustin , I extracted @params to fields' descriptions. Review again please~

@jongyeol Would you mind pasting the updated screenshot one last time? Thanks for your patience!

Services - Method

Classes

@trustin , I updated it with updating regexp and css things. :)

@jongyeol Merged!

Thank you!


link llvm lib dynamically and use split dwarf for smaller images

This will make llvm compile faster, take up less space, and skip building lldb.  Building llvm 10.0.0 for ubuntu 22.04 went from 7.36gb to 3.05gb.  It isn't even building with MinSizeRel, but this seems like a solid win.

Replaced by #64!


standard section overhaul

This PR for the standard section includes:

resolving grammar and styling
updating nav arrangement by not using decimals
changing huge tables into HTML for readability and easier re-arrangement
adding unified function and event declarations to smart contract descriptions
adding/resolving external links
changing headings on the menu

without the hyphen as in links
with spaces between the standard's words
(spaceless writing should refer to functions or files)

Explanation of using array[  ] instead of array[ ]:
Arrays are declared with spaces between brackets to improve clarity, but if you have more than one possible type or a small device, the second bracket gets split up with a line break. That's why we need to use the space symbol to always keep it as one object.


Are you able to give sample requests? Thanks!

@christianseptimo  can you give more details? what's sample requests you want?

Hello, Thanks for the response, we need sample requests for BookingCreate. Me and my colleague trying to use BookingCreate to book 2 different types of rooms for single hotel. We were able to figure out how to use the AvailabilitySearch, now we are trying to understand how to send a request for BookingCreate. Our understanding is that QouteID should use the ResultID from AvailabilitySearch and our understanding is that ResultID represents a single room, but what if we want to book two different rooms in a hotel?
Our guess is to use  however, your BookingCreate class looks doesn't support that. Am I right? Or if that supports it, can you give us example data to pass on that class that will book 2 different room types?

Hey @christianseptimo I'm working on documentation for the library, Are you still needing help?


plotting limits

There should be an option to set the upper and lower limit of the plotted axes.
requested by @skalbfleisch

This is also available through the built in mpl figure option.

Moved to NSLS-II/replay#18


Nothing on workflow zip？

file is empty，no json

Which workflow are you trying out?  I just tested all four workflows currently posted and they contain JSON.  You'll want to open the full size image and then drag it over into ComfyUI.

Ok, I think I got it. You mean the image contains a JSON file, and I just
need to drag the image into ComfyUI, right? I thought they were just
regular PNG images. Thank you!
Wonderflex @.***> 于 2024年9月21日周六 01:09写道：

Which workflow are you trying out? I just tested all four workflows
currently posted and they contain JSON. You'll want to open the full size
image and then drag it over into ComfyUI.
—
Reply to this email directly, view it on GitHub
https://github.com/Wonderflex/WonderflexComfyWorkflows/issues/1#issuecomment-2364160489,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGZSDREKKEHN5MGTRRLDXTDZXRJDZAVCNFSM6AAAAABOSK44YGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRUGE3DANBYHE
.
You are receiving this because you authored the thread.Message ID:
@.***>


Separate folder for MySQL functions in Database Navigator

Is your feature request related to a problem? Please describe.
MySQL "Procedures" folder is a little misleading as it includes functions as well.
Describe the solution you'd like
A separate folder for functions.
Describe alternatives you've considered
Relying on the icon to differentiate between the two.

Hello @yoni-yad2
Thanks for the idea.


these changes allow SMUI to run with mysql 8

This will fix #130 .

Current PR can not be merged to main, as it would harm backwards compatibility of existing SMUI installations. Modifying existing migrations would lead to a major version update, and can not be supported in V4 of SMUI.

Would making the jump then to MySQL 8 be worth bumping the major version to 5 then?   MySql 5.6 EOL was in 2021 and 5.7 is October 2023.    Quepid was moved to Mysql 8, and the Chorus reference implementation is kind of stuck in between.
I did find an interesting way of "patching" a 4.x SMUI to work with MySQL 8: https://github.com/querqy/chorus/pull/163/files#diff-2a301e09731b384355af3f1fe4691b51811ba84654757c2c10c2901858eb54d9

Would this then rather be a fork of SMUI to properly maintain this one instance that requires these changes?
IMO the querqy/smui main should support all clients still depending on it incl. backwards compatability of the data model.
I know it's tempting to adjust SQL migrations, but it is tampering backwards compatability. I would rather like to see a direction where changes of the database model happen in line with this requirement. Though we'd probably need to technical spike to properly find out a way forward here (i.e. skipping migrations for certain database clients, switching/migrating to an improved/varied data structure for certain tables). WDYT?

I hadn't really thought about the idea of checking the database client and using that to influence the type of migration made.   If that is a viable path forward, then great.   It "feels" like a lot of work to support old mysql versus just major version jump and telling folks to manually migrate/reimport their setups, however most important is to come up with a forward motion path and not stagnate.
I'm probably waiting for my next SMUI dayjob project to come through before I can push forward on that effort!


API responses and calls for each MS

Link to Notion page

ESTIMATED - 30 minutes
REALIZED - 30 minutes


default settings

hi ı open package and default setting not  there and bridges start ,end doesn't exist .I tried unity version 2019.1.9f1 and 2018.1.9f2 it is same on both can you help me

First off, I would recommend using FritzsHero's fork. It has several bug fixes and a few other features.
Second, the base folder needs to be named just RoadArchitect (and nothing else).
Hope that helps.

Sorry for taking ages to reply.
The main problem you are facing is that the RoadArchitect folder in your project is named RoadArchitect-1.7 instead of just RoadArchitect .
This seems to be a problem by the unitypackage, I might republish a fixed 1.7 version.
As embeddedt already stated there is a more up to date version available on his fork and my fork.
If you need RoadArchitect in a stable state, I would recommend 1.7 / 1.8 or 1.9.
If you like a experimental version you can also use my fork (wip 2.0), but it might not be fully compatible with prior version.

thank you problem solved


Update azure-sdk-build-tools Repository Resource Refs in Yaml files

Update triggered by - https://dev.azure.com/azure-sdk//internal/_build/results?buildId=3920934

Will update ref in #44727


Incorrect Mocha Global Error

http://stringjs.com/browser.test.html

This works in Safari 5.1.3 (OS X 10.7.3)
It fails in Chrome 17.0.9 (OS X 10.7.3)
Looks ugly in Firefox, but if I recall reading, Mocha only supports Webkit browsers.

Any thoughts on the Chrome/Safari discrepancy?

"Mocha only supports Webkit browsers." that's incorrect.. that's just the err.stack that FF gives you

works in chrome 17.0.9 for me

Here's what I'm getting:

Although, come to think of it... do you think that it could be some weird Chrome extension?

I was having the same issue a few days ago. It was a chrome extension... JSON Formatter.

@logicalparadox interesting... I do have that extension installed.
At the very least, the Mocha global error should be moved outside of the method then. Because it makes it look like the method cloberPrototype() is causing the error.

@jprichardson it doesn't / cannot know about anything like that, either there's a new global or there's not, so there's no way to tell in order to move it out

Ok, no problem. Thanks for responding.


Update Readme File with New feature Mobile Menu

Great Job Elijah.
Please, update your Readme file, add the new feature mobile menu using javascript

Great Job Elijah 👍
But I think you could update your new feature mobile menu by using either Google Hamburger fonts or Awesome font, This will make you write short codes.


Multi-selection of BPMN elements

Is your feature request related to a problem? Please describe.
Add ability to select more than 1 element using a rectangular selection area
Describe the solution you'd like
Multi-select with area-like selection tool

Extremely annoying when missing - hard to edit the diagram


New Model for Fake news detection(Passive Aggressive)

This is new model for detection of fake news with good accuracy rate. Easy to implement.. Sending Complete project of our new model

Hey man, any screenshots or papers published of this project. I'd love to see your implementation since you've also added HTML files in the PR


[CARBONDATA-2960] SDK Reader fix with projection columns

SDK Reader was not working when all projection columns were given.
Added exception for Complex child projections too.
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[x] Testing done

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Can one of the admins verify this patch?

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/421/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/600/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8670/

retest this please

retest this please

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/442/

add to whitelist

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/445/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8695/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/625/

LGTM


Moving logging (8) resources to v1beta1 version

Moving logging (8) resources to v1beta1 version

[ ] google_logging_billing_account_exclusion
[ ] google_logging_billing_account_sink
[ ] google_logging_folder_bucket_config
[ ] google_logging_folder_exclusion
[ ] google_logging_folder_sink
[ ] google_logging_organization_bucket_config
[ ] google_logging_organization_exclusion
[ ] google_logging_organization_sink

Extracted from https://github.com/upbound/provider-gcp/issues/150

google_logging_folder_bucket_config - need permissions to create a folder
google_logging_folder_exclusion - need permissions to create a folder
google_logging_folder_sink - need permissions to create a folder
google_logging_billing_account_exclusion - need more wide access to the billing account
Message:               observe failed: cannot run refresh: refresh failed: Error when reading or editing Logging Exclusion my-exclusion: Error retrieving logging exclusion for "billingAccounts" "015CE2-E29302-2811C2": googleapi: Error 403: Permission 'logging.exclusions.get' denied on resource

google_logging_billing_account_sink - need more wide access to the billing account
Message:               observe failed: cannot run refresh: refresh failed: Error when reading or editing Logging Exclusion my-exclusion: Error retrieving logging exclusion for "billingAccounts" "015CE2-E29302-2811C2": googleapi: Error 403: Permission 'logging.exclusions.get' denied on resource

google_logging_organization_bucket_config - need org-level permissions
Message:               observe failed: cannot run refresh: refresh failed: googleapi: Error 403: Permission 'logging.buckets.get' denied on resource

google_logging_organization_exclusion - need org-level permissions
Message:               observe failed: cannot run refresh: refresh failed: googleapi: Error 403: Permission 'logging.buckets.get' denied on resource

google_logging_organization_sink - need org-level permissions
Message:               observe failed: cannot run refresh: refresh failed: googleapi: Error 403: Permission 'logging.buckets.get' denied on resource

The following resources are configured in this PR: https://github.com/upbound/provider-gcp/pull/423

google_logging_folder_bucket_config
google_logging_folder_exclusion
google_logging_folder_sink


Error when unchecked Telegram plugin and links from ok.ru

Hi everyone. Yesterday I unchecked the Telegram plugin in the settings by unchecking the #. However this caused the plugin to not work again and I couldn't get it to work again so I had to reinstall it. So I tried putting links to my videos from my ok.ru account however it doesn't work, I guess because it needs to be implemented. Is there any chance this is possible or is some kind of internal plugin like the one from Yt or Twitch needed? Thanks. Regards.

In a few days I will be able to continue with the telegram integration and other pending tasks (fix crunchyroll, fix tv3) and I will work on integrating ok.ru as well.


minor version bump to fit pypi

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@65a15b4). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master     #55   +/-   ##
========================================
  Coverage          ?   5.22%
========================================
  Files             ?       6
  Lines             ?     651
  Branches          ?     100
========================================
  Hits              ?      34
  Misses            ?     617
  Partials          ?       0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 65a15b4...02a5f3c. Read the comment docs.


Add an item macro.

This change is

crates/cairo-lang-parser/src/parser_test_data/attribute_errors line 137 at r3 (raw file):

//! > cairo_code
#[aaa]
[bbb]

make it skipped, as discussed

Merged in https://github.com/starkware-libs/cairo/pull/3966 with a minor fix over this.


Menu bar not showing in global menu

When using KDE with global menu enabled, the app no longer has its menu bar displayed in app (this is probably okay), but the menu bar also doesn't show up in global menu (this is problematic).
I think we could either don't support global menu at all, just show a menu bar no matter what. Or, we support global menu. BTW, the usual workaround of having application menu in title bar also doesn't work. So, effectively, I don't have access to most of the settings.
This happens with both the AUR version and flatpak version.
OS: ArchLinux
KDE: 5.25.1
KDE Plasma Version: 5.95.0
Qt Version: 5.15.5
Kernel Version: 5.18.5-arch1-1
Graphics Platform: X11

duplicate of #36


ci: use standard workflow

:tada: This PR is included in version 2.2.13 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Implement Basic Web Server (Server X)

Objective: Create a basic web server using Go’s net/http package.
Tasks:

[x] Write a Go script to launch a basic web server.
[x] Implement routes/handlers for a home page.

Acceptance Criteria: Running the Go script should start a web server that responds on the homepage.

Completed


Fix convert_file_size_to_int for kilobits and megabits

Minor change to fully align this function with the recent change in Transformers (https://github.com/huggingface/transformers/pull/16891)

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


Conflict resolution for collaborative editing.

Is your feature request related to a problem? Please describe.

In the current implementation, the message received via socket connection is set as a value for the editor as well. There is no conflict resolution strategy.
For example:-
If one user types "foo" in front of "bar" and the other types "baz" after "bar" at the same time, you will notice inconsistencies.
To handle this we need some kind of conflict resolution strategy.
Demo Link

Describe the solution you'd like

There are two well-known conflict resolution algorithms that are operational transformation and CRDT.
Operational Transformation
CRDT

Motivation

Resolving conflicts in the editor to maintain consistency for all the participants of a room.

Are you willing to contribute to this issue?

Yes

Describe alternatives you've considered

These are the only conflict resolution algorithms I know of. Personally, I cant see an alternative.

Additional context

I would like to work on this issue. I have implemented Operational Transformation previously.
Can you please assign this issue to me?
This is a major change and I would suggest discussing it beforehand.

Hi @Aryaman1706, First of all, thank you so much for taking out the time to create this issue. 🚀
We will try to analyze these algorithms and will get back to you shortly, that what we can do in this scenario.
Also, @nehaparmar99, can you please look into this issue and share your reviews 🙌

So I have read more on both these algorithms to figure out which one would be better.
Links in my previous comment depicts why do we need any of them.
Here is a very nice article comparing OT with CRDT. It covers up most of the things without going into technical details of algorithms.
It basically boils down to this:

OT requires a central server to store a log of all the operations which I know expands crazy fast.
CRDT does not require a central server but the document's size increases by around 1.5x.

But we can cut out the operation logs in OT by just restricting it to a limited number and deleting all of them if there is only one active user editing the document.
I would love to discuss it further.
Thank You.

@Aryaman1706 I went through both of these algorithms and they are pretty amazing.
So, talking about OT, we currently don't have a central server to transfer data from 1 peer to another. We have implemented socket programming, keeping web-RTC in mind.
So if we use OT in our express(backend), do you think it will increase latency, and socket communication speed will decrease eventually?
Also here is my discord username - kothariji#7469, we can connect there for further discussions.
Happy Contributing :raised_hands:

please assign me this


Create Post Package structure (Including Post and UniquePostList)

The design of the Post class structure.

Currently Post have 5 fields:

Title
Content
PostDate
Category
Notes

For now, all the fields are String format, for PostDate need change to DateTime format, will create a separate issue for it


Add responseType to README.md

Document the usage of the responseType option.
See also: https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest#responseType

Seems legit.
I'll make sure unusual responseTypes are handled well (I wonder how responseType=json it interacts with our own json option) and I guess we can merge it.

lgtm.

There's actually no way to make a cross-browser test for this, because setting responseType to an unsupported value throws a DOMException (in phantomjs) while in new browsers it just works. So no unit test for that, but it works as expected.


Bad description for MessageElement when reference a type

When generating the description of MessageElement, the description of each parts are not call and return a return the object not the description. This issue happens when the part references a type.
With the wsdl-to-ts project, this generates bad interface : https://github.com/TimLuq/wsdl-to-ts/issues/7

Coverage decreased (-0.3%) to 93.096% when pulling 7c128f048200b8a67be43c70f4951d7b714cd552 on lafeuil:lafeuil/master into 3167cc78432a19a9694be6646ebe683be6f6257d on vpulim:master.

please add a test


feat: LEAP-1097: Show Review buttons in Quick View

If that's the task of another person we will show Accept/Reject. Part of "Reviewer Flow" experiment, hidden behind FF.

[x] Check if user is of Manager role
[x] Check if we are in Quick View

PR fulfills these requirements

[ ] Tests for the changes have been added/updated
[ ] Docs have been added/updated
[ ] Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.)
[x] Self-reviewed and ran all changes on a local instance

Describe the reason for change
(if it's not clear from main description — otherwise remove this section)
What feature flags were used to cover this change?
fflag_feat_all_leap_1081_reviewer_flow_updates
This change affects (describe how if yes)

[ ] Performance
[ ] Security
[x] UX

Does this PR introduce a breaking change?

[x] Yes, and covered entirely by feature flag(s)
[ ] Yes, and covered partially by feature flag(s)
[ ] No
[ ] Not sure (briefly explain the situation below)

What level of testing was included in the change?

[ ] e2e (codecept)
[ ] integration (cypress)
[ ] unit (jest)

/git merge

/git merge


HHH-13094 - Add unit tests for lazy any mapping in XML

According to #2683, unit tests for lazy any mapping in XML is required.

Superseded by this PR.


Add Ignored_Nothing_Values

Pull Request Description
Add a IgnoredNothing warning for Table.Running

Important Notes
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[ ] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

Do we want to also add this to aggregate? (Perhaps at least have a ticket to track that?)
As from what I understood from the discussions, we wanted this warning on both running and aggregate.

Do we want to also add this to aggregate? (Perhaps at least have a ticket to track that?)
As from what I understood from the discussions, we wanted this warning on both running and aggregate.

Ticketed https://github.com/enso-org/enso/issues/9772


Add developer context for ENUM_VALUE deprecated directive similar to FIELD_DEFINITION

I noticed when working with the @deprecated directive that the deprecated tag and reason is only generated when the directive is used on FIELD_DEFINITION types but not ENUM_VALUE types. This was noticed when deprecating an enum value, the IDE would not show the enum value with a line through it like on a deprecated field definition. Below shows the schema and generated file when using the @deprecated directive on both types.
schema.graphql:
type ExampleField {
  id: Int!
  name: String! @deprecated(reason: "No longer used.")
  username: String!
  email: String!
}

enum ExampleEnum {
  Alpha
  Bravo
  Charlie @deprecated(reason: "No longer used.")
  Delta
}

resolver-types.ts:
export type ExampleField = {
  __typename?: 'ExampleField';
  email: Scalars['String'];
  id: Scalars['Int'];
  /** @deprecated No longer used. */
  name: Scalars['String'];
  username: Scalars['String'];
};

export enum ExampleEnum {
  Alpha = 'Alpha',
  Bravo = 'Bravo',
  Charlie = 'Charlie',
  Delta = 'Delta',
}

I have a solution working which makes use of the getFieldDefinition function in the base-types-visitor.ts file to add a similar comment to the ENUM_VALUE type when generating. Happy to put up for PR but wanted to create this issue first. Thanks!
Additional context
For context here is the IDE for both deprecated FIELD_DEFINITION types and ENUM_VALUE types:
Deprecated field definition with line through:

Deprecated enum value with no line through:

Hi @tombailey14, thank you for spotting this missing enum values support!
Of course, go forward with the pull request, I'll review it as soon as it is ready.
Let me know if you need any guidance.

Thank you for your contribution @tombailey14 ! 🤓
Your changes has been released in:

<EMAIL_ADDRESS><EMAIL_ADDRESS>and all dependent packages


Adjust Removing property section

The action to remove a property now draws a lot of attention, more than it really needs to.

Make these changes to make it avaliable, but distract from other more important areas. Prototype

Remove the heading
Change the paragraph text
Add "Request we hide this property" button which will link to the Request Removal page

closed by #580


Order Endpoint, line item issue

variant_title is a line item attribute. Some merchants ignore it and it is left as Default Title. Some may not like that, so they erase Default Title leaving an empty string.
The API provides orders to an App as JSON. JSON has no concept of a nil value, but I best an empty string is ok. I am wondering why I have an App throwing a no method X on a nil object error, when the nil object is the variant_title?
How can the variant title be nil? Should it not be just an empty string at worst?
A Pry session shows how it could be, but I am confused about how Shopify maps a variant title to nil in the first place?
x = { foo: nil }.to_json
=> "{\"foo\":null}"
y = JSON.parse(x)
=> {"foo"=>nil}
y["foo"]
=> nil       # so ya, it can happen, but only if the original object is actually nil.

Thankfully, this is no longer an issue. The "Default Title" label is no longer exposed to merchants, and API clients aren't able to do anything that would set it to a nil value. You shouldn't run into this again!


feat(context): add mask_surface method

:+1:
Just waiting for CIs and then I merge, thanks!

@Brooooooklyn Please try this change
--- a/.travis.yml
+++ b/.travis.yml
@@ -19,7 +19,7 @@ script:
   - cargo build --features purge-lgpl-docs
   - git diff -R --exit-code
   - mkdir .cargo
-  - echo 'paths = ["."]' > .cargo/config
+  - echo 'paths = [".","./cairo-sys-rs"]' > .cargo/config
   - git clone -q --depth 50 -b pending https://github.com/rust-gnome/examples _examples
   - cd _examples
   - ./build_travis.sh

@EPashkin CI looks good now, thanks

@Brooooooklyn Thanks for PR
Strange that apveyor not started, but it fails by other reason and need separate fix.


Fix MetaData channel creation

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
Fix Add MTD Channel and Add MTD Array from UI. Fix associated tests.
Why should this Pull Request be merged?
Fixes feature bug.
What testing has been done?
Manual testing on IA CD. Ran relevant automated tests.

Add New MetaData Channel.vi -> It seems like there is a glitch in Diff Bot or all the Block Diagram code was removed from this RTM Menu.

Add New MetaData Channel.vi -> It seems like there is a glitch in Diff Bot because the description below states the apparent correct changes. Can you double check that the VI is in a good running state? And maybe add a Block Diagram snip here?

Sure, here it is:


Column alias support

I have not seen anything in the docs about giving an alias to a selected field.
Example
select e.id as employee_id, c.id as customer_id from employee e, customer c;
My current workaround has been using the functions.cast(e.id, 'string').as_('employee_id'). Is there a way to do this without casting?

Nevermind. I found the solution 10 seconds after posting.
just 'e.id'.as_('employee_id')  did the trick.


Add a test for a macro introducing members to an enum

There was a short time where this was broken. Add a test to make sure we don't regress it later. rdar://105228228

@swift-ci please smoke test