[stable/prometheus-operator] Grafana pod cannot start for SSL certificate verification

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

Version of Helm and Kubernetes:
Helm v2.11.0
Kubernetes v1.11.2
Which chart:
stable/prometheus-operator
stable/grafana
What happened:
I tried to install prometheus-operator by helm for monitoring k8s cluster. I used default dashboard for grafana, and enable sidecar for dashboards and datasources. But the grafana pod status is always CrashLoopBackOff. Then I get the error log below, how to resolve this certification issue? Thanks.
kubectl logs -n monitor prometheus-operator-grafana-648d54556-5lghm grafana-sc-dashboard

Starting config map collector
Config for cluster api loaded...
2018-11-08 15:54:03,929 WARNING Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:833)'),)': /api/v1/configmaps?watch=True
2018-11-08 15:54:03,935 WARNING Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:833)'),)': /api/v1/configmaps?watch=True
2018-11-08 15:54:03,940 WARNING Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:833)'),)': /api/v1/configmaps?watch=True
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/urllib3/connectionpool.py", line 601, in urlopen
chunked=chunked)
File "/usr/local/lib/python3.6/site-packages/urllib3/connectionpool.py", line 346, in _make_request
self._validate_conn(conn)
File "/usr/local/lib/python3.6/site-packages/urllib3/connectionpool.py", line 850, in validate_conn
conn.connect()
File "/usr/local/lib/python3.6/site-packages/urllib3/connection.py", line 326, in connect
ssl_context=context)
File "/usr/local/lib/python3.6/site-packages/urllib3/util/ssl.py", line 329, in ssl_wrap_socket
return context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/local/lib/python3.6/ssl.py", line 407, in wrap_socket
_context=self, _session=session)
File "/usr/local/lib/python3.6/ssl.py", line 814, in init
self.do_handshake()
File "/usr/local/lib/python3.6/ssl.py", line 1068, in do_handshake
self._sslobj.do_handshake()
File "/usr/local/lib/python3.6/ssl.py", line 689, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:833)

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/app/sidecar.py", line 58, in
main()
File "/app/sidecar.py", line 54, in main
watchForChanges(label, targetFolder)
File "/app/sidecar.py", line 23, in watchForChanges
for event in w.stream(v1.list_config_map_for_all_namespaces):
File "/usr/local/lib/python3.6/site-packages/kubernetes/watch/watch.py", line 122, in stream
resp = func(*args, **kwargs)
File "/usr/local/lib/python3.6/site-packages/kubernetes/client/apis/core_v1_api.py", line 11024, in list_config_map_for_all_namespaces
(data) = self.list_config_map_for_all_namespaces_with_http_info(**kwargs)
File "/usr/local/lib/python3.6/site-packages/kubernetes/client/apis/core_v1_api.py", line 11121, in list_config_map_for_all_namespaces_with_http_info
collection_formats=collection_formats)
File "/usr/local/lib/python3.6/site-packages/kubernetes/client/api_client.py", line 321, in call_api
_return_http_data_only, collection_formats, _preload_content, _request_timeout)
File "/usr/local/lib/python3.6/site-packages/kubernetes/client/api_client.py", line 155, in __call_api
_request_timeout=_request_timeout)
File "/usr/local/lib/python3.6/site-packages/kubernetes/client/api_client.py", line 342, in request
headers=headers)
File "/usr/local/lib/python3.6/site-packages/kubernetes/client/rest.py", line 231, in GET
query_params=query_params)
File "/usr/local/lib/python3.6/site-packages/kubernetes/client/rest.py", line 205, in request
headers=headers)
File "/usr/local/lib/python3.6/site-packages/urllib3/request.py", line 66, in request
**urlopen_kw)
File "/usr/local/lib/python3.6/site-packages/urllib3/request.py", line 87, in request_encode_url
return self.urlopen(method, url, **extra_kw)
File "/usr/local/lib/python3.6/site-packages/urllib3/poolmanager.py", line 321, in urlopen
response = conn.urlopen(method, u.request_uri, **kw)
File "/usr/local/lib/python3.6/site-packages/urllib3/connectionpool.py", line 668, in urlopen
**response_kw)
File "/usr/local/lib/python3.6/site-packages/urllib3/connectionpool.py", line 668, in urlopen
**response_kw)
File "/usr/local/lib/python3.6/site-packages/urllib3/connectionpool.py", line 668, in urlopen
**response_kw)
File "/usr/local/lib/python3.6/site-packages/urllib3/connectionpool.py", line 639, in urlopen
_stacktrace=sys.exc_info()[2])
File "/usr/local/lib/python3.6/site-packages/urllib3/util/retry.py", line 388, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='<IP_ADDRESS>', port=443): Max retries exceeded with url: /api/v1/configmaps?watch=True (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:833)'),))

What you expected to happen:
I expected the grafana pod to start up successfully.

Could you please share your values.yaml and a command you deployed prometheus-operator with?

Could you please share your values.yaml and a command you deployed prometheus-operator with?

Could you please share your values.yaml and a command you deployed prometheus-operator with?

Hi, paskal
The common I used to deployment prometheus-operator like this:
helm package prometheus-operator
helm push -f prometheus-operator-0.1.15.tgz my-chartmuseum

helm repo update
helm install my-chartmuseum/prometheus-operator --namespace=monitor --name=prometheus-operator-v0.1.15

Here is my values.yaml, I just enable Ingress and and a k8s-pod job, then the other config is default.
# Default values for prometheus-operator.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

## Provide a name in place of prometheus-operator for `app:` labels
##
nameOverride: ""

## Provide a name to substitue for the full names of resources
##
fullnameOverride: ""

## Labels to apply to all resources
##
commonLabels: {}
# scmhash: abc123
# myLabel: aakkmd

## Create default rules for monitoring the cluster
##
defaultRules:
  create: true

##
global:
  rbac:
    create: true
    pspEnabled: true

  ## Reference to one or more secrets to be used when pulling images
  ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
  ##
  imagePullSecrets: []
  # - name: "image-pull-secret"

## Configuration for alertmanager
## ref: https://prometheus.io/docs/alerting/alertmanager/
##
alertmanager:

  ## Deploy alertmanager
  ##
  enabled: true

  ## Service account for Alertmanager to use.
  ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/
  ##
  serviceAccount:
    create: true
    name: ""

  ## Configure pod disruption budgets for Alertmanager
  ## ref: https://kubernetes.io/docs/tasks/run-application/configure-pdb/#specifying-a-poddisruptionbudget
  ## This configuration is immutable once created and will require the PDB to be deleted to be changed
  ## https://github.com/kubernetes/kubernetes/issues/45398
  ##
  podDisruptionBudget:
    enabled: false
    minAvailable: 1
    maxUnavailable: ""

  ## Alertmanager configuration directives
  ## ref: https://prometheus.io/docs/alerting/configuration/#configuration-file
  ##      https://prometheus.io/webtools/alerting/routing-tree-editor/
  ##
  config:
    global:
      resolve_timeout: 5m
    route:
      group_by: ['job']
      group_wait: 30s
      group_interval: 5m
      repeat_interval: 12h
      receiver: 'null'
      routes:
      - match:
          alertname: DeadMansSwitch
        receiver: 'null'
    receivers:
    - name: 'null'

  ## Alertmanager template files to format alerts
  ## ref: https://prometheus.io/docs/alerting/notifications/
  ##      https://prometheus.io/docs/alerting/notification_examples/
  ##
  templateFiles: {}
  #
  # An example template:
  #   template_1.tmpl: |-
  #       {{ define "cluster" }}{{ .ExternalURL | reReplaceAll ".*alertmanager\\.(.*)" "$1" }}{{ end }}
  #
  #       {{ define "slack.myorg.text" }}
  #       {{- $root := . -}}
  #       {{ range .Alerts }}
  #         *Alert:* {{ .Annotations.summary }} - `{{ .Labels.severity }}`
  #         *Cluster:*  {{ template "cluster" $root }}
  #         *Description:* {{ .Annotations.description }}
  #         *Graph:* <{{ .GeneratorURL }}|:chart_with_upwards_trend:>
  #         *Runbook:* <{{ .Annotations.runbook }}|:spiral_note_pad:>
  #         *Details:*
  #           {{ range .Labels.SortedPairs }} • *{{ .Name }}:* `{{ .Value }}`
  #           {{ end }}

  ingress:
    enabled: true

    annotations: {}

    labels: {}

    ## Hosts must be provided if Ingress is enabled.
    ##
    hosts:
      - alertmanager.test.com.cn

    ## TLS configuration for Alertmanager Ingress
    ## Secret must be manually created in the namespace
    ##
    tls: []
    # - secretName: alertmanager-general-tls
    #   hosts:
    #   - alertmanager.example.com

  ## Configuration for Alertmanager service
  ##
  service:
    ## Port to expose on each node
    ## Only used if service.type is 'NodePort'
    ##
    nodePort: 30903

    ## Service type
    ##
    type: ClusterIP

  ## If true, create a serviceMonitor for alertmanager
  ##
  serviceMonitor:
    selfMonitor: true

  ## Settings affecting alertmanagerSpec
  ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#alertmanagerspec
  ##
  alertmanagerSpec:
    ## Standard object’s metadata. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/api-conventions.md#metadata
    ## Metadata Labels and Annotations gets propagated to the Alertmanager pods.
    ##
    podMetadata: {}

    ## Image of Alertmanager
    ##
    image:
      repository: quay.io/prometheus/alertmanager
      tag: v0.15.2

    ## Secrets is a list of Secrets in the same namespace as the Alertmanager object, which shall be mounted into the
    ## Alertmanager Pods. The Secrets are mounted into /etc/alertmanager/secrets/.
    ##
    secrets: []

    ## ConfigMaps is a list of ConfigMaps in the same namespace as the Alertmanager object, which shall be mounted into the Alertmanager Pods.
    ## The ConfigMaps are mounted into /etc/alertmanager/configmaps/.
    ##
    configMaps: []

    ## Log level for Alertmanager to be configured with.
    ##
    logLevel: info

    ## Size is the expected size of the alertmanager cluster. The controller will eventually make the size of the
    ## running cluster equal to the expected size.
    replicas: 1

    ## Time duration Alertmanager shall retain data for. Default is '120h', and must match the regular expression
    ## [0-9]+(ms|s|m|h) (milliseconds seconds minutes hours).
    ##
    retention: 120h

    ## Storage is the definition of how storage will be used by the Alertmanager instances.
    ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/user-guides/storage.md
    ##
    storage: {}
    # volumeClaimTemplate:
    #   spec:
    #     storageClassName: gluster
    #     accessModes: ["ReadWriteOnce"]
    #     resources:
    #       requests:
    #         storage: 50Gi
    #   selector: {}

    ## 	The external URL the Alertmanager instances will be available under. This is necessary to generate correct URLs. This is necessary if Alertmanager is not served from root of a DNS name.	string	false
    ##
    externalUrl:

    ## 	The route prefix Alertmanager registers HTTP handlers for. This is useful, if using ExternalURL and a proxy is rewriting HTTP routes of a request, and the actual ExternalURL is still true,
    ## but the server serves requests under a different route prefix. For example for use with kubectl proxy.
    ##
    routePrefix: /

    ## If set to true all actions on the underlying managed objects are not going to be performed, except for delete actions.
    ##
    paused: false

    ## Define which Nodes the Pods are scheduled on.
    ## ref: https://kubernetes.io/docs/user-guide/node-selection/
    ##
    nodeSelector: {}

    ## Define resources requests and limits for single Pods.
    ## ref: https://kubernetes.io/docs/user-guide/compute-resources/
    ##
    resources: {}
    # requests:
    #   memory: 400Mi

    ## Pod anti-affinity can prevent the scheduler from placing Prometheus replicas on the same node.
    ## The default value "soft" means that the scheduler should *prefer* to not schedule two replica pods onto the same node but no guarantee is provided.
    ## The value "hard" means that the scheduler is *required* to not schedule two replica pods onto the same node.
    ## The value "" will disable pod anti-affinity so that no anti-affinity rules will be configured.
    ##
    podAntiAffinity: ""

    ## If specified, the pod's tolerations.
    ## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
    ##
    tolerations: []
    # - key: "key"
    #   operator: "Equal"
    #   value: "value"
    #   effect: "NoSchedule"

    ## SecurityContext holds pod-level security attributes and common container settings.
    ## This defaults to non root user with uid 1000 and gid 2000.	*v1.PodSecurityContext	false
    ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
    ##
    securityContext: {}

    ## ListenLocal makes the Alertmanager server listen on loopback, so that it does not bind against the Pod IP.
    ## Note this is only for the Alertmanager UI, not the gossip communication.
    ##
    listenLocal: false

    ## Containers allows injecting additional containers. This is meant to allow adding an authentication proxy to an Alertmanager pod.
    ##
    containers: []

    ## Priority class assigned to the Pods
    ##
    priorityClassName: ""

    ## AdditionalPeers allows injecting a set of additional Alertmanagers to peer with to form a highly available cluster.
    ##
    additionalPeers: []

