additionalScrapConfig not working

What happened?
I added scrape config in values.yamal
additionalScrapeConfigs:
- job_name: "logstash"
static_configs:
- targets: ["logstash:9198"]
with full values.yaml here:
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 substitute 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
rules:
alertmanager: true
etcd: true
general: true
k8s: true
kubeApiserver: true
kubePrometheusNodeAlerting: true
kubePrometheusNodeRecording: true
kubeScheduler: true
kubernetesAbsent: true
kubernetesApps: true
kubernetesResources: true
kubernetesStorage: true
kubernetesSystem: true
node: true
prometheusOperator: true
prometheus: true
Labels for default rules
labels: {}
Annotations for default rules
annotations: {}
Provide custom recording or alerting rules to be deployed into the cluster.

additionalPrometheusRules: []
- name: my-rule-file
groups:
- name: my_group
rules:
- record: my_record
expr: 100 * my_record

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: Watchdog
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: false
annotations: {}

labels: {}

## Hosts must be provided if Ingress is enabled.
##
hosts: []
  # - alertmanager.domain.com

## Paths to use for ingress rules - one path should match the alertmanagerSpec.routePrefix
##
paths: []
# - /

## 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:
annotations: {}
labels: {}
clusterIP: ""
Port to expose on each node
Only used if service.type is 'NodePort'

nodePort: 30903
List of IP addresses at which the Prometheus server service is available
Ref: https://kubernetes.io/docs/user-guide/services/#external-ips

externalIPs: []
loadBalancerIP: ""
loadBalancerSourceRanges: []
## Service type
##
type: ClusterIP

If true, create a serviceMonitor for alertmanager

serviceMonitor:
## Scrape interval. If not set, the Prometheus default scrape interval is used.
##
interval: ""
selfMonitor: true
## 	metric relabel configs to apply to samples before ingestion.
##
metricRelabelings: []
# - action: keep
#   regex: 'kube_(daemonset|deployment|pod|namespace|node|statefulset).+'
#   sourceLabels: [__name__]

# 	relabel configs to apply to samples before ingestion.
##
relabelings: []
# - sourceLabels: [__meta_kubernetes_pod_node_name]
#   separator: ;
#   regex: ^(.*)$
#   target_label: nodename
#   replacement: $1
#   action: replace

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.17.0

## If true then the user will be responsible to provide a secret with alertmanager configuration
## So when true the config part will be ignored (including templateFiles) and the one in the secret will be used
##
useExistingSecret: false

## 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 anti-affinity is enabled sets the topologyKey to use for anti-affinity.
## This can be changed to, for example, failure-domain.beta.kubernetes.io/zone
##
podAntiAffinityTopologyKey: kubernetes.io/hostname

## Assign custom affinity rules to the alertmanager instance
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
##
affinity: {}
# nodeAffinity:
#   requiredDuringSchedulingIgnoredDuringExecution:
#     nodeSelectorTerms:
#     - matchExpressions:
#       - key: kubernetes.io/e2e-az-name
#         operator: In
#         values:
#         - e2e-az1
#         - e2e-az2

## 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:
  runAsNonRoot: true
  runAsUser: 1000
  fsGroup: 2000

## 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: prom-operator
ingress:
## If true, Grafana Ingress will be created
##
enabled: false
## Annotations for Grafana 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:
#   - grafana.domain.com
hosts: []

## Path for grafana ingress
path: /

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

sidecar:
dashboards:
enabled: true
label: grafana_dashboard
datasources:
enabled: true
defaultDatasourceEnabled: true
label: grafana_datasource
extraConfigmapMounts: []
- name: certs-configmap
mountPath: /etc/grafana/ssl/
configMap: certs-configmap
readOnly: true
Configure additional grafana datasources
ref: http://docs.grafana.org/administration/provisioning/#datasources
additionalDataSources: []
- name: prometheus-sample
access: proxy
basicAuth: true
basicAuthPassword: pass
basicAuthUser: daco
editable: false
jsonData:
tlsSkipVerify: true
orgId: 1
type: prometheus
url: https://prometheus.svc:9090
version: 1
If true, create a serviceMonitor for grafana

serviceMonitor:
## Scrape interval. If not set, the Prometheus default scrape interval is used.
##
interval: ""
selfMonitor: true
## 	metric relabel configs to apply to samples before ingestion.
##
metricRelabelings: []
# - action: keep
#   regex: 'kube_(daemonset|deployment|pod|namespace|node|statefulset).+'
#   sourceLabels: [__name__]

# 	relabel configs to apply to samples before ingestion.
##
relabelings: []
# - sourceLabels: [__meta_kubernetes_pod_node_name]
#   separator: ;
#   regex: ^(.*)$
#   target_label: nodename
#   replacement: $1
#   action: replace

Component scraping the kube api server

kubeApiServer:
enabled: true
tlsConfig:
serverName: kubernetes
insecureSkipVerify: false
If your API endpoint address is not reachable (as in AKS) you can replace it with the kubernetes service

relabelings: []
- sourceLabels:
- __meta_kubernetes_namespace
- __meta_kubernetes_service_name
- __meta_kubernetes_endpoint_port_name
action: keep
regex: default;kubernetes;https
- targetLabel: address
replacement: kubernetes.default.svc:443
serviceMonitor:
## Scrape interval. If not set, the Prometheus default scrape interval is used.
##
interval: ""
jobLabel: component
selector:
matchLabels:
component: apiserver
provider: kubernetes
## 	metric relabel configs to apply to samples before ingestion.
##
metricRelabelings: []
# - action: keep
#   regex: 'kube_(daemonset|deployment|pod|namespace|node|statefulset).+'
#   sourceLabels: [__name__]

Component scraping the kubelet and kubelet-hosted cAdvisor

kubelet:
enabled: true
namespace: kube-system
serviceMonitor:
## Scrape interval. If not set, the Prometheus default scrape interval is used.
##
interval: ""
## Enable scraping the kubelet over https. For requirements to enable this see
## https://github.com/coreos/prometheus-operator/issues/926
##
https: true

## Metric relabellings to apply to samples before ingestion
##
cAdvisorMetricRelabelings: []
# - sourceLabels: [__name__, image]
#   separator: ;
#   regex: container_([a-z_]+);
#   replacement: $1
#   action: drop
# - sourceLabels: [__name__]
#   separator: ;
#   regex: container_(network_tcp_usage_total|network_udp_usage_total|tasks_state|cpu_load_average_10s)
#   replacement: $1
#   action: drop

# 	relabel configs to apply to samples before ingestion.
##
cAdvisorRelabelings: []
# - sourceLabels: [__meta_kubernetes_pod_node_name]
#   separator: ;
#   regex: ^(.*)$
#   target_label: nodename
#   replacement: $1
#   action: replace

metricRelabelings: []
# - sourceLabels: [__name__, image]
#   separator: ;
#   regex: container_([a-z_]+);
#   replacement: $1
#   action: drop
# - sourceLabels: [__name__]
#   separator: ;
#   regex: container_(network_tcp_usage_total|network_udp_usage_total|tasks_state|cpu_load_average_10s)
#   replacement: $1
#   action: drop

# 	relabel configs to apply to samples before ingestion.
##
relabelings: []
# - sourceLabels: [__meta_kubernetes_pod_node_name]
#   separator: ;
#   regex: ^(.*)$
#   target_label: nodename
#   replacement: $1
#   action: replace

Component scraping the kube controller manager

kubeControllerManager:
enabled: true
If your kube controller manager is not deployed as a pod, specify IPs it can be found on

endpoints: []
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
If using kubeControllerManager.endpoints only the port and targetPort are used

service:
port: 10252
targetPort: 10252
selector:
component: kube-controller-manager
serviceMonitor:
## Scrape interval. If not set, the Prometheus default scrape interval is used.
##
interval: ""
## Enable scraping kube-controller-manager over https.
## Requires proper certs (not self-signed) and delegated authentication/authorization checks
##
https: false

## 	metric relabel configs to apply to samples before ingestion.
##
metricRelabelings: []
# - action: keep
#   regex: 'kube_(daemonset|deployment|pod|namespace|node|statefulset).+'
#   sourceLabels: [__name__]

# 	relabel configs to apply to samples before ingestion.
##
relabelings: []
# - sourceLabels: [__meta_kubernetes_pod_node_name]
#   separator: ;
#   regex: ^(.*)$
#   target_label: nodename
#   replacement: $1
#   action: replace

Component scraping coreDns. Use either this or kubeDns

coreDns:
enabled: true
service:
port: 9153
targetPort: 9153
selector:
k8s-app: kube-dns
serviceMonitor:
## Scrape interval. If not set, the Prometheus default scrape interval is used.
##
interval: ""
## 	metric relabel configs to apply to samples before ingestion.
##
metricRelabelings: []
# - action: keep
#   regex: 'kube_(daemonset|deployment|pod|namespace|node|statefulset).+'
#   sourceLabels: [__name__]

# 	relabel configs to apply to samples before ingestion.
##
relabelings: []
# - sourceLabels: [__meta_kubernetes_pod_node_name]
#   separator: ;
#   regex: ^(.*)$
#   target_label: nodename
#   replacement: $1
#   action: replace

Component scraping kubeDns. Use either this or coreDns

