Failed to get job complete status: <nil

Rancher versions:rancher/rancher Release v2.0.0
Infrastructure Stack versions:
healthcheck:
ipsec:
network-services:
scheduler:
kubernetes (if applicable):
**Docker version:  17.03.2-ce
**Operating system and kernel: Ubuntu  16.04.4 LTS
**Type/provider of hosts:  LAN
**Setup details:  HA rancher, internal DB
**Environment Template: Kubernetes
Steps to Reproduce:
I'm a noob to user Rancher
I hava four ubuntu machine in my Local area network
hosts <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>
I wan't to set up rancher with kubernetes  on my machines
see this document  https://rancher.com/docs/rancher/v2.x/en/installation/server-installation/ha-server-install/#provision-linux-hosts
do it on my host  <IP_ADDRESS>
take the rke
rke version v0.1.6
down the .yml file
but the .yml  file  i don't  know  how to write it
I can only guess
##----------------------------------------the third part--------------------------------------------
spec:
rules:

host:  <IP_ADDRESS>
http:
paths:

backend:
serviceName: cattle-service
servicePort: 80
tls:

secretName: cattle-keys-ingress
hosts:

<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>

##--------------------------------------the fourth part------------------------------------------
i use the cfssl tools to make ssl files and copy to other machines
root@server01:/opt/cert# cat ca-config.json
{
"signing": {
"default": {
"expiry": "43800h"
},
"profiles": {
"server": {
"expiry": "43800h",
"usages": [
"signing",
"key encipherment",
"server auth"
]
},
"client": {
"expiry": "43800h",
"usages": [
"signing",
"key encipherment",
"client auth"
]
}
}
}
}
root@server01:/opt/cert# cat ca-csr.json
{
"CN": "Self Signed Ca",
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"L": "HB",
"ST": "TS"
}
]
}
root@server01:/opt/cert# cfssl gencert -initca ca-csr.json | cfssljson -bare ca -
root@server01:/opt/cert# cat server.json
{
"CN": "server",
"hosts": [
"<IP_ADDRESS>",
"<IP_ADDRESS>",
"<IP_ADDRESS>",
"<IP_ADDRESS>",
"<IP_ADDRESS>",
"<IP_ADDRESS>"
],
"key": {
"algo": "ecdsa",
"size": 256
},
"names": [
{
"C": "CN",
"L": "HB",
"ST": "TS"
}
]
}
root@server01:/opt/cert# cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=server server.json | cfssljson -bare server
root@server01:/opt/cert# cat client.json
{
"CN": "Client",
"hosts": [],
"key": {
"algo": "ecdsa",
"size": 256
},
"names": [
{
"C": "CN",
"L": "HB",
"ST": "TS"
}
]
}
root@server01:/opt/cert# cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=client client.json | cfssljson -bare client
and turn the client.pem to client.crt
root@server01:/opt/cert# openssl x509 -outform der -in client.pem -out client.crt
now i have these certificate files
root@server01:/opt/cert# ls
ca-config.json  ca-csr.json  ca-key.pem  ca.csr  ca.pem  client-key.pem  client.crt  client.csr  client.json  client.pem  server-key.pem  server.csr  server.json  server.pem
i write these to .yml file
apiVersion: v1
kind: Secret
metadata:
name: cattle-keys-server
namespace: cattle-system
type: Opaque
data:
cert.pem: /opt/cert/server.pem    # ssl cert for cattle server.
key.pem: /opt/cert/server-key.pem     # ssl key for cattle server.
cacerts.pem: /opt/cert/ca.pem  # CA cert used to sign cattle server cert and key
##--------------------------------------the fifth part------------------------------------------
apiVersion: v1
kind: Secret
metadata:
name: cattle-keys-ingress
namespace: cattle-system
type: Opaque
data:
tls.crt: /opt/cert/client.crt  # ssl cert for ingress. If self-signed, must be signed by same CA as cattle server
tls.key: /opt/cert/client-key.pem  # ssl key for ingress. If self-signed, must be signed by same CA as cattle server
Now I
root@server01:/apps/rancher# ./rke up --config kube_config_4-node-certificate.yml
Results:
INFO[0000] Building Kubernetes cluster
INFO[0000] [dialer] Setup tunnel for host [<IP_ADDRESS>]
INFO[0000] [dialer] Setup tunnel for host [<IP_ADDRESS>]
INFO[0000] [dialer] Setup tunnel for host [<IP_ADDRESS>]
INFO[0000] [dialer] Setup tunnel for host [<IP_ADDRESS>]
INFO[0000] [network] Deploying port listener containers
INFO[0001] [network] Successfully started [rke-etcd-port-listener] container on host [<IP_ADDRESS>]
INFO[0001] [network] Successfully started [rke-etcd-port-listener] container on host [<IP_ADDRESS>]
INFO[0001] [network] Successfully started [rke-etcd-port-listener] container on host [<IP_ADDRESS>]
INFO[0002] [network] Successfully started [rke-cp-port-listener] container on host [<IP_ADDRESS>]
INFO[0002] [network] Successfully started [rke-worker-port-listener] container on host [<IP_ADDRESS>]
INFO[0002] [network] Successfully started [rke-worker-port-listener] container on host [<IP_ADDRESS>]
INFO[0003] [network] Successfully started [rke-worker-port-listener] container on host [<IP_ADDRESS>]
INFO[0003] [network] Successfully started [rke-worker-port-listener] container on host [<IP_ADDRESS>]
INFO[0003] [network] Port listener containers deployed successfully
INFO[0003] [network] Running etcd <-> etcd port checks
INFO[0003] [network] Successfully started [rke-port-checker] container on host [<IP_ADDRESS>]
INFO[0003] [network] Successfully started [rke-port-checker] container on host [<IP_ADDRESS>]
INFO[0004] [network] Successfully started [rke-port-checker] container on host [<IP_ADDRESS>]
INFO[0004] [network] Running control plane -> etcd port checks
INFO[0004] [network] Successfully started [rke-port-checker] container on host [<IP_ADDRESS>]
INFO[0005] [network] Running control plane -> worker port checks
INFO[0005] [network] Successfully started [rke-port-checker] container on host [<IP_ADDRESS>]
INFO[0005] [network] Running workers -> control plane port checks
INFO[0006] [network] Successfully started [rke-port-checker] container on host [<IP_ADDRESS>]
INFO[0006] [network] Successfully started [rke-port-checker] container on host [<IP_ADDRESS>]
INFO[0006] [network] Successfully started [rke-port-checker] container on host [<IP_ADDRESS>]
INFO[0006] [network] Successfully started [rke-port-checker] container on host [<IP_ADDRESS>]
INFO[0007] [network] Checking KubeAPI port Control Plane hosts
INFO[0007] [network] Removing port listener containers
INFO[0007] [remove/rke-etcd-port-listener] Successfully removed container on host [<IP_ADDRESS>]
INFO[0007] [remove/rke-etcd-port-listener] Successfully removed container on host [<IP_ADDRESS>]
INFO[0007] [remove/rke-etcd-port-listener] Successfully removed container on host [<IP_ADDRESS>]
INFO[0007] [remove/rke-cp-port-listener] Successfully removed container on host [<IP_ADDRESS>]
INFO[0008] [remove/rke-worker-port-listener] Successfully removed container on host [<IP_ADDRESS>]
INFO[0008] [remove/rke-worker-port-listener] Successfully removed container on host [<IP_ADDRESS>]
INFO[0008] [remove/rke-worker-port-listener] Successfully removed container on host [<IP_ADDRESS>]
INFO[0008] [remove/rke-worker-port-listener] Successfully removed container on host [<IP_ADDRESS>]
INFO[0008] [network] Port listener containers removed successfully
INFO[0008] [certificates] Attempting to recover certificates from backup on [etcd] hosts
INFO[0008] [certificates] Successfully started [cert-fetcher] container on host [<IP_ADDRESS>]
INFO[0009] [certificates] Successfully started [cert-fetcher] container on host [<IP_ADDRESS>]
INFO[0010] [certificates] Successfully started [cert-fetcher] container on host [<IP_ADDRESS>]
INFO[0010] [certificates] No Certificate backup found on [etcd] hosts
INFO[0010] [certificates] Generating CA kubernetes certificates
INFO[0011] [certificates] Generating Kubernetes API server certificates
INFO[0013] [certificates] Generating Kube Controller certificates
INFO[0014] [certificates] Generating Kube Scheduler certificates
INFO[0014] [certificates] Generating Kube Proxy certificates
INFO[0015] [certificates] Generating Node certificate
INFO[0015] [certificates] Generating admin certificates and kubeconfig
INFO[0016] [certificates] Generating etcd-<IP_ADDRESS> certificate and key
INFO[0016] [certificates] Generating etcd-<IP_ADDRESS> certificate and key
INFO[0017] [certificates] Generating etcd-<IP_ADDRESS> certificate and key
INFO[0017] [certificates] Temporarily saving certs to [etcd] hosts
INFO[0023] [certificates] Saved certs to [etcd] hosts
INFO[0023] [reconcile] Reconciling cluster state
INFO[0023] [reconcile] This is newly generated cluster
INFO[0023] [certificates] Deploying kubernetes certificates to Cluster nodes
INFO[0030] Successfully Deployed local admin kubeconfig at [./kube_config_4-node-certificate.yml]
INFO[0030] [certificates] Successfully deployed kubernetes certificates to Cluster nodes
INFO[0030] Pre-pulling kubernetes images
INFO[0030] Kubernetes images pulled successfully
INFO[0030] [etcd] Building up etcd plane..
INFO[0030] [etcd] Successfully started [etcd] container on host [<IP_ADDRESS>]
INFO[0030] [etcd] Successfully started [rke-log-linker] container on host [<IP_ADDRESS>]
INFO[0031] [remove/rke-log-linker] Successfully removed container on host [<IP_ADDRESS>]
INFO[0031] [etcd] Successfully started [etcd] container on host [<IP_ADDRESS>]
INFO[0031] [etcd] Successfully started [rke-log-linker] container on host [<IP_ADDRESS>]
INFO[0031] [remove/rke-log-linker] Successfully removed container on host [<IP_ADDRESS>]
INFO[0032] [etcd] Successfully started [etcd] container on host [<IP_ADDRESS>]
INFO[0034] [etcd] Successfully started [rke-log-linker] container on host [<IP_ADDRESS>]
INFO[0034] [remove/rke-log-linker] Successfully removed container on host [<IP_ADDRESS>]
INFO[0034] [etcd] Successfully started etcd plane..
INFO[0034] [controlplane] Building up Controller Plane..
INFO[0034] [controlplane] Successfully started [kube-apiserver] container on host [<IP_ADDRESS>]
INFO[0034] [healthcheck] Start Healthcheck on service [kube-apiserver] on host [<IP_ADDRESS>]
INFO[0048] [healthcheck] service [kube-apiserver] on host [<IP_ADDRESS>] is healthy
INFO[0048] [controlplane] Successfully started [rke-log-linker] container on host [<IP_ADDRESS>]
INFO[0048] [remove/rke-log-linker] Successfully removed container on host [<IP_ADDRESS>]
INFO[0049] [controlplane] Successfully started [kube-controller-manager] container on host [<IP_ADDRESS>]
INFO[0049] [healthcheck] Start Healthcheck on service [kube-controller-manager] on host [<IP_ADDRESS>]
INFO[0054] [healthcheck] service [kube-controller-manager] on host [<IP_ADDRESS>] is healthy
INFO[0054] [controlplane] Successfully started [rke-log-linker] container on host [<IP_ADDRESS>]
INFO[0055] [remove/rke-log-linker] Successfully removed container on host [<IP_ADDRESS>]
INFO[0055] [controlplane] Successfully started [kube-scheduler] container on host [<IP_ADDRESS>]
INFO[0055] [healthcheck] Start Healthcheck on service [kube-scheduler] on host [<IP_ADDRESS>]
INFO[0060] [healthcheck] service [kube-scheduler] on host [<IP_ADDRESS>] is healthy
INFO[0060] [controlplane] Successfully started [rke-log-linker] container on host [<IP_ADDRESS>]
INFO[0061] [remove/rke-log-linker] Successfully removed container on host [<IP_ADDRESS>]
INFO[0061] [controlplane] Successfully started Controller Plane..
INFO[0061] [authz] Creating rke-job-deployer ServiceAccount
INFO[0061] [authz] rke-job-deployer ServiceAccount created successfully
INFO[0061] [authz] Creating system:node ClusterRoleBinding
INFO[0061] [authz] system:node ClusterRoleBinding created successfully
INFO[0061] [certificates] Save kubernetes certificates as secrets
INFO[0061] [certificates] Successfully saved certificates as kubernetes secret [k8s-certs]
INFO[0061] [state] Saving cluster state to Kubernetes
INFO[0061] [state] Successfully Saved cluster state to Kubernetes ConfigMap: cluster-state
INFO[0061] [worker] Building up Worker Plane..
INFO[0061] [sidekick] Sidekick container already created on host [<IP_ADDRESS>]
INFO[0061] [worker] Successfully started [kubelet] container on host [<IP_ADDRESS>]
INFO[0061] [healthcheck] Start Healthcheck on service [kubelet] on host [<IP_ADDRESS>]
INFO[0061] [worker] Successfully started [nginx-proxy] container on host [<IP_ADDRESS>]
INFO[0062] [worker] Successfully started [rke-log-linker] container on host [<IP_ADDRESS>]
INFO[0062] [remove/rke-log-linker] Successfully removed container on host [<IP_ADDRESS>]
INFO[0062] [worker] Successfully started [nginx-proxy] container on host [<IP_ADDRESS>]
INFO[0062] [worker] Successfully started [nginx-proxy] container on host [<IP_ADDRESS>]
INFO[0062] [worker] Successfully started [kubelet] container on host [<IP_ADDRESS>]
INFO[0062] [healthcheck] Start Healthcheck on service [kubelet] on host [<IP_ADDRESS>]
INFO[0063] [worker] Successfully started [rke-log-linker] container on host [<IP_ADDRESS>]
INFO[0063] [worker] Successfully started [rke-log-linker] container on host [<IP_ADDRESS>]
INFO[0064] [remove/rke-log-linker] Successfully removed container on host [<IP_ADDRESS>]
INFO[0064] [remove/rke-log-linker] Successfully removed container on host [<IP_ADDRESS>]
INFO[0065] [worker] Successfully started [kubelet] container on host [<IP_ADDRESS>]
INFO[0065] [healthcheck] Start Healthcheck on service [kubelet] on host [<IP_ADDRESS>]
INFO[0066] [worker] Successfully started [kubelet] container on host [<IP_ADDRESS>]
INFO[0066] [healthcheck] Start Healthcheck on service [kubelet] on host [<IP_ADDRESS>]
INFO[0067] [healthcheck] service [kubelet] on host [<IP_ADDRESS>] is healthy
INFO[0067] [worker] Successfully started [rke-log-linker] container on host [<IP_ADDRESS>]
INFO[0067] [remove/rke-log-linker] Successfully removed container on host [<IP_ADDRESS>]
INFO[0067] [worker] Successfully started [kube-proxy] container on host [<IP_ADDRESS>]
INFO[0067] [healthcheck] Start Healthcheck on service [kube-proxy] on host [<IP_ADDRESS>]
INFO[0068] [healthcheck] service [kubelet] on host [<IP_ADDRESS>] is healthy
INFO[0068] [worker] Successfully started [rke-log-linker] container on host [<IP_ADDRESS>]
INFO[0068] [remove/rke-log-linker] Successfully removed container on host [<IP_ADDRESS>]
INFO[0069] [worker] Successfully started [kube-proxy] container on host [<IP_ADDRESS>]
INFO[0069] [healthcheck] Start Healthcheck on service [kube-proxy] on host [<IP_ADDRESS>]
INFO[0070] [healthcheck] service [kubelet] on host [<IP_ADDRESS>] is healthy
INFO[0071] [healthcheck] service [kubelet] on host [<IP_ADDRESS>] is healthy
INFO[0071] [worker] Successfully started [rke-log-linker] container on host [<IP_ADDRESS>]
INFO[0072] [remove/rke-log-linker] Successfully removed container on host [<IP_ADDRESS>]
INFO[0072] [worker] Successfully started [rke-log-linker] container on host [<IP_ADDRESS>]
INFO[0072] [worker] Successfully started [kube-proxy] container on host [<IP_ADDRESS>]
INFO[0072] [healthcheck] Start Healthcheck on service [kube-proxy] on host [<IP_ADDRESS>]
INFO[0073] [remove/rke-log-linker] Successfully removed container on host [<IP_ADDRESS>]
INFO[0073] [healthcheck] service [kube-proxy] on host [<IP_ADDRESS>] is healthy
INFO[0073] [worker] Successfully started [rke-log-linker] container on host [<IP_ADDRESS>]
INFO[0073] [remove/rke-log-linker] Successfully removed container on host [<IP_ADDRESS>]
INFO[0073] [worker] Successfully started [kube-proxy] container on host [<IP_ADDRESS>]
INFO[0073] [healthcheck] Start Healthcheck on service [kube-proxy] on host [<IP_ADDRESS>]
INFO[0074] [healthcheck] service [kube-proxy] on host [<IP_ADDRESS>] is healthy
INFO[0074] [worker] Successfully started [rke-log-linker] container on host [<IP_ADDRESS>]
INFO[0075] [remove/rke-log-linker] Successfully removed container on host [<IP_ADDRESS>]
INFO[0078] [healthcheck] service [kube-proxy] on host [<IP_ADDRESS>] is healthy
INFO[0079] [healthcheck] service [kube-proxy] on host [<IP_ADDRESS>] is healthy
INFO[0079] [worker] Successfully started [rke-log-linker] container on host [<IP_ADDRESS>]
INFO[0079] [remove/rke-log-linker] Successfully removed container on host [<IP_ADDRESS>]
INFO[0080] [worker] Successfully started [rke-log-linker] container on host [<IP_ADDRESS>]
INFO[0080] [remove/rke-log-linker] Successfully removed container on host [<IP_ADDRESS>]
INFO[0080] [worker] Successfully started Worker Plane..
INFO[0080] [sync] Syncing nodes Labels and Taints
INFO[0083] [sync] Successfully synced nodes Labels and Taints
INFO[0083] [network] Setting up network plugin: canal
INFO[0083] [addons] Saving addon ConfigMap to Kubernetes
INFO[0083] [addons] Successfully Saved addon to Kubernetes ConfigMap: rke-network-plugin
INFO[0083] [addons] Executing deploy job..
INFO[0088] [addons] Setting up KubeDNS
INFO[0088] [addons] Saving addon ConfigMap to Kubernetes
INFO[0088] [addons] Successfully Saved addon to Kubernetes ConfigMap: rke-kubedns-addon
INFO[0088] [addons] Executing deploy job..
INFO[0093] [addons] KubeDNS deployed successfully..
INFO[0093] [ingress] Setting up nginx ingress controller
INFO[0093] [addons] Saving addon ConfigMap to Kubernetes
INFO[0093] [addons] Successfully Saved addon to Kubernetes ConfigMap: rke-ingress-controller
INFO[0093] [addons] Executing deploy job..
INFO[0099] [ingress] ingress controller nginx is successfully deployed
INFO[0099] [addons] Setting up user addons
INFO[0099] [addons] Saving addon ConfigMap to Kubernetes
INFO[0099] [addons] Successfully Saved addon to Kubernetes ConfigMap: rke-user-addon
INFO[0099] [addons] Executing deploy job..
ERRO[0124] Failed to get job complete status:
FATA[0124] Failed to deploy addon execute job: Failed to get job complete status:

Facing the exact same issue, any luck with this?

The content needs to be base64 encoded and saved in the yaml as described here: https://rancher.com/docs/rancher/v2.x/en/installation/single-node-install/#option-b-bring-your-own-certificate-self-signed
You can't use filenames.

Also, both host andhosts should be the FQDN you use to connect to your cluster.

Does this assume that the load balancer is set up first? There is no FQDN for the cluster before that I guess.

Updated the link to https://rancher.com/docs/rancher/v2.x/en/installation/ha-server-install/#overview
You can follow the steps on there. There is no dependency on the LB when setting it up, because the ingress controller will be able to respond to requests individually as well.

Same error this is my yml:
nodes:
  - address: xx.xx.xx.xx # hostname or IP to access nodes
    user: root # root user (usually 'root')
    role: [controlplane,etcd] # K8s roles for node
    ssh_key_path: ~/.ssh/id_rsa # path to PEM file
  - address: xx.xx.xx.xx
    user: root
    role: [controlplane,etcd]
    ssh_key_path: ~/.ssh/id_rsa
  - address: xx.xx.xx.xx
    user: root
    role: [controlplane,etcd]
    ssh_key_path: ~/.ssh/id_rsa
  - address: xx.xx.xx.xx
    user: root
    role: [worker]
    ssh_key_path: ~/.ssh/id_rsa
  - address: xx.xx.xx.xx
    user: root
    role: [worker]
    ssh_key_path: ~/.ssh/id_rsa
  - address: xx.xx.xx.xx
    user: root
    role: [worker]
    ssh_key_path: ~/.ssh/id_rsa