## Using default values from https://github.com/helm/charts/blob/master/stable/grafana/values.yaml
##
grafana:
  enabled: true

  ## Deploy default dashboards.
  ##
  defaultDashboardsEnabled: true

  adminPassword: admin

  ingress:
    ## If true, Prometheus Ingress will be created
    ##
    enabled: true

    ## Annotations for Prometheus Ingress
    ##
    annotations: {}
      # kubernetes.io/ingress.class: nginx
      # kubernetes.io/tls-acme: "true"

    ## Labels to be added to the Ingress
    ##
    labels: {}

    ## Hostnames.
    ## Must be provided if Ingress is enable.
    ##
    # hosts:
    #   - prometheus.domain.com
    hosts:
      - grafana.test.com.cn

    ## TLS configuration for prometheus Ingress
    ## Secret must be manually created in the namespace
    ##
    tls: []
    # - secretName: prometheus-general-tls
    #   hosts:
    #   - prometheus.example.com

  sidecar:
    dashboards:
      enabled: true
      label: grafana_dashboard
    datasources:
      enabled: true
      label: grafana_datasource

## Component scraping the kube api server
##
kubeApiServer:
  enabled: true
  tlsConfig:
    serverName: kubernetes
    insecureSkipVerify: false

  serviceMonitor:
    jobLabel: component
    selector:
      matchLabels:
        component: apiserver
        provider: kubernetes

## Component scraping the kubelet and kubelet-hosted cAdvisor
##
kubelet:
  enabled: true
  namespace: kube-system

  serviceMonitor:
    ## Enable scraping the kubelet over https. For requirements to enable this see
    ## https://github.com/coreos/prometheus-operator/issues/926
    ##
    https: false

## Component scraping the kube controller manager
##
kubeControllerManager:
  enabled: true
  service:
    port: 10252
    targetPort: 10252
    selector:
      k8s-app: kube-controller-manager
## Component scraping coreDns. Use either this or kubeDns
##
coreDns:
  enabled: true
  service:
    port: 9153
    targetPort: 9153
    selector:
      k8s-app: coredns

## Component scraping kubeDns. Use either this or coreDns
##
kubeDns:
  enabled: false
  service:
    selector:
      k8s-app: kube-dns
## Component scraping etcd
##
kubeEtcd:
  enabled: true

  ## If your etcd is not deployed as a pod, specify IPs it can be found on
  ##
  endpoints: []
  # - <IP_ADDRESS>
  # - <IP_ADDRESS>
  # - <IP_ADDRESS>

  ## Etcd service. If using kubeEtcd.endpoints only the port and targetPort are used
  ##
  service:
    port: 4001
    targetPort: 4001
    selector:
      k8s-app: etcd-server

  ## Configure secure access to the etcd cluster by loading a secret into prometheus and
  ## specifying security configuration below. For example, with a secret named etcd-client-cert
  ##
  ## serviceMonitor:
  ##   scheme: https
  ##   insecureSkipVerify: false
  ##   serverName: localhost
  ##   caFile: /etc/prometheus/secrets/etcd-client-cert/etcd-ca
  ##   certFile: /etc/prometheus/secrets/etcd-client-cert/etcd-client
  ##   keyFile: /etc/prometheus/secrets/etcd-client-cert/etcd-client-key
  ##
  serviceMonitor:
    scheme: http
    insecureSkipVerify: false
    serverName: ""
    caFile: ""
    certFile: ""
    keyFile: ""

## Component scraping kube scheduler
##
kubeScheduler:
  enabled: true
  service:
    port: 10251
    targetPort: 10251
    selector:
      k8s-app: kube-scheduler

## Component scraping kube state metrics
##
kubeStateMetrics:
  enabled: true

## Configuration for kube-state-metrics subchart
##
kube-state-metrics:
  rbac:
    create: true

## Deploy node exporter as a daemonset to all nodes
##
nodeExporter:
  enabled: true

  ## Use the value configured in prometheus-node-exporter.podLabels
  ##
  jobLabel: jobLabel

## Configuration for prometheus-node-exporter subchart
##
prometheus-node-exporter:
  podLabels:
    ## Add the 'node-exporter' label to be used by serviceMonitor to match standard common usage in rules and grafana dashboards
    ##
    jobLabel: node-exporter
  extraArgs:
    - --collector.filesystem.ignored-mount-points=^/(dev|proc|sys|var/lib/docker/.+)($|/)
    - --collector.filesystem.ignored-fs-types=^(autofs|binfmt_misc|cgroup|configfs|debugfs|devpts|devtmpfs|fusectl|hugetlbfs|mqueue|overlay|proc|procfs|pstore|rpc_pipefs|securityfs|sysfs|tracefs)$

## Manages Prometheus and Alertmanager components
##
prometheusOperator:
  enabled: true

  ## Service account for Alertmanager to use.
  ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/
  ##
  serviceAccount:
    create: true
    name: ""

  ## Deploy CRDs used by Prometheus Operator.
  ##
  createCustomResource: true

  ## Attempt to clean up CRDs created by Prometheus Operator.
  ##
  cleanupCustomResource: false

  ## Labels to add to the operator pod
  ##
  podLabels: {}

  ## If true, the operator will create and maintain a service for scraping kubelets
  ## ref: https://github.com/coreos/prometheus-operator/blob/master/helm/prometheus-operator/README.md
  ##
  kubeletService:
    enabled: true
    namespace: kube-system

  ## Create a servicemonitor for the operator
  ##
  serviceMonitor:
    selfMonitor: true

  ## Resource limits & requests
  ##
  resources: {}
  # limits:
  #   cpu: 200m
  #   memory: 200Mi
  # requests:
  #   cpu: 100m
  #   memory: 100Mi

  ## Define which Nodes the Pods are scheduled on.
  ## ref: https://kubernetes.io/docs/user-guide/node-selection/
  ##
  nodeSelector: {}

  ## Tolerations for use with node taints
  ## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
  ##
  tolerations: []
  # - key: "key"
  #   operator: "Equal"
  #   value: "value"
  #   effect: "NoSchedule"

  ## Assign the prometheus operator to run on specific nodes
  ## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
  ##
  affinity: {}
  # requiredDuringSchedulingIgnoredDuringExecution:
  #   nodeSelectorTerms:
  #   - matchExpressions:
  #     - key: kubernetes.io/e2e-az-name
  #       operator: In
  #       values:
  #       - e2e-az1
  #       - e2e-az2

  ## Prometheus-operator image
  ##
  image:
    repository: quay.io/coreos/prometheus-operator
    tag: v0.25.0
    pullPolicy: IfNotPresent

  ## Configmap-reload image to use for reloading configmaps
  ##
  configmapReloadImage:
    repository: quay.io/coreos/configmap-reload
    tag: v0.0.1

  ## Prometheus-config-reloader image to use for config and rule reloading
  ##
  prometheusConfigReloaderImage:
    repository: quay.io/coreos/prometheus-config-reloader
    tag: v0.25.0

  ## Hyperkube image to use when cleaning up
  ##
  hyperkubeImage:
    repository: gcr.io/google-containers/hyperkube
    tag: v1.12.1
    pullPolicy: IfNotPresent

