Multilingual Stacks

When multilingual websites are enabled, each stack ought to get a dropdown. By default it defaults to the default locale, but you can change the flag for each stack and get a different instance of it. Then, on the front-end the stack renders in the default locale.
If a stack block is displayed in the site, the current locale of the page informs which version of the stack to grab.
If a global area is rendered, the locale of the current page informs which multilingual stack to grab.

Definitely need this functionality. I have been using the GlobalArea mod created by hissy to try to get this behavior.

+1

Hi Andrew, I saw that you changed up the milestone names and dates. Any idea when this one might get assigned?

Not yet – we are currently throwing our development resources at some other targets for 5.7.4.

Will be released in 5.7.5

Nice! Thanks @aembler !

Great! Can I test it with develop branch?

Yep, should be ready to go
On Tue, Jun 16, 2015 at 4:47 PM, Takuro Hishikawa<EMAIL_ADDRESS>wrote:

Great! Can I test it with develop branch?
—
Reply to this email directly or view it on GitHub
https://github.com/concrete5/concrete5/issues/1718#issuecomment-112604375
.

GREAT!

+1 needing this sooo bad. Hope it will really make it to the next release! Thank you guys!


Boot output

Hi,
I copied your image to an SD card (dd if=mangopi-mq-riscv-2023-1-serial-console.img of=/dev/sda bs=1024), plugged the Mango Pi in, but I am not getting any output on either UART0 (P3 header) or UART1 (P2 header) at 115200 baud.
Where should I be looking? 😅

Hi!
Serial console is on UART3. Its not available from P2 or P3 headers but thru special pads near DSI MIPI connector. Look at my picture "Activated interfaces".

Spot on! I soldered a header for the debug output (I'm still puzzled why it is not mounted by default) and now it boots straight into shell.
Thank you.


Kube-dns crashed when weave plugin used

What you expected to happen?
Expect that kube-dsn is up after deployment of weave plugin.
What happened?
E0205 15:05:28.519183       1 reflector.go:201] k8s.io/dns/pkg/dns/dns.go:150: Failed to list *v1.Service: Get https://<IP_ADDRESS>:443/api/v1/services?resourceVersion=0: dial tcp <IP_ADDRESS>:443: i/o timeout
E0205 15:05:28.519486       1 reflector.go:201] k8s.io/dns/pkg/dns/dns.go:147: Failed to list *v1.Endpoints: Get https://<IP_ADDRESS>:443/api/v1/endpoints?resourceVersion=0: dial tcp <IP_ADDRESS>:443: i/o timeout
I0205 15:05:29.018365       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:29.518414       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:30.018394       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:30.518408       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:31.018377       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:31.518468       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:32.018393       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:32.518415       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:33.018413       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:33.518439       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:34.018393       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:34.518386       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:35.018409       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:35.518429       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:36.018444       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:36.518384       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:37.018413       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:37.518474       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:38.018362       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:38.518355       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:39.018387       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:39.518432       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:40.018414       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:40.518397       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:41.018433       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:41.518866       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:42.018433       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:42.518424       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:43.018396       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:43.518485       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:44.018403       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:44.518406       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:45.018414       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:45.518460       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:46.018373       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:46.518308       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:47.018392       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:47.518437       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:48.018438       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:48.518390       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:49.018386       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:49.518444       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:50.018406       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:50.518386       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:51.018364       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:51.518433       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:52.018375       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:52.518384       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:53.018387       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:53.518378       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:54.018393       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:54.518388       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:55.018362       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:55.520461       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:56.018395       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:56.518402       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:57.018370       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:57.518387       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0205 15:05:58.018384       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
F0205 15:05:58.518384       1 dns.go:167] Timeout waiting for initialization

How to reproduce it?
Deploy k8s via kubeadm
# kubeadm init --pod-network-cidr=<IP_ADDRESS>/16 --token abcdef.1234567890123456
# export KUBECONFIG=/etc/kubernetes/admin.conf
# kubever=$(kubectl version | base64 | tr -d '\n')
# kubectl apply -f "https://cloud.weave.works/k8s/net?k8s-version=$kubever"
Anything else we need to know?

  Can you reach the outside world, or ping one pod from another by its pod IP address?
I'll note you have a lot of these warnings, going on for ~30 minutes:
{"log":"WARN: 2018/02/05 14:59:17.548655 Vetoed installation of hairpin flow FlowSpec{keys: [EthernetFlowKey{src: fe:57:00:5f:b9:aa, dst: 16:6b:33:12:99:e0} InPortFlowKey{vport: 1}], actions: [OutputAction{vport: 1}]}\n","stream":"stderr","time":"2018-02-05T14:59:17.549006348Z"}
{"log":"WARN: 2018/02/05 14:59:17.548748 Vetoed installation of hairpin flow FlowSpec{keys: [EthernetFlowKey{src: fe:57:00:5f:b9:aa, dst: 16:6b:33:12:99:e0} InPortFlowKey{vport: 1}], actions: [OutputAction{vport: 1}]}\n","stream":"stderr","time":"2018-02-05T14:59:17.549039384Z"}
{"log":"WARN: 2018/02/05 14:59:18.550029 Vetoed installation of hairpin flow FlowSpec{keys: [EthernetFlowKey{src: fe:57:00:5f:b9:aa, dst: 16:6b:33:12:99:e0} InPortFlowKey{vport: 1}], actions: [OutputAction{vport: 1}]}\n","stream":"stderr","time":"2018-02-05T14:59:18.550310826Z"}

@bboreham Thanks for the fast answer
I created two test pods
# kubectl get pods
NAME         READY     STATUS    RESTARTS   AGE
test-pod-1   1/1       Running   0          12m
test-pod-2   1/1       Running   0          12m

ping from pod to another pod IP - PASS
ping from node to pod IP - FAILED

# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
From <IP_ADDRESS> icmp_seq=1 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=2 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=3 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=4 Destination Host Unreachable

ping from pod to internal node IP - FAILED

# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
--- <IP_ADDRESS> ping statistics ---
16 packets transmitted, 0 received, 100% packet loss, time 14999ms

Give me know if you will need additional information.

@cynepco3hahue You have specified --pod-network-cidr=<IP_ADDRESS>/16 which is different from the default of Weave - <IP_ADDRESS>/12.
Mind trying to bootstrap the cluster with kudeadm without passing --pod-network-cidr?

@brb I tried to run

kubeadm init --pod-network-cidr=<IP_ADDRESS>/12 --token abcdef.1234567890123456
kubeadm init --token abcdef.1234567890123456
But I have the same result.

@cynepco3hahue Thanks for the experiments.
Is it possible to get a ssh access to your machine? I'm martynas at the Weave community Slack.
If not, I'm interested in the following:

Do you have the br_netfilter module compiled in? Is it enabled (cat /proc/sys/net/bridge/bridge-nf-call-iptables)?
In your previous experiments, is fe:57:00:5f:b9:aa a MAC addr of eth0 belonging to kubedns?
Is your node a VM? If yes, what kind of?
Output of weave report.
Output of dmesg from the node.
Output of ip link from the node.
PCAPs of tcpdump -i weave from the node and tcpdump -i eth0 from the pod when pinging the pod from the node and vice versa.

@brb It is locally running vagrant machine, so I can not provide access to it, but will try to give much info as I can :smile:
0. br_netfilter
# cat /proc/sys/net/bridge/bridge-nf-call-iptables
1
# cat /proc/sys/net/bridge/bridge-nf-call-ip6tables
1

I run each time new Vagrant machine so it hard to say for me, will provide new logs and ip addr info

[root@master ~]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 52:54:00:4d:81:d8 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic eth0
       valid_lft 3080sec preferred_lft 3080sec
    inet6 fe80::5054:ff:fe4d:81d8/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 52:54:00:f9:9e:21 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::5054:ff:fef9:9e21/64 scope link
       valid_lft forever preferred_lft forever
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN
    link/ether 02:42:80:3a:c9:80 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 scope global docker0
       valid_lft forever preferred_lft forever
5: datapath: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1376 qdisc noqueue state UNKNOWN
    link/ether 26:7a:d2:96:ae:87 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::247a:d2ff:fe96:ae87/64 scope link
       valid_lft forever preferred_lft forever
6: weave: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1376 qdisc noqueue state UP
    link/ether ae:f6:9e:b9:f8:fd brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/12 brd <IP_ADDRESS> scope global weave
       valid_lft forever preferred_lft forever
    inet6 fe80::acf6:9eff:feb9:f8fd/64 scope link
       valid_lft forever preferred_lft forever
7: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN
    link/ether 7a:aa:1b:f2:1f:dd brd ff:ff:ff:ff:ff:ff
9: vethwe-datapath@vethwe-bridge: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1376 qdisc noqueue master datapath state UP
    link/ether e6:f8:86:00:7d:22 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::e4f8:86ff:fe00:7d22/64 scope link
       valid_lft forever preferred_lft forever
10: vethwe-bridge@vethwe-datapath: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1376 qdisc noqueue master weave state UP
    link/ether ce:83:63:c7:5e:5f brd ff:ff:ff:ff:ff:ff
    inet6 fe80::cc83:63ff:fec7:5e5f/64 scope link
       valid_lft forever preferred_lft forever
12: vethweple1854e6@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1376 qdisc noqueue master weave state UP
    link/ether ce:0a:91:ea:a3:b0 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::cc0a:91ff:feea:a3b0/64 scope link
       valid_lft forever preferred_lft forever

weave_0.log
weave-npc_0.log

Yes it vagrant VM
weave_report.log
dmesg.log
# ip link

# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
    link/ether 52:54:00:4d:81:d8 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
    link/ether 52:54:00:f9:9e:21 brd ff:ff:ff:ff:ff:ff
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT
    link/ether 02:42:80:3a:c9:80 brd ff:ff:ff:ff:ff:ff
5: datapath: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1376 qdisc noqueue state UNKNOWN mode DEFAULT
    link/ether 26:7a:d2:96:ae:87 brd ff:ff:ff:ff:ff:ff
6: weave: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1376 qdisc noqueue state UP mode DEFAULT
    link/ether ae:f6:9e:b9:f8:fd brd ff:ff:ff:ff:ff:ff
7: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN mode DEFAULT
    link/ether 7a:aa:1b:f2:1f:dd brd ff:ff:ff:ff:ff:ff
9: vethwe-datapath@vethwe-bridge: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1376 qdisc noqueue master datapath state UP mode DEFAULT
    link/ether e6:f8:86:00:7d:22 brd ff:ff:ff:ff:ff:ff