addons: |-
  ---
  kind: Namespace
  apiVersion: v1
  metadata:
    name: cattle-system
  ---
  kind: ServiceAccount
  apiVersion: v1
  metadata:
    name: cattle-admin
    namespace: cattle-system
  ---
  kind: ClusterRoleBinding
  apiVersion: rbac.authorization.k8s.io/v1
  metadata:
    name: cattle-crb
    namespace: cattle-system
  subjects:
  - kind: ServiceAccount
    name: cattle-admin
    namespace: cattle-system
  roleRef:
    kind: ClusterRole
    name: cluster-admin
    apiGroup: rbac.authorization.k8s.io
  ---
  apiVersion: v1
  kind: Secret
  metadata:
    name: cattle-keys-ingress
    namespace: cattle-system
  type: Opaque
  data:
    tls.crt:
[encoded data, 4864 characters]
    tls.key:
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  b3FKL3dkNQo2ME9uNERTWVM3V0d4eWkrNlFzT3dNN1ZTTFppanBYKzFFTjBoenN4
  SmdPeUF5RVROYzlTCi0tLS0tRU5EIFJTQSBQUklWQVRFIEtFWS0tLS0tCg==
  ---
  apiVersion: v1
  kind: Service
  metadata:
    namespace: cattle-system
    name: cattle-service
    labels:
      app: cattle
  spec:
    ports:
    - port: 80
      targetPort: 80
      protocol: TCP
      name: http
    - port: 443
      targetPort: 443
      protocol: TCP
      name: https
    selector:
      app: cattle
  ---
  apiVersion: extensions/v1beta1
  kind: Ingress
  metadata:
    namespace: cattle-system
    name: cattle-ingress-http
    annotations:
      nginx.ingress.kubernetes.io/proxy-connect-timeout: "30"
      nginx.ingress.kubernetes.io/proxy-read-timeout: "1800"   # Max time in seconds for ws to remain shell window open
      nginx.ingress.kubernetes.io/proxy-send-timeout: "1800"   # Max time in seconds for ws to remain shell window open
  spec:
    rules:
    - host: rancher.xx.xx  # FQDN to access cattle server
      http:
        paths:
        - backend:
            serviceName: cattle-service
            servicePort: 80
    tls:
    - secretName: cattle-keys-ingress
      hosts:
      - rancher.xx.xx      # FQDN to access cattle server
  ---
  kind: Deployment
  apiVersion: extensions/v1beta1
  metadata:
    namespace: cattle-system
    name: cattle
  spec:
    replicas: 1
    template:
      metadata:
        labels:
          app: cattle
      spec:
        serviceAccountName: cattle-admin
        containers:
        - image: rancher/rancher:latest
          imagePullPolicy: Always
          name: cattle-server
          ports:
          - containerPort: 80
            protocol: TCP
          - containerPort: 443
            protocol: TCP

Interface access show error default backend - 404

>kubectl --kubeconfig kube_config_rancher-cluster.yml logs -l job-name=rke-user-addon-deploy-job -n kube-system Error from server (NotFound): the server could not find the requested resource ( pods/log rke-user-addon-deploy-job-7hgx2)
>kubectl --kubeconfig kube_config_rancher-cluster.yml -n kube-system logs rke-user-addon-deploy-job-vcmdz Error from server (NotFound): the server could not find the requested resource ( pods/log rke-user-addon-deploy-job-vcmdz)
>kubectl --kubeconfig kube_config_rancher-cluster.yml -n kube-system describe pod rke-user-addon-deploy-job-vcmdz
Name:           rke-user-addon-deploy-job-vcmdz
Namespace:      kube-system
Node:           <IP_ADDRESS>/
Labels:         controller-uid=ecec4407-6d16-11e8-bcd3-9600000b7e21
                job-name=rke-user-addon-deploy-job
Annotations:    <none>
Status:         Pending
IP:
Controlled By:  Job/rke-user-addon-deploy-job
Containers:
  rke-user-addon-pod:
    Image:      rancher/hyperkube:v1.10.1-rancher2
    Port:       <none>
    Host Port:  <none>
    Command:
      kubectl
      apply
      -f
      /etc/config/rke-user-addon.yaml
    Environment:  <none>
    Mounts:
      /etc/config from config-volume (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from rke-job-deployer-token-nz5hv (ro)
Volumes:
  config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      rke-user-addon
    Optional:  false
  rke-job-deployer-token-nz5hv:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  rke-job-deployer-token-nz5hv
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:          <none>

I will try concat all lines in cert. I did try with | syntax to multiline yml, no progress

Also use certutil to create the base64. I will try something different.

@superseb @Ze8898  Problem solved. In my case the custom SSL was wrong base64.
The way it works, is with the command:
cat certificate.key | base64 -w 0 > certificate.key.base64

Note the use of -w 0 which removes \n.
Certutil didn't work for me.
Thanks.

See at How Can I Encode My PEM Files in base64? at https://rancher.com/docs/rancher/v2.x/en/installation/ha-server-install/#faq-and-troubleshooting
Anyone else encountering this error, please file a new issue with the steps described.


Implements custom method subjects

The PR also includes a new option that controls how to build the default subject for a service and a method.

This PR almost complete #7, the only missing piece is the method subject parameters.


Windows Support

Now that the camera plugin works on Windows, it is definetely possible to leverage the existing WinRT APIs to support this on Windows 10+.

We need support for Windows

Is there any plan to add Windows support? Is there any update? It will be nice to have ✨


Waf add route link

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

Do not merge for now, will reopen later on.

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk


Update README.md

Fixes: https://github.com/microsoft/dotnet/issues/1308
Adding changelog to this readme, with information about updates in each release.

cc @YoshiRulz


Inconsistent SuperGLUE Results from P-Tuning and P-TuningV2 Paper

Hi, I find most of the SuperGLUE metrics of PT reported in P-Tuning paper are superior to metrics of fine-tuning. But the metrics of PT reported in P-TuningV2 paper are much worse than fine-tuning. For example in BoolQ tasks, in P-Tuning paper the acc is 72.9 for fine-tuning and 73.9 for PT. While in P-TuningV2 paper the acc is 77.7 for fine-tuning and 67.2 for PT.
It seems that from P-TuningV2 paper is much worse than fine-tuning which is opposite to the conclusion from P-Tuning paper.

@theoqian Hi,
I think this issue in P-tuning v2 repo asks the same problem as yours. It is because in P-tuning v2 we report a fixed backbone version of P-tuning v1 to follow the experimental setting of Lesters et al.'s setting.

Thanks for your reply.


Suggestion: Not allow voting for own pictures, videos and albums

At the moment is it possible to vote for the own pictures, videos and albums, what I believe that it's not good. Now only voting for the own profile is not allowed.
This feature is now already integrated in my fork. I can make a PR if you believe that it's of public interest.

Great, please do so and I will be glad to review it :)
Indeed, it's not a bug, but actually it might be wrong to allow users to rate their own contents, so your PR is welcome! 🤗


node-red-pi --help is a bad option but it's shown in the help

What are the steps to reproduce?
node-red-pi --help
What happens?
$ node-red-pi --help
Node-RED v1.0.3
Usage: node-red [-v] [-?] [--settings settings.js] [--userDir DIR]
                [--port PORT] [--title TITLE] [--safe] [flows.json]

Options:
  -p, --port     PORT  port to listen on
  -s, --settings FILE  use specified settings file
      --title    TITLE process window title
  -u, --userDir  DIR   use specified user directory
  -v, --verbose        enable verbose output
      --safe           enable safe mode
  -?, --help           show this help

Documentation can be found at http://nodered.org
$ node-red-pi --safe --max-old-space-size=256
node: bad option: --safe

What do you expect to happen?
It just works.
Please tell us about your environment:
Node-RED version: v1.0.3
Node.js  version: v12.14.0
npm version 6.13.4
Linux 4.19.75-v7+ arm LE (Raspberry 3B+)

if you use the actual command node-red --safe as shown in the usage it should work. You are using node-red-pi which is a shortcut command. that passes different options down to the underlying node process.

Yes, it worked, thanks.


⚠ Bofrost.be has degraded performance

In a6d7341, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1765 ms

Resolved: Bofrost.be performance has improved in 3e0df0d.


Toast background filter blur rendering issue in Safari

Rendering issue toast in safari only visible when there's an image behind the toast.
The background blur is broken at the left side of the toast. When you don't use a header, it's also broken at the top.

I also found out, that when you remove the box-shadow of the toast, the issues disappears. As a box shadow for a toast is a must in my eyes, this is not a solution.
I made a codepen to as example: https://codepen.io/katrienvh/pen/JjYebmy

Operating system and version: macOS Catalina version 10.15.4
Browser and version: Safari version 13.1

Yeah, I've been noticing some issues in Safari with this CSS in a few locations. Will look into it further to see if there's a fix, and if not, I'll likely just remove it.


Filter profiling tool based on start time.

Closes: #4323
Added an option (--start-app-time and -s) in Profiling tool to filter event logs using application start time. This is similar to the one used in Qualification tools.
Examples:

--start-app-time 1d <event-logs>

22/06/27 11:38:02 INFO FilterAppInfo: Parsing Event Log: file:/Users/psarthi/Desktop/Work/profiling/event-logs/local-1655514904001
22/06/27 11:38:02 INFO FilterAppInfo: Parsing Event Log: file:/Users/psarthi/Desktop/Work/profiling/event-logs/local-1655514789396
22/06/27 11:38:03 INFO FilterAppInfo: Total number of events parsed: 6 for file:/Users/psarthi/Desktop/Work/profiling/event-logs/local-1655514789396
22/06/27 11:38:03 INFO FilterAppInfo: Total number of events parsed: 6 for file:/Users/psarthi/Desktop/Work/profiling/event-logs/local-1655514904001
22/06/27 11:38:03 WARN ProfileMain: No event logs to process after checking paths, exiting!

--start-app-time 1m <event-logs>