## Deploy a Prometheus instance
##
prometheus:

  enabled: true

  ## Service account for Prometheuses to use.
  ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/
  ##
  serviceAccount:
    create: true
    name: ""

  rbac:
    ## Create role bindings in the specified namespaces, to allow Prometheus monitoring
    ## a role binding in the release namespace will always be created.
    ##
    roleNamespaces:
      - kube-system

  ## Configure pod disruption budgets for Prometheus
  ## ref: https://kubernetes.io/docs/tasks/run-application/configure-pdb/#specifying-a-poddisruptionbudget
  ## This configuration is immutable once created and will require the PDB to be deleted to be changed
  ## https://github.com/kubernetes/kubernetes/issues/45398
  ##
  podDisruptionBudget:
    enabled: false
    minAvailable: 1
    maxUnavailable: ""

  ingress:
    enabled: true
    annotations: {}
    labels: {}

    ## Hostnames.
    ## Must be provided if Ingress is enabled.
    ##
    # hosts:
    #   - prometheus.domain.com
    hosts:
      - prometheus.test.com.cn

    ## TLS configuration for Prometheus Ingress
    ## Secret must be manually created in the namespace
    ##
    tls: []
      # - secretName: prometheus-general-tls
      #   hosts:
      #     - prometheus.example.com

  serviceMonitor:
    selfMonitor: true

  ## Settings affecting prometheusSpec
  ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#prometheusspec
  ##
  prometheusSpec:

    ## Interval between consecutive scrapes.
    ##
    scrapeInterval: ""

    ## Interval between consecutive evaluations.
    ##
    evaluationInterval: ""

    ## ListenLocal makes the Prometheus server listen on loopback, so that it does not bind against the Pod IP.
    ##
    listenLocal: false

    ## Image of Prometheus.
    ##
    image:
      repository: quay.io/prometheus/prometheus
      tag: v2.4.3

    #  repository: quay.io/coreos/prometheus
    #  tag: v2.4.3

    ## Tolerations for use with node taints
    ## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
    ##
    tolerations: []
    #  - key: "key"
    #    operator: "Equal"
    #    value: "value"
    #    effect: "NoSchedule"

    ## Alertmanagers to which alerts will be sent
    ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#alertmanagerendpoints
    ##
    ## Default configuration will connect to the alertmanager deployed as part of this release
    ##
    alertingEndpoints: []
    # - name: ""
    #   namespace: ""
    #   port: http
    #   scheme: http

    ## External labels to add to any time series or alerts when communicating with external systems
    ##
    externalLabels: {}

    ## External URL at which Prometheus will be reachable.
    ##
    externalUrl: ""

    ## Define which Nodes the Pods are scheduled on.
    ## ref: https://kubernetes.io/docs/user-guide/node-selection/
    ##
    nodeSelector: {}

    ## Secrets is a list of Secrets in the same namespace as the Prometheus object, which shall be mounted into the Prometheus Pods.
    ## The Secrets are mounted into /etc/prometheus/secrets/. Secrets changes after initial creation of a Prometheus object are not
    ## reflected in the running Pods. To change the secrets mounted into the Prometheus Pods, the object must be deleted and recreated
    ## with the new list of secrets.
    ##
    secrets: []

    ## ConfigMaps is a list of ConfigMaps in the same namespace as the Prometheus object, which shall be mounted into the Prometheus Pods.
    ## The ConfigMaps are mounted into /etc/prometheus/configmaps/.
    ##
    configMaps: []

    ## Namespaces to be selected for PrometheusRules discovery.
    ## If unspecified, only the same namespace as the Prometheus object is in is used.
    ##
    ruleNamespaceSelector: {}

    ## Rules CRD selector
    ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/design.md
    ## If unspecified the release `app` and `release` will be used as the label selector
    ## to load rules
    ##
    ruleSelector: {}
    ## Example which select all prometheusrules resources
    ## with label "prometheus" with values any of "example-rules" or "example-rules-2"
    # ruleSelector:
    #   matchExpressions:
    #     - key: prometheus
    #       operator: In
    #       values:
    #         - example-rules
    #         - example-rules-2
    #
    ## Example which select all prometheusrules resources with label "role" set to "example-rules"
    # ruleSelector:
    #   matchLabels:
    #     role: example-rules

    ## serviceMonitorSelector will limit which servicemonitors are used to create scrape
    ## configs in Prometheus. By default all are loaded
    ##
    serviceMonitorSelector: {}

    # serviceMonitorSelector: {}
    #   matchLabels:
    #     prometheus: somelabel

    ## serviceMonitorNamespaceSelector will limit namespaces from which serviceMonitors are used to create scrape
    ## configs in Prometheus. By default all namespaces will be used
    ##
    serviceMonitorNamespaceSelector: {}

    ## How long to retain metrics
    ##
    retention: 10d

    ## If true, the Operator won't process any Prometheus configuration changes
    ##
    paused: false

    ## Number of Prometheus replicas desired
    ##
    replicas: 1

    ## Log level for Prometheus be configured in
    ##
    logLevel: info

    ## Prefix used to register routes, overriding externalUrl route.
    ## Useful for proxies that rewrite URLs.
    ##
    routePrefix: /

    ## Standard object’s metadata. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/api-conventions.md#metadata
    ## Metadata Labels and Annotations gets propagated to the prometheus pods.
    ##
    podMetadata: {}
    # labels:
    #   app: prometheus
    #   k8s-app: prometheus

    ## Pod anti-affinity can prevent the scheduler from placing Prometheus replicas on the same node.
    ## The default value "soft" means that the scheduler should *prefer* to not schedule two replica pods onto the same node but no guarantee is provided.
    ## The value "hard" means that the scheduler is *required* to not schedule two replica pods onto the same node.
    ## The value "" will disable pod anti-affinity so that no anti-affinity rules will be configured.
    podAntiAffinity: ""

    ## The remote_read spec configuration for Prometheus.
    ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#remotereadspec
    remoteRead: {}
    # - url: http://remote1/read

    ## The remote_write spec configuration for Prometheus.
    ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#remotewritespec
    remoteWrite: {}
      # remoteWrite:
      #   - url: http://remote1/push

    ## Resource limits & requests
    ##
    resources: {}
    # requests:
    #   memory: 400Mi

    ## Prometheus StorageSpec for persistent data
    ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/user-guides/storage.md
    ##
    storageSpec: {}
    #  volumeClaimTemplate:
    #    spec:
    #      storageClassName: gluster
    #      accessModes: ["ReadWriteOnce"]
    #      resources:
    #        requests:
    #          storage: 50Gi
    #    selector: {}

    ## AdditionalScrapeConfigs allows specifying additional Prometheus scrape configurations. Scrape configurations
    ## are appended to the configurations generated by the Prometheus Operator. Job configurations must have the form
    ## as specified in the official Prometheus documentation:
    ## https://prometheus.io/docs/prometheus/latest/configuration/configuration/#<scrape_config>. As scrape configs are
    ## appended, the user is responsible to make sure it is valid. Note that using this feature may expose the possibility
    ## to break upgrades of Prometheus. It is advised to review Prometheus release notes to ensure that no incompatible
    ## scrape configs are going to break Prometheus after the upgrade.
    ##
    ## The scrape configuraiton example below will find master nodes, provided they have the name .*mst.*, relabel the
    ## port to 2379 and allow etcd scraping provided it is running on all Kubernetes master nodes
    ##
    additionalScrapeConfigs:
    # - job_name: kube-etcd
    #   kubernetes_sd_configs:
    #     - role: node
    #   scheme: https
    #   tls_config:
    #     ca_file:   /etc/prometheus/secrets/etcd-client-cert/etcd-ca
    #     cert_file: /etc/prometheus/secrets/etcd-client-cert/etcd-client
    #     key_file:  /etc/prometheus/secrets/etcd-client-cert/etcd-client-key
    #   relabel_configs:
    #   - action: labelmap
    #     regex: __meta_kubernetes_node_label_(.+)
    #   - source_labels: [__address__]
    #     action: replace
    #     target_label: __address__
    #     regex: ([^:;]+):(\d+)
    #     replacement: ${1}:2379
    #   - source_labels: [__meta_kubernetes_node_name]
    #     action: keep
    #     regex: .*mst.*
    #   - source_labels: [__meta_kubernetes_node_name]
    #     action: replace
    #     target_label: node
    #     regex: (.*)
    #     replacement: ${1}
    #   metric_relabel_configs:
    #   - regex: (kubernetes_io_hostname|failure_domain_beta_kubernetes_io_region|beta_kubernetes_io_os|beta_kubernetes_io_arch|beta_kubernetes_io_instance_type|failure_domain_beta_kubernetes_io_zone)
    #     action: labeldrop

    # Example scrape config for pods
    #
    # The relabeling allows the actual pod scrape endpoint to be configured via the
    # following annotations:
    #
    # * `prometheus.io/scrape`: Only scrape pods that have a value of `true`
    # * `prometheus.io/path`: If the metrics path is not `/metrics` override this.
    # * `prometheus.io/port`: Scrape the pod on the indicated port instead of the default of `9102`.
      - job_name: 'kubernetes-pods'
        kubernetes_sd_configs:
          - role: pod
        relabel_configs:
          - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_scrape]
            action: keep
            regex: true
          - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_path]
            action: replace
            target_label: __metrics_path__
            regex: (.+)
          - source_labels: [__address__, __meta_kubernetes_pod_annotation_prometheus_io_port]
            action: replace
            regex: ([^:]+)(?::\d+)?;(\d+)
            replacement: $1:$2
            target_label: __address__
          - action: labelmap
            regex: __meta_kubernetes_pod_label_(.+)
          - source_labels: [__meta_kubernetes_namespace]
            action: replace
            target_label: kubernetes_namespace
          - source_labels: [__meta_kubernetes_pod_name]
            action: replace
            target_label: kubernetes_pod_name

    ## AdditionalAlertManagerConfigs allows for manual configuration of alertmanager jobs in the form as specified
    ## in the official Prometheus documentation https://prometheus.io/docs/prometheus/latest/configuration/configuration/#<alertmanager_config>.
    ## AlertManager configurations specified are appended to the configurations generated by the Prometheus Operator.
    ## As AlertManager configs are appended, the user is responsible to make sure it is valid. Note that using this
    ## feature may expose the possibility to break upgrades of Prometheus. It is advised to review Prometheus release
    ## notes to ensure that no incompatible AlertManager configs are going to break Prometheus after the upgrade.
    ##
    additionalAlertManagerConfigs: []
    # - consul_sd_configs:
    #   - server: consul.dev.test:8500
    #     scheme: http
    #     datacenter: dev
    #     tag_separator: ','
    #     services:
    #       - metrics-prometheus-alertmanager

    ## AdditionalAlertRelabelConfigs allows specifying Prometheus alert relabel configurations. Alert relabel configurations specified are appended
    ## to the configurations generated by the Prometheus Operator. Alert relabel configurations specified must have the form as specified in the
    ## official Prometheus documentation: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#alert_relabel_configs.
    ## As alert relabel configs are appended, the user is responsible to make sure it is valid. Note that using this feature may expose the
    ## possibility to break upgrades of Prometheus. It is advised to review Prometheus release notes to ensure that no incompatible alert relabel
    ## configs are going to break Prometheus after the upgrade.
    ##
    additionalAlertRelabelConfigs: []
    # - separator: ;
    #   regex: prometheus_replica
    #   replacement: $1
    #   action: labeldrop

    ## SecurityContext holds pod-level security attributes and common container settings.
    ## This defaults to non root user with uid 1000 and gid 2000.
    ## https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md
    ##
    securityContext: {}

    ## 	Priority class assigned to the Pods
    ##
    priorityClassName: ""

    ## Thanos configuration allows configuring various aspects of a Prometheus server in a Thanos environment.
    ## This section is experimental, it may change significantly without deprecation notice in any release.
    ## This is experimental and may change significantly without backward compatibility in any release.
    ## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#thanosspec
    ##
    thanos: {}

    ## Containers allows injecting additional containers. This is meant to allow adding an authentication proxy to a Prometheus pod.
    ##
    containers: []

    ## Enable additional scrape configs that are managed externally to this chart. Note that the prometheus
    ## will fail to provision if the correct secret does not exist.
    ##
    additionalScrapeConfigsExternal: false