kubeDns:
enabled: false
service:
selector:
k8s-app: kube-dns
serviceMonitor:
## Scrape interval. If not set, the Prometheus default scrape interval is used.
##
interval: ""
## 	metric relabel configs to apply to samples before ingestion.
##
metricRelabelings: []
# - action: keep
#   regex: 'kube_(daemonset|deployment|pod|namespace|node|statefulset).+'
#   sourceLabels: [__name__]

# 	relabel configs to apply to samples before ingestion.
##
relabelings: []
# - sourceLabels: [__meta_kubernetes_pod_node_name]
#   separator: ;
#   regex: ^(.*)$
#   target_label: nodename
#   replacement: $1
#   action: replace

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: 2379
targetPort: 2379
selector:
component: etcd
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:
## Scrape interval. If not set, the Prometheus default scrape interval is used.
##
interval: ""
scheme: http
insecureSkipVerify: false
serverName: ""
caFile: ""
certFile: ""
keyFile: ""
## 	metric relabel configs to apply to samples before ingestion.
##
metricRelabelings: []
# - action: keep
#   regex: 'kube_(daemonset|deployment|pod|namespace|node|statefulset).+'
#   sourceLabels: [__name__]

# 	relabel configs to apply to samples before ingestion.
##
relabelings: []
# - sourceLabels: [__meta_kubernetes_pod_node_name]
#   separator: ;
#   regex: ^(.*)$
#   target_label: nodename
#   replacement: $1
#   action: replace

Component scraping kube scheduler

kubeScheduler:
enabled: true
If your kube scheduler is not deployed as a pod, specify IPs it can be found on

endpoints: []
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
If using kubeScheduler.endpoints only the port and targetPort are used

service:
port: 10251
targetPort: 10251
selector:
component: kube-scheduler
serviceMonitor:
## Scrape interval. If not set, the Prometheus default scrape interval is used.
##
interval: ""
## Enable scraping kube-controller-manager over https.
## Requires proper certs (not self-signed) and delegated authentication/authorization checks
##
https: false
## 	metric relabel configs to apply to samples before ingestion.
##
metricRelabelings: []
# - action: keep
#   regex: 'kube_(daemonset|deployment|pod|namespace|node|statefulset).+'
#   sourceLabels: [__name__]

# 	relabel configs to apply to samples before ingestion.
##
relabelings: []
# - sourceLabels: [__meta_kubernetes_pod_node_name]
#   separator: ;
#   regex: ^(.*)$
#   target_label: nodename
#   replacement: $1
#   action: replace

Component scraping kube state metrics

kubeStateMetrics:
enabled: true
serviceMonitor:
## Scrape interval. If not set, the Prometheus default scrape interval is used.
##
interval: ""
## 	metric relabel configs to apply to samples before ingestion.
##
metricRelabelings: []
# - action: keep
#   regex: 'kube_(daemonset|deployment|pod|namespace|node|statefulset).+'
#   sourceLabels: [__name__]

# 	relabel configs to apply to samples before ingestion.
##
relabelings: []
# - sourceLabels: [__meta_kubernetes_pod_node_name]
#   separator: ;
#   regex: ^(.*)$
#   target_label: nodename
#   replacement: $1
#   action: replace

Configuration for kube-state-metrics subchart

kube-state-metrics:
rbac:
create: true
podSecurityPolicy:
enabled: true
Deploy node exporter as a daemonset to all nodes

nodeExporter:
enabled: true
Use the value configured in prometheus-node-exporter.podLabels

jobLabel: jobLabel
serviceMonitor:
## Scrape interval. If not set, the Prometheus default scrape interval is used.
##
interval: ""
## 	metric relabel configs to apply to samples before ingestion.
##
metricRelabelings: []
# - sourceLabels: [__name__]
#   separator: ;
#   regex: ^node_mountstats_nfs_(event|operations|transport)_.+
#   replacement: $1
#   action: drop

## 	relabel configs to apply to samples before ingestion.
##
relabelings: []
# - sourceLabels: [__meta_kubernetes_pod_node_name]
#   separator: ;
#   regex: ^(.*)$
#   target_label: nodename
#   replacement: $1
#   action: replace

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: ""
Configuration for Prometheus operator service

service:
annotations: {}
labels: {}
clusterIP: ""
Port to expose on each node
Only used if service.type is 'NodePort'

nodePort: 30080
Additional ports to open for Prometheus service
ref: https://kubernetes.io/docs/concepts/services-networking/service/#multi-port-services

additionalPorts: []
#  - name: thanos-cluster
#    port: 10900
#    nodePort: 30111

Loadbalancer IP
Only use if service.type is "loadbalancer"

loadBalancerIP: ""
loadBalancerSourceRanges: []

Service type
NodepPort, ClusterIP, loadbalancer

type: ClusterIP

## List of IP addresses at which the Prometheus server service is available
## Ref: https://kubernetes.io/docs/user-guide/services/#external-ips
##
externalIPs: []

Deploy CRDs used by Prometheus Operator.

createCustomResource: true
Customize CRDs API Group
crdApiGroup: monitoring.coreos.com
Attempt to clean up CRDs created by Prometheus Operator.

cleanupCustomResource: false
Labels to add to the operator pod

podLabels: {}
Annotations to add to the operator pod

podAnnotations: {}
Assign a PriorityClassName to pods if set
priorityClassName: ""
Define Log Format
Use logfmt (default) or json-formatted logging
logFormat: logfmt
Decrease log verbosity to errors only
logLevel: error
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:
## Scrape interval. If not set, the Prometheus default scrape interval is used.
##
interval: ""
selfMonitor: true
## 	metric relabel configs to apply to samples before ingestion.
##
metricRelabelings: []
# - action: keep
#   regex: 'kube_(daemonset|deployment|pod|namespace|node|statefulset).+'
#   sourceLabels: [__name__]

# 	relabel configs to apply to samples before ingestion.
##
relabelings: []
# - sourceLabels: [__meta_kubernetes_pod_node_name]
#   separator: ;
#   regex: ^(.*)$
#   target_label: nodename
#   replacement: $1
#   action: replace

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 custom affinity rules to the prometheus operator
ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/

affinity: {}
# nodeAffinity:
#   requiredDuringSchedulingIgnoredDuringExecution:
#     nodeSelectorTerms:
#     - matchExpressions:
#       - key: kubernetes.io/e2e-az-name
#         operator: In
#         values:
#         - e2e-az1
#         - e2e-az2
securityContext:
runAsNonRoot: true
runAsUser: 65534
Prometheus-operator image

image:
repository: quay.io/coreos/prometheus-operator
tag: v0.30.1
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.30.1
Set the prometheus config reloader side-car CPU limit. If unset, uses the prometheus-operator project default

configReloaderCpu: 100m
Set the prometheus config reloader side-car memory limit. If unset, uses the prometheus-operator project default

configReloaderMemory: 25Mi
Hyperkube image to use when cleaning up

hyperkubeImage:
repository: k8s.gcr.io/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: ""
Configuration for Prometheus service

service:
annotations: {}
labels: {}
clusterIP: ""
## To be used with a proxy extraContainer port
targetPort: 9090

## List of IP addresses at which the Prometheus server service is available
## Ref: https://kubernetes.io/docs/user-guide/services/#external-ips
##
externalIPs: []

## Port to expose on each node
## Only used if service.type is 'NodePort'
##
# nodePort: 30090

## Loadbalancer IP
## Only use if service.type is "loadbalancer"
loadBalancerIP: ""
loadBalancerSourceRanges: []
## Service type
##
type: ClusterIP

sessionAffinity: ""

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: false
annotations: {}
labels: {}
## Hostnames.
## Must be provided if Ingress is enabled.
##
# hosts:
#   - prometheus.domain.com
hosts: []

## Paths to use for ingress rules - one path should match the prometheusSpec.routePrefix
##
paths: []
# - /

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

serviceMonitor:
## Scrape interval. If not set, the Prometheus default scrape interval is used.
##
interval: ""
selfMonitor: true
## 	metric relabel configs to apply to samples before ingestion.
##
metricRelabelings: []
# - action: keep
#   regex: 'kube_(daemonset|deployment|pod|namespace|node|statefulset).+'
#   sourceLabels: [__name__]

# 	relabel configs to apply to samples before ingestion.
##
relabelings: []
# - sourceLabels: [__meta_kubernetes_pod_node_name]
#   separator: ;
#   regex: ^(.*)$
#   target_label: nodename
#   replacement: $1
#   action: replace

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

## EnableAdminAPI enables Prometheus the administrative HTTP API which includes functionality such as deleting time series.
## This is disabled by default.
## ref: https://prometheus.io/docs/prometheus/latest/querying/api/#tsdb-admin-apis
##
enableAdminAPI: false

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

## 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: {}

## Name of the external label used to denote replica name
##
replicaExternalLabelName: ""

## If true, the Operator won't add the external label used to denote replica name
##
replicaExternalLabelNameClear: false

## Name of the external label used to denote Prometheus instance name
##
prometheusExternalLabelName: ""

## If true, the Operator won't add the external label used to denote Prometheus instance name
##
prometheusExternalLabelNameClear: false

## 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: []

## QuerySpec defines the query command line flags when starting Prometheus.
## ref: https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#queryspec
##
query: {}

## Namespaces to be selected for PrometheusRules discovery.
## If nil, select own namespace. Namespaces to be selected for ServiceMonitor discovery.
## See https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#namespaceselector for usage
##
ruleNamespaceSelector: {}