10: vethwe-bridge@vethwe-datapath: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1376 qdisc noqueue master weave state UP mode DEFAULT
    link/ether ce:83:63:c7:5e:5f brd ff:ff:ff:ff:ff:ff
12: vethweple1854e6@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1376 qdisc noqueue master weave state UP mode DEFAULT
    link/ether ce:0a:91:ea:a3:b0 brd ff:ff:ff:ff:ff:ff link-netnsid 0

I will add tcpdump later, I need to configure environment first

TCP dumps

ping from node to pod
ping_node_to_pod.tar.gz
ping pod to node
ping_pod_to_node.tar.gz

I do not sure why, but when I used tcpdump ping started work fine and when I stopped tcpdump ping failed again.

I do not sure why, but when I used tcpdump ping started work fine and when I stopped tcpdump ping failed again.

This suggests that ICMP traffic is enabled after the iface entered the promiscuous mode (due to tcpdump).
Could you verify whether some HTTP traffic is enabled as well by creating a nginx Pod and trying to curl it?
If it fails, then it is a good indicator that you might be suffering from leaking netns (#2842) and could explain why the promisc mode enabled the traffic.

I create simple nginx with the command
kubectl run my-nginx --image=nginx --replicas=1 --port=80
# kubectl get pods -o wide
NAME                       READY     STATUS    RESTARTS   AGE       IP          NODE
my-nginx-9d5677d94-j6kvs   1/1       Running   0          4m        <IP_ADDRESS>   master

[root@master ~]# curl http://<IP_ADDRESS>:80
curl: (7) Failed connect to <IP_ADDRESS>:80; No route to host
[root@master ~]# curl http://<IP_ADDRESS>
curl: (7) Failed connect to <IP_ADDRESS>:80; No route to host

Thanks. Is it the same when tcpdump is running?

With tcpdump all works fine
# kubectl get pods -o wide
NAME                       READY     STATUS    RESTARTS   AGE       IP          NODE
my-nginx-9d5677d94-d76fx   1/1       Running   0          2m        <IP_ADDRESS>   master
[root@master ~]# tcpdump -i weave -w ping &
[1] 18608
[root@master ~]# tcpdump: listening on weave, link-type EN10MB (Ethernet), capture size 262144 bytes

[root@master ~]# curl http://<IP_ADDRESS>
<!DOCTYPE html>

<title>Welcome to nginx!</title>

Welcome to nginx!

If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.

For online documentation and support please refer to
nginx.org.

Commercial support is available at
nginx.com.

Thank you for using nginx.

Thanks. I was expecting curl to fail, but it didn't.
Could you share the VM image or point me to Vagrantfile that I could run and debug myself?

You can check it via GitHub https://github.com/kubevirt/kubevirt/blob/master/Vagrantfile

Hello,
I've met a similar problem, when I've tried to use a Kubernetes cluster with Weave Net plugin.
I've configured weave network by two ways:

via yaml file and applying this file to kubernetes using kubeclt apply -f command
via weave installation like a service according Weave documentation.

In both of cases I 've gotten a network between containers and containers could see each other and communicate via his weave IPs.
But I've gotten an error from kube-dns service, where kubedns container was not able to reach <IP_ADDRESS>:443 (standart "kubernetes" service for apiserver endpoint). Also any NodePort of any service have not available for me from a host machine.
A NodePort (e.g. 30101) became available only when I've run a "tcpdump -i weave" command.
I've tried to investigate it and found that weave plugin shown a strange behavior and sometimes can't create a route record. Also in ARP table also something was wrong and weave rows was in incomplete status. But, after running tcpdump, these lines has became completed and port has became available.
ARP without tcpdump:
Address                  HWtype  HWaddress           Flags Mask            Iface
<IP_ADDRESS>                        (incomplete)                              weave
<IP_ADDRESS>                        (incomplete)                              weave

ARP with tcpdump:
Address                  HWtype  HWaddress           Flags Mask            Iface
<IP_ADDRESS>                ether   c2:7d:41:6d:33:50   C                     weave
<IP_ADDRESS>                ether   2a:bf:4d:95:3a:e5   C                     weave

I've solved the issue by using another network plugin: Flannel.

Hi @dostoevskoy,
Thanks for the info.
What is your distro, kernel vsn and weave vsn?

Distributive: SLES 12.0
Kernel version: 3.12.61-52.106-default
Weave version: Version: 2.2.0

Any Update?

@zhoulouzi What exactly is the issue you are running into?

My hypothesis is that on old kernels (< v4.0) the promiscuous mode setting of the weave bridge gets reset. However, I haven't had a chance to validate it.

@brb I just encountered the same issue described above. My kernel is 3.13.0-33-generic #58-Ubuntu.
I'm running kubernetes inside a DinD container so it's easy for me to tear everything down and start from scratch. Here's the dmesg output following after the deployment of weave:
Oct  2 03:44:18 master0 kernel: [939208.830660] br-480f57c2d95b: port 6(veth91e2cd9) entered forwarding state
Oct  2 03:44:26 master0 kernel: [939216.353176] device datapath entered promiscuous mode
Oct  2 03:44:26 master0 kernel: [939216.354305] device vethwedu entered promiscuous mode
Oct  2 03:44:26 master0 kernel: [939216.354601] device vethwedu left promiscuous mode
Oct  2 03:44:26 master0 kernel: [939216.354613] weave: port 1(vethwedu) entered disabled state
Oct  2 03:44:26 master0 kernel: [939216.376595] device vethwe-bridge entered promiscuous mode
Oct  2 03:44:26 master0 kernel: [939216.376843] IPv6: ADDRCONF(NETDEV_UP): vethwe-datapath: link is not ready
Oct  2 03:44:26 master0 kernel: [939216.377151] device vethwe-datapath entered promiscuous mode
Oct  2 03:44:26 master0 kernel: [939216.377277] IPv6: ADDRCONF(NETDEV_CHANGE): vethwe-datapath: link becomes ready
Oct  2 03:44:26 master0 kernel: [939216.409769] IPv6: ADDRCONF(NETDEV_UP): weave: link is not ready
Oct  2 03:44:27 master0 kernel: [939217.375560] weave: port 1(vethwe-bridge) entered forwarding state
Oct  2 03:44:27 master0 kernel: [939217.375590] weave: port 1(vethwe-bridge) entered forwarding state
Oct  2 03:44:27 master0 kernel: [939217.375648] IPv6: ADDRCONF(NETDEV_CHANGE): weave: link becomes ready
Oct  2 03:44:36 master0 kernel: [939226.716896] IPVS: Creating netns size=2048 id=622
Oct  2 03:44:36 master0 kernel: [939226.716903] ip_set: protocol 6
Oct  2 03:44:36 master0 kernel: [939226.719557] IPVS: Creating netns size=2048 id=623
Oct  2 03:44:36 master0 kernel: [939226.719561] ip_set: protocol 6
Oct  2 03:44:37 master0 kernel: [939227.122286] IPVS: Creating netns size=2048 id=624
Oct  2 03:44:37 master0 kernel: [939227.122291] ip_set: protocol 6
Oct  2 03:44:37 master0 kernel: [939227.218483] device vethwepld768548 entered promiscuous mode
Oct  2 03:44:37 master0 kernel: [939227.297445] IPv6: ADDRCONF(NETDEV_UP): vethwepld768548: link is not ready
Oct  2 03:44:37 master0 kernel: [939227.323747] IPv6: ADDRCONF(NETDEV_CHANGE): vethwepld768548: link becomes ready
Oct  2 03:44:37 master0 kernel: [939227.323772] weave: port 2(vethwepld768548) entered forwarding state
Oct  2 03:44:37 master0 kernel: [939227.323785] weave: port 2(vethwepld768548) entered forwarding state
Oct  2 03:44:37 master0 kernel: [939227.414281] device vethwepl61fd29e entered promiscuous mode
Oct  2 03:44:37 master0 kernel: [939227.505344] IPv6: ADDRCONF(NETDEV_UP): vethwepl61fd29e: link is not ready
Oct  2 03:44:37 master0 kernel: [939227.505354] weave: port 3(vethwepl61fd29e) entered forwarding state
Oct  2 03:44:37 master0 kernel: [939227.505361] weave: port 3(vethwepl61fd29e) entered forwarding state
Oct  2 03:44:37 master0 kernel: [939227.523509] IPv6: ADDRCONF(NETDEV_CHANGE): vethwepl61fd29e: link becomes ready
Oct  2 03:44:37 master0 kernel: [939227.868768] device vethwepldd0c839 entered promiscuous mode
Oct  2 03:44:37 master0 kernel: [939227.921777] IPv6: ADDRCONF(NETDEV_UP): vethwepldd0c839: link is not ready
Oct  2 03:44:37 master0 kernel: [939227.921787] weave: port 4(vethwepldd0c839) entered forwarding state
Oct  2 03:44:37 master0 kernel: [939227.921798] weave: port 4(vethwepldd0c839) entered forwarding state
Oct  2 03:44:37 master0 kernel: [939227.944009] IPv6: ADDRCONF(NETDEV_CHANGE): vethwepldd0c839: link becomes ready
Oct  2 03:44:38 master0 kernel: [939228.181736] IPv6: eth0: IPv6 duplicate address fe80::1ca1:3aff:fedf:d782 detected!
Oct  2 03:44:38 master0 kernel: [939228.209851] IPv6: eth0: IPv6 duplicate address fe80::a4b8:71ff:fe41:707a detected!
Oct  2 03:44:38 master0 kernel: [939228.394079] IPv6: eth0: IPv6 duplicate address fe80::981e:6ff:fee4:6d1 detected!
Oct  2 03:44:42 master0 kernel: [939232.396132] weave: port 1(vethwe-bridge) entered forwarding state
Oct  2 03:44:52 master0 kernel: [939242.385756] weave: port 2(vethwepld768548) entered forwarding state
Oct  2 03:44:52 master0 kernel: [939242.545986] weave: port 3(vethwepl61fd29e) entered forwarding state
Oct  2 03:44:52 master0 kernel: [939242.962095] weave: port 4(vethwepldd0c839) entered forwarding state
Oct  2 03:45:11 master0 kernel: [939261.254871] weave: port 2(vethwepld768548) entered disabled state
Oct  2 03:45:11 master0 kernel: [939261.255375] device vethwepld768548 left promiscuous mode
Oct  2 03:45:11 master0 kernel: [939261.255385] weave: port 2(vethwepld768548) entered disabled state

At this point all pods relying on <IP_ADDRESS>:443 to access the kubernetes api will fail (such as the kubernetes dashboard, CoreDNS or kube-dns)
The actual device 'weave' is not set in promisc mode, if I then run:
ip link set dev weave promisc on
I get the following in dmesg
Oct  2 03:49:13 master0 kernel: [939503.961032] device weave entered promiscuous mode
and the <IP_ADDRESS>:443 endpoint becomes accessible from the pods (as well as any ips assigned to the host through ping)

@drake7707 Thanks for the info.

@drake7707 Did you just enable the promiscuous mode for the weave bridge on each node or did you enable for any other interface as well to make it work?

@brb Nope, just the master and only the weave bridge (though the master is the one that had an older Linux kernel). Technically I didn't even need any worker nodes. When just deploying the master I tried both CoreDNS and Kube-DNS pods and both still failed to connect to the kubernetes API (<IP_ADDRESS>). As soon as I enabled promisc on of the weave interface inside the DinD container they could connect.

Fixed by #3442

Thanks @drake7707 for all the info. It was very helpful to diagnose and fix the problem.


luarocks needs lua 5.1

Did you check docs and existing issues?

[X] I have read all the lazy.nvim docs
[X] I have searched the existing issues of lazy.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.10
Operating system/version
MacOs
Describe the bug
When i do a LazyHealth check wihtin lazyvim it says that luarocks is installed but the version is not correct. Looking at the website of luarocks they are even using luarock with lua 5.3.
Steps To Reproduce
Install the latest version of lua
Install luarocks
LazyHealth

Expected Behavior
It should not give a warning as I'm using a newer version of lua
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

luarocks for NEovim plugins requires Lua 5.1, that is completely correct.

I've improved the health check to show steps you can do to fix your luarocks installation.

luarocks for NEovim plugins requires Lua 5.1, that is completely correct.

oh! ok thank you! I wanted to create the ticket more of a question as I wasn't sure.

luarocks for NEovim plugins requires Lua 5.1, that is completely correct.

@folke thanks for a lot of you plugins!
I have a question, since Lazy supports now luarocks and especially on macOS with Homebrew<EMAIL_ADDRESS>is deprecated and needs workaround to work with newer version,
isn't enough luarocks --lua-version=5.1 even with newer version of Lua as you’re already using ?
https://github.com/folke/lazy.nvim/blob/ec95702ae617308df35f35ad93c469c86d47346f/lua/lazy/pkg/rockspec.lua#L167-L184

Yes, you need 5.1. This is the last time I'll answer this question.

As is explained in the healthcheck, you can just enable hererocks instead

In case it's helpful to anyone, mise can be used to install lua 5.1 (with luarocks):
mise plugins add lua
mise use -g<EMAIL_ADDRESS>
after which luarocks should be available from ~/.local/share/mise/installs/lua/5.1/luarocks/bin/luarocks and :checkhealth in neovim won't show any errors or warnings.

5.1 is on nix as well, if that's more your thing:
nix profile install nixpkgs#lua51Packages.lua
nix profile install nixpkgs#lua51Packages.luarocks

Naive question: any idea why it is locked to lua 5.1 ? Is it a neovim or a lazy thing ?

neovim thing :h lua-compat


Engine scaled wider than my monitor

Godot version
4.1
System information
Windows 11
Issue description
Very strange issue with my editor. I was testing a game and hit something on my bluetooth controller by mistake (Not sure if this was the cause). I don't know what happened but my editor is now way wider than my monitor so a lot or the editor is off-screen.. I don't know what to do about this. I've tried changing the size and monitor display and the editor settings and nothing helps.
I've even restarted my pc and reinstalling Godot and its still like this

Steps to reproduce
I have no idea...
It only seems to bug out on the project I was on but I don't know of any project settings that could have done this.
Minimal reproduction project
No idea

Someone in discord told me to delete all of the text in the project.godot file. This worked. Still zero idea how this happened...

Someone in discord told me to delete all of the text in the project.godot file. This worked. Still zero idea how this happened...

In the future, please post the contents of project.godot here before removing it.

I thought that all of that info looked fine but I guess that wasn't the case.... it happened again. This time I was changing my game window to be large and shrunk down, which was working fine, but then I tried to make it a little taller and the scaling issue came back. Hers is the project.godot content:
`; Engine configuration file.
; It's best edited using the editor UI and not directly,
; since the parameters that go here are not all obvious.
;
; Format:
;   [section] ; section goes between []
;   param=value ; assign values to parameters
config_version=5
[application]
config/name="Dungeon Strikers"
run/main_scene="res://game.tscn"
config/features=PackedStringArray("4.1")
[autoload]
Globals="*res://globals.gd"
GameManager="*res://game_manager.gd"
[display]
window/size/viewport_width=5120
window/size/viewport_height=3072
window/size/window_width_override=1024
window/size/window_height_override=614
window/stretch/mode="canvas_items"
[gui]
theme/custom="res://Scenes/UI/src/ui_theme.tres"
theme/custom_font="res://Scenes/UI/src/light_pixel-7.ttf"
[input]
LEFT={
"deadzone": 0.5,
"events": [Object(InputEventKey,"resource_local_to_scene":false,"resource_name":"","device":0,"window_id":0,"alt_pressed":false,"shift_pressed":false,"ctrl_pressed":false,"meta_pressed":false,"pressed":false,"keycode":0,"physical_keycode":4194319,"key_label":0,"unicode":0,"echo":false,"script":null)
, Object(InputEventKey,"resource_local_to_scene":false,"resource_name":"","device":-1,"window_id":0,"alt_pressed":false,"shift_pressed":false,"ctrl_pressed":false,"meta_pressed":false,"pressed":false,"keycode":0,"physical_keycode":65,"key_label":0,"unicode":65,"echo":false,"script":null)
, Object(InputEventJoypadMotion,"resource_local_to_scene":false,"resource_name":"","device":-1,"axis":0,"axis_value":-1.0,"script":null)
]
}
RIGHT={
"deadzone": 0.5,
"events": [Object(InputEventKey,"resource_local_to_scene":false,"resource_name":"","device":0,"window_id":0,"alt_pressed":false,"shift_pressed":false,"ctrl_pressed":false,"meta_pressed":false,"pressed":false,"keycode":0,"physical_keycode":4194321,"key_label":0,"unicode":0,"echo":false,"script":null)
, Object(InputEventKey,"resource_local_to_scene":false,"resource_name":"","device":-1,"window_id":0,"alt_pressed":false,"shift_pressed":false,"ctrl_pressed":false,"meta_pressed":false,"pressed":false,"keycode":0,"physical_keycode":68,"key_label":0,"unicode":68,"echo":false,"script":null)
, Object(InputEventJoypadMotion,"resource_local_to_scene":false,"resource_name":"","device":-1,"axis":0,"axis_value":1.0,"script":null)
]
}
UP={
"deadzone": 0.5,
"events": [Object(InputEventKey,"resource_local_to_scene":false,"resource_name":"","device":0,"window_id":0,"alt_pressed":false,"shift_pressed":false,"ctrl_pressed":false,"meta_pressed":false,"pressed":false,"keycode":0,"physical_keycode":4194320,"key_label":0,"unicode":0,"echo":false,"script":null)
, Object(InputEventKey,"resource_local_to_scene":false,"resource_name":"","device":-1,"window_id":0,"alt_pressed":false,"shift_pressed":false,"ctrl_pressed":false,"meta_pressed":false,"pressed":false,"keycode":0,"physical_keycode":87,"key_label":0,"unicode":87,"echo":false,"script":null)
, Object(InputEventJoypadMotion,"resource_local_to_scene":false,"resource_name":"","device":-1,"axis":1,"axis_value":-1.0,"script":null)
]
}
DOWN={
"deadzone": 0.5,
"events": [Object(InputEventKey,"resource_local_to_scene":false,"resource_name":"","device":0,"window_id":0,"alt_pressed":false,"shift_pressed":false,"ctrl_pressed":false,"meta_pressed":false,"pressed":false,"keycode":0,"physical_keycode":4194322,"key_label":0,"unicode":0,"echo":false,"script":null)
, Object(InputEventKey,"resource_local_to_scene":false,"resource_name":"","device":-1,"window_id":0,"alt_pressed":false,"shift_pressed":false,"ctrl_pressed":false,"meta_pressed":false,"pressed":false,"keycode":0,"physical_keycode":83,"key_label":0,"unicode":83,"echo":false,"script":null)
, Object(InputEventJoypadMotion,"resource_local_to_scene":false,"resource_name":"","device":-1,"axis":1,"axis_value":1.0,"script":null)
]
}
AIM_LEFT={
"deadzone": 0.5,
"events": [Object(InputEventJoypadMotion,"resource_local_to_scene":false,"resource_name":"","device":-1,"axis":2,"axis_value":-1.0,"script":null)
]
}
AIM_RIGHT={
"deadzone": 0.5,
"events": [Object(InputEventJoypadMotion,"resource_local_to_scene":false,"resource_name":"","device":-1,"axis":2,"axis_value":1.0,"script":null)
]
}
AIM_UP={
"deadzone": 0.5,
"events": [Object(InputEventJoypadMotion,"resource_local_to_scene":false,"resource_name":"","device":-1,"axis":3,"axis_value":-1.0,"script":null)
]
}
AIM_DOWN={
"deadzone": 0.5,
"events": [Object(InputEventJoypadMotion,"resource_local_to_scene":false,"resource_name":"","device":-1,"axis":3,"axis_value":1.0,"script":null)
]
}
Attack={
"deadzone": 0.5,
"events": [Object(InputEventMouseButton,"resource_local_to_scene":false,"resource_name":"","device":-1,"window_id":0,"alt_pressed":false,"shift_pressed":false,"ctrl_pressed":false,"meta_pressed":false,"button_mask":0,"position":Vector2(0, 0),"global_position":Vector2(0, 0),"factor":1.0,"button_index":1,"canceled":false,"pressed":false,"double_click":false,"script":null)
]
}
`

Am working on a project with a team, and we've noticed this issue comes into play when we set the custom theme, as it appears you have this as well, so perhaps its an issue with the custom theme loader interacting with the editor for some reason?

Am working on a project with a team, and we've noticed this issue comes into play when we set the custom theme for the project, as it appears you have this as well, so perhaps its an issue with the custom theme loader interacting with the editor for some reason?

Indeed, I noticed last night, through process of elimination, that this is somehow tied to the custom project theme. If I use the theme individually on my components, everything is fine.

Please upload an MRP with a theme resource that you think causes this issue.

Please upload an MRP with a theme resource that you think causes this issue.

I'm not really sure how to reproduce this. I've made themes in similar ways before and have never seen this issue. I was also using this theme for a while before the issue presented itself and only later realized that removing the theme from the project settings seemed to fix it.

I'm not sure about the editor getting too wide, but the issue with the scene tabs getting so tall, as demonstrated on the screenshot in the OP, was reported before and the cause of it should be fixed in 4.2.
Can you somehow test your setup there?

I'm not sure about the editor getting too wide, but the issue with the scene tabs getting so tall, as demonstrated on the screenshot in the OP, was reported before and the cause of it should be fixed in 4.2.
Can you somehow test your setup there?

I've been meaning to give 4.2 a try. Should have some time this weekend


Release new version on cocoapods

Last version on cocoapods is from 24 march 2014. There are a lot of changes since this date.
Please, submit new release to cocoapods.

You can feel free to specify last commit from github for your classy pod. https://guides.cocoapods.org/using/the-podfile.html

@belkevich v0.2.6 is now available.


[kwokctl] Support port exposure for controller-port

What type of PR is this?
/kind feature
What this PR does / why we need it:
Exposes port on host when flag or env variable is specified.
Which issue(s) this PR fixes:
Fixes controller-port for #261
Special notes for your reviewer:

[x] controller-port
[ ] etcd-port
[ ] kube-controller-manager-port
[ ] kube-scheduler-port

Does this PR introduce a user-facing change?

TODO

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

TODO

/ok-to-test

Squash the commits

Thank you so much for the reviews!


GIT CLONE ISSUE

while executing game of life in jenkins .git is not cloning the repo .it is throwing timeout error

Can you switch as jenkins user & execute git clone manually & share results

Duplicate #141


Fixed client tests

Now client tests compare between response and entire HTML file #107

Nice work

@Omeramsc could this get merged? @Yarboa  approved

@Omeramsc could this get merged? @Yarboa  approved

????@Yarboa @Omeramsc


Can't create azure cloud cred  error : could not find tenant ID

Rancher Server Setup

Rancher version: 2.6.5
Installation option (Docker install/Helm Chart): helm chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): k3s v1.23.6+k3s1

