[BUG] Node Scheduling not Behaving as Expected

Describe the bug
When node scheduling "Run VM on any available node" is selected the VMs are not evenly distributed across all node rather they are all scheduled on one node until that node is full and then scheduled on the next node util it is full and then the next etc.
To Reproduce
Launch a multiple instance set of VMs. Launch multiple single instance VMs.
Expected behavior
When "Run VM on any available node" is selected it is expected that the VMs would be equally distributed across all nodes based on each node's current workload.
Support bundle
attached
supportbundle_bf7fcf45-64e7-4b57-9499-30359d8de5ba_2021-12-09T19-03-54Z.zip
Environment:

Harvester ISO version: 1.0.0-rc1
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): bare metal

Additional context

@guangbochen not sure if we did anything different from v0.3.0. Might be a Kubernetes scheduling behavior?

Yes it's the kube-scheduler behavior. The scheduling scores are not straightforward to check though(https://github.com/kubernetes/kubernetes/issues/101820).
The following statement doesn't seem to be valid in the provided environment.

they are all scheduled on one node until that node is full

name
CPU usage
Memory usage
# of VMs in the default namespace
# of Pods in recorded namespaces

harvester-p9xvk
32.5%
70.0%
9
68

harvester-t5b2f
22.3%
51.3%
10
34

harvester-txhll
19.0%
51.0%
10
33

If we disable overcommit, we can distribute VMs to all node. Probably, we can let users choose whether to use overcommit in creating VM page. If they choose not, we show some warning message like "It may let all VMs run in 1 node". WDYT? cc @guangbochen @weihanglo
https://user-images.githubusercontent.com/4927361/154242981-dfbb0c50-aa80-46ca-acd1-48c4c172f84e.mp4
https://user-images.githubusercontent.com/4927361/154243002-eeefd7e0-b2ea-413d-b09e-feffcadb6ac5.mp4

@FrankYang0529
I think we should minimize to one independent variable to test. For example, only enable one metric at a time.

100% CPU and memory, but overcommit on volume size
100% volume and memory, but overcommit on CPU
100% volume and CPU, but overcommit on memory

Also, we could try to find the exact number of the ratio of overcommit affecting scheduling. Is 200% CPU overcommit influences the scheduling? What about 500% or 1000%?
Also, there are some node affinity/selector rules on VM/VMI. We also need to check that, though I guess there was nothing be set.

Hi @weihanglo, I did an experiment to see how scores change with/without the overcommit feature. For enabling overcommit feature, overcommit-config is {cpu: 1600, memory: 150, storage: 200}. I create 2 VMs (1 CPU, 1G RAM) once a time. VM1 is created first and then VM2.
I summarize score change from the kube-scheduler log. Please see Table 1 and Table 2.
In the With Overcommit case, request-cpu changes from 8832 to 8894. It's because 1 CPU will be 16x smaller. 1000m CPU / 16 = 62. The difference between 8832 and 8894 is 62. The calculation for request-memory is similar.
In the Without Overcommit case, request-cpu changes from 19225 to 20225, it's because 1 CPU is equal to 1000m CPU.
The overcommit feature changes the requested quantity of CPU and memory. However, when kube-scheduler calculates scores, it uses normalization, so it's hard to say which number for overcommit is best for scheduling. It depends on cluster resources. I think it's better to let users choose whether to use the overcommit feature when users create VM and default is disabled. We can use an annotation for it like harvesterhci.io/overcommit: true. WDYT? @weihanglo @guangbochen
Table 1 - With Overcommit

With Overcommit
harvester-zwvbr
harvester-bk6zp
hpd8s7

NodeResourcesBalancedAllocation
request-cpu: 18287request-memory:<PHONE_NUMBER>6score: 71
request-cpu: 9357request-memory:<PHONE_NUMBER>score: 66
request-cpu: 8832 -> 8894request-memory:<PHONE_NUMBER> -><PHONE_NUMBER>score: 67 -> 67

NodeResourcesLeastAllocated
request-cpu: 18287request-memory:<PHONE_NUMBER>6score: 71
request-cpu: 9357request-memory:<PHONE_NUMBER>score: 66
request-cpu: 8832 -> 8894request-memory:<PHONE_NUMBER> -><PHONE_NUMBER>score: 79 -> 78

Table 2 - Without Overcommit

Without Overcommit
harvester-zwvbr
harvester-bk6zp
hpd8s7

NodeResourcesBalancedAllocation
request-cpu: 19225 -> 20225request-memory:<PHONE_NUMBER>4 -><PHONE_NUMBER>0score: 69 -> 68
request-cpu: 10295request-memory:<PHONE_NUMBER>score: 62
request-cpu: 9770request-memory:<PHONE_NUMBER>score: 63

NodeResourcesLeastAllocated
request-cpu: 19225 -> 20225request-memory:<PHONE_NUMBER>4 -><PHONE_NUMBER>0score: 74 -> 73
request-cpu: 10295request-memory:<PHONE_NUMBER>score: 75
request-cpu: 9770request-memory:<PHONE_NUMBER>score: 77

kube-scheduler scores
vm1-with-overcommit
virt-launcher-vm1-with-overcommit-z22wx -> harvester-zwvbr: NodeResourcesBalancedAllocation, map of allocatable resources map[cpu:48000 memory:135037677568], map of requested resources map[cpu:18287 memory:12814995456] ,score 71,
virt-launcher-vm1-with-overcommit-z22wx -> harvester-bk6zp: NodeResourcesBalancedAllocation, map of allocatable resources map[cpu:24000 memory:135036702720], map of requested resources map[cpu:9357 memory:7146393600] ,score 66,
virt-launcher-vm1-with-overcommit-z22wx -> hpd8s7: NodeResourcesBalancedAllocation, map of allocatable resources map[cpu:24000 memory:135044558848], map of requested resources map[cpu:8832 memory:5791633408] ,score 67,

virt-launcher-vm1-with-overcommit-z22wx -> harvester-zwvbr: NodeResourcesLeastAllocated, map of allocatable resources map[cpu:48000 memory:135037677568], map of requested resources map[cpu:18287 memory:12814995456] ,score 75,
virt-launcher-vm1-with-overcommit-z22wx -> harvester-bk6zp: NodeResourcesLeastAllocated, map of allocatable resources map[cpu:24000 memory:135036702720], map of requested resources map[cpu:9357 memory:7146393600] ,score 77,
virt-launcher-vm1-with-overcommit-z22wx -> hpd8s7: NodeResourcesLeastAllocated, map of allocatable resources map[cpu:24000 memory:135044558848], map of requested resources map[cpu:8832 memory:5791633408] ,score 79,

"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="InterPodAffinity" node="harvester-zwvbr" score=0
"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="InterPodAffinity" node="harvester-bk6zp" score=0
"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="InterPodAffinity" node="hpd8s7" score=0

"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="NodeResourcesLeastAllocated" node="harvester-zwvbr" score=75
"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="NodeResourcesLeastAllocated" node="harvester-bk6zp" score=77
"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="NodeResourcesLeastAllocated" node="hpd8s7" score=79

"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="NodeAffinity" node="harvester-zwvbr" score=0
"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="NodeAffinity" node="harvester-bk6zp" score=0
"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="NodeAffinity" node="hpd8s7" score=0

"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="NodePreferAvoidPods" node="harvester-zwvbr" score=1000000
"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="NodePreferAvoidPods" node="harvester-bk6zp" score=1000000
"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="NodePreferAvoidPods" node="hpd8s7" score=1000000

"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="PodTopologySpread" node="harvester-zwvbr" score=200
"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="PodTopologySpread" node="harvester-bk6zp" score=200
"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="PodTopologySpread" node="hpd8s7" score=200

"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="TaintToleration" node="harvester-zwvbr" score=100
"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="TaintToleration" node="harvester-bk6zp" score=100
"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="TaintToleration" node="hpd8s7" score=100

"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="NodeResourcesBalancedAllocation" node="harvester-zwvbr" score=71
"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="NodeResourcesBalancedAllocation" node="harvester-bk6zp" score=66
"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="NodeResourcesBalancedAllocation" node="hpd8s7" score=67

"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="ImageLocality" node="harvester-zwvbr" score=54
"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="ImageLocality" node="harvester-bk6zp" score=54
"Plugin scored node for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" plugin="ImageLocality" node="hpd8s7" score=54

"Calculated node's final score for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" node="harvester-zwvbr" score=1000500
"Calculated node's final score for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" node="harvester-bk6zp" score=1000497
"Calculated node's final score for pod" pod="default/virt-launcher-vm1-with-overcommit-z22wx" node="hpd8s7" score=1000500

vm2-with-overcommit
virt-launcher-vm2-with-overcommit-qnwx4 -> hpd8s7: NodeResourcesBalancedAllocation, map of allocatable resources map[cpu:24000 memory:135044558848], map of requested resources map[cpu:8894 memory:6686416896] ,score 67,
virt-launcher-vm2-with-overcommit-qnwx4 -> harvester-bk6zp: NodeResourcesBalancedAllocation, map of allocatable resources map[cpu:24000 memory:135036702720], map of requested resources map[cpu:9357 memory:7146393600] ,score 66,
virt-launcher-vm2-with-overcommit-qnwx4 -> harvester-zwvbr: NodeResourcesBalancedAllocation, map of allocatable resources map[cpu:48000 memory:135037677568], map of requested resources map[cpu:18287 memory:12814995456] ,score 71,

virt-launcher-vm2-with-overcommit-qnwx4 -> hpd8s7: NodeResourcesLeastAllocated, map of allocatable resources map[cpu:24000 memory:135044558848], map of requested resources map[cpu:8894 memory:6686416896] ,score 78,
virt-launcher-vm2-with-overcommit-qnwx4 -> harvester-bk6zp: NodeResourcesLeastAllocated, map of allocatable resources map[cpu:24000 memory:135036702720], map of requested resources map[cpu:9357 memory:7146393600] ,score 77,
virt-launcher-vm2-with-overcommit-qnwx4 -> harvester-zwvbr: NodeResourcesLeastAllocated, map of allocatable resources map[cpu:48000 memory:135037677568], map of requested resources map[cpu:18287 memory:12814995456] ,score 75,