## If true, a nil or {} value for prometheus.prometheusSpec.ruleSelector will cause the
## prometheus resource to be created with selectors based on values in the helm deployment,
## which will also match the PrometheusRule resources created
##
ruleSelectorNilUsesHelmValues: true

## PrometheusRules to be selected for target discovery.
## If {}, select all ServiceMonitors
##
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

## If true, a nil or {} value for prometheus.prometheusSpec.serviceMonitorSelector will cause the
## prometheus resource to be created with selectors based on values in the helm deployment,
## which will also match the servicemonitors created
##
serviceMonitorSelectorNilUsesHelmValues: true

## ServiceMonitors to be selected for target discovery.
## If {}, select all ServiceMonitors
##
serviceMonitorSelector: {}
## Example which selects ServiceMonitors with label "prometheus" set to "somelabel"
# serviceMonitorSelector:
#   matchLabels:
#     prometheus: somelabel

## Namespaces to be selected for ServiceMonitor discovery.
## See https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#namespaceselector for usage
##
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

## Log format for Prometheus be configured in
##
logFormat: logfmt

## 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: ""

## If anti-affinity is enabled sets the topologyKey to use for anti-affinity.
## This can be changed to, for example, failure-domain.beta.kubernetes.io/zone
##
podAntiAffinityTopologyKey: kubernetes.io/hostname

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

## 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: []
# - 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: "logstash"
  static_configs:
  - targets: ["logstash:9198"]
# - 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

## 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:
  runAsNonRoot: true
  runAsUser: 1000
  fsGroup: 2000

## 	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.
##  if using proxy extraContainer  update targetPort with proxy container port
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

additionalServiceMonitors: []
Name of the ServiceMonitor to create

- name: ""
## Additional labels to set used for the ServiceMonitorSelector. Together with standard labels from
## the chart
##
# additionalLabels: {}

## Service label for use in assembling a job name of the form <label value>-<port>
## If no label is specified, the service name is used.
##
# jobLabel: ""

## labels to transfer from the kubernetes service to the target
##
# targetLabels: ""

## Label selector for services to which this ServiceMonitor applies
##
# selector: {}

## Namespaces from which services are selected
##
# namespaceSelector:
  ## Match any namespace
  ##
  # any: false

  ## Explicit list of namespace names to select
  ##
  # matchNames: []

## Endpoints of the selected service to be monitored
##
# endpoints: []
  ## Name of the endpoint's service port
  ## Mutually exclusive with targetPort
  # - port: ""

  ## Name or number of the endpoint's target port
  ## Mutually exclusive with port
  # - targetPort: ""

  ## File containing bearer token to be used when scraping targets
  ##
  #   bearerTokenFile: ""

  ## Interval at which metrics should be scraped
  ##
  #   interval: 30s

  ## HTTP path to scrape for metrics
  ##
  #   path: /metrics

  ## HTTP scheme to use for scraping
  ##
  #   scheme: http

  ## TLS configuration to use when scraping the endpoint
  ##
  #   tlsConfig:

      ## Path to the CA file
      ##
      # caFile: ""

      ## Path to client certificate file
      ##
      # certFile: ""

      ## Skip certificate verification
      ##
      # insecureSkipVerify: false

      ## Path to client key file
      ##
      # keyFile: ""

      ## Server name used to verify host name
      ##
      # serverName: ""

here is the config from the deployed server
global:
scrape_interval: 1m
scrape_timeout: 10s
evaluation_interval: 1m
alerting:
alertmanagers:

kubernetes_sd_configs:

role: pod
bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
tls_config:
ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
insecure_skip_verify: false
scheme: http
timeout: 10s
relabel_configs:
source_labels: [__meta_kubernetes_namespace]
separator: ;
regex: default
replacement: $1
action: keep
source_labels: [__meta_kubernetes_pod_label_app]
separator: ;
regex: prometheus
replacement: $1
action: keep
source_labels: [__meta_kubernetes_pod_label_component]
separator: ;
regex: alertmanager
replacement: $1
action: keep
source_labels: [__meta_kubernetes_pod_container_port_number]
separator: ;
regex: null
replacement: $1
action: drop
rule_files:

/etc/config/rules
/etc/config/alerts
scrape_configs:
job_name: prometheus
honor_timestamps: true
scrape_interval: 1m
scrape_timeout: 10s
metrics_path: /metrics
scheme: http
static_configs:

targets:

localhost:9090

job_name: kubernetes-apiservers
honor_timestamps: true
scrape_interval: 1m
scrape_timeout: 10s
metrics_path: /metrics
scheme: https
kubernetes_sd_configs:

role: endpoints
bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
tls_config:
ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
insecure_skip_verify: true
relabel_configs:
source_labels: [__meta_kubernetes_namespace, __meta_kubernetes_service_name, __meta_kubernetes_endpoint_port_name]
separator: ;
regex: default;kubernetes;https
replacement: $1
action: keep

job_name: kubernetes-nodes
honor_timestamps: true
scrape_interval: 1m
scrape_timeout: 10s
metrics_path: /metrics
scheme: https
kubernetes_sd_configs:

role: node
bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
tls_config:
ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
insecure_skip_verify: true
relabel_configs:
separator: ;
regex: _meta_kubernetes_node_label(.+)
replacement: $1
action: labelmap
separator: ;
regex: (.*)
target_label: address
replacement: kubernetes.default.svc:443
action: replace
source_labels: [__meta_kubernetes_node_name]
separator: ;
regex: (.+)
target_label: metrics_path
replacement: /api/v1/nodes/$1/proxy/metrics
action: replace

job_name: kubernetes-nodes-cadvisor
honor_timestamps: true
scrape_interval: 1m
scrape_timeout: 10s
metrics_path: /metrics
scheme: https
kubernetes_sd_configs:

role: node
bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
tls_config:
ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
insecure_skip_verify: true
relabel_configs:
separator: ;
regex: _meta_kubernetes_node_label(.+)
replacement: $1
action: labelmap
separator: ;
regex: (.*)
target_label: address
replacement: kubernetes.default.svc:443
action: replace
source_labels: [__meta_kubernetes_node_name]
separator: ;
regex: (.+)
target_label: metrics_path
replacement: /api/v1/nodes/$1/proxy/metrics/cadvisor
action: replace

job_name: kubernetes-service-endpoints
honor_timestamps: true
scrape_interval: 1m
scrape_timeout: 10s
metrics_path: /metrics
scheme: http
kubernetes_sd_configs:

role: endpoints
relabel_configs:
source_labels: [__meta_kubernetes_service_annotation_prometheus_io_scrape]
separator: ;
regex: "true"
replacement: $1
action: keep
source_labels: [__meta_kubernetes_service_annotation_prometheus_io_scheme]
separator: ;
regex: (https?)
target_label: scheme
replacement: $1
action: replace
source_labels: [__meta_kubernetes_service_annotation_prometheus_io_path]
separator: ;
regex: (.+)
target_label: metrics_path
replacement: $1
action: replace
source_labels: [address, __meta_kubernetes_service_annotation_prometheus_io_port]
separator: ;
regex: ([^:]+)(?::\d+)?;(\d+)
target_label: address
replacement: $1:$2
action: replace
separator: ;
regex: _meta_kubernetes_service_label(.+)
replacement: $1
action: labelmap
source_labels: [__meta_kubernetes_namespace]
separator: ;
regex: (.*)
target_label: kubernetes_namespace
replacement: $1
action: replace
source_labels: [__meta_kubernetes_service_name]
separator: ;
regex: (.*)
target_label: kubernetes_name
replacement: $1
action: replace
source_labels: [__meta_kubernetes_pod_node_name]
separator: ;
regex: (.*)
target_label: kubernetes_node
replacement: $1
action: replace

job_name: prometheus-pushgateway
honor_labels: true
honor_timestamps: true
scrape_interval: 1m
scrape_timeout: 10s
metrics_path: /metrics
scheme: http
kubernetes_sd_configs:

role: service
relabel_configs:
source_labels: [__meta_kubernetes_service_annotation_prometheus_io_probe]
separator: ;
regex: pushgateway
replacement: $1
action: keep

job_name: kubernetes-services
honor_timestamps: true
params:
module:

http_2xx
scrape_interval: 1m
scrape_timeout: 10s
metrics_path: /probe
scheme: http
kubernetes_sd_configs:
role: service
relabel_configs:
source_labels: [__meta_kubernetes_service_annotation_prometheus_io_probe]
separator: ;
regex: "true"
replacement: $1
action: keep
source_labels: [address]
separator: ;
regex: (.*)
target_label: __param_target
replacement: $1
action: replace
separator: ;
regex: (.*)
target_label: address
replacement: blackbox
action: replace
source_labels: [__param_target]
separator: ;
regex: (.*)
target_label: instance
replacement: $1
action: replace
separator: ;
regex: _meta_kubernetes_service_label(.+)
replacement: $1
action: labelmap
source_labels: [__meta_kubernetes_namespace]
separator: ;
regex: (.*)
target_label: kubernetes_namespace
replacement: $1
action: replace
source_labels: [__meta_kubernetes_service_name]
separator: ;
regex: (.*)
target_label: kubernetes_name
replacement: $1
action: replace

job_name: kubernetes-pods
honor_timestamps: true
scrape_interval: 1m
scrape_timeout: 10s
metrics_path: /metrics
scheme: http
kubernetes_sd_configs:

role: pod
relabel_configs:
source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_scrape]
separator: ;
regex: "true"
replacement: $1
action: keep
source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_path]
separator: ;
regex: (.+)
target_label: metrics_path
replacement: $1
action: replace
source_labels: [address, __meta_kubernetes_pod_annotation_prometheus_io_port]
separator: ;
regex: ([^:]+)(?::\d+)?;(\d+)
target_label: address
replacement: $1:$2
action: replace
separator: ;
regex: _meta_kubernetes_pod_label(.+)
replacement: $1
action: labelmap
source_labels: [__meta_kubernetes_namespace]
separator: ;
regex: (.*)
target_label: kubernetes_namespace
replacement: $1
action: replace
source_labels: [__meta_kubernetes_pod_name]
separator: ;
regex: (.*)
target_label: kubernetes_pod_name
replacement: $1
action: replace
Did you expect to see some different?

I would expect the new scrape configured appended.
How to reproduce it (as minimally and precisely as possible):
use the values.yaml
Environment

Prometheus Operator version:
prometheus-8.11.4  	2.9.2

Kubernetes version information:

larrysmac:src/tools/prometheus lazhu% kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:38:32Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"12+", GitVersion:"v1.12.7-3+1a4d39a9763d23", GitCommit:"1a4d39a9763d23548d16e262d6dbe0fb2198a8ce", GitTreeState:"clean", BuildDate:"2019-03-27T01:47:38Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}
larrysmac:src/tools/prometheus lazhu%

Kubernetes cluster kind:
insert how you created your cluster: kops, bootkube, tectonic-installer, etc.

Manifests:

insert manifests relevant to the issue

Prometheus Operator Logs:

insert Prometheus Operator logs relevant to the issue here

Anything else we need to know?:

We don’t use nor maintain the helm chart, please report your problem on the repo where the chart is maintained.

Hi, Does additionalScrapeConfigs support consul_sd_configs?
I am using Prometheus v2.5.0, Prometheus operator 0.18.0. I want to automatically discover and monitor SpringCloud applications through consul_sd_configs. But after I added the additionalScrapeConfigs configuration and redeployed Prometheus using kubectl apply, I did not find the added consul_sd_configs configuration in the Prometheus Web UI. Is additionalScrapeConfigs not supporting consul_sd_configs, or is my version of Prometheus operator too low?
prometheus-additional.yaml:
- job_name: 'consul-prometheus'
  scheme: http
  metrics_path: '/actuator/prometheus'
  consul_sd_configs:
    - server: 'eureka-balancer.eureka:8000'
      scheme: http
      services: []
  relabel_configs:
  - source_labels: [__meta_consul_tags]
    action: keep

prometheus-k8s.yaml:
apiVersion: monitoring.coreos.com/v1
kind: Prometheus
metadata:
  name: k8s
  labels:
    prometheus: k8s
spec:
  replicas: 2
  secrets:
  - etcd-certs
  version: v2.5.0
  serviceAccountName: prometheus-k8s
  serviceMonitorSelector: {}
  serviceMonitorNamespaceSelector: {}

  #  matchExpressions:
  #  - {key: k8s-app, operator: Exists}
  ruleSelector:
    matchLabels:
      role: alert-rules
      prometheus: k8s
  resources:
    requests:
      # 2Gi is default, but won't schedule if you don't have a node with >2Gi
      # memory. Modify based on your target and time-series count for
      # production use. This value is mainly meant for demonstration/testing
      # purposes.
      memory: 800Mi
  alerting:
    alertmanagers:
    - namespace: monitoring
      name: alertmanager-main
      port: web
  additionalScrapeConfigs:
    name: additional-configs
    key: prometheus-additional.yaml
    optional: true


create a sticky navigation bar

What is the motivation for adding/enhancing this feature?
It will be a simple responsive navigation bar that will be create by myself.
What are the acceptance criteria?
I would like to do this feature using html,css only.

[x] ...

Can you complete this feature request by yourself?

[x] YES
[ ] NO

Additional information

Hey, @Sulagna-Dutta-Roy we are not accepting components from outside the figma file. @Sulagna-Dutta-Roy


Upgrade Spring Boot to 2.2.5

Sprint Boot 2.2.5 RELEASE was released on Feb 2020. It fixed some security vulnerable issues. Current version is 2.1.3 RELEASE

Tried to upgrade to 2.2.5 but was not successful. But I was able to upgrade to 2.1.9

Done


shows no file avaliable

hi
I have put the correct product id and put ring as slow but it shows no document available. I found three links all three links show the same. please provide me a solution for the above.
Thank you [](url

)

i have also posted the screenshot here

@sriniketh-cp you need to push "Close issue" button below the writing text field

@MlgmXyysd issue resolved


Can't reproduce DDPPO trained RL policy

I tried to train a RL object navigation policy following the instructions. The only thing I changed is the camera configurations (hfov, height etc) so that it matches with the camera on our robot. Note: I didn't change the reward functions, learning rate, nn architectures etc.
I train the policy on 5 GPU (each running 18 envs).
However, the agent seems not able to learn anything: it only learns to take the STOP action in order to avoid collision penalties. Please check the attach screenshot of tensorboard for details.
I tried several times (training from scratch) but none of the trails succeeded.

I'm wondering if there's any tricks the homerobot team used to make it work?
Any help here is appreciated! @yvsriram @cpaxton

Hey, we actually add the collision penalties and segmentation noise in second stage of training. You can find the first stage configs here: https://github.com/facebookresearch/habitat-lab/commit/803774127d43ee95c7bfe5b4b2d43868e168df3e


Feature Request: Support for using heroku postgres outside of heroku

Heroku allows external access to its postgres databases, but only over SSL.  This can be useful for testing an application destined for Heroku locally.
https://devcenter.heroku.com/articles/connecting-to-relational-databases-on-heroku-with-java#connecting-to-a-database-remotely

Huh. It wouldn't have occurred to me to use a Heroku database to develop locally: I use Postgres.app to run a development database, instead, for example. I'll patch something in to make this work; do you have opinions about the user interface side of this?
I don't like Heroku's recommended approach, much: "fuck it, turn off certificate validation" is a terrible way to deal with validation issues. I do have some insight into why those validation issues exist, so I can't really fault them on that front, but I'm going to pressure Heroku to use Let's Encrypt for ephemeral services as soon as that's live and widely-respected. In the interim I don't think it's suitable to default to SSL when running on Heroku, since broken SSL is in some ways worse than no SSL.
Do you think it'd be sufficient to copy query parameters from DATABASE_URL into the generated JDBC URL? Local development would have to use
DATABASE_URL=postgres://mumble@some-random-ec2-host/my-database?ssl=true&sslfactory=org.postgresql.ssl.NonValidatingFactory

Thanks for the quick respo

Gah, phone interface. Thanks for the quick response. I think your proposal of supporting use of query parameters in the env var URL is a great way to go. It facilitates the use case cleanly without adding any surprising "magical" behaviors (such as always skipping certificate validation).

If you want to give this a try, there's a snapshot release available. Add the repo https://dl.bintray.com/login-box/snapshots/ to your repositories and set the desired version to 0.1.3-dev.1+7885623. If that solves your issue, let me know and I'll release it (probably as version 0.2.0).

@ojacobson Works great!  Thank you for being so responsive.  This project makes using dropwizard with Heroku so much easier.

Sorry it took me so long to get to the release! It's out on Bintray now, as version 0.2.0. Enjoy!


🐞 Font Family not rendered

Describe the bug 🐛
When you render the Event video with a custom font, it take noto sans and don't render with the chosen font.
Expected behavior 🦾
We want to render with the selected font
Screenshots 📸
Should render with banger font

But don't
https://github.com/lyonjs/shortvid.io/assets/72607059/d54678ef-462d-4f61-a895-3ce9ffe4416f

Hey @Boyadjie I'd like to work on the issue, can you assign it to me?

hey @Boyadjie I've been trying to fix the bug but so far I haven't made much progress.
i already checked the loadfont() method and it while it does imports the selected font before rendering of the frames starts, it switches to importing 'Noto Sans' font while rendering the frames.
I can't seem to figure out why it switches back to the default selected font.
It'll be great if you could guide me a bit on what can I do to fix the bug.

Hi @light-200! Sorry for taking so long to reply, but I think we're going to look at doing things differently for this issue, so we'll think about it. Thanks for trying to work on it! ❤


Remove extra space from powershell command to register VMHibernationPreview feature, fails with bad request

[Enter feedback here]
Remove extra space from powershell ommand to register VMHibernationPreview
Get-AzProviderFeature -FeatureName " VMHibernationPreview " -ProviderNamespace "Microsoft.Compute"

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 0fdf5aef-450d-5a31-34b4-9095ea4d9275
Version Independent ID: ed699927-72b8-8b8f-6bab-005b8db455e8
Content: Learn about hibernating your VM - Azure Virtual Machines
Content Source: articles/virtual-machines/hibernate-resume.md
Service: virtual-machines
GitHub Login: @mattmcinnes
Microsoft Alias: jainan

@SauravB-MS
Thanks for your feedback! We will investigate and update as appropriate.

@SauravB-MS
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.


Project Zomboid Template Failing to start VM