22/06/27 11:46:40 INFO FilterAppInfo: Parsing Event Log: file:/Users/psarthi/Desktop/Work/profiling/event-logs/local-1655514789396
22/06/27 11:46:40 INFO FilterAppInfo: Parsing Event Log: file:/Users/psarthi/Desktop/Work/profiling/event-logs/local-1655514904001
22/06/27 11:46:41 INFO FilterAppInfo: Total number of events parsed: 6 for file:/Users/psarthi/Desktop/Work/profiling/event-logs/local-1655514904001
22/06/27 11:46:41 INFO FilterAppInfo: Total number of events parsed: 6 for file:/Users/psarthi/Desktop/Work/profiling/event-logs/local-1655514789396
22/06/27 11:46:41 INFO Profiler: Threadpool size is 3
22/06/27 11:46:41 INFO ApplicationInfo: Parsing Event Log: file:/Users/psarthi/Desktop/Work/profiling/event-logs/local-1655514904001
22/06/27 11:46:41 INFO ApplicationInfo: Parsing Event Log: file:/Users/psarthi/Desktop/Work/profiling/event-logs/local-1655514789396

Signed-off-by : Partho Sarthi<EMAIL_ADDRESS>

build

Please update the profiling tool doc - https://github.com/NVIDIA/spark-rapids/blob/branch-22.08/docs/spark-profiling-tool.md#profiling-tool-options

Could you please push the updated  spark-profiling-tool.md  file in this PR.

build

build


negative value starting from 0

I am using this plugin. In middle of stack  i have a negative value. Which is starting from 0. Is there any way that will start from where its previous stack ended?

A negative value in the stack only makes sense if the balance of the total chart needs is negative at this point.
Let's say your first element has the value + 100, then this stack simply has that amount for its data field. If the next element has a value of - 30, it will only decrease the total balance by 30 to 70. So the visible bar needs a height (and therefore data-value) of 70, and the dummy stack would be 70-30=40.
If you want to display negative balances you can do the same just with negative data elements:
        {
            data: [-60],
            waterfall: {
                dummyStack: true,
            },
            stack: 'stack 5',
        },
        {
            label: 'Some Text',
            data: [-100],
            backgroundColor: '#a538ab',
            stack: 'stack 5',
        },

This would give you a waterfall element starting at -60, going down 40 to -100.
If your previous stack is positive, however, you will run into sum problems.
Example: Stack 1 ends at 30, stack 2 should go down 50 to end at -20. If you want to do something like this, you would have to split the second stack into two elements, one with a value of 30, the second one with a value of -20:
        {
            label: 'Another label',
            data: [30],
            backgroundColor: '#a538ab',
            stack: 'stack 5',
        },
        {
            label: 'Another label',
            data: [-20],
            backgroundColor: '#a538ab',
            stack: 'stack 5',
        },

This will however leave you with two labels in the legend, so you might want to turn that off.
I hope I could help you, otherwise please post your dataset or a picture of what you are trying to achieve.


Liquid Exception: undefined method `[]' for nil:NilClass in _drafts/JekyllAnchors.md/#excerpt

When I try to use the picture tag I am constantly getting this error:
Liquid Exception: undefined method `[]' for nil:NilClass in _drafts/JekyllAnchors.md/#excerpt
Trace:
  Liquid Exception: undefined method `[]' for nil:NilClass in _drafts/JekyllAnchors.md/#excerpt
/home/vit/work/vrepinblog/_plugins/jekyll-picture-tag.rb:43:in `render': undefined method `[]' for nil:NilClass (NoMethodError)
	from /usr/lib64/ruby/gems/2.1.0/gems/liquid-2.6.2/lib/liquid/block.rb:109:in `block in render_all'
	from /usr/lib64/ruby/gems/2.1.0/gems/liquid-2.6.2/lib/liquid/block.rb:96:in `each'
	from /usr/lib64/ruby/gems/2.1.0/gems/liquid-2.6.2/lib/liquid/block.rb:96:in `render_all'
	from /usr/lib64/ruby/gems/2.1.0/gems/liquid-2.6.2/lib/liquid/block.rb:82:in `render'
	from /usr/lib64/ruby/gems/2.1.0/gems/liquid-2.6.2/lib/liquid/template.rb:128:in `render'
	from /usr/lib64/ruby/gems/2.1.0/gems/liquid-2.6.2/lib/liquid/template.rb:138:in `render!'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/convertible.rb:106:in `render_liquid'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/convertible.rb:233:in `do_layout'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/post.rb:258:in `render'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/site.rb:298:in `block in render'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/site.rb:297:in `each'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/site.rb:297:in `render'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/site.rb:51:in `process'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/command.rb:28:in `process_site'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/commands/build.rb:56:in `build'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/commands/build.rb:34:in `process'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/commands/build.rb:18:in `block (2 levels) in init_with_program'
	from /usr/lib64/ruby/gems/2.1.0/gems/mercenary-0.3.5/lib/mercenary/command.rb:220:in `call'
	from /usr/lib64/ruby/gems/2.1.0/gems/mercenary-0.3.5/lib/mercenary/command.rb:220:in `block in execute'
	from /usr/lib64/ruby/gems/2.1.0/gems/mercenary-0.3.5/lib/mercenary/command.rb:220:in `each'
	from /usr/lib64/ruby/gems/2.1.0/gems/mercenary-0.3.5/lib/mercenary/command.rb:220:in `execute'
	from /usr/lib64/ruby/gems/2.1.0/gems/mercenary-0.3.5/lib/mercenary/program.rb:42:in `go'
	from /usr/lib64/ruby/gems/2.1.0/gems/mercenary-0.3.5/lib/mercenary.rb:19:in `program'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/bin/jekyll:20:in `<top (required)>'
	from /usr/bin/jekyll:9:in `load'
	from /usr/bin/jekyll:9:in `<main>'

My source file has basically one line in the content section:
{% picture  anchor.jpg %}
Jekyll version: 2.5.3
_config related to picture:
picture:
  source: "assets/imgs/_fullsize"
  output: "generated"
  markup: "picture"

I use redcarpet processor and re-define excerpt_separator.

I believe you need to define presets, so something like this:
picture:
  source: "assets/imgs/_fullsize"
  output: "generated"
  markup: "picture"
  presets:
    default:
      ppi: [1, 1.5]
    source_medium:
      media: "(min-width: 40em)"
      width: "600"
      height: "300"
    source_default:
      width: "300"

I did it:
picture:
  source: "assets/imgs/_fullsize"
  output: "generated"
  markup: "picture"
  presets:
    default:
      ppi: [1, 1.5]
    source_medium:
      media: "(min-width: 40em)"
      width: "600"
      height: "300"
    source_default:
      width: "300"

Unfortunately the behavior is exactly the same:
$ jekyll b --drafts --trace
Configuration file: /home/vit/work/vrepinblog/_config.yml
            Source: /home/vit/work/vrepinblog
       Destination: /home/vit/work/vrepinblog/_site
      Generating...
  Liquid Exception: undefined method `[]' for nil:NilClass in _drafts/JekyllAnchors.md/#excerpt
/home/vit/work/vrepinblog/_plugins/jekyll-picture-tag.rb:162:in `render': undefined method `[]' for nil:NilClass (NoMethodError)
	from /usr/lib64/ruby/gems/2.1.0/gems/liquid-2.6.2/lib/liquid/block.rb:109:in `block in render_all'
	from /usr/lib64/ruby/gems/2.1.0/gems/liquid-2.6.2/lib/liquid/block.rb:96:in `each'
	from /usr/lib64/ruby/gems/2.1.0/gems/liquid-2.6.2/lib/liquid/block.rb:96:in `render_all'
	from /usr/lib64/ruby/gems/2.1.0/gems/liquid-2.6.2/lib/liquid/block.rb:82:in `render'
	from /usr/lib64/ruby/gems/2.1.0/gems/liquid-2.6.2/lib/liquid/template.rb:128:in `render'
	from /usr/lib64/ruby/gems/2.1.0/gems/liquid-2.6.2/lib/liquid/template.rb:138:in `render!'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/convertible.rb:106:in `render_liquid'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/convertible.rb:233:in `do_layout'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/post.rb:258:in `render'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/site.rb:298:in `block in render'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/site.rb:297:in `each'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/site.rb:297:in `render'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/site.rb:51:in `process'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/command.rb:28:in `process_site'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/commands/build.rb:56:in `build'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/commands/build.rb:34:in `process'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/lib/jekyll/commands/build.rb:18:in `block (2 levels) in init_with_program'
	from /usr/lib64/ruby/gems/2.1.0/gems/mercenary-0.3.5/lib/mercenary/command.rb:220:in `call'
	from /usr/lib64/ruby/gems/2.1.0/gems/mercenary-0.3.5/lib/mercenary/command.rb:220:in `block in execute'
	from /usr/lib64/ruby/gems/2.1.0/gems/mercenary-0.3.5/lib/mercenary/command.rb:220:in `each'
	from /usr/lib64/ruby/gems/2.1.0/gems/mercenary-0.3.5/lib/mercenary/command.rb:220:in `execute'
	from /usr/lib64/ruby/gems/2.1.0/gems/mercenary-0.3.5/lib/mercenary/program.rb:42:in `go'
	from /usr/lib64/ruby/gems/2.1.0/gems/mercenary-0.3.5/lib/mercenary.rb:19:in `program'
	from /usr/lib64/ruby/gems/2.1.0/gems/jekyll-2.5.3/bin/jekyll:20:in `<top (required)>'
	from /usr/bin/jekyll:9:in `load'
	from /usr/bin/jekyll:9:in `<main>'

You appear to be using a version of the plugin from before it was converted into a gem. I've looked through a few of the most recent commits and I couldn't find anything that would cause that stack trace. Could you try installing the gem and post an updated stack trace?

I just copied https://raw.githubusercontent.com/robwierzbowski/jekyll-picture-tag/master/lib/jekyll-picture-tag.rb to _plugins folder of my blog. Shall I install something else in addition to it?
I tried to switch to gems but everything stopped to work for me (not a problem with your plugin but something weird with Gentoo Jekyll setup).  Can I somehow put your code to my setup without using gems?

I had the same error and it was because of the indenting in the YAML. source_medium: should be indented to under ppi otherwise it's interpreted as a preset, not a property of the default preset (same goes for all the subsequent lines. It's a copy-paste thing.

Thank you!  It was my case also.
Working config:
picture:
  source: "_assets/imgs/_fullsize"
  output: "generated"
  markup: "picture"
  presets:
    default:
      ppi: [1, 1.5]
      source_medium:
        media: "(min-width: 40em)"
        width: "600"
        height: "300"
      source_default:
        width: "300"


Visible mark is not rendering correctly for tabs

