text:
[BUG]添加计算节点成功，无法显示

问题描述/What happened:
环境/Environment:

OS (e.g. cat /etc/os-release):kylinos v10 aarch
Kernel (e.g. uname -a):4.19.90
Service Version (e.g. kubectl exec -n onecloud $(kubectl get pods -n onecloud | grep climc | awk '{print $1}') -- climc version-list):3.10

查看注册宿主机
[root@cloudpods-1 ~]# climc host-list
***  Total: 0  ***
[root@cloudpods-1 ~]# kubectl -n onecloud get pods -o wide | grep 10.1.99.30
default-host-health-h2glj                           1/1     Running            0          5h18m   10.1.99.30      cloudpods-s1
default-host-image-gfprr                            1/1     Running            0          5h18m   10.1.99.30      cloudpods-s1
default-host-mrctx                                  3/3     Running               1          5h18m   10.1.99.30      cloudpods-s1
default-telegraf-4r8n7                              1/1     Init:CrashLoopBackOff            0          5h18m   10.1.99.30      cloudpods-s1
通过查看docker日志，发现缺少/etc/telegraf/telegraf.conf 。判断为缺少telegraf的安装和配置导致

@lvzhiweilv
重启 telegraf  相关pod？

重启之后计算节点的状态
[root@cloudpods-1 ~]# kubectl get pods -A  -o wide | grep telegraf
onecloud             default-telegraf-r4mmm                              0/1     Init:CrashLoopBackOff   4          102s    10.1.99.30      cloudpods-s1
查看pods中docker日志如下：
[root@cloudpods-S1 ~]# docker logs -f b1f90aee84af
2023/07/20 07:53:17 stat telegraf config file error stat /etc/telegraf/telegraf.conf: no such file or directory

重启之后计算节点的状态 [root@cloudpods-1 ~]# kubectl get pods -A -o wide | grep telegraf onecloud default-telegraf-r4mmm 0/1 Init:CrashLoopBackOff 4 102s 10.1.99.30 cloudpods-s1 查看pods中docker日志如下： [root@cloudpods-S1 ~]# docker logs -f b1f90aee84af 2023/07/20 07:53:17 stat telegraf config file error stat /etc/telegraf/telegraf.conf: no such file or directory
应该是添加计算节点的脚本中没有安装和配置相关服务

@lvzhiweilv  计算节点是物理机吗？发下添加计算节点的命令？

@lvzhiweilv telegraf 服务依赖 host-agent 启动成功，查看一下 host-agent 日志
kubectl logs -n onecloud -c host <host POD>

@lvzhiweilv 计算节点是物理机吗？发下添加计算节点的命令？

是物理机 ./ocboot.py add-node 10.1.1.12 10.1.99.30