I'm trying to use the Project Zomboid Template, everything started downloading right and the verification too, when I try to start the server i get the following error and trace:
pzexe: vmArg (json) 1: -Djava.awt.headless=true
pzexe: vmArg (json) 2: -Xmx8g
pzexe: vmArg (json) 3: -Dzomboid.steam=1
pzexe: vmArg (json) 4: -Dzomboid.znetlog=1
pzexe: vmArg (json) 5: -Djava.library.path=linux64/:natives/
pzexe: vmArg (json) 6: -Djava.security.egd=file:/dev/urandom
pzexe: vmArg (json) 7: -XX:+UseZGC
pzexe: vmArg (json) 8: -XX:-OmitStackTraceInFastThrow
pzexe: vmArg (args) 9: -Dzomboid.steam=False
pzexe: vmArg (args) 10: -Duser.home=./
pzexe: vmArg (args) 11: -Xmx4096m
pzexe: vmArg (args) 12: CustomJavaArgs
pzexe: using jvm "/home/AMP/.ampdata/instances/ProjectZomboid01/project-zomboid/380870/jre64/lib/server/libjvm.so"
pzexe: looking for PZXInitThreads.so
Unrecognized option: CustomJavaArgs
XInitThreads.cpp: calling XInitThreads()
pzexe: libPZXInitThreads64.so loaded successfully.
pzexe: about to run java hack to locate libjvm.so...
pzexe: executing "java -classpath pzexe.jar -Djava.library.path=. zombie.pzexe"
pzexe.java: loading shared library "pzexe_jni64"
JVM=/home/AMP/.ampdata/instances/ProjectZomboid01/project-zomboid/380870/jre64/lib/server/libjvm.so
pxexe: /proc/self/exe=/home/AMP/.ampdata/instances/ProjectZomboid01/project-zomboid/380870/ProjectZomboid64
pzexe config file: /home/AMP/.ampdata/instances/ProjectZomboid01/project-zomboid/380870/ProjectZomboid64.json
pzexe: mainClass: zombie/network/GameServer
pzexe: classpath: -Djava.class.path=java/.:java/istack-commons-runtime.jar:java/jassimp.jar:java/javacord-2.0.17-shaded.jar:java/javax.activation-api.jar:java/jaxb-api.jar:java/jaxb-runtime.jar:java/lwjgl.jar:java/lwjgl-natives-linux.jar:java/lwjgl-glfw.jar:java/lwjgl-glfw-natives-linux.jar:java/lwjgl-jemalloc.jar:java/lwjgl-jemalloc-natives-linux.jar:java/lwjgl-opengl.jar:java/lwjgl-opengl-natives-linux.jar:java/lwjgl_util.jar:java/sqlite-jdbc-<IP_ADDRESS>.jar:java/trove-3.0.3.jar:java/uncommons-maths-1.2.3.jar
pzexe: vmArg (json) 1: -Djava.awt.headless=true
pzexe: vmArg (json) 2: -Xmx8g
pzexe: vmArg (json) 3: -Dzomboid.steam=1
pzexe: vmArg (json) 4: -Dzomboid.znetlog=1
pzexe: vmArg (json) 5: -Djava.library.path=linux64/:natives/
pzexe: vmArg (json) 6: -Djava.security.egd=file:/dev/urandom
pzexe: vmArg (json) 7: -XX:+UseZGC
pzexe: vmArg (json) 8: -XX:-OmitStackTraceInFastThrow
pzexe: vmArg (args) 9: -Dzomboid.steam=False
pzexe: vmArg (args) 10: -Duser.home=./
pzexe: vmArg (args) 11: -Xmx4096m
pzexe: vmArg (args) 12: CustomJavaArgs
pzexe: using jvm "/home/AMP/.ampdata/instances/ProjectZomboid01/project-zomboid/380870/jre64/lib/server/libjvm.so"
Failed to create Java VM

I read a couple of messages on the Steam support and followed the instruction to no succes, is there any way to fix it?

https://discord.com/channels/266012086423912458/275351759306620941/932217104692834364

Thanks, that fixed it!

for those of us without discord, could the actual information be posted?

Seeing as you asked so nicely...
There is a bug in AMP that will be fixed in the next update. The last update should have included a workaround in the PZ template but for some reason an older PZ template was included.
The workaround is as follows.
For the instance you created, go into the datastore in the file manager in ADS, open configmanifest.json.
In the two parts at the bottom for CustomJavaArgs and CustomServerArgs, change the DefaultValue from “” to “ “, ie with a space.
Restart the instance and you should be good.
If you want to fix the underlying template so that other instances of PZ are created OK, you can make the same change in the ADS datastore in Plugins/ADSModule/GenericTemplates/project-zomboidconfig.json, then restart ADS.


window_size attention pretrain

Thanks for your great job!
I want to ask how to use initial token like section 3.3 to pretrain a gpt-like model ,which use window_size attention...For example, the input length is 2048 while the window_size is 512,query and key will be shaped like (batch,len/window_size,window_size,dimension), should I append the initial token into every q,make the shape (batch,len/window_seze,window_size+1,dimension)?

GPT-like models use dense attention while pre-training. You can prepend a BOS token to each sample or forcefully set all inputs' first token to a specific BOS token.

thanks! but in the original training settings ,for example, Pythia, doesn't every pre-training sample already start with a BOS token ?

Pythia, MPT, and Falcon didn't. While Llama has a BOS, it's at paragraph level, not chunk level, which means that after text chunking, the first token of each chunk is not necessary (mostly not) the BOS token.


Aishwarya - Added words for 7 to 11

I have added 5 words to fill up brackets numbered from 7 to 11

Yeah, first the madlibs needs to be edited and from that the story will come, so 2 files in total should be present when requesting a pull.

Added values to madlibs_list file


Fix sensor list not wrapping #34, fix version lookup in console, add show_state

#34

thanks for the fix, looks great now!


[Feature Request] Add Idempotency Support

Description:
Based on a conversation between @yordis and @vroldanbet in Discord, there seems to be a need for first-class idempotency support in the WriteRelationship API.
This is crucial for achieving reliable operations, especially in scenarios involving event processing retries, and ensuring the linearization of processing.
Context:
The WriteRelationship API already supports batch writes of relationships, which allow transactional creation, touching, or deletion of relationships. However, there are challenges around ensuring idempotent writes, especially when there could be serialization conflicts if transactions overlap.
In scenarios described by Yordis Prieto:
T1: Add Relationship - takes too long.
T2: Remove Relationship - happens faster than T1.
T1: Timeout - timeouts.
T1: Retry Add Relationship - redo.
In such a case, the sequence of operations can lead to unexpected results.
Suggested Solution:
A proposed solution by @vroldanbet is to combine CREATE with an idempotency key. By doing this, if the WriteRelationships operation fails because the idempotency-key-relationship already exists, it would signify that the operation was previously carried out.
However, this solution has limitations. For instance, it returns an error result, and we don't get the zedtoken returned by the operation.
Proposal
Integrate first-class support for idempotency keys in the WriteRelationship API.
Ensure that with the idempotency key, repeated calls to WriteRelationship with the same key will result in the same effect without unintended side effects.

A proposed solution by @vroldanbet is to combine CREATE with an idempotency key. By doing this, if the WriteRelationships operation fails because the idempotency-key-relationship already exists, it would signify that the operation was previously carried out.
However, this solution has limitations. For instance, it returns an error result, and we don't get the zedtoken returned by the operation.

Have you considered a solution where repeated calls with the same key would return the same exact response as the original request? That's the most common implementation of idempotency keys, and would have the issue with zedtoken.

Have you considered a solution where repeated calls with the same key would return the same exact response as the original request? That's the most common implementation of idempotency keys, and would not have the issue with zedtoken.

This could be possible but leads to a situation where the client stores the replayed zedtoken, and ends up with an older zedtoken stored in their DB, which opens up the "new enemy problem".


Show purgebanned in the feedback message of pban

Current when a user is banned or purgebanned this feedback message will be sent:

:incoming_envelope: :ok_hand: applied ban to USER permanently.

It would be nice to have purgeban instead of ban in the message.
To achieve that, we can add a purge: True entry to the infraction dictionary in
https://github.com/python-discord/bot/blob/bafa6a9dbf61ae30ef235537408f0b073a88dd19/bot/exts/moderation/infraction/infractions.py#L327
And append purge at the beginning of infr_type if infraction.get('purge') is True
https://github.com/python-discord/bot/blob/bafa6a9dbf61ae30ef235537408f0b073a88dd19/bot/exts/moderation/infraction/_scheduler.py#L237

I'll be yoinking this one.


Regd. Fetching of Records

Hi,
Application is very nice & has great GUI (Look & Feel is good).
Created user from backend, all is working fine but when I log in as admin & check the entries created by USER not able to view the full details .
In DASHBOARD can see the record names in list but when I click the form is empty without data same for UPDATE also but can see the record details created by Admin........User not able to see is fine but can view records created by USER only......
What can be done to view all the record details when someone is logged in as ADMIN.
Appreciate the help in resolving the issue.
Thanks,
Nick

Hi Nick,
atm ppma doesn't support multiple users. Do you download the your version from this repository?
Regards, Pierre

Hi Pierre,
Thanks for the response.
Not sure from where I downloaded as I was looking for similar product like things & tried lot other products but liked this one...so not sure..
Version what I have is 0.6.0.
Is there anyway with this 0.6.0 version where we can have admin access all the records...
Thanks,
Nick

Hi Nick!
Nop, this is not possible. The encryption key is different for every user and depends on the individually user password


Port over the existing tests and set up CI

This PR moves over the existing testing infrastructure from https://github.com/CDCgov/wastewater-informed-covid-forecasting, and modifies the tests as needed to fit the new functions. It also sets up CI to run the tests every time there is a PR into main or prod. Other scope creep things it does:

adds documentation to the data using data.R
includes some but not complete set of examples for exported functions

Definitely need to figure out how to set up caching because the r-cmd-check is taking on the order of 20 min to fail :(  I think this can be a separate issue though.
Do we want to set up any other CI? For example, I know @zsusswein set up code-cov (we would not do well right now....) and also a check to make sure that the change log( NEWS.md) was updated every time a PR merges to main
Need to have main merged in once #5  is merged

Fixing up a few things but think this is almost ready @dylanhmorris however, I don't the pkgdown is working correctly. When I go to Settings >Pages it says that it was deployed 2 weeks ago, and I think it should have been deployed with the latest merge to main?

Fixing up a few things but think this is almost ready @dylanhmorris however, I don't the pkgdown is working correctly. When I go to Settings >Pages it says that it was deployed 2 weeks ago, and I think it should have been deployed with the latest merge to main?

Edit: added main to pkgdown.yaml, and presuming this should fix it. This is ready for review. Note I moved the COVID delay distributions to delay_distribs.R to keep them as internal package functions.

@dylanhmorris this is ready for re-review


Add option to let subscriptionExchange handle all operations

This adds an option to the subscriptionExchange to let it handle query and mutation operations as well.
Resolve #543

Also it would be nice if we could pass fetchOptions as well. Right now i am using it to pass an authentication header

@zenios Kind of unrelated, but I think that's already possible.
https://github.com/FormidableLabs/urql/blob/73bdd698f72a17840abcc4f38708fda23d1aaee2/packages/core/src/exchanges/subscription.ts#L46-L48
You receive the entire operation in forwardSubscription, so you can just use operation.context.fetchOptions

@zenios Kind of unrelated, but I think that's already possible.
https://github.com/FormidableLabs/urql/blob/73bdd698f72a17840abcc4f38708fda23d1aaee2/packages/core/src/exchanges/subscription.ts#L46-L48
You receive ~the entire~ the masked operation with context in forwardSubscription, so you can just use operation.context.fetchOptions

Not if fetchOptions is a function

@zenios Like in fetchExchange you can just run the function though
https://github.com/FormidableLabs/urql/blob/8877e0fbc1169405e385579934fc68e1daa49942/packages/core/src/exchanges/fetch.ts#L81-L84

@zenios Like in fetchExchange you can just run the function though
https://github.com/FormidableLabs/urql/blob/8877e0fbc1169405e385579934fc68e1daa49942/packages/core/src/exchanges/fetch.ts#L81-L84

If i use this subsciption exchange and fetchOptions is a function on my server fetchOptions will arrive as [object]

@zenios That sounds like a different problem. You just need to call the function. If you're talking about serialisation, we don't plan or account for context ever to be sent to the server, so this shouldn't happen 😅
Either way, if you need an answer to this feel free to open an issue, where we can discuss this separately. :+1:


Problems about enviroment building

Thank you for your amazing work!
When i running
conda activate p-csg
pip3 install -r requirements.txt

there are some error like
Collecting numpy==1.18.1 (from -r requirements.txt (line 22))
  Using cached https://pypi.tuna.tsinghua.edu.cn/packages/40/de/0ea5092b8bfd2e3aa6fdbb2e499a9f9adf810992884d414defc1573dca3f/numpy-1.18.1.zip (5.4 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [55 lines of output]
      Running from numpy source directory.
      <string>:461: UserWarning: Unrecognized setuptools command, proceeding with generating Cython sources and expanding templates
      /tmp/pip-install-2ovxovaw/numpy_0ce59474edf64d0d8b969896919b2750/tools/cythonize.py:75: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
        required_version = LooseVersion('0.29.14')
      /tmp/pip-install-2ovxovaw/numpy_0ce59474edf64d0d8b969896919b2750/tools/cythonize.py:77: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
        if LooseVersion(cython_version) < required_version:

      Error compiling Cython file:
      ------------------------------------------------------------
      ...
          def __init__(self, seed=None):
              BitGenerator.__init__(self, seed)
              self.rng_state.pcg_state = &self.pcg64_random_state

              self._bitgen.state = <void *>&self.rng_state
              self._bitgen.next_uint64 = &pcg64_uint64
                                         ^
      ------------------------------------------------------------

      _pcg64.pyx:113:35: Cannot assign type 'uint64_t (*)(void *) except? -1 nogil' to 'uint64_t (*)(void *) noexcept nogil'. Exception values are incompatible. Suggest adding 'noexcept' to the type of the value being assigned.
      Processing numpy/random/_bounded_integers.pxd.in
      Processing numpy/random/_bounded_integers.pyx.in
      Processing numpy/random/_pcg64.pyx
      Traceback (most recent call last):
        File "/tmp/pip-install-2ovxovaw/numpy_0ce59474edf64d0d8b969896919b2750/tools/cythonize.py", line 238, in <module>
          main()
        File "/tmp/pip-install-2ovxovaw/numpy_0ce59474edf64d0d8b969896919b2750/tools/cythonize.py", line 234, in main
          find_process_files(root_dir)
        File "/tmp/pip-install-2ovxovaw/numpy_0ce59474edf64d0d8b969896919b2750/tools/cythonize.py", line 225, in find_process_files
          process(root_dir, fromfile, tofile, function, hash_db)
        File "/tmp/pip-install-2ovxovaw/numpy_0ce59474edf64d0d8b969896919b2750/tools/cythonize.py", line 191, in process
          processor_function(fromfile, tofile)
        File "/tmp/pip-install-2ovxovaw/numpy_0ce59474edf64d0d8b969896919b2750/tools/cythonize.py", line 80, in process_pyx
          subprocess.check_call(
        File "/home/hxa/anaconda3/envs/p-csg/lib/python3.9/subprocess.py", line 373, in check_call
          raise CalledProcessError(retcode, cmd)
      subprocess.CalledProcessError: Command '['/home/hxa/anaconda3/envs/p-csg/bin/python', '-m', 'cython', '-3', '--fast-fail', '-o', '_pcg64.c', '_pcg64.pyx']' returned non-zero exit status 1.
      Cythonizing sources
      Traceback (most recent call last):
        File "/home/hxa/anaconda3/envs/p-csg/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/home/hxa/anaconda3/envs/p-csg/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/home/hxa/anaconda3/envs/p-csg/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 149, in prepare_metadata_for_build_wheel
          return hook(metadata_directory, config_settings)
        File "/tmp/pip-build-env-1p8cdnwt/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 366, in prepare_metadata_for_build_wheel
          self.run_setup()
        File "/tmp/pip-build-env-1p8cdnwt/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 487, in run_setup
          super().run_setup(setup_script=setup_script)
        File "/tmp/pip-build-env-1p8cdnwt/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 311, in run_setup
          exec(code, locals())
        File "<string>", line 488, in <module>
        File "<string>", line 469, in setup_package
        File "<string>", line 275, in generate_cython
      RuntimeError: Running cythonize failed!
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

Similar issues occurred with numpy, matplotlib, and scipy. After some research, it was found that matplotlib and scipy could be installed successfully, and the latest version of numpy can also be installed. However, specifying version 1.18.1 of numpy results in an error. Do you have any insights on this?

Or rather, what I'd like to ask is, if I install the latest version of numpy instead of the specified 1.18.1 version, will there be any issues? How can I install version 1.18.1 without encountering errors?

When i running
cd leaderboard
pip3 install -r requirements.txt

new errors occur like
Collecting nbformat==5.3.0 (from -r requirements.txt (line 33))
  Using cached https://mirrors.cloud.tencent.com/pypi/packages/16/19/ae7286d58c4aa5f95d99a3eaa19ee5f6a334254b5a78ec88006b62f81476/nbformat-5.3.0-py3-none-any.whl (73 kB)
Collecting nvidia-ml-py3==7.352 (from -r requirements.txt (line 34))
  Using cached https://mirrors.cloud.tencent.com/pypi/packages/6d/64/cce82bddb80c0b0f5c703bbdafa94bfb69a1c5ad7a79cff00b482468f0d3/nvidia-ml-py3-7.352.0.tar.gz (19 kB)
  Preparing metadata (setup.py) ... done
ERROR: Ignored the following versions that require a different python version: 8.19.0 Requires-Python >=3.10; 8.20.0 Requires-Python >=3.10; 8.21.0 Requires-Python >=3.10; 8.22.0 Requires-Python >=3.10; 8.22.1 Requires-Python >=3.10; 8.22.2 Requires-Python >=3.10; 8.23.0 Requires-Python >=3.10; 8.24.0 Requires-Python >=3.10
ERROR: Could not find a version that satisfies the requirement open3d==<IP_ADDRESS> (from versions: 0.14.1, 0.15.2, 0.16.0, 0.17.0, 0.18.0)
ERROR: No matching distribution found for open3d==<IP_ADDRESS>

I'm currently attempting to proceed with the process by removing the specific version numbers following them, but it's unclear whether this might lead to unknown issues.

Collecting nvidia-ml-py3==7.352 (from -r requirements.txt (line 34))
  Using cached https://mirrors.cloud.tencent.com/pypi/packages/6d/64/cce82bddb80c0b0f5c703bbdafa94bfb69a1c5ad7a79cff00b482468f0d3/nvidia-ml-py3-7.352.0.tar.gz (19 kB)
  Preparing metadata (setup.py) ... done
Collecting open3d (from -r requirements.txt (line 35))
  Downloading https://mirrors.cloud.tencent.com/pypi/packages/e1/36/00032c1f99f67ec9d0afdb4bcb2561f78a9f5feaafdabd1043e12a6f9b6e/open3d-0.18.0-cp39-cp39-manylinux_2_27_x86_64.whl (399.7 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 399.7/399.7 MB 1.1 MB/s eta 0:00:00
ERROR: Ignored the following yanked versions: <IP_ADDRESS>
ERROR: Ignored the following versions that require a different python version: 8.19.0 Requires-Python >=3.10; 8.20.0 Requires-Python >=3.10; 8.21.0 Requires-Python >=3.10; 8.22.0 Requires-Python >=3.10; 8.22.1 Requires-Python >=3.10; 8.22.2 Requires-Python >=3.10; 8.23.0 Requires-Python >=3.10; 8.24.0 Requires-Python >=3.10
ERROR: Could not find a version that satisfies the requirement opencv-python==<IP_ADDRESS> (from versions: <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>)
ERROR: No matching distribution found for opencv-python==<IP_ADDRESS>


Boost build script

This is a python port of the build-c++ script found here. It defines the Boost linked libraries and header-only dependencies at the top of the file, and then proceeds to:

Creates an empty build folder in the submodule's root.
Downloads and unpacks the appropriate Boost tarball based on the version.
Build the appropriate libraries.
Package the libraries into a "fat lib" at lib/libboost.a.
Use bcp to extract only the headers we need into include/boost.
Remove the build folder.

PTAL @petersibley
CC @FiftyThree/team-app

I stole a ton of python utilities from our own build script.

I'd make one change which is to manage lib/libboost.a via git lfs so "run build script" commit would require a git lfs add lib/libboost.a

LGTM to me. yeah wish we had a better way to manage our cross repo python stuff but this is already dramatically better than the shell script way of doing things. heads up @thomasmarsh @floatplane

so "run build script" commit would require a git lfs add lib/libboost.a

Can't we just setup git lfs once in the repo and have it track *.a files?

Yup works for me.


When host is in "Inactive" state, stopping/starting/deleting/restarting containers in the host results in containers being stuck in "stopping/starting" state.

Server Version - V0.20.0
Steps to reproduce the problem:
Deploy few containers on a host.
Put host in "inactive" state.
Now try to stop/start/delete/restart containers in the host .
The action never completes and the containers are stuck in "stopping/starting" state.
In such cases , should the API error out stating that we cannot perform these actions on containers that are in Inactive hosts ?

Tested with server version - V0.24.0-rc1
stop/start/delete/restart of containers on an inactive host succeeds.


wuffs_base__magic_number_guess_fourcc can't identify VP8X

        if (y == 0x56503820) {         // 'VP8 'be
          return 0x57503820;           // 'WP8 'be
        } else if (y == 0x5650384C) {  // 'VP8L'be
          return 0x5750384C;           // 'WP8L'be
        }

An "Extended file format" WEBP starts with a "VP8X" chunk, VP8/VP8L may come after that.
https://github.com/webmproject/libwebp/blob/master/doc/webp-container-spec.txt
I'm not entirely sure what the current WEBP magic detection is for--if it said just "WEBP", it would be workable.

I thought it might be nice for wuffs_base__magic_number_guess_fourcc to discriminate lossy from lossless. But you're right that that's not 100% do-able (when looking at a fixed number of opening bytes) because of VP8X and its optional but arbitrarily long ICCP chunk before we hit the image data bitstream.
If I'm reading that linked WebP spec right (pretty HTML version is at https://developers.google.com/speed/webp/docs/riff_container), an animated WebP can actually mix lossy and lossless between frames.
As you said, we should probably just group them all as "WEBP".


apply system variables for poetry path

Fixes #16606
Cc @karrtikr @karthiknadig

If we go with this solution, it also handles replacing VSCode specific variables, handling relative paths etc. Although I haven't tested this solution out yet, so please let me know if it goes well.

@karrtikr tested that change locally and it works nicely.

@karrtikr applied those changes and tested locally, worked nicely.


add io priority

issue: https://github.com/containers/youki/issues/2065
kind/featur

Codecov Report

Merging #2164 (bc91c63) into main (d7e4a04) will decrease coverage by 0.10%.
The diff coverage is 51.88%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2164      +/-   ##
==========================================
- Coverage   64.82%   64.73%   -0.10%
==========================================
  Files         129      129
  Lines       14769    14875     +106
==========================================
+ Hits         9574     9629      +55
- Misses       5195     5246      +51

@lengrongfu v0.6.2 for oci-spec-rs is pushed.

This error is very strange, do you have any ideas. @yihuaf

This error is very strange, do you have any ideas. @yihuaf

Yes, the interface was changes with an previous, so you would have to rebase. I can try to fix this tomorrow if you are not sure.


Question: How to view top 5 or 10 slow transaction in poinpoint web ui?

Hello,
I want to know, how to get the top 5 or 10 slow transaction which is slowing as count in response summary graph?

hi @subusharma2001
Pinpoint does not yet support that feature.
Unfortunately, Pinpoint has no plans for that functionality too.
I think it would be very helpful if you develop the feature and contribute it to Pinpoint.
thanks :)

Hi,
When i can expect pinpoint 1.9.0 version release?

@subusharma2001
Pinpoint goes for to release 2.0.0 this month.
But If we will find bug that is solving, then It can not be as planned.
thanks :)