cred info is correct by test
POST /meta/aksCheckCredentials
get response
{"error":"could not find tenant ID: Request failed: subscriptions.Client#Get: Failure sending request: StatusCode=0 -- Original Error: context deadline exceeded"}

After reading the code , I found it  before sending request , rancher will set context.WithTimeout
Finally I solved it by  changing the system time zone to my local zone, default is UTC.
And you must reboot  , just restart rancher is not work.
I don't know this is a bug for rancher  or azure sdk

And I also found that ,  the Environment field would not be handle


Default fail if first resource fails to load

Fix NPE in MapConfig

archaius-pull-requests #129 FAILURE
Looks like there's a problem with this pull request


Create an organization

Create an organization where to hold both prebuild and prebuild-install projects.

+-0 from me

No strong opinion from me but an organization could centralize all prebuild related projects. Adding some hints to every useful repository regarding the prebuild project in the README would do it also, because I found https://github.com/juliangruber/prebuild-ci today that is super useful, because I don't own a mac and OSX VMs are not that straightforward :)

+1 for organization, current repositories I know about:
https://github.com/mafintosh/prebuild
https://github.com/mafintosh/prebuild-install
https://github.com/juliangruber/prebuild-ci
https://github.com/mafintosh/prebuildify
https://github.com/mafintosh/node-gyp-build