When marking a region that includes tab characters, the reverse video highlighting falls behind the cursor by the length of the tabs. The video reversal highlighting is crosssing the 8 character distance as if it were spaces.

fixed

This is fixed in branch emsys2


Translations Portuguese and French

Hello Wiesty,
I am submitting my translations for Portuguese and French. The translations are good for both variations pt and pt-BR, as well as for both fr and fr-CA.
Thanks.
Julio

Thanks for helping out!


Handle emoji tooltip

Details

Display a tooltip when hovering over emoji in report action
Fixed Issues

$ https://github.com/Expensify/App/issues/34307
PROPOSAL: https://github.com/Expensify/App/issues/34307#issuecomment-1886072144
Tests

Send a message containing only emoji
Verify that the font size of emoji is big
Send a message containing only emoji and text, not contain any markdown
Verify that the font size of emoji is smaller
Send a message with emoji and any markdown
For the three cases above, hover over the emoji and verify that the emoji tooltip appears with the correct emoji and emoji name

[x] Verify that no errors appear in the JS console

Offline tests

Same as above
QA Steps

Send a message containing only emoji
Verify that the font size of emoji is big
Send a message containing only emoji and text, not contain any markdown
Verify that the font size of emoji is smaller
Send a message with emoji and any markdown
For three cases above, hover over the emoji and verify that the emoji tooltip appears with the correct emoji and emoji name

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome
https://github.com/Expensify/App/assets/129500732/64beafad-4485-416b-9168-9038c75e4782

iOS: Native

iOS: mWeb Safari
https://github.com/Expensify/App/assets/129500732/b17d2228-b1ce-4c78-bfaf-843da38901bd

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/129500732/04bb4f7f-472b-4d2f-a3fe-149413f07109

MacOS: Desktop
https://github.com/Expensify/App/assets/129500732/de46358f-3453-4ef8-a7d6-3abeb59dd92f

Hi!  Who is this waiting on, what are they doing, and when will it be done?

@fedirjh I think that we should do nothing with regards to emojis sent before this change. They just won't work for hover, but I think that is fine IMO, we should just start doing it moving forwards

I believe the backend changes have not been deployed yet?. The frontend is successfully sending the data, but the backend is returning stripped data.

I will look into this, the backend PR has been deployed to production so something else must be going on

Okay I have another backend PR up to stop stripping the tags. 2 other things that can be worked on in the mean time:

Composite emojis like 😶🌫 are actually made up of 3 different emojis as you can see in the first screenshot. This is causing a bug where we are adding the tags like this test<emoji>😶</emoji><emoji></emoji><emoji>🌫</emoji><emoji></emoji>. This also causes the hover to be incorrect.
Can we please change the mouse type to a regular pointer like slack does when hovering emojis?

@dukenv0307 now that the common pr is merged, are we good to go here?

Changes look good but there are conflicts :( Just a quick package change and we should be good to go!

🚀 Deployed to staging by https://github.com/stitesExpensify in version: 1.4.47-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
failure ❌

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/roryabraham in version: 1.4.47-10 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Dark Mode

I have added Dark Mode and Updated the README.

Hey @adi-075, Thank you for the PR!
The dark mode is already added to the app. Therefore, this PR will be close.


roslaunch kinect2_bridge kinect2_bridge.launch fails

I am trying to use my kinect in ros and I run
$ roscore
$ roslaunch kinect2_bridge kinect2_bridge.launch
I get the following error:
[ERROR] [1472742289.526802846]: Failed to load nodelet [/kinect2_bridge] of type [kinect2_bridge/kinect2_bridge_nodelet] even after refreshing the cache: Failed to load library /opt/ros/jade/lib//libkinect2_bridge_nodelet.so. Make sure that you are calling the PLUGINLIB_EXPORT_CLASS macro in the library code, and that names are consistent between this macro and your XML. Error string: Could not load library (Poco exception = libfreenect2.so.0.2: cannot open shared object file: No such file or directory)
[ERROR] [1472742289.526876189]: The error before refreshing the cache was: Failed to load library /opt/ros/jade/lib//libkinect2_bridge_nodelet.so. Make sure that you are calling the PLUGINLIB_EXPORT_CLASS macro in the library code, and that names are consistent between this macro and your XML. Error string: Could not load library (Poco exception = libfreenect2.so.0.2: cannot open shared object file: No such file or directory)
[FATAL] [1472742289.527077481]: Failed to load nodelet '/kinect2_bridgeof typekinect2_bridge/kinect2_bridge_nodeletto managerkinect2'
Protonect works...

needed to run ldconfig...


Added aarch64 & update go version

go mod tidy
go mod vendor

Work checked on Darwin aarch64

@qaoru ping

Please tag new release
Thanks!


Consider adding a section for Lifecycle Callbacks in the handbook

I found it really hard to figure out what lifecycle hooks were available in Stimulus until I read the Handbook cover to cover and found them buried in the section about 'Managing State'.
What do you think about pulling them out into a distinct section so they are easier to find?
Another option could be to publish some more concise docs that read less like a guide and simply outline the API that a Controller provides you.
Thanks for your consideration :)

Thanks for raising the issue. I agree that the table of lifecycle callbacks is difficult to find.
However, there’s only three callbacks to document. I don’t really think they merit their own chapter in the handbook.
We’re planning on adding full API documentation for the next release and I suspect lifecycle callback methods will be quite natural to explain in the Controller class.
Closing for now, but please feel free to open more documentation issues as you encounter them.

We’re planning on adding full API documentation for the next release and I suspect lifecycle callback methods will be quite natural to explain in the Controller class.

This would solve the problem perfectly. Thanks for letting me know!


RTL support (minor tweak)

Hey,
It seems to me like that all that's missing for full RTL support is switching .glyphicon-chevron-left inside of th.prev with .glyphicon-chevron-right and vice versa.
Could be controlled by a rtl: true option.
This is very important for me, any chance for an implementation?

couldn't you just change the icon option?
        icons: {
            next: 'glyphicon glyphicon-chevron-left',
            previous: 'glyphicon glyphicon-chevron-right',
        }

You're right, missed that one.
We're still better off with an official RTL option, since building an application that fully supports RTL requires controling every plugin the app uses seperately, and instead of hacking and tweaking each plugin we use, a LTR/RTL option (which is very common in other plugins) is much easier to control and way more elegant.
Also, sepecifically for this plugin, it only makes sense. Since as I said, as far as I can tell the only thing missing from officially adding the "RTL support" title to this plugin, is this tiny tweak. In the future, if other tweaks are needed, they can all be added under the hood, for the RTL option.
Thanks a lot.


DOC: link to pkgs.org/download/netperf

A link to https://pkgs.org/download/netperf (which links to 3rd party packages for many operating systems) would be useful; in lieu of just uploading packages to the releases section of this gh project.
As would this for building from source:
dnf install -y texinfo  # (are there additional packages that i already have installed?)
./autogen.sh
./configure --enable-demo --prefix=/usr/local
make
make install

https://flent.org/intro.html#quick-start specifies --enable-demo


UWP1.1 compatibility

As of the latest revision of the Template10 library, it is fully compatible with UWP1.1 (SDK build 10586). To that end, this pull request makes build 10586 the targeted SDK version. 10240 is still supported as the minimum.

Why is this neccessary? Will it break anything on existing applications that still require 10240 SDK?

Hey guys, let's release 1.0.9. We will branch it to preserve the 10240 support side of things, and then we will introduce version 1.10586.1. This is not a technical decision, please understand, this is a simplification decision for us and for developers trying to use T10.

OK. I'll keep working on compatibility with UWP1.1, and I'll submit a pull request post-1.0.9. Although, shouldn't the first UWP1.1 release be 1.10586.0?


Main Show One Nutrition Table

Be able to do the following when running a start.sh file from the host virtual machine:

Build the static web files and host them in a static web server.
Host a postgresql database in a docker container and route requests on the database from the static web server.

We need to do the following:

[ ] Be able to run bash ./start.sh from the root of the project and have all docker containers running properly.

We need to install the latest docker to be able to mount multiple volumes to a single container I think:

[ ] https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository

The next thing we need to do is:

[ ] Upload a csv file to the browser.
[ ] Create a SQL query from the csv file to create the empty table.
[ ] Create a set of SQL queries to populate the table.
[ ] Create a Postgresql database container and wire it through the api we have.

[ ] Use docker compose in this project to start the containers?

[ ] Use the sqlalchemy python project to create the tables in the database.
[ ] Use the sqlalchemy python project to fill the tables with records.
[ ] The sqlalchemy python project should be built using twig and exposed as a command line interface.
[ ] The database creation application should be configured using an application json file and run using the start.sh script!

[ ] How to run a file reader in a web worker!

[ ] Create the CREATE TABLE filename without suffix ( column_1, column_2, ... );
[ ] Create the DROP TABLE filename without suffix IF EXISTS;
[ ] Create the INSERT ... queries as an array of batched queries to be run in parallel?

[ ] Enhance the worker.js file to support running the wasm code in the worker thread!

[ ] Write an application definition for the whole nutrition app.
[ ] Ensure the CREATE statement is sent to the node that will query against the database.  I think this one should be written in rust?

Add a unit test for the create_sql_schema_from_csv function.  Consider making a test configuration file option for app creators to configure automated test sequences that should run for their application!

[ ] Update the create_sql_schema_from_csv rust function to output a create statement with full column data types like the following:

CREATE TABLE films (
    code        char(5) CONSTRAINT firstkey PRIMARY KEY,
    title       varchar(40) NOT NULL,
    did         integer NOT NULL,
    date_prod   date,
    kind        varchar(10),
    len         interval hour to minute
);

CREATE TABLE distributors (
     did    integer PRIMARY KEY GENERATED BY DEFAULT AS IDENTITY,
     name   varchar(40) NOT NULL CHECK (name <> '')
);

[ ] Create small insert chunks and send them to the database in that fashion.


[Auth] Mutations should be written to server using token of initiating user

Currently this is done in the background worker by the currently logged in user.

(to persist associations between users and mutations)

@gino-m any clarification around this? We currently write and use the user that authored the mutation, but it's not clear to me yet if/where we check that this user has permissions to mutate the target object

@gino-m any clarification around this? We currently write and use the user that authored the mutation, but it's not clear to me yet if/where we check that this user has permissions to mutate the target object