334 finish camera backend

Fixes #334.

The branch was out of date, but it still builds now that it is up-to-date with develop.


Drop support for MongoDB 4.4

MongoDB 4.4 reached its EOL in February so let's make the CI lighter for upcoming version

If 4.4 gets dropped, does it make sense to have older versions mentioned in the docs? At this point multi-document transactions are a given.
https://github.com/doctrine/mongodb-odm/blob/2a9429659f6dd2dead2c0fcb2406f9d14d31d55e/docs/en/reference/transactions-and-concurrency.rst?plain=1#L18-L19

Good catch! It does not. Github did not showed me those when grepping for 4.4 with UI. Will adjust it later :)

For the record, even if the server is no longer supported in version 4.4, we continue to maintain the driver for 3 years from the server version EOL.

For the record, even if the server is no longer supported in version 4.4, we continue to maintain the driver for 3 years from the server version EOL.

Luckily enough no code paths were made, so technically 4.4 still works with ODM. We're just not testing against it which I think is fair given it has reached EOL :)
I'll be merging this PR as CI fails are not related.

Dang, I've missed some 5.0 sharded cluster fail. That's what one gets from a broken CI :( I'll be looking into it


Updated Pydantic Branch

This PR contains the new Signature type based on Pydantic.
It also contains 112 unit tests.
Finally it has the module dspy/functional which include the TypedPredictor class, that lets you generate constrained on the types in the signature.

Hey @thomasahle , thanks so much for this! Looks ready to merge for me except for the comments above. The comment about prefix is probably ~safe to ignore. The others are probably easy to address. Let me know what you think. I think we can merge right after these, assuming the notebooks don't break.


colcon-coveragepy-result package to collect coverage.py results

I wrote a colcon extension that collects coverage.py results: https://github.com/christophebedard/colcon-coveragepy-result

combines .coverage files for each package (ros.ament_cmake packages might have multiple files)
optionally prints a report for each package
combines all .coverage files into one
optionally prints a global report
generates a global HTML report

It's basically colcon-lcov-result but for Python/coverage.py.
As per the contribution recommendations, I'd like to offer to move the repo to the colcon org.
Also, feel free to take a look at the code and review/propose changes/improvements.

As per the contribution recommendations, I'd like to offer to move the repo to the colcon org.

SGTM. Please transfer the repo to my username and I will transfer it from there to the colcon org unit.

I transfered it.

Thanks, I transferred it to the final destination: https://github.com/colcon/colcon-coveragepy-result
You should still have admin access to the repository. Please update the URLs in the package metadata to reflect the new location. You can do PyPI releases on your own (as before). If you would like to create Debian packages for a tagged version please create a ticket in the colcon-coveragepy-result for it and mention me on the ticket (since it is required to have upload access to the ROS apt repo for doing so).


Landscape，The lower right corner of the project does not need to modify the time

全景页，项目右下角应不显示修改时间

resolved


fetch: add --bottle-tag flag

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

It would be useful for maintainers to be able to easily fetch bottles for different OSes.
Not sure if the implementation itself is fine but it works.

Review period will end on 2021-07-13 at 00:00:00 UTC.

Review period ended.

What do you mean by saying PATH? The famous env variable?

I think Mike means the path to the downloaded bottle, as in the Downloaded to: line here:
❯ brew fetch hello
==> Downloading https://ghcr.io/v2/homebrew/core/hello/manifests/2.10
Already downloaded: /Users/carlocab/Library/Caches/Homebrew/downloads/93309a1636f67f0f51e2604bb2ece243b5a9324eda1d49e05192ed285af508cd--hello-2.10.bottle_manifest.json
==> Downloading https://ghcr.io/v2/homebrew/core/hello/blobs/sha256:69489ae397e4645127aa7773211310f81ebb6c99e1f8e3e22c5cdb55333f540
==> Downloading from https://pkg-containers.githubusercontent.com/ghcr1/blobs/sha256:69489ae397e4645127aa7773211310f81ebb6c99e1f8e3
######################################################################## 100.0%
Downloaded to: /Users/carlocab/Library/Caches/Homebrew/downloads/e0395c201b40d07f50d44b84fccab28bb89bb292929894555688f6510f583a4c--hello--2.10.big_sur.bottle.tar.gz
SHA256: 69489ae397e4645127aa7773211310f81ebb6c99e1f8e3e22c5cdb55333f5408

What do you mean by saying PATH? The famous env variable?

Apparently @carlocab can understand me even when I talk drivel! I have no idea why I capitalised that 😅


How to use appsearch client for search with precision setting?

Custom precision for search does not work on current version, but somehow runable on older version (7.17.0 ).
I afraid that other part of code would not work as intended if I downgraded the lib. Please help
test = client.search(engine_name="esri-poi-711-location-search",
body={
"query": "acb",
"precision": 2                    })
---------------------------------------------------------------------------TypeError                                 Traceback (most recent call last)
Input In [6], in <cell line: 1>()
----> 1 test = client.search(engine_name="esri-poi-711-location-search",
2                     body={
3                         "query": "acb",
4                         "precision": 2      5                     })
File ~\miniconda3\lib\site-packages\elastic_enterprise_search_utils.py:454, in _rewrite_parameters..wrapper..wrapped(*args, **kwargs)
451         except KeyError:
452             pass--> 454 return api(*args, **kwargs)
TypeError: search() got an unexpected keyword argument 'precision'

I'm getting the same error, we built a python proxy service to sit between frontend and elastic, and since trying to implement precision does not work. Considering this issue has been here since 2022, that's reason to believe Elastic do not care. Please contradict this belief.


An error occurred during hot update!

Describe the bug
When the first startup, everything is well. Click the add button you can see counter change.Click the plus button again after modifying the content of the CounterProvider.tsx file, and nothing will happen on the page
Your Example Website or App
no,only happen when use vite hot update
Steps to Reproduce the Bug or Issue
npm i
npm start
click the add button, everything goes well
modify the content of CounterProvider file, save
click add button again, the counter no longer react
Expected behavior
the counter should be normal
Screenshots or Videos
No response
Platform
windows chrome
Additional context
No response

b1a62732-f8e7-46d0-b5b6-b1f6a4f583af.zip

I want to know what I missed?

This is a Solid Refresh based issue related to detached context. We have a PR for the fix. https://github.com/solidjs/solid-refresh/issues/24
I will close this as a duplicate for now. Track the issue there.

@ryansolid it seems that https://github.com/solidjs/solid-refresh/pull/34 doesn't work well on my demo

@liuyike98 because it isn't merged yet. Please wait for it to be merged.

@lxsmnsyc i know, i just download your newest branch, build dist, and replace the node_modules,fix require,and run again, but it just like before, headache for this a lot...

vite-plugin-solid must be changed too. I also I have already tested this on Vite.

@lxsmnsyc thanks for your reply, hope to get it soon


Merge linting phases into one megaphase

Unused, shadowing, and other future linting warns should be calculated in one megaphase. Right now, an undiagnosed issue is preventing us from doing that. The issue should be diagnosed and phases put in one megaphase

In my version, the problem was the way CheckShadowing was detecting the class type params it wanted. I kludged it a bit.


can we use openbabel instead of meeko to prepare PDBQT files?

we had trouble with meeko to prepare receptor pdbqt file:
mk_prepare_receptor.py -i 5tmn_protein.pdb -o 5tmn -p
mk_prepare_receptor.py: error: unrecognized arguments: -i 5tmn_protein.pdb -p

and we find it convenient to use openbabel:
$ obabel -ipdb 5tmn_protein.pdb -opdbqt -O 5tmn_protein.pdbqt
==============================
*** Open Babel Warning  in PerceiveBondOrders
  Failed to kekulize aromatic bonds in OBMol::PerceiveBondOrders (title is 5tmn_protein.pdb)

1 molecule converted

so is it correct to use obabel to prepare the pdbqt files? We didn't find that obabel approach recommended on your document website. https://autodock-vina.readthedocs.io/en/latest/docking_requirements.html#meeko

Hello @RJ-Li
That might to be a version issue. Could you try to re-install the latest meeko=0.6.1?
mk_prepare_receptor.py -i 5tmn.pdb -o 5tmn -p

worked for me with the raw 5tmn.pdb file from Protein Data Bank. See output:
5tmn.pdbqt.txt
I am responsible for the latest update on Vina documentation, but before that it didn't mention obabel for receptor preparation. Personally, I do not recommend obabel to prepare pdbqt file. Meeko uses a more sophisticated approach to perceive the macromolecule structure from PDB file by sanitizing the chemical structure. While Meeko is more stringent in its processing, it provides a feedback on any issues in the input file. You can at least use Meeko to pre-screen the receptor PDB file, and resort to Obabel only if you really need a quick workaround ^^


Sample code causes stack overflow on Scala 3.5.1

Your example code causes a stack overflow on Scala 3.5.1.
Replacing the implicit vals with givens fixes it.
Exception in thread "main" java.lang.StackOverflowError
	at PhobosTest$Journey$3$.<init>(PhobosTest.scala:23)
	at PhobosTest$.Journey$lzyINIT1$1(PhobosTest.scala:23)
	at PhobosTest$.PhobosTest$$$_$Journey$2(PhobosTest.scala:23)
	at PhobosTest$Journey$3$.<init>(PhobosTest.scala:24)
	at PhobosTest$.Journey$lzyINIT1$1(PhobosTest.scala:23)
	at PhobosTest$.PhobosTest$$$_$Journey$2(PhobosTest.scala:23)
	at PhobosTest$Journey$3$.<init>(PhobosTest.scala:24)
	at PhobosTest$.Journey$lzyINIT1$1(PhobosTest.scala:23)
	at PhobosTest$.PhobosTest$$$_$Journey$2(PhobosTest.scala:23)
	at PhobosTest$Journey$3$.<init>(PhobosTest.scala:24)
	at PhobosTest$.Journey$lzyINIT1$1(PhobosTest.scala:23)
	at PhobosTest$.PhobosTest$$$_$Journey$2(PhobosTest.scala:23)
	at PhobosTest$Journey$3$.<init>(PhobosTest.scala:24)
etc

Hi!
Could you please provide a full code sample (including build configuration) and info about phobos and java versions?
With sbt console compilation fails, so I should fix that, but I didn't manage to reproduce StackOverflowError both locally and in Scastie


clean up tapes for initialisation phase

What changes does this PR introduce?
cleanup of tape initialisation
What is the current behaviour?
A few tapes are never used, more than one tape defined for the same purpose, etc. see issue #440
What is the new behaviour
Code is a little cleaner, one unused file removed.
Does this PR introduce a breaking change?
Nope
Suggested addition to tag-index
o clean up of tape initialisation for the init-phase; affects

model/src/the_main_loop.F
pkg/ctrl/ctrl_map_ini_gentim2d.F (and a local version in verification/halfpipe_streamice)
remove unused pkg/ecco/cost_averages_bar_directives.h
adjust comment in pkg/autodiff/adread_adwrite.F

Looks good, thanks @mjlosch. Looks like a straightforward merge.

@owang01 thanks for having a look at this and good catch with "verification_other/lab_sea". There are a couple of special files in this experiment, that would need cleanup, aren't there? We could do this in a separate PR (following up on this one), but currently this experiment is not tested, is it? There's no "results" directory, or does it use the default results in "verification/lab_sea"? @jm-c?
@owang01, what do you think about the comments in adread_adwrite.F?

@mjlosch You're right. That experiment is not being tested so there is no need to change that experiment, at least for now.
The comments in adread_adwrite.F looks good to me.
I did not read carefully the discussion in issue #440 regarding tape dir names before this PR was opened (sorry for that) but have a (late) comment regarding removing "ctrltape" in favor of "dummytape": the first name gives a better idea of what is used for (storage of control vars) whereas "dummytape" is not really informative (+ if "dummy" variables need to be stored they are probably not "dummy" variables to start with).

I did not read carefully the discussion in issue #440 regarding tape dir names before this PR was opened (sorry for that) but have a (late) comment regarding removing "ctrltape" in favor of "dummytape": the first name gives a better idea of what is used for (storage of control vars) whereas "dummytape" is not really informative (+ if "dummy" variables need to be stored they are probably not "dummy" variables to start with).

The rational behind the name, is that it is not for the actual control variables but for the "dummy" control variables, i.e. the ones that are being passed to TAF. I don't know why they need storing.
The OpenAD experiments are now falling after the latest commit. Any idea why? The content of the commit cannot be the reason.

I am going to fix my mistake (regarding OpenAD).

Independently of the name dummytape or ctrltape, it is interesting that this tape is needed at all (only for xx_gentim2d_dummy). Maybe we can get rid of it altogether.

@mjlosch OK, it's fine to keep "dummytape" then.
Otherwise, will push unrelated little changes to update some comments in  main_do_loop.F (since, in this PR, you updated some comments in the_main_loop.F).

@mjlosch I am going to merge master in, re-running some tests, and then if it's OK with you will merge this PR soon.


Footer div is not placed in center

Issue Description
[Describe the problem or request here.]
Here is a screenshot of alignment of the footer's DIV :

Steps to Reproduce (if applicable)

Visit the Site, see the footer alignment

Expected Behavior
Should be placed in center i guess.
Current Behavior
Not placed in center, slightly aligned towards left.
Possible Solution (optional)

Fixing the CSS should do the job.

If you want @varun-singhh I can work on this issue ?

Please go ahead.

already fixed