I'm okay moving stuff to an org if people want it as long as we keep things simple. Is that something I have to setup?

Is that something I have to setup? (github noob)

That's only create an organization in the same link to create a new repo, and transfer the repos to the organization from their settings tab. Don't doubt to ask for help, I have done it several times :-)

I'm okay moving stuff to an org if people want it as long as we keep things simple. Is that something I have to setup? (github noob)

You or someone else. There's functionality in github to transfer repositories which is handy if you want to keep issue/pr history etc (repo settings page)

I have just created the organization. @mafintosh, I have just send you an invitation to it as owner of the organization, just accept it and later you'll only need to go to each one of the projects an transfer the ownership of the projects to the organization, on the "settings" tab. @juliangruber, I have also send you an invitation so you can also transfer your prebuild-ci repo.

1 of 5 repositories moved, not big progress here :)

1 of 5 repositories moved, not big progress here :)

We can continue discussion while that :-) What about a logo? ;-)

Would be cool to see some progress here :)
BTW I just set up prebuild , prebuild-install  and prebuild-ci in my project. It was super easy and first try :ok_hand:


Improve gem checksum mismatch error message

Improve gem checksum mismatch error message by telling users how to resolve it.
Old message:
The checksum for the downloaded `rack-1.0.0.gem` did not match the checksum given by the API. This means that the contents of the gem appear to be different from what was uploaded, and could be an indicator of a security issue.
(The expected SHA256 checksum was "abababababababababababababababababababababab", but the checksum for the downloaded gem was "BR6Oc6Gqnq93u1aIVX4m6DvTHaFgFxdYaLUfa4ekJKI=".)
Bundler cannot continue installing rack (1.0.0).

New message:
Bundler cannot continue installing rack (1.0.0).
The checksum for the downloaded `rack-1.0.0.gem` does not match the checksum given by the server. This means the contents of the downloaded gem is different from what was uploaded to the server, and could be a potential security issue.

To resolve this issue:
1. delete the downloaded gem located at: `full-path/gems/rack-1.0.0/rack-1.0.0.gem`
2. run `bundle install`

If you wish to continue installing the downloaded gem, and are certain it does not pose a security issue despite the mismatching checksum, do the following:
1. run `bundle config disable.checksum_validaiton true` to turn off checksum verification
2. run `bundle install`

(More info: The expected SHA256 checksum was "abababababababababababababababababababababab", but the checksum for the downloaded gem was "PbfaoemSetv76QdcxuoP0ggZ0TZhMELlMMWURJoX+dw=".)

Closes #5075

@indirect r?

@olleolleolle Good catch! Thanks.

Updated PR with typo fix and rebased to master.

@bundlerbot r+


Update Tuple.values return object

Right now Tuple.values return and array of values. Chaise apps have to check whether each value is HTML with Tuple.isHTML for display. Update Tuple.values to return an array of {value, isHTML} objects.

Let's not focus on this at the moment though.

@hongsudt can we all discuss this?

Is the isHTML flag possibly different for different tuples of the same relation (reference)? Then I could see it might need to be on the tuple and not on the column definition.

I took a look at where isHTML is assigned. It is essentially a function of the column type (is col type is markdown, ishtml is true) with the exception that if the tuple value is empty or null then ishtml is false. I don't understand why that exception is important. This really seems like a function that belongs in the Column object.

Would be a nice time to change it to isMarkdown if we're refactoring...


Cannot install iOS app

What App Center service does this affect?
iOS app distribution
Describe the bug
All devices are provisioned (green) and a release has been prepared but the testers cannot install the build.
There is no install button available for the testers, only a "GET" button. Once the tester clicks GET he gets an error "Oops,there was a problem building the app".
Automatic device management is turned on.
To Reproduce
Steps to reproduce the behavior:

As a tester select a release
Click GET

Expected behavior
The app should be downloaded on the device
Screenshots

iPad (please complete the following information):

Device: iPad
OS: iOS 12.4
Browser Safari

Same issue here 😞

The problem was that Apple updated the format of their UDIDs from their previous generations iPhones to the iPhone XS.
This issue is only happening on iPhone XR for me.

We believe we have identified the cause of this issue and are working on a fix that should be available within the next few hours 🙏🏼

@lumaxis thanks for the quick response. Our testers are now able to install the app :)

Cool, thanks for confirming @pgorzelany-objectivity ! I'll close this Issue.
@weslley39 If you're still experiencing a problem, please reply here or open a new Issue with details.

Hey @lumaxis, I am seeing this issue on an iPhone XR and two iPad Pros, both of which have the new style UDIDs (they are first devices with this style UDID I have tried). As you say the issue should be fixed, is there any way I can get more debug info?

Hi @lumaxis, could this have been resurfacing recently? I have two testers that can no longer install my app on their XS and X phones, while the rest with older devices have no problems. The testers with X-devices used to be able to do so, but now get the "Oops! There was a problem..." message. Since they are unable to start the app, I really don't have much more information.