"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="NodeResourcesBalancedAllocation" node="hpd8s7" score=67
"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="NodeResourcesBalancedAllocation" node="harvester-bk6zp" score=66
"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="NodeResourcesBalancedAllocation" node="harvester-zwvbr" score=71

"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="ImageLocality" node="hpd8s7" score=54
"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="ImageLocality" node="harvester-bk6zp" score=54
"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="ImageLocality" node="harvester-zwvbr" score=54

"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="InterPodAffinity" node="hpd8s7" score=0
"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="InterPodAffinity" node="harvester-bk6zp" score=0
"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="InterPodAffinity" node="harvester-zwvbr" score=0

"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="NodeResourcesLeastAllocated" node="hpd8s7" score=78
"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="NodeResourcesLeastAllocated" node="harvester-bk6zp" score=77
"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="NodeResourcesLeastAllocated" node="harvester-zwvbr" score=75

"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="NodeAffinity" node="hpd8s7" score=0
"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="NodeAffinity" node="harvester-bk6zp" score=0
"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="NodeAffinity" node="harvester-zwvbr" score=0

"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="NodePreferAvoidPods" node="hpd8s7" score=1000000
"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="NodePreferAvoidPods" node="harvester-bk6zp" score=1000000
"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="NodePreferAvoidPods" node="harvester-zwvbr" score=1000000

"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="PodTopologySpread" node="hpd8s7" score=200
"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="PodTopologySpread" node="harvester-bk6zp" score=200
"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="PodTopologySpread" node="harvester-zwvbr" score=200

"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="TaintToleration" node="hpd8s7" score=100
"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="TaintToleration" node="harvester-bk6zp" score=100
"Plugin scored node for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" plugin="TaintToleration" node="harvester-zwvbr" score=100

"Calculated node's final score for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" node="hpd8s7" score=1000499
"Calculated node's final score for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" node="harvester-bk6zp" score=1000497
"Calculated node's final score for pod" pod="default/virt-launcher-vm2-with-overcommit-qnwx4" node="harvester-zwvbr" score=1000500

vm1-without-overcommit
virt-launcher-vm1-without-overcommit-4zlgd -> harvester-bk6zp: NodeResourcesBalancedAllocation, map of allocatable resources map[cpu:24000 memory:135036702720], map of requested resources map[cpu:10295 memory:7505707008] ,score 62,
virt-launcher-vm1-without-overcommit-4zlgd -> hpd8s7: NodeResourcesBalancedAllocation, map of allocatable resources map[cpu:24000 memory:135044558848], map of requested resources map[cpu:9770 memory:6150946816] ,score 63,
virt-launcher-vm1-without-overcommit-4zlgd -> harvester-zwvbr: NodeResourcesBalancedAllocation, map of allocatable resources map[cpu:48000 memory:135037677568], map of requested resources map[cpu:19225 memory:13174308864] ,score 69,

virt-launcher-vm1-without-overcommit-4zlgd -> harvester-bk6zp: NodeResourcesLeastAllocated, map of allocatable resources map[cpu:24000 memory:135036702720], map of requested resources map[cpu:10295 memory:7505707008] ,score 75,
virt-launcher-vm1-without-overcommit-4zlgd -> hpd8s7: NodeResourcesLeastAllocated, map of allocatable resources map[cpu:24000 memory:135044558848], map of requested resources map[cpu:9770 memory:6150946816] ,score 77,
virt-launcher-vm1-without-overcommit-4zlgd -> harvester-zwvbr: NodeResourcesLeastAllocated, map of allocatable resources map[cpu:48000 memory:135037677568], map of requested resources map[cpu:19225 memory:13174308864] ,score 74,

"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="NodePreferAvoidPods" node="harvester-bk6zp" score=1000000
"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="NodePreferAvoidPods" node="hpd8s7" score=1000000
"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="NodePreferAvoidPods" node="harvester-zwvbr" score=1000000

"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="PodTopologySpread" node="harvester-bk6zp" score=200
"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="PodTopologySpread" node="hpd8s7" score=200
"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="PodTopologySpread" node="harvester-zwvbr" score=200

"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="TaintToleration" node="harvester-bk6zp" score=100
"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="TaintToleration" node="hpd8s7" score=100
"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="TaintToleration" node="harvester-zwvbr" score=100

"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="NodeResourcesBalancedAllocation" node="harvester-bk6zp" score=62
"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="NodeResourcesBalancedAllocation" node="hpd8s7" score=63
"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="NodeResourcesBalancedAllocation" node="harvester-zwvbr" score=69

"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="ImageLocality" node="harvester-bk6zp" score=54
"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="ImageLocality" node="hpd8s7" score=54
"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="ImageLocality" node="harvester-zwvbr" score=54

"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="InterPodAffinity" node="harvester-bk6zp" score=0
"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="InterPodAffinity" node="hpd8s7" score=0
"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="InterPodAffinity" node="harvester-zwvbr" score=0

"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="NodeResourcesLeastAllocated" node="harvester-bk6zp" score=75
"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="NodeResourcesLeastAllocated" node="hpd8s7" score=77
"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="NodeResourcesLeastAllocated" node="harvester-zwvbr" score=74

"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="NodeAffinity" node="harvester-bk6zp" score=0
"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="NodeAffinity" node="hpd8s7" score=0
"Plugin scored node for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" plugin="NodeAffinity" node="harvester-zwvbr" score=0

"Calculated node's final score for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" node="harvester-bk6zp" score=1000491
"Calculated node's final score for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" node="hpd8s7" score=1000494
"Calculated node's final score for pod" pod="default/virt-launcher-vm1-without-overcommit-4zlgd" node="harvester-zwvbr" score=1000497

vm2-without-overcommit
virt-launcher-vm2-without-overcommit-hhdpj -> harvester-bk6zp: NodeResourcesBalancedAllocation, map of allocatable resources map[cpu:24000 memory:135036702720], map of requested resources map[cpu:10295 memory:7505707008] ,score 62,
virt-launcher-vm2-without-overcommit-hhdpj -> harvester-zwvbr: NodeResourcesBalancedAllocation, map of allocatable resources map[cpu:48000 memory:135037677568], map of requested resources map[cpu:20225 memory:14428405760] ,score 68,
virt-launcher-vm2-without-overcommit-hhdpj -> hpd8s7: NodeResourcesBalancedAllocation, map of allocatable resources map[cpu:24000 memory:135044558848], map of requested resources map[cpu:9770 memory:6150946816] ,score 63,

virt-launcher-vm2-without-overcommit-hhdpj -> harvester-bk6zp: NodeResourcesLeastAllocated, map of allocatable resources map[cpu:24000 memory:135036702720], map of requested resources map[cpu:10295 memory:7505707008] ,score 75,
virt-launcher-vm2-without-overcommit-hhdpj -> harvester-zwvbr: NodeResourcesLeastAllocated, map of allocatable resources map[cpu:48000 memory:135037677568], map of requested resources map[cpu:20225 memory:14428405760] ,score 73,
virt-launcher-vm2-without-overcommit-hhdpj -> hpd8s7: NodeResourcesLeastAllocated, map of allocatable resources map[cpu:24000 memory:135044558848], map of requested resources map[cpu:9770 memory:6150946816] ,score 77,

"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="NodePreferAvoidPods" node="harvester-bk6zp" score=1000000
"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="NodePreferAvoidPods" node="harvester-zwvbr" score=1000000
"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="NodePreferAvoidPods" node="hpd8s7" score=1000000

"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="PodTopologySpread" node="harvester-bk6zp" score=200
"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="PodTopologySpread" node="harvester-zwvbr" score=200
"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="PodTopologySpread" node="hpd8s7" score=200

"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="TaintToleration" node="harvester-bk6zp" score=100
"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="TaintToleration" node="harvester-zwvbr" score=100
"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="TaintToleration" node="hpd8s7" score=100

"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="NodeResourcesBalancedAllocation" node="harvester-bk6zp" score=62
"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="NodeResourcesBalancedAllocation" node="harvester-zwvbr" score=68
"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="NodeResourcesBalancedAllocation" node="hpd8s7" score=63

"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="ImageLocality" node="harvester-bk6zp" score=54
"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="ImageLocality" node="harvester-zwvbr" score=54
"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="ImageLocality" node="hpd8s7" score=54

"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="InterPodAffinity" node="harvester-bk6zp" score=0
"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="InterPodAffinity" node="harvester-zwvbr" score=0
"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="InterPodAffinity" node="hpd8s7" score=0

"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="NodeResourcesLeastAllocated" node="harvester-bk6zp" score=75
"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="NodeResourcesLeastAllocated" node="harvester-zwvbr" score=73
"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="NodeResourcesLeastAllocated" node="hpd8s7" score=77

"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="NodeAffinity" node="harvester-bk6zp" score=0
"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="NodeAffinity" node="harvester-zwvbr" score=0
"Plugin scored node for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" plugin="NodeAffinity" node="hpd8s7" score=0

"Calculated node's final score for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" node="harvester-bk6zp" score=1000491
"Calculated node's final score for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" node="harvester-zwvbr" score=1000495
"Calculated node's final score for pod" pod="default/virt-launcher-vm2-without-overcommit-hhdpj" node="hpd8s7" score=1000494

@rebeccazzzz, @guangbochen I think this issue can be closed directly(as the KB already merged), but it seems Docs pipeline has been removed?
I don't think QA needs to validate such issues (like this one), but in the current pipeline process, can we just close it?

This is a kube-scheduler behavior, and please refer to the KB article How does Harvester schedule a VM for a detailed explanation. Feel free to reopen this issue if you have any further questions; thanks.


Improve clangd configuration

I added support for this extension. Very convenient feature to work with C / C++.
Made by analogy with texlab

Thanks :)


Unable to pull image

When I try to pull image using command docker pull eu.gcr.io/opsgy-com/loki-rule-operator:v0.5.0, it says
Error response from daemon: pull access denied for eu.gcr.io/opsgy-com/loki-rule-operator, repository does not exist or may require 'docker login': denied: Permission denied for "v0.5.0" from request "/v2/opsgy-com/loki-rule-operator/manifests/v0.5.0".