I think it's related only with [stable/grafana] and happening due to ingress enabled with some domain. I think you can safely omit all configuration except grafana block, remove comments from it, and rename the ticket to [stable/grafana].
Sadly I am not an expert of ingress and couldn't help to reproduce and fix the issue.

I think it's related only with [stable/grafana] and happening due to ingress enabled with some domain. I think you can safely omit all configuration except grafana block, remove comments from it, and rename the ticket to [stable/grafana].
Sadly I am not an expert of ingress and couldn't help to reproduce and fix the issue.

Thank you so much. Now I also think the issue is related to grafana, I rename the ticket to [stable/grafana]. But when I disabled ingress, the grafana pod cannot start up still.
I think the reason maybe due to sidecar watched change of configmap, because the log show error happened when list configmap for all namespaces. I wander what need to be configured.
Traceback (most recent call last):
  File "/app/sidecar.py", line 58, in <module>
    main()
  File "/app/sidecar.py", line 54, in main
    watchForChanges(label, targetFolder)
  File "/app/sidecar.py", line 23, in watchForChanges
    for event in w.stream(v1.list_config_map_for_all_namespaces):
  File "/usr/local/lib/python3.6/site-packages/kubernetes/watch/watch.py", line 122, in stream
    resp = func(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/kubernetes/client/apis/core_v1_api.py", line 11024, in list_config_map_for_all_namespaces

Same error here, @shangjin92 did you find a workaround for this, please?

We were faced the same error @shangjin92 , in our case is because we generated our own certificates for kubernetes and we didn't have the complete chain of our ca certificate. I think the python request lib need to verify the complete chain of CA certificate. After we added the CA_BUNDLE in /etc/kubernetes/pki/ca.crt, the problem was solved.


Move checking Docker connectivity to ContainerManager

Description of changes:
Eliminated _check_docker_connectivity() method and introduced new property in ContainerManager is_docker_reachable. Also now ContainerManager is created on __enter__ by InvokeContext.
Updated tests and added new as required. This is the first part of porting enhancing changes from #774 .
I think we could close #774 now, right?
Checklist:

[x] Implement required changes
[x] Write unit tests
[x] make pr passes

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@jfuss more to come 😉


Pulsar manager always uses default user/password

Expected behavior
Providing non default username and password for Pulsar Admin Manager component should actually change the username and password
Actual behavior
Pulsar admin manager always uses the default username and password (not secure)
Steps to reproduce
helm upgrade --install --set pulsar_manager.admin.password=myspecialpassword --set pulsar_manager.admin.user=myspecialuser --set initialize=true --values examples/values-minikube.yaml --namespace pulsar pulsar-mini apache/pulsar
*I am aware that default chart does not restart pods if the secret changes, but lets say this is fresh install (also the case).
System configuration
Helm chart commit: c059ea25d80d6165b67ee163252a682198d8933f
Using all default values for minkube

hi @sloan-dog , this report looks a lot like #31 to me :)

Please review PR #212, it should fix this issue.

Hi @lhotari ,
As a workaround, I managed to create a simple k8s-job that performed the steps described in

https://pulsar.apache.org/docs/en/administration-pulsar-manager/#set-administrator-account-and-password

Here is the gist of it:

https://gist.github.com/mkoertgen/a3c45689e78b88f71d2c373a243c95d7

Please have a look. It should be straight-forward to add it to the helm chart as a post-install helm-hook
Note: Not sure whether the pod also needs to persist state. Might be the configuration gets lots on restarts (not sure where this is persisted).

solved by #457


Error when trying to archive using new build system in Xcode 10

For what I've found it's because both versions (10.0, 11.4) share the same build settings "Product name", what can I do about it?
(Cocoapods 1.6.0.beta 2)
Thank you!
--
Multiple commands produce '/Users/doc/Library/Developer/Xcode/DerivedData/Project-dmploethkfrsshdqgntaiiyrihlf/Build/Intermediates.noindex/ArchiveIntermediates/Project/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/UICKeyChainStore.framework':

Target 'UICKeyChainStore-iOS11.4' has create directory command with output '/Users/doc/Library/Developer/Xcode/DerivedData/Project-dmploethkfrsshdqgntaiiyrihlf/Build/Intermediates.noindex/ArchiveIntermediates/Project/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/UICKeyChainStore.framework'
Target 'UICKeyChainStore-iOS10.0' has create directory command with output '/Users/doc/Library/Developer/Xcode/DerivedData/Project-dmploethkfrsshdqgntaiiyrihlf/Build/Intermediates.noindex/ArchiveIntermediates/Project/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/UICKeyChainStore.framework'
--

@AlonZilb Thanks for reporting. I'll investigate it.


Firefox & Opera crashes

FF (or Crome) crashed when user set permissions to use microphone and select No video for video input device. In FF was detected next message:
MediaRecorder Error error { target: MediaRecorder, isTrusted: true, name: "OutOfMemoryError", currentTarget: MediaRecorder, eventPhase: 2, bubbles: false, cancelable: false, defaultPrevented: false, timeStamp:<PHONE_NUMBER>006891, originalTarget: MediaRecorder, explicitOriginalTarget: MediaRecorder }
Problem is actually in Chrome 48/49 and FF 44/45 versions on Windows 10 and Ubuntu 14.04. Is any quickfix for this problem?

What code are you using?

@thijstriemstra ,
Player configs:
var player = videojs("recorded-video", {     controls: true,     loop: false,     plugins: {         record: {             maxLength: 90,             debug: true,             image: false,             audio: true,             video: {                 width: { min: 640, ideal: 800, max: 1280 },                 height: { min: 480, ideal: 600, max: 720 }             }         }     } });
I use custom button for starting record:
$('#record-modal .start-record').click(function(){     player.recorder.getDevice();     player.recorder.start(); });
This demo crashed too https://collab-project.github.io/videojs-record/examples/audio-video.html

You shouldn't start the recorder right after you call getDevice, make sure the device is active first and call recorder.start() from the deviceReady event handler. With that being said, I'm also seeing an error in Firefox 45.0.2 on OSX 10.11.4 that I've never encountered before:
 MediaStreamError {
name: "NotFoundError",
message: "The object can not be found here.",
constraint: "",
stack: ""
}

Now that I restarted the browser I can't reproduce it though, weird.
It could be a imcompatible constraint thing as well, can you try including http://webrtc.github.io/adapter/adapter-latest.js before your scripts and see if that helps?

Ok, when I select 'No video' for that option my browser crashes as well. May I ask why you select no video when you're trying to record both audio and video? To reproduce a user error?

When I do the same in this example the browser doesn't crash.

I've tried debugging the issue and it looks like it's a recordrtc problem, specifically https://github.com/muaz-khan/RecordRTC/issues/117. When I downgrade recordrtc to 5.3.0 (bower install recordrtc#5.3.0) a stacktrace appears and an error about too much recursion:
MediaStreamRecorder/this.record/mediaRecorder.onerror()
 RecordRTC.js:1542
MediaStreamRecorder/this.pause()
 RecordRTC.js:1685
MediaStreamRecorder/this.clearRecordedData()
 RecordRTC.js:1728
startRecording()
 RecordRTC.js:51
MRecordRTC/this.startRecording/</<()
 RecordRTC.js:917
initRecorder/config.initCallback()
 RecordRTC.js:72
MediaStreamRecorder/this.record()
 RecordRTC.js:1585
MediaStreamRecorder/this.resume()
 RecordRTC.js:1702
startRecording()
 RecordRTC.js:52
MRecordRTC/this.startRecording/</<()
 RecordRTC.js:917
initRecorder/config.initCallback()
 RecordRTC.js:72
MediaStreamRecorder/this.record()
 RecordRTC.js:1585
MediaStreamRecorder/this.resume()
 RecordRTC.js:1702
startRecording()
 RecordRTC.js:52
MRecordRTC/this.startRecording/</<()
 RecordRTC.js:917
initRecorder/config.initCallback()
 RecordRTC.js:72
MediaStreamRecorder/this.record()
 RecordRTC.js:1585
MediaStreamRecorder/this.resume()
 RecordRTC.js:1702
startRecording()
 RecordRTC.js:52
MRecordRTC/this.startRecording/</<()
 RecordRTC.js:917
initRecorder/config.initCallback()
 RecordRTC.js:72
MediaStreamRecorder/this.record()
 RecordRTC.js:1585
MediaStreamRecorder/this.resume()
etc...

Also seeing the OutofMemory error after some fiddling with RecordRTC:
error { target: MediaRecorder,
isTrusted: true,
name: "OutOfMemoryError",
currentTarget: MediaRecorder,
eventPhase: 2,
bubbles: false,
cancelable: false,
defaultPrevented: false,
timeStamp:<PHONE_NUMBER>534266,
originalTarget: MediaRecorder,
explicitOriginalTarget: MediaRecorder }

@thijstriemstra First of all thank you for replies and help. You say:

May I ask why you select no video when you're trying to record both audio and video?

I'm just acted as a user. They can do it, so I have to handle this behavior.

And how are you selecting 'no' for video on Chrome. I do not have a option to set it to no in OSX, can you make a screenshot?

Sure, just go to chrome://settings/content#media-stream-mic and there we can disable camera or microphone screen.
You also can get this settings by click this link.

When I do the same in this example the browser doesn't crash. The recordrtc audio+video example also seems to work fine in Firefox.

It's strange, but first link doesn't work in my FF 44.0.2. Error:
Unable to create MediaRecorder with options Object:  TypeError: Argument 1 is not valid for any of the 2-argument overloads of MediaRecorder.
Stack trace:
startRecording@https://simpl.info/mediarecorder/js/main.js:112:21
toggleRecording@https://simpl.info/mediarecorder/js/main.js:98:5

I've opened a new recordrtc issue because I can also reproduce it without videojs-record so it's a recordrtc.js issue, see https://github.com/muaz-khan/RecordRTC/issues/118. I agree that it's a user error that should be handled. I've tried debugging the error but couldn't fix it, let's continue the conversation on the recordrtc.js ticket because there's not much I can do in this plugin I think.

@web-maker well looks like @muaz-khan pushed a fix for this issue, can you give the latest recordrtc a try?

@thijstriemstra I have already tested the latest version. Looks like it works fine - no crashes now in Chrome and FF. Many thanks to you andI  have already tested the latest version. Looks like it works fine - no crashes now in Chrome and FF. Many thanks to you and mauz-khan.

Awesome! Thanks guys.


Accept header could not be properly parsed because of a strict matching process

It is asking for accept header on all routes
local.ERROR: 400 - exception
'Symfony\Component\HttpKernel\Exception\BadRequestHttpException' with
message 'Accept header could not be properly parsed because of a strict
matching process.' in
/home2/bhuvamka/public_html/apcivilsupplies.com/protected/vendor/dingo/api/src/Http/Parser/Accept.php:66
I have enabled strict mode from env file. so now help me what can I pass in the header?

Please use the new issue format.


Python documentation

I appreciated the Quick Start guide a lot to get me using the model comfortably, but do you have a more extensive documentation for the use of Prophet in Python? For instance, I would be interested in what the syntax is for each parameter that can be specified in the prophet/fit functions.
Also, is there a way to suppress output in the model fitting?

I think you should find the docstrings for each method to be pretty complete. So for instance
help(Prophet)

It would be good to put this in the online documentation too though.
As for suppressing output, see #170 . The output is coming from the underlying C++ Stan routines and so it's proving challenging to suppress. We might end up having to wait for upstream changes from Stan but I need to look more into it.

Thanks!

@p9anand I'm not exactly sure what you mean by online training - if you mean updating the model as new data come in, then there is some discussion of that in #46. Basically you just have to re-fit the model from scratch each time.


Simulation and debugging

\ this issue should be decomposed into smaller issues \
Intro:
Currently, the user is not able to "walk" through the models. This would be a nice feature in order to allow the user to visualise the flow through the models when time is passing. This would also ease the process of debugging the system when errors occur, and the user wishes to test different ways to solve the problem.
Defintion of Done:

[ ] It is possible for the user to start the execution of the system and follow the execution/time passing via highlighting of the current state (locations and clock values).
[ ] It is possible for the user to add break points to locations and go directly to these.
[ ] It is possible for the user to increment the clocks with a user defined increment.

Skal være muligt at tage transitions, det skal ikke rigtigt været baseret på clocks (spørg mere ind til det)

Der er lavet noget i forhold til opdeling af view (snak med Niels)


Changelog.

Fixes #14.

Lgtm

Bummer that we declared 1.0.0 so early. Our 1.0.1 release breaks semantic versioning with the confirmation validator change. We should beware of this in the future.

@blimmer we can always release 2.0 and 3.0 :P

Yeah, bumping the number is not a big deal, but following semantic versioning 1.0.1 should have been 2.0.0 because of breaking api changes.

@blimmer lets consider it a "bugfix" then, and do better going forward.

:+1:


C3 alignment suggestion

from  alignment search c3 website:
A non-packed struct has the alignment of the member that has the highest alignment.
A packed struct has alignment 1.
https://c3-lang.org/references/docs/specification/#align-attribute
for details on changing the alignment.
struct Foo @align(8)
{
int a;
}
uint a = Foo.alignof; // 8
macro new_aligned($Type, ...) @nodiscard
macro new_array_aligned($Type, usz elements) @nodiscard
So if you want to use VectorN  specify an acceptible alignment for wasm?

Feels free to submit a working PR that demonstrates that in the actual code of the project.


Doesn't have release version klock:klock-android

Working with com.soywiz.korlibs.klock:klock-android. When I use debug, it works. When i tried to build internal/release version i faced with problem
`Execution failed for task ':app:checkInternalAarMetadata'.

Could not resolve all files for configuration ':app:internalRuntimeClasspath'.
Could not resolve com.soywiz.korlibs.klock:klock-android:2.0.0.
Required by:
project :app
No matching variant of com.soywiz.korlibs.klock:klock-android:2.0.0 was found. The consumer was configured to find a runtime of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'internal', attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' but:
- Variant 'debugApiElements-published' capability com.soywiz.korlibs.klock:klock-android:2.0.0 declares a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm':
- Incompatible because this component declares an API of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' and the consumer needed a runtime of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'internal'
- Variant 'debugRuntimeElements-published' capability com.soywiz.korlibs.klock:klock-android:2.0.0 declares a runtime of a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm':
- Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'internal'
- Variant 'ApiElements-published' capability com.soywiz.korlibs.klock:klock-android:2.0.0 declares a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm':
- Incompatible because this component declares an API of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value '' and the consumer needed a runtime of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'internal'
- Variant 'RuntimeElements-published' capability com.soywiz.korlibs.klock:klock-android:2.0.0 declares a runtime of a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm':
- Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value '' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'internal'`

As I see we have only debug lib version

I can add  matchingFallbacks but could you add release version?
ps. com.soywiz.korlibs.klock:klock-jvm doesn't have such problem

I'm assuming this is not an issue anymore: https://repo.maven.apache.org/maven2/com/soywiz/korlibs/klock/klock-android/2.4.7/


Sparsifying Dynamic-VHDs

Problem description
In the branch https://github.com/vorteil/vorteil/tree/aws-rework. The dynamic-vhd's that get built are broken. Potentially something to do with the RegionisHole function and File seeking.
Steps to reproduce

List of steps that must be taken to reproduce the issue.

Build a disk using dynamic-vhd format from this branch
Use the disk attached to compare the hex

vhd that works

Resolved able to run on hyper-v now


{AzureNotificationHub} fixes Azure/azure-sdk-for-net#29233

The link to https://developer.apple.com/library/ios/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Chapters/ApplePushService.html is broken.
Updated Link for Documentation on the APNS payload: https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/generating_a_remote_notification
fixes Azure/azure-sdk-for-net#29233

Things to consider before you submit the PR:

[ ] Are tests passing locally?
[ ] Are the files formatted correctly?
[ ] Did you add unit tests?
[ ] Did you test your change with either the sample apps that are included in the repository or with a blank app that uses your change?

Description
A few sentences describing the overall goals of the pull request.
Related PRs or issues
List related PRs and other issues.
Misc
Add what's missing, notes on what you tested, additional thoughts or questions.

@tjsomasundaram-zz Could you please review this PR ?


Multiprocessing added to py_mimic_fhir

Multiprocessing added to speed up py_mimic_fhir

The validation step can use as many cores as are on the computer
User specifies cores in the command line call
Speeds up validation only so much as each worker node still waits for responses from the server

Can validate with multiple cores if wanted, but will default to one core validation


Problem instalation in laravel 7

PS C:\AppServ\www\restaurantes\web> composer require tcg/voyager
Using version ^1.4 for tcg/voyager
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- tcg/voyager 1.4.x-dev requires intervention/image ^2.4 -> satisfiable by intervention/image[2.4.0, 2.4.1, 2.4.2, 2
.4.3, 2.5.0, 2.5.1, 2.4.x-dev].
- tcg/voyager 1.x-dev requires intervention/image ^2.4 -> satisfiable by intervention/image[2.4.0, 2.4.1, 2.4.2, 2.4
.3, 2.5.0, 2.5.1, 2.4.x-dev].
- tcg/voyager v1.4.0 requires intervention/image ^2.4 -> satisfiable by intervention/image[2.4.0, 2.4.1, 2.4.2, 2.4.
3, 2.5.0, 2.5.1, 2.4.x-dev].
- tcg/voyager v1.4.1 requires intervention/image ^2.4 -> satisfiable by intervention/image[2.4.0, 2.4.1, 2.4.2, 2.4.
3, 2.5.0, 2.5.1, 2.4.x-dev].
- intervention/image 2.4.x-dev requires ext-fileinfo * -> the requested PHP extension fileinfo is missing from your
system.
- intervention/image 2.5.1 requires ext-fileinfo * -> the requested PHP extension fileinfo is missing from your syst
em.
- intervention/image 2.5.0 requires ext-fileinfo * -> the requested PHP extension fileinfo is missing from your syst
em.
- intervention/image 2.4.3 requires ext-fileinfo * -> the requested PHP extension fileinfo is missing from your syst
em.
- intervention/image 2.4.2 requires ext-fileinfo * -> the requested PHP extension fileinfo is missing from your syst
em.
- intervention/image 2.4.1 requires ext-fileinfo * -> the requested PHP extension fileinfo is missing from your syst
em.
- intervention/image 2.4.0 requires ext-fileinfo * -> the requested PHP extension fileinfo is missing from your syst
em.
- Installation request for tcg/voyager ^1.4 -> satisfiable by tcg/voyager[1.4.x-dev, 1.x-dev, v1.4.0, v1.4.1].
To enable extensions, verify that they are enabled in your .ini files:
- C:\AppServ\php7\php.ini
You can also run php --ini inside terminal to see which files are used by PHP in CLI mode.
Installation failed, reverting ./composer.json to its original content.
PS C:\AppServ\www\restaurantes\web>

The issue template is not optional when opening issues.
This can be reopened when the requested information are provided.

@mikipalm Same problem for me , have you found a solution ?

https://laravel.com/docs/7.x#server-requirements

@emptynick @mikipalm I just uncommented this "extension=fileinfo" in php.ini and everything is working now :)