Hi @klogeaage, did you ever find a resolution?  I am seeing the same issue with my testers now (the latest tester is using XS.

Yes I did. The problem was that my testers devices got deprovisioned because of an issue with my Apple developer account. This can happen if Apple update the legal agreement and want you to reconfirm that you accept it. They did that very recently.
To see if this is the case, go to the Distribute menu in AppCenter and select Group and then Devices. There your are likely to see that they are not all Provisioned. You will then need to login to your Apple developer account and accept their updated conditions. Then go back to AppCenter and run through the automatic provisioning process again. And then you should be good again - until next time. Hope this helps, otherwise write to Microsoft with the chat function in AppCenter and they will respond rather quickly.

I have the same problem today with an iPhone 8 Plus running iOS 14.3.
Is there a way to see logs on server side ?

I have the same problem today with an iPhone 8 Plus running iOS 14.3.
Is there a way to see logs on server side ?

I have solved it by clearing the browser cache from the Settings app.

I have solved it by clearing the browser cache from the Settings app.

Same here with iphone 11. Any Fix ?

Same here with iphone 11. Any Fix ?

Same problem, iOS 14.4 on iPhone 12 Pro Max emulator.

Same problem, iPhone SE (2020), iOS 14.4.2, using a private tab in Safari doesn't help.

Encountering this same problem with an iPhone XR, iOS 14.6

We ended up migrating away from AppCenter on iOS and instead just push our builds directly to TestFlight (we build on Azure Pipelines, so this is using the Azure App Store extension).
Feels like there are so many moving parts to iOS App Center and I was constantly battling random issues like this, expired tokens etc. With TestFlight, you remove a lot of those moving pieces and can authenticate for uploading to it with an api token that never expires.

I missed being provisioned. If I remember correctly, somebody needed to provision me in the App Center settings, then another build was needed to be published and then I was able to download/install app from the App Center on my iPhone.

any fix on this ?

Still experiencing this. iOS 15.5 on iPhone 8 plus

There is a fix for this issue as mentioned ealier. Delete the safari cache, history and website data from the settings. Close all tabs and the issue should be solved. It worked for me anyway.


Require async/await usage in templates

The current async mode happily allows coroutines to be awaited without requiring the await keyword. Whilst this is nice, it is actually quite a confusing and a non-obvious behavior. In addition it doesn't always work, for example {% if coroutine %}, and I'm not sure {% async for ... or {% async with ... work. (Edit: The if statement does work, I'm unsure about async for or async with)
I propose that templating engine understand and require the usage of the async and await keywords dropping the current support for non awaited coroutines.
It would also be nice if the engine did not use any asyncio features so as to be event loop agnostic.

Based on the docs, the intention seems to be that the template designer doesn't need to understand what type of function was passed, they could continue to write templates as they always had. Whether this has actually been beneficial is impossible to measure.
The main benefit I see is a sort of re-wording of that. By not requiring the await keyword, you don't have to care if your templates will be rendered in an async environment or not. For example, a Flask extension could provide a blueprint with some templates that loop over a database query, and they'd continue to work even if the project using the extension was using an async query library.
I can envision making enable_async accept the value "strict" instead of just True. This would enable async behavior but the compiler wouldn't output the auto_await wrapper. Instead, a new await token and node would be added to tell the compiler to output the await keyword. This would probably be more performant since the wrapper wouldn't be called on literally everything, but would not be as portable. The compiler could skip the await in sync mode, but this wouldn't be completely equivalent to the current behavior, as the template author would have to decide what would and would not have to be async in async mode.

As to using asyncio features, I'm not clear what we'd have to do not to, but I'm open to it. It looks like all it's used for right now is to get an event loop when patching some functions.

This also appears to be a blocker for async support in aiohttp-jinja2:
https://github.com/aio-libs/aiohttp-jinja2/pull/154

I think an additional "strict" mode is a better solution, as I can see the value in the original intention - although I personally would like to avoid this.
I'm also not sure if asyncio features are required, but aiming to avoid them would certainly help support other event loops.

I'm also in favour of adding explicit/strict mode, at least as an option. Perhaps someone maintaining a library with templates might think differently, but as far as your own code where you control both front-end and back-end is concerned, being explicit with await calls is significantly better than being implicit.

@nirvana-msu It sounds like you've misunderstood the strict mode I'm proposing. It would not add or require the await keyword in templates, it would always generate them behind the scenes when compiling the templates. That makes rendering more efficient when you can guarantee everything will be async.

@davidism indeed - I misinterpreted what "new await token" meant. It feels to me though that actually supporting await and async for within the templating language itself would have been the best design - otherwise you end up with a kind of "implicit" concurrency as opposed to asyncio philosophy of "explicit" concurrency / context switching. Not having control of when you await a coroutine can significantly complicate implementation in certain [more complex] situations (say, what if you need to pass a coroutine / async generator as an argument to macro.. I believe in current implementation you have to wrap it in another method, otherwise it would be awaited too early.. etc).

Using keywords does nothing for us now, as we still continue supporting the current behavior. Requiring it also brings the problems with Python's async into Jinja's syntax too, where it becomes viral and no existing template is reusable, even though nothing changed about what it's rendering or what variables are passed to it.
The strict mode makes the keyword explicit, in the compiled code. There's no reason to require writing async everywhere in that case because it's the default already.


Improve grammar and paragraph structure in documentation

Description
Fixes #2573 @Madoshakalaka maybe you can test the new JetBrains templates and review them
Fixes #2180, i.e. https://github.com/yewstack/yew/pull/2178#discussion_r754165481 (the offending sentence has been removed from the docs. It shall never be seen again. I think I know what it was meant to document, but I'm not sure if that "feature" is intended behaviour at this point)
This also slightly changes the keyed_list example. According to my tests, it did not actually perf-test the time it took for individual renders to happen. This now reports the time it takes from an initial view -> rendered of the wrapper class, which should be more reliable. To see that the current way is absurd, add a few thousand items to the live example and be surprised that it reports <100ms render times even as the browser visibly lags and stops to a crawl.
Checklist

[x] I have run cargo make pr-flow
[x] I have reviewed my own code

I was a bit confused when it required a Default trait property when rendered without explicit props

@Madoshakalaka You might be misremembering, start_app requires COMP::Properties: Default already in 0.19. Thanks for taking the time to try out the macros.

Remove use_<hook> page and instead use API docs for those. We shouldn't be documenting the API in the website1

I'll leave that for a future PR. I think it would be nice to have the rust docs for master linked here, instead of the rust docs for the most-recently deployed version. That's a bit more effort than I can spend right now.

Remove use_<hook> page and instead use API docs for those. We shouldn't be documenting the API in the website1

I'll leave that for a future PR. I think it would be nice to have the rust docs for master linked here, instead of the rust docs for the most-recently deployed version. That's a bit more effort than I can spend right now.

That's fine. I'll do that soon
I'm going to merge it now. If any docs changes are wanted later, those can come in separate PRs


expand the list for the "hall of fame"---example/targets

[ ]  synthetic examples that are challenging to sample

[x] Banana
[ ] 25 Guassian mixture
[x] warped Gaussian
[x] neal's funnel

Please suggested more interesting synthetic distributions for sampling!

This is an idle thought that might be cool, could we sample from the Datasaurus Dozen?

This is an idle thought that might be cool, could we sample from the Datasaurus Dozen?

This looks fun! I'm keeping this link to the dataset for reference: https://github.com/jumpingrivers/datasauRus


Build and use custom nginx container

Proposed changes
Replace the publicly available nginx image with a custom nginx image.
Problem: Using the publicly available nginx image requires users to create ConfigMaps for the nginx.conf file and the njs module and mount them to the NKG Pod as volumes. This pattern is not extensible and adds extra steps for developers and users. Additionally, an init container is required in order to set up the nginx config environment.
Solution: Build and use a custom nginx container. The nginx.conf and njs module are now baked into the nginx image. This eliminates the need for ConfigMaps. The config directories /etc/nginx/conf.d and /etc/nginx/secrets are created as volumes and mounted to the Pod with a group ID 1001. This allows the control plane to write to the directories and nginx to read from them. Both the nginx and nginx-gateway processes run under group ID 1001 but have different user IDs (101 and 102). The nginx container now runs as user 101 instead of root.
Testing: Verified conformance tests pass and that the directory permissions are correct:
/etc/nginx $ whoami
nginx
/etc/nginx $ ls -l
total 36
drwxrwsrwx    2 root     1001          4096 Aug  4 16:36 conf.d
-rw-r--r--    1 nginx    1001          1077 Jun 13 17:34 fastcgi.conf
-rw-r--r--    1 nginx    1001          1007 Jun 13 17:34 fastcgi_params
-rw-r--r--    1 nginx    1001          5349 Jun 13 17:34 mime.types
lrwxrwxrwx    1 nginx    1001            22 Jun 15 00:20 modules -> /usr/lib/nginx/modules
-rw-r--r--    1 nginx    1001           440 Aug  3 21:23 nginx.conf
-rw-r--r--    1 nginx    1001           636 Jun 13 17:34 scgi_params
drwxrwsrwx    2 root     1001          4096 Aug  4 16:36 secrets
-rw-r--r--    1 nginx    1001           664 Jun 13 17:34 uwsgi_params

Note
Marking this as draft because I'm still working on the pipeline steps and have not updated the architecture doc yet.

Closes #798
Checklist
Before creating a PR, run through this checklist and mark each as complete.

[x] I have read the CONTRIBUTING doc
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have checked that all unit tests pass after adding my changes
[ ] I have updated necessary documentation
[x] I have rebased my branch onto main
[x] I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

The conformance CI file needs to be updated with the new container, as the conformance tests aren't running, but otherwise looks great! 🚀

Thanks! Just updated the conformance CI file and the tests are now passing. Not sure if there's a better way to build and reference the two images so LMK what you think!


Fix bound listener

Explanation About What Code Achieves:

Fixes #97

Steps To Test:

Construct a test page with more than one frappe-charts on it
Remove the charts
Resize the window
Should not see any error in JS console about can't removeChild

TODOs:

None

@pratu16x7 Do I need to run rollup locally and commit those changes too? A CONTRIBUTING.md would be good to have.

Pull Request Test Coverage Report for Build 49

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 38.158%

Totals

Change from base Build 47:
0.0%

Covered Lines:
29

Relevant Lines:
62

💛  - Coveralls

@t47io Would you mind rebasing again? Looks like when we keep the policy to update generated files. merging a separate PR is not autonomous to the others, and all others have to be rebased whenever one is merged.
Ideally though, generated files shouldn't be committed, but we have no other way at present it seems.

Rebased. I'd also recommend to consider making a patch release to have it available sooner.

Still an issue at 25 March 2019.

@pratu16x7 please release it. Why do you have features stuck on the develop branch for more than a year? :/


Moving PAT token secret out of web service parameters

We don't want to pass this secret around.
Fixes #113 (Make PAT tokens more secure)

Pull Request Test Coverage Report for Build 739002438

81 of 83 (97.59%)  changed or added relevant lines in 13 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.03%) to 90.645%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/DevOpsMetrics.Service/Controllers/ChangeFailureRateController.cs
2
4
50.0%

Files with Coverage Reduction
New Missed Lines
%

src/DevOpsMetrics.Core/DataAccess/TableStorage/AzureTableStorageDA.cs
3
95.16%

Totals

Change from base Build 738513567:
-0.03%

Covered Lines:
1810

Relevant Lines:
1972

💛  - Coveralls


Fixes issues with some wtfs

Fixes:
"Why you should use semicolons" - example
"Double dot" - explanation

Line 2013 should be fixed for the double dot example also

This was because of prettier. We should add prettier-ignore statements for every block of code.


[PE-D][Tester A] Unable to select event to be removed when dealing with events of the same name

There isn't a way for me to remove a specific event when dealing with events with the same name but different time/day slots.
The rmschedule command removes in the order of input of the first event to the last event, which might be a problem for users who wants to remove only the last event.

Labels: type.FeatureFlaw severity.High
original: WinSheng1/ped#16

Shouldn't be high severity imo.

Resolved by updating UG


Report errors in normalize_url method

This should be reported to Sentry with a custom capture_message, making it easier to contact blog authors.

Implemented via 6223163.


AspNetCore.App 2.1 not installing latest patch version

I think this might be the same issue as #942 but I'm not 100% sure...
I removed the version from package reference as stated in the ASP.NET Core 2.0 to 2.1 upgrade guide but when I look in my project -> dependencies -> NuGet I see Microsoft.AspNetCore.App (2.1.1) and I have the 2.1.603 SDK installed.  Shouldn't I be seeing (2.1.10)?

Remove the "Version" attribute on the package reference to Microsoft.AspNetCore.App. Projects which use  do not need to set the version. The version will be implied by the target framework and selected to best match the way ASP.NET Core 2.1 works. (See below for more information.)

Workaround
Once I added the version number to the package I got the latest version under my project dependencies
<PackageReference Include="Microsoft.AspNetCore.App" Version="2.1.10"/>

Questions

The version number shouldn't be specified in the package reference, right?  I'm not supposed to have to do that, right?
It's supposed to automatically find that SDK version installed on my machine, right?
Was that the correct workaround?

https://stackoverflow.com/a/50977224/185123

Are you still seeing issues with this?

I haven't tried putting in back, I can but what would have changed to fix this?

Just tried w/ VS 2019 Preview (16.2 Preview 4), same behavior.  @dseefeld


Websocket SSL ProxyPass not working

I have apache server in EC2 instance and my Ratchet Server is Configure in the Port 8080. In HTTP it works fine, but after configure SSL it not worked and i search error and place the proxy coding in my httpd conf. Still issue not solved. Please help me in solving this issue.
My Websocket proxy coding
HTTPD.conf
`LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_wstunnel_module modules/mod_proxy_wstunnel.so
LoadModule ssl_module modules/mod_ssl.so
ProxyRequests off
SSLProxyEngine on
SSLProxyVerify none
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
ProxyPass /wss2/ wss://<IP_ADDRESS>:8080
ProxyPassReverse /wss2/ wss://<IP_ADDRESS>:8080
`
Google chrome show console log - WebSocket connection to 'wss://<IP_ADDRESS>/wss2/' failed: Error in connection establishment: net::ERR_INSECURE_RESPONSE

Please help me in solve the issue and make the websocket working in SSL.
Thank you

I have the same issue. Anyone?

I have same issue

Hello,
I change my port from 8080 to 8888, also allowed permission for 8888 port in your security group of ec2 server
`LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_wstunnel_module modules/mod_proxy_wstunnel.so
LoadModule ssl_module modules/mod_ssl.so
ProxyRequests off
SSLProxyEngine on
SSLProxyVerify none
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
ProxyPass /wss2/ ws://www.yourdomain.com:8888`
For Establishing Socket Connection:-
$server = IoServer::factory(new HttpServer(new WsServer(new Chat)), 8888);
Use this url for connection establishment
www.yourdomain.com/wss2/
The above code worked for me

I have same issue.
Can anybody help me out?
Ratchet works fine with http, but on ssl it gives error:
Error: Failed to execute 'send' on 'WebSocket': Still in CONNECTING state.
at Connection.sendMsg (Connection.js:44)

I'm also facing the same issue with chrome, there is a problem with either your certs or with chrome accepting them


Configure TFX endpoint

Set up a Tensorflow Extended endpoint for internal use and as an API bridge to other team(s)

Splitting this issue up into one issue per component for ease of tracking progress.


Shared Solr search links get lost in historic conversations

Proxy for https://github.com/assistify/smarti/issues/8

Duplicate of #100


PR Comments generated by SonarCloud?

Working through this tutorial I can see that it's possible to get SonarCloud generated comments in your pull requests. I'm not getting this behaviour, do you know that this is specific to msbuild and .NET projects? I hypothesize that because we use a standalone scanner in our SonarCloud analysis it may be different.
Link to tutorial

@peeter-piegaze-sonarsource or @duncanp-sonar it looks like you are contributors for this part of the document, do you have any idea?

@JamesEarle the SonarSource community forum is the best place to ask for help.
I believe PR commenting should work for all supported languages. However, if you are analysing C# or VB.NET code you need to use the SonarScanner for .NET for any type of analysis (i.e. "normal" CI analysis or PR analysis).

Thanks @duncanp-sonar  I will look there. The code is Python actually so we want to use the standalone scanner, if I understand correctly


Rails 7

Pull requests into Cypress require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[ ] This pull request describes why these changes were made.
[ ] Internal ticket for this PR:
[ ] Internal ticket links to this PR
[ ] Code diff has been done and been reviewed
[ ] Tests are included and test edge cases
[ ] Tests have been run locally and pass

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

app/controllers/measures_controller.rb
lib/api.rb
lib/cypress.rb
lib/cypress/demographics_randomizer.rb
lib/ext/provider.rb
test/factories/providers.rb


Bjorncs/detect reindexing config change

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

Laggy github + laggy brain = two differing reviews.

@jonmv PTAL

@jonmv PTAL


Send chat action automatically

Sending chat action automatically by calling any send... command. for example the following command send typing... chat action:
$result = Request::sendMessage([
    'chat_id' => $chat_id,
   'sendChatAction' => true,
    'text'   => 'test',
]);

@smoqadam I like this idea!
We'd have to establish a safe way of passing the value though, as the $data array is what gets sent to the Telegram API. So we'd either have to make sure that it is a key that will never be used by Telegram, or (and maybe better), have an extra parameter for $extras like this.
@php-telegram-bot/developers
What do you guys think about this?
Do you use the chat actions often enough to make this a necessary / 'makes sense' addition?

As API says it should only be used if bot is about to do something that is gonna take some time, it should definitely not be default behaviour.

@jacklul It isn't default! That's why it would be passed as an extra parameter :+1:

@jacklul @noplanman
you mean like this?
Request::sendMessage([
    'chat_id' => $chat->getId(),
    'text' => 'test'
], ['sendChatActiob'=>true]);

@chuv1 I like things that make it easier for the user, but I agree with you that it's a question of adding a single line to send the chat action separately.
I do see the advantage of the parameter though, to easily define a long operation with a boolean and have the chat action be managed automatically, without any extra if or anything.
@smoqadam Yes, something like that was in my head. Haven't checked to see if that makes complete sense, but it should do the trick i think.
Before coding more, let's first establish that it's something that would be merged in the first place :blush:

Actually, @chuv1 is right.

Aah... Of course... I read his comment wrongly.
Of course it should be sent as the request comes in, not out.

So all ok to close this then?
@smoqadam Thanks a lot for the idea though! Keep them coming :+1:

@noplanman no problem.
I'm glad I to be helpful if I can


Sam's their

Sam refers to player as their in the scene with Heller. I don't feel this is right, if the player has chosen a gender and narrative branches are in place.

Game Version
<IP_ADDRESS>
Language
English (EN)
New Game
Yes
Reproduction Steps
just go do the mission.

Needs more information. What mission, what scene, what location

Marked invalid due to the lack of info

Many games use "their" instead of she or he due to needing more voice lines recorded. This is not a bug and how many games reduce the number of voice lines needed for a game.


Fix that typo in the usage message

This PR aims to fix a possible typing error in the usage message displayed upon invoking imgur-screenshot --help. It does so by replacing the word isntead with instead, which seems to be what the author of the message meant. (It is spelled correctly in the readme)
This commit is essential for the survival of this project because proper spelling implies a professional distributed cloud Quality Assurance team, which helps users build confidence in this product.
Thanks!

Hello,
sorry for not getting back to your request earlier, our team was recently focusing on streaming services in our telecommunication department. We have received and reviewed your request and after consulting our QA team have come to the conclusion that this is indeed a critical problem in this part of our software.
Although the word was spelled correctly in the readme file, as you have noticed, it was not spelled correctly in the main software's core code base. This, in retrospect, had the effect of users being confused by messages displayed to them with an improperly spelled word.
We spoke to our language specialists and have indeed identified the problem to be Literallie a typing error. It is unimaginable what a lose in spread, trust, and reputation this has probably caused.
The whole imgur-screenshot team would like to thank you for bringing this issue to us and therefore improving our product. Our security team has reviewed offered a positive summary on your proposed changes. Thus we will proceed by soon merging your pull request into the main code of our product and reward you with this cookie.
Thanks again for improving our product and thus keeping up user satisfaction.

:+1:


Allow flexible channel priority

Problem description
I'm trying to get introduce Pixi at the company I work at, when I ran into this issue compared to our old conda setup.
Basically we have our own internal conda channels with custom versions of some conda packages. Some projects depend on the custom version of those libraries, some depend on the upstream ones.
Pixi, according to the docs here, follows the behavior conda has with "strict channel priority" set.
We can work around it by setting the channel source on a per-package basis, but that won't scale for wider adoption.
Is there a plan to implement flexible channel priority in Pixi? Does the solver have this behavior and it's only a matter of exposing it in Pixi?

He @dp-alvarez
Do you build your custom channel on top of conda-forge?
This is a known request, the latest response is: https://github.com/prefix-dev/pixi/discussions/1029#discussioncomment-8862908.
With enough people wanting this, we probably need to give in at some point :wink:  Track it by giving a thumbs up! :+1:

Ooh I didn't that thread it as I only searched in issues, thanks for pointing it out.
We don't build it on top of conda-forge, that channel only has our own internal packages plus patched versions of some upstream libraries.

There is also some work ongoing in rattler, the underlying library: https://github.com/mamba-org/rattler/pull/598 :)

We don't build it on top of conda-forge, that channel only has our own internal packages plus patched versions of some upstream libraries.

Oh that is interesting. Are you building everything from scratch? Including all compilers etc?

Oh that is interesting. Are you building everything from scratch? Including all compilers etc?
Sadly it's nowhere that cool. We just build patched versions of libraries (pulling dependencies from conda-forge) and upload them to an internal conda channel.
When I said "we don't build it on top of conda-forge" I meant that the internal channel isn't a mirror of conda-forge + patched packages, it contains just our internal patched packages and nothing else.

@wolfv great to know there is already code underway for it, thanks for the link!

Just saw that the py-rattler PR is merged (https://github.com/mamba-org/rattler/pull/598). Would it be possible to expose the option in pixi now? :-)


Field for symptom still exists after deleting in edit

Can now add individual symptoms. However, if go to edit issue and delete an existing symptom (by unchecking it from the list), the bulleted field where it existed is still there. Needs fixing.

Would something like
symptom = Symptom.find_or_create_by(symptom_name: symptom_attribute["symptom_name"])

work better instead? 🤔


Bank Feed API description statementID vs statementId

The path parameter for the getStatement operation has a different name in the two places it is declared. In the clients we generate from this, the statementId parameter does not work as a result.
https://github.com/XeroAPI/Xero-OpenAPI/blob/master/xero_bankfeeds.yaml#L512
Expected Behavior

Code generates as expected - the defined path parameter gets inserted into the path template as expected.
Current Behavior

This fragment of generated code illustrates the problem:
        $resourcePath = '/Statements/{statementID}'; // <--- placeholder is not proper camelCase
...
            $resourcePath = str_replace(
                '{' . 'statementId' . '}', // <--- matching on camelCase
                ObjectSerializer::toPathValue($statementId),
                $resourcePath
            );

In this generated code, using a case-insensitive match should work around this issue, but there are a hundred other languages and tools that need this to be consistent.
Possible Solution

Change the statementID path template placeholder to statementId here:
https://github.com/XeroAPI/Xero-OpenAPI/blob/master/xero_bankfeeds.yaml#L512
Steps to Reproduce (for bugs)

Context

Your Environment

Version used:
Browser Name and version:
Operating System and version (desktop or mobile):
Link to your project:

Can do a PR if that helps. Just need to get some other work out the way first.

Resolved https://github.com/XeroAPI/Xero-OpenAPI/releases/tag/2.10.1


support folders in dbnames and prefix option

follow up for #1 which got closed by accident

:dancer:


KAFKA-9042: Auto infer external topic partitions in stream reset tool

https://issues.apache.org/jira/browse/KAFKA-9042
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

This Jira requires a KIP and this PR cannot be merged before a KIP was accepted.


Run upgrade to an specific tag

Hi, I've been looking documentation on how to run force upgrade to an specific function, but I couldn't find it. Seems like I always have to create a "latest" image too and always deploy from it. Is this correct? Or I can do a --force-upgrade and add the tag I want to be upgraded to?
Thanks.

Please check https://github.com/rancher/ui/pull/2319


Improving "Always start with pinning enforcement disabled" documentation section

Reading the documentation for Always start with pinning enforcement disabled section I cannot understand why I need to set kTSKEnforcePinning to NO.
Based on the source code, I see that the trust decision is marked as allowed when the previous flag is set to NO:
if (validationResult == TSKTrustEvaluationFailedNoMatchingPin)
{
    // Is pinning enforced?
    if ([domainConfig[kTSKEnforcePinning] boolValue] == YES)
    {
        // Yes - Block the connection
        finalTrustDecision = TSKTrustDecisionShouldBlockConnection;
    }
    else
    {
        finalTrustDecision = TSKTrustDecisionShouldAllowConnection;
    }
}

Based on this, why should I set that value as written in the documentation? Should I change it after? Setting to NO means not taking into account the pinning. Or am I missing something?
Thanks, Lorenzo

This sections says the following: "To avoid locking out too many users from your App when deploying SSL pinning for the first time". It's to avoid making a big mistake with your pinning configuration that bricks your app.


edpm-hardened-uefi improvements

README tweaks

Don't pip install edpm-image-builder, source the elements from the
current directory
Use :Z for the volume mount to extract the image, for correct SELinux
labelling

Remove networking specific elements and scripts
This is part of the effort to align this image with base images of
pre-provisioned nodes.

iptables removed, handled by edpm-ansible
51-enable-network-service, if this is still an issue it needs to be
handled in edpm-ansible anyway
openssh UseDNS no, not required in an EDPM environment
interface names, keep the same behaviour as the base image

Increase all small volumes to 300MiB
Recent mkfs.xfs now fails when volumes are smaller that 300MiB
(mkfs.xfs-6.1.0 on Fedora 38)
This change uses 300MiB as the smallest size for the small partitions.
Depends-On: https://github.com/openstack-k8s-operators/ci-framework/pull/324

recheck

recheck

recheck

@steveb
With depends-On the bmaas job is working correctly:-
https://logserver.rdoproject.org/7/7/7a4e01a428dfc0ec3f31edbe559d4720f62cd964/github-check/eib-crc-podified-edpm-baremetal/ccd5aa6/ci-framework-data/logs/edpm/pods/openstack/edpm-compute-provisionserver-openstackprovisionserver-c6bfknjg9-describe.txt
 Successfully pulled image "<IP_ADDRESS>:5001/edpm-hardened-uefi:7a4e01a428dfc0ec3f31edbe559d4720f62cd964"

The failure here is real and looks related to this patch, Job failed because we can't ssh to compute node
https://logserver.rdoproject.org/7/7/7a4e01a428dfc0ec3f31edbe559d4720f62cd964/github-check/eib-crc-podified-edpm-baremetal/ccd5aa6/ci-framework-data/logs/edpm/pods/openstack/dataplane-deployment-configure-network-edpm-compute-k4tt6-logs.txt
TASK [Gathering Facts] *********************************************************
task path: /runner/project/playbook.yaml:3
fatal: [edpm-compute-0]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: connect to host <IP_ADDRESS> port 22: No route to host", "unreachable": true}

Compute node got a wrong IP(got .90 not .100):-
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 52:54:00:5b:9c:de brd ff:ff:ff:ff:ff:ff
    altname enp1s0
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic noprefixroute eth0
       valid_lft 2512sec preferred_lft 2512sec
    inet6 fe80::5054:ff:fe5b:9cde/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

the interface name here is now eth0 we use enp1s0
https://github.com/openstack-k8s-operators/dataplane-operator/blob/main/config/samples/dataplane_v1beta1_openstackdataplane_baremetal_with_ipam.yaml#L33
edpm-compute-0 lib]# less /var/log/cloud-init.log  | grep 172.22
2023-07-02 06:36:08,369 - stages.py[DEBUG]: applying net config names for {'version': 1, 'config': [{'name': 'enp1s0', 'type': 'physical', 'subnets': [{'gateway': '<IP_ADDRESS>', 'netmask': '<IP_ADDRESS>', 'type': 'static', 'address': '<IP_ADDRESS>', 'ipv4': True}], 'mac_address': None}, {'address': ['<IP_ADDRESS>'], 'search': ['ctlplane.example.com', 'osptest.openstack.org'], 'type': 'nameserver'}]}

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 52:54:00:5b:9c:de brd ff:ff:ff:ff:ff:ff
    altname enp1s0
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic noprefixroute eth0
       valid_lft 2512sec preferred_lft 2512sec
    inet6 fe80::5054:ff:fe5b:9cde/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

Looks like removing stable-interface-names caused the issue.

eib-crc-podified-edpm-baremetal is green, could we merge it please?
https://review.rdoproject.org/zuul/buildset/b189eda3b6844b90adfb53ca669cc7e3

wondering if we want to enable automation to merge PRs according to results posted by CI.

wondering if we want to enable automation to merge PRs according to results posted by CI.

Yeah now that we have eib-crc-podified-edpm-baremetal. Plus requiring a / lgtm


Support #[ignore] attribute

Will re-add tests after #860 is merged
Introduced changes

support #[ignored] attribute
--ignored flag to run only ignored tests
--include-ignored flag to run all tests regardless if ignored

Checklist

[x] Linked relevant issue
[x] Updated relevant documentation
[ ] Added relevant tests
[x] Performed self-review of the code
[x] Added changes to CHANGELOG.md

Will re-add tests after #860 is merged

It's merged now, tests can be added. Though you need to rebase your changes, because refactor branch was updated.


Feature Request: camera snapshot

Would be nice to be able to get a snapshot, especially when motion has been detected

You can use https://www.home-assistant.io/integrations/camera/#service-snapshot


Using multiple pools in a virtualized deployment

I understand that a virtualized deployment does not support all selectors available since the pf - vf association is unknown. However, the section on Virtual Deployment Support states that we can use the common selector pciAddress.
If I have 4 pci and am using two networks, I would like to create two pools, one for each network. For example
      "resourceList": [
          {
              "resourceName": "sr1",
              "selectors": {
                  "vendors": ["8086"],
                  "devices": ["154c", "10ed"],
                  "drivers": ["vfio-pci"],
                  "pciAddresses": ["00:06.0","00:07.0"]
              }
          },
          {
              "resourceName": "sr2",
              "selectors": {
                  "vendors": ["8086"],
                  "devices": ["154c", "10ed"],
                  "drivers": ["vfio-pci"],
                  "pciAddresses": ["00:08.0","00:09.0"]
              }
          }

However, it seems that the pciAddress selector is not being used and all four pci addresses are being place into each pool.
W0712 19:26:43.105213 2131075 pciNetDevice.go:61] unable to get PF name "open /sys/bus/pci/devices/0000:00:06.0/net: no such file or directory"
I0712 19:26:43.105284 2131075 manager.go:220] discoverDevices(): device found: 0000:00:07.0 02 Intel Corporation Ethernet Virtual Function 700 Series
W0712 19:26:43.105329 2131075 pciNetDevice.go:61] unable to get PF name "open /sys/bus/pci/devices/0000:00:07.0/net: no such file or directory"
I0712 19:26:43.105390 2131075 manager.go:220] discoverDevices(): device found: 0000:00:08.0 02 Intel Corporation Ethernet Virtual Function 700 Series
W0712 19:26:43.105433 2131075 pciNetDevice.go:61] unable to get PF name "open /sys/bus/pci/devices/0000:00:08.0/net: no such file or directory"
I0712 19:26:43.105495 2131075 manager.go:220] discoverDevices(): device found: 0000:00:09.0 02 Intel Corporation Ethernet Virtual Function 700 Series
W0712 19:26:43.105542 2131075 pciNetDevice.go:61] unable to get PF name "open /sys/bus/pci/devices/0000:00:09.0/net: no such file or directory"
.....
I0712 19:26:43.105617 2131075 manager.go:112] Creating new ResourcePool: sr1
I0712 19:26:43.105625 2131075 factory.go:100] device added: [pciAddr: 0000:00:06.0, vendor: 8086, device: 154c, driver: vfio-pci]
I0712 19:26:43.105629 2131075 factory.go:100] device added: [pciAddr: 0000:00:07.0, vendor: 8086, device: 154c, driver: vfio-pci]
I0712 19:26:43.105631 2131075 factory.go:100] device added: [pciAddr: 0000:00:08.0, vendor: 8086, device: 154c, driver: vfio-pci]
I0712 19:26:43.105634 2131075 factory.go:100] device added: [pciAddr: 0000:00:09.0, vendor: 8086, device: 154c, driver: vfio-pci]
I0712 19:26:43.105643 2131075 manager.go:126] New resource server is created for sr1 ResourcePool
I0712 19:26:43.105648 2131075 manager.go:111]
I0712 19:26:43.105650 2131075 manager.go:112] Creating new ResourcePool: sr2
I0712 19:26:43.105657 2131075 factory.go:100] device added: [pciAddr: 0000:00:06.0, vendor: 8086, device: 154c, driver: vfio-pci]
I0712 19:26:43.105660 2131075 factory.go:100] device added: [pciAddr: 0000:00:07.0, vendor: 8086, device: 154c, driver: vfio-pci]
I0712 19:26:43.105663 2131075 factory.go:100] device added: [pciAddr: 0000:00:08.0, vendor: 8086, device: 154c, driver: vfio-pci]
I0712 19:26:43.105666 2131075 factory.go:100] device added: [pciAddr: 0000:00:09.0, vendor: 8086, device: 154c, driver: vfio-pci]
I0712 19:26:43.105671 2131075 manager.go:126] New resource server is created for sr2 ResourcePool