Looking at https://console.cloud.google.com/gcr/images/opsgy-com/EU/loki-rule-operator it show this error
Project not found or deleted

Closing issue as the image is available now.


Support github actions natively

It would be great if the ConsoleReporter could add additional output lines using the github action format when running in github actions (there is an env var to detect that). This way, violations could appear as annotations in the diff UI, but we would still have the full console report in the checks tab (which is useful when you have lots of violations, as annotations are limited and so they would not all appear if you have lots of them)

@stof, they are some reporters available. Can you show me an exemple of result for github actions ? The ecma report is not good ?

@Ciloe see https://github.com/symfony/symfony/pull/38 which implements that in Symfony for one of its lint commands
the format looks like that:
::error file=some/file.twig, line=12, col=3::some message

Property values and the message need to escape some chars. and properties can be omitted.
the emacs (and not ecma) reporter won't work for that, because the format is not the same.
And as I said, these special errors should be rendered in addition to a human-readable text output (visible in the checks tab of the PR) because annotations are limited so if you have lots of violations, you will need to check the raw logs to see them all (and having to unescape the special chars of the annotations syntax won't be human-friendly).
The pattern I saw in various tools implementing this is to output the full human-readable report, and then put all github annotations at the end. this way, you can read the report without being distracted by the annotations, and you can simply stop scrolling the logs when you reach the annotations (or jump over all of them at once).

Closed with https://github.com/friendsoftwig/twigcs/pull/186.


When the VUE version of v2.0

Whether the framework7 v2 is listed on the schedule

I imagine F7Vue 2 will be released within a few days of F7 2

Hopefully F7Vue 2 will be released next month


[FEATURE] Configuration Update

Proposed Semver Increment Bump: [MAJOR/MINOR/PATCH]
Patch
Changes Proposed in this Pull Request (List new items in CHANGELOG.MD)

Configuration System broken down into smaller, manageable parts.

drawls Much Better my young apprentice.


Improve error message when /app/your_server.hs is not found or not executable

We shouldn't be segfaulting here, we should just say that the binary isn't executable

If the file is not found, we should say:

/app/your_server.sh not found

If the file is found but not executable, we should say:

/app/your_server.sh is not an executable file

When attempting to terminate, we shouldn't segfault and we should just exit without an error.

This is to be fixed in https://github.com/codecrafters-io/tester-utils/tree/master/executable. Assigning this to you @ryan-gang


Too many errors!

[Enter feedback here]

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

ID: aecf9610-b6e2-75fc-a674-869d9b95702c
Version Independent ID: 360def71-eacf-185b-4f6d-41e60e57e610
Content: Tutorial: Create an Android app that uses the Microsoft identity platform for authentication - Microsoft identity platform
Content Source: articles/active-directory/develop/tutorial-v2-android.md
Service: active-directory
Sub-service: develop
GitHub Login: @mmacy
Microsoft Alias: hahamil

@MalvinOsborne Thanks for your feedback! .  Can you please more details where are you getting errors ?

@MalvinOsborne @SaurabhSharma-MSFT This open issue on Android quickstart might be related:
#72118: New implementations of adding MSAL to an Android application will not build using the current documentation. The following needs to be added to the project build.gradle
@MalvinOsborne, can you let us know whether the issue described in the quickstart similar to your issue with this tutorial?
Cc: @iambmelt @Om83 @hamiltonha

@mmacy  Thanks
@MalvinOsborne Can you please provide your comments on the above ask.


add public_raw_download

This add the new column public_raw_download to the study table and the interactions with the GUI. Note that to solve https://github.com/biocore/qiita/issues/2679 we still need to fix the RawDownload handler, which will happen in a follow up PR.
This is how it looks:

Codecov Report

Merging #2714 into dev will increase coverage by <.01%.
The diff coverage is 94.59%.

@@            Coverage Diff             @@
##              dev    #2714      +/-   ##
==========================================
+ Coverage   94.34%   94.34%   +<.01%
==========================================
  Files         166      166
  Lines       19788    19824      +36
==========================================
+ Hits        18668    18702      +34
- Misses       1120     1122       +2

Impacted Files
Coverage Δ

qiita_db/test/test_study.py
99.77% <100%> (ø)
:arrow_up:

qiita_db/study.py
95.24% <100%> (+0.09%)
:arrow_up:

qiita_pet/handlers/api_proxy/tests/test_studies.py
99.48% <100%> (+0.03%)
:arrow_up:

qiita_pet/handlers/api_proxy/studies.py
87.09% <71.42%> (-0.62%)
:arrow_down:

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 0144eb3...7911e43. Read the comment docs.

Turns out that the number of changes to allow public raw data download was much smaller than expected so just pushed to this PR.


Error in starting project

Getting the following error, seems to be related to Hawk.
Any help?
const Hoek = require('hoek');
^^^^^
SyntaxError: Use of const in strict mode.
at Module._compile (module.js:439:25)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/usr/local/lib/node_modules/hawk/lib/index.js:5:33)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
Use of const in strict mode. (CLI v1.7.14)
Your system information:
Cordova CLI: 6.1.0
Ionic CLI Version: 1.7.14
Ionic App Lib Version: 0.7.0
OS: Distributor ID:	Ubuntu Description:	Ubuntu 14.04.4 LTS
Node Version: v0.10.25

What command are you running to get this error?

I was running the command "ionic start myapp". This was later solved by updating node to version 4.

Ah yes that node version is quite old. Going to close this, but please let us know if you're still having issues, thanks!


v6: history cannot work in the case of asynchronous

this is the demo: https://codesandbox.io/s/charming-solomon-16zgq
when i use
setTimeout(()=>{
  history.push('/login')
})

enter address: https://16zgq.csb.app
result:

when i use:
history.push('/login')

enter address: https://16zgq.csb.app
result:

I need to use it in the axios interceptor, when the status code is 401, I need to jump to the login page, I don’t know what to do

You should put that check and that call inside your React component so it's a part of the render cycle. Otherwise, it's just going to run whenever it can and that may not coincide with a render. Hence your out of date display.

https://codesandbox.io/s/charming-solomon-16zgq
export default function App() {
  useMemo(() => {
    setTimeout(() => {
      history.push("/login");
    });
  }, []);

  useEffect(() => {
    setTimeout(() => {
      history.push("/login");
    });
  }, []);

  return (
    <div className="App">
      <HashRouter>
        <Routes>
          <Route path={"/login"} element={<Login />} />
          <Route path={"/"} element={<Navigate to={"/home"} />} />
          <Route path={"/home"} element={<Home />} />
        </Routes>
      </HashRouter>
    </div>
  );
}

I put it in useMemo and useEffect, it's not working.
In the above code, I used setTimeout to simulate the interceptor
I will use the axios interceptor in the global environment to decide whether to jump to the login page.
axios.interceptors.response.use(
  response => {},
  error => {
    const { status } = error.response
    if (status == 401) {
      history.push("/login");
    }
  },
)

I should have coding it wrong, can you show me the way?
my English is not good, sorry


plot_sky crashes with matplotlib>v3.4.0 and astroplan v0.8

Calling plot_sky from astroplan v0.8 with matplotlib > 3.4 triggers a TypeError
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
Cell In [147], line 1
----> 1 plot_sky(FixedTarget(coord=source_altaz, name=source_name), Observer.at_site('Roque de los Muchachos'), time, north_to_east_ccw=False)
      3 plt.legend(loc='center left', bbox_to_anchor=(1.25, 0.5))
      4 plt.show()

File ~/Applications/mambaforge/envs/astro/lib/python3.10/site-packages/astropy/units/decorators.py:316, in QuantityInput.__call__.<locals>.wrapper(*func_args, **func_kwargs)
    314 # Call the original function with any equivalencies in force.
    315 with add_enabled_equivalencies(self.equivalencies):
--> 316     return_ = wrapped_function(*func_args, **func_kwargs)
    318 # Return
    319 ra = wrapped_signature.return_annotation

File ~/Applications/mambaforge/envs/astro/lib/python3.10/site-packages/astroplan/plots/sky.py:120, in plot_sky(target, observer, time, ax, style_kwargs, north_to_east_ccw, grid, az_label_offset, warn_below_horizon, style_sheet)
    118 # Set up axes & plot styles if needed.
    119 if ax is None:
--> 120     ax = plt.gca(projection='polar')
    121 if style_kwargs is None:
    122     style_kwargs = {}

TypeError: gca() got an unexpected keyword argument 'projection'

caused by the deprecation and later removal of the keywords associated to plt.cga()
see https://matplotlib.org/stable/api/prev_api_changes/api_changes_3.4.0.html#pyplot-gca-and-figure-gca-keyword-arguments
The deprecation notice using matplotlib v3.4 read in fact as follows,

Calling gca() with keyword arguments was deprecated in Matplotlib 3.4.
Starting two minor releases later, gca() will take no keyword arguments.
The gca() function should only be used to get the current axes,
or if no axes exist, create new axes with default keyword arguments.
To create a new axes with non-default arguments,
use plt.axes() or plt.subplot().

So solution to this problem is to:

require a matpltlib version way more recent than the one you are currently using as the bottom limit in your setup.cfg (v1.4)
modifying the plot_sky function to do ax = fig.add_subplot(projection='polar') instead of ax = plt.gca(projection='polar')

I noticed that this doesn't happen and the function behaves as expected if I use the development version.
I guess you either fixed this bug or modified the code for other reasons and you fixed it without realizing it was there.
What about a bugfix release v0.8.1?

On Thu, Jun 29, 2023 at 04:21 Brett M. Morris @.***>
wrote:

Hi @HealthyPear https://github.com/HealthyPear, thanks for the heads
up. I think we're probably due for v0.9 anyways. @wtgee
https://github.com/wtgee – any objections?

No objections here! It would be nice to get #555 in before a release, which
I could try to work on this weekend.
—