[root@cloudpods-1 ~]# kubectl logs -n onecloud -c host default-host-mrctx| more
[info 230720 00:59:30 procutils.WaitZombieLoop(zombie_others.go:36)] My pid is not 1 and no need to wait zombies
[info 230720 00:59:30 options.ParseOptions(options.go:314)] Use configuration file: /etc/yunion/host.conf
[warning 230720 00:59:30 structarg.(*ArgumentParser).parseJSONKeyValue(structarg.go:1214)] Cannot find argument disk-is-ssd
[warning 230720 00:59:30 structarg.(*ArgumentParser).parseJSONKeyValue(structarg.go:1214)] Cannot find argument enable-qmp-monitor
[warning 230720 00:59:30 structarg.(*ArgumentParser).parseJSONKeyValue(structarg.go:1214)] Cannot find argument enable-health-checker
[warning 230720 00:59:30 structarg.(*ArgumentParser).parseJSONKeyValue(structarg.go:1214)] Cannot find argument enable-rbac
[warning 230720 00:59:30 structarg.(*ArgumentParser).parseJSONKeyValue(structarg.go:1214)] Cannot find argument health-driver
[info 230720 00:59:30 options.ParseOptions(options.go:336)] Set log level to "info"
[info 2023-07-20 00:59:30 options.ParseOptions(options.go:314)] Use configuration file: /etc/yunion/common/common.conf
[info 2023-07-20 00:59:30 options.ParseOptions(options.go:336)] Set log level to "info"
[info 2023-07-20 00:59:30 hostman.(*SHostService).InitService(host_services.go:63)] exec socket path: /var/run/onecloud/exec.sock
[info 2023-07-20 00:59:30 app.InitApp(app.go:32)] RequestWorkerCount: 8
[info 2023-07-20 00:59:30 appsrv.NewApplication(appsrv.go:116)] App hostId: 4fDlUDl6XrIb-LdigCU19aN-zRQ= (host,cloudpods-S1,10.1.99.30)
2023/07/20 00:59:30 Allow hosts []
[info 2023-07-20 00:59:30 appsrv.(*Application).SetDefaultTimeout(appsrv.go:132)] adjust application default timeout to 60.000000 seconds
[info 2023-07-20 00:59:30 hostinfo.DetectCpuInfo(hostinfohelper.go:77)] cpuinfo freq 0
[error 2023-07-20 00:59:30 sysutils.ParseCPUInfo(sysutils.go:122)] Failed to get cpu MHz
[error 2023-07-20 00:59:30 sysutils.ParseCPUInfo(sysutils.go:125)] Failed to get cpu cache size
[info 2023-07-20 00:59:30 hostinfo.NewHostInfo(hostinfo.go:2243)] CPU Model Phytium,FT-2000+/64 Microcode 2
[info 2023-07-20 00:59:30 hostinfo.NewHostInfo(hostinfo.go:2264)] Get kubelet container image Fs: /opt/docker, eviction config: {"evictionHard":{"imagefs.available":{"Signal":"i
magefs.available","Operator":"LessThan","Value":{"Quantity":null,"Percentage":0.05}},"memory.available":{"Signal":"memory.available","Operator":"LessThan","Value":{"Quantity":"1
00Mi","Percentage":0}},"nodefs.available":{"Signal":"nodefs.available","Operator":"LessThan","Value":{"Quantity":null,"Percentage":0.05}},"nodefs.inodesFree":{"Signal":"nodefs.i
nodesFree","Operator":"LessThan","Value":{"Quantity":null,"Percentage":0.05}}}}
[info 2023-07-20 00:59:32 hostinfo.(*SHostInfo).prepareEnv(hostinfo.go:404)] I/O Scheduler switch to bfq
[info 2023-07-20 00:59:32 fileutils2.ChangeBlkdevParameter(fileutils.go:202)] Set queue/scheduler of sdb to bfq
[info 2023-07-20 00:59:32 hostinfo.(*SHostInfo).Init(hostinfo.go:196)] Start detectHostInfo
[info 2023-07-20 00:59:32 hostinfo.(*SHostInfo).detectKVMMaxCpus(hostinfo.go:855)] KVM API VERSION 12
[info 2023-07-20 00:59:32 hostinfo.(*SHostInfo).detectKVMMaxCpus(hostinfo.go:860)] KVM CAP MAX VCPUS: 512
[info 2023-07-20 00:59:32 hostinfo.(*SHostInfo).detectKVMMaxCpus(hostinfo.go:868)] KVM CAP NR VCPUS: 64
[error 2023-07-20 00:59:32 sysutils.isNestSupport(kvm.go:160)] exit status 1
[error 2023-07-20 00:59:32 hostinfo.(*SHostInfo).detectOsDist(hostinfo.go:740)] exit status 1
[info 2023-07-20 00:59:32 hostinfo.(*SHostInfo).detectOsDist(hostinfo.go:750)] DetectOsDist
[error 2023-07-20 00:59:32 hostinfo.(*SHostInfo).detectOsDist(hostinfo.go:752)] Failed to detect distribution info
[info 2023-07-20 00:59:32 hostinfo.(*SHostInfo).detectQemuVersion(hostinfo.go:822)] Detect qemu version is 4.2.0
[info 2023-07-20 00:59:32 hostinfo.(*SHostInfo).detectOvsVersion(hostinfo.go:963)] Detect OVS version is 2.10.5
[info 2023-07-20 00:59:32 hostinfo.(*SHostInfo).detectOvsKOVersion(hostinfo.go:980)] kernel module openvswitch vermagic:       4.19.90-24.4.v2101.ky10.aarch64 SMP mod_unload mod
versions aarch64
WARNING: failed to determine memory area for node: open /sys/devices/system/node/node2/hugepages: no such file or directory
[info 2023-07-20 00:59:33 hostinfo.(*SHostInfo).Init(hostinfo.go:207)] Start parseConfig
[info 2023-07-20 00:59:33 hostinfo.(*SHostInfo).generateLocalNetworkConfig(hostinfo.go:238)] Find dev: br0 ip: 10.1.99.30
[info 2023-07-20 00:59:33 hostinfo.(*SHostInfo).generateLocalNetworkConfig(hostinfo.go:258)] port eno1 link type device
[info 2023-07-20 00:59:33 hostinfo.(*SHostInfo).generateLocalNetworkConfig(hostinfo.go:294)] bridge name br0
[info 2023-07-20 00:59:33 hostinfo.(*SHostInfo).parseConfig(hostinfo.go:308)] Generate network config eno1/br0/10.1.99.30
[info 2023-07-20 00:59:33 hostinfo.NewNIC(hostinfohelper.go:233)] IP 10.1.99.30/br0/eno1
[info 2023-07-20 00:59:33 hostinfo.NewNIC(hostinfohelper.go:286)] Confirm to configuration!!
[info 2023-07-20 00:59:33 hostinfo.(*SNIC).SetupDhcpRelay(hostinfohelper.go:202)] Not enable dhcp relay on nic: &hostinfo.SNIC{Inter:"eno1", Bridge:"br0", Ip:"10.1.99.30", Netwo
rk:"", WireId:"", Mask:24, Bandwidth:1000, BridgeDev:(*hostbridge.SOVSBridgeDriver)(0x4001773470), dhcpServer:(*hostdhcp.SGuestDHCPServer)(0x40018549f0)}
[info 2023-07-20 00:59:33 hostinfo.(*SHostInfo).setupOvnChassis(hostinfo.go:225)] Start setting up ovn chassis
[info 2023-07-20 00:59:33 hostman.(*SHostService).RunService.func1(host_services.go:83)] Auth complete!!
[info 2023-07-20 00:59:33 policy.(*SPolicyManager).init(policy.go:136)] policy fetch worker count 1
[info 2023-07-20 00:59:33 consts.SetNonDefaultDomainProjects(consts.go:109)] set non_default_domain_projects to false
[info 2023-07-20 00:59:33 storageman.StartSnapshotRecycle(storage_base.go:484)] Snapshot recyle job started
[info 2023-07-20 00:59:33 guestman.NewGuestCpuSetCounter(guesthelper.go:187)] NewGuestCpuSetCounter from topo: {"architecture":"numa","nodes":[{"caches":[{"level":1,"logical_pro
cessors":[0],"size_bytes":32768,"type":"instruction"},{"level":1,"logical_processors":[1],"size_bytes":32768,"type":"instruction"},{"level":1,"logical_processors":[2],"size_byte
s":32768,"type":"instruction"},{"level":1,"logical_processors":[3],"size_bytes":32768,"type":"instruction"},{"level":1,"logical_processors":[4],"size_bytes":32768,"type":"instru
ction"},{"level":1,"logical_processors":[5],"size_bytes":32768,"type":"instruction"},{"level":1,"logical_processors":[6],"size_bytes":32768,"type":"instruction"},{"level":1,"log
ical_processors":[7],"size_bytes":32768,"type":"instruction"},{"level":1,"logical_processors":[0],"size_bytes":32768,"type":"data"},{"level":1,"logical_processors":[1],"size_byt
es":32768,"type":"data"},{"level":1,"logical_processors":[2],"size_bytes":32768,"type":"data"},{"level":1,"logical_processors":[3],"size_bytes":32768,"type":"data"},{"level":1,"
logical_processors":[4],"size_bytes":32768,"type":"data"},{"level":1,"logical_processors":[5],"size_bytes":32768,"type":"data"},{"level":1,"logical_processors":[6],"size_bytes":
32768,"type":"data"},{"level":1,"logical_processors":[7],"size_bytes":32768,"type":"data"},{"level":2,"logical_processors":[0,1,2,3],"size_bytes":33554432,"type":"unified"},{"le
vel":2,"logical_processors":[4,5,6,7],"size_bytes":33554432,"type":"unified"}],"cores":[{"id":0,"index":0,"logical_processors":[0],"total_threads":1},{"id":1,"index":1,"logical_
processors":[1],"total_threads":1},{"id":2,"index":2,"logical_processors":[2],"total_threads":1},{"id":3,"index":3,"logical_processors":[3],"total_threads":1},{"id":4,"index":4,
"logical_processors":[4],"total_threads":1},{"id":5,"index":5,"logical_processors":[5],"total_threads":1},{"id":6,"index":6,"logical_processors":[6],"total_threads":1},{"id":7,"
index":7,"logical_processors":[7],"total_threads":1}],"distances":[10,20,40,30,20,30,50,40],"id":0,"memory":{"supported_page_sizes":[2097152,536870912],"total_physical_bytes":33
285996544,"total_usable_bytes":32273596416}},{"caches":[{"level":1,"logical_processors":[8],"size_bytes":32768,"type":"instruction"},{"level":1,"logical_processors":[9],"size_by
tes":32768,"type":"instruction"},{"level":1,"logical_processors":[10],"size_bytes":32768,"type":"instruction"},{"level":1,"logical_processors":[11],"size_bytes":32768,"type":"in
struction"},{"level":1,"logical_processors":[12],"size_bytes":32768,"type":"instruction"},{"level":1,"logical_processors":[13],"size_bytes":32768,"type":"instruction"},{"level":
1,"logical_processors":[14],"size_bytes":32768,"type":"instruction"},{"level":1,"logical_processors":[15],"size_bytes":32768,"type":"instruction"},{"level":1,"logical_processors
":[8],"size_bytes":32768,"type":"data"},{"level":1,"logical_processors":[9],"size_bytes":32768,"type":"data"},{"level":1,"logical_processors":[10],"size_bytes":32768,"type":"dat
a"},{"level":1,"logical_processors":[11],"size_bytes":32768,"type":"data"},{"level":1,"logical_processors":[12],"size_bytes":32768,"type":"data"},{"level":1,"logical_processors"
:[13],"size_bytes":32768,"type":"data"},{"level":1,"logical_processors":[14],"size_bytes":32768,"type":"data"},{"level":1,"logical_processors":[15],"size_bytes":32768,"type":"da
ta"},{"level":2,"logical_processors":[8,9,10,11],"size_bytes":33554432,"type":"unified"},{"level":2,"logical_processors":[12,13,14,15],"size_bytes":33554432,"type":"unified"}],"
cores":[{"id":10,"index":0,"logical_processors":[10],"total_threads":1},{"id":11,"index":1,"logical_processors":[11],"total_threads":1},{"id":12,"index":2,"logical_processors":[
12],"total_threads":1},{"id":13,"index":3,"logical_processors":[13],"total_threads":1},{"id":14,"index":4,"logical_processors":[14],"total_threads":1},{"id":15,"index":5,"logica
l_processors":[15],"total_threads":1},{"id":8,"index":6,"logical_processors":[8],"total_threads":1},{"id":9,"index":7,"logical_processors":[9],"total_threads":1}],"distances":[2
0,10,30,20,30,20,40,30],"id":1,"memory":{"supported_page_sizes":[2097152,536870912],"total_physical_bytes":34359738368,"total_usable_bytes":33214431232}}]}
[info 2023-07-20 00:59:33 hostdhcp.(*SGuestDHCPServer).Start(dhcpserver.go:72)] SGuestDHCPServer starting ...
[info 2023-07-20 00:59:33 guestman.(*SGuestManager).InitQemuMaxCpus(guestman.go:134)] KVM max cpus count: 64
[info 2023-07-20 00:59:33 guestman.(*SGuestManager).InitQemuMaxCpus(guestman.go:152)] Machine type virt max cpus: 64
[error 2023-07-20 00:59:35 hostinfo.(*SHostInfo).GetMasterNicIpAndMask(hostinfo.go:988)] MasterNic (*netutils2.SNetInterface)(nil)
[error 2023-07-20 00:59:35 hostinfo.(*SHostInfo).onFail(hostinfo.go:1068)] register failed: try create network: find_matched == false
[error 2023-07-20 00:59:35 timeutils2.AddTimeout.func1.1(timeutils.go:31)] register failed, try 30 seconds later...
goroutine 706 [running]:
runtime/debug.Stack()
/usr/lib/go/src/runtime/debug/stack.go:24 +0x68
runtime/debug.PrintStack()
/usr/lib/go/src/runtime/debug/stack.go:16 +0x20
yunion.io/x/onecloud/pkg/util/timeutils2.AddTimeout.func1.1()
/root/go/src/yunion.io/x/onecloud/pkg/util/timeutils2/timeutils.go:32 +0x60
panic({0x214e6a0, 0x2dc5410})
/usr/lib/go/src/runtime/panic.go:838 +0x20c
yunion.io/x/onecloud/pkg/hostman/hostinfo.(*SHostInfo).onFail(0x4000c8e180, {0x214e6a0?, 0x2dc5420?})
/root/go/src/yunion.io/x/onecloud/pkg/hostman/hostinfo/hostinfo.go:1070 +0xd8
yunion.io/x/onecloud/pkg/hostman/hostinfo.(*SHostInfo).tryCreateNetworkOnWire(0x4d68b00?)
/root/go/src/yunion.io/x/onecloud/pkg/hostman/hostinfo/hostinfo.go:1095 +0x5a0
yunion.io/x/onecloud/pkg/hostman/hostinfo.(*SHostInfo).fetchAccessNetworkInfo(0x4000c8e180)
/root/go/src/yunion.io/x/onecloud/pkg/hostman/hostinfo/hostinfo.go:1128 +0x588
yunion.io/x/onecloud/pkg/hostman/hostinfo.(*SHostInfo).register(0x40011b7901?)
/root/go/src/yunion.io/x/onecloud/pkg/hostman/hostinfo/hostinfo.go:1055 +0x28
yunion.io/x/onecloud/pkg/util/timeutils2.AddTimeout.func1()
/root/go/src/yunion.io/x/onecloud/pkg/util/timeutils2/timeutils.go:37 +0x60
created by yunion.io/x/onecloud/pkg/util/timeutils2.AddTimeout
/root/go/src/yunion.io/x/onecloud/pkg/util/timeutils2/timeutils.go:28 +0x70
[error 2023-07-20 01:00:05 hostinfo.(*SHostInfo).GetMasterNicIpAndMask(hostinfo.go:988)] MasterNic (*netutils2.SNetInterface)(nil)
[error 2023-07-20 01:00:05 hostinfo.(*SHostInfo).onFail(hostinfo.go:1068)] register failed: try create network: find_matched == false
[error 2023-07-20 01:00:05 timeutils2.AddTimeout.func1.1(timeutils.go:31)] register failed, try 30 seconds later...

@lvzhiweilv 这里有一些排查计算节点 host 服务启动失败的文档，可以参考下：https://www.cloudpods.org/zh/docs/function_principle/onpremise/host/troubleshooting/#查看host服务的日志

[error 2023-07-20 00:59:35 hostinfo.(*SHostInfo).GetMasterNicIpAndMask(hostinfo.go:988)] MasterNic (*netutils2.SNetInterface)(nil)
[error 2023-07-20 00:59:35 hostinfo.(*SHostInfo).onFail(hostinfo.go:1068)] register failed: try create network: find_matched == false
[error 2023-07-20 00:59:35 timeutils2.AddTimeout.func1.1(timeutils.go:31)] register failed, try 30 seconds later...
goroutine 706 [running]:
runtime/debug.Stack()
/usr/lib/go/src/runtime/debug/stack.go:24 +0x68
runtime/debug.PrintStack()
/usr/lib/go/src/runtime/debug/stack.go:16 +0x20
yunion.io/x/onecloud/pkg/util/timeutils2.AddTimeout.func1.1()
/root/go/src/yunion.io/x/onecloud/pkg/util/timeutils2/timeutils.go:32 +0x60
panic({0x214e6a0, 0x2dc5410})
/usr/lib/go/src/runtime/panic.go:838 +0x20c
yunion.io/x/onecloud/pkg/hostman/hostinfo.(*SHostInfo).onFail(0x4000c8e180, {0x214e6a0?, 0x2dc5420?})
/root/go/src/yunion.io/x/onecloud/pkg/hostman/hostinfo/hostinfo.go:1070 +0xd8
yunion.io/x/onecloud/pkg/hostman/hostinfo.(*SHostInfo).tryCreateNetworkOnWire(0x4d68b00?)
/root/go/src/yunion.io/x/onecloud/pkg/hostman/hostinfo/hostinfo.go:1095 +0x5a0
yunion.io/x/onecloud/pkg/hostman/hostinfo.(*SHostInfo).fetchAccessNetworkInfo(0x4000c8e180)
/root/go/src/yunion.io/x/onecloud/pkg/hostman/hostinfo/hostinfo.go:1128 +0x588
yunion.io/x/onecloud/pkg/hostman/hostinfo.(*SHostInfo).register(0x40011b7901?)
/root/go/src/yunion.io/x/onecloud/pkg/hostman/hostinfo/hostinfo.go:1055 +0x28
yunion.io/x/onecloud/pkg/util/timeutils2.AddTimeout.func1()
/root/go/src/yunion.io/x/onecloud/pkg/util/timeutils2/timeutils.go:37 +0x60
created by yunion.io/x/onecloud/pkg/util/timeutils2.AddTimeout
/root/go/src/yunion.io/x/onecloud/pkg/util/timeutils2/timeutils.go:28 +0x70
[error 2023-07-20 01:00:05 hostinfo.(*SHostInfo).GetMasterNicIpAndMask(hostinfo.go:988)] MasterNic (*netutils2.SNetInterface)(nil)
[error 2023-07-20 01:00:05 hostinfo.(*SHostInfo).onFail(hostinfo.go:1068)] register failed: try create network: find_matched == false
[error 2023-07-20 01:00:05 timeutils2.AddTimeout.func1.1(timeutils.go:31)] register failed, try 30 seconds later...

@lvzhiweilv 应该是没有找到宿主机对应的网络，需要创建下，参考这个文档解决：https://www.cloudpods.org/zh/docs/ops/hosterror/#宿主机的host服务启动失败且报错fail-to-get-network-infono-networks该怎么解决

climc network-create bcast0 host02  10.168.222.226  10.168.222.226 24 --gateway 10.168.222.1
链接中的各种信息该如何和现有环境对应。谢谢

climc network-create bcast0 host02 10.168.222.226 10.168.222.226 24 --gateway 10.168.222.1 链接中的各种信息该如何和现有环境对应。谢谢

@lvzhiweilv 执行下面的命令看下添加的计算的网络信息，麻烦把下面命令的输出贴下，需要根据当前节点的网络信息对应下：
# 查看网卡 ip
$ ip a

# 查看路由
$ ip route

#计算节点
[root@cloudpods-S1 ~]# ip ad
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
link/ether b4:05:5d:9a:46:68 brd ff:ff:ff:ff:ff:ff
3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether b4:05:5d:9a:46:69 brd ff:ff:ff:ff:ff:ff
4: eno3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether b4:05:5d:9a:46:66 brd ff:ff:ff:ff:ff:ff
5: eno4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether b4:05:5d:9a:46:67 brd ff:ff:ff:ff:ff:ff
6: cni0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether ee:22:c7:3e:e5:e7 brd ff:ff:ff:ff:ff:ff
inet 10.88.0.1/16 brd 10.88.255.255 scope global cni0
valid_lft forever preferred_lft forever
inet6 fe80::ec22:c7ff:fe3e:e5e7/64 scope link
valid_lft forever preferred_lft forever
9: kube-ipvs0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default
link/ether a6:0e:95:ec:f6:69 brd ff:ff:ff:ff:ff:ff
inet 10.96.0.1/32 brd 10.96.0.1 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.96.0.10/32 brd 10.96.0.10 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.101.127.185/32 brd 10.101.127.185 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.101.245.128/32 brd 10.101.245.128 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.103.17.226/32 brd 10.103.17.226 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.108.244.162/32 brd 10.108.244.162 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.100.71.19/32 brd 10.100.71.19 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.109.225.60/32 brd 10.109.225.60 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.109.74.241/32 brd 10.109.74.241 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.101.71.222/32 brd 10.101.71.222 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.106.88.88/32 brd 10.106.88.88 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.101.190.223/32 brd 10.101.190.223 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.109.128.228/32 brd 10.109.128.228 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.103.137.78/32 brd 10.103.137.78 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.107.170.124/32 brd 10.107.170.124 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.104.126.171/32 brd 10.104.126.171 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.101.6.133/32 brd 10.101.6.133 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.110.136.245/32 brd 10.110.136.245 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.111.191.220/32 brd 10.111.191.220 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.103.174.245/32 brd 10.103.174.245 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.106.120.156/32 brd 10.106.120.156 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.102.201.44/32 brd 10.102.201.44 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.98.94.168/32 brd 10.98.94.168 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.109.85.101/32 brd 10.109.85.101 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.110.28.135/32 brd 10.110.28.135 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.99.60.244/32 brd 10.99.60.244 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.96.26.135/32 brd 10.96.26.135 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.96.219.167/32 brd 10.96.219.167 scope global kube-ipvs0
valid_lft forever preferred_lft forever
inet 10.111.236.46/32 brd 10.111.236.46 scope global kube-ipvs0
valid_lft forever preferred_lft forever
10: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether ee:56:28:b7:0e:09 brd ff:ff:ff:ff:ff:ff
11: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
link/ether b4:05:5d:9a:46:68 brd ff:ff:ff:ff:ff:ff
inet 10.1.99.30/24 brd 10.1.99.255 scope global br0
valid_lft forever preferred_lft forever
12: tunl0@NONE: <NOARP,UP,LOWER_UP> mtu 1440 qdisc noqueue state UNKNOWN group default qlen 1000
link/ipip 0.0.0.0 brd 0.0.0.0
inet 10.40.245.192/32 brd 10.40.245.192 scope global tunl0
valid_lft forever preferred_lft forever
16: brvpc: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
link/ether 7a:fb:6e:db:d6:47 brd ff:ff:ff:ff:ff:ff
17: brtap: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
link/ether 1a:a6:74:5f:c7:48 brd ff:ff:ff:ff:ff:ff
20: caliec5b88df7a0@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1440 qdisc noqueue state UP group default
link/ether ee:ee:ee:ee:ee:ee brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::ecee:eeff:feee:eeee/64 scope link
valid_lft forever preferred_lft forever
[root@cloudpods-S1 ~]# ip route
default via 10.1.99.254 dev br0
10.1.99.0/24 dev br0 src 10.1.99.30
10.40.19.128/26 via 10.1.1.15 dev tunl0 proto bird onlink
10.40.72.0/26 via 10.1.1.13 dev tunl0 proto bird onlink
10.40.84.64/26 via 10.1.1.14 dev tunl0 proto bird onlink
blackhole 10.40.245.192/26 proto bird
10.40.245.193 dev caliec5b88df7a0 scope link
10.88.0.0/16 dev cni0 proto kernel scope link src 10.88.0.1 linkdown

10.1.99.30
在部署cloudpods的控制节点上执行
climc network-create bcast0 adm0 10.1.99.30 10.1.99.30 24 --gateway 10.1.99.254

adm0这个ip子网已经存在，且是管理集群使用的ip网段10.1.1.13。bcast0这个二层网络也已经存在，这样还可以直接创建么

adm0这个ip子网已经存在，且是管理集群使用的ip网段10.1.1.13。bcast0这个二层网络也已经存在，这样还可以直接创建么
@lvzhiweilv 可以换成adm1
climc network-create bcast0 adm1 10.1.99.30 10.1.99.30 24 --gateway 10.1.99.254

等xj有时间帮我模拟一下环境，我来测试、修复。

authors: hoganlxj lvzhiweilv wanyaoqi zexi zhasm

repo: yunionio/cloudpods


text:
Automated cherry pick of #10292: fix(monitor): fix monitor export err

Cherry pick of #10292 on release/3.7.
#10292: fix(monitor): fix monitor export err

Codecov Report

Merging #10293 (c068bad) into release/3.7 (0ff3997) will increase coverage by 1.87%.
The diff coverage is 0.00%.

@@               Coverage Diff                @@
##           release/3.7   #10293       +/-   ##
================================================
+ Coverage         5.98%    7.86%    +1.87%
================================================
  Files              848      110      -738
  Lines           131795    13368   -118427
================================================
- Hits              7887     1051     -6836
+ Misses          123206    12197   -111009
+ Partials           702      120      -582

Flag
Coverage Δ

aFlag
7.86% <0.00%> (+1.87%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/apigateway/handler/auth.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/auth_totp.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/idp.go
1.84% <0.00%> (ø)

pkg/apigateway/handler/misc.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/resource.go
0.00% <0.00%> (ø)

pkg/util/imagetools/imagetools.go
40.50% <0.00%> (-2.74%)
:arrow_down:

pkg/monitor/alerting/eval_context.go
34.82% <0.00%> (-2.18%)
:arrow_down:

pkg/hostman/diskutils/nbd/lvmutils.go
4.70% <0.00%> (-0.24%)
:arrow_down:

pkg/monitor/alerting/rule.go
1.78% <0.00%> (-0.09%)
:arrow_down:

pkg/monitor/alerting/engine.go
0.99% <0.00%> (-0.04%)
:arrow_down:

... and 688 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 889755f...c068bad. Read the comment docs.

source: gharchive/pull-request

authors: codecov-io zhaoxiangchun

repo: yunionio/onecloud

license_type: permissive

license_source: github-api


text:
Automated cherry pick of #2284: feature: 1. limit for bucket object count and size 2. quota for object count and size

Cherry pick of #2284 on release/2.12.
#2284: feature: 1. limit for bucket object count and size 2. quota for object count and size

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.12@c40b699). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.12   #2286   +/-   ##
==============================================
  Coverage                ?   7.09%
==============================================
  Files                   ?     452
  Lines                   ?   71313
  Branches                ?       0
==============================================
  Hits                    ?    5060
  Misses                  ?   65837
  Partials                ?     416

Flag
Coverage Δ

#aFlag
7.09% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/quotas.go
2.8% <0%> (ø)

pkg/compute/models/buckets.go
1.58% <0%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c40b699...b00f2b7. Read the comment docs.

/approve
/lgtm

authors: codecov-io swordqiu yousong


text:
Automated cherry pick of #2442: nat delele should overvide Delete() and call RealDelete() after delete cloud resource successfully

Cherry pick of #2442 on release/2.11.
#2442: nat delele should overvide Delete() and call RealDelete() after delete cloud resource successfully

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@fb45719). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.11   #2445   +/-   ##
==============================================
  Coverage                ?   7.08%
==============================================
  Files                   ?     454
  Lines                   ?   71668
  Branches                ?       0
==============================================
  Hits                    ?    5075
  Misses                  ?   66176
  Partials                ?     417

Flag
Coverage Δ

#aFlag
7.08% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/natstable.go
4.76% <0%> (ø)

pkg/compute/models/purge.go
0% <0%> (ø)

pkg/compute/models/natdtable.go
5.14% <0%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fb45719...f5a038c. Read the comment docs.

/lgtm

/approve

authors: Mjoycarry codecov-io zexi


text:
fix(region): allow member user get saml auth addr

这个 PR 实现什么功能/修复什么问题:

[x] 功能、bugfix描述
[x] 冒烟测试
[ ] 单元测试编写

是否需要 backport 到之前的 release 分支:

release/3.5

/area region
/cc @zexi

Codecov Report

Merging #8998 (880e09e) into master (d7c096d) will increase coverage by 11.76%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #8998       +/-   ##
===========================================
+ Coverage    5.86%   17.63%   +11.76%
===========================================
  Files         827       89      -738
  Lines      129104     8959   -120145
===========================================
- Hits         7576     1580     -5996
+ Misses     120848     7205   -113643
+ Partials      680      174      -506

Flag
Coverage Δ

aFlag
17.63% <ø> (+11.76%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/util/sysutils/hostname.go

pkg/compute/models/vcenters.go

pkg/cloudcommon/db/quotas/register.go

pkg/mcclient/options/k8s/statefulset.go

pkg/scheduler/models/pending_usage.go

pkg/compute/regiondrivers/aliyun.go

pkg/hostman/system_service/openvswitch.go

pkg/hostman/guestfs/fsdriver/esxi.go

pkg/compute/guestdrivers/aliyun.go

pkg/compute/models/secgroupresource.go

... and 728 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d7c096d...880e09e. Read the comment docs.

/lgtm
/approve

authors: codecov-io ioito zexi


text:
build: docker: use openvswitch 2.10.5-1

这个 PR 实现什么功能/修复什么问题:

[x] 冒烟测试

是否需要 backport 到之前的 release 分支:
NONE
/area host
/area vpcagent
/cc @zexi @swordqiu @wanyaoqi @zhasm

Codecov Report

Merging #9583 (ce86ed8) into master (159c1bc) will increase coverage by 10.59%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #9583       +/-   ##
===========================================
+ Coverage    5.90%   16.50%   +10.59%
===========================================
  Files         843       87      -756
  Lines      130900     9120   -121780
===========================================
- Hits         7736     1505     -6231
+ Misses     122463     7483   -114980
+ Partials      701      132      -569

Flag
Coverage Δ

aFlag
16.50% <ø> (+10.59%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/cloudcommon/db/statusdomainresource.go

pkg/multicloud/aws/imageowners.go

pkg/compute/models/dnszoneresource.go

pkg/apis/api.go

pkg/compute/models/vpcresource.go

pkg/multicloud/aws/iam_policy.go

pkg/mcclient/options/k8s/pvc.go

pkg/hostman/system_service/docker.go

pkg/util/qemuimg/init.go

pkg/cloudcommon/db/update.go

... and 746 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 159c1bc...ce86ed8. Read the comment docs.

/lgtm
/approve

authors: codecov-io yousong zexi


text:
hook provider, finally

let's see how this looks. I deliberately won't try to redirect on invalid group/store ids

Codecov Report

Merging #561 into master will increase coverage by 0.16%.
The diff coverage is 98.41%.

@@            Coverage Diff             @@
##           master     #561      +/-   ##
==========================================
+ Coverage   98.41%   98.58%   +0.16%
==========================================
  Files         239      231       -8
  Lines        3734     3669      -65
==========================================
- Hits         3675     3617      -58
+ Misses         59       52       -7

Impacted Files
Coverage Δ

client/app/components/userDetail/userDetail.js
100% <ø> (ø)
:arrow_up:

client/app/components/signup/signup.js
100% <ø> (ø)
:arrow_up:

client/app/components/home/home.js
100% <ø> (ø)
:arrow_up:

...ient/app/components/notifications/notifications.js
66.66% <ø> (-8.34%)
:arrow_down:

...lient/app/components/userDetail/userDetail.spec.js
100% <ø> (ø)
:arrow_up:

client/app/components/login/login.spec.js
100% <ø> (ø)
:arrow_up:

client/app/components/login/login.js
100% <ø> (ø)
:arrow_up:

client/app/components/group/groupEdit/groupEdit.js
100% <ø> (ø)
:arrow_up:

client/app/components/verifyMail/verifyMail.js
100% <ø> (ø)
:arrow_up:

...ient/app/services/authentication/authentication.js
100% <ø> (ø)
:arrow_up:

... and 29 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5277155...8b54f03. Read the comment docs.

authors: codecov-io tiltec

repo: yunity/foodsaving-frontend

license: mit

license_source: bigquery


text:
🛑 Bitwarden is down

In 98483b2, Bitwarden (https://bitwarden.yunus.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bitwarden is back up in 3b9b534 after 10 minutes.

source: gharchive/issue

license: MIT


text:
Bug: mangarock.com

Bug report
Environment (please complete the following information):

Description
Data

OS
Arch Linux (5.1.2-arch1-1-ARCH)

Python version
3.7.3

Pip version
19.0.3

Manga-py version
1.5.5.2

URL
https://mangarock.com/manga/mrs-serie-100226981

.
https://mangarock.com/manga/mrs-serie-100114548

.
...

To Reproduce:
Steps to reproduce the behavior:

Run manga-py https://mangarock.com/manga/mrs-serie-100226981
Command fails

Additional context
All downloads for mangarock seem to be broken at the moment. Possibly they changed how manga is delivered
Trying to download any manga from mangarock results in an error like this before anything can download at all:
[me@pc downloads]$ manga-py https://mangarock.com/manga/mrs-serie-100114548

2019-05-18 15:33:01.162 | ERROR    | manga_py.cli:start:45 - An error has been caught in function 'start', process 'MainProcess' (7963), thread 'MainThread' (140140626380416):
Traceback (most recent call last):

  File "/home/me/.local/bin/manga-py", line 11, in <module>
    load_entry_point('manga-py==1.5.5.2', 'console_scripts', 'manga-py')()
    └ <function load_entry_point at 0x7f75071f8268>

  File "/home/me/.local/lib/python3.7/site-packages/manga_py/__init__.py", line 93, in main
    code, _info = _run_util(args)
                  │         └ ArgumentParser(prog='manga-py', usage=None, description=None, formatter_class=<class 'argparse.HelpFormatter'>, conflict_handler...
                  └ <function _run_util at 0x7f75070c4730>
  File "/home/me/.local/lib/python3.7/site-packages/manga_py/__init__.py", line 52, in _run_util
    code = _init_cli(args, _info)
           │         │     └ <manga_py.info.Info object at 0x7f7507f54160>
           │         └ ArgumentParser(prog='manga-py', usage=None, description=None, formatter_class=<class 'argparse.HelpFormatter'>, conflict_handler...
           └ <function _init_cli at 0x7f75070c46a8>
  File "/home/me/.local/lib/python3.7/site-packages/manga_py/__init__.py", line 40, in _init_cli
    cli_mode.start()
    │        └ <bound method Cli.start of <manga_py.cli.Cli object at 0x7f75071a7b38>>
    └ <manga_py.cli.Cli object at 0x7f75071a7b38>
> File "/home/me/.local/lib/python3.7/site-packages/manga_py/cli/__init__.py", line 45, in start
    self.parser.start()
    │    │      └ <bound method Parser.start of <manga_py.parser.Parser object at 0x7f75071a79b0>>
    │    └ <manga_py.parser.Parser object at 0x7f75071a79b0>
    └ <manga_py.cli.Cli object at 0x7f75071a7b38>
  File "/home/me/.local/lib/python3.7/site-packages/manga_py/parser.py", line 44, in start
    self.provider.process(self.params['url'], self.params)
    │    │        │       │    │              │    └ {'url': 'https://mangarock.com/manga/mrs-serie-100114548', 'name': '', 'destination': 'Manga', 'no_progress': False, 'not_change...
    │    │        │       │    │              └ <manga_py.parser.Parser object at 0x7f75071a79b0>
    │    │        │       │    └ {'url': 'https://mangarock.com/manga/mrs-serie-100114548', 'name': '', 'destination': 'Manga', 'no_progress': False, 'not_change...
    │    │        │       └ <manga_py.parser.Parser object at 0x7f75071a79b0>
    │    │        └ <bound method Provider.process of <manga_py.providers.mangarock_com.MangaRockCom object at 0x7f75071a7438>>
    │    └ <manga_py.providers.mangarock_com.MangaRockCom object at 0x7f75071a7438>
    └ <manga_py.parser.Parser object at 0x7f75071a79b0>
  File "/home/me/.local/lib/python3.7/site-packages/manga_py/provider.py", line 83, in process
    self.loop_chapters()
    │    └ <bound method Provider.loop_chapters of <manga_py.providers.mangarock_com.MangaRockCom object at 0x7f75071a7438>>
    └ <manga_py.providers.mangarock_com.MangaRockCom object at 0x7f75071a7438>
  File "/home/me/.local/lib/python3.7/site-packages/manga_py/provider.py", line 114, in loop_chapters
    self._info.add_volume(self.chapter_for_json(), self.get_archive_path())
    │    │     │          │    │                   │    └ <bound method Provider.get_archive_path of <manga_py.providers.mangarock_com.MangaRockCom object at 0x7f75071a7438>>
    │    │     │          │    │                   └ <manga_py.providers.mangarock_com.MangaRockCom object at 0x7f75071a7438>
    │    │     │          │    └ <bound method MangaRockCom.chapter_for_json of <manga_py.providers.mangarock_com.MangaRockCom object at 0x7f75071a7438>>
    │    │     │          └ <manga_py.providers.mangarock_com.MangaRockCom object at 0x7f75071a7438>
    │    │     └ <bound method Info.add_volume of <manga_py.info.Info object at 0x7f7507f54160>>
    │    └ <manga_py.info.Info object at 0x7f7507f54160>
    └ <manga_py.providers.mangarock_com.MangaRockCom object at 0x7f75071a7438>
  File "/home/me/.local/lib/python3.7/site-packages/manga_py/provider.py", line 181, in get_archive_path
    _path + '.%s%s' % (additional_data_name, self._archive_type())
    │                  │                     │    └ <bound method Base._archive_type of <manga_py.providers.mangarock_com.MangaRockCom object at 0x7f75071a7438>>
    │                  │                     └ <manga_py.providers.mangarock_com.MangaRockCom object at 0x7f75071a7438>
    │                  └ ''
    └ 'vol_000'
  File "/home/me/.local/lib/python3.7/site-packages/manga_py/fs.py", line 73, in path_join
    return str(Path(_path).joinpath(*args))
           │   │    │                └ (None, 'vol_000.zip')
           │   │    └ 'Manga'
           │   └ <class 'pathlib.Path'>
           └ <class 'str'>
  File "/usr/lib/python3.7/pathlib.py", line 898, in joinpath
    return self._make_child(args)
           │    │           └ (None, 'vol_000.zip')
           │    └ <bound method PurePath._make_child of PosixPath('Manga')>
           └ PosixPath('Manga')
  File "/usr/lib/python3.7/pathlib.py", line 688, in _make_child
    drv, root, parts = self._parse_args(args)
                       │    │           └ (None, 'vol_000.zip')
                       │    └ <bound method PurePath._parse_args of <class 'pathlib.PosixPath'>>
                       └ PosixPath('Manga')
  File "/usr/lib/python3.7/pathlib.py", line 642, in _parse_args
    a = os.fspath(a)
    │   │  │      └ None
    │   │  └ <built-in function fspath>
    │   └ <module 'os' from '/usr/lib/python3.7/os.py'>
    └ None

TypeError: expected str, bytes or os.PathLike object, not NoneType

Thanks for the issue. I will check it

Component
Value

OS
Ubuntu 16.04.6 LTS

Python version
Python 3.5.2

Pip version
pip 19.1.1

Npm version
3.5.2

Manga-py version
1.5.5.2

URL
https://mangarock.com/manga/mrs-serie-100226981 Dont' work :bug: :boom:

URL
https://mangarock.com/manga/mrs-serie-100114548 Dont' work :bug: :boom:

URL
https://mangarock.com/manga/mrs-serie-100058029 Dont' work :bug: :boom:

URL
https://mangarock.com/manga/mrs-serie-100096263 Strange case. Works when downloading just the last chapters (it download a duplicate of 14 and 15 as 16 and 17), but breaks when downloading all :bug: :boom: .

So. I finally get my hands today to this issue.
The site has changed ... yes :-)
Now you can not just get the content. However, it is even better for us. They have an API. It's good
The logic will be slightly simplified. Wait for updates in the next day

Working for me now :+1:
@alexanderdegre, Is it working for you in this version?

Component
Value

OS
Ubuntu 16.04.6 LTS

Python version
Python 3.5.2

Pip version
pip 19.1.1

Npm version
3.5.2

Manga-py version
1.5.6.1

URL
https://mangarock.com/manga/mrs-serie-100226981

URL
https://mangarock.com/manga/mrs-serie-100114548

URL
https://mangarock.com/manga/mrs-serie-100058029

URL
https://mangarock.com/manga/mrs-serie-100096263

I close this issue. If you still have a problem, click "Reopen issue"

authors: 1271 alexanderdegre gromenauer

repo: yuru-yuri/manga-dl


text:
man without arguments: show summaries

So far, man without argument just listed the available commands. This patch adds a brief summary of the command description after each command. This should be helpful in particular for movie users, and users unfamiliar with posix commands:
[~/Documents]$ man
     alias: List or define shell aliases.
       cat: Print the contents of the given files.
        cd: Change the current working directory.
...

Notes:

The first line of the docstring is used as summary. This is in accordance to  PEP 257
I updated several docstrings to provide better summaries.
This parses all Python scripts in BINPATH. With many scripts, this could in theory be slow. However, with the commands currently included with stash, it's still quite fast (on my iPad 4). If necessary, performance could be improved by caching the docstrings.

Thanks @oefe
These are good changes and well explained.

authors: oefe ywangd

repo: ywangd/stash


text:
代授权小程序上传资源请求参数错误

sdk里用的component_access_token

哪个地方呢

repo: yydzxz/ByteDanceOpen


text:
Invalid password in signup should show a better error message

It should be validated by the frontend form before it even reaches the backend.

https://github.com/yzernik/squeakroad/pull/567

repo: yzernik/squeakroad


text:
数据没有刷新

_Dashboard_里面_Widget_数据缓存之后，第二次访问不能自动刷新

82f688d6cb126aef5285ec1cf312a07c68b14324


text:
Hot Fix for SOD

All Submissions Basics:

[ ] Have you followed the guidelines in our Contributing document?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[ ] Have you checked all Issues to tie the PR to a specific one?

All Submissions Cores:

[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your core changes, as applicable?
[ ] Have you successfully ran tests with your changes locally?
[ ] Does your submission pass tests, including CircleCI, Travis CI, and AppVeyor?
[ ] Does your submission have appropriate code coverage? The cutoff threshold is 95% by Coversall.

New Model Submissions:

[ ] Have you created a .py in ~/pyod/models/?
[ ] Have you created a _example.py in ~/examples/?
[ ] Have you created a test_.py in ~/pyod/test/?
[ ] Have you lint your code locally prior to submission?

Pull Request Test Coverage Report for Build 1420

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 95.533%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pyod/models/sod.py
0
1
0.0%

Totals

Change from base Build 1401:
0.0%

Covered Lines:
4406

Relevant Lines:
4612

💛  - Coveralls


text:
How to add a tab as a link?

Laravel Version: 5.6.*
PHP Version: 7.1
Laravel-admin: 1.5

Description:
Hello!
How to add a tab as a link which will lead to the sub-page?
http://joxi.ru/12MY4YLHlMRoR2

Supported in version 1.5.x-dev now

authors: shelestovas z-song

repo: z-song/laravel-admin


text:
post error 419 in v1.6.11

Laravel Version: v5.8.13
PHP Version:7.2.15
Laravel-admin: v1.6.11
我今晚项目运行composer update后发生了 #1651  的问题.
在我将composer.json中的laravel-admin版本"encore/laravel-admin": "1.6.11"修改为更新前的"encore/laravel-admin": "1.6.10",后恢复正常。
我在我的项目中能复现，不确定其他人是否遇到这个问题。
以下是我的出现问题时的composer.json
{     "name": "laravel/laravel",     "type": "project",     "description": "The Laravel Framework.",     "keywords": [         "framework",         "laravel"     ],     "license": "MIT",     "require": {         "php": "^7.1.3",         "encore/laravel-admin": "^1.6",         "fideloper/proxy": "^4.0",         "laravel-admin-ext/log-viewer": "^1.0",         "laravel-admin-ext/media-manager": "^1.0",         "laravel-admin-ext/redis-manager": "^1.0",         "laravel/framework": "5.8.*",         "laravel/passport": "^7.2",         "laravel/tinker": "^1.0"     },     "require-dev": {         "beyondcode/laravel-dump-server": "^1.0",         "filp/whoops": "^2.0",         "fzaninotto/faker": "^1.4",         "mockery/mockery": "^1.0",         "nunomaduro/collision": "^2.0",         "phpunit/phpunit": "^7.5"     },     "config": {         "optimize-autoloader": true,         "preferred-install": "dist",         "sort-packages": true     },     "extra": {         "laravel": {             "dont-discover": []         }     },     "autoload": {         "psr-4": {             "App\\": "app/"         },         "classmap": [             "database/seeds",             "database/factories"         ]     },     "autoload-dev": {         "psr-4": {             "Tests\\": "tests/"         }     },     "minimum-stability": "dev",     "prefer-stable": true,     "scripts": {         "post-autoload-dump": [             "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",             "@php artisan package:discover --ansi"         ],         "post-root-package-install": [             "@php -r \"file_exists('.env') || copy('.env.example', '.env');\""         ],         "post-create-project-cmd": [             "@php artisan key:generate --ansi"         ]     } }

所有的post请求都有这个问题，试试清空各种缓存呢？

更换浏览器后正常了。感谢大佬

authors: pennfly z-song


text:
How to remove option (scope) from Export button?

Laravel Version:5.8.35
PHP Version:7.2.8
Laravel-admin: 1.6.13

Description:
How to remove 'Selected rows' option (scope) from export  button in Grid method?
Steps To Reproduce:
Enable export option & go to list view page of any model.
Click on Export button to view 'Selected rows' option.
For ref:

The author did not provide a solution, I can think of a solution:
namespace Encore\Admin\Grid\Tools\ExportButton

Line 83 ‘selected’, delete or disable it

Thanks @UnaHe .

Same question and my solution:
css hide.
use Encore\Admin\Admin;

Admin::style('.dropdown-menu li:last-child {display:none;}');

authors: UnaHe chent1024 rwmediaworks


text:
Interactor\Form 支持 table && Text 增加方法决定是否显示 icon

使行弹框支持 table

谢谢！

authors: Hanson z-song


text:
Enhance documentation

[ ] Update README
[ ] Add descriptive documentation to attributes in mappings in data.rb
[ ] Add example usage (citing ccr as an advanced implementation)

Updated the README a bit. Not sure if anything else is worth saying.
(Still need to link ccr as an example bot implementation, but I'll wait until I implement the new scores endpoints)


text:
401 Unauthorized

I can't download firmware.

It works fine for me.

it's working now, after allow access to download folder.

Thanks.

authors: kuragna zacharee

repo: zacharee/SamloaderKotlin


text:
Issue 995

In the Brackets Git extension, a diff is used to review the changes you are about to commit, this means that on our flow it is important that all changes--even untracked files--must have a diff. Without a diff of untracked files the user gets the feeling that none of these new file will get committed.
After doing some investigation on how git diff works, I found that the only way to get a diff of a untracked files is to compare the file against /dev/null which did not sound like a good cross-platform solution.  Also I tried to run the command via brackets git but it was not returning the actual diff.
So, our solution requires flows for two cases:

Commit all: We need to check the status of the files that are candidates for the commit and check for untracked files.  If there are untracked files we will stage all the changes and do a diff of all files.  Once we have the diff we can unstage all the changes and then show the commit dialog using the diff.
Single commit: In this case we already know the status of the file, so if it is untracked we stage it, do the diff and unstage and show the commit dialog using the diff.

@zaggino I forgot to use the return calls on those places, I guess I got confused because the code is creating a new Promise, thought that was not required on that case. I'm also adding the catch on the reset index call

sorry, still a bit messy. you shouldn't do this:
return Git.stage(fileArray, false).then(function () {
+                return new Promise(function () {
+                    return Git.getDiffOfStagedFiles().then(function (diff) {
+                        return Git.resetIndex().then(function () {
+                            resolve(diff);
+                        });
+                    });
+                });
+            })

but instead it should be something like this:
var diff
return Git.stage(fileArray, false)
  .then(function () {
    return Git.getDiffOfStagedFiles();
  }).then(function (_diff) {
    diff = _diff;
    return Git.resetIndex();
  }).then(function () {
    return diff;
  });

and you shouldn't need to create your own Promise objects here

The changes now have your suggested changes from previous comment I think that is the right thing to do. I did a local test and it is doing the diff of untracked files. Now I have a better understanding of the Promises, thanks

Sorry, I forgot about this - merged.

authors: nmorenor zaggino

repo: zaggino/brackets-git


text:
Unable to install the clustersecret helm chart

Before I now, I didn't have any problems using the cluster secret helm chart, but suddenly I have problems installing it.
Exception: invoke of kubernetes:helm:template failed: invocation of kubernetes:helm:template returned an error:
failed to generate YAML for specified Helm chart: failed to pull chart:
looks like "https://charts.clustersecret.io/" is not a valid chart repository or cannot be reached:
Get "https://charts.clustersecret.io/index.yaml": dial tcp: lookup charts.clustersecret.io on 67.207.67.2:53: no such host

And when I do a nslookup on the domain:
Server:		8.8.8.8
Address:	8.8.8.8#53

** server can't find charts.clustersecret.io: NXDOMAIN

Is something wrong with the domain?

same issue here

Renovatebot complains as well.

Same here, it seems like it is a DNS issue, as the main website cannot be resolved either.

A workaround right now is to use it directly from github. Do an helm install directly from repo as https://raw.githubusercontent.com/zakkg3/ClusterSecret/cluster-secret-0.4.1/docs/ where cluster-secret-0.4.1 is the branch / tag. No need to specify the version anymore to helm unless you get an error of the version not existing - no version resolution needs to take place anymore since you already specified in the URL.

Domain problem is still unsolve?

Im not sure if this Repo is maintained anymore ... It is a nice project

@ThisIsIPat hahah same here, replicator might be the better option, since one can control the ns that gets the secret + other ressources are also shareable

https://github.com/zakkg3/ClusterSecret/issues/139

authors: LoricAndre Montralis ThisIsIPat damey2011 duchuyvp zakkg3 zoispag


text:
Avoid terminating delete on errors.

When there is an error happening upon deletion of the Kubernetes object
belonging to the cluster being removed, it makes no sense to abort the
deletion: the manifest will be removed anyway, therefore all the objects
after the one we aborted at will stay forever.

This partially addresses #218 , as it will not stop deletion when the object to delete is not there; however, it will also continue on any other error, as delete is a one-shot operation: once the CRD is removed the operator leaves no traces of the cluster existence (we could avoid removing the in-memory structures, but that wouldn't suffice in case the operator is restarted somewhere after the unsuccessful deletion).

👍

:+1:

authors: alexeyklyukin zerg-junior

repo: zalando-incubator/postgres-operator


text:
Rephrased section about stack traces in error messages.

In response to request in issue #51.

rely on

👍

:+1:

rely on

I didn't read the sentence correctly...

authors: fmueller hjacobs tkrop whiskeysierra

repo: zalando/restful-api-guidelines


text:
Notification icon is small than other icons

Notification icon is small than other icons.
I think the you're using incorrect res sizes and suggest to increase.
Tried in a Redmi Note 9S and also in a Google Pixel 7Pro and same issue.
Thanks in advance

Thank for letting me know. I'll look into this!

authors: robertoprubio zaneschepke

repo: zaneschepke/wgtunnel


text:
Project overlap, differences from lighttiger2505/lab

Hi, thanks for working on this gitlab CLI project! I find it very useful, especially the forking and git wrapping features.
I'm curious how the design or roadmap of this project compares to lighttiger2505/lab? I'd like to contribute to one of these projects but I'm not sure which one. Thanks again.
BTW, I opened a similar ticket in the other project: https://github.com/lighttiger2505/lab/issues/65

Sorry for the late reply here I've been battle with a nasty cold all weekend.
I can outline some of the differences and where this tool is headed.
Differences
Feature wise it looks like lighttiger's lab supports some operations with project variables and projects users that we don't
Over here it looks like we have forking, a CI pipeline interface, and job tracing.
Design
As @lighttiger2505 mentions, we have different command structure. We strictly use lab <noun> <verb> whereas lighttigers tool uses lab <verb> or lab <noun> as needed.
zaquestion/lab was initially designed to be a hub replacement for gitlab. We used to follow the conventions there much closer, but have since decided to move in our own direction. Firstly with our strict command structure, then by supporting origin or upstream remote schemes, now going beyond hub features to support more features like the CI pipeline interface which wouldn't make sense in hub.
zaquestion/lab is fundamentally workflow tool. We don't add features just to cover the API. We add them to support and improve our cli workflows.
Roadmap
For 1.0 there are a few things we'd like to do. The next "big thing" is an MR review workflow for the CLI. An outline can be seen here: https://github.com/zaquestion/lab/projects -- I see you're interested in supporting comments on MRs (and issues) thats going to be an early part of this project covered in https://github.com/zaquestion/lab/issues/83
We will also be removing the hub/git wrapper aspect of the project and moving to use git extensions in https://github.com/zaquestion/lab/issues/217
We may change the lab mr create syntax https://github.com/zaquestion/lab/issues/127
The config structure is very likely to change, at least to support https://github.com/zaquestion/lab/issues/151

Thanks for the detailed overview! Hopefully I can contribute in the near future.

It would be nice to mention the existance of lighttiger2505/lab in the README.md together with the differences.
And why you don't work together to produce an even more feature complete tool, because both have features that the other doesn't and that's a pity !

@varac what would detailing differences between the tools in the readme serve to achieve? I'm open to referencing lighttiger2505/lab in something like a similar tools section and evwn indicating briefly why one might prefer his their tool to this one, but that's about it.
No reason not to work together really, currently the tools take different approaches and I believe both started as hobby projects meant to serve the founders objectives.
lighttiger highlights some of the advantages of labs command structure (cobra),  it's possible lab could support both syntaxes with minimal work and functionality could be consolidated.
This is appealling to me as it would serve to unify the communities and pave way to the ultimate goal of becoming an officially regconized tool with GitLab

what would detailing differences between the tools in the readme serve to achieve?

I.e., if I would have known that this project currently doesn't support multiple instances (#151), and lighttiger2505/lab does, I would have taken lighttiger2505/lab. However, I'm super happy about lab ci trace, and there might be other features that are better in this project, so it would be just good for users to know what to choose.

I'm open to referencing lighttiger2505/lab in something like a similar tools section and even indicating briefly why one might prefer their tool to this one, but that's about it.

That's fine.

This is appealling to me as it would serve to unify the communities and pave way to the ultimate goal of becoming an officially regconized tool with GitLab

Woooo ! That would be really great !

authors: bzub varac zaquestion

repo: zaquestion/lab


text:
Improvements

quite some changes piled up...

Thanks!
Regarding ctf-tools-test-action, maybe we should redo the current CI trainwreck in terms of that. That could possibly be done without too much headache!

repo: zardus/ctf-tools


text:
Ignore incorrect color formats.

I think that when the color format is wrong, give a warning instead of throwing an exception directly, which will make the entire SVG parsing fail.
SVG: https://openseauserdata.com/files/863685b93036afafb014b12754a43b3e.svg
This SVG contains some percentage values, how to determine the width and height of the SVG for calculation?

See also https://github.com/zathras/jovial_svg/issues/35 and https://github.com/zathras/jovial_svg/issues/36

authors: xuelongqy zathras


text:
KSP 1.7.22-1.0.8

For a Gradle dependency:

Update the dependency version in the root gradle.properties
Update the dependency locks

For Gradle plugins: ./gradlew dependencies --write-locks
For Gradle dependencies: ./gradlew resolveAll --write-locks

Verify no unexpected entries appear in the lockfiles. A supply chain attack could occur during this stage. The lockfile narrows the supply chain attack window to this very moment (as opposed to every time a build occurs)
Are there any new APIs or possible migrations for this dependency?

com.google.devtools.ksp:com.google.devtools.ksp.gradle.plugin [1.7.20-1.0.6 -> 1.7.22-1.0.8]
https://goo.gle/ksp
com.google.devtools.ksp:symbol-processing [1.7.20-1.0.6 -> 1.7.22-1.0.8]
https://goo.gle/ksp

We should probably just bump kotlin to 1.7.21 and not 22 since 22 isn't an official release.

authors: HonzaR ccjernigan

repo: zcash/zcash-android-wallet-sdk


text:
有个疑问哈，为什么部分文件还是js写法

请教下，我看vben里边基本都是ts写法，包括也谢utils,大佬项目里边还有部分文件使用的js写法，这是出于什么目的考虑的呢

以后会出ts版本，不过我觉得短期内js版本对大部分前端更友好，不能为了用ts而用ts，ts解决的无非是规范和代码提示的问题，配置好vscode，代码提示已经很全面了，各种跳转定义和自动引入也很顺畅；至于规范，我觉得ts只能尽可能的保证代码的最低质量，经验丰富的前端哪怕使用js也可以有意识的预判和规避掉大部分错误，规避不掉的使用ts也不行

authors: geekLeopoldFitz zclzone

repo: zclzone/vue-naive-admin


text:
Why the test results are different using same data?

I used pl.seed_everything to set seed,
pl.seed_everything(_config["seed"], workers=True)

but I still got different result when I tested flickr30k Image2Text Retrieval task on the model trained by myself.
First:
(tensor(0.7382),  tensor(0.9274), tensor(0.9638), tensor(0.8965), tensor(0.9814), tensor(0.9941)) 0)

Second:
(tensor(0.7366), tensor(0.9294), tensor(0.9656), tensor(0.8975), tensor(0.9814), tensor(0.9941)) 0

I ensure the config files are same.
Do you meet this problem?

您好，
请教你一个问题，我和你一样使用这个模型meter_clip16_288_roberta_flickr.ckpt“，为什么代码报告这个错误显示模型meter_clip16_288_roberta_flickr.ckpt与网络权重参数维度不一致，感谢你能回答我的问题。


text:
Has this algorithm been tested with the Hesa 64-line radar?

The problem I am facing now is that the time of each point cloud of PandarQT-64 LiDAR is not relative to the time of the first point. The time field is timestamp. The node map is correct when mapping, but there is no point cloud.

I think you should modify some code in imageProjection.cpp, which is the extry of the whole pipeline. The time field of each point is use to integrate the angle of each point. You can refer codes around here

Hello senior, I have already resolved the issue you answered earlier. However, I am currently using the Pandar64 lidar for mapping, which produces approximately 72,000 points per frame. When running in ROS2, there are problems of dropped frames or no point cloud data. Could you please advise on how to adjust its communication? Specifically, do you have knowledge about DDS and the Cyclone DDS communication protocol?

I actually have a similar problem before. The message missing problem may be the ros2 bug(I think mostly the dds middleware). I spend many time to trace this problem but got no solution. I replace the default ros2 default dds (FastDDS) to cyclone dds and the problem was partially solved.

authors: LHZ-code zeal-up

repo: zeal-up/Simple-LIO-SAM


text:
Not guaranteed order of calling onCarinaAfterMethod  method from IAbstractTest as last afterMethod

if add afterMethod to the interface (nor does this interface inherit the IAbstractTest interface) and specify it above the class at the same level as IAbstractTest, then the order of calling onCarinaAfterMethod as the last afterMethod is not guaranteed.
So it is not guaranteed in such situation that driver will be available.

wontfix. Working as designed

repo: zebrunner/carina


text:
diff-remove-timestamps: Use sed -E directly

On any sufficiently modern Linux distro, sed -E will work.

On any sufficiently modern Linux distro, sed -E will work.

Evidence for this is that CI for zeek/zeek#3578 passed on all supported platforms with a similar change.

authors: awelzel bbannier

repo: zeek/package-template


text:
Consistently use HexEscapeSequences where applicable

For code points in the range from U+0000 to U+00FF there is no point in using a UnicodeEscapeSequence of the form \u00ff — so use \xff instead.

Thanks!

authors: leo mathiasbynens

repo: zeit/email-prompt


text:
2.0.0-canary.12 is broken

Hi guys, looks like you broke app in last canary release. Scroll and vertical split does not work after update.

Yes we broke it intentionally. Sorry for the inconvenience. You can switch to the stable release by chaning updateChannel: 'stable'
No this is a regression, thanks for reporting. We're on it.

Fixed by https://github.com/zeit/hyper/commit/52ac609c6ecacc2801da84203f617e0f7a0ca91f
New canary incomming

Broken by https://github.com/xtermjs/xterm.js/pull/1208

authors: VladimirHumeniuk albinekb chabou

repo: zeit/hyper


text:
linux build not available

[ ] I am on the latest Hyper.app version
[x] I have searched the issues of this repo and believe that this is not a duplicate

ubuntu 16.04:
N/A:
N/A:
N/A (CMD+SHIFT+I on Mac OS, CTRL+SHIFT+I elsewhere):
N/A:

Issue

curl -svi https://hyper-updates.now.sh/download/linux
*   Trying 54.193.10.167...
* Connected to hyper-updates.now.sh (54.193.10.167) port 443 (#0)
* found 179 certificates in /etc/ssl/certs/ca-certificates.crt
* found 720 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_256_GCM_SHA384
* 	 server certificate verification OK
* 	 server certificate status verification SKIPPED
* 	 common name: *.now.sh (matched)
* 	 server certificate expiration date OK
* 	 server certificate activation date OK
* 	 certificate public key: RSA
* 	 certificate version: #3
* 	 subject: OU=Domain Control Validated,OU=PositiveSSL Wildcard,CN=*.now.sh
* 	 start date: Thu, 25 Feb 2016 00:00:00 GMT
* 	 expire date: Fri, 24 Feb 2017 23:59:59 GMT
* 	 issuer: C=GB,ST=Greater Manchester,L=Salford,O=COMODO CA Limited,CN=COMODO RSA Domain Validation Secure Server CA
* 	 compression: NULL
* ALPN, server accepted to use http/1.1
> GET /download/linux HTTP/1.1
> Host: hyper-updates.now.sh
> User-Agent: curl/7.47.0
> Accept: */*
>
< HTTP/1.1 500 Internal Server Error
HTTP/1.1 500 Internal Server Error
< Server: nginx
Server: nginx
< Date: Wed, 02 Nov 2016 18:51:11 GMT
Date: Wed, 02 Nov 2016 18:51:11 GMT
< Content-Type: text/plain; charset=utf-8
Content-Type: text/plain; charset=utf-8
< Content-Length: 25
Content-Length: 25
< Connection: keep-alive
Connection: keep-alive
< X-Powered-By: Express
X-Powered-By: Express
< Vary: Accept
Vary: Accept
< ETag: W/"19-NTDF/tOqmR8oP9ZkUYuC4A"
ETag: W/"19-NTDF/tOqmR8oP9ZkUYuC4A"

<
* Connection #0 to host hyper-updates.now.sh left intact
Version not found: latest

#799 😄

authors: bsdlp matheuss


text:
Do not register app for ssh:// url scheme handling on dev mode

Have added a condition to check if its in Dev mode or not

Thank you so much for your help 🙏
Some advices:
For your next PR, keep in mind that the title of the PR will be shown in the Release Notes. It should be chosen to be understable by final user.
And this is a good practice to add issue number with Fixes prefix in your comment as your commit messages.
Fixes #2740

@chabou Sure. :+1:

authors: ajomadlabs chabou


text:
Default OS X keyboard shortcuts are not working

I use cmd+h to hide all windows belong to an app (can't remember if it's default OS X behaviour or not). It's working in other Electron apps, such as Slack and Atom, when focusing on text inputs. Not sure if this is true for other global OS X shortcuts people have set up.
Edit: I tried with cmd+option+m for minimizing the current window, which isn't working in Hyperterm.
Version: 0.2.1.

Fixed

authors: johanbrook rauchg

repo: zeit/hyperterm


text:
Fixup source map log

This ensures that ncc build -s will properly include the source map file in the rendered output log.

Codecov Report

Merging #267 into master will increase coverage by 0.23%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #267      +/-   ##
==========================================
+ Coverage   74.23%   74.46%   +0.23%
==========================================
  Files          17       17
  Lines         885      893       +8
==========================================
+ Hits          657      665       +8
  Misses        228      228

Impacted Files
Coverage Δ

src/cli.js
61.58% <100%> (+1.96%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 61dcf6c...3839925. Read the comment docs.

authors: codecov-io guybedford

repo: zeit/ncc


text:
Setting global styles with a _styles.css file

Just like we can use _document.js to customise the document and _error.js to customise the error page is would be great to be able to have _styles.css to set global css.
Reading the page on global styles and layouts left me feeling that there must be a better solution.

The easiest way to accomplish it is by using the

The idea with styled JSX is to add a

@pddigital I agree that css-in-js is the best choice for most cases. My issue with this approach is when it comes to global styles and tying them to a specific component. I would like a way to be able to set a style in one place and be done. As soon as I add them to a <Layout> component I'm making big assumptions about the future structure of my app

That's sort of the antithesis of CSS-in-JS: to have the styles all in one place... so if you're not into it, don't use Styled JSX then. Just use a link tag and a stylesheet. That's what you want to do, there's nothing stopping you from doing that now!! Or using one of the numerous CSS preprocessors (lots of examples) that are supported.

Found a solution similar to what I was wanting solution https://github.com/zeit/next.js/tree/canary/examples/with-global-stylesheet

authors: malimichael pddigital


text:
with-apollo-auth fails with no cookie

Describe the bug
The current solution checks for a req cookie and falls back to document if the cookie is not in the request. When no cookie exists, this causes an error.
To Reproduce
Clear cookies - then load the example - the offending code is:
withApollo.js:
function parseCookies(req, options = {}) {   return cookie.parse(     req && req.headers.cookie       ? req.headers.cookie       : document.cookie,     options   ) }
A fix would look something like:
   cookie.parse(     req ? (req.headers.cookie ? req.headers.cookie : "") : document.cookie,     options   )

@lfades

authors: glenarama timneutkens


text:
Do not try to server unnecessary files in either dev or prod.

This doesn't fix anything.
But this will make sure our logs are clean and does not contains surprising error messages.

Nice 👍

authors: arunoda timneutkens


text:
[CircleCI] Add seperate jobs for now dev integration tests

Run the now dev integration tests in parallel with the "standard" integration tests, since they both take a long time. This should cut the CI testing time in about half.

Codecov Report

Merging #2662 into canary will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           canary   #2662      +/-   ##
=========================================
- Coverage    7.92%   7.86%   -0.06%
=========================================
  Files         259     259
  Lines       10444   10420      -24
  Branches     1321    1320       -1
=========================================
- Hits          828     820       -8
+ Misses       9563    9547      -16
  Partials       53      53

Impacted Files
Coverage Δ

src/util/dev/yarn-installer.ts
37.28% <0%> (-0.81%)
:arrow_down:

src/util/dev/builder-cache.ts
32.79% <0%> (-0.71%)
:arrow_down:

src/util/dev/server.ts
11.52% <0%> (-0.25%)
:arrow_down:

src/util/dev/builder.ts
12.43% <0%> (+0.26%)
:arrow_up:

src/util/dev/router.ts
80.3% <0%> (+4.58%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 42f9745...6d08d4a. Read the comment docs.

authors: TooTallNate codecov-io

repo: zeit/now-cli


text:
How are you using this?

Would love to see what you are doing with it.

I think to use it for play with http://timesquair.io/ (http://thethingbox.io/ http://nodered.org/).
But it's not a fixed idea ;)

authors: rogerguess zeitungen

repo: zeitungen/node-rpi-rgb-led-matrix

license: WTFPL


text:
Add composer.lock to git

composer.lock should be in VCS.
php composer.phar install will be faster

Please read previous discussions about that.

@Ocramius is prior discussion stale now? @weierophinney and @ezimuel decided to ship composer.lock and not ship compooser.phar in the Apgility skeleton. They also suggested same should apply to this skeleton. See https://github.com/zfcampus/zf-apigility-skeleton/pull/92#issuecomment-110063604

Implemented as part of #286

authors: akrabat jeremiahsmall jmleroux

repo: zendframework/ZendSkeletonApplication


text:
Fixed links to PRs in the CHANGELOG

[x] Is this related to documentation?

These are also wrong here:
https://github.com/weierophinney/hal/releases/tag/0.2.0

Thanks, @webimpress.

authors: webimpress weierophinney

repo: zendframework/zend-expressive-hal


text:
Path segregation - pipeline middleware - config-driven

@weierophinney
Good morning,
I've an expressive application with a config-driven pipeline. That application exposes different UI levels such as /admin, /reseller and /client, among others...
Right now, I've a specific pipeline middleware that I want to execute only for specific paths:
...
protected function getPipeline()
{
    return [
        [
            'path' => '/admin',
            'middleware' => \Zend\Expressive\Navigation\Middleware\NavigationMiddleware::class
        ],
        [
            'path' => 'reseller',
            'middleware' => \Zend\Expressive\Navigation\Middleware\NavigationMiddleware::class
        ],
        [
            'path' => '/client',
            'middleware' => \Zend\Expressive\Navigation\Middleware\NavigationMiddleware::class
        ],
    ];
}
...

This is working but, I would rather be able to do something like this:
...
protected function getPipeline()
{
    return [
        [
            'paths' => ['/admin', '/reseller', '/client'],
            'middleware' => \Zend\Expressive\Navigation\Middleware\NavigationMiddleware::class
        ],
    }
}
...

Of course, I could use a custom delegator but I think this could be integrated in the default \Zend\Expressive\Container\ApplicationConfigInjectionDelegator delegator as follows:
...
    public static function injectPipelineFromConfig(Application $application, array $config) : void
    {
        if (empty($config['middleware_pipeline'])) {
            return;
        }

        // Create a priority queue from the specifications
        $queue = array_reduce(
            array_map(self::createCollectionMapper(), $config['middleware_pipeline']),
            self::createPriorityQueueReducer(),
            new SplPriorityQueue()
        );

        foreach ($queue as $spec) {
            $paths = $spec['path'] ?? ($spec['paths'] ?? '/');
            foreach((array) $paths as $path) {
                $application->pipe($path, $spec['middleware']);
            }
        }
    }
...

instead of
....
    public static function injectPipelineFromConfig(Application $application, array $config) : void
    {
        if (empty($config['middleware_pipeline'])) {
            return;
        }

        // Create a priority queue from the specifications
        $queue = array_reduce(
            array_map(self::createCollectionMapper(), $config['middleware_pipeline']),
            self::createPriorityQueueReducer(),
            new SplPriorityQueue()
        );

        foreach ($queue as $spec) {
            $path = $spec['path'] ?? '/';
            $application->pipe($path, $spec['middleware']);
        }
    }
....

Thank you.

We don't recommend usage of config-driven routes or pipelines at this point; starting in Expressive 2, we began moving away from using them in examples, and we've discussed deprecating the feature. I know some people swear by them, but it's a complicated feature, and easy to misconfigure. However, if you want to submit a pull request (which will require tests and documentation), I'll review. (We may separate the feature into a standalone package later, so new features will continue to live.)

@weierophinney

some people swear by them

We are one of them. You should really avoid opinionated implementations. This was the mistake you have done with your MVC implementation. Zend Expressive is really cool as micro-framework but if you start forcing developers to follow a single road, that will make it unusable or a bad choice for some developers.
We prefer a config-driven pipeline rather than a pipeline programmatically configured. This is a choice we've made because we want make the configuration close to our modules.
Please don't force us to configure our pipelines and/or routes programatically by deprecating the feature, even through, we could always create our own delegator. If you deprecate that feature which is not so complicated to understand you will really make some of your supporters unhappy.
The major problem with the programmatically approach is that the configuration is not close to the modules. When we setup our OPTIONAL modules (which are close to our application), we want just have to inject their configuration providers, nothing helse. Having to add each module's pipeline/route configurations programatically is really a pain for us and for our end-users.
I'll see if I can contribute a bit more. Right now, I'm developing a Zend helper extension for Plates (extension that compose an helper plugin manager to provide Zend view helpers-like (doctype, navigation ...) in Plates templates).
Thank you.

You should really avoid opinionated implementations. This was the mistake you have made with your MVC implementation. Zend Expressive is really cool as micro-framework and a great alternative to symfony but if you start forcing developers to follow a single road, that will make it unusable or a bad choice for some developers.

We have to choose carefully where we spend our time maintaining code and educating users. While I appreciate that the config-driven approach is useful to a number of people, the number of support questions we had to field based on them was disproportionate, which was why we moved away from the feature.
This sort of feature is quite easy for us to separate into its own package, however, and we could hand off maintenance of that to interested users. This would be the best of both worlds, I feel, as those who want the feature can install the package and use the support, and we can still direct folks to the explicit routing/pipeline approach we document initially.

This repository has been closed and moved to mezzio/mezzio; a new issue has been opened at https://github.com/mezzio/mezzio/issues/4.

authors: nuxwin weierophinney

repo: zendframework/zend-expressive


text:
Ensure all keys in this associative array are valid XML tag names

We do this by replacing invalid characters with an _.

Thanks, @Akrabat!

authors: akrabat weierophinney

repo: zendframework/zend-problem-details


text:
netusb: TX path doesn't work in RNDIS driver

Describe the bug
When using the RNDIS driver communication with the host doesn't work. Enabling some debugging shows that the driver is able to receive data, but not to send it. Enabling more debugging shows that the RNDIS driver try to do more USB bulk IN transfer while the current one hasn't finished.
To Reproduce
Build any net sample with the RNDIS driver for the interface. Tested on Nucleo L432KC and SAM E70 Xplained.
Expected behavior
IP communication works out of the box.
Impact
The driver is unusable.
Screenshots or console output
uart:~$ net ping 192.0.2.2
S[00:00:27.310,000] <dbg> usb_net.netusb_send: Send pkt, len 42
[00:00:27.310,000] <dbg> usb_rndis.rndis_send: send pkt 0x20003968 len 42
[00:00:27.310,000] <dbg> usb_rndis.net_pkt_hexdump: <
[00:00:27.310,000] <dbg> usb_rndis:
ff ff ff ff ff ff 00 00 |........
5e 00 53 00 08 06       |^.S...
[00:00:27.310,000] <dbg> usb_rndis:
00 01 08 00 06 04 00 01 |........
00 00 5e 00 53 00 c0 00 |..^.S...
02 01 00 00 00 00 00 00 |........
c0 00 02 02             |....
[00:00:27.310,000] <dbg> usb_rndis.rndis_hdr_add: type 1 len 86 payload offset 36 payload len 42
[00:00:27.310,000] <dbg> usb_net: USB <
01 00 00 00 56 00 00 00 |....V...
24 00 00 00 2a 00 00 00 |$...*...
00 00 00 00 00 00 00 00 |........
00 00 00 00 00 00 00 00 |........
00 00 00 00 00 00 00 00 |........
00 00 00 00 ff ff ff ff |........
ff ff 00 00 5e 00 53 00 |....^.S.
08 06 00 01 08 00 06 04 |........
[00:00:27.310,000] <dbg> usb_dc_stm32.usb_dc_ep_write: ep 0x82, len 64
[00:00:27.310,000] <dbg> usb_net: USB <
00 01 00 00 5e 00 53 00 |....^.S.
c0 00 02 01 00 00 00 00 |........
00 00 c0 00 02 02       |......
[00:00:27.310,000] <dbg> usb_dc_stm32.usb_dc_ep_write: ep 0x82, len 22
[00:00:27.310,000] <err> usb_dc_stm32: Unable to write ep 0x82 (-16)
ent a ping to 192.0.2.2
[00:00:27.310,000] <wrn> usb_net: Error writing to ep 0x82 ret -16
Ping timeout
[00:00:27.310,000] <err> usb_dc_stm32: Unable to write ep 0x82 (-16)
[00:00:27.310,000] <wrn> usb_net: Error writing to ep 0x82 ret -16

Environment (please complete the following information):

OS: Linux
Toolchain: Debian
Commit SHA: 35b7fde8a60b55ca0806a50e5b8cb4cca83f1b84

It looks like the RNDIS driver should be switch to use the transfer API instead of reinventing the wheel with the try_write function. Something similar to ccf0b46a3120afd8156dc183eb3149c82cd24d4c.

It looks like the RNDIS driver should be switch to use the transfer API instead of reinventing the wheel with the try_write function. Something similar to ccf0b46.

try_write() was before new USB API, so it was not reinvented. However I have added patch moving to new API here:  PR #13985

repo: zephyrproject-rtos/zephyr


text:
userspace: thread indexes are not released when dynamic threads lose all references

When a dynamic object has its permission count go to zero, the object is automatically freed. In the case of thread objects, the thread object will be freed, but the thread index is not released.
This does work correctly for explicit calls to k_object_free(). It's only when the object is freed in unref_check() that this doesn't happen.
This simple patch ought to fix it, but doesn't actually work:
diff --git a/kernel/userspace.c b/kernel/userspace.c
index a9adb59e5b..7bb6a6458b 100644
--- a/kernel/userspace.c
+++ b/kernel/userspace.c
@@ -394,6 +394,9 @@ static void unref_check(struct _k_object *ko, int index)
                break;
        }

+       if (dyn_obj->kobj.type == K_OBJ_THREAD) {
+               thread_idx_free(dyn_obj->kobj.data);
+       }
        rb_remove(&obj_rb_tree, &dyn_obj->node);
        sys_dlist_remove(&dyn_obj->obj_list);
        k_free(dyn_obj);

If you try this, you will get a recursive spinlock error; the code in thread_idx_free() tries to grab the lists_lock, but we are already holding it. Need to reconsider the concurrency control.

Please be sure to amend the test cases in tests/kernel/threads/dynamic_thread once this is fixed.

@wentongwu see #17027

Wondering if a k_mutex would be better? It supports nested locking, and as a bonus won't disable interrupts.

@camicarballo hold off on this.
I've found deeper problems with dynamic threads, and we may have to remove them entirely.


text:
Sample/subsys/fs/littlefs with board=nucleo_f429zi  don't work

Describe the bug
The sample project subsys/Ifs/littlefs don't work on a nucleo_f429zi board. I always get this error: littlefs: format failed (LFS -28)
The configuration option CONFIG_APP_WIPE_STORAGE=y don't change the behavior.
To Reproduce
cd zepyr/samples/subsys/fs/littlefs
west build -b nucleo_f429zi .
west flash
Expected behavior
Those output is generated by the sample project on the board nrf52840dk_nrf52840:
Area 4 at 0x0 on MX25R64 for 65536 bytes
[00:00:00.006,683] <inf> littlefs: LittleFS version 2.2, disk version 2.0
[00:00:00.006,744] <inf> littlefs: FS at MX25R64:0x0 is 16 0x1000-byte blocks with 512 cycle
[00:00:00.006,744] <inf> littlefs: sizes: rd 16 ; pr 16 ; ca 64 ; la 32
[00:00:00.007,080] <err> littlefs: WEST_TOPDIR/modules/fs/littlefs/lfs.c:998: Corrupted dir pair at {0x0, 0x1}
[00:00:00.007,110] <wrn> littlefs: can't mount (LFS -84); formatting
/lfs mount: 0
/lfs: bsize = 16 ; frsize = 4096 ; blocks = 16 ; bfree = 14
/lfs/boot_count stat: -2
/lfs/boot_count read count 0: 0
/lfs/boot_count seek start: 0
/lfs/boot_count write new boot count 1: 4
/lfs/boot_count close: 0
/lfs opendir: 0
  F 4 boot_count
End of files
/lfs unmount: 0
[00:00:00.104,095] <inf> littlefs: /lfs mounted
[00:00:00.111,572] <err> fs: failed get file or dir stat (-2)
[00:00:00.132,232] <inf> littlefs: /lfs unmounted

Logs and console output
Those output is generated by the sample project on the board nucleo_f429zi:
*** Booting Zephyr OS build zephyr-v2.3.0  ***
Area 1 at 0x10000 on FLASH_CTRL for 65536 bytes
FAIL: mount id 1 at /lfs: -28
[00:00:00.008,000] <inf> littlefs: LittleFS version 2.2, disk version 2.0
[00:00:00.008,000] <inf> littlefs: FS at FLASH_CTRL:0x10000 is 1 0x10000-byte blocks with 512 cycle
[00:00:00.008,000] <inf> littlefs: sizes: rd 16 ; pr 16 ; ca 64 ; la 32
[00:00:00.008,000] <wrn> littlefs: can't mount (LFS -84); formatting
[00:00:00.008,000] <err> littlefs: WEST_TOPDIR/modules/fs/littlefs/lfs.c:495: No more free space 1
[00:00:00.008,000] <err> littlefs: format failed (LFS -28)
[00:00:00.008,000] <err> fs: fs mount error (-28)

Environment (please complete the following information):

OS: Linux
Toolchain: GNU ARM EMB 8.3.1
Zephyr Version: v2.3.0

Will look into it in details but generally flash based samples do not play well on nucleo_f429zi due to unusual flash map (cf https://github.com/zephyrproject-rtos/zephyr/issues/19895).

@Cimex97 Following discussion during review of #28387, it appears that LittleFS is not made to work with few STM32 series such as F2/F4/F7.
Reason is that LittleFS (similarly to other FS solutions) will use one flash page per file to be saved (plus one for the superblock).
Since STM32F2/F4/F7 flash hardware block is made of quite little number of big pages, it would be a waste of memory to use 256KB to save only 1 file.
If you're looking for an alternative storage solution, you can check #19895 that exposes solution to use nvs. Though it requires careful flash partition configuration to respect nvs constraints (expect min 2 blocks of memory with total size < 64kB).
Btw, https://github.com/zephyrproject-rtos/zephyr/pull/23876 should help relaxing those constraints.

Marking as low as littlefs is not easily supported on this platform, nothing Zephyr can do about that.  Alternative solutions identified above.  This could also be closed.

From Triage the concern is why is this being run on a platform that doesn't support it.  The problem is that the test/sample requires a "storage" partition.  Only boards where that partition has at least four blocks will pass this test.
I don't know of a way to filter it other than the existing "platform_allow", which does not include this platform.
@nashif what should I do?

Removing the "STM32" tag since the remaining point to discuss is not STM32 specific.
Meanwhile, it wouild be good to have @Cimex97's feedback on ticket evolution.

I tried to use LittleFS in combination with the SMP, that comes with the MCUBoot bootloader to transfer configuration files onto the nucleo_f429zi board.
I used now the memory map example from @erwangoc and it works fine, in the sample and my own application. But is it a good idea, when I waste a lot of flash for the LittleFS?

I would probably look for a different solution, but offhand I have no suggestions (the ideas I have in mind would be a bit of work, e.g. faked file systems).  If it meets your application needs and you have no other use for the flash it should be fine to use littlefs this way.

I need to talk to my colleagues if we can realize it with a different solution.
Maybe we can help you, to implement your Idea.

authors: Cimex97 erwango pabigot


text:
TF-M: BL2 signing is broken due to incompatible MCUboot version

Describe the bug
Enabling TFM_BL2 (default y) results in build errors.
This is because BL2 expects an MCUboot version that includes imgtool version 1.7.2 (minimum).
Workaround:
Either:

Install 1.7.2 in system environment. (See additional context).
Disable TFM_BL2.

To Reproduce
Steps to reproduce the behavior:

west build -b nrf5340dk_nrf5340_cpuapp_ns ../zephyr/samples/tfm_integration/tfm_regression_test

Logs and console output
Traceback (most recent call last):
  File "/home/joakim/repos/zephyrproject/modules/tee/tf-m/trusted-firmware-m/bl2/ext/mcuboot/scripts/wrapper/wrapper.py", line 128, in <module>
    wrap()
  File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/home/joakim/repos/zephyrproject/modules/tee/tf-m/trusted-firmware-m/bl2/ext/mcuboot/scripts/wrapper/wrapper.py", line 103, in wrap
    img = imgtool.image.Image(version=imgtool.version.decode_version(version),
TypeError: __init__() got an unexpected keyword argument 'rom_fixed'

Environment (please complete the following information):

OS: Any
Toolchain: Any
Commit SHA or Version used: 2.7.0

Additinal context:
It is unclear why installing a newer imgtool version works, and also if this is at all an acceptable solution.
BL2 wrapper.py states that the mcuboot imgtool is preferred over the system imgtool. So why it actually picks the system imgtool is strange.
# Add the cwd to the path so that if there is a version of imgtool in there then
# it gets used over the system imgtool. Used so that imgtool from upstream
# mcuboot is preferred over system imgtool

@d3zd3z Any comment on the BL2 and upstream mcuboot integration here?

BL2 wrapper.py states that the mcuboot imgtool is preferred over the system imgtool. So why it actually picks the system imgtool is strange.

I seem to have lost this argument a long time ago. My argument has always been that the tools should only use the imgtool that is in the mcuboot tree, and it shouldn't be installed at all.
Aside from that, I don't know if that would actually fix this problem, since as I understand, you are using an older mcuboot, but the TF-M code is passing an argument only accepted by the newer version of imgtool. Is my understanding correct?
Can you state which version of Zephyr you are using? Is TF-M and mcuboot coming from the west.yml file?

BL2 wrapper.py states that the mcuboot imgtool is preferred over the system imgtool. So why it actually picks the system imgtool is strange.

I seem to have lost this argument a long time ago. My argument has always been that the tools should only use the imgtool that is in the mcuboot tree, and it shouldn't be installed at all.
Aside from that, I don't know if that would actually fix this problem, since as I understand, you are using an older mcuboot, but the TF-M code is passing an argument only accepted by the newer version of imgtool. Is my understanding correct?
Can you state which version of Zephyr you are using? Is TF-M and mcuboot coming from the west.yml file?

The imgtool that is included in the mcuboot tree is the one that is being used. And that one is not compatible with the TF-M build script wrapper.
The version tested was 2.7.0, this has been partially fixed in main branch with 031ed1859b8318ce9aad5798656816510fb5bb27 (upgrading from imgtool 1.7.0 to 1.8.0.rc2), however there is still one problem.
There is a dependency now on the command always being called with the working directory set to the mcuboot/scripts path.
This is brittle and it fails currently because we don't set this for all calls to the wrapper script. I can submit a fix for that.

authors: d3zd3z joerchan microbuilder


text:
wifi: esp_at: shell command "wifi scan" not working well

Describe the bug
The shell command "wifi scan" doesn't print every wifi AP available when used by esp-at driver
To Reproduce
To launch the wifi sample with esp-at driver :

Connect your board to ESP32 board. I used a ST board b_u585i_iot02a connected to esp32-c3-devkitC, through UART3.

Create overlay file : zephyr/samples/net/wifi/boards/b_u585i_iot02a.overlay containing
"&usart3 {
pinctrl-0 = <&usart3_tx_pd8 &usart3_rx_pd9>;
pinctrl-names = "default";
current-speed = <115200>;
status = "okay";
espressif,esp-at {
label = "Driver AT for ESP32-C3";
compatible = "espressif,esp-at";
};
};"

Modify zephyr/samples/net/wifi/prj.conf :

Remove line 4: CONFIG_TEST_RANDOM_GENERATOR=y
add lines "CONFIG_NET_TCP_ISN_RFC6528=n" and "CONFIG_WIFI_ESP_AT=y"

west build -b b_u585i_iot02a platform/zephyr/samples/net/wifi/ -p

west flash -r openocd

Expected behavior
Every wifi AP detected by esp32-c3-devkitC should be printed on zephyr shell.
Impact
annoyance, I need this functionnality for tests
Logs and console output
The zephyr shell prints :
"
uart:~$ *** Booting Zephyr OS build v2.7.99-2259-ge9f6e05b5a97  ***
Connected
Disconnected
uart:~$ wifi scan
Scan requested
Num  | SSID                             (len) | Chan | RSSI | Sec      | MAC
1    | SFR_1985                         8     | 1    | -50  | WPA/WPA2 |
2    | FreeWifi_secure                  15    | 11   | -87  | WPA/WPA2 |
3    |                                  0     | 11   | -88  | WPA/WPA2 |
4    | FreeWifi                         8     | 11   | -89  | Open     |
Scan request done
"
I am able to spy the AT communication between esp32-c3-devkitC and the ST board
On the AT link the anwser of esp32-c3-devkitC is
"+CWLAP:(2,"SFR_1985",-50,1)
+CWLAP:(2,"Livebox-642C",-85,1)
+CWLAP:(0,"SFR WiFi FON",-85,6)
+CWLAP:(5,"SFR WiFi Mobile",-87,6)
+CWLAP:(4,"SFR_3838",-87,6)
+CWLAP:(2,"freebox_XEGBMZ",-87,11)
+CWLAP:(5,"FreeWifi_secure",-87,11)
+CWLAP:(3,"",-88,11)
+CWLAP:(0,"FreeWifi",-89,11)
"
-> so we can see that some lines have been dropped
Environment (please complete the following information):

OS: WSL in windows 10

I have been able to solve the bug with this workarround :
diff --git a/subsys/net/l2/wifi/wifi_shell.c b/subsys/net/l2/wifi/wifi_shell.c
index 5a8bb3e9cb..c00893139e 100644
--- a/subsys/net/l2/wifi/wifi_shell.c
+++ b/subsys/net/l2/wifi/wifi_shell.c
@@ -31,6 +31,7 @@ LOG_MODULE_REGISTER(net_wifi_shell, LOG_LEVEL_INF);
                                NET_EVENT_WIFI_CONNECT_RESULT |         \
                                NET_EVENT_WIFI_DISCONNECT_RESULT)

+#define WIFI_SCAN_RESULT_MAX 20
 static struct {
        const struct shell *shell;

@@ -49,6 +50,8 @@ static uint32_t scan_result;

 static struct net_mgmt_event_callback wifi_shell_mgmt_cb;

+static struct wifi_scan_result wifi_scan_result_list[WIFI_SCAN_RESULT_MAX];
+
 #define print(shell, level, fmt, ...)                                  \
        do {                                                            \
                if (shell) {                                            \
@@ -62,11 +65,15 @@ static void handle_wifi_scan_result(struct net_mgmt_event_callback *cb)
 {
        const struct wifi_scan_result *entry =
                (const struct wifi_scan_result *)cb->info;
-       uint8_t mac_string_buf[sizeof("xx:xx:xx:xx:xx:xx")];
+       /*uint8_t mac_string_buf[sizeof("xx:xx:xx:xx:xx:xx")];*/
+
+       if (scan_result<WIFI_SCAN_RESULT_MAX) {
+               memcpy(&wifi_scan_result_list[scan_result], entry, sizeof(struct wifi_scan_result));
+       }

        scan_result++;

-       if (scan_result == 1U) {
+       /*if (scan_result == 1U) {
                print(context.shell, SHELL_NORMAL,
                      "\n%-4s | %-32s %-5s | %-4s | %-4s | %-5s    | %s\n",
                      "Num", "SSID", "(len)", "Chan", "RSSI", "Sec", "MAC");
@@ -77,7 +84,7 @@ static void handle_wifi_scan_result(struct net_mgmt_event_callback *cb)
              (entry->security == WIFI_SECURITY_TYPE_PSK ? "WPA/WPA2" : "Open    "),
              ((entry->mac_length) ?
                      net_sprint_ll_addr_buf(entry->mac, WIFI_MAC_ADDR_LEN, mac_string_buf,
-                                            sizeof(mac_string_buf)) : ""));
+                                            sizeof(mac_string_buf)) : ""));*/
 }

 static void handle_wifi_scan_done(struct net_mgmt_event_callback *cb)
@@ -85,13 +92,29 @@ static void handle_wifi_scan_done(struct net_mgmt_event_callback *cb)
        const struct wifi_status *status =
                (const struct wifi_status *)cb->info;

+       uint8_t mac_string_buf[sizeof("xx:xx:xx:xx:xx:xx")];
+
        if (status->status) {
                print(context.shell, SHELL_WARNING,
                      "Scan request failed (%d)\n", status->status);
        } else {
+               for (int i=0; i<scan_result; i++) {
+                       if (i == 0U) {
+                               print(context.shell, SHELL_NORMAL,
+                                       "\n%-4s | %-32s %-5s | %-4s | %-4s | %-5s    | %s\n",
+                                       "Num", "SSID", "(len)", "Chan", "RSSI", "Sec", "MAC");
+                       }
+                       print(context.shell, SHELL_NORMAL, "%-4d | %-32s %-5u | %-4u  | %-4d| %-5s | %s\n",
+                               i, wifi_scan_result_list[i].ssid, wifi_scan_result_list[i].ssid_length,
+                               wifi_scan_result_list[i].channel, wifi_scan_result_list[i].rssi,
+                               (wifi_scan_result_list[i].security == WIFI_SECURITY_TYPE_PSK ? "WPA/WPA2" : "Open    "),
+                               ((wifi_scan_result_list[i].mac_length) ?
+                                       net_sprint_ll_addr_buf(wifi_scan_result_list[i].mac, WIFI_MAC_ADDR_LEN, mac_string_buf,
+                                                               sizeof(mac_string_buf)) : ""));
+               }
                print(context.shell, SHELL_NORMAL, "Scan request done\n");
        }
-
+
        scan_result = 0U;
 }

@pbatiot thanks for the report, please consider opening a Pull Request with the workaround you posted.

@mniestroj Would you take a look?

@pbatiot Could you see if increasing NET_MGMT_EVENT_QUEUE_SIZE Kconfig option solves your problem? Set it to value that is higher than the number of WiFi networks you are expecting.

@mniestroj Your solution works.
I put CONFIG_NET_MGMT_EVENT_QUEUE_SIZE=20 in prj.conf, now i am not missing any wifi in the printed list.
As you have said, the queue size must be higher than the number of WiFi networks expected, to avoid dropping some.
I will close the issue, the correct configuration of the queue size is what i needed.
Thanks Marcin

authors: carlescufi mniestroj pbatiot sylvioalves


text:
Bluetooth: legacy advertising doesn't resume if CONFIG_BT_EXT_ADV=y

Describe the bug
In this configuration: HCI over RPMSG, CONFIG_BT_EXT_ADV=y, CONFIG_BT_MAX_CONN>1:

a legacy advertiser is started using bt_le_adv_start, without setting BT_LE_ADV_OPT_ONE_TIME.
a device connects
bt_le_adv_resume fails to resume the advertiser

See the original discussion in https://github.com/zephyrproject-rtos/zephyr/pull/51309 .
edit: wasn't really related to nRF53, also reproduced with just a single device with CONFIG_BT_EXT_ADV=y.
To Reproduce
Steps to reproduce the behavior:

flash samples/bluetooth/peripheral with the following config: CONFIG_BT_MAX_CONN=2, CONFIG_BT_EXT_ADV=y to the nRF5340 app core.
flash samples/bluetooth/hci_rpmsg with the following config: CONFIG_BT_MAX_CONN=2, CONFIG_BT_EXT_ADV=y to the nRF5340 net core.

Expected behavior
Advertising resumes after a connection is established.

@jhedberg can you have a look?

@tgagneret-embedded could you double-check if the merged patch fixes your original issue?

authors: jori-nordic kruithofa