Is there a proper way to do this, or is using the pic address of the vf not supported?

Hi @bjeremy23 , this should work AFAIK. what version of device plugin are you using ? you need version V3.3 or newer

Ahh... I'm using 3.2... let me give 3.3 a try... thanks
From: Adrian Chiris @.>
Sent: Tuesday, July 13, 2021 10:25 AM
To: k8snetworkplumbingwg/sriov-network-device-plugin @.>
Cc: Jeremy Brown @.>; Mention @.>
Subject: Re: [k8snetworkplumbingwg/sriov-network-device-plugin] Using multiple pools in a virtualized deployment (#361)
Hi @bjeremy23https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbjeremy23&data=04|01|brownjer%40microsoft.com|7f5f68637b3348f13dc208d946126cdc|72f988bf86f141af91ab2d7cd011db47|1|0|637617867221809198|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=El1sdA7DojUHL0q4%2BMpFL5r24kOpOvFizxPARYrYZq0%3D&reserved=0 , this should work AFAIK. what version of device plugin are you using ? you need version v3.3 or newer

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fk8snetworkplumbingwg%2Fsriov-network-device-plugin%2Fissues%2F361%23issuecomment-879184624&data=04|01|brownjer%40microsoft.com|7f5f68637b3348f13dc208d946126cdc|72f988bf86f141af91ab2d7cd011db47|1|0|637617867221819184|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=R1k8v02SzkbVduli83PWUSNFJ8kJ5G61f8kDQZfwVWw%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAU2U2OQGE3QPEVZ5WQRCV53TXRLF7ANCNFSM5AJKGM4Q&data=04|01|brownjer%40microsoft.com|7f5f68637b3348f13dc208d946126cdc|72f988bf86f141af91ab2d7cd011db47|1|0|637617867221829179|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=2WDi7OqdrZO5Lode9gjKe6cqgr47JLI50z3zBEhPNbc%3D&reserved=0.

I tried v3.3 and actually it was a little worse results... now instead of all four pci in both pools... now no pci was in either.
Maybe I didn't communicate what I was wanting to do. The pci I was trying to use is for the VF. I just want two pools with the ability to put the VFs in either pool. Is that possible in a virtualized environment?

I tried v3.3 and actually it was a little worse results... now instead of all four pci in both pools... now no pci was in either.

You may want to try the full pci address ID in the config.json such as: 0000:00:06.0.
The device will only be selected when pciAddresses filter contains the entire device PCI ID.

Thanks for the response. However, that was actually already tried earlier. I did notice the particular config.json that I cut and pasted didn't have that though. Regardless, there was no difference. The outcome was the same.
It seems that the pciAddresses are only for pf devices? I'm not really sure what the difference then is between pciAddresses and rootDevices as a selector other than with rootDevices you can optionally choose the vf to join the pool?
From: zshi @.>
Sent: Tuesday, July 13, 2021 5:52 PM
To: k8snetworkplumbingwg/sriov-network-device-plugin @.>
Cc: Jeremy Brown @.>; Mention @.>
Subject: Re: [k8snetworkplumbingwg/sriov-network-device-plugin] Using multiple pools in a virtualized deployment (#361)
I tried v3.3 and actually it was a little worse results... now instead of all four pci in both pools... now no pci was in either.
You may want to try the full pci address ID in the config.json such as: 0000:00:06.0.
The device will only be selected when pciAddresses filter contains the entire device PCI ID.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fk8snetworkplumbingwg%2Fsriov-network-device-plugin%2Fissues%2F361%23issuecomment-879456563&data=04|01|brownjer%40microsoft.com|f7afed694bf0446d79ed08d94650c4a7|72f988bf86f141af91ab2d7cd011db47|1|0|637618134984578046|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=6BGN4Yg%2Bni%2BTBNLkTF1j61Wv3DH%2FfRSNf4ffgNkg5UE%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAU2U2OXZNONCFWI3QXOZZLTTXS7PPANCNFSM5AJKGM4Q&data=04|01|brownjer%40microsoft.com|f7afed694bf0446d79ed08d94650c4a7|72f988bf86f141af91ab2d7cd011db47|1|0|637618134984588038|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=s3eMlDsAvdgBQRAOh7B85oxs75b369P5PpGdqz8h2Vg%3D&reserved=0.

Zshi,
Good catch... yeah that was it. I actually thought I caught that earlier... but as luck would have it... I still made the same mistake.  But that was problem after I went to 3.3
Thanks again.

Maybe opportunity to validate the PCI address.
Seems your issue is fixed. Closing.


Only set automountServiceAccountToken to false in testpmd-related pods

It looks like https://github.com/openshift-kni/example-cnf/pull/74 caused https://issues.redhat.com/browse/CILAB-1603, and TRexConfig started to complain about service token not found, but this didn't happen, curiously, in the loadbalancer case.
Let's just use automountServiceAccountToken set to false in testpmd pods (testpmd-lb and testpmd operators), and removing the other cases, also testpmd-operator-controller-manager, which was added in the previous change by mistake.

CC @manurodriguez and @capolrik as CI Duty, I'm start running tests with direct mode and then with LB mode.

Change is ready, it's behaving as expected.

from change #76:

SUCCESS https://www.distributed-ci.io/jobs/3ffb92eb-51d3-4fc3-b573-7990982733ca/jobStates

Direct mode worked

from change #76:

SUCCESS https://www.distributed-ci.io/jobs/1f13c5d8-614e-4a95-a2c3-094d743523ea/jobStates

LB mode worked


for GKE launcher, add more detail on non-IAP process

in this section of the docs: https://www.kubeflow.org/docs/started/getting-started-gke/#deploy-kubeflow-on-gke-using-the-ui
consider describing how to connect via either setup path (either use IAP, or don't use IAP)
For the non-IAP path, the instructions could look something like what's in step 3 of this codelab:
https://codelabs.developers.google.com/codelabs/cloud-kubeflow-pipelines-gis/#2
(clicking on the cloud shell button in the launcher UI, doing the port forwarding, etc.)

/close

Fixed by https://github.com/kubeflow/website/pull/712


Make swizzled URLSession init method signature match the origin init method to avoid unexpected crash

Hi @kean, first of all, thank you for creating such a cool library!
After the integration using the swizzling approach, we've noticed that our app started to crash occasionally. Apparently, the crash reason was related to the fact that pust_init URLSession method signature didn't really match the original init method. The swizzled method had delegate defined as non-optional whereas the original method has it defined as optional. Since we're swizzling the init method for every instance of URLSession created after a call of URLSession.enableAutomaticRegistration() it may lead to a crash when nil passed as a delegate value.
This PR shall also fix #29

Thanks, @ivanlisovyi! I appreciate you taking your taking and fixing it.


added FTDI C232HM-DDHSL-0 to compatible usb id list

Add another valid usb vendor id / product id pair to ftdi backend.
Tested, at least jtag scanning works, so communication is probably ok.

bors r+

@Tiwalun I don`t think merging myself works. bors says permission denied

bors d+

bors r+


Updated dependencies to some newer versions to resolve security issues.

Pull Request Test Coverage Report for Build 98

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 96:
0.0%

Covered Lines:
296

Relevant Lines:
296

💛  - Coveralls


failures in Scala 2.12 community build

at e.g. https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/4307/ I'm seeing
[perfolation] [info] Date Formatting
[perfolation] [info] - should retrieve millisecond info *** FAILED ***
[perfolation] [info]   0 was not equal to -18000000 (DateFormatSpec.scala:14)
[perfolation] [info] - should retrieve seconds info
[perfolation] [info] - should retrieve minutes info
[perfolation] [info] - should retrieve hours info *** FAILED ***
[perfolation] [info]   21 was not equal to 16 (DateFormatSpec.scala:29)
[perfolation] [info] - should retrieve days info
[perfolation] [info] - should retrieve week info
[perfolation] [info] - should retrieve month info
[perfolation] [info] - should retrieve years info
[perfolation] [info] - should retrieve miscellaneous info *** FAILED ***
[perfolation] [info]   "[]00" was not equal to "[3]00" (DateFormatSpec.scala:66)
[perfolation] [info] - should format a date properly *** FAILED ***
[perfolation] [info]   "[21]:56" was not equal to "[16]:56" (DateFormatSpec.scala:73)

heh oh I see now
commit 0d2e82a879f4b63e159bc9cb2b318eb0a286b64f
    Simplification of DateFormatSpec (only support CDT right now)

that seems like a clue :-)

Sorry about that.  I should be able to fix that pretty quickly.

@SethTisue, please confirm the build is working now.

all good, thanks!


[ci skip] adding user @rxm7706

Hi! This is the friendly automated conda-forge-webservice.
I've added user @rxm7706 as instructed in #19.
Merge this PR to add the user. Please do not rerender this PR or change it in any way. It has [ci skip] in the commit message to avoid pushing a new build and so the build configuration in the feedstock should not be changed.
Please contact conda-forge/core to have this PR merged, if the maintainer is unresponsive.
Fixes #19

@conda-forge/core @mariusvniekerk  - Can I be added as a maintainer - I am happy to help keep this feedstock updated.


docs: adds doc build

@carsonfarmer just looking for a quick 👍
with upcoming changes i felt it would be good to start capturing the docstrings


Inquiry About TCGA LUAD 5-genes Mutation Prediction Label

Hi, thanks for this impressive work on this project!
I have a question regarding the use of the Gigapath model to generate embeddings for the task of TCGA LUAD 5 genes mutation prediction. I noticed that there are 1608 available TCGA-LUAD samples on TCGA currently, but the LUAD-5-gene_TCGA.csv dataset you used has 1346 SVS images. I plan to use my own set of 1608 samples.
My question is, where do the binary mutation labels for the genes PTEN, EGFR, KRAS, TP53, ALK, ROS1, BRAF, MET, PIK3CA, LKB1, STK11, RET, FAT1, and LRP1B come from? I couldn't find these binary mutation labels on the TCGA GDC platform. Should I analyze the MAF(Mutation Annotation Format) files corresponding to each SVS image to obtain the gene mutation labels?

Thank you, looking forward for your response!

Hi, any news about the labeling?
Another confusing part is that there are multiple TRUE labels for a single case, e.g. the first row has TP53 and LRP1B.
Do we need multi-hot coding for that? Any ideas?


[meta] add tests for k8s 1.19

This commit add tests on GKE 1.18 following new GKE version updates:
https://cloud.google.com/kubernetes-engine/docs/release-notes#May_19_2021

failing tests are transient errors