Unless something changed, it's the token of the currently authenticated user that is used to do server writes. Even if the current user changes and still has write permission, it's obviously incorrect to write using a different principal than the one taking the action. That said, storing and refreshing per-user tokens is likely out of scope of our first release.
Perhaps for now we can instead show a Big Scary Warning when users sign out and delete any pending mutations in the local db?

Got it, that sgtm! Going to bump this down in priority for now and open a separate issue.

Mutations are now removed when the user signs out, so there's no risk of the wrong user performing sync.


Something went wrong, please try running the script again

Cool project!
Unfortunately, get this error message all the time
PS C:\> "owershell is is fun" | Invoke-SpellCheck -ShowErrors
Something went wrong, please try running the script again

There are a couple of things I want to mention

This error is not actionable. I tried run it few times. What's next? I cannot google it. I tried use -Verbose option. Are my keys not good? Is service down? Bug in the module? What should I do?
To make it actionable error message needs more details. Maybe more output with -Verbose to understand the context.
This is especially discouraging, when you encounter it on the very first try (like me).

I've created PR to fix this (hopefully)

There was a wrong reference to API URL for Invoke-SpellCheck Function , which was Identified by @4c74356b41 , also I've added some code to add verbosity while handling error making error more actionable now.
Downlaod the updated module from - Https://github.com/PrateekKumarSingh/ProjectOxford/blob/master/ProjectOxford.psm1


add unit tests

each component should have thorough unit tests
components currently written that still need tests:

[ ] <AudioContext>
[ ] <Modulation>
[ ] <Oscillator>
[ ] <Output>

might make sense to hold off on these all until full basic functionality is established


MSTest.TestAdapter does not get nuget-restored if the target framework is .NETStandard2.0

Description
MSTest.TestAdapter does not get nuget-restored if the target framework is .NETStandard2.0
Steps to reproduce

Install Visual Studio 15.5.0 Preview 2
Create a new project using File | New Project | Visual C# | .NET Standard | Class Library (.NET Standard)
Add a NuGet Reference to the project to MSTest.TestFramework (v1.2.0)
Add a NuGet Reference to the project to MSTest.TestAdapter (v1.2.0)
Build the project

Expected behavior
No warning. The MSTest packages should get NuGet-restored as expected.
Actual behavior
warning NU1701: Package 'MSTest.TestAdapter 1.2.0' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETStandard,Version=v2.0'. This package may not be fully compatible with your project.

It is not possible to author a test project targeting NETStandard. It must target a app runtime (net46, netcoreappX.Y etc.).

Why does the warning show up only for the TestAdapter package (and not for the TestFramework package)?

MSTest.TestFramework lists following as supported targets:

net45
netstandard1.0
uap10.0

The netstandard1.0 target is used for netcoreapp1.0 test projects and it can be used for netstandard1.x projects too.
The test adapter on the other hand lists support for following:

net45
netcoreapp1.0
uap10.0

OK, closing this issue.

@pvlakshm  Could we reopen this issue? I have a use-case for using the TestAdapter as .NET Standard, when executing tests on Xamarin.
I've created my own port of MSTest.TestAdapter (https://www.nuget.org/packages/MSTestX.TestAdapter/) for this purpose, but would prefer just referencing the official package rather than forking and having to attempt to keep in-sync (it compiles as is, so very little effort on your part).

It is not possible to author a test project targeting NETStandard. It must target a app runtime (net46, netcoreappX.Y etc.).

This makes no sense to me. That restriction applies to executables, but not class libraries.

I'm blocked by this one as well in the context of WebAssembly tests. netstandard2.0 is the only possible target at the time for this kind of environment.

You need a runtime to run tests on, and Netstd isn't a runtime, so I don't see how that could ever work.

I'm blocked. Unit tests are supposed to test my ClassLibraries. All the libraries are targeting .NETStandard 2.0. Then why should a Unit test target anything else?
Voting for REOPEN

@ionsphere You need a runtime to run your tests on. Do you want to run your tests on .NET Framework, .NET Core, Mono, UWP .NET Core, or... and which version of any of those?
There's not such thing as a .NET Standard app, and thus there are no such thing as a .NET Standard Unit Test. You have to the very least reference your class library from a runtime-specific project and execute it in that context.

If I have a library that I want to make sure runs on any NET Standard, why shouldn’t it be possible? Isn’t the point of having a regency in VisualStudio stating “NETStandardLibrary 2.0” means all applicable references of that library set? And if so, how testing on NET Core 2.2 proves that the library can run on any NET Standard? There is quite a chance that it may end up requiring NET Framework 4.7.2 with this kind flaky testing.

A unit test is not only checking the internal stability, but also the surface of exposed components. How can I be sure that someone’s library while using mine can be NET Standard? How can I verify that all the interfaces and objects in my requirements are implemented under all NET Standard implementations. (Notice, there are interfaces that have no implementing classes under NET Standard and a unit test should hint and help avoiding it)
Are you suggesting that with NET Standard I’m forced to have multitude of Unit Test projects each referencing different runtimes, while NET Standard should be a guaranteed testable subset of those runtimes? You know, that NET Core > NET Standard, that NET Framework > NET Standard and that (NET Core ∩ NET Framework) != NET Standard.

And I get the point of confusion. Unit Test project should target NETStandard because I want the code to compile under strict limitations of NETStandard. But Unit Test project should run in some runtime compatible with that Standard. As VisualStudio doesn’t seem to have this distinction, then it should be possible to have NETStandard Unit Test and let vstest or dotnet-test pick any installed one with minimal compatibility.

As part of CPS change, we are trying to consolidate the adapter and framework nuget packages. We will try  if this too can be fixed as part of that.

Any progress?
I have .net core 3 web app which has all of its libraries in .net standard 2.1. I really need to be able to test at .net standard 2.1.
Is there a workaround for this?

Same here, two years later. Any change to get it fixed? Any known workarounds?

I to have the same problem. I have a .NET Standard Assembly that I want to write Unit Tests against. Why cant i?

The fact this know bug is open for 2+ years and kept without movement is quite frustrating.

I am having similar issue where MSTest.TestAdapter loses reference after I create an executable from C# project and so when I run dot exe I get error . The VM where I am running this does not have VS and code base. Requirement is that Exe should include everything .
When I run on local , tests run fine , directly through VS or through dot exe
No test is available in C:\Users\..\Desktop\MyExeName.exe. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.
I am running exe through VSTest.console on this VM
How can I make sure that MSTest tests are discovered through dot exe ?

I got stuck for a while on this, is .net standard is not supported for test libraries then can we get a better error message that states as such?