Reply to this email directly, view it on GitHub
https://github.com/astropy/astroplan/issues/561#issuecomment-1613270149,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAARIUF62KCCUQ2B5A42FQLXNWFOZANCNFSM6AAAAAAZYJCBSY
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
~Wilfred Tyler Gee

I stumbled upon this issue again, so since months have passed if I were you I'd just go for a bugfix release (0.8.1)

With matplotlib 3.8.1 and astoplan 0.9.1 this bug is solved - closing.


Update Disable-CsOnlineSipDomain.md

To fix: https://github.com/MicrosoftDocs/office-docs-powershell/pull/7520#issuecomment-824962428.

Docs Build status updates of commit bebbeb7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Disable-CsOnlineSipDomain.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit fdc47e5:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit ec0147b:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit d90a842:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Disable-CsOnlineSipDomain.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Enable-CsOnlineSipDomain.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@get-itips

@Kateyanne Please merge this PR. Thanks

Docs Build status updates of commit f89ebef:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Disable-CsOnlineSipDomain.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Enable-CsOnlineSipDomain.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Checking for config params fixing #2193

@Kartones CR this, please.
@santisaez could you check those are the params you'd set? (see  app/controllers/admin/users_controller.rb extra_* methods).

Retest this, please.

Frontend tests were OK :+1: (details)

+1
PS: I want to build a small wrapper class to stop this madness of config handling and nulls and missing fields

This is the default look, without setting :geocoder and :datasource_search keys in the config:

extra_geocodings_enabled() is working as expected, if geocoder key is enabled the option appears:

But something is wrong with extra_tweets_enabled(), although the config keys are added it's not displaying the option, seems it's failing looking for config keys in the tree.
This is the config for Twitter I'm currently using:
  datasource_search:
    twitter_search:
      standard:
        auth_required:  true
        username:       'xxx'
        password:       'xxx'
        search_url:     'xxx'
        ratelimit_active:       true
        ratelimit_ttl:          4
        ratelimit_concurrency:  8
        ratelimit_wait_secs:    0.5
      customized_user_list: ['xxx']
      customized_orgs_list: ['xxx']
      entity_to_config_map: [ { twitter: 'twitter_conf'}, { xxx: 'xxx' } ]
      customized:
        twitter_conf:
          auth_required:  true
          username:       'xxx'
          password:       'xxx'
          search_url:     'xxx'
          ratelimit_active:       true
          ratelimit_ttl:          4
          ratelimit_concurrency:  8
          ratelimit_wait_secs:    0.5
        srogers_twitter_conf:
          auth_required:  true
          username:       'xxx'
          password:       'xxx'
          search_url:     'xxx'
          ratelimit_active:       true
          ratelimit_ttl:          4
          ratelimit_concurrency:  8
          ratelimit_wait_secs:    0.5

It works for me :-\

Twitter check checks not only for username key presence but also not empty value. For example, username: '' won't enable twitter. Could that be the problem?

:+1: it's working!
Sorry it was an issue with a duplicated entry for datasource_search in my open-source deploy, it has been removed from the template to avoid more issues in the future ;-)


GUVNOR-2773 : [Guided Decision Table] ValidationWebWorkerServlet fails to load web worker

https://issues.jboss.org/browse/GUVNOR-2773
Depends on:
https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/pull/343
Fixing this by merging drools-wb-verifier-web-worker and drools-wb-verifier-backend. -backend only had one class. I originally followed the approach where client side GWT generation and backend are in different files, but since this is not a "real" GWT application that produces a .war having both the servlet and code generation in one module should be ok.

Hi @Rikkola . Thanks for the fix. Just question about the fix. The problem was that maven-resources-plugin didn't copied the resources from drools-wb-verifier-backend into drools-wb-verifier-webworker during copy-resources goal?

@jomarko The problem was probably that the drools-wb-verifier-backend and drools-wb-verifier-web-worker were not build in the correct order or by the same slave. Not entirely sure how the build servers did this.
But because of this the resource that maven-resources-plugin was trying to copy was not where it was supposed to be.
The thing is, can't really test this locally. It has always worked in my local builds. Now that it is merged the next builds will show if this actually was the issue and this fixes the issue.


Unable to sign request without credentials set

Greetings ! I've been unable to open a connection to an RDS Aurora database, and I'm no expert on AWS API, so I might've been missing something obvious...
But it seems to me like Aws::RDSDataService::Client requires a credentials parameter. The readme doesn't specify how these credentials are supposed to be given. I'm not sure it can be done through the config file.
I've been able to solve the issue by patching this gem, by editing lib/active_record/connection_adapters/aurora_serverless/client.rb and adding the following line just before the instantiation of the Aws::RDSDataService::Client:
  options[:credentials] = Aws::Credentials.new options[:access_key]["id"], options[:access_key]["secret"]

I am then able to add my credentials to my config file as such:
aurora: &aurora
  adapter: aurora_serverless
  region: 'eu-west-2'
  access_key:
    id: "access_key_id"
    secret: "secret_access_key"
  resource_arn: "---"
  secret_arn: "---"