@mikipalm Same problem for me , have you found a solution ?

Yes I upgraded localhost server.


Ability to restrict generic to a partial of another generic

Search Terms

Suggestion
It does not seem possible to restrict a generic to be a partial of another generic
declare function foo<O, P>(obj: O, part: P & Partial<O>): P

This syntax currently does restrict P to only keys of O either
declare function foo<O, P extends Partial<O>>(obj: O, part: P): P

This should be the case
Use Cases
Many. For example, an update to state O using P where keys of P are required to in keys of O. Generic P is required as the function returns some computation resulting in P or a derivation thereof.
This current syntax does not allow for generic P, only to confine the second parameter as desired
declare function foo<O>>(obj: O, part: Partial<O>): unknown

Checklist
My suggestion meets these guidelines:

[x ] This wouldn't be a breaking change in existing TypeScript/JavaScript code

The syntax is valid today yet it does nothing.

[ x] This wouldn't change the runtime behavior of existing JavaScript code
[x ] This could be implemented without emitting different JS based on the types of the expressions
[x ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[ x] This feature would agree with the rest of TypeScript's Design Goals.

declare function foo<P, O extends P>(obj: O, part: P): P;

foo({ 1: '', 2: '', 3: '' }, { 1: '', 4: '' });
//           ~~~~~ '2' does not exist in type { 1: '', 4: '' }

seems to achieve what you are trying to do, but the error messages are on the wrong parameter now.
Afaik, extends means that O is a more specialized version of P, meaning it has to have the properties of P but it can also have some more.

What you have here is the intended behavior. If you want to log a suggestion, please provide information like what valid and invalid foo calls should be - with two floating type parameters like this and two argument positions, there are really a lot of possible interpretations and it's not at all clear what you're trying to achieve.


Delete pkgutil directories that are really files.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

Sometimes, pkgutil will return actual files (usually .nib files) as if they were part of the directory.  Microsoft Office is an example of this: in a recent update the file /Library/Application Support/Microsoft/MAU2.0/Microsoft AutoUpdate.app/Contents/SharedSupport/Microsoft Error Reporting.app/Contents/Resources/en.lproj/MainWindowAlt.nib was returning from /usr/sbin/pkgutil --only-dirs --files com.microsoft.package.component even though it should have been a file instead of a directory.  This caused the rmdir command to fail.
This patch will check if we are trying to delete a “directory” that is really a “file” - and if we are, we just delete the file instead.  This will allow packages that get in this state to be uninstalled cleanly.
--
Fixes https://github.com/caskroom/homebrew-cask/issues/29804.

Oops - forgot to run brew style on my file... 😁

@toonetown, thanks!


The newest vscode update broke debugging in older AL extensions

Version: 1.52.0 (user setup)
Commit: 940b5f4bb5fa47866a54529ed759d95d09ee80be
Date: 2020-12-10T22:45:11.850Z
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042
The newest vscode update just broke old vscode AL extensions (see https://github.com/microsoft/al) which are required for older versions of business central / dynamics NAV.
Steps to Reproduce:

Open AL project with vscode
Install old AL extension (e.g. v3.0.168874) direct link on marketplace
Try to publish your AL project with F5
Get the following error:
Couldn't find a debug adapter descriptor for debug type 'al' (extension might have failed to activate)

Does this issue occur when all extensions are disabled?: Yes/No
AL extension is required for debugging.
I posted this to both repos (see https://github.com/microsoft/AL/issues/6368) because I don't know which Team is responsible for fixing this.

Thanks for filing this against the AL extension, let's close this until their team investigates initialy.
If they discover the issue is on the VS Code side we can reopen this one.
Thanks!


add option "RANDOMIZE_DOWNLOAD_DELAY" true/false in the "advanced settings"

check also ref : https://github.com/entrepreneur-interet-general/OpenScraper/issues/40

fixed with commits : https://github.com/entrepreneur-interet-general/OpenScraper/commit/92d99089b7c01b903b3a5e005447ad6bfbc7d47f , https://github.com/entrepreneur-interet-general/OpenScraper/commit/218aad63a71c8e653d5f23e598ce02654a820b4c


TcpUtils.java only uses the first found non-local host address

When playing with multiple network gateways this becomes a problem with registering incorrect IP's in zookeeper. (eg can become non-trivial when using multiple gateways with Docker). The default behavior on CentOS with eth0 and docker0 in this case to pick up the docker0 gateway, which may not be what is desired.
public class TcpUtils {

    public static InetAddress getFirstNonLocalhostInetAddress() throws SocketException {
        final List<InetAddress> addrs = getAllInetAddress();
        return addrs.stream()
                .filter(i -> !i.isLoopbackAddress() && i instanceof Inet4Address)
                .findFirst()
                .orElseThrow(() -> new DempsyException("There are no non-local network interfaces among " + addrs));
    }

    public static List<InetAddress> getAllInetAddress() throws SocketException {
        final List<InetAddress> ret = new ArrayList<>();
        final Enumeration<NetworkInterface> netInterfaces = NetworkInterface.getNetworkInterfaces();
        while (netInterfaces.hasMoreElements()) {
            final NetworkInterface networkInterface = netInterfaces.nextElement();
            for (final Enumeration<InetAddress> loopInetAddress = networkInterface.getInetAddresses(); loopInetAddress.hasMoreElements();) {
                final InetAddress tempInetAddress = loopInetAddress.nextElement();
                ret.add(tempInetAddress);
            }
        }
        return ret;
    }

}

Yes. This is definitely a problem in Docker. I've fixed this in other systems multiple ways (e.g. a standalone REST service with a well known location that tells the process that hits it it's external IP, using DC/OS VIPs, docker-compose overlay networks). This is compounded by the problem that server ports in Dempsy are ephemeral so if you're not running with a "host" netowrk it wont have the correct port wither.
Other than making the functionality pluggable/customizable I'm not sure what to do. I'm open to suggestions. Let me know what you think.

This use case is using host mode, so we make sure that eth0 is the first network gateway listed by brute force at the OS level. Without going into an overly robust networking solution, for this use case simply passing in the network bridge name would work.

Okay. I'll make the network interface it selects configurable by name. I can have a change up probably later today. It will be on 0.9.1-SNAPSHOT.
I'll write tests for it but let me know if it works for you and I'll cut a release with the change. You'll be able to supply the setting in the Infrastructure configuration (e.g. https://github.com/Dempsy/dempsy/blob/0.9/dempsy-framework.impl/src/test/resources/td/node.xml#L20 ).
As an alternative, if you're interested, the 0.9 codebase has the ability to customize the IP address resolution with your own code. See https://github.com/Dempsy/dempsy/blob/0.9/dempsy-framework.core/src/main/java/net/dempsy/transport/tcp/AbstractTcpReceiver.java#L37 . It you're configuring programatically you can just call that on the NioReceiver, otherwise this can be set using Spring on the NioReceiver (e.g. it would be set as a property here https://github.com/Dempsy/dempsy/blob/0.9/dempsy-framework.impl/src/test/resources/td/transport-nio.xml#L10 ). This was added to support Docker.
I'm not sure if you noticed but the documentation is out of date. I've been working on updating it slowly but it's currently referencing 0.8.x and 0.9 was a significant refactor.

See #90 Let me know if that works for you


How to run more than one account?

If I have several telegram accounts, do I need to generate the api_ids and api_hashs for each account? If I should do so, how can I fill them? Because in .env i only need provide one api_id and api_hash.

If I have several telegram accounts, do I need to generate the api_ids and api_hashs for each account? If I should do so, how can I fill them? Because in .env i only need provide one api_id and api_hash.

you need to run the bot and in menu you can add as many as you like sessions

If I have several telegram accounts, do I need to generate the api_ids and api_hashs for each account? If I should do so, how can I fill them? Because in .env i only need provide one api_id and api_hash.

you need to run the bot and in menu you can add as many as you like sessions

But the api_id and api_hash is just generated by the first account. In each session, i can only choose the proxy and log in with phone, is that okay? Using just one api pairs for all of the accounts?

If I have several telegram accounts, do I need to generate the api_ids and api_hashs for each account? If I should do so, how can I fill them? Because in .env i only need provide one api_id and api_hash.

you need to run the bot and in menu you can add as many as you like sessions

But the api_id and api_hash is just generated by the first account. In each session, i can only choose the proxy and log in with phone, is that okay? Using just one api pairs for all of the accounts?

yes, you need only one api pairs and add sessions by logging into the account

If I have several telegram accounts, do I need to generate the api_ids and api_hashs for each account? If I should do so, how can I fill them? Because in .env i only need provide one api_id and api_hash.

you need to run the bot and in menu you can add as many as you like sessions

But the api_id and api_hash is just generated by the first account. In each session, i can only choose the proxy and log in with phone, is that okay? Using just one api pairs for all of the accounts?

yes, you need only one api pairs and add sessions by logging into the account

Great! Thank you so much!

If I have several telegram accounts, do I need to generate the api_ids and api_hashs for each account? If I should do so, how can I fill them? Because in .env i only need provide one api_id and api_hash.

you need to run the bot and in menu you can add as many as you like sessions

But the api_id and api_hash is just generated by the first account. In each session, i can only choose the proxy and log in with phone, is that okay? Using just one api pairs for all of the accounts?

yes you need only one api pairs and add sessions by logging into the account

No matter how many accounts i will use, just one api pairs is enough? Will my tg account be banned due to this issue or be considered as Sybil Attack by the hamster? Lets say for example 1000 accounts (though i don't have so many lol)


Support python setup.py develop.

Fixes #6.

Looks good!
If this really does fix the issue, then I am happy to merge it right away.

As I really can't see how this code would cause any problems I'll merge it right now.


Pass request args into get, put, post, etc.

It would be nice if we could pass the supported RestClient::Request args, like :timeout, into the get, post, etc. methods and have them passed along to Request.  Otherwise it seems like we have to create a custom get method that calls RestClient::Request directly if we want to adjust the settings.  Or is there some other way to do this I'm not seeing in the code?

The API design for RestClient is very bad, and there's truly no way to pass complex settings to the RestClient.get and similar helpers.
You'll have to call RestClient::Request.execute(method: :get, ...) in order to adjust the settings, or create your own get method as you describe.


Restructure policy dir, create python package openbot

It will be easier to import training files into the server after this refactor.

thanks


The bean 'com.alibaba.cloud.dubbo.metadata.repository.DubboServiceMetadataRepository' could not be injected as a 'com.alibaba.cloud.dubbo.metadata.repository.DubboServiceMetadataRepository' because it is a JDK dynamic proxy that implements:

Which Component
spring-cloud-starter-dubbo:2.2.5.RELEASE
Describe what problem you have encountered
16:44:34.623 [main] WARN  o.s.c.a.AnnotationConfigApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'targeterBeanPostProcessor' defined in class path resource [com/alibaba/cloud/dubbo/autoconfigure/DubboOpenFeignAutoConfiguration.class]: Unsatisfied dependency expressed through method 'targeterBeanPostProcessor' parameter 1; nested exception is org.springframework.beans.factory.BeanNotOfRequiredTypeException: Bean named 'com.alibaba.cloud.dubbo.metadata.repository.DubboServiceMetadataRepository' is expected to be of type 'com.alibaba.cloud.dubbo.metadata.repository.DubboServiceMetadataRepository' but was actually of type 'com.sun.proxy.$Proxy86'
16:44:34.624 [main] INFO  c.a.c.d.s.DubboGenericServiceFactory - The Dubbo GenericService ReferenceBeans are destroying...
16:44:34.631 [main] INFO  o.s.b.a.l.ConditionEvaluationReportLoggingListener -
Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
16:44:34.634 [main] ERROR o.s.b.d.LoggingFailureAnalysisReporter -

APPLICATION FAILED TO START

Description:
The bean 'com.alibaba.cloud.dubbo.metadata.repository.DubboServiceMetadataRepository' could not be injected as a 'com.alibaba.cloud.dubbo.metadata.repository.DubboServiceMetadataRepository' because it is a JDK dynamic proxy that implements:
org.springframework.beans.factory.SmartInitializingSingleton
org.springframework.context.ApplicationEventPublisherAware
Action:
Consider injecting the bean as one of its interfaces or forcing the use of CGLib-based proxies by setting proxyTargetClass=true on @EnableAsync and/or @EnableCaching.

如果希望实现 Spring Cloud 应用调用 Dubbo 服务，建议先直接通过 Spring Boot 将 Dubbo 服务暴露为 RESTful API 的方式以供对外调用。

@keylihai 能否麻烦提供一个可复现的DEMO工程呢？


bug: a difference to Java version

This implementation:
https://github.com/risingwavelabs/nexmark-rs/blob/f07f4622a464a0a7b234b62a01ff9a9306db411a/src/event.rs#L179-L193
Note the id used in Person::last_id(id, cfg) (L190) and Person::next_id(id, rng, cfg) (L192) is the one defined in L182, instead of the one passed in as an argument.
While in the Java version, it is named as event_id which is the one passed in as an argument.
https://github.com/nexmark/nexmark/blob/d0556873bb4f115dae82ab34fedc1b2cfd4ebd71/nexmark-flink/src/main/java/com/github/nexmark/flink/generator/model/AuctionGenerator.java#L44-L56
Is it a bug or intended? (If yes, I am working on a fix)

It seems like a bug introduced by https://github.com/risingwavelabs/risingwave/commit/7ed9ea2d2653b5ed939845240a09b7c4befa9da7#diff-5318bbda349f15d4ab95f0a22c3dd1e1b9b0d6c27e50118c171c2e17cdf7f2deR134. cc @KeXiangWang

Sorry🫣, should be a bug.


Linked from 'awesome' lists

Hi,
First, I'd like to congrats you, these two repositories: oas-generator and oas-tools are really amazing projects, I'm sure they will be so useful in my future projects.
In addition, I thought that could be a good idea having them in the 'awesome' lists which exist across GitHub in order to increment the visibility of them. Here I would like to give you guys these two that I've found:

https://github.com/APIs-guru/awesome-openapi3

https://github.com/marmelab/awesome-rest

Cheers.

Thanks Dani! :-)  It's a great idea! We'll sure go for it!

Thanks for your suggestion! Pull requests for both tools have been opened in those two lists, and, in fact, oas-generator can be already found in the first one!
I'm closing this issue since I don't think we need to wait until every pull request has been merged to do it.

Cool! We will wait for stars and forks! 😉


Sync mode cleanup

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[ ] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[ ] It's submitted to the dev branch.
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[ ] All tests are passing: https://github.com/vuejs/vue-test-utils/blob/dev/.github/CONTRIBUTING.md#development-setup
[ ] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

@lmiller1990 I actually forgot about this 😆 .  I will likely do another audit of this but I think these changes were the bulk of it. Is there anything in particular we should be looking at when cleaning up sync mode?

@AtofStryker no idea - I think most of the sync mode stuff is gone now, I haven't thought about it in a long time.
We could just merge this up now and then I could do a release with your new config handle feature, what do you think?

@lmiller1990 Sounds like a solid plan to me! If I find anything missed while cleaning up, opening another PR is always an option 🙂


Expose GCM as an interface for easier testing

Writing test code for packages using this lib is difficult because of the static send methods. Exposing an interface wrapping the public facing methods will help writing more testable code for users depending on this lib.
Thoughts?

That's a great suggestion, unfortunately I don't have much time to dedicate to this project right now :/


Multi parallel capability and bug fixes

Description

fixing h5py import error
Fixing the change of nc and h5 depending if one uses parallel or not. issue is related to comparison of the object versus its explicit comparision
enabling parallel as input argument parallel for both delay and download change the args parse to be a dictionary update delay to handle a dictionary

fixes #188 and #190
How Has This Been Tested?

Tested in parallel mode and without
Tested for MERRA2, GMAO, ERA5, ECMWF
Latter has an issue reported in #191
Screenshots (if appropriate):
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] I have added an explanation of what your changes do and why you'd like us to include them.
[ ] I have written new tests for your core changes, as applicable.
[x] I have successfully ran tests with your changes locally.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

thanks @bbuzz31 for testing and fixes


[FLINK-20517] Disallow operators with mixed key/non-keyed inputs with BATCH state backend

What is the purpose of the change
Using the batch state backend requires that the inputs are sorted by a key. Right now when sorting, we sort either all of the inputs or none. It is because we expect that the same key is consumed from all inputs at the same time.
We throw an exception if such a combination is used.
Verifying this change
Added tests:

org.apache.flink.streaming.api.graph.StreamGraphGeneratorBatchExecutionTest#testMixingKeyedAndNonKeyedInputInBatchMode
org.apache.flink.streaming.api.graph.StreamGraphGeneratorBatchExecutionTest#testMixingKeyedAndNonKeyedInputsInBatchMode

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented) Should we add it to the docs in the Considerations on "Writing Custom Operators"?

superseded by https://github.com/apache/flink/pull/14312

superseded by https://github.com/apache/flink/pull/14312


feat(); Perps Schema SDK; Add perps schema SDK

@harsh9200 there are a few missing fields that I am adding in rn. I will add you as a reviwer on that schema change so you are familiar. It should not be difficult to update the SDK to support it. ✅

@dmelotik Sounds Good.

https://github.com/messari/subgraphs/pull/1748

@dmelotik Just checking if other changes need to be made.

@harsh9200

There were a few more fields that we snuck in this week: https://github.com/messari/subgraphs/pull/1784
Also what is the 2.0.0 version you mention?

I updated the schema, would it be possible to add the subdivision in this pull request. If it is a lot of work we can push it to another issue. let me know what you think.
https://github.com/messari/subgraphs/pull/1825

@ishraq8 I will add the new changes in this PR only.

Hey @harsh9200 it'll be great if you could add a README indicating methods that are to be externally set / internally used

Hey @harsh9200 it'll be great if you could add a README indicating methods that are to be externally set / internally used

Here is a comprehensive example

@harsh9200 can you version the files in the SDK like something along the lines of this: https://github.com/dmelotik/subgraphs/blob/292e545821134cdf959e582746705a49bfd6f8fa/subgraphs/reference/src/sdk/protocols/lending/manager.ts#L54

Hello @dmelotik @jaimehgb, this PR is ready for review.


portico: Update Recurse Center link on /plans to point to case study.

No visual changes; manually tested the link.

Merged, thanks @alya!


No Start Menu icon in Linux Mint

Running ModernDeck in Linux Mint 20.3, Cinnamon 5.2.7, there is no start menu icon:

(Could be related to #330 and #323?)

Sorry for the delayed reply, are you using Flatpak or AppImage?

Sorry for the delayed reply, are you using Flatpak or AppImage?

I'm using the AppImage.

ModernDeck has been updated to version 10.0.0, is the issue you were facing still present in the new version?

Yes, looks like nothing has changed. No icon in the start menu. And even the custom icon I set for the panel pin has been wiped out by the update.


Implementing UI Updates

Problem
The UI is being revised based on user feedback.
Proposed Solution
Implement the updates. This ticket will also contain paper cuts resulting from the update.

Paper Cuts

All/Closest dropdown seems broken. On chrome it always jumps back to all.
The pin on the minimap makes the campaign appear further north east than it is.

The pin on the minimap makes the campaign appear further north east than it is.

Can you explain more about this?

The popup looks like a polygon.

I couldn't change the markers, this is from the provider. http://staticmap.openstreetmap.de

All of these issues are solved, closing it now.


Periodic Systems

First of all, this is a great model and I'm enjoying playing around with it.
I set up various different systems and it was able to run a geometry optimization for all of them.
Furthermore, I ran an MD simulation and e.g., in a Box of sulfuric acid and water I could see a proton transfer

I used the ASECalculator to run the MD simulations. The unwrapped simulation looks good, but when wrapping the particles back into the Box, some particles are too close together.
Here is an example for a system of water.

Is there a certain key that has to be set for periodic systems / are periodic systems possible?

Hi. At present, PBCs are not supported. The calculator just ignores PBC flag. Therefore after wrapping atoms into the cell, you see overlaps.
PBC-enabled implementation is on the way, expect an update within one or few weeks.

Are there any updates with respect to the PBC-enabled implementation? I love AIMnet2 so far, would really like to test it in MD simulations with bigger systems.


PemWriter creates an invalid PEM file when byte begin with a zero

Initially I found an intermittent issue in my integration tests with RSAParameters to PEM conversion using PemWriter and reading it back using PemReader.
Now I have narrowed it down to PemWriter and I can replicate it.
When any of the RSAParameters such as Modulus, D, P, etc start with zero as the first byte, PemWriter generates an invalid PEM file. It does not include the first zero in the PEM file.
I am looking further into this. I will post if I find anything interesting.

The initial zeros are sort of lost when we convert the byte array in RSAParameters to big integers.
        public void WritePrivateKey(RSAParameters parameters)         {             var sequence = new DerAsnSequence(new DerAsnType[]             {                 new DerAsnInteger(ToBigInteger(new byte[] { 0x00 })),   // Version                 new DerAsnInteger(ToBigInteger(parameters.Modulus)),                 new DerAsnInteger(ToBigInteger(parameters.Exponent)),                 new DerAsnInteger(ToBigInteger(parameters.D)),                 new DerAsnInteger(ToBigInteger(parameters.P)),                 new DerAsnInteger(ToBigInteger(parameters.Q)),                 new DerAsnInteger(ToBigInteger(parameters.DP)),                 new DerAsnInteger(ToBigInteger(parameters.DQ)),                 new DerAsnInteger(ToBigInteger(parameters.InverseQ))             });
Unless we know the length of the array by some means such as knowing RSA Key size, I'm not sure how DerAsn can tell the real length.

Turns out that the problem is not in the export, it's the import that doesn't work well.
I used .net core's inbuilt PKS#1 exporter and tried exporting a certificate that doesn't get exported back by PemUtils properly. The exported PEM file are exactly the same from both methods. So, it must be the import that is not taking care of the leading zero bytes.

Thanks for reaching out. Can you post the RSA parameters you're testing with? Just to make sure we'll do the same testing...

Sure. I basically ran a loop 100 times and kept generating new RSAParameters and trying to export to PEM and import back until it failed. I noticed that every time it fails, one of the RSA parts starts with zero byte. For example, D or Private Exponent is like byte[] {0, .......}
Here's a valid PEM file that works on this website: https://8gwifi.org/PemParserFunctions.jsp
-----BEGIN RSA PRIVATE KEY-----
MIIBOgIBAAJBAM/tOjXpAjH/9npX23HbImf9ve8JWR4GH7MQze+RdtYYsSY++zQa
OAOzI8qlXIwsZ37dPLHmA4DmDQ8UmEHWTMECAwEAAQJAAKNAn3O0fwTC88MbODEs
3NbJY1dK/62TIVB24To3/BYb4ZwSGSPCmiqJm+rjpQT3SBS4O+sv5xuTDHvFUyOW
5QIhAPk05e5fFsUXKvAusue/6uTsyDVt1tn+fr+hUdgXMuC3AiEA1ZhBOSQotoUw
m3emmJNwQEg1vdsVwfg+WNFVdmkn1kcCIQDCf+TNbO3KmdBrcSc09XcRgTSpbrb3
oUevrOrB6ylMdQIgeCbXuc8PX+z4dNwPyRBXOrHkGVKeoKiGWewXyS5KDI0CIEZ9
Zx+Hyty+TgFVgqXkXCEBW6wj0IlojSeesHMw1AKj
-----END RSA PRIVATE KEY-----

Here's another one where InverseQ or the coefficient starts with a zero:
-----BEGIN RSA PRIVATE KEY-----
MIIBOwIBAAJBALaKjfztjNBmquEGlPNLNG5fhoARa7D3vZ+lGHD7Yx7GdOjqPCw2
gmMg/2LrZ3mSqRVNMe8TdjOq5ymUAn7a0Y0CAwEAAQJBAK1xDORr2cYSJv7UwCZD
KLhOr390Df0CB/xuY8DGOzH7Bx6UTlb0wSIfNQT/i+zqStynBYDB9esCnXb3aRoV
xkkCIQDIq/fFd91n1HyFqLbJAXVyvR+WSV6va83hKVYElldvAwIhAOje4O4YPnaX
8tyfs+/XzclDm0adFU2SijLdAZUmidAvAiBgX0ZFDYXFQaTzw8zUx+CR1AYBdQcG
FC3xvppS5ajj5QIhALQ+Ps9LSJ22gq4tlrKf0JJll7wSPbjrIbi4w07Uo3rVAiAA
uDFv77OpPej7Jgi0xfYnJAtkrPG8PKghMe706MhUAw==
-----END RSA PRIVATE KEY-----

In short, the 0x00 is used as padding in case the second byte is > 0x80 (sign-bit) so the number isn't being treated as a negative integer. However, sometimes the 0x00 should be stripped before putting the byte array into RSAParameters and in other cases the 0x00 must be kept, and I don't see when or why.
For reference, here is the openssl code that manages the ASN INTEGER type: https://github.com/openssl/openssl/blob/e7fb44e7c3f7a37ff83a6b69ba51a738e549bf5c/crypto/asn1/a_int.c


fix: lock down max terraform version to <1.6

changes made in https://github.com/terraform-ibm-modules/terraform-ibm-hpcs/pull/97
closing this one


Update Ledger support for chains with updated runtime

Chains with updated runtime:

Polkadot:

Energy Web X
frequency
hyperbridge
invarch
polkadotPeople
acala
nodle
pendulum

Kusama:

amplitude
karura

Validation passed in case :

Check when receive token

Check when send token from normal account to ledger account

Check when send token from ledger account to normal account

Check sign transaction with polkadot js
Check when perform stake => Can't reproceduce because don't enough balance


Scored cards appearing at bottom of game page

Cards appear at the bottom only if you score them yourself and then they disappear if you refresh the page,

I think the bug is on this line:
this.createAndAddToZone(this.zone.my_score_verso, card.position_to, card.age, card.type, card.is_relic, card.id, dojo.body(), card);

Specifically the dojo.body part.

I just tested this in production and am not able to replicate it there. So this is definitely a regression.

This is still stumping me. I have no idea how this is happening. Interestingly, we haven't heard any complaints about this in alpha. But I also haven't tested it in the alpha to see if I can replicate it there.

I tried to replicate this today and was not able to anymore. Hopefully the bug is gone!

I'll remove as release-blocking but leave this open until we get confirmation from others that it's gone.

Closing this and we can re-open if we see it again!

Re-opening this because @ultimatefiend saw this happen with Canning.


convert pretrained pt to huggingface

thanks your work.
I fine-tune it at my own dataset and now I want to convert it to your huggingcace format.
can you share the script that you used to convert pretrained pt to the huggingface ?

You can use scripts/convert_glm_checkpoint_to_transformers.py to convert the checkpoint
python scripts/convert_glm_checkpoint_to_transformers.py CHECKPOINT_PATH MODEL_NAME

where CHECKPOINT_PATH is the path to the mp_rank_00_model_states.pt file and MODEL_NAME is the repo name on huggingface hub (should be in ["glm-large", "glm-roberta-large", "glm-large-chinese", "glm-515m", "glm-2b", "glm-10b", "glm-10b-chinese"])


Add something like getserversideprops in nextjs to sveltekit

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. For example: I'm always frustrated when [...]
Describe the solution you'd like
A way to sending props to a component from the backend before rendering
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
How important is this feature to you?
Note: the more honest and specific you are here the more we will take you seriously.
Very Important for API's
Additional context
Add any other context or screenshots about the feature request here.

There's a previous discussion about getServerSideProps in #758.


Change istioctl x webhook tests output statements

Per https://github.com/istio/istio/issues/18025:
remove all fmt.Printf from webhook.go. Replace with fmt.Fprintf(writer, ... like the other istioctl commands.
The goal is that doing go test in the istioctl/cmd should not produce any output from webhook.go or webhook_test.go.
Please provide a description for what this PR is for: https://github.com/istio/istio/issues/18025
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[X ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@lei-tang: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
8737261742ebb13f7fc9fe9c9f6a299c8f20a2be
link
/test integ-galley-k8s-tests_istio

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

/retest

@lei-tang: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
8737261742ebb13f7fc9fe9c9f6a299c8f20a2be
link
/test integ-galley-k8s-tests_istio

pilot-e2e-envoyv2-v1alpha3_istio
8737261742ebb13f7fc9fe9c9f6a299c8f20a2be
link
/test pilot-e2e-envoyv2-v1alpha3_istio

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

@lei-tang: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-e2e-envoyv2-v1alpha3_istio
8737261742ebb13f7fc9fe9c9f6a299c8f20a2be
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-galley-k8s-tests_istio
8737261742ebb13f7fc9fe9c9f6a299c8f20a2be
link
/test integ-galley-k8s-tests_istio

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

/retest

@lei-tang: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-e2e-envoyv2-v1alpha3_istio
8737261742ebb13f7fc9fe9c9f6a299c8f20a2be
link
/test pilot-e2e-envoyv2-v1alpha3_istio

integ-galley-k8s-tests_istio
8737261742ebb13f7fc9fe9c9f6a299c8f20a2be
link
/test integ-galley-k8s-tests_istio

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

/retest

@lei-tang: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
8737261742ebb13f7fc9fe9c9f6a299c8f20a2be
link
/test unit-tests_istio

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

/retest
opened https://github.com/istio/istio/issues/18081

/cherrypick release-1.4

@lei-tang: new pull request created: #18206

In response to this:

/cherrypick release-1.4

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


pmbootstrap: 1.43.0 -> 1.45.0

Description of changes
Updated pmbootstrap. This fixes https://gitlab.com/postmarketOS/pmbootstrap/-/issues/2137
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

LGTM


tour: [https://tour.golang.org/concurrency/9 misleading by GOMAXPROCS(1)]

This may not be a big deal, but it will bring confusion to beginners. On the web of https://tour.golang.org/concurrency/9, the code would RUN NORMALLY if c.mux.Lock() and c.mux.Unlock() are commented in func (c *SafeCounter) Inc(key string), as follows:
func (c *SafeCounter) Inc(key string) {
	// c.mux.Lock()
	// Lock so only one goroutine at a time can access the map c.v.
	c.v[key]++
	// c.mux.Unlock()
}

It seems like the official TOUR SERVER is single core limited so that the problem of concurrency will not happen.

Those lines are not commented in the original code.
My guess is that someone using the same browser on the same computer changed them to experiment with the code. The editor locally caches changes. You can click on the "reset" button on each page to restore it to the original status.
Closing here.

@ALTree Thanks for your reply. But if c.mux.Lock() and c.mux.Unlock() are commented in func (c *SafeCounter) Inc(key string), I believe that the code should report an  error instead of running normally...

Ah, I misunderstood your report. What you're saying is that you commented the mutex calls and expected the compiler and or runtime to raise an error. Sorry for the confusion.
To answer your question: this is not actually possible. The Go runtime doesn't "know" that the mutex is supposed to protect the map itself. So it's the programmer that is in charge of locking and unlocking the variables that the mutex was created to protect before and after each access.
In general, Go does not (and cannot) guarantee data-race free code at a compiler level. What Go programmers usually do is test their code with the -race flag enabled (see https://blog.golang.org/race-detector). The race detector can detect and report data races at runtime.

@ALTree Thanks your detailed explanation. After my verification, the code can report an error if GOMAXPROCS is set as 3.
func main() {
	runtime.GOMAXPROCS(3)
	// other lines
}

As an experienced Golang developer, I agree that -race is a obvious way to check the data-race. But It would be better reporting errors of concurrent map writes for beginners in https://tour.golang.org/concurrency/9.