@redwyre for what it's worth I just updated my test adapter with the latest 2.1.0 code base, if you need it: https://www.nuget.org/packages/MSTestX.TestAdapter/
While I mainly make it to be used with the unit test runner, it should work for anything (just note that it can't do deployment)

@MrHinsh

I have a .NET Standard Assembly that I want to write Unit Tests against. Why cant i?

Of course you can. But your unit test project MUST target a framework. Nothing can run as ".NET Standard". That's merely an API contract, not an actual runtime. You'll have to decide to execute the tests on top of .NET Framework, .NET Core or Mono etc. (or all of the above - MSTest does support multi targeting just fine!)
My port to .NET Standard was mainly done so I could run the executor and communications classes on Android and iOS (and thus vstest.console is actually able to talk to my test runner app as the same communication classes are used). But I still have to run the tests themselves in the context of a runtime, in this case the Mono-Xamarin runtime.

As for my comment above , I was able to ran my test.  The issue actually was that  I needed to provide  MSTest.TestAdapter  package dll through below mentioned config in .runsettings file .  I was running test using vstest.console and I used /Settings:[file name]  option on command line
Here is the config I used
<MSTest>
.....
<AssemblyResolution>
      <Directory path="D:\myfolder\bin\" includeSubDirectories="false"/>
    </AssemblyResolution>
...
<MSTest>

But your unit test project MUST target a framework. Nothing can run as ".NET Standard".

Hmm, no. It's not how it works. Test project produces merely a DLL. VSTest.Console.exe is the EXE that runs that DLL. Isn't it?

yes. I was targeting framework 4.7.2  and was using vstest.console to run my exe and and provided above mentioned config.

VSTest.Console.exe is the EXE that runs that DLL. Isn't it?
Well yes and no. It might start a separate process and run it (a good example is UWP which runs completely isolated in a window). The console then just connects via a socket to control and monitor the test run

@dotMorten I think I am still missing the point here. If my test project is netstandard, who will execute the tests? 🙂 I actually tried to move the mstest to netstandard earlier this month, but to do it properly I would need to move the ObjectModel to netstandard1.0 as well (or stick with the very old version it is using now).
Are the changes in your repo preventing some of our other scenarios from running? If not please PR so we can possibly get it merged.
(I am on twitter as @nohwnd and I would love to discuss this with you a bit further, my DMs are open. I have whole two-pager rant about the reasoning around why the projects are currently netcoreapp, and when it might be beneficial to have the project as netstandard, but I don't want to pollute the issue here with it, and because my partial understanding would be a source of confusion here).

@nohwnd perhaps I should put it a different way: I really don't need .net standard support. What I need is xamarin.android and xamarin.ios and Tizen support. But then I might as well just use .net standard library. I'll then be referencing mstest in my Xamarin app and use it to do all the test execution, aborts, timeouts, socket communication etc.

Any updated on this, please? I drags on, and on, and on.

Warning NU1701: Package 'MSTest.TestAdapter 2.1.2' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the project target framework '.NETStandard,Version=v2.1'. This package may not be fully compatible with your project.

We added NETStandard2.0 support into the Test Platform. The next step is to add it to TestFX in upcoming previews of Visual Studio 16.9.

This will be handled through #1095

Fixed by #1194


Updates deprecated iceServer preparation.

In more recent versions of FF (>= 38) we're getting a deprecation
warning:

RTCIceServer.url is deprecated! Use urls instead

This PR changes the iceServer preparation in 2 ways:

the property of a iceServer member is now urls not url.

There was already a comment hinting to this change:

Change 'url' to 'urls' whenever this issue is solved:
https://code.google.com/p/webrtc/issues/detail?id=2096
(The mentioned issue has been resolved.)

the turn server urls are no longer flattened and instead
passed on as an array.
(http://w3c.github.io/webrtc-pc/#idl-def-RTCIceServer)

Since there are 2 places (UA and MediaHandler) where the stun
and turn server options/configurations are modified
I wasn't 100% sure if this is the right place.
I've also added some specs. If you have any questions or suggestions,
I'm more than happy to address them.
Cheers

Hi @wpp,
This PR looks good to me. Since it looks like it's been about 6 months since that bug's patch was introduced into Chrome (if milestone 44 is accurate) and has been in Firefox longer than that, I have no issues merging this. I'll ask the other authors to review before merging. Let's give it until the end of the week.
Thanks,
James

Thanks for following up on this, @wpp, it looks great!


Add sparse pointwise equality & inequality functions

Closes https://github.com/cupy/cupy/issues/3831.

The implementation of the feature is done for now, so could you review this PR when you have time?

pfnCI, test this please

Jenkins CI test (for commit f9d48c7b75757bb34538847283cc6f3ea2ce3041, target branch master) succeeded!

Jenkins, test this please.

Jenkins CI test (for commit d517aee5d3c79bdb6f3e6b0639936c99cb415637, target branch master) succeeded!

LGTM!


Quarkiverse is ignoring zone-id

Hi I tried the default quarkus json logger with: quarkus.log.console.json.zone-id=UTC and it works. When I enable quarkiverse it seems that the zone-id is ignore.
Looking at the configs: https://github.com/quarkiverse/quarkiverse-logging-json/blob/master/runtime/src/main/java/io/quarkiverse/loggingjson/Config.java
It seems missing or is it supposed to inherit it?

That is not implemented yet, I will add it to the list of requested features.

@javadevmtl I have just released 0.1.7, with support for zone id.
Config to use for UTC:
quarkus.log.console.json.fields.timestamp.zone-id="UTC"


cesium concierge has gone quite

@ggetz are you looking into this?

@ggetz, it appears something may have changed on the GitHub API side of things, the log is full of errors.  Either that or the server just needs a reboot because of the AWS outages earlier.  Let me know if you need help debugging tomorrow, but I assume we want this fixed ASAP (CC @pjcozzi).
    at tryOnImmediate (timers.js:645:5)
    at processImmediate [as _immediateCallback] (timers.js:617:5)
Unhandled rejection SyntaxError: Unexpected token a in JSON at position 14966
    at Object.parse (native)
    at /var/app/lib/commentOnOpenedPullRequest.js:113:28
    at tryCatcher (/var/app/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/var/app/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/var/app/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/var/app/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/var/app/node_modules/bluebird/js/release/promise.js:693:18)
    at Async._drainQueue (/var/app/node_modules/bluebird/js/release/async.js:133:16)
    at Async._drainQueues (/var/app/node_modules/bluebird/js/release/async.js:143:10)
    at Immediate.Async.drainQueues (/var/app/node_modules/bluebird/js/release/async.js:17:14)
    at runCallback (timers.js:672:20)
    at tryOnImmediate (timers.js:645:5)
    at processImmediate [as _immediateCallback] (timers.js:617:5)
SyntaxError: Unexpected token a in JSON at position 14966
    at Object.parse (native)
    at /var/app/lib/commentOnOpenedPullRequest.js:113:28
    at tryCatcher (/var/app/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/var/app/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/var/app/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/var/app/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/var/app/node_modules/bluebird/js/release/promise.js:693:18)
    at Async._drainQueue (/var/app/node_modules/bluebird/js/release/async.js:133:16)
    at Async._drainQueues (/var/app/node_modules/bluebird/js/release/async.js:143:10)
    at Immediate.Async.drainQueues (/var/app/node_modules/bluebird/js/release/async.js:17:14)
    at runCallback (timers.js:672:20)
    at tryOnImmediate (timers.js:645:5)
    at processImmediate [as _immediateCallback] (timers.js:617:5)

Sooner is better, but let's discuss if the scope is somehow large.

I'll take a look and see what all is needed, hopefully it's just the outages. Ran a quick test yesterday and it was still successfully commenting on closed issues.

It looks like an error parsing CLA.json due to a typo, I'll add some error checking so this doesn't happen in the future.

I think the error checking should happen in CI, just like glTF, 3D Tiles, etc.

We can check in both places, but I agree with @ggetz in that cesium-concierge should definitely have an error check as well, so that the actual problem is obviously logged if it gets bad data as opposed to the obtuse callstack we had.

OK, I guess it is also good if others are using concierge without our CI.
Just keep it quick and simple please.


SVG gradients

As I understand there's still no support for parsing SVG gradients, right?
This would be the expected result.

<svg width="109" height="109" viewBox="0 0 109 109" fill="none" xmlns="http://www.w3.org/2000/svg"> <circle cx="54.5" cy="54.5" r="54.5" fill="url(#paint0_linear)"/> <defs> <linearGradient id="paint0_linear" x1="54.5" y1="0" x2="54.5" y2="109" gradientUnits="userSpaceOnUse"> <stop stop-color="#F01A1A"/> <stop offset="1" stop-color="#C4C4C4" stop-opacity="0"/> </linearGradient> </defs> </svg>

@mixmastertube can you try to use the master branch? Fix for gradients not in release yet.

This sample works fine in the master branch, closing this issue.

How did you do it?
I did try and still not working, I still don't get any gradient.
My steps:
Step 1
Cloning the project to local (master branch selected)
Step 2
Editing the Podfile inside the Example folder to
pod 'Macaw', :git => 'https://github.com/exyte/Macaw.git', :branch => 'master'
just to be sure it's pointing to master branch.
Step 3
I change the svg inside the Assets folder tiger.svg to my svg, just to do a quick test.


It works within redux?

How I can import data from local-mongodb to my app using redux? Redux loads state in the first time,then it loads componentDidMount. Where I can use function to load data from local db?

You can read the data from AsyncStorage. Please, note this: https://github.com/antoniopresto/react-native-local-mongodb#persistence


Android Studio All Project Error

Build was configured to prefer settings repositories over project repositories but repository 'Google' was added by build file 'build.gradle'

I think your build is configured to only allow repositories to be declared in settings and something is adding a repository to your project's build script:
https://docs.gradle.org/current/userguide/declaring_repositories.html#sub:centralized-repository-declaration


Update event-44-rds-licensing-server.md

Removed Windows Server 2012 as it is in EOS and added 2019 and 2022 as the customer required the change.
Pull request guidance
Thank you for submitting your contribution to our support content! Our team works closely with subject matter experts in CSS and PMs in the product group to review all content requests to ensure technical accuracy and the best customer experience. This process can sometimes take one or more days, so we greatly appreciate your patience.
We also need your help in order to process your request as soon as possible:

We won't act on your pull request (PR) until you type "#sign-off" in a new comment in your pull request (PR) to indicate that your changes are complete.

After you sign off in your PR, the article will be tech reviewed by the PM or SME if it has more than minor changes. Once the article is approved, it will undergo a final editing pass before being merged.

#sign-off

The changes are live. Please close this PR.

Changes confirmed. Thank you for your review!


Cannot read property 'IO' of undefined

I am getting the following error when trying creating from boot script  a record in a json model which contains an array of string property .
my model is like :
The variants field is generating the problem :
"properties": {
"name": {
"type": "string",
"required": true
},
"variants": {
"type": [
"string"
],
"required": true
}
brandname = "test";
variant = ["1 item","2 Items", "3 Items"];
myModel.create([
{
name: brandName,
variants : variants
}
It seems that array of string property is not supported ???
error  :
var retval = fn(context, next);
TypeError: Cannot read property 'IO' of undefined
....\loopback-component-realtime\dist\mixins\fire-loop.js:32:25
When i change in mixins fireloop to false, it works ???

@MROALI hello and thanks for reaching out,
Hey so... for me it seems that you have an asynchronous issue. If you need that you model is able to create Real-Time connections, then you need to keep the FireLoop mixing as true, but also within your boot script, you will need to wait until fireloop is ready.
module.exports = function(app) {
   app.on('fire-connection-started', () => {
     // do your things in here.
   })
}

I hope this helps you clarify your problem
Cheers
Jon

@jonathan-casarrubias Hello, you have reason its is an asynchronous issues.
Thanks for your answer.
It works now :)  :+1:


jib-maven-plugin fails if maven-war-plugin "warName" property references maven property created by properties-maven-plugin

Environment:

Jib version: 2.4.0
Build tool: Maven 3.6.0
OS: Ubuntu (WSL)

Description of the issue:
This issue further extends #2206. I.e. using the <warName> property of the maven-war-plugin works as expected in combination with the jib-maven-plugin. Even using a maven property for the <warName> works fine, as long as the maven property is defined somewhere in the pom itself.
In our build however, we are using the plugin org.kuali.maven.plugins:properties-maven-plugin:2.0.1 to be able to define certain properties that are used throughout the project in one place. This is where the jib-maven-plugin starts to complain about not being able to find the .war file. The error message reads as follows:
[ERROR] Failed to execute goal com.google.cloud.tools:jib-maven-plugin:2.4.0:build (default) on project helloworld.ui.html.app.war: Obtaining project build output files failed; make sure you have compiled your project before trying to build the image. (Did you accidentally run "mvn clean jib:build" instead of "mvn clean compile jib:build"?): /path/to/src/jib-test-repository/helloworld.ui.html.app.war/target/${ui.html.war.name}.war -> [Help 1]
It seems to me as if the <warName> property was read and all properties it contains were resolved against the maven properties that are defined at that time. The properties-maven-plugin seems to inject its properties later which causes them to not be taken into account by the jib-maven-plugin.
Expected behavior:
Building a war module with the jib-maven-plugin should work, even if the <warName> property of the maven-war-plugin contains a maven property that is defined by the properties-maven-plugin.
Steps to reproduce:
I updated the code from the #2206 issue to demonstrate this problem: https://github.com/michaelze/jib-test-repository
Working configuration (initial repository

Alter the pom.xml File in helloworld.ui.html.app.war and change the target image to a location you can push to.
Execute the build as follows: mvn -Djib.to.auth.username=xxxxx -Djib.to.auth.password=xxxxx -DskipTests -P docker clean package (Success)

Error when using property defined by properties-maven-plugin for <warName>

Change the configuration of the maven-war-plugin in the helloworld.ui.html.app.war/pom.xml (comment out the <warName> property with the literal value and remove the comments from the <warName> property containing the maven property reference
Execute build like mentioned above

jib-maven-plugin Configuration:
<!-- from parent module (build / pluginManagement -->
<plugin>
	<groupId>com.google.cloud.tools</groupId>
	<artifactId>jib-maven-plugin</artifactId>
	<version>2.4.0</version>
	<executions>
		<execution>
			<phase>package</phase>
			<goals>
				<goal>build</goal>
			</goals>
		</execution>
	</executions>
</plugin>

<!-- from module configuration -->
<plugin>
	<groupId>com.google.cloud.tools</groupId>
	<artifactId>jib-maven-plugin</artifactId>
	<configuration>
		<from>
			<image>tomcat:9-jdk11</image>
		</from>
		<to>
			<image>changeme/testimage</image>
		</to>
	</configuration>
</plugin>

Thanks for the detailed info and the sample project. I think I understand what's going on, but I don't find a good way to make this work.
properties-maven-plugin has certain inherent limitations due to the fact that it runs as an additional plugin during Maven execution, which means that the property injection happens far after Maven has already parsed pom.xml and completed certain evaluation steps. For example, you can't use the plugin to substitute a dependency version. The SO answer goes into explaining at high level some stages Maven goes through (whose details I honestly don't fully understand), but the point is that it's inevitable that properties-maven-plugin has certain limitations.
In your case, if I check the effective POMs, I see that <warName> remains untouched.
$ mvn -DskipTests -pl helloworld.ui.html.app.war -am package help:effective-pom | grep war\.name
      <ui.html.war.name>uihtml</ui.html.war.name>
      <ui.html.war.name>uihtml</ui.html.war.name>
      <ui.html.war.name>uihtml</ui.html.war.name>
      <ui.html.war.name>uihtml</ui.html.war.name>
      <ui.html.war.name>uihtml</ui.html.war.name>
              <warName>${ui.html.war.name}</warName>
                <warName>${ui.html.war.name}</warName>
            <warName>${ui.html.war.name}</warName>

OTOH, if you pass the corresponding system variable on the command line, or directly set the property inside the project pom.xml (as you tried), then I see the effective POM already substituted the given value for <warName>.
$ mvn -DskipTests -Dui.html.war.name=cool.war.name -pl helloworld.ui.html.app.war -am package help:effective-pom | grep war\.name
[INFO] Building war: /home/chanseok/tmp/gitrepos/jib-test-repository/helloworld.ui.html.app.war/target/cool.war.name.war
      <ui.html.war.name>uihtml</ui.html.war.name>
      <ui.html.war.name>uihtml</ui.html.war.name>
      <ui.html.war.name>uihtml</ui.html.war.name>
      <ui.html.war.name>uihtml</ui.html.war.name>
      <ui.html.war.name>uihtml</ui.html.war.name>
              <warName>cool.war.name</warName>
                <warName>cool.war.name</warName>
            <warName>cool.war.name</warName>

$ mvn -DskipTests -pl helloworld.ui.html.app.war -am package help:effective-pom | grep war\.name
[INFO] Building war: /home/chanseok/tmp/gitrepos/jib-test-repository/helloworld.ui.html.app.war/target/inlined.war.name.in.pom.xml.war
      <ui.html.war.name>uihtml</ui.html.war.name>
      <ui.html.war.name>uihtml</ui.html.war.name>
      <ui.html.war.name>uihtml</ui.html.war.name>
      <ui.html.war.name>uihtml</ui.html.war.name>
      <ui.html.war.name>uihtml</ui.html.war.name>
              <warName>inlined.war.name.in.pom.xml</warName>
                <warName>inlined.war.name.in.pom.xml</warName>
            <warName>inlined.war.name.in.pom.xml</warName>

The problem is that, in Maven, the only way I am aware of for one Maven plugin (jib-maven-plugin) to read a config value of another plugin (maven-war-plugin) is through the final effective POM model that Maven evaluated. Maven is probably instantiating plugin configuration instances while factoring in session properties, so I guess that's the reason why each plugin fortunately gets the substituted values in their config MOJO. However, for one plugin to consult a config value of another plugin, AFAIK, the final POM model is the only medium, and the model just contains the placeholder values.
Unless there's another way that I'm unaware of to get the evaluated values of another plugin, I think this is somewhat tricky to make it work. Theoretically Jib could implement an independent evaluation logic to resolve ${..} expressions in a string value using the Maven session/system properties, but I don't really feel this is what Jib should do.

@chanseokoh
Thank you for your analysis, from the behavior I was seeing, I kinda expected something along those lines.
What I don't get though is why the maven-war-plugin works with the property set by the properties-maven-plugin (i.e. why the created .war file has the name I defined in my .properties file).
I looked at the code of the maven-war-plugin (https://github.com/apache/maven-war-plugin/blob/master/src/main/java/org/apache/maven/plugins/war/WarMojo.java) to maybe find a "standard" way to also implement the same behavior in the jib-maven-plugin but I could not find any custom/non-custom code to "parse a string and replace property references from the maven session". Somehow, Maven seems to set the warName property already parsed and replaced as soon as the WarMojo is constructed/initialized.
There's also a difference in those two cases:

maven-war-plugin: the ${property} reference in the <warName> property of the war plugin's configuration seems to be parsed and replaced soon enough for the plugins execution to be correct
jib-maven-plugin: it is not some value of the plugins' configuration itself that needs to be parsed and replaced but the value of another plugins configuration value. In your implementation, you are reading the value from the parsed Dom whereas actually you are interested in the value the plugin is using at runtime.

So maybe it would be possible to not parse the value from the war plugin's Dom but to get the value from its Mojo at runtime?
I agree with you, that implementing the parsing of the warName string and doing a replacement using properties from the maven session is not something one would expect the jib-maven-plugin to do, although, I was wondering if there might be a standard way of accomplishing this (a quick google search did not support this assumption, though).

What I don't get though is why the maven-war-plugin works with the property set by the properties-maven-plugin (i.e. why the created.

No wonder. Not just maven-war-plugin, but jib-maven-plugin also works with properties-maven-plugin for its <configuration> values. (For example, <configuration><to><image>.) Hence the following guess in my previous comment:

Maven is probably instantiating plugin configuration instances while factoring in session properties, so I guess that's the reason why each plugin fortunately gets the substituted values in their config MOJO.

Therefore, the problem is only when one plugin needs to read a configuration of another plugin in Maven. The last time (a few months ago) I tried to google for the best and ideal way to achieve this goal, all I was able to find on Stack Overflow answers was to read the other plugin's effective project object model (POM), which is what Jib is doing. And last Friday, I happened to have a chance to look into native-image-maven-plugin for a work unrelated to this and found that it also reads configuration values from other plugins in the same way. Take a look at their code: this and this.
So probably it's also what Oracle folks thought the only way. Therefore, if you were to use native-image-maven-plugin with properties-maven-plugin, you would run into the same problem. Unfortunately, there does not seem a way in Maven for one plugin to retrieve at runtime an actual MOJO instance of another plugin instantiated by Maven. This isn't a Jib-specific issue, it seems. There are some inherent limitations in using properties-mave-plugin, and I think this is the price you should take into account when deciding to use properties-maven-plugin. Maybe it might be simpler to use text-processing tools (such as sed or awk) to replace strings in pom.xml to attain your ultimate goal of keeping some values in a file.

I see (there's really not much further to say 😉
Thank you again for your thorough investigation and explanation, it's "close as won't fix" then, I guess?

You're welcome. Yeah, unfortunately, I cannot really think of a good solution. If you happen to come with any idea in the future, let us know anytime. Thanks!


Batch statement results return Forbidden

In the batch processing API, there are at least 4 places in the code where batch.userId is being compared using  !== to user.id.  user.id is an integer, and batch.userId is a string, so 'Forbidden' is always returned.
I hacked in a parseInt on batch.userId, and my API calls are now working.  I'm not sure that's the correct answer, though, so I haven't created a pull request.

Hi @jden98, userId is stored as a string in the backing database (SQLite, Postgres, MySQL, Mariadb, or SQL Server depending on setup)
If using the REST API, try sending your userId as a string like { userId: '123' }.
If this doesn't work let me know...

Hi @jden98, userId is stored as a string in the backing database (SQLite, Postgres, MySQL, Mariadb, or SQL Server depending on setup)
If using the REST API, try sending your userId as a string like { userId: '123' }.
If this doesn't work let me know...

Hi @rickbergfalk , I got the same issue Now.
Actually your advise doesn't work in my case. just like the following code block in the bataches.js under server/routes folder which is called when /api/batches/<batchId> is called.
async function batchToReq(req, res, next) {
  try {
    const { models, user, params } = req;
    const batch = await models.batches.findOneById(params.batchId);

    if (!batch) {
      return res.utils.notFound();
    }

    if (batch.userId !== user.id) {
      return res.utils.forbidden();
    }

    req.batch = batch;
    return next();
  } catch (error) {
    return next(error);
  }
}

the userId property of batch.userId is read from backend database who's type is varchar, while the id of user.id is the id property of serviceToken object read from database too under the PassportJwtStrategy, but who's type is integer.


FIX Recommendations

Description
FIX Recommendations issue where recommendation were removed after adding to shelf
Fixes #173
Type of Change
Please delete options that are not relevant.

[X] Bug Fix

Change Status

[X] Complete, tested, ready to review and merge

How Has This Been Tested?

[X] Locally tested
[X] Test suite has been ran, and provides the same result as prior to changes

Checklist

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] My code has been reviewed by at least one peer
[X] My changes generate no new warnings
[X] New and existing unit tests pass locally with my changes
[X] There are no merge conflicts

 Recommendations Bug


Adding entry.content with bytesOffset and blockOffet

When a new entry is added to an archive, the content field of the entry message is populated with that entry's bytesOffset and blockOffset -- just pulled from the the hypercore on insertion.
Added a few tests for archives containing one and two files in test/misc.js.

nice


Config reloading for custom DNS records

This would allow using grimd with templating with Nomad for service discovery, using something like described here except we do not need to restart the DNS server every time, we could just send a signal and update the handlers

Fixed in 2.2.0


Select with a transform may break when refetchInterval is set to a function

#5310
This may affect more than just refetchInterval, it appears to be from usage of a data variable alongside select changing the type of that variable

as we found out, this is a TypeScript limitation


Ignore unknown fields in protobuf parsing

closes #131

Tested and now it works! Thanks @lukasIO

@ThisAccountHasBeenSuspended thanks for the report and for confirming the fix works!


support for solidity Custom Errors

It seems that ethcontract-rs doesn't support solidity Custom Errors yet. That would be a great feature addition

This is great suggestion. Unfortunately, we don't really have the capacity to do this ATM, but PRs are welcome 😄

Latest ethabi https://github.com/rust-ethereum/ethabi/commit/afae7c79248ccf87fd81b2d7831f3f0aea451d51 supports this FYI


Define PLATFORM and PLATFORM_NUMBER based on the minimum Android SDK Version.

It's #1826 but i changed the branch to 8.3.0-Dev branch.

@Dimensionscape is it good to go now?