And it seems to work (I don't have access to any aws resource yet, but it seems to work).
I'm wondering:

If there's another way to do that, shouldn't we talk about it in the README ?
Or should I make a PR so we can work on implementing that in the gem ? And if so, any hints on how you'd want this to be done ?

Interesting, in my code I am not using credentials, only secret_arn and resource_arn described in the usage section. https://github.com/customink/activerecord-aurora-serverless-adapter#usage
Your usage may be different tho and highlight some more docs. I suspect you are using the gem on something that does not have an IAM Role? On EC2, Containers, Lambda, we use that along with some policies to ensure the workload can access things. More details here that like should be in the Usage section. https://technology.customink.com/blog/2020/01/03/migrate-your-rails-app-from-heroku-to-aws-lambda/


Indents ignored due to TTML parsing not handling local scoped xml:space="preserve"

Have you read the FAQ and checked for duplicate open issues?
yes
What version of Shaka Player are you using?
v3.0.6
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from master?
Yes
Are you using the demo app or your own custom app?
Both
If custom app, can you reproduce the issue using our demo app?
Yes
What browser and OS are you using?
Win & Mac
Chrome v87, Firefox v83, Edge v87
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
N/A
What are the manifest and license server URIs?
https://dash.akamaized.net/dash264/CTA/imsc1/IT1-20171027_dash.mpd
What did you do?

Play this stream
Enable the English subtitle stream
Seek to 2m15s.
Observe the subtitles until approx 2m30s

What did you expect to happen?
Increasing indent of the subtitles by 4 chars per iteration
What actually happened?
No change in indentation, all "Indent X" text appears in the same place, without moving to the right.

Note our custom player's Text Displayer overcomes other basic styling issues observed in the Shaka Demo App.

My analysis has pinpointed the lack of handling for localized scope of xml:space="preserve":

I have an idea for a fix which needs some refinement before a PR can be submitted:
In parseCue_() we can grab knowledge of any locally overriding xml:space setting but defaulting to the global scope.
    ...
    let spaceStyle = null;
    spaceStyle = cueElement.getAttribute('xml:space') ||
        (whitespaceTrim ? 'default' : 'preserve');

    const localWhitespaceTrim = spaceStyle == 'default';
    ...


added delete religion route

Looks good!
Only thing i see is the name deletedReligionID  for variable name. Does the .destroy() function return the deleted id?

No, turns out it returns amount deleted. When I tested it I deleted with id 1 and mistook amount for id.


Use current docker images for development

This PR drops the specific point revisions in the docker images in favour of the more recent major version tags.  No functional change, aside from a much more recent database image being tested.
Your pull request should…

[x] have a concise title
[x] ~close an accompanying issue if one exists~
[x] be against the correct branch
[x] ~include migration scripts and documentation, if appropriate~
[x] pass automated tests
[x] have a clean commit history
[x] have proper commit messages (title and body) for all commits

I'm fine updating the major versions too, though I don't know what would be common in the community.


Doesn't work in ESM due to __dirname

Hi, when importing the lib directly into ES module Node.js project, it doesn't work, because there is no __dirname.
Faulty code:
https://github.com/dotenvx/dotenvx/blob/main/src/shared/packageJson.js#L4
Code on my end:
import dotenvx from "@dotenvx/dotenvx"
dotenvx.config()

Error:
App threw an error during load
ReferenceError: __dirname is not defined in ES module scope
This file is being treated as an ES module because it has a '.js' file extension and '/Users/[redacted]/package.json' contains "type": "module". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.

what node version and dotenvx version are you on, @Igloczek?
I can't reproduce this yet on v21.6.1 and<EMAIL_ADDRESS>// index.mjs
import dotenvx from "@dotenvx/dotenvx"
dotenvx.config()

console.log(`Hello ${process.env.HELLO}`)

{
  "type": "module",
  "dependencies": {
    "@dotenvx/dotenvx": "^0.24.0"
  }
}

no errors for me

closing. let me know if still experiencing the issue and if so what versions you are on. thank you.

what electron version are you on? https://www.electronjs.org/docs/latest/tutorial/electron-timelines
from there I can probably get to a point of reproducing the issue.

Electron v28.2.0 on Node.js v20.11.0

i haven't been able to duplicate this yet. @Igloczek are you able to set up a basic example and link to it as a github repo?

going to close. if anyone else runs into this, please let me know.


Unveilhooks not always firing data-bg correctly?

Describe the bug
I am trying to use the unveilhooks plugin to lazyload images with data-bg, however it seems that the images do not always load and display consistently.  I'm using lazysizes 5.2.0, but
To Reproduce
Here is a test URL of a static version of the page I wish to use lazysizes on, this is using data-bg:
https://www.kawai-global.com/menutest/product_static.htm
Here is the actual page which is currently using background:url() to load the images, but looks ugly (because the images display as they are loading):
https://www.kawai-global.com/product/
Steps to reproduce the behavior:
Refresh the page at the above URL a few times.
Here is video capture that demonstrates what happens:
https://drive.google.com/file/d/15rYL2PebCGkJ5xF5IWUs9li02CpdHRSn/view?usp=sharing
What is the expected behavior
The images should always display.
What happened instead
The images sometimes do not display correctly.
In what environment (browser/device etc.) does this bug happen/not happen:
Windows 10 desktop, Chrome 84.0

Hey did you find any solution to this? I have this issue now. 25% of the time the images do not load and give no hint as to why.

Hello,
No, unfortunately, I couldn't find a solution, so just disabled lazyloading on those images... ;(
@aFarkas closed this issue, so I guess he does not believe it is a problem, or that there is a problem with my implementation.
I noticed that the test URL I provided previously was invalid, however the URL should be working again now.
If you're able to find a solution, please let me know!

@jmbattle0
Yes, it was offline and I don't believe that it is a script failure. There are many problems that can cause this problem.
For example some carousels do copy the markup change it and throw it back in using innerHtml while images are loading. This results to the situation that the DOM references break. Solution use a proper carousel script or delay lazysizes start after the carousel.
In your case it is much simpler. You load every script separate. This results in the situation that you first load lazysizes which starts working and transforms the header images and then after that situation you load unveilhooks. Solution: Combine your scripts or at least load unveilhooks before lazysizes.

@aFarkas
Thank you for your reply.

Solution: ...load unveilhooks before lazysizes.

That worked, thank you very much!

So far so good for me too. I was dreading moving to a different library as my bg images have hover images too which seems tricky to manage.


feat(19217): add custom plan on atlas

https://kontur.fibery.io/Tasks/Task/Add-custom-plan-on-Atlas-19217

Summary by CodeRabbit
Release Notes

New Features

Added new localization entries for "Contact sales" and "Book a demo."
Introduced functions to open the Intercom interface for user support.
Added a new constant for a sales representative scheduling link.

Improvements

Updated external link detection to include "mailto" links.
Enhanced the PaymentPlanCard component for better handling of payment plan configurations.
Improved the structure and rendering logic of the PaymentPlanCard.

Bug Fixes

Resolved layout issues in the PricingContent component by adjusting flex properties.

Documentation

Updated constants and types for better clarity and usage across components.

PR foxes


求加一个定时关闭的功能

仅仅提交一个建议。Submit just one proposal.
在你提交此建议前请注意：Please note before you submit this proposal:

详细阅读椒盐音乐帮助内容（应用设置-帮助）。Read more about the SaltPlayer help content (app Settings - Help).

反馈时候请注意：When giving feedback, please note:

尽量详细的描述。Be as detailed as possible.
不接收任何 UI 样式调整相关的反馈，出现此类 issue 会被关闭（如 “我不喜欢此设计” 、“我觉得这样设计更好” 、“还没原来好看” 等等类似反馈）。Do not receive any feedback on UI style changes, and the issue will be closed (" I don't like this design ", "I think this design is better", "it's not as good as the original", etc.).

建议内容 The proposals
<在此输入你的建议 Enter your suggestions here>

谢谢建议，会在后续开发此功能，暂时被搁置。

可以关注 #2


CentralManager().startDiscovery() got "StateError"

Hello. I am new for both Flutter and bluetooth_low_energy package. I was trying to call startDiscovery() but seems I got an error with "StateError: No Element".

May I kindly ask how should I fix this issue?
Many thanks in advance!

Forgot to mention. I am using:
bluetooth_low_energy package v6.0.2
Flutter v3.24.3
Dart v3.5.3
DevTools v2.37.3

Sorry my bad... Seems after adding CentralManager().discovered.listen() handler then it works.


Specify account_identifier for IPLists

Looking at the API documentation for Lists (e.g. https://api.cloudflare.com/#rules-lists-create-list), the POST needs to be sent to an endpoint using an account_identifier.
I'm experiencing issues by using an email & API key combination that has access to multiple accounts.
How can / should I specify the correct account identifier I wish to make IP list changes?

For setting the account ID in the client, you can use UsingAccount() in your client instantiation.
package main

import (
	"context"
	"fmt"
	"log"

	"github.com/cloudflare/cloudflare-go"
)

func main() {
	api, err := cloudflare.New(apiKey, user, cloudflare.UsingAccount(accountID))
	if err != nil {
		log.Fatal(err)
	}

	l, err := api.ListIPLists(context.TODO())
	if err != nil {
		log.Fatal(err)
	}

	fmt.Println(l)
}

Thanks, I was able to get it working now!


Table "click-move" not working

@jfo8000 :100: :+1: Thanks a lot for providing this windows version of ScratchJr! It is really great
I have it successfully running on my surface pro. Together with the keyboard and Touchpad it is working great.
However, in tablet mode without a keyboard the click-move is not working on the touchscreen.
Simple click and also the virtual keyboard work properly.
Would it be feasible to add the click-move also in tablet using the touchscreen.
Perhaps the tab-move = click-move events are not the save using a mouse or the touch screen.
Thanks best,
ruebox

Hello, I have the same issue.
It's good to know that this is known and not a bug. At first I though that was related with my touchscreen laptop. I think that because this is for kids, a full touch interface could be great.
Thanks for all the effort, we are enjoying the software.
Best


Examples of ITK.js

Thanks to your help, I have become more comfortable with the use of vtk and itk.
Now I want to use itk.js with vtk.js. However, there seems to be few examples of this.
Do you plan to create or release examples of itk.js?
Thank you!!

Hi @rjsgml5698, your feedback on your experiences are very helpful.
Yes, we will be creating some examples. xref #198 #141 #74

Hi @thewtex , I'm sorry to use this 2-years  old issue for my need but I'm currently a bit lost. Can you please give me some pointers where I can find the examples you mentioned? Thanks a lot in advance!


Unsupported geometry type error when using OpenFileGDB driver and GDAL >=3.6.2

The OpenFileGDB driver now supports write operations with GDAL >= 3.6.x.
Expected behavior and actual behavior:
I am trying to use fiona to write to a .gdb. I expect the below code to run without error, but I'm seeing that fiona was compiled against an older version of GDAL which throws an error:
import geopandas as gpd
import fiona

# Create a GeoDataFrame and save it to the File GeoDatabase
gdf = gpd.read_file(gpd.datasets.get_path("naturalearth_lowres"))
gdf.to_file("test.gdb", layer="test_fc", driver="OpenFileGDB")

Error when running this interactively:
# Traceback (most recent call last):
#   File "fiona/ogrext.pyx", line 1238, in fiona.ogrext.WritingSession.start
# File "fiona/ogrext.pyx", line 1239, in fiona.ogrext.WritingSession.start
# File "fiona/_err.pyx", line 291, in fiona._err.exc_wrap_pointer
# fiona._err.CPLE_NotSupportedError: Unsupported geometry type
#
# During handling of the above exception, another exception occurred:
#
#   Traceback (most recent call last):
#   File "<stdin>", line 1, in <module>
#   File "/home/porlando/.local/share/virtualenvs/fgdb_to_gpkg-TVksE44w/lib/python3.10/site-packages/geopandas/geodataframe.py", line 1203, in to_file
# _to_file(self, filename, driver, schema, index, **kwargs)
# File "/home/porlando/.local/share/virtualenvs/fgdb_to_gpkg-TVksE44w/lib/python3.10/site-packages/geopandas/io/file.py", line 545, in _to_file
# _to_file_fiona(df, filename, driver, schema, crs, mode, **kwargs)
# File "/home/porlando/.local/share/virtualenvs/fgdb_to_gpkg-TVksE44w/lib/python3.10/site-packages/geopandas/io/file.py", line 572, in _to_file_fiona
# with fiona.open(
#   File "/home/porlando/.local/share/virtualenvs/fgdb_to_gpkg-TVksE44w/lib/python3.10/site-packages/fiona/env.py", line 457, in wrapper
#   return f(*args, **kwds)
#   File "/home/porlando/.local/share/virtualenvs/fgdb_to_gpkg-TVksE44w/lib/python3.10/site-packages/fiona/__init__.py", line 347, in open
#   colxn = Collection(
#     File "/home/porlando/.local/share/virtualenvs/fgdb_to_gpkg-TVksE44w/lib/python3.10/site-packages/fiona/collection.py", line 237, in __init__
#     self.session.start(self, **kwargs)
#     File "fiona/ogrext.pyx", line 1247, in fiona.ogrext.WritingSession.start
#     fiona.errors.DriverIOError: Unsupported geometry type

Error when using pytest:
Edit: this GDAL compilation error is due to accidentally running pytest outside of the desired pipenv. Calling pytest from the desired pipenv produces the same Unsupported geometry type error as the interactive test above.
# fiona.errors.DriverError: OpenFileGDB driver requires at least GDAL 3.6.0 for mode 'w', Fiona was compiled against: 3.5.3

Operating System
# Ubuntu 22.04.2 LTS x86_64

Fiona and GDAL version provenance
Installed fiona from PyPi via pipenv install fiona:
# fiona==1.9.2 ; python_version >= '3.7'; pipenv version 2023.3.20

Installed GDAL from the unstable version of the ubuntugis personal package archives:
add-apt-repository ppa:ubuntugis/ubuntugis-unstable
apt-get update
apt-get install gdal-bin libgdal-dev

gdalinfo --version
# GDAL 3.6.2, released 2023/01/02

gdal-config --version
# 3.6.2

Is there anything I can do to compile fiona against the latest version of GDAL? Please let me know if I can provide any additional details.

@philiporlando the binary wheel of Fiona includes a GDAL version. You can install Fiona against a GDAL installation by not using the wheel: pip install --no-binary fiona fiona. You can check which version Fiona is using with fiona.show_versions().

@rbuffat, thanks for the suggestion!
I was able to install fiona without the binary via pipenv and it looks like it is using the newer version of GDAL:
pipenv uninstall fiona
export PIP_NO_BINARY=fiona && pipenv install fiona

import fiona
fiona.show_versions()
# Fiona version: 1.9.2
# GDAL version: 3.6.2
# PROJ version: 9.1.1
#
# OS: Linux 5.15.0-67-generic
# Python: 3.10.6

However, I'm still seeing the same error when running the reprex above:
# fiona.errors.DriverError: OpenFileGDB driver requires at least GDAL 3.6.0 for mode 'w', Fiona was compiled against: 3.5.3

Could this be a bug with fiona, or do you think I'm missing some additional environment config? Thanks again for the help!

My first thought would be that something is broken with your environment. The function for the error message uses the same methods as fiona.show_versions(): https://github.com/Toblerity/Fiona/blob/eaf6e0a5948b2b7585b7b216c90e8704e1d88904/fiona/collection.py#L116-L130

Thanks for the suggestion. I completely wiped my pipenv and started over from scratch. I installed fiona and geopandas using the --no-binary flag.
I think the previous GDAL compilation issue  was due to operator error on my part. I am using pipenv to setup my environment and pytest for testing, but I forgot to call pytest from my activated pipenv via pipenv run pytest tests. When I call pytest from my pipenv I'm getting the same unsupported geometry error that I was originally seeing when running the reprex interactively.
# E   fiona.errors.DriverIOError: Unsupported geometry type
# fiona/ogrext.pyx:1247: DriverIOError

It looks like my environment is configured correctly and fiona is using GDAL 3.6.
import fiona
fiona.show_versions()

# Fiona version: 1.9.2
# GDAL version: 3.6.2
# PROJ version: 9.1.1

# OS: Linux 5.15.0-67-generic
# Python: 3.10.6

Any support with troubleshooting this unsupported geometry type error would be greatly appreciated!

I've added some additional checks within my reprex to better understand the geometry types of our test geodataframe:
import geopandas as gpd
import fiona

gdf = gpd.read_file(gpd.datasets.get_path("naturalearth_lowres"))
print(gdf.geom_type.unique())
print(gdf.is_valid.all())
gdf.to_file(fgdb_path, layer="test", driver="OpenFileGDB")

# ['MultiPolygon' 'Polygon']
# True

It looks like all of our input geometries are valid. However, I'm seeing that there is a mix of MultiPolygon and Polygon geometries within the same vector. While both of these are listed as valid values within the GEOMETRY_TYPES dictionary, I'm beginning to wonder if mixing two different geometries within the same geodataframe may be causing problems when trying to write to File GeoDataBase. Coercing all MultiPolygons into Polygons appears to resolve the issue!!
import geopandas as gpd
import fiona

gdf = gpd.read_file(gpd.datasets.get_path("naturalearth_lowres"))

gdf = gdf.explode()
print(gdf.geom_type.unique())
print(gdf.is_valid.all())

# ['Polygon']
# True

gdf.to_file(fgdb_path, layer="test", driver="OpenFileGDB")

@philiporlando thanks for the follow up. "Unsupported geometry type" is the error Fiona propagates from OGR https://github.com/OSGeo/gdal/blob/5d75d7e95d0bc479611fb7a67f5c0e452ca36500/ogr/ogrsf_frmts/openfilegdb/ogropenfilegdblayer_write.cpp#L430. Curiously, the driver supports a "multipatch" type but not "multipolygon".
What do you see if you coerce all your data to be multipolygon instead of polygon?

@sgillies thanks for the details here.
Coercing from polygon to multipolygon is working for me!
import geopandas as gpd
from shapely.geometry.polygon import Polygon
from shapely.geometry.multipolygon import MultiPolygon

# Create a GeoDataFrame and save it to the File GeoDatabase
gdf = gpd.read_file(gpd.datasets.get_path("naturalearth_lowres"))

# Convert MultiPolygon to Polygon
# gdf = gdf.explode()

# Convert Polygon to MultiPolygon
gdf["geometry"] = [
    MultiPolygon([feature]) if isinstance(feature, Polygon) else feature
    for feature in gdf["geometry"]
]

print(gdf.geom_type.unique())
print(gdf.is_valid.all())

gdf.to_file("test.gdb", layer="test_fc", driver="OpenFileGDB")

# ['MultiPolygon']
# True

@philiporlando thanks for the followup! As you suspected, the mix of types is where trouble begins. I think Fiona could try to be better about this and offer an option to normalize geometries (towards multi) when writing, as some OGR utilities do with their -nln options. I still don't understand why this error occurs during layer creation.
Meanwhile, we have available workarounds. Are you okay with those for now?

@sgillies, an option to promote geometries to their multi equivalent would be a helpful feature. I wish I had the expertise needed to develop something like this.
Yes, I think we're good to close this issue for now. Thanks again for your help troubleshooting!


rule type_literal_in_constant_pattern in switch cases

so I have a function that basically is this
get<T>() {
 switch(T) {
  case Person:
   //code
  case Dog:
   //code
  }
}

which is called like get<Person>();
and by using the notation suggested by this rule (Person _), it does not work.
How am I supposed to change my code to be adequate to this linter rule?
Originally posted by @Fernandomr88 in https://github.com/dart-lang/lints/issues/117#issuecomment-1775789382

From @bwilkerson on the original (closed) issue:

It sounds like the rule might need to be changed to not produce a diagnostic if the value being switched over is Type.


Can't run cent init

I have installed go through brew
Verified that the go was installed properly [current file path: Users/name/go
Redirected to Users/name/go/bin/cent
when running cent the cli responds "zsh: command not found: cent"

Can you help me 'bout this please thank you
Device Used: Macbook Pro 2020 M1
Current OS version: Ventura 13.3

Thank you for getting back to me. I apologize for the delayed response. To clarify, I would like to ask if the error you reported in the issue is still occurring. If you have encountered the same problem again or if there are any new issues you would like to address, please provide me with the details. I'll be glad to assist you further.

Hi @vanzybanez ,
closing this issue as I haven't received a reply, if there is any news feel free to reopen this issue again

I have same problem:(


[iOS] Verifier App has to be Started Twice Because Screen Freezes on Intitial Mask upon the First Start

Describe the bug
When I start the iOS Verifier App it freezes at the initial Mask.  Then I have to put it in the background and start it again in order for the app to really start.
Expected behaviour
App starts right away the first time it is opened.
Technical Details
Verifier App <IP_ADDRESS> Build Version
iPhone 8 plus v. Lutz, iOS 14.4

I did not have this problem in Version 1.2.3 of the Verifier so I will close the ticket.


python2Packages.pillow: freeze at 6.2.2

Motivation for this change
fixes calibre
addresses https://github.com/NixOS/nixpkgs/commit/0e5e6b08aad464744ed5ad8e2fe79d28a4438748#commitcomment-39708178
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build calibre nixops

Argh.  Thanks @jonringer!
Should have figured there would be more breakages than nixpkgs-review would show.
Moving forward, is it a good idea to write things like pillow/6 proactively/when bumping major versions? Or just as the need arises?

@evanjs it's more for the python2/3 divide than a major version on a given package. In general we don't want many versions of the same package in python-modules, but if a given interpreter is only able to see one version, then that's alright


Quesqions about pre-process part

could u explain what the variable "malicious_entity" in "trace_parser.py" represent? （as following,if I take trace as dataset parameter, what should trace.txt be?）
def read_graphs(dataset):
malicious_entities = '../data/{}/{}.txt'.format(dataset, dataset)
f = open(malicious_entities, 'r')
malicious_entities = set()
for l in f.readlines():
malicious_entities.add(l.lstrip().rstrip())
...

Go to ThreaTrace and you will find these .txt ground truth files in the folder "groundtruth".

Thank you! I GOT IT.


Update deployer CLI examples to match airnode

This PR is about the changes made here: #869

Is there a need to add the output of npx @api3/airnode-admin --help to the admin-cli docs?


Heatmap Symmetry

The Asymmetry in the heatmap is mostly from Dong having multiple copies of variants, which is obscuring the more interesting case of variants being grouped together in some papers.
The duplicates in Dong is not a very interesting statistic to show, whereas I believe that the grouping/splitting of adjacent variants is more relevant to the about section where we describe the methods of data harmonization and curation.
Solution for the moment is to:
-Remove the asymmetry from the heatmap.
-Add a graphic displaying the grouping/splitting to our data harmonization/curation section.

Resolved by removing asymmetry from the heatmap.


svg football pitch to geojson convert

Version
4.4.0-rc.1
Reproduction link
https://www.dbface.com/assets/echarts/doc/example/map19.html#-en
Steps to reproduce
i want use to echarts.util.mapData.params.params.football but Cannot read property 'params' of undefined
What is expected?
Footballers heatmap
What is actually happening?
Cannot read property 'params' of undefined

SVG map support has been removed since v3.0. But it will be back soon!

Can you add this future on version 5.0?

SVG map support has been removed since v3.0. But it will be back soon!

Do you plan to add svg map support to the new version?

@partitect Yes. It's on the schedule of v5.1.0.


Adds maxUploadSize option

Fix for #536

Super! 👍

tests seems failing for weird reasons.
@tanmays can you test that branch? I blindly followed what you suggested :)

@flovilmart just gave a quick test and tried uploading an image to S3, it works! :)

@tanmays thanks! :tada:

LGTM. Probably we should document this new option somewhere too.

I'll document it with proper-cli if you merge that one :)


add arneja-arnav as contributor

Part of hacktoberfest 2022 program

@arneja-arnav I am happy to merge this PR for you but this repository isn't part of Hacktoberfest. Sorry for any inconvenience caused. :)

I have invited you to the organisation. Please remember to set your membership as public.

@all-contributors please add @arneja-arnav for content

@arneja-arnav if you search for 'Hacktoberfest 2022' in the search on GitHub, it should come up with plenty of hacktoberfest repositories. Make sure you are contributing to repositories that follow the Hacktoberfest guidelines and are accepted by hacktoberfest. Hope this helps, if you need any help, please let us know 🙂


Redfish boot option with IPMI verification

Continuation to https://github.com/openbmc/openbmc-test-automation/issues/1601
Add use cases to verify using IPMI

[ ] Set via redfish Interface, verify via IPMI
[ ] Set via IPMI, verify via redfish interface

[ ] https://gerrit.openbmc-project.xyz/#/c/openbmc/openbmc-test-automation/+/20184/


Publisher could not permitted to add certificates when endpoint host-name is like 'abcdef45'.

Steps to reproduce:

Login to the publisher and start to create an API.
Create endpoint as like 'https://abcdef45/'.
Then try to add the certificate by clicking on the 'Add new certificate'.
It will return an error of 'You must first enter Production/ Sandbox endpoints to add a certificate or the Endpoints you have entered are not valid.'

Reason:

But the hostname is valid according to the original specification of hostnames in (RFC 952)[1] and the subsequent specification (RFC 1123)[2].

References
[1] - https://tools.ietf.org/html/rfc952
[2] - https://tools.ietf.org/html/rfc1123

Need to check in 3.0 release after React UI revamp

fixed in 3.0.0 beta


Is this project still alive and can I add Scala to the language list ? :D

Chapter Request
Description
A clear and concise description of what the new algorithm, method or data structure would be about, including links to the relevant academic articles or sources.
Additional context
Add any other reasons why this chapter should be a higher priority.
Delete this section, if you don't think the chapter is of a high priority.

For Algorithm Archive Developers

[ ] This chapter can be added to the Master Overview (if it cannot be, explain why in a comment below -- lack of sufficient technical sources, not novel enough, too ambitious, etc.)
[ ] There is a timeline for when this chapter can be written
[ ] The chapter has been added to the Master Overview
[ ] The chapter has been written (Please link the PR)

The project is still alive, but was on life support for the past few cough years... But I will be focusing on it way, way more in 2021, so expect it to grow a lot!
As for the Scala language, there are already chapters with scala in them and a few PRs for scala. If you want to add a new language implementation, please check to make sure you are not doubling up first.

@leios thanks for clarification :D I will close this issue


--wrap support for MacOS

Hi
Looks like --wrap support for MacOS is missing.
It seems it should easy to match ELF support here.
I'd like to know, if it's something that would be accepted as PR?

Sold linker development is no longer active because Apple's linker has caught up with us in terms of speed.

Maybe this repo should be archived then?


Inject_embed: run-dartpad info string breaks syntax highlighting

From the Embedding Guide, Converting code blocks to DartPad section:

Step 2: Add a code snippet
In Markdown:
```run-dartpad:theme-light:mode-flutter:run-true
main() => print("Hello, World!");
```

Using an info string of run-dartpad rather than dart breaks syntax highlighting, both in the IDE and the generated site (users will get to see the original code block in cases where DartPad hasn't been injected yet, or hasn't been successfully injected). Users see this:

Instead of this:

Probably shouldn't happen that often, but still. /cc @kwalrath @legalcodes

It would be great if we could:

Leave the info string as dart, and
Have the option of triggering the injector by attaching classes to a parent element.

For example:

```dart
main() => print("Hello, World!");
```

Or using a Jekyll-specific syntax:
{:.run-dartpad:theme-light:mode-flutter:run-true}
```dart
main() => print("Hello, World!");
```

Jekyll renders this as:

main() => ...

I know this issue is rather old but I also encountered this problem.
Here is how I was able to solve it for my system (highlight.js v 11.5.1)
```lang-dart:run-dartpad:theme-light:width-100%:height-500px:mode-inline
enum SomeEnum {
//...
}
 ```

Highlight.js picks up the lang-dart part and the DartPad injector is happy as well.


chore(main): release 1.2.1

:robot: I have created a release beep boop
1.2.1 (2024-05-19)
Bug Fixes

Add nodejs test (#30) (50bc3ff)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/cedricziel/node-red-contrib-mattermost-app/releases/tag/v1.2.1 :sunflower:


chore: upgrade dependencies

Pull Request Test Coverage Report for Build 406

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

Totals

Change from base Build 401:
0.0%

Covered Lines:
1111

Relevant Lines:
1318

💛  - Coveralls


Update dependency eslint-plugin-prefer-let to v4

This PR contains the following updates:

Package
Type
Update
Change

eslint-plugin-prefer-let
devDependencies
major
3.0.1 -> 4.0.0

Release Notes

thefrontside/javascript (eslint-plugin-prefer-let)
v4.0.0
Compare Source

e597fa9 Support ESLint v9

Configuration
📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Self-Hosted Renovate Bot. Find all logs here.

 You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


dns.google.com

Energized Protection - block ⚡

Let's make an annoyance free, better open internet, altogether!

Issue Submit Form

  Provide the following info properly, which will help us to resolve your issue quickly.

Issue(s):
Type x in between [ ] and make sure there isn't any space between brackets. Example; for Your Selected Issue(s), type like this - [x]
You can select more than one category of issues if you need to!

[X ] Whitelist
[ ] Blacklist
[ ] App Broken
[ ] Website Broken
[ ] Request
[ ] Other Issue

Pack(s):
Write the name of the pack(s) you are using.

Pack(s) Name: BluGo

Extension(s):
Also name the extension(s) if you are using any. If you don't then leave it blank.

Extension(s) Name:

Domain(s):
If you are submitting this issue for whitelist/blacklist issue, send us the domain(s) for whitelisting/blacklisting here. Kindly use the Code Tag to prevent tracking.

Domain(s):

dns.google.com

Your Config:
Just to ensure there is no issues or conflicts with other app/software/magisk module/extension/source list.
Make sure you are running Energized Protection Service only.

Client:  PiHole 5.14.2

Version:

Detail:
Write us a lil bit more about your issue or query. You can attach any screen shot or log of the issue or advert, this will help to highlight it.

Your Issue Detail:
dns.google.com is a legit Google domain. false positive

Thank you for making Energized Protection great, with your kind help!
A project by Ador with ❤

This is a wild guess why this is on the list:
Android devices are known to ignore custom DNS-servers and fallback to google DNS-servers.
By doing this, the actively bypass any kind of ad/tracking/malware protection for example a pihole offers.
Google hardcoded this behavior into Android to ensure that no simple host or DNS blocking will prevent you from seeing google ads or getting tracked by google and their partners.
However, an entry like dns.google.com will not prevent this behavior because Android devices use the actual IP (<IP_ADDRESS> and <IP_ADDRESS>) to connect to the google dns servers.
To prevent dns leakage for android devices you need to block all outgoing DNS requests (i.e. out with target port 53) for all devices except your pihole.
This entry should indeed be removed from the list as it is completely useless.


Add hasExtra return value to IsValueSubtypeOf()

@rafael-atticlabs This is my change to enable ComputeView to determine whether a value can be returned as-is or whether it needs to be narrowed. I ended up with the idea that we needed to bits of info: whether a value was a subtype of something and whether it had extra fields. It seems like the easiest thing to do was to add a return value to IsValueSubtypeOf() to return that additional piece of information.

@arv fyi

I'm going to defer to @arv, here but WRT API, I feel like the public signature for IsValueSubtype should not change here but rather add another public call like IsValueSubtypeDetailed() which returns two bools and IsValueSubtype just calls. That way the existing call sites which don't care don't look so strange.

@arv PTAL


Consider using a factory library to generate model instances for testing purposes

Proposed Changes
We should consider using something like https://factoryboy.readthedocs.io/en/stable/orms.html to create model instances for testing purposes.
Justification
This would:

Speed up test development and abstract away all the trivial stuff into the factory classes.
Make tests clearer and more succinct.
Make it easier to cope with schema changes

See also #1999, #1034.

We have a lot of low-level factories today. Factories for things like Devices will be much more complex. As we introduce new models we add factories if feasible. The spirit of this is complete and will evolve. Including using DB snapshots for other performance considerations.


Remove universe schema json

We should remove the schema for universe repository and packages. After 0.4.0, Cosmos will be responsible for managing packages and interfacing with Universe. That information is not needed in the CLI.

this is still being referenced in the bundle code. assuming we are going to bring back bundle we should keep this, no?


refactor(collectBy): use groupBy for grouping

Hello and thank you for your contribution. Not sure if you've seen this comment but it may be worth reading it if you (or other reviewers) didn't. I personally don't have an issue with this refactor as long as it doesn't incur a performance penalty.

I didn't see that comment. Thanks for linking. I am not sure about the performance cost of this refactor. Feel free to close this if it is not something desirable. 😄

Let's wait for some more comments on this :)

Let's leave this for the 2.0 refactor.  At that point we'll be rewriting all the functions anyway using modern JS features, and we will probably have to do regular perf testing.
It's not that I think this is a bad idea, just that the timing is not right for it.  When we do go to more modern JS, we can look at where the simplicity of function layering outweighs a minor perf loss.

@ycmjason
We'll defer the merge after our v1.0 release (which we'll eventually happen in 2022). At which point we'll start working on our v2.0 which will include a modern rewrite and be the best opportunity for this kind of refactor.


Will there be a doc of this project?

Docs will be added gradually. A detailed README will be available with release 0.1.1.  Module, class, method, and function docstrings will be gradually added in future. However, there is no plan for standalone docs in the foreseeable future.


Updates and clean up - Validate Configuration UI

Made some changes to the Validate Config UI - cleaned up a number of small items that needed to be fixed for better usability.
BEFORE

AFTER

The time input fields in the constraint cards (in tera-constraint-group-form) are not scaling in the row to 100% correctly. This is due to the fact that the InputNumber component is over-riding the button-row class. The bounds fields are, they are using a different component.

The time input fields in the constraint cards (in tera-constraint-group-form) are not scaling in the row to 100% correctly. This is due to the fact that the InputNumber component is over-riding the button-row class. The bounds fields are, they are using a different component.

@ngraham76 using CSS grids might be a better choices for those blocks, and we can place elements more easily.


#4209: Pulsar IO Source Connector for Couchbase

Fixes #4209
<--
Contribution Checklist

Name the pull request in the form "[Issue XYZ][component] Title of the pull request", where XYZ should be replaced by the actual issue number.
Skip Issue XYZ if there is no associated github issue for this pull request.
Skip component if you are unsure about which is the best component. E.g. [docs] Fix typo in produce method.

Fill out the template below to describe the changes contributed by the pull request. That will give reviewers the context they need to do the review.

Each pull request should address only one issue, not mix up code from multiple issues.

Each commit in the pull request has a meaningful commit message

Once all items of the checklist are addressed, remove the above text and this checklist, leaving only the filled out template below.

(The sections below can be removed for hotfixes of typos)
-->
(If this PR fixes a github issue, please add Fixes #<xyz>.)
Fixes #
(or if this PR is one task of a github issue, please add Master Issue: #<xyz> to link to the master issue.)
Master Issue: #
Motivation
Explain here the context, and why you're making that change. What is the problem you're trying to solve.
Modifications
Describe the modifications you've done.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API: (yes / no)
The schema: (yes / no / don't know)
The default values of configurations: (yes / no)
The wire protocol: (yes / no)
The rest endpoints: (yes / no)
The admin cli options: (yes / no)
Anything that affects deployment: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

@ambition119 @murong00 @tuteng if any of you have time, can you help reviewing this connector? since you guys have written quite a lot of connectors :)

@sreev Thank you for being able to submit this PR, a little suggest. Hope you can add CBAbstractSourceTest or CBByteArraySourceTest , doc about Couchbase like site2/docs/io-connectors.md, site2/docs/io-kafka.md.
You can
git config --global user.email "your email"

then Your commit avatar will show highlights.

Closed as stale. Sad that we don't catch up the effort then.


'TextField' focus does not change border color (TW starter kit)

Provide a general summary of the issue here
When focusing the TextField component in your Tailwind CSS starter kit, the border-gray-600 class is not applied (strangely for SearchField it works as expected) - this seems to affect the starter kit for download as well as the repository, but not the online demo 🤔
https://github.com/adobe/react-spectrum/assets/122524301/efc9a088-4612-49b3-8d6b-e4b693cb6a0d
🤔 Expected Behavior?
Dark color (border-gray-600) being applied to the border when TextField receives focus
😯 Current Behavior
Light color (border-gray-300) remains unchanged when TextField receives focus
💁 Possible Solution
No response
🔦 Context
No response
🖥 Steps to Reproduce
Just try out the starter kit from the website or inside the repository, go to TextField component, click inside - nothing changes
Version
3.33.0 / 1.2.0
What browsers are you seeing the problem on?
Firefox, Chrome
If other, please specify.
No response
What operating system are you using?
macOS
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

const inputStyles = tv({   extend: focusRing,   base: 'border-2 rounded-md',   variants:    {     isFocused: fieldBorderStyles.variants.isFocusWithin,     isDisabled: fieldBorderStyles.variants.isDisabled,     isInvalid: fieldBorderStyles.variants.isInvalid     // ...fieldBorderStyles.variants,   } }); This seems to fix it for me, something is wrong with spreading tho idk what


speedment.Gui connect button throws SQLException: Table name pattern can not be NUL...

All Select Database form fields are filled.
Here you can read about possible solution https://github.com/JetBrains/Exposed/issues/32
But speedment.Gui supports only host, no connection URL:
jdbc:mysql://localhost/test?nullNamePatternMatchesAll=true
mysql:mysql-connector-java:6.0.3
gradle.plugin.com.speedment.gradle:SpeedmentGradlePlugin:2.2.3
com.speedment:speedment:3.0.0-EA
:speedment.Gui
2016-11-11T20:03:06.862Z INFO  [JavaFX Application Thread] (c.s.i.u.a.LoggingAdapterImpl) - JGoogleAnalytics: Tracking Asynchronously focusPoint=GuiStarted
2016-11-11T20:03:41.272Z INFO  [JavaFX Application Thread] (c.s.i.c.d.AbstractRelationalDbmsHandler) - Reading metadata from com.speedment.internal.ui.config.DbmsProperty@692899f8
2016-11-11T20:03:41.286Z INFO  [JavaFX Application Thread] (c.s.i.c.d.AbstractRelationalDbmsHandler) - Parsing Schema 'sakila'
2016-11-11T20:06:48.663Z INFO  [JavaFX Application Thread] (c.s.i.c.d.AbstractRelationalDbmsHandler) - Reading metadata from com.speedment.internal.ui.config.DbmsProperty@692899f8
2016-11-11T20:06:48.667Z INFO  [JavaFX Application Thread] (c.s.i.c.d.AbstractRelationalDbmsHandler) - Parsing Schema 'sakila'

The newest MySQL driver does not work yet. There is an issue (#190) on this. Please use mysql:mysql-connector-java:5.x.x until this is fixed.
Also, the gradle 2.x plugin is unlikely to work with Speedment 3.x


feature/initial-build-pipeline

What
Added Dockerfile, Jenkinsfile and deployment scripts. Also vendored external dependencies.
How to review

Check the build pipeline for this branch, it should be passing
Check the application has been deployed to the correct environment with the correct configuration

Who can review
Anyone but myself.

LGTM 👍


fix(charts): YAML indentation for API resources

Tested and verified.
Thanks for catching this @nlamirault!


Running on device causes Lost connection to device. Exited on startup

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

Create a new flutter project via vscode or command line (flutter create) with any newer version of Flutter
Run it on an Android device in debug mode
About 50% of the time it fails

Actual results
I have already filed an issue on the vscode dart side here: https://github.com/Dart-Code/Dart-Code/issues/4726
While attempting to start a Flutter application, running from VSCode only sometimes (about a 50% chance) simply fails after the APK gets installed, the app's splash screen shows, and the VM service gets connected to with the message
Lost connection to device.
Exited

My entire development team is encountering this issue on multiple computers (all Mac) across multiple types of Android devices.
Logs

Logs
Since this is executed from VSCode only, I've attached logs that were requested over on the vscode tracker. (Dart: Capture Debugging Logs command)
https://gist.github.com/Moncader/6f5072d72679da2cf5d9f34b6aa78b83

Flutter Doctor output

Doctor output

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.13.0, on macOS 13.5.1 22G90 darwin-arm64, locale en-CA)
[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] VS Code (version 1.82.0)
[✓] Connected device (3 available)
[✓] Network resources

• No issues found!

cc @DanTup

I tried reproducing this on a MacBook w/ Ventura 13.4 on two Android devices I have, but without success. I used current stable Flutter 3.13.3 and a newly created application using the Flutter: New Project command and chose Application. I ran each app and ensured the app fully loaded and remained visible for a few seconds before stopping the session.

Xiaomi Mi A2 (10/10 no errors with SDK DAPs ("dart.previewSdkDaps": true), 5/5 no errors with legacy DAPs ("dart.previewSdkDaps": false))
Google Pixel 4a (10/10 no errors with SDK DAPs, 5/5 no errors with legacy DAPs)

@Moncader one thing I noticed is that you were already using legacy debug adapters in your first try, so testing with "dart.previewSdkDaps": false, wouldn't have changed anything. Is it possible you can test with "dart.previewSdkDaps": true, to see if it makes any difference? (I suspect not, but it's worth testing because there are some differences between the debug adapters).

@DanTup
Manually setting it to true seems to have fixed the issue.
I assume since this is a 'preview' flag, it's not enabled by default hence why all our team members have the same issue?

I'm not sure how previewSdkDaps is related to the tool but I tried configuring it to true/false and running it on my device (Realme 6, Android 11), but could not reproduce this issue. Checking this on the latest Flutter stable 3.13.3.
@Moncader I notice there is a difference between Flutter/Dart extension versions:
Your:
Dart Code extension: 3.73.20230906
Flutter extension: 3.73.20230904 (activated)

Mine:
Dart: v3.72.2
Flutter: v3.72.0

Are you using pre-release versions? Do you team members also use those versions?

@huycozy
Yes I do seem to be on the preview version.
However, my teammates are not and are on the same version as you are.

Manually setting it to true seems to have fixed the issue.

Ah, that's interesting! I did test with both legacy and new SDK DAPs but couldn't reproduce on either. If this solves the issue I would recommend just setting that flag for all the team. In the near future, the SDK DAPs will be the default and everyone will use them. The legacy DAPs are not being further developed.

I assume since this is a 'preview' flag, it's not enabled by default hence why all our team members have the same issue?

This change is rolling out gradually, so on the latest Flutter version around 30% of users are currently opted-in. The flag was added before the rollout began and was kept as a way of explicitly opting in/out during the migration (if it's unset, then it will be controlled by the experiment % that is being increased over time).

I'm not sure how previewSdkDaps is related to the tool but I tried configuring it to true/false and running it on my device

The "debug adapters" (which I often refer to as "DAPs" collectively after the Debug Adapter Protocol, because it's easier to say than "DAs") are adapters that translates between VS Code (and other DAP-compliant editors) and the Dart VM's debugger protocol ("The VM Service Protocol").
The original implementation of the debugger adapters was written in TypeScript specifically for the Dart VS Code extension and lives/ships in the VS Code extension. The new debug adapters live inside the Dart/Flutter SDKs so that a) they can be written in Dart and use existing libraries for communicating with the VM Service, and b) they can be easily used be other DAP-compliant editors (other than VS Code) without needing to clone the VS Code extension source.
The VS Code extension is switching users over to the new SDK DAPs gradually (while we monitor for errors/bug reports) and the previewSdkDaps flag allows you to explicitly enable/disable them. If it's set to false you'll get the legacy debug adapters (from the Dart VS Code extension)  and if you set to true you'll get the new SDK debug adapters (from the "dart debug_adapter" and "flutter debug_adapter" commands). If it's unset, it will be controlled by the "experiment" which has a percentage of users that is slowly increasing.

Are you using pre-release versions? Do you team members also use those versions?

I don't think being on the pre-release VS Code extension will make a difference here because there should be no differences in the debug adapters between them. That said, I don't know what might be causing this - it's odd for a whole team to be affected by it on different devices and it to reproduce on a newly created app (which rules out anything specific in their app). My guess is that there is some subtle bug or race condition in the legacy DAPs that's being triggered here, but I've not been able to reproduce it and I don't see anything obviously bad in the logs.
If the issue definitely doesn't occur on the new SDK DAPs, I'd be inclined to close this though. Everyone will soon be on the new DAPs and can enable them today if they happen to hit an issue like this.
However, if this issue does start coming up in the SDK DAPs, it definitely requires tracking down.

Thank @DanTup for these insights. Based on the information provided and confirmation from @Moncader that the issue can be solved using the DAPs SDK, I'm going to close this issue.
@Moncader Please feel free to write a comment if you have this issue with SDK DAPs, and I will reopen this for investigation. Thank you!