LoadBalancer unreachable outside of cluster

greetings,
My setup is as-is:
On <IP_ADDRESS>/24 network, I got an ubuntu 21.10 host
6: net100: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 6e:43:9d:8e:6b:c2 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global net100
       valid_lft forever preferred_lft forever
    inet6 fe80::6c43:9dff:fe8e:6bc2/64 scope link
       valid_lft forever preferred_lft forever

This host runs 4 VMs:
 Id   Name           State
------------------------------
 11   eck-worker01   running
 12   eck-worker02   running
 13   eck-worker03   running
 14   eck-master     running

All VMs are using bridged interface to net100, in order to be accessible from <IP_ADDRESS>/24 without routing/NATing.
eck-master uses <IP_ADDRESS>
eck-worker01 uses <IP_ADDRESS>
eck-worker02 uses <IP_ADDRESS>
eck-worker03 uses <IP_ADDRESS>

I have enabled dns, storage and metallb modules, from a 1.23.5 release (running with ubuntu 21.10)
metallb range is from <IP_ADDRESS> to <IP_ADDRESS>
](Within the cluster, everything seems fine:
root@eck-master:~# curl https://<IP_ADDRESS>/app/home#/ --insecure

<title>404 Not Found</title>

404 Not Found

nginx

Outside of it, there is no route to host.
root@host~# curl https://<IP_ADDRESS>/app/home#/ --insecure
curl: (7) Failed to connect to <IP_ADDRESS> port 443: No route to host

From the host itself, handling the VMs:
IPTables are, on host:
root@host:~# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
LIBVIRT_INP  all  --  anywhere             anywhere

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
LIBVIRT_FWX  all  --  anywhere             anywhere
LIBVIRT_FWI  all  --  anywhere             anywhere
LIBVIRT_FWO  all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
LIBVIRT_OUT  all  --  anywhere             anywhere

Chain LIBVIRT_FWI (1 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             <IP_ADDRESS>/24     ctstate RELATED,ESTABLISHED
REJECT     all  --  anywhere             anywhere             reject-with icmp-port-unreachable

Chain LIBVIRT_FWO (1 references)
target     prot opt source               destination
ACCEPT     all  --  <IP_ADDRESS>/24     anywhere
REJECT     all  --  anywhere             anywhere             reject-with icmp-port-unreachable

Chain LIBVIRT_FWX (1 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere

Chain LIBVIRT_INP (1 references)
target     prot opt source               destination
ACCEPT     udp  --  anywhere             anywhere             udp dpt:domain
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:domain
ACCEPT     udp  --  anywhere             anywhere             udp dpt:bootps
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:67

Chain LIBVIRT_OUT (1 references)
target     prot opt source               destination
ACCEPT     udp  --  anywhere             anywhere             udp dpt:domain
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:domain
ACCEPT     udp  --  anywhere             anywhere             udp dpt:bootpc
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:68

on VMs:
root@eck-master:~# iptables -L
# Warning: iptables-legacy tables present, use iptables-legacy to see them
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
ACCEPT     all  --  <IP_ADDRESS>/16          anywhere             /* generated for MicroK8s pods */
ACCEPT     all  --  anywhere             <IP_ADDRESS>/16          /* generated for MicroK8s pods */

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

here are the different nmap results:
root@host:~#  nmap -p1-65535 <IP_ADDRESS>
Starting Nmap 7.80 ( https://nmap.org ) at 2022-04-06 12:46 CEST
Nmap scan report for <IP_ADDRESS>
Host is up (0.00052s latency).
All 65535 scanned ports on <IP_ADDRESS> are filtered
MAC Address: 52:54:00:A8:16:6A (QEMU virtual NIC)

Nmap done: 1 IP address (1 host up) scanned in 1313.70 seconds

root@eck-master:~# nmap -p1-65535 <IP_ADDRESS>
Starting Nmap 7.80 ( https://nmap.org ) at 2022-04-06 10:36 UTC
Host is up (0.00074s latency).
All 65535 scanned ports on elk.geoconcept.com (<IP_ADDRESS>) are filtered
MAC Address: 52:54:00:A8:16:6A (QEMU virtual NIC)

Nmap done: 1 IP address (1 host up) scanned in 1313.61 seconds

Using kubectl port forward from the host is working.
Have I done something wrong with this setup?
What would you suggest for me to be digging?
Best Regards,
inspection-report-20220406_145730.tar.gz

Hi @sebastienle14, thank you for filing the issue.
What does the routing table on your host look like? Also, I assume you can ping/curl the addresses of the VMs directly? E.g. <IP_ADDRESS>?

greetings @neoaggelos
Indeed, I can:
root@host:~# ip route show
default via <IP_ADDRESS> dev net100 proto static
<IP_ADDRESS>/24 dev net100 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS>/24 dev net102 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS>/24 dev virbr0 proto kernel scope link src <IP_ADDRESS> linkdown

I believe this output shall be necessary too, sorry I forgot to add it in OP:
root@eck-master:~# kubectl get svc -o wide -n eck
NAME                                 TYPE           CLUSTER-IP       EXTERNAL-IP       PORT(S)                      AGE    SELECTOR
elasticsearch-es-transport           ClusterIP      None             <none>            9300/TCP                     26h    common.k8s.elastic.co/type=elasticsearch,elasticsearch.k8s.elastic.co/cluster-name=elasticsearch
elasticsearch-es-http                ClusterIP      <IP_ADDRESS>    <none>            9200/TCP                     26h    common.k8s.elastic.co/type=elasticsearch,elasticsearch.k8s.elastic.co/cluster-name=elasticsearch
elasticsearch-es-internal-http       ClusterIP      <IP_ADDRESS>    <none>            9200/TCP                     26h    common.k8s.elastic.co/type=elasticsearch,elasticsearch.k8s.elastic.co/cluster-name=elasticsearch
kibana-kb-http                       ClusterIP      <IP_ADDRESS>   <none>            5601/TCP                     26h    common.k8s.elastic.co/type=kibana,kibana.k8s.elastic.co/name=kibana
elasticsearch-es-default             ClusterIP      None             <none>            9200/TCP                     26h    common.k8s.elastic.co/type=elasticsearch,elasticsearch.k8s.elastic.co/cluster-name=elasticsearch,elasticsearch.k8s.elastic.co/statefulset-name=elasticsearch-es-default
ingress-nginx-controller-admission   ClusterIP      <IP_ADDRESS>    <none>            443/TCP                      26h    app.kubernetes.io/component=controller,app.kubernetes.io/instance=ingress-nginx,app.kubernetes.io/name=ingress-nginx
cert-manager                         ClusterIP      <IP_ADDRESS>   <none>            9402/TCP                     26h    app.kubernetes.io/component=controller,app.kubernetes.io/instance=cert-manager,app.kubernetes.io/name=cert-manager
cert-manager-webhook                 ClusterIP      <IP_ADDRESS>    <none>            443/TCP                      26h    app.kubernetes.io/component=webhook,app.kubernetes.io/instance=cert-manager,app.kubernetes.io/name=webhook
nginx-elk                            ClusterIP      <IP_ADDRESS>   <none>            443/TCP                      26h    app=nginx-elk,release=nginx-elk
fleet-server-agent-http              ClusterIP      <IP_ADDRESS>   <none>            8220/TCP                     26h    agent.k8s.elastic.co/name=fleet-server,common.k8s.elastic.co/type=agent
logstash-prod-logstash-headless      ClusterIP      None             <none>            9600/TCP                     5h7m   app=logstash-prod-logstash
logstash-prod-logstash               LoadBalancer   <IP_ADDRESS>    <IP_ADDRESS>   5044:31489/TCP               5h7m   app=logstash-prod-logstash,chart=logstash,release=logstash-prod
ingress-nginx-controller             LoadBalancer   <IP_ADDRESS>    <IP_ADDRESS>   80:32092/TCP,443:30932/TCP   26h    app.kubernetes.io/component=controller,app.kubernetes.io/instance=ingress-nginx,app.kubernetes.io/name=ingress-nginx

I am unable to reproduce this unfortunately, using a similar setup (libvirt hosts, bridged networking), the LB IP is reachable as it should.
If you use a NodePort service, can you reach your service from the host?
What is the networking equipment? Is this on a cloud environment? What does the routing table look like in the VMS? Can you use tcpdump and see if traffic reaches any of the VMs (though this seems unlikely due to the ? Can you double check the firewall rules in the ho
Do you see any warning logs in the metallb pods?

Our Hosting team confirms all networking the host is plugged to are managed by a CISCO Nexus 3064-T, 48 x 10GBase appliance, which should be manageable but they know nothing about yet (they are waiting for the course on this matter).
At the moment, this appliance is managed by one of our partners, and not ourselves.
I will setup tcpdump on both sides (host & VMs) today and will get back to you.
We tried with nodePort service, and the same issue occured.
root@eck-master:~# kubectl -n eck get svc

NAME                                 TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)                      AGE
<snipped>
ingress-nginx-controller             NodePort       <IP_ADDRESS>    <none>        80:32092/TCP,443:30932/TCP   21h

root@host ~# nmap -p1-65535 <IP_ADDRESS>
Starting Nmap 7.80 ( https://nmap.org ) at 2022-04-06 10:31 UTC
Nmap scan report for eck-master (<IP_ADDRESS>)
Host is up (0.0000070s latency).
Not shown: 65523 closed ports
PORT      STATE    SERVICE
22/tcp    open     ssh
111/tcp   open     rpcbind
10250/tcp open     unknown
10255/tcp open     unknown
10257/tcp open     unknown
10259/tcp open     unknown
16443/tcp open     unknown
19001/tcp open     unknown
25000/tcp open     icl-twobase1
30932/tcp filtered unknown
32092/tcp filtered unknown
32381/tcp filtered unknown

Here are the routing tables for the VMs:
root@eck-master:~# ip route show
default via <IP_ADDRESS> dev ens3 proto static
<IP_ADDRESS>/26 via <IP_ADDRESS> dev vxlan.calico onlink
<IP_ADDRESS>/26 via <IP_ADDRESS> dev vxlan.calico onlink
<IP_ADDRESS> dev cali4790718892a scope link
<IP_ADDRESS> dev calie0d8cbdd008 scope link
<IP_ADDRESS>/26 via <IP_ADDRESS> dev vxlan.calico onlink
<IP_ADDRESS>/24 dev ens3 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS>/24 dev ens4 proto kernel scope link src <IP_ADDRESS>

root@eck-worker01:~# ip route show
default via <IP_ADDRESS> dev ens3 proto static
<IP_ADDRESS>/26 via <IP_ADDRESS> dev vxlan.calico onlink
<IP_ADDRESS>/26 via <IP_ADDRESS> dev vxlan.calico onlink
<IP_ADDRESS>/26 via <IP_ADDRESS> dev vxlan.calico onlink
<IP_ADDRESS> dev cali736072e4537 scope link
<IP_ADDRESS> dev calia28b2c14776 scope link
<IP_ADDRESS> dev cali34e6a0f39f4 scope link
<IP_ADDRESS> dev cali0ebfa45a26d scope link
<IP_ADDRESS> dev cali5153b943d31 scope link
<IP_ADDRESS> dev calic4101f61c36 scope link
<IP_ADDRESS> dev calic9ba359cc71 scope link
<IP_ADDRESS> dev cali79a8d91cda9 scope link
<IP_ADDRESS> dev calibb1f5dc25d1 scope link
<IP_ADDRESS>/24 dev ens3 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS>/24 dev ens4 proto kernel scope link src <IP_ADDRESS>

root@eck-worker02:~# ip route show
default via <IP_ADDRESS> dev ens3 proto static
<IP_ADDRESS> dev cali24e82f0ac32 scope link
<IP_ADDRESS> dev cali042c4949e87 scope link
<IP_ADDRESS> dev cali69c374ce9a6 scope link
<IP_ADDRESS> dev cali8b67281a788 scope link
<IP_ADDRESS> dev cali3ab98e7ef56 scope link
<IP_ADDRESS> dev cali0d440ae4e03 scope link
<IP_ADDRESS> dev cali9bbe8a269ad scope link
<IP_ADDRESS> dev cali9382a4fd853 scope link
<IP_ADDRESS> dev cali392ae983540 scope link
<IP_ADDRESS>/26 via <IP_ADDRESS> dev vxlan.calico onlink
<IP_ADDRESS>/26 via <IP_ADDRESS> dev vxlan.calico onlink
<IP_ADDRESS>/26 via <IP_ADDRESS> dev vxlan.calico onlink
<IP_ADDRESS>/24 dev ens3 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS>/24 dev ens4 proto kernel scope link src <IP_ADDRESS>

root@eck-worker03:~# ip route show
default via <IP_ADDRESS> dev ens3 proto static
<IP_ADDRESS>/26 via <IP_ADDRESS> dev vxlan.calico onlink
<IP_ADDRESS> dev cali88e0e4ee76f scope link
<IP_ADDRESS> dev cali52f2043b50e scope link
<IP_ADDRESS> dev caliac9d8debdd8 scope link
<IP_ADDRESS> dev cali63b96077834 scope link
<IP_ADDRESS>/26 via <IP_ADDRESS> dev vxlan.calico onlink
<IP_ADDRESS>/26 via <IP_ADDRESS> dev vxlan.calico onlink
<IP_ADDRESS>/24 dev ens3 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS>/24 dev ens4 proto kernel scope link src <IP_ADDRESS>

And this is the full iptables-save from host:
# Generated by iptables-save v1.8.7 on Thu Apr  7 09:30:08 2022
*mangle
:PREROUTING ACCEPT [433177972:332515709504]
:INPUT ACCEPT [433176194:332515609320]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [285353385:132902329149]
:POSTROUTING ACCEPT [285353385:132902329149]
:LIBVIRT_PRT - [0:0]
-A POSTROUTING -j LIBVIRT_PRT
-A LIBVIRT_PRT -o virbr0 -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill
COMMIT
# Completed on Thu Apr  7 09:30:08 2022
# Generated by iptables-save v1.8.7 on Thu Apr  7 09:30:08 2022
*raw
:PREROUTING ACCEPT [433177972:332515709504]
:OUTPUT ACCEPT [285353385:132902329149]
COMMIT
# Completed on Thu Apr  7 09:30:08 2022
# Generated by iptables-save v1.8.7 on Thu Apr  7 09:30:08 2022
*filter
:INPUT ACCEPT [433176194:332515609320]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [285353385:132902329149]
:LIBVIRT_FWI - [0:0]
:LIBVIRT_FWO - [0:0]
:LIBVIRT_FWX - [0:0]
:LIBVIRT_INP - [0:0]
:LIBVIRT_OUT - [0:0]
-A INPUT -j LIBVIRT_INP
-A FORWARD -j LIBVIRT_FWX
-A FORWARD -j LIBVIRT_FWI
-A FORWARD -j LIBVIRT_FWO
-A OUTPUT -j LIBVIRT_OUT
-A LIBVIRT_FWI -d <IP_ADDRESS>/24 -o virbr0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A LIBVIRT_FWI -o virbr0 -j REJECT --reject-with icmp-port-unreachable
-A LIBVIRT_FWO -s <IP_ADDRESS>/24 -i virbr0 -j ACCEPT
-A LIBVIRT_FWO -i virbr0 -j REJECT --reject-with icmp-port-unreachable
-A LIBVIRT_FWX -i virbr0 -o virbr0 -j ACCEPT
-A LIBVIRT_INP -i virbr0 -p udp -m udp --dport 53 -j ACCEPT
-A LIBVIRT_INP -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
-A LIBVIRT_INP -i virbr0 -p udp -m udp --dport 67 -j ACCEPT
-A LIBVIRT_INP -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
-A LIBVIRT_OUT -o virbr0 -p udp -m udp --dport 53 -j ACCEPT
-A LIBVIRT_OUT -o virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
-A LIBVIRT_OUT -o virbr0 -p udp -m udp --dport 68 -j ACCEPT
-A LIBVIRT_OUT -o virbr0 -p tcp -m tcp --dport 68 -j ACCEPT
COMMIT
# Completed on Thu Apr  7 09:30:08 2022
# Generated by iptables-save v1.8.7 on Thu Apr  7 09:30:08 2022
*nat
:PREROUTING ACCEPT [1270779:76548008]
:INPUT ACCEPT [1269001:76447824]
:OUTPUT ACCEPT [274161:12540602]
:POSTROUTING ACCEPT [274161:12540602]
:LIBVIRT_PRT - [0:0]
-A POSTROUTING -j LIBVIRT_PRT
-A LIBVIRT_PRT -s <IP_ADDRESS>/24 -d <IP_ADDRESS>/24 -j RETURN
-A LIBVIRT_PRT -s <IP_ADDRESS>/24 -d <IP_ADDRESS>/32 -j RETURN
-A LIBVIRT_PRT -s <IP_ADDRESS>/24 ! -d <IP_ADDRESS>/24 -p tcp -j MASQUERADE --to-ports 1024-65535
-A LIBVIRT_PRT -s <IP_ADDRESS>/24 ! -d <IP_ADDRESS>/24 -p udp -j MASQUERADE --to-ports 1024-65535
-A LIBVIRT_PRT -s <IP_ADDRESS>/24 ! -d <IP_ADDRESS>/24 -j MASQUERADE
-A LIBVIRT_PRT -s <IP_ADDRESS>/24 -d <IP_ADDRESS>/24 -j RETURN
-A LIBVIRT_PRT -s <IP_ADDRESS>/24 -d <IP_ADDRESS>/32 -j RETURN
-A LIBVIRT_PRT -s <IP_ADDRESS>/24 ! -d <IP_ADDRESS>/24 -p tcp -j MASQUERADE --to-ports 1024-65535
-A LIBVIRT_PRT -s <IP_ADDRESS>/24 ! -d <IP_ADDRESS>/24 -p udp -j MASQUERADE --to-ports 1024-65535
-A LIBVIRT_PRT -s <IP_ADDRESS>/24 ! -d <IP_ADDRESS>/24 -j MASQUERADE
COMMIT
# Completed on Thu Apr  7 09:30:08 2022

the only reccurent log I see on the metallb-controller is the following line:
W0406 21:22:16.792009       1 reflector.go:302] pkg/mod/k8s.io/client-go@v0.0.0-20190620085101-78d2af792bab/tools/cache/reflector.go:98: watch of *v1.ConfigMap ended with: too old resource version: 10848161 (10849179)
But there's not remarkable warnings about the issue we're discussing, so it seems.
Best Regards,

Yes, the routing tables look good, at this point I think tcpdump is needed to point out what may be going wrong.

We tried with nodePort service, and the same issue occured.

I see the nmap, can you also try a curl?

I see the nmap, can you also try a curl?

Here it is:
root@host:~# curl https://<IP_ADDRESS>:30932/ --insecure
curl: (28) Failed to connect to <IP_ADDRESS> port 30932: Connection timed out

How about curl https://<IP_ADDRESS>:30932 (on the IPs of the nodes directly)?

From the node itself:
root@eck-master:~# curl https://<IP_ADDRESS>:30932 --insecure

<title>404 Not Found</title>

404 Not Found

nginx

From the host, it stalls indefinitively (so far, I'll let it TO):
root@host:~# curl https://<IP_ADDRESS>:30932 --insecure -vvv
*   Trying <IP_ADDRESS>:30932...
* connect to <IP_ADDRESS> port 30932 failed: Connection timed out
* Failed to connect to <IP_ADDRESS> port 30932: Connection timed out
* Closing connection 0
curl: (28) Failed to connect to <IP_ADDRESS> port 30932: Connection timed out

( on another term, at the same time: )
root@host:~# nmap -p1-65535 <IP_ADDRESS> -Pn
Starting Nmap 7.80 ( https://nmap.org ) at 2022-04-07 15:08 CEST
Nmap scan report for <IP_ADDRESS>
Host is up (0.00052s latency).
Not shown: 65520 closed ports
PORT      STATE    SERVICE
22/tcp    open     ssh
111/tcp   open     rpcbind
7472/tcp  open     unknown
7946/tcp  open     unknown
10250/tcp open     unknown
10255/tcp open     unknown
10257/tcp open     unknown
10259/tcp open     unknown
16443/tcp open     unknown
19001/tcp open     unknown
25000/tcp open     icl-twobase1
30418/tcp open     unknown
30932/tcp filtered unknown
31489/tcp filtered unknown
32092/tcp filtered unknown
MAC Address: 52:54:00:9F:B0:4D (QEMU virtual NIC)

Nmap done: 1 IP address (1 host up) scanned in 3.24 seconds
root@host:~#

from the other nodes, it also stall:
root@eck-worker01:~# curl https://<IP_ADDRESS>:30932 --insecure
curl: (28) Failed to connect to <IP_ADDRESS> port 30932: Connection timed out

root@eck-worker01:~# curl https://<IP_ADDRESS>:443 --insecure

<title>404 Not Found</title>

404 Not Found

nginx

as a follow-up:
cross-nodes, the curl on 30932 is not working, but it works on each node querying itself
root@eck-master:~# kubectl -n eck get svc
NAME                                 TYPE           CLUSTER-IP       EXTERNAL-IP       PORT(S)                      AGE
<snipped>
logstash-prod-logstash               LoadBalancer   <IP_ADDRESS>    <IP_ADDRESS>   5044:31489/TCP               26h
ingress-nginx-controller             LoadBalancer   <IP_ADDRESS>    <IP_ADDRESS>   80:32092/TCP,443:30932/TCP   2d
root@eck-master:~# curl https://<IP_ADDRESS>:30932 --insecure

<title>404 Not Found</title>

404 Not Found

nginx

root@eck-worker01:~#  curl https://<IP_ADDRESS>:30932 --insecure

<title>404 Not Found</title>

404 Not Found

nginx

root@eck-worker03:~#  curl https://<IP_ADDRESS>:30932 --insecure

<title>404 Not Found</title>

404 Not Found

nginx

as a follow-up:
cross-nodes, the curl on 30932 is not working, but it works on each node querying itself
root@eck-master:~# kubectl -n eck get svc
NAME                                 TYPE           CLUSTER-IP       EXTERNAL-IP       PORT(S)                      AGE
<snipped>
logstash-prod-logstash               LoadBalancer   <IP_ADDRESS>    <IP_ADDRESS>   5044:31489/TCP               26h
ingress-nginx-controller             LoadBalancer   <IP_ADDRESS>    <IP_ADDRESS>   80:32092/TCP,443:30932/TCP   2d
root@eck-master:~# curl https://<IP_ADDRESS>:30932 --insecure

<title>404 Not Found</title>

404 Not Found

nginx

root@eck-worker01:~#  curl https://<IP_ADDRESS>:30932 --insecure

<title>404 Not Found</title>

404 Not Found

nginx

root@eck-worker03:~#  curl https://<IP_ADDRESS>:30932 --insecure

<title>404 Not Found</title>

404 Not Found

nginx

Okay, judging from that I think the most possible scenario is that something is cutting off network traffic in high ports (30000-32XXX). The issues you are facing with the loadbalancer also stem from that.
Can you test the same scenario, but using the local bridge instead? (that would be <IP_ADDRESS>/24, virbr0). If the issue is with MicroK8s, I would expect the error to persist.

I will try & setup the cluster accordinly, but it might take some time; I do not know if the ticket may be put on hold until monday or so
best regards,

Greetings,
So we tried to set-up a POC environnement, and so far, we failed to even deploy the LoadBalancer (keeps in Pending Status)
poc-master on virbr0 with <IP_ADDRESS>
poc-worker01 on virbr0 with <IP_ADDRESS>
poc-worker02 on virbr0 with <IP_ADDRESS>
We found out that one on the calico component was failing. We are not sure if it's linked or not to our issue.
What's your advice?
We tried to recreate the poc-cluster from scratch, without any deployment, and calico-kube-controllers is still in CrashLoopBack state
Here is what we did on poc-master:
root@poc-master:~# snap install microk8s --classic --channel=latest/stable
microk8s v1.23.5 from Canonical✓ installed
root@poc-master:~# usermod -a -G microk8s $USER
root@poc-master:~# chown -f -R $USER ~/.kube
root@poc-master:~# microk8s status --wait-ready
microk8s is running
high-availability: no
  datastore master nodes: <IP_ADDRESS>:19001
  datastore standby nodes: none
addons:
  enabled:
    ha-cluster           # Configure high availability on the current node
  disabled:
    ambassador           # Ambassador API Gateway and Ingress
    cilium               # SDN, fast with full network policy
    dashboard            # The Kubernetes dashboard
    dashboard-ingress    # Ingress definition for Kubernetes dashboard
    dns                  # CoreDNS
    fluentd              # Elasticsearch-Fluentd-Kibana logging and monitoring
    gpu                  # Automatic enablement of Nvidia CUDA
    helm                 # Helm 2 - the package manager for Kubernetes
    helm3                # Helm 3 - Kubernetes package manager
    host-access          # Allow Pods connecting to Host services smoothly
    inaccel              # Simplifying FPGA management in Kubernetes
    ingress              # Ingress controller for external access
    istio                # Core Istio service mesh services
    jaeger               # Kubernetes Jaeger operator with its simple config
    kata                 # Kata Containers is a secure runtime with lightweight VMS
    keda                 # Kubernetes-based Event Driven Autoscaling
    knative              # The Knative framework on Kubernetes.
    kubeflow             # Kubeflow for easy ML deployments
    linkerd              # Linkerd is a service mesh for Kubernetes and other frameworks
    metallb              # Loadbalancer for your Kubernetes cluster
    metrics-server       # K8s Metrics Server for API access to service metrics
    multus               # Multus CNI enables attaching multiple network interfaces to pods
    openebs              # OpenEBS is the open-source storage solution for Kubernetes
    openfaas             # OpenFaaS serverless framework
    portainer            # Portainer UI for your Kubernetes cluster
    prometheus           # Prometheus operator for monitoring and logging
    rbac                 # Role-Based Access Control for authorisation
    registry             # Private image registry exposed on localhost:32000
    storage              # Storage class; allocates storage from host directory
    traefik              # traefik Ingress controller for external access
root@poc-master:~# microk8s enable dns storage
Enabling DNS
Applying manifest
serviceaccount/coredns created
configmap/coredns created
deployment.apps/coredns created
service/kube-dns created
clusterrole.rbac.authorization.k8s.io/coredns created
clusterrolebinding.rbac.authorization.k8s.io/coredns created
Restarting kubelet
DNS is enabled
Enabling default storage class
deployment.apps/hostpath-provisioner created
storageclass.storage.k8s.io/microk8s-hostpath created
serviceaccount/microk8s-hostpath created
clusterrole.rbac.authorization.k8s.io/microk8s-hostpath created
clusterrolebinding.rbac.authorization.k8s.io/microk8s-hostpath created
Storage will be available soon
oot@poc-master:~# vi /var/snap/microk8s/current/certs/csr.conf.template
root@poc-master:~# microk8s refresh-certs
Taking a backup of the current certificates under /var/snap/microk8s/3052/var/log/ca-backup/
Creating new certificates
Can't load /root/.rnd into RNG
140342700733888:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:88:Filename=/root/.rnd
Can't load /root/.rnd into RNG
140211887805888:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:88:Filename=/root/.rnd
Signature ok
subject=C = GB, ST = Canonical, L = Canonical, O = Canonical, OU = Canonical, CN = <IP_ADDRESS>
Getting CA Private Key
Signature ok
subject=CN = front-proxy-client
Getting CA Private Key
1
Creating new kubeconfig file
Stopped.
Started.

The CA certificates have been replaced. Kubernetes will restart the pods of your workloads.
Any worker nodes you may have in your cluster need to be removed and re-joined to become aware of the new CA.

root@poc-master:~# microk8s enable metallb:<IP_ADDRESS>-<IP_ADDRESS>
Enabling MetalLB
Applying Metallb manifest
namespace/metallb-system created
secret/memberlist created
Warning: policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
podsecuritypolicy.policy/controller created
podsecuritypolicy.policy/speaker created
serviceaccount/controller created
serviceaccount/speaker created
clusterrole.rbac.authorization.k8s.io/metallb-system:controller created
clusterrole.rbac.authorization.k8s.io/metallb-system:speaker created
role.rbac.authorization.k8s.io/config-watcher created
role.rbac.authorization.k8s.io/pod-lister created
clusterrolebinding.rbac.authorization.k8s.io/metallb-system:controller created
clusterrolebinding.rbac.authorization.k8s.io/metallb-system:speaker created
rolebinding.rbac.authorization.k8s.io/config-watcher created
rolebinding.rbac.authorization.k8s.io/pod-lister created
Warning: spec.template.spec.nodeSelector[beta.kubernetes.io/os]: deprecated since v1.14; use "kubernetes.io/os" instead
daemonset.apps/speaker created
deployment.apps/controller created
configmap/config created
MetalLB is enabled
root@poc-master:~# kubectl taint nodes poc-master node-role.kubernetes.io/master=:NoSchedule
node/poc-master tainted
root@poc-master:~# microk8s add-node

On workers, here is what we did:
root@poc-worker01:~# snap install microk8s --classic --channel=latest/stable
microk8s v1.23.5 from Canonical✓ installed
root@poc-worker01:~# microk8s join <IP_ADDRESS>:25000/fc169cbb2003ec5642dd050b9afb11d8/127e916e28e6 --worker
Contacting cluster at <IP_ADDRESS>

The node has joined the cluster and will appear in the nodes list in a few seconds.

Currently this worker node is configured with the following kubernetes API server endpoints:
    - <IP_ADDRESS> and port 16443, this is the cluster node contacted during the join operation.

If the above endpoints are incorrect, incomplete or if the API servers are behind a loadbalancer please update
/var/snap/microk8s/current/args/traefik/provider.yaml

and here is the result from kubectl from Host:
root@host:~/# kubectl get all --all-namespaces
NAMESPACE        NAME                                           READY   STATUS             RESTARTS        AGE
kube-system      pod/coredns-64c6478b6c-p2qkx                   0/1     Running            1 (5m21s ago)   6m14s
metallb-system   pod/speaker-6vw7v                              1/1     Running            0               3m45s
kube-system      pod/calico-node-nmq6m                          1/1     Running            0               93s
metallb-system   pod/speaker-999mv                              1/1     Running            0               93s
kube-system      pod/hostpath-provisioner-7764447d7c-j7xdj      1/1     Running            0               3m45s
metallb-system   pod/controller-558b7b958-z4gnh                 1/1     Running            0               3m45s
kube-system      pod/calico-node-ps67f                          1/1     Running            0               93s
metallb-system   pod/speaker-p5pch                              1/1     Running            0               63s
kube-system      pod/calico-node-5j4mn                          1/1     Running            0               62s
kube-system      pod/calico-kube-controllers-55bcdcf5c6-ht8dz   0/1     CrashLoopBackOff   8 (23s ago)     6m51s

NAMESPACE     NAME                 TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                  AGE
default       service/kubernetes   ClusterIP   <IP_ADDRESS>    <none>        443/TCP                  6m57s
kube-system   service/kube-dns     ClusterIP   <IP_ADDRESS>   <none>        53/UDP,53/TCP,9153/TCP   6m14s

NAMESPACE        NAME                         DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR                 AGE
metallb-system   daemonset.apps/speaker       3         3         3       3            3           beta.kubernetes.io/os=linux   4m49s
kube-system      daemonset.apps/calico-node   3         3         3       3            3           kubernetes.io/os=linux        6m56s

NAMESPACE        NAME                                      READY   UP-TO-DATE   AVAILABLE   AGE
kube-system      deployment.apps/calico-kube-controllers   0/1     1            0           6m56s
kube-system      deployment.apps/coredns                   0/1     1            0           6m14s
kube-system      deployment.apps/hostpath-provisioner      1/1     1            1           6m4s
metallb-system   deployment.apps/controller                1/1     1            1           4m49s

NAMESPACE        NAME                                                 DESIRED   CURRENT   READY   AGE
kube-system      replicaset.apps/calico-kube-controllers-55bcdcf5c6   1         1         0       6m52s
kube-system      replicaset.apps/coredns-64c6478b6c                   1         1         0       6m14s
kube-system      replicaset.apps/hostpath-provisioner-7764447d7c      1         1         1       3m45s
metallb-system   replicaset.apps/controller-558b7b958                 1         1         1       3m45s

And when we tried deploying nginx-ingress, here were the state of the cluster:
NAMESPACE        NAME                                            READY   STATUS    RESTART                            S        AGE
<snipped>
kube-system      pod/calico-kube-controllers-7c6fcdff9f-5hzsf    0/1     Error     13 (32s                             ago)    25h

NAMESPACE     NAME                                         TYPE           CLUSTER-IP                                   EXTERNAL-IP   PORT(S)                     AGE
eck           service/cert-manager-webhook                 ClusterIP      <IP_ADDRESS>                               <none>        443/TCP                     11m
eck           service/cert-manager                         ClusterIP      <IP_ADDRESS>                                <none>        9402/TCP                    11m
eck           service/ingress-nginx-controller-admission   ClusterIP      <IP_ADDRESS>                                <none>        443/TCP                     11m
eck           service/ingress-nginx-controller             LoadBalancer   <IP_ADDRESS>                                <pending>    80:31764/TCP,443:31426/TCP   11m

~# kubectl logs calico-kube-controllers-7c6fcdff9f-5hzsf -n kube-system
2022-04-14 09:32:22.052 [INFO][1] main.go 88: Loaded configuration from environment config=&config.Config{LogLevel:"info", WorkloadEndpointWorkers:1, ProfileWorkers:1, PolicyWorkers:1, NodeWorkers:1, Kubeconfig:"", DatastoreType:"kubernetes"}
W0414 09:32:22.054172       1 client_config.go:543] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
2022-04-14 09:32:22.055 [INFO][1] main.go 109: Ensuring Calico datastore is initialized
2022-04-14 09:32:32.055 [ERROR][1] client.go 261: Error getting cluster information config ClusterInformation="default" error=Get "https://<IP_ADDRESS>:443/apis/crd.projectcalico.org/v1/clusterinformations/default": context deadline exceeded
2022-04-14 09:32:32.055 [FATAL][1] main.go 114: Failed to initialize Calico datastore error=Get "https://<IP_ADDRESS>:443/apis/crd.projectcalico.org/v1/clusterinformations/default": context deadline exceeded

On the former and OP cluster, we do not have issues with calico-controller:
2022-04-14 09:43:49.608 [INFO][1] main.go 88: Loaded configuration from environment config=&config.Config{LogLevel:"info", WorkloadEndpointWorkers:1, ProfileWorkers:1, PolicyWorkers:1, NodeWorkers:1, Kubeconfig:"", DatastoreType:"kubernetes"}
W0414 09:43:49.612469       1 client_config.go:543] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
2022-04-14 09:43:49.613 [INFO][1] main.go 109: Ensuring Calico datastore is initialized
2022-04-14 09:43:56.814 [INFO][1] main.go 149: Getting initial config snapshot from datastore
2022-04-14 09:43:56.853 [INFO][1] main.go 152: Got initial config snapshot
2022-04-14 09:43:56.854 [INFO][1] watchersyncer.go 89: Start called
2022-04-14 09:43:56.854 [INFO][1] main.go 169: Starting status report routine
2022-04-14 09:43:56.854 [INFO][1] main.go 402: Starting controller ControllerType="Node"
2022-04-14 09:43:56.854 [INFO][1] node_controller.go 138: Starting Node controller
2022-04-14 09:43:56.854 [INFO][1] watchersyncer.go 127: Sending status update Status=wait-for-ready
2022-04-14 09:43:56.854 [INFO][1] node_syncer.go 40: Node controller syncer status updated: wait-for-ready
2022-04-14 09:43:56.854 [INFO][1] watchersyncer.go 147: Starting main event processing loop
2022-04-14 09:43:56.854 [INFO][1] watchercache.go 174: Full resync is required ListRoot="/calico/resources/v3/projectcalico.org/nodes"
2022-04-14 09:43:56.854 [INFO][1] resources.go 349: Main client watcher loop
2022-04-14 09:43:56.868 [INFO][1] watchercache.go 271: Sending synced update ListRoot="/calico/resources/v3/projectcalico.org/nodes"
2022-04-14 09:43:56.868 [INFO][1] watchersyncer.go 127: Sending status update Status=resync
2022-04-14 09:43:56.868 [INFO][1] node_syncer.go 40: Node controller syncer status updated: resync
2022-04-14 09:43:56.868 [INFO][1] watchersyncer.go 209: Received InSync event from one of the watcher caches
2022-04-14 09:43:56.868 [INFO][1] watchersyncer.go 221: All watchers have sync'd data - sending data and final sync
2022-04-14 09:43:56.868 [INFO][1] watchersyncer.go 127: Sending status update Status=in-sync
2022-04-14 09:43:56.868 [INFO][1] node_syncer.go 40: Node controller syncer status updated: in-sync
2022-04-14 09:43:56.882 [INFO][1] hostendpoints.go 90: successfully synced all hostendpoints
2022-04-14 09:43:56.955 [INFO][1] node_controller.go 151: Node controller is now running
2022-04-14 09:43:56.955 [INFO][1] ipam.go 45: Synchronizing IPAM data
2022-04-14 09:43:56.999 [INFO][1] ipam.go 191: Node and IPAM data is in sync

@neoaggelos I'll also add our netplan config file from the host to the discussion:
~# cat /etc/netplan/00-installer-config.yaml
network:
  version: 2
  renderer: networkd
  ethernets:
    eno1:
      dhcp4: false
      dhcp6: false
      match:
          macaddress: b0:7b:25:be:ea:da
    enp2s0f0np0:
      dhcp4: false
      dhcp6: false
      match:
          macaddress: 2c:ea:7f:a7:49:3b
  bridges:
    net100:
      interfaces: [eno1]
      mtu: 1500
      addresses: [ <IP_ADDRESS>/24 ]
      nameservers:
          addresses:
             - <IP_ADDRESS>
             - <IP_ADDRESS>
             - <IP_ADDRESS>
          search: []
      routes:
          - to: default
            via: <IP_ADDRESS>
    net102:
      interfaces: [enp2s0f0np0]
      mtu: 1500
      addresses: [ <IP_ADDRESS>/24 ]

I tried to bypass the cisco appliance by plugging a L2 switch on the NIC, the issue remains.
root@host:~# arping -I net100 <IP_ADDRESS>
ARPING <IP_ADDRESS> from <IP_ADDRESS> net100
Unicast reply from <IP_ADDRESS> [52:54:00:A8:16:6A]  0.937ms
Unicast reply from <IP_ADDRESS> [52:54:00:A8:16:6A]  1.071ms
Unicast reply from <IP_ADDRESS> [52:54:00:A8:16:6A]  0.983ms
Unicast reply from <IP_ADDRESS> [52:54:00:A8:16:6A]  1.088ms
Sent 4 probes (1 broadcast(s))

The issue remains, no route to host while trying to reach <IP_ADDRESS> on 443

OK,
After further investigation, it seems the ha-cluster module was to blame.
Upon disabling it and setting up the cluster again, everything seems fine.
ha-cluster disabled means there is no calico layer deployed anymore, so it seems.
We will run it for a week and will let you know how it goes.

Hello,
We ran into a similar problem. is there anything known about the Problems of HA configuration with metallb?


ci: fix handling of single quotes in release changelog

Single quotes in a commit message were causing the exec
plugin of the semantic release process to execute an invalid
command.

Codecov Report

Merging #124 (d9181bc) into main (84c1a30) will decrease coverage by 2.73%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main     #124      +/-   ##
============================================
- Coverage     98.16%   95.43%   -2.74%
- Complexity       51       76      +25
============================================
  Files            15       22       +7
  Lines           109      197      +88
  Branches          2        2
============================================
+ Hits            107      188      +81
- Misses            2        8       +6
- Partials          0        1       +1

Impacted Files
Coverage Δ

...centric/hc/gateway/security/GatewayAuthConfig.java
100.00% <0.00%> (ø)

...ric/hc/gateway/filters/AddRequestHeaderUserId.java
91.66% <0.00%> (ø)

...ric/hc/gateway/filters/UserIdMissingException.java
100.00% <0.00%> (ø)

...odecentric/hc/gateway/security/SecurityConfig.java
95.55% <0.00%> (ø)

...hc/gateway/filters/RewriteTrackPathWithUserId.java
93.33% <0.00%> (ø)

...decentric/hc/gateway/security/ApplicationUser.java
100.00% <0.00%> (ø)

...in/java/de/codecentric/hc/gateway/Application.java
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[Feature] set instance properties in json format: agent.instance_properties_json

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description

I find some configurations are in configurations.md , but not in the agent.config , such as agent.trace_segment_ref_limit_per_span 、agent.instance_properties[key]=value . Otherwise , the configuration plugin.dubbo.consumer_provider_length_threshold  in the agent.config is not the same as plugin.dubbo.provider_arguments_length_threshold in the configurations.md.

@dashanji can you open a pull request to fix this? For agent.instance_properties[xxx], I think we also need to migrate to the format of agent.instance_properties_json={}.  plugin.dubbo.consumer_provider_length_threshold should be typo of plugin.dubbo.consumer_length_threshold
Originally posted by @kezhenxu94 in https://github.com/apache/skywalking/issues/7470#issuecomment-922471256
Use case
For containerized scenarios, we should be able to set the agent.instance_properties easily via environment variables, instead of modifying the config file.
Related issues
https://github.com/apache/skywalking/pull/7470#issuecomment-922471256
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Anyone who wants to take this, please reply and I can assign.

@kezhenxu94 Hi, I would like to take this up, can you please assign it to me? Since I am new to the project, can you also please give a bit more context about the task, and the files which I should start looking at?

@kezhenxu94 Hi, I would like to take this up, can you please assign it to me? Since I am new to the project, can you also please give a bit more context about the task, and the files which I should start looking at?

Hi @deepto98 , thanks for the interest, the rationale behind this task is that, for containerized scenarios, the style of agent.instance_properties[xxx]=xxx is hard (if not impossible) to modify, using json style like agent.instance_properties_json={xxx:yyy}, the users can modify via environment variables.

https://github.com/apache/skywalking-java/pull/67 supported


Updated the section on why we do sprint planning

Added details on what is the purpose of sprint planning

[ x] I have read freeCodeCamp's contribution guidelines.
[ x] My pull request has a descriptive title (not a vague title like Update index.md)
[x ] My pull request targets the master branch of freeCodeCamp.
[x ] None of my changes are plagiarized from another source without proper attribution.
[ x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Looks good to me, and congratulations on your first Pull Request!  🎉🎉🎉
We look forward to future contributions!


/allianceHistory/{alliance_id} throws an internal server error

Cause: pydantic expects integer values in the returned AllianceOut & UserOut objects, but those are None for Collections of data version 8 and below.

Closed with v1.3.0


Caller is not able to end the call

We are using v1.10.0, the issue we are facing is when caller cuts the call, the call is still active.
We are not getting the event callDisconnect and so.
When caller is making a call and it is ringing to the other person, at the same time we are getting callConnected event event call is in ringing state now. Call is ringing at the other side and caller cuts the call there is no event trigger to the caller except the RNKeep's endCall and call is still ringing and other person can still receive call.

// For Android if Caller is not able to end the call add below line inside TwilioPhoneModule.kt file line no. 338
activeCalls[call.sid!!] = call
Now Check Enjoy !!


Update qr_code_suspicious_indicators.yml

Adding image size restrictions

/mql-mimic-exempt: 112340,111602,114206,114016,114015,111578,113081,113550,115144
These fire other tighter scoped QR code rules


CI: bump numpy version from 1.10.2 to 1.10.4

We should be testing against the last micro version of the numpy 1.10.x series.
(Originally, it was 1.10.1 when that was the last one, then it got bumped to 1.10.2, and then it was not updated when 1.10.4 came out).

Agreed, merged. Thanks Evgeni


HAWQ-867. Replace the git-submobule mechanism with git-clone

This is a further code change based on the previous patch for this JIRA.
This patch updates the pgcrypto commit number to the correct one
which we previously used.

+1

+1


[FEATURE REQUEST] Category Card Improvements

I have 2 suggestions regarding category cards:
1- There is min-height set on the category cards, but it creates an issue on the mobile screens where the min-height causes for the card to be too high.
Solution here might be removing min-height on sm-down.
2- We should decrease padding-sides from 24px to 16px on md-down. It is already 16px on sm-down.

Sounds good. We need to take an action @hsnaydd @bugrakocak


no wallet api

Some of the cooler language clients support the /wallet api.  This would be a significant improvement to the the java client.  This would seem to require:

a new WalletService with these methods http://dev.blockcypher.com/#wallet-api
new model classes:

Wallet http://dev.blockcypher.com/#wallet
AddressKeychain http://dev.blockcypher.com/#addresskeychain
HDWallet http://dev.blockcypher.com/#hdwallet
HDChain http://dev.blockcypher.com/#hdchain
HDAddress http://dev.blockcypher.com/#hdaddress

update Address to include "wallet" and "hdWallet" (assuming we ever return those)
update Webhook and WebhookService to include a "walletName"
[probably more stuff]

Ideally, we could also get some helper to generate the "extended public key" necessary for HD wallets.

A wallet API would be good. In the meantime, for anyone who wants to spend from a wallet without specifying input transactions, you can do it like this:
String transactionJson = "{" +
                        "\"inputs\":[{\"wallet_name\":\"" + WALLET_NAME + "\"," +
                        " \"wallet_token\":\"" + TOKEN + "\"}]," +
                        "\"outputs\":[{\"addresses\": [\"" + sendToAddress + "\"], " +
                        "\"value\": -1}]}"; // -1 means sweep all value from all addresses

                IntermediaryTransaction unsignedTx = context.getTransactionService().newTransaction(transactionJson);

I'm tagging this as help wanted as this would be really useful.


[Q] Read state of X1 contact?

Is it possible to see the state of X1 contact in the list of sensor values?
I found some hints in the UDP programmers guide, that X1 is transfered, but didn't find a matching sensor in HA.
These chapters talk about X1:
2.3 UDP Broadcast Messages
2.6 UDP command „report“

Hi @PulsarFX
sorry for my late reply. This is already implemented. Check out the optional sensor named "Input"


Align UI for credential view edit and view mode

Task/Issue URL: https://app.asana.com/0/488551667048375/1202630343540913/f
include also:

https://app.asana.com/0/0/1202630343540914/f
https://app.asana.com/0/0/1202630343540909/f

Description
This PR includes

aligning UI and UX to design for Credential read only mode
aligning UI and UX to design for Credential edit mode
Increasing test coverage for AutofillSettingsViewModel
This doesn't include updating in the store any of the new fields: domain title, last updated and notes.

Steps to test this PR
Happy path view and edit mode

[ ] Be sure to have some autofill credentials already saved
[ ] Open credential view for one credential
[ ] Verify that read only mode is shown and is aligned with design. Key things to check: Toolbar buttons, Title,  handling for unset fields and copy/password buttons.
[ ] Press context menu and click on edit
[ ] Verify that edit mode is shown and is aligned with design. Key things to check: Toolbar buttons, Title and copy/password buttons.
[ ] Press check icon and confirm that read only mode is set and data is saved (except for notes)

Edge cases

[ ] Check that no weird states in toolbar/views when locking screen / backgrounding screen / changing orientation
[ ] Check that no weird states when removing device auth while in edit / read only modes
[ ] Check no UI issues on Dark mode

Bug: If I edit a username and then hit the ✖ button, I should see the original username but the one I typed in remains. (it doesn't persist, but it remains in the UI)

Bug: editing the URL doesn't persist, even when tapping ✔ button (changes to username and password works fine)

Minor UX complaint: it would be great if the cursor position wasn't reset when toggling the password visibility. If i just want to check i've typed the password correctly so far, it's annoying it throws the cursor back to the beginning each toggle

It's quite harsh that if you switch apps momentarily when editing you lose all edits without a chance to keep what you've changed. If you want to merge what you have now, with that behaviour, I'm good with it, but if so can you raise that with design/product for input on what should be done because it's not great long term.


I/you/we haven't seen those...

I/you/we haven't seen those... created by<EMAIL_ADDRESS>on 2017-01-07 13:32:13

<EMAIL_ADDRESS>replied, how should I say "i haven't seen your dogs" or "you haven't seen those things"?

<EMAIL_ADDRESS>replied, Ng dirkak ues a chermem el bilis.Ng dirkak mues aikei el klalo.

<EMAIL_ADDRESS>replied, kmal mesaul, e Ulang!OMES is so irregular, that sometimes I feel frustrated using it)

<EMAIL_ADDRESS>replied, Ke omes er ker e Aleks.

<EMAIL_ADDRESS>replied, Dirkak a ta el kues...
E kemiu, how I'd do?

<EMAIL_ADDRESS>replied, So we have UES already as a noun but this usage seems like a verb.  Is this a variant of MES and is a v.pf.3p.inan.?

<EMAIL_ADDRESS>replied, John, it was hypo. of MES, not UES, but DIRKAK KUES. Ulang missed the one K saving her time))))

<EMAIL_ADDRESS>replied, No no dirkak ues. Ues: sight/seenMes: see/seenUlemes: saw/have seenOmes:see/lookAika kmal meral ungil ues. These are really breathtaking sights.Good night.

<EMAIL_ADDRESS>replied, Komla mes a chermek el bilis. You've seen my dogs.Ke miles a chermek el bilis? Did you see my dogs?Aika blak ues. I have seen these.Kulemes el Mei. You looked this way.Aika oblem ues er chelii. You saw them yesterday.

<EMAIL_ADDRESS>replied, Josephs would write it so: Aika bla kues. I have seen these.Ke ulemes el mei. You looked this way.Aika choble mues er a elii. You saw them yesterday.Thanks! Great, Ulang! Now I am familiarized with OMES

<EMAIL_ADDRESS>replied, That way to write them is strange because the consonant sound is not with the ues.Bla kues, bla mues, bla luesare pronounced blak ues, blam ues, blal ues.

<EMAIL_ADDRESS>replied, Josephs spelling is officially adopted, so I'm trying to follow it consequentially. k-, m-, l- are all prefixes for UES, but not suffixes for auxiliary verb BLA

<EMAIL_ADDRESS>replied, This seems like an instance where we should add these hypo forms since they
seem pretty irregular.
kues
mues
lues
kimues
dues
What do we call these?  v.hypo.1s, etc?

<EMAIL_ADDRESS>replied, why not v.hyp.1s. ? i don't know whether that sounds foolishly in English...in any case, the most convenient term for these form is irrealis: v.irr.1s. etc. but Josephs had not used it, while other austronesianists call it only irrealis.


Trouble importing APIClient from openlaw npm package

Hi, I am trying to incorporate openlaw into my project. I've installed openlaw using npm, but as soon as I try to import the APIClient into my react component using
import { APIClient, Openlaw } from "openlaw";
I get this error:
Starting the development server...

<--- Last few GCs --->

[20276:00000179AF5DAE30]    87321 ms: Mark-sweep 1301.0 (1441.3) -> 1286.4 (1438.8) MB, 2155.7 / 0.0 ms  (average mu = 0.115, current mu = 0.083) allocation failure scavenge might not succeed
[20276:00000179AF5DAE30]    87424 ms: Scavenge 1300.7 (1438.8) -> 1287.9 (1441.3) MB, 5.5 / 0.0 ms  (average mu = 0.115, current mu = 0.083) allocation failure

<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 000001A4F19DC5C1]
Security context: 0x00631041e6e9 <JSObject>
    1: next [0000006310419FB9](this=0x01d8eb6bcce1 <Array Iterator map = 00000138CD906141>)
    2: StubFrame [pc: 000001A4F19D5D8B]
    3: StubFrame [pc: 000001A4F198B75A]
    4: validate [0000021A631CA679] [C:\repos\ProjectPegasus\node_modules\@babel\types\lib\definitions\utils.js:~199] [pc=000001A4F26786D8](this=0x021a631c7849 <Object map = 000001B9B2544...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 00007FF699C9DD8A v8::internal::GCIdleTimeHandler::GCIdleTimeHandler+4506
 2: 00007FF699C78886 node::MakeCallback+4534
 3: 00007FF699C79200 node_module_register+2032
 4: 00007FF699F930DE v8::internal::FatalProcessOutOfMemory+846
 5: 00007FF699F9300F v8::internal::FatalProcessOutOfMemory+639
 6: 00007FF69A179804 v8::internal::Heap::MaxHeapGrowingFactor+9620
 7: 00007FF69A1707E6 v8::internal::ScavengeJob::operator=+24550
 8: 00007FF69A16EE3C v8::internal::ScavengeJob::operator=+17980
 9: 00007FF69A177B87 v8::internal::Heap::MaxHeapGrowingFactor+2327
10: 00007FF69A177C06 v8::internal::Heap::MaxHeapGrowingFactor+2454
11: 00007FF69A2A1EA7 v8::internal::Factory::NewFillerObject+55
12: 00007FF69A31F096 v8::internal::operator<<+73494
13: 000001A4F19DC5C1
error Command failed with exit code 134.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.```

Has anyone encountered this before? Is there something else that I need to do?

Hi, @javaadpatel it's a matter of a local copy of npm and its settings.
One solution I've read is to delete your C:\Users\{USER}\.npmrc and try again. Or, try increasing the memory limit of npm as described in this article: https://medium.com/@vuongtran/how-to-solve-process-out-of-memory-in-node-js-5f0de8f8464c#targetText=By default the memory limit,avoid the memory limit issue.&targetText=That's it.


Udated with new 2022.3 hbp improvements NO_JIRA

Updated with new HBP improvements from 2022.3 release (new HBP chart colours/legend, new HBP table data)

Corrected the typo and made the other suggested improvements, thanks.


.find("textArea[name='description']") is broken

The following find fails to find the component in the latest version of enzyme (2.2.0), looks likes its broken in 2.1.0. We are using React 0.14.x, does that mean we can't upgrade enzyme?
var component = enzyme.mount(Component, props);
var textArea = component.find("textArea[name='description']");
textArea.simulate('change');
The following error occurs:
// Error: This method is only meant to be run on single node. 0 found instead.
Test runs fine with 1.5.0 version.
//Component

<textarea name="description" rows="5" cols="55" />

@cliren why would textArea find a textarea?

@ljharb Sorry I should have given a complete example, textarea is child of another component.

Can you update the code for Component? it doesn't contain textArea.

ah..., that's right it should be textarea instead of textArea. That fixed it. But still wondering why this passed in 1.5.0, guessing its a bug that got fixed. Here is an example test that would pass 1.5.0 and not in the latest just for reference.
describe("TextArea Test", ()=> {
const TestComponent = React.createClass({
render(){
return (

);
}
});
it("should render text area", () => {
let testComponent = mount();
testComponent.find("input").length.should.eql(1);
testComponent.find("textArea").simulate("change");

});
});

I'm not sure why .find("textArea") would have passed in any version of enzyme. The casing definitely matters here.

Agree with you.

@coderefractor that would have passed precisely because calling "simulate(change)" is not an assertion - ie, the line was always a noop. At some point, enzyme started throwing when calling simulate on a wrapper that doesn't contain one node, turning your noop into a failure.

got it, thanks!


systemd running with 100% and does not respond

Version
Microsoft Windows [Version 10.0.22000.1042]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
Linux version <IP_ADDRESS>-microsoft-standard-WSL2
Distro Version
Ubuntu 22.04
Other Software
systemd/jammy-updates,now 249.11-0ubuntu3.6 amd64
Repro Steps

enable systemd
set log_target to kmsg
run dmesg

Expected Behavior
Systemd is running and system behaves normal
Actual Behavior
systemd is running but floods kmsg and cpu is at 100% (even w/o log_target). No systemctl command passes through.
steven:~$ LANG=C systemctl status
Failed to read server status: Transport endpoint is not connected

Diagnostic Logs
dmesg output
[ 1273.089268] systemd[1]: acpid.service: Trying to enqueue job acpid.service/start/replace
[ 1273.089282] systemd[1]: tmp.mount: Cannot add dependency job, ignoring: Unit tmp.mount not found.
[ 1273.089344] systemd[1]: ovsdb-server.service: Cannot add dependency job, ignoring: Unit ovsdb-server.service not found.
[ 1273.089380] systemd[1]: acpid.service: Installed new job acpid.service/start as 552357512
[ 1273.089381] systemd[1]: acpid.service: Enqueued job acpid.service/start as 552357512
[ 1273.089385] systemd[1]: acpid.service: ConditionVirtualization=!container failed.
[ 1273.089386] systemd[1]: acpid.service: Starting requested but condition failed. Not starting unit.
[ 1273.089387] systemd[1]: acpid.service: Job 552357512 acpid.service/start finished, result=done
[ 1273.089388] systemd[1]: Condition check resulted in ACPI event daemon being skipped.
[ 1273.089389] systemd[1]: acpid.path: Got notified about unit deactivation.
[ 1273.089395] systemd[1]: acpid.path: Got triggered.
[ 1273.089396] systemd[1]: acpid.service: Trying to enqueue job acpid.service/start/replace
[ 1273.089409] systemd[1]: tmp.mount: Cannot add dependency job, ignoring: Unit tmp.mount not found.
[ 1273.089471] systemd[1]: ovsdb-server.service: Cannot add dependency job, ignoring: Unit ovsdb-server.service not found.
[ 1273.089505] systemd[1]: acpid.service: Installed new job acpid.service/start as 552357593
[ 1273.089506] systemd[1]: acpid.service: Enqueued job acpid.service/start as 552357593
[ 1273.089510] systemd[1]: acpid.service: ConditionVirtualization=!container failed.
[ 1273.089511] systemd[1]: acpid.service: Starting requested but condition failed. Not starting unit.
[ 1273.089512] systemd[1]: acpid.service: Job 552357593 acpid.service/start finished, result=done
[ 1273.089513] systemd[1]: Condition check resulted in ACPI event daemon being skipped.
[ 1273.089514] systemd[1]: acpid.path: Got notified about unit deactivation.
[ 1273.089520] systemd[1]: acpid.path: Got triggered.
[ 1273.089521] systemd[1]: acpid.service: Trying to enqueue job acpid.service/start/replace
[ 1273.089534] systemd[1]: tmp.mount: Cannot add dependency job, ignoring: Unit tmp.mount not found.

Looks like acpid is stuck in a runaway activation loop. But since acpid isn't going to be doing anything useful under WSL anyway (being for hardware support), I suggest you manually mask the relevant units with:
sudo ln -s /dev/null /etc/systemd/system/acpid.service
sudo ln -s /dev/null /etc/systemd/system/acpid.path

then shut down and restart your WSL instance.

Hi, systemd is starting now, thanks for the quick fix, but still doesn't respond:
[   48.293227] systemd[163]: Not remounting /run/systemd/unit-root/sys/fs/cgroup/pids deny-listed by /run/systemd/unit-root/sys/fs/cgroup, called for /run/systemd/unit-root/sys
[   48.293232] systemd[163]: Not remounting /run/systemd/unit-root/sys/fs/cgroup/rdma deny-listed by /run/systemd/unit-root/sys/fs/cgroup, called for /run/systemd/unit-root/sys
[   49.155384] hv_balloon: Max. dynamic memory size: 8044 MB
[   93.311250] Failed to query system state: Transport endpoint is not connected
[   93.312174] WSL (2) ERROR: InitCreateSessionLeader:1072: systemd: failed to start within 10000

and
 systemctl status
Failed to read server status: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)

Hi, systemd is starting now, thanks for the quick fix, but still doesn't respond:
[   48.293227] systemd[163]: Not remounting /run/systemd/unit-root/sys/fs/cgroup/pids deny-listed by /run/systemd/unit-root/sys/fs/cgroup, called for /run/systemd/unit-root/sys
[   48.293232] systemd[163]: Not remounting /run/systemd/unit-root/sys/fs/cgroup/rdma deny-listed by /run/systemd/unit-root/sys/fs/cgroup, called for /run/systemd/unit-root/sys
[   49.155384] hv_balloon: Max. dynamic memory size: 8044 MB
[   93.311250] Failed to query system state: Transport endpoint is not connected
[   93.312174] WSL (2) ERROR: InitCreateSessionLeader:1072: systemd: failed to start within 10000

and
 systemctl status
Failed to read server status: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)

Same issue here solved with the same solution
> wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19044.2604

I had to disable other hw related services as well (gpu)

Looks like acpid is stuck in a runaway activation loop. But since acpid isn't going to be doing anything useful under WSL anyway (being for hardware support), I suggest you manually mask the relevant units with:
sudo ln -s /dev/null /etc/systemd/system/acpid.service
sudo ln -s /dev/null /etc/systemd/system/acpid.path

then shut down and restart your WSL instance.

This broke my WSL2 setup. Can't access any of my distros now.


Another segfault

The equation
$=\text{Ker}\begin{pmatrix}{\tiny \begin{matrix}\lambda_1-\lambda_i\\&\lambda_1-\lambda_i\end{matrix}}\\&{\tiny \begin{matrix}\ddots\\&0\\&&0\\&&&0\\&&&&0\end{matrix}\\&&{\tiny \begin{matrix}\lambda_1-\lambda_i\\&\lambda_1-\lambda_i\end{matrix}}}$

causes MicroTeX to segfault. While this isn't valid TeX and should probably result in a parsing failure, it shouldn't cause whatever application links against MicroTeX to crash.
(Also occurs on clm)
I've tried fixing it, however the entire stack seems to be exlusively random garbage in gdb

fixed by 97e4b5d.
See this example.
On XeLaTeX and LuaLaTeX, this code will result in an error. The best approach would be to inform the user that using it this way is incorrect, but for now let's leave it as is.

fixed by 97e4b5d .

great. I think I had already found a working version that used matrices within the matrix (useful when you want to "box" a certain part of the matrix using \fbox.
But the most important thing about this was that the stack-smashing that happened won't occur anymore (at least in this case), given that with specifically crafted formula input you're likely to get arbitrary code execution, which seems really dangerous. Maybe one should look into fuzzing to check if there is more of that.

given that with specifically crafted formula input you're likely to get arbitrary code execution, which seems really dangerous

That's true. But currently it seems that this situation is still within a controllable range, so I don't think we need to worry too much about it right now.

But currently it seems that this situation is still within a controllable range, so I don't think we need to worry too much about it right now.

I'm not actually sure it is 🙃 . On the one hand, I'm don't think anyone is currently rendering "untrusted" equations using clm/µTeX, however if someone were to do that, it'll likely be quite fatal.
However, a very large majority of crashes logged by notekit are due to cLaTeXMath. Obv. a large chunk of them already shouldn't occur anymore once MicroTeX is released, as the most common segfaults are already fixed, but running a fuzzer over it (~sp1ritCS:cLaTeXMath/fuzzer) I found 600 (filtered to 100) crashes in a very short amount of time, so I'll look into fixing at least some of them.

But currently it seems that this situation is still within a controllable range, so I don't think we need to worry too much about it right now.

I'm not actually sure it is upside_down_face . On the one hand, I'm don't think anyone is currently rendering "untrusted" equations using clm/µTeX, however if someone were to do that, it'll likely be quite fatal.
However, a very large majority of crashes logged by notekit are due to cLaTeXMath. Obv. a large chunk of them already shouldn't occur anymore once MicroTeX is released, as the most common segfaults are already fixed, but running a fuzzer over it (~sp1ritCS:cLaTeXMath/fuzzer) I found 600 (filtered to 100) crashes in a very short amount of time, so I'll look into fixing at least some of them.

Wow, that's really scary... Are you willing to submit fuzzer test code to the openmath branch? I'd like to test it out as well.

closing this as it has been fixed


Calls never complete

Hello,
I made a fork of bitrave here and modified it but have experienced quite a few issues when it comes to building thus my search for something else. I found Unity3dAzure and it is good to see you are carrying on! I am more than interested to help development with this. Anyway onto the issue!
I tried cloning this repo and following the steps but none of the network requests ever seem to complete. Ignore the error, that is related to onGUI code from inputting a score

What platform are you running Unity on? I am adding support for Windows UnityEditor once I merge the 'windows' branch.

I am running on Windows 10 (though can test on OSX if needed).
I was able to build to Android and have the calls successfully complete from the master branch.
From the windows branch I was able to build to .exe and android and have the calls complete in the editor. However I encountered compile errors when building to windows store / phone

Yes please try on Mac for now as Windows branch is not yet 100% ready. But let me know if you get it working on Mac so I can close this issue. I hope to have an update in soon!

Both the master and windows branch works on OSX in editor and mac .app build.
I got an on GUI error that didn't break anything (only on mac), I may bring over my new UI scene from here if you are interested

Cool I will close off this issue. I've just pushed a commit into 'windows' branch that works in Windows RT app now so I'll issue a PR on that once I test changes on other platforms again. I was looking into the new Unity UI and that would be a good idea as the legacy GUI can get a bit flaky sometimes. I have created a new issue for this #3 if you want to fork it and do a PR. Although I will need to write up a Contributions doc to make sure this demo project works the way Unity developers expect / like.


Implement getTailCallCopyArgsThunk

This is needed to support tail calling methods with many parameters.
The stub itself doesn't seem too hard, but we'll need to add some sort of support for emitting labels in the machine code stream. Also, GC info encoding at some point.

@janvorli is working on the design for this.

Duplicate of https://github.com/dotnet/corert/issues/1683


add column user_max to history table, as describled in https://www.percona.c…

…om/doc/percona-toolkit/2.0/pt-query-digest.html#cmdoption-pt-query-digest--review-history, this will cause pt-query-digest tool to store user info to this column.
This solves issue #138

Hi @hankya, thanks for the pull request. Before we can merge it, we need you to sign our Contributor License Agreement. You can do so electronically here: http://opensource.box.com/cla
Once you have signed, just add a comment to this pull request saying, "CLA signed". Thanks!

CLA signed.

I couldn't find a signed CLA for @hankya. Can you please try again?

Signed again, could you please verify?

@hankya boxcla is a bot. I guess it's waiting for a "CLA signed." comment.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.yangrun seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.yangrun seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


OpenCL output erroe

Hello:
I use Tesseract 3.4 on CentOS 7, and I test it by some sample words.  In general environmental condition(not opencl), it work successfully, and output words is right.  In opencl condition(./configure --enable-opencl), it can work, but output words is garbled.
Why?

You should read the wiki, search issues (also closed), search in the tesseract forum before you post your issues/question.
Opencl is still experimental feature with a lot of open issues (and original committer is not fixing them...)

Hi Zdenko!
I added a note about the state of OpenCL in Tesseract to this wiki page:
https://github.com/tesseract-ocr/tesseract/wiki/TesseractOpenCL


what about a bower components loader for browsers ?

The approach using for bowerder can be a good start since components are provided with files ready for production. However it's far away from AMD module philosophy. That said feedback are welcome, specially if they concert behavior, necessity and enhancements.

Maybe once can think that it isn't a place for that but since this specially concern bower, why not ?

Hey. That's a nice project, it's really similar to jspm. It could be good for development, but production applications probably require also bundler like webpack, jspm, browserify, or rollup.

Web technologies are growing so fast with divers solutions. However, it firstly affect particular developers who are directly involved. From universities to startup, it generally with time that they get involved. Specially in my country, when i look around, CommonJS, AMD, es-module features are just improvements that once ear about (if he do) and that will maybe transform the future of project's development. (soon old or maybe) actual approach steel persevere (and maybe will continue to) because it is difficult to tell today to someone who want to learn thing that he have to do like this and tomorrow that he have to throw it because this (for him complicate (this because he is inexperienced)) (for you better (cause your are experienced and futurist)) new way is more efficient.
without counting that these new solutions (preferable for professional developers) are like Linux was (or is) to Windows users.

Feel free to send PR to list this project on our official "Tools" page :)
https://bower.io/docs/tools/


Feature request: Add option for current opened file's directory to 'terminal.integrated.cwd'

Currently when opening the integrated terminal, we have two options for the default terminal path:

The path is set to the current working directory (i.e. the current working project folder).
The path is set to an explicit path given by the user.

There should be a 3rd option, where the path is the current opened file's directory.

Right now this use case is covered by https://marketplace.visualstudio.com/items?itemName=Tyriar.vscode-terminal-here


Document Emitted Metrics

Add documentation describing which metrics are emitted when a metric.Client is provided to scroll.AppConfig.

This repository is not maintained. Feel free to fork if you still need it.


Implement Svelte 5

Since Svelte 5 is on RC it would be nice to start searching about updating svelte-standalone to svelte 5 and identify breaking changes.

https://github.com/brenoliradev/svelte-standalone/tree/svelte-5
status: not even building
breaking list:

generate.d.ts only generates { [x: string]: any }
toast story example breaking apart (needs to correctly be rewrite using $state rune
rollup doesnt see to be parsing correctly


Added patch support to wrapper

Thanks so much for writing this, it has saved me a lot of time. One quick addition - I was having trouble getting my email addresses to update, so added the following to line 100 below case 'delete':
case 'patch':
                    curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'PATCH');
                    curl_setopt($ch, CURLOPT_POSTFIELDS, $json_data);
                    break;

Thanks!

Sounds good - are you able to make a pull request? Otherwise I'll add it when I get a chance.

Hi Drew,
I attempted a pull request, but please let me know if it didn't go through
correctly, since I've not done this before. Thanks again for write the
wrapper, I appreciate your taking the time to put it together!

Leanne

On Sat, Jul 18, 2015 at 8:10 AM, Drew McLellan<EMAIL_ADDRESS>wrote:

Sounds good - are you able to make a pull request? Otherwise I'll add it
when I get a chance.
—
Reply to this email directly or view it on GitHub
https://github.com/drewm/mailchimp-api/issues/44#issuecomment-122535327.

--
Leanne Heller
<EMAIL_ADDRESS>www.adaroconsulting.com
p<PHONE_NUMBER>
Adaro Consulting LLC
WordPress Web Development
We focus on business websites and agency partnerships.


[BUG] retrieving accountUser needs to be batched (limited by 2500 records)

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior

the fact that we downloaded exactly 2500 records is a dead giveaway that we ran into max batch size
Expected Behavior
run retrieve in batches to retrieve > 2500 records
Steps To Reproduce

Go to '...'
Click on '....'
Run '...'
See error...

Version
4.1.12
Environment

OS:
Node:
npm:

Participation

[X] I am willing to submit a pull request for this issue.

Additional comments
No response

looks like that was a mere coincidence:


Last minute content update

Change 'proposed solution' to 'proposal everywhere
Added 'to' to 'Try not take too many...'


Odd error messages

Related Ticket - https://jhulibraries.atlassian.net/browse/LAGS-184

Looks like this needs more work. I didn't export configs before testing a rebuild locally and this is likely the cause of the issues.


No harvest report created when it is launched by schedule

JIRA issue created by: pkiraly
Originally opened: 2012-03-19 02:45 PM
Issue body:
(nt)
This issue has an attachment associated with it (external link): 1078.png

JIRA Comment by user: pkiraly
JIRA Timestamp: 2012-04-12 06:51 PM
Comment body:
Now the schedule page contains the link of harvest reports made during cron based running.

JIRA Comment by user: pkiraly
JIRA Timestamp: 2012-04-12 06:55 PM
Comment body:
There is a problem still here, the URL of the report. Currently it is
admin/xc/harvester/batch/[batch ID]
instead of something like
admin/xc/harvester/schedule/[schedule ID]/batch/[batch ID]
which is more expressive.

Issue resolved: 2012-04-13 02:25 PM


ES - Add Ability to Recreate the RAM Disk via Command (GSFC DCR 21594)

The ES startup creates and initializes the RAM disk. If the RAM disk becomes corrupted there is no ground interface provided to recreate the RAM disk.

During GSFC GPM TV testing, a RAM disk corruption was experienced. A processor reset was needed in order to restore the RAM disk to an operational state. See the attached PFR description for more details.

Imported from trac issue 94.  Created by sstrege on 2015-08-27T14:53:56, last modified: 2019-03-21T16:25:24

Trac comment by glimes on 2015-09-18 10:00:29:
It might also be useful as part of this effort to deploy a tool that checks the RAM disk metadata for inconsistencies.
The ability to repair an inconsistent filesystem in place is customary in other environments, so it may be worth thinking about whether it might be useful in this context.

Trac comment by glimes on 2016-10-18 15:07:03:
Remove my name from many tickets (where it was applied by default), so others can tell that there are tickets that need some attention.


Feasibility as lockscreen.

Could it be possible to use ly without logging out of the X session as a potential screen lock?

Just passing by to say I'd be interested too.
Currently I'm using i3-lock-fancy with a mini-script that picks a random WhatTheCommit quote but I'd gladly change for Ly with Doomfire on.

As said in #291, I don't know if this is possible, and if it is it must be incredibly complex, closing for now :(


Diagnostics still showing on different buffer

Hi @rachartier,
first of all thank you for such a great plugin, I'm eager to adopt it!
I'm using NvChad and have set things up as documented, here's my config:
-- plugin install
{
	"rachartier/tiny-inline-diagnostic.nvim",
	event = "VeryLazy",
	config = function()
		require("tiny-inline-diagnostic").setup()
	end,
},

-- nvchad
{
	"neovim/nvim-lspconfig",
	config = function()
		require("nvchad.configs.lspconfig").defaults() # source: https://github.com/NvChad/NvChad/blob/v2.5/lua/nvchad/configs/lspconfig.lua#L55-L85
		vim.diagnostic.config({ virtual_text = false })
	end,
},

At first glance, things seem to work, e.g. my neovim configs using lua-language-server LSP

However, opening a different file retains the diagnostics

Do you happen to have an idea what could be causing this?
Let me know if there's any additional debug info I can provide.
Thank you!

Hello,
Thanks for the issue !
I will try to take a look at it tomorow.

The latest fix should resolve your issue. If you can try it !


[BUG] 同一个注解在不同命名空间的同一个类名，只会收集到一个类

Execute the command and paste the result below.
Command: uname -a && php -v && composer info | grep hyperf && php --ri swoole
Darwin macdeMacBook-Pro.local 20.6.0 Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:31 PDT 2021; root:xnu-7195.141.2~5/RELEASE_X86_64 x86_64
PHP 7.4.19 (cli) (built: May 13 2021 06:28:47) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
    with Yasd v0.3.9-alpha, Our Copyright, by codinghuang
    with Zend OPcache v7.4.19, Copyright (c), by Zend Technologies
hyperf/amqp                          v2.2.3             A amqplib for hyperf.
hyperf/async-queue                   v2.2.0             A async queue component for hyperf.
hyperf/cache                         v2.2.0             A cache component for hyperf.
hyperf/circuit-breaker               v2.2.0             A circuit breaker component for hyperf.
hyperf/command                       v2.2.0             Command for hyperf
hyperf/config                        v2.2.0             An independent component that provides configuration container.
hyperf/config-apollo                 v2.2.0             An apollo adapter for Hyperf config component.
hyperf/config-center                 v2.2.0             The abstraction component of config center
hyperf/constants                     v2.2.0             A constants component for hyperf.
hyperf/consul                        v2.2.0             A Consul Client for Hyperf.
hyperf/contract                      v2.2.0             The contracts of Hyperf.
hyperf/database                      v2.2.0             A flexible database library.
hyperf/db-connection                 v2.2.0             A hyperf db connection handler for hyperf/database.
hyperf/devtool                       v2.2.0             A Devtool for Hyperf.
hyperf/di                            v2.2.1             A DI for Hyperf.
hyperf/dispatcher                    v2.2.0             A HTTP Server for Hyperf.
hyperf/elasticsearch                 v2.2.0             Elasticsearch client for hyperf
hyperf/engine                        v1.1.6
hyperf/event                         v2.2.0             an event manager that implements PSR-14.
hyperf/exception-handler             v2.2.0             Exception handler for hyperf
hyperf/framework                     v2.2.0             A coroutine framework that focuses on hyperspeed and flexible, specifically use for build microservices and m...
hyperf/guzzle                        v2.2.0             Swoole coroutine handler for guzzle
hyperf/http-message                  v2.2.0             microservice framework base on swoole
hyperf/http-server                   v2.2.1             A HTTP Server for Hyperf.
hyperf/ide-helper                    v2.2.0             IDE help files for Hyperf.
hyperf/json-rpc                      v2.2.0             A JSON RPC component for Hyperf RPC Server or Client.
hyperf/load-balancer                 v2.2.0             A load balancer library for Hyperf.
hyperf/logger                        v2.2.0             A logger component for hyperf.
hyperf/memory                        v2.2.0             An independent component that use to operate and manage memory.
hyperf/model-cache                   v2.2.0             A model cache component for hyperf.
hyperf/model-listener                v2.2.0             A model listener for Hyperf.
hyperf/nacos                         v2.2.3             Nacos SDK
hyperf/paginator                     v2.2.0             A paginator component for hyperf.
hyperf/pool                          v2.2.0             An independent universal connection pool component.
hyperf/process                       v2.2.3             A process component for hyperf.
hyperf/redis                         v2.2.0             A redis component for hyperf.
hyperf/rpc                           v2.2.0             A rpc basic library for Hyperf.
hyperf/rpc-client                    v2.2.0             An abstract rpc server component for Hyperf.
hyperf/rpc-server                    v2.2.0             An abstract rpc server component for Hyperf.
hyperf/server                        v2.2.0             A base server library for Hyperf.
hyperf/service-governance            v2.2.0             A service governance component for Hyperf.
hyperf/service-governance-consul     v2.2.0             A consul adapter for service governance.
hyperf/service-governance-nacos      v2.2.3             A nacos adapter for service governance.
hyperf/snowflake                     v2.2.0             A snowflake library
hyperf/testing                       v2.2.0             Testing for hyperf
hyperf/tracer                        v2.2.0             A open tracing system implemented for Hyperf or other coroutine framework
hyperf/translation                   v2.2.0             An independent translation component, forked by illuminate/translation.
hyperf/utils                         v2.2.0             A tools package that could help developer solved the problem quickly.
hyperf/validation                    v2.2.0             hyperf validation
hyperf/watcher                       v2.2.2             Hot reload watcher for Hyperf

swoole

Swoole => enabled
Author => Swoole Team<EMAIL_ADDRESS>Version => 4.7.0
Built => Jul 30 2021 11:21:23
coroutine => enabled with boost asm context
kqueue => enabled
rwlock => enabled
openssl => OpenSSL 1.1.1k  25 Mar 2021
dtls => enabled
json => enabled
curl-native => enabled
pcre => enabled
zlib => 1.2.11
brotli => E16777225/D16777225
async_redis => enabled

Directive => Local Value => Master Value
swoole.enable_coroutine => On => On
swoole.enable_library => On => On
swoole.enable_preemptive_scheduler => Off => Off
swoole.display_errors => On => On
swoole.use_shortname => Off => Off
swoole.unixsock_buffer_size => 262144 => 262144

Description:
如题
Steps To Reproduce:

对的，就是这么设计的


[RTM] Fixing regressed schema tests

Fixes #322

I am not sure why this code was removed and the error regressed.
@suyashdb I'm gonna go ahead and merge it now - will add tests later.


Bootstrap fiber framework.

Codecov Report
Attention: Patch coverage is 85.71429% with 2 lines in your changes missing coverage. Please review.

Project coverage is 75.00%. Comparing base (f463adc) to head (b45425d).

Files with missing lines
Patch %
Lines

cmd/argocd-tangle-server/main.go
85.71%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##            main       #5       +/-   ##
==========================================
+ Coverage   0.00%   75.00%   +75.00%
==========================================
  Files          1        1
  Lines          3       16       +13
==========================================
+ Hits           0       12       +12
- Misses         3        4        +1

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


Tapping in the comment column, instead resulting in pressing the material code button

Expected behavior
When tapping in the comment column, it should look like the image in this capture

Actual behavior
Error occurs, when I tap the comment column, some code material will appear in the comment column. As shown in the image below

Note:
Although this behavior is rare, but this is very disturbing.
How to reproduce

Explore https://busy.org. Then go to some post to reply to a comment
Then tap on the comment column
It will result in such behavior as described above
Browser: Google Chrome fast & secure version 67.0.3396.81
Operating system: Oppo a57 android version 6.0.1

Recording Of The Bug
https://youtu.be/MXUbUQFtJNg

This error also occurs when pressing other features. For example when I want to tap an activity feature. It actually took me to the wallet. See youtube link above please.
https://youtu.be/2KqlS5wR-KI

This is happening on phone only. It is not a control issue, rather a touch alignment issue (touch is getting trigger about half above the actual point of contact). I have been having this issue since last 3 days now intermittently. It happens in the text area as well.

Does this problem still persist? I tested it on Chrome 67.0.3396.87 on Android 8.0 on current busy.org and couldn't reproduce.

Yeah,  i am still having this problem, this is very disturbing to me

Could you provide specific post that has this problem?

I do not know what you mean about specific problem, but you can see my other videotape here https://youtu.be/2KqlS5wR-KI

It's not post specific.  It seems to appear randomly, but persists once it has occurred until you renavigate to Busy. Happens at least once a day to be on Brave Browser on Android 8.

@thewizardstudio. Are this issue will be fixed?


Support asymmetric matching in toMatchObject

Closes #2781.
This adds support for “asymmetric matching” to toMatchObject. Example:
const houseForSale = {
  bath: true,
  bedrooms: 4
};

expect(houseForSale).toMatchObject({
  bedrooms: expect.any(Number)
});

Now passes.

Hm, that doesn't look good - but the CI failure seems to be related to a possibly-intermittent yarn problem. Can the job for the failing Node version be rerun?

This looks good, thanks for the PR!

Nice work!

I just want to say, this was really good. @nfarina, great first contribution. @thymikee, great work on helping Nick through this. Looking forward to using this in Jest 19 myself!

Well shucks…it was only four lines of copy-pasted code and @thymikee told me exactly how to do it but I am loving this positive feedback!


Update Armeria to 1.19.0 from 1.16.0

Description
Updates Armeria to 1.19.0 which is the current latest version of Armeria.
Issues Resolved
Resolves #1806
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1837 (a67dacf) into main (3999fb7) will decrease coverage by 0.04%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #1837      +/-   ##
============================================
- Coverage     94.19%   94.14%   -0.05%
- Complexity     1521     1522       +1
============================================
  Files           191      191
  Lines          4460     4460
  Branches        363      363
============================================
- Hits           4201     4199       -2
- Misses          177      179       +2
  Partials         82       82

Impacted Files
Coverage Δ

...rwarder/discovery/AwsCloudMapPeerListProvider.java
92.68% <0.00%> (-2.44%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

The WhiteSource Security Check is failing. But, it is reporting a failure on snakeyaml from the OpenSearch client. So I don't think this was introduced by Armeria.


Scheduled jobs: Update Hugo modules is failing

https://github.com/pulumi/docs/runs/4910749034?check_suite_focus=true#step:8:37

@cnunciato do you know whats up with this?

From the log -- Yarn was temporarily unavailable:
error An unexpected error occurred: "https://registry.yarnpkg.com/purgecss/-/purgecss-4.0.3.tgz:
Request failed \"502 Bad Gateway\"".

Momentarily blip, happens sometimes. Looks like the next run passed and the site's currently deploying, so nothing to be done on our end.


feat: hook up pay changes to new pay redeem card

feat: hook up pay changes to new pay redeem card
Add support for redeem
ethereum logo
pot

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#4310  👈
#4309
#4308
#4307
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @wraeth-eth and the rest of your teammates on  Graphite


ci: print node version

:tada: This PR is included in version 2.13.0 :tada:
The release is available on:

v2.13.0
npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fixed uninitialised variable

The big change from before seems to have missed this.
Fix uninitialised variable in callable_method_pointer.h

@hbina  Is this still desired? If so, it needs to be rebased and tested on the latest master branch.


V6 use clickable

Overview
This introduces a new hook (a couple actually!) called use-clickable. It implies the ability to gain focus (through tabIndex). It uses onKeyDown to capture Enter or Space keys. This is useful for things like Button or Tab even when they aren't a button element (e.g. have role="button"). It also ensures consistent behavior across browsers.

added useLiveRef which just holds onto a mutable value so it can be can be used in other hooks
removed deprecated style config hook (no longer used)
unified exports for useStyleConfig to make consistent with other /hooks/*

Screenshots (if applicable)
NA
Documentation

[ ] Updated Typescript types and/or component PropTypes
[ ] Added / modified component docs
[ ] Added / modified Storybook stories

Alright, made some updates here – this is ready for review again @akleiner2 @colinlohner


Multiple Endpoints

Hi,
If I have more than 1 webhook what is the best way to utilise that method?

There is not.

Can this be supported in the future as we used to use Client('hook')


you will want to fine the Authentication/AuthenticationTypes section.

change to
you will want to find the Authentication/AuthenticationTypes section.
for file powerbi-docs/powerbi-docs/report-server/configure-kerberos-powerbi-reports.md

Thanks for your feedback, @hiteshgaur ! Did you know that because our docs are in GitHub, you can edit them yourself? For a fix like this, please select the Edit pencil at the top-right on this page, make the change yourself, and submit it. OK? Then the author can review it and accept it.
Thanks again for your help in improving the docs!

Thank you Kelly, I tried the pencil, but it forked out the repo for me. :)
Happy Friday !!


We should skip the non-existing text unit and continue importing tran…

…slations
@aurambaj We ran into issues while importing exported tm xliffs because some of the xliffs had translation for non-existing translation units. I think skipping them is better than throwing run-time exception and aborting the whole import process. Let me know what you think.
Do you know why we have some translations in the exported localized tm xliffs for the text unit that is not in the source tm xliff?

@jeeyi With the current implementation, I think the hard error make sense. We don't remove text units as far as I know so there must be a bug somewhere else.
Did you check if the entry was in the DB?

@aurambaj The text unit differences come from plurals. In English tm xliff, I have text unit *_one and *_other. In localized tm xliff for ar-SA, I have more text units according to the plural rules. tm-import gets terminated when it tries to import translation for *_zero because it is not in the English tm xliff and considered as adding a translation to a non-existing text unit.

oh when importing plural strings for the source it should actually create all forms, that's the issue. Your fix can be a temporary solution, though
Why do still use that feature btw, what's the use case?

@jeeyi btw, if you re-generate the source file they should have all the plural form, right?

@aurambaj You mean, if I push the source file? Let me test it. I think it should work.