text:
树莓派做客户端，iptable 送流量到dokodemo-door ,客户端报UDP端口被占用。

Please skip to the English section below if you don't write Chinese.
中文：
提交 Issue 之前请先阅读 Issue 指引，然后回答下面的问题，谢谢。
除非特殊情况，请完整填写所有问题。不按模板发的 issue 将直接被关闭。

你正在使用哪个版本的 V2Ray？（如果服务器和客户端使用了不同版本，请注明）
3.6

你的使用场景是什么？比如使用 Chrome 通过 Socks/VMess 代理观看 YouTube 视频。
树莓派做WS+TLS+Caddy+Dokodemo-Door 路由上网,基本功能正常，不确定UDP是否成功转发。

你看到的不正常的现象是什么？（请描述具体现象，比如访问超时，TLS 证书错误等）
日志报错UDP端口被占用，但其实并没有发现有其他程序监听12345端口。
Feb  8 09:41:49 raspberrypi v2ray[387]: 2018/02/08 09:41:49 [Warning]: App|Proxyman|Inbound: connection ends > Proxy|Dokodemo: connection ends > Transport|Internet|UDP: failed to bind source address > address already in use

你期待看到的正确表现是怎样的？
希望修复这个问题，让UDP顺利转发。

请附上你的配置（提交 Issue 前请隐藏服务器端IP地址）。
服务器端配置:
{
"inbound": {
"port": 10000,
"listen":"127.0.0.1",
"protocol": "vmess",
"settings": {
"clients": [
{
"id": "",
"alterId": 64
}
]
},
"streamSettings": {
"network": "ws",
"wsSettings": {
"path": "/ray"
}
}
},
"outbound": {
"protocol": "freedom",
"settings": {}
},
"routing": {
"strategy": "rules",
"settings": {
"rules": [
{
"type": "field",
"ip": [
"0.0.0.0/8",
"10.0.0.0/8",
"100.64.0.0/10",
"127.0.0.0/8",
"169.254.0.0/16",
"172.16.0.0/12",
"192.0.0.0/24",
"192.0.2.0/24",
"192.168.0.0/16",
"198.18.0.0/15",
"198.51.100.0/24",
"203.0.113.0/24",
"::1/128",
"fc00::/7",
"fe80::/10"
],
"outboundTag": "blocked"
}
]
}
}
}
客户端配置:
{
"inbound": {
"port": 1080,
"listen": "127.0.0.1",
"protocol": "socks",
"settings": {
"auth": "noauth",
"udp": true
}
},
"inboundDetour": [
{
"domainOverride":["tls","http"],
"port":12345,
"protocol":"dokodemo-door",
"settings":{
"network": "tcp,udp",
"followRedirect": true
}
}
],

"outbound": {
"mux": {"enabled": true},
"tag":"proxy",
"protocol": "vmess",
"settings": {
"vnext": [
{
"address": "domain.net",
"port": 443,
"users": [
{
"id": "",
"alterId": 64
}
]
}
]
},
"streamSettings": {
"network": "ws",
"security": "tls",
"tlsSettings": {
"serverName": "domain.net"
},
"wsSettings": {
"path": "/ray"
}
}
},
"outboundDetour": [
{
"tag": "direct",
"protocol": "freedom",
"settings": {
"response": null
}
},
{
"tag": "blockout",
"protocol": "blackhole",
"settings": {
"response": {
"type": "http"
}
}
}
],
"dns": {
"servers": [
"8.8.8.8",
"8.8.4.4",
"localhost"
]
},
"routing": {
"settings": {
"rules": [
{
"type": "field",
"domain": [
"www.google.com.hk",
"googleapis.cn",
"google.cn",
"ggpht.cn",
"chrome.google.com",
"googleusercontent.com",
"android.clients.google.com",
"gvt1.com",
"ångströ.com"
],
"outboundTag": "proxy"
},
{
"ip": [
"0.0.0.0/8",
"10.0.0.0/8",
"100.64.0.0/10",
"127.0.0.0/8",
"169.254.0.0/16",
"172.16.0.0/12",
"192.0.0.0/24",
"192.0.2.0/24",
"192.168.0.0/16",
"198.18.0.0/15",
"198.51.100.0/24",
"203.0.113.0/24",
"::1/128",
"fc00::/7",
"fe80::/10"
],
"domain": null,
"type": "field",
"port": null,
"outboundTag": "direct"
},
{
"type": "chinaip",
"outboundTag": "direct"
},
{
"type": "chinasites",
"outboundTag": "direct"
}
],
"domainStrategy": "IPIfNonMatch"
},
"strategy": "rules"
}
}
6)  请附上出错时软件输出的错误日志。在 Linux 中，日志通常在 /var/log/v2ray/error.log 文件中。
树莓派客户端错误日志:
Feb  8 09:41:49 raspberrypi v2ray[387]: 2018/02/08 09:41:49 [Warning]: App|Proxyman|Inbound: connection ends > Proxy|Dokodemo: connection ends > Transport|Internet|UDP: failed to bind source address > address already in use
Feb  8 09:41:49 raspberrypi v2ray[387]: 2018/02/08 09:41:49 [Warning]: App|Proxyman|Inbound: connection ends > Proxy|Dokodemo: connection ends > Transport|Internet|UDP: failed to bind source address > address already in use
Feb  8 09:41:55 raspberrypi v2ray[387]: 2018/02/08 09:41:55 [Warning]: App|Proxyman|Inbound: connection ends > Proxy|Dokodemo: connection ends > Transport|Internet|UDP: failed to bind source address > address already in use
Feb  8 09:41:55 raspberrypi v2ray[387]: 2018/02/08 09:41:55 [Warning]: App|Proxyman|Inbound: connection ends > Proxy|Dokodemo: connection ends > Transport|Internet|UDP: failed to bind source address > address already in use
Feb  8 09:42:06 raspberrypi v2ray[387]: 2018/02/08 09:42:06 [Warning]: App|Proxyman|Inbound: connection ends > Proxy|Dokodemo: connection ends > Transport|Internet|UDP: failed to bind source address > address already in use
Feb  8 09:42:06 raspberrypi v2ray[387]: 2018/02/08 09:42:06 [Warning]: App|Proxyman|Inbound: connection ends > Proxy|Dokodemo: connection ends > Transport|Internet|UDP: failed to bind source address > address already in use
Feb  8 09:42:12 raspberrypi v2ray[387]: 2018/02/08 09:42:12 [Warning]: App|Proxyman|Inbound: connection ends > Proxy|Dokodemo: connection ends > Transport|Internet|UDP: failed to bind source address > address already in use
Feb  8 09:42:12 raspberrypi v2ray[387]: 2018/02/08 09:42:12 [Warning]: App|Proxyman|Inbound: connection ends > Proxy|Dokodemo: connection ends > Transport|Internet|UDP: failed to bind source address > address already in use
Feb  8 09:42:17 raspberrypi v2ray[387]: 2018/02/08 09:42:17 [Warning]: App|Proxyman|Inbound: connection ends > Proxy|Dokodemo: connection ends > Transport|Internet|UDP: failed to bind source address > address already in use
Feb  8 09:42:17 raspberrypi v2ray[387]: 2018/02/08 09:42:17 [Warning]: App|Proxyman|Inbound: connection ends > Proxy|Dokodemo: connection ends > Transport|Internet|UDP: failed to bind source address > address already in use
服务器端日志
Feb  8 09:39:15 instance-1 rc.local[657]: 2018/02/08 09:39:15 114.249.36.38:43874 accepted tcp:v1.mux.cool:9527
Feb  8 09:39:57 instance-1 rc.local[657]: 2018/02/08 09:39:57 114.249.36.38:43932 accepted tcp:v1.mux.cool:9527
Feb  8 09:39:58 instance-1 rc.local[657]: 2018/02/08 09:39:58 219.234.220.80:43940 accepted tcp:v1.mux.cool:9527
Feb  8 09:40:14 instance-1 rc.local[657]: 2018/02/08 09:40:14 219.234.220.80:43978 accepted tcp:v1.mux.cool:9527
Feb  8 09:41:16 instance-1 rc.local[657]: 2018/02/08 09:41:16 114.249.36.38:44058 accepted tcp:v1.mux.cool:9527
Feb  8 09:41:34 instance-1 rc.local[657]: 2018/02/08 09:41:34 219.234.220.80:44064 accepted tcp:v1.mux.cool:9527
Feb  8 09:41:34 instance-1 rc.local[657]: 2018/02/08 09:41:34 219.234.220.80:44076 accepted tcp:v1.mux.cool:9527
Feb  8 09:41:35 instance-1 rc.local[657]: 2018/02/08 09:41:35 219.234.220.80:44096 accepted tcp:v1.mux.cool:9527
Feb  8 09:41:36 instance-1 rc.local[657]: 2018/02/08 09:41:36 219.234.220.80:44116 accepted tcp:v1.mux.cool:9527
Feb  8 09:41:40 instance-1 rc.local[657]: 2018/02/08 09:41:40 219.234.220.80:44144 accepted tcp:v1.mux.cool:9527
Feb  8 09:41:42 instance-1 rc.local[657]: 2018/02/08 09:41:42 219.234.220.80:44180 accepted tcp:v1.mux.cool:9527
Feb  8 09:41:46 instance-1 rc.local[657]: 2018/02/08 09:41:46 219.234.220.80:44210 accepted tcp:v1.mux.cool:9527
Feb  8 09:41:48 instance-1 rc.local[657]: 2018/02/08 09:41:48 219.234.220.80:44290 accepted tcp:v1.mux.cool:9527
Feb  8 09:42:06 instance-1 rc.local[657]: 2018/02/08 09:42:06 219.234.220.80:44538 accepted tcp:v1.mux.cool:9527
Feb  8 09:42:12 instance-1 rc.local[657]: 2018/02/08 09:42:12 114.249.36.38:44566 accepted tcp:v1.mux.cool:9527
Feb  8 09:42:26 instance-1 rc.local[657]: 2018/02/08 09:42:26 219.234.220.80:44708 accepted tcp:v1.mux.cool:9527
Feb  8 09:43:16 instance-1 rc.local[657]: 2018/02/08 09:43:16 114.249.36.38:44806 accepted tcp:v1.mux.cool:9527
Feb  8 09:44:07 instance-1 rc.local[657]: 2018/02/08 09:44:07 219.234.220.80:44908 accepted tcp:v1.mux.cool:9527
Feb  8 09:44:11 instance-1 rc.local[657]: 2018/02/08 09:44:11 114.249.36.38:44918 accepted tcp:v1.mux.cool:9527
Feb  8 09:44:29 instance-1 rc.local[657]: 2018/02/08 09:44:29 219.234.220.80:44968 accepted tcp:v1.mux.cool:9527
Feb  8 09:44:29 instance-1 rc.local[657]: 2018/02/08 09:44:29 219.234.220.80:44972 accepted tcp:v1.mux.cool:9527
Feb  8 09:44:35 instance-1 rc.local[657]: 2018/02/08 09:44:35 219.234.220.80:45016 accepted tcp:v1.mux.cool:9527
Feb  8 09:44:56 instance-1 rc.local[657]: 2018/02/08 09:44:56 114.249.36.38:45048 accepted tcp:v1.mux.cool:9527
Feb  8 09:45:17 instance-1 rc.local[657]: 2018/02/08 09:45:17 114.249.36.38:45088 accepted tcp:v1.mux.cool:9527
Feb  8 09:45:23 instance-1 rc.local[657]: 2018/02/08 09:45:23 219.234.220.80:45114 accepted tcp:v1.mux.cool:9527
Feb  8 09:46:11 instance-1 rc.local[657]: 2018/02/08 09:46:11 114.249.36.38:45198 accepted tcp:v1.mux.cool:9527
Feb  8 09:46:12 instance-1 rc.local[657]: 2018/02/08 09:46:12 219.234.220.80:45208 accepted tcp:v1.mux.cool:9527
Feb  8 09:46:30 instance-1 rc.local[657]: 2018/02/08 09:46:30 219.234.220.80:45236 accepted tcp:v1.mux.cool:9527
Feb  8 09:47:20 instance-1 rc.local[657]: 2018/02/08 09:47:20 114.249.36.38:45324 accepted tcp:v1.mux.cool:9527
Feb  8 09:48:11 instance-1 rc.local[657]: 2018/02/08 09:48:11 114.249.36.38:45378 accepted tcp:v1.mux.cool:9527
Feb  8 09:49:46 instance-1 rc.local[657]: 2018/02/08 09:49:46 114.249.36.38:45446 accepted tcp:v1.mux.cool:9527
Feb  8 09:51:46 instance-1 rc.local[657]: 2018/02/08 09:51:46 114.249.36.38:45490 accepted tcp:v1.mux.cool:9527
Feb  8 09:52:11 instance-1 rc.local[657]: 2018/02/08 09:52:11 114.249.36.38:45514 accepted tcp:v1.mux.cool:9527

请附上访问日志。在 Linux 中，日志通常在 /var/log/v2ray/access.log 文件中。

其它相关的配置文件（如 Nginx）和相关日志。
报端口占用的时候检查过树莓派其他端口占用情况，并未有其他程序占用12345端口。

root@raspberrypi:/var/log# netstat -anp|grep 12345
tcp6       0      0 :::12345                :::*                    LISTEN      387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57444    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57466    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57384    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60171     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60153     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60206     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60161     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57420    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60268     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60157     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60256     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57392    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57381    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60269     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57404    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57367    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57462    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60216     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:59919     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60220     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60155     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60016     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60205     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60209     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60124     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60240     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60005     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60221     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60128     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:59951     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60266     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60244     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57374    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57388    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60258     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:59900     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60139     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57380    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60004     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:59902     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57428    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57377    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:59886     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60154     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57376    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57382    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60204     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:59897     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60044     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57421    FIN_WAIT2   -
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60134     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60129     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60126     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57405    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60219     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60156     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57390    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57431    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57403    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57427    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60218     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60267     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60006     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60257     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60202     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60265     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60132     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60217     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60203     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60184     TIME_WAIT   -
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57406    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:59906     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60228     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60215     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:59895     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60210     TIME_WAIT   -
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60002     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:59874     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60190     CLOSE_WAIT  387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57465    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60255     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60262     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60243     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60270     ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.105:57437    ESTABLISHED 387/v2ray
tcp6       0      0 172.29.121.177:12345    172.29.121.96:60200     ESTABLISHED 387/v2ray
udp6       0      0 :::12345                :::*                                387/v2ray**

可以贴一下你的 iptables配置吗？你的这个配置实现透明代理功能了没有？

我比较怀疑UDP的原目标数据是否被正确读取，是否可以贴一下完整的debug log？
建议给出 iptables -vL -t $TABLE
另外 https://github.com/v2ray/v2ray-core/blob/52ad41cda393792632ff9d3f13184ace51f7ca3a/transport/internet/udp/hub_linux.go， https://github.com/v2ray/v2ray-core/blob/90925bdf7a49bfcddf3fd6e8ef75276cc23d3cac/transport/internet/udp/hub.go 这里没有相关的调试输出，建议 @VictoriaRaymond 加上，帮助对于这个问题的调试

root@raspberrypi:~# iptables -vL -t nat
Chain PREROUTING (policy ACCEPT 785 packets, 133K bytes)
pkts bytes target     prot opt in     out     source               destination
491 28863 V2RAY      tcp  --  any    any     anywhere             anywhere
Chain INPUT (policy ACCEPT 876 packets, 98329 bytes)
pkts bytes target     prot opt in     out     source               destination
Chain OUTPUT (policy ACCEPT 2692 packets, 208K bytes)
pkts bytes target     prot opt in     out     source               destination
Chain POSTROUTING (policy ACCEPT 2692 packets, 208K bytes)
pkts bytes target     prot opt in     out     source               destination
Chain V2RAY (1 references)
pkts bytes target     prot opt in     out     source               destination
0     0 RETURN     all  --  any    any     anywhere             16.127.196.35.bc.googleusercontent.com
0     0 RETURN     all  --  any    any     anywhere             172.28.0.0/16
7  2223 RETURN     all  --  any    any     anywhere             172.29.0.0/16
0     0 RETURN     all  --  any    any     anywhere             172.30.0.0/16
0     0 RETURN     all  --  any    any     anywhere             192.168.0.0/24
0     0 RETURN     all  --  any    any     anywhere             192.168.1.0/24
0     0 RETURN     all  --  any    any     anywhere             192.168.89.0/24
0     0 RETURN     all  --  any    any     anywhere             192.168.88.0/24
0     0 RETURN     all  --  any    any     anywhere             192.168.86.0/24
484 26640 REDIRECT   tcp  --  any    any     anywhere             anywhere             redir ports 12345
root@raspberrypi:~# iptables -vL -t mangle
Chain PREROUTING (policy ACCEPT 69588 packets, 38M bytes)
pkts bytes target     prot opt in     out     source               destination
71633   39M V2RAY      all  --  any    any     anywhere             anywhere
Chain INPUT (policy ACCEPT 71062 packets, 39M bytes)
pkts bytes target     prot opt in     out     source               destination
Chain FORWARD (policy ACCEPT 9 packets, 360 bytes)
pkts bytes target     prot opt in     out     source               destination
Chain OUTPUT (policy ACCEPT 77480 packets, 38M bytes)
pkts bytes target     prot opt in     out     source               destination
Chain POSTROUTING (policy ACCEPT 77530 packets, 38M bytes)
pkts bytes target     prot opt in     out     source               destination
Chain V2RAY (1 references)
pkts bytes target     prot opt in     out     source               destination
0     0 RETURN     all  --  any    any     anywhere             172.30.0.0/16
41889   35M RETURN     all  --  any    any     anywhere             172.29.0.0/16
0     0 RETURN     all  --  any    any     anywhere             172.28.0.0/16
0     0 RETURN     all  --  any    any     anywhere             192.168.0.0/16
0     0 RETURN     all  --  any    any     anywhere             16.127.196.35.bc.googleusercontent.com
2045 1117K TPROXY     udp  --  any    any     anywhere             anywhere             TPROXY redirect 0.0.0.0:12345 mark 0x1/0x1

请尝试向
"inboundDetour": [ { "domainOverride":["tls","http"], "port":12345, "protocol":"dokodemo-door", "settings":{ "network": "tcp,udp", "followRedirect": true }
加上 "listen": "0.0.0.0"
强制其监听IPv4

root@raspberrypi:/etc/v2ray# /usr/bin/v2ray/v2ray --config /etc/v2ray/config.json
V2Ray v3.6 (die Commanderin) 20180112
An unified platform for anti-censorship.
2018/02/09 10:35:39 [Warning]: Core: V2Ray started
2018/02/09 10:35:55 [Warning]: App|Proxyman|Inbound: connection ends > Proxy|Dokodemo: connection ends > Transport|Internet|UDP: failed to bind source address > address already in use
2018/02/09 10:36:06 [Warning]: App|Proxyman|Inbound: connection ends > Proxy|Dokodemo: connection ends > Transport|Internet|UDP: failed to bind source address > address already in use
2018/02/09 10:37:37 [Warning]: App|Proxyman|Inbound: connection ends > Proxy|Dokodemo: connection ends > Transport|Internet|UDP: failed to bind source address > address already in use
强制IPV4之后还是有这样的日志出来，ebug 日志内容太多了不便于分析。

请尝试使用本版本的V2Ray并将输出调整至debug。 应该会出现和 Original Destination 相关的输出 https://github.com/v2ray/v2ray-core/releases/tag/v3.8.1

使用3.8.1版本后经过十几分钟观察,迅雷大流量下载,日志里未输出udp端口被占用的消息.

晚上又看了一下，还是有报udp端口被占用，新版程序指明是到网关的udp数据包，比较奇怪


text:
Pre-fill destination airport in ManEntry based on flight-plan destination

TTSIA

added, closing

source: gharchive/issue

repo: vNAAATS/vatsim-NAAATS

license_type: permissive

license_source: github-api


text:
Cleanup tests, avoid dependency on

Connected to #57

This change is

Review status: 0 of 3 files reviewed at latest revision, 1 unresolved discussion.

vaadin-dropdown-menu.html, line 513 at r1 (raw file):

        }

        _setFocused(focused) {

why is this removed?

Comments from Reviewable

Review status: 0 of 2 files reviewed at latest revision, 1 unresolved discussion.

vaadin-dropdown-menu.html, line 513 at r1 (raw file):
Previously, manolo (Manuel Carrasco Moñino) wrote…
why is this removed?

Oops, that was unintentional. Reverted.

Comments from Reviewable

Reviewed 2 of 3 files at r1.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

test/dropdown-menu-test.html, line 325 at r2 (raw file):

        });

        it('Should set tabindex attribute to -1 on the native input', () => {

Why is this test removed? It was added to check if the workaround to prevent tabbing into native input is applied.

Comments from Reviewable

Review status: 1 of 2 files reviewed at latest revision, 2 unresolved discussions.

test/dropdown-menu-test.html, line 325 at r2 (raw file):
Previously, web-padawan (Sergey Kulikov) wrote…
Why is this test removed? It was added to check if the workaround to prevent tabbing into native input is applied.

Oh, sorry, not intentional removal. Reverted.

Comments from Reviewable

Reviewed 1 of 1 files at r2, 1 of 1 files at r3.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable

Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from Reviewable

source: gharchive/pull-request

authors: manolo platosha web-padawan

repo: vaadin/vaadin-dropdown-menu


text:
Remove autofocus from username field. Closes #33

This removes the auto focus from the username fields - as discussed in #33
Thanks!

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant peterblazejewicz

repo: vaadin/vaadin-login


text:
IntelliJ IDEA complains about not being able to resolve Lumo custom properties

When you use --lumo-* custom properties in a CSS file in IntelliJ IDEA (at least in Ultimate edition), it will highlight the variable with a red underline and a message like:

Cannot resolve '--lumo-success-color' custom property

I did a quick test by manually duplicating the variable declarations to a css file within node_modules/@vaadin/vaadin-lumo-styles and that seems to be enough to let InteliJ properly discover the variables and does not complain about their usage in your project anymore.
I propose that all the styles in this repo would be refactored to *.css source files (to resolve this issue) and then those sources can be used in a build step to generate ES modules (or HTML imports) as needed so that the CSS code doesn't need to be duplicated to several files.
This idea is also mentioned as part of issue #90 but these are 2 different issues which may be possible to solve in different ways too.

If/when this is implemented, it should also be done for vaadin-material-styles (or issue created there).

As a workaround I created this gist which contains a copy of all the Lumo CSS custom properties in a plain CSS file. Just save this as a CSS file somewhere in your project and IntelliJ IDEA should be able to autocomplete the Lumo custom properties and not complain about them being unresolved.

repo: vaadin/vaadin-lumo-styles


text:
chore: first template adjustments

This is an initial take on adjusting the foundry-template to the Vac's smart contract unit's needs. In a nutshell what this does is:

Update README to not refer to upstream repo where not necessary
Removes PRBergTest library from dependencies
Removes FUNDING.qml
Adjust CI actions

There are more things to be done and decided on in follow-up commits.

@rymnc thank you for your feedback.
I've done the following additional changes:

Added your suggested changes in scripts
Removed some more boilerplate in tests that we don't need for now
Added a PULL_REQUEST_TEMPLATE.md with an initial (but simple) checklist
Generated a first gas snapshot

license: MIT


text:
Add native script derivation

Native script derivation
Keeping in Draft state as the Ledger Cardano app doesn't yet support this feature
Given a script in the form defined as NativeScript returns a script hash in form of a hex encoded string.
The INS assigned to the derive script hash call is 0x21.
After parsing the NativeScript I split the resulting ParsedNativeScript into two subsets.

ParsedComplexNativeScript are scripts that have nested "subscripts" (types: ALL, ANY, N_OF_K).
The interaction on ledger should display the series of messages:

Information about the script (e.g. Script - ALL, Confirm 12 scripts)
Then each individual script
And a final finished message

The calls to Ledger reflect this structure:

The call is initiated with P1=0x01 and sends the type of script in a number (uint8) representation according to the cddl
, the number (uint32) of all subscripts contained within the script, and in case of script type N_OF_K also the number (uint32) of required scripts.
Then the individual subscripts are processed

It's Ledger's responsibility to keep track of the current depth and index of currently processed script.

ParsedSimpleNativeScript are scripts without "subscripts" (types: PUBKEY_DEVICE_OWNED, PUBKEY_THIRD_PARTY, INVALID_BEFORE, INVALID_HEREAFTER).
The interaction on ledger should only display one message containing the information about the script.
For example: Script - Key hash, 80f9e2c88e6c817008f3a812ed889b4a4da8e0bd103f86e7335422aa
Therefore for this subset of scripts only call to ledger is made:
The call initiated with P1=0x02. The data sent begins with a number (uint8) representation of the script type
and then one of the following depending on the type:

For PUBKEY_DEVICE_OWNED first a byte (uint8) of value 1, to distinguish between the two PUBKEY script types, and then it's the byte representation of the public key path
For PUBKEY_THIRD_PARTY first a byte (uint8) of value 2, to distinguish between the two PUBKEY script types, and then it's the byte representation of the provided key hash
For INVALID_BEFORE and INVALID_HEREAFTER a number (uint64)

After the whole native script is sent to the Ledger device it will send an explicit finish call (P1 = 0x03) with one uint8 value specifying the display format of the native script hash on the Ledger.

WIll be merged via #130.

authors: KubqoA janmazak

repo: vacuumlabs/ledgerjs-cardano-shelley


text:
Exposing currentPageIndex

It allows you to bind the currentPageIndex as a prop on the Carousel component. With this change you can handle the current page outside the component (p.e a menu linked with the Carousel)

There are methods for setting pages: goTo, goToPrev, goToNext

authors: LeVarez vadimkorr

repo: vadimkorr/svelte-carousel


text:
Task1-4

Commit to Main

@Sandhyathota1
Task -1
Missing annotation
Code verified. default activity names

Task -2
Code verified. default activity names

Task -3
Code verified. default activity names

No need for another sequence for give annotations
Task -4
Code verified. default activity names and code not excuted correctly.

When you raise the pr that pr no is updated in tracker also


text:
Configure cargo to use -Ctarget-cpu=native

Objective
Tell rustc to use native CPU features when building the project. Especially useful for the benchmarks.
Solution
Add a .cargo/config.toml with the following contents:
[build]
rustflags = ["-Ctarget-cpu=native"]

This makes it so that built binaries can possibly be not portable.

True, but I didn't think it would matter since the config only applies to those building valence from the repo AFAIK. But I can still see that coming back to bite us.

repo: valence-rs/valence


text:
Default config directory

I just learned about this plugin (No topic on the forums!) - you've essentially consolidated my entire D&D workflow by now, which is fantastic.
It would be great if you could implement the same feature that Obsidian Leaflet has to change the default plugin directory, so we can have cross-device syncing. Thanks loads!

Forgot to do this yesterday, sorry :) should be working in 1.9.0


text:
Removed Node.js version 10 support

Node.js version 10 is deprecated.
https://nodejs.org/en/about/releases/

Hey, thanks for the PR. I had the patches around for months so I split them from #52 and landed them.

repo: validator/gulp-html


text:
chore: migrate existing geth + dek accounts to the Keychain based wallet

Description
Builds on top of #2519 to add backward compatibility for existing user accounts.
This transparently migrates the existing geth + dek accounts into the Keychain based wallet.
The geth account is re-imported from the mnemonic the next time the user enters their PIN to perform an action that requires it (signing, updating their PIN, etc).
The dek is re-imported on the first launch if a user account is already set. It doesn't require the PIN (by design).
Tested

Updated unit tests for the KeychainWallet
Manually upgrading the app from the the geth based wallet to the new Keychain based wallet on both iOS and Android.

How others should test

Have an existing app <= v1.33 with a user account set
Ensure TXs can be sent and and the seed phrase can be seen.
Update the app with version >= 1.34 (containing this commit)
Make sure all things related to signing work as expected

sending transaction
swaping
signing with dapps
phone number verification
updating the PIN

Related issues

Part of #2392

Backwards compatibility
Yes

Hey @MuckT, We have verified above task on iOS TestFlight Release build V1.34.0 & updated status in test rails.
Observation :

User is able to perform transaction from previous builds and also able to upgrade to latest build
Note : For Android we are blocking the upgrade test case as we are not able to update it due to work profile issue
User is able to send request and complete the transaction by sending the money
User is able to connect to Dapps and swap the funds
User is able to confirm Phone number via create and restore account flow
User is able to update the PIN to latest PIN

Test rail links:
iOS 14: https://valoraapp.testrail.io/index.php?/tests/view/41889
Devices: iPhone 12(14.7.1)
CC: @jeanregisser
Thanks..!!

Hey @MuckT, We have verified above task on iOS Test Flight Release build V1.34.0 & updated status in test rails.
Observation :

User is able to perform transaction from previous builds and also able to upgrade to latest build
Note : For Android we are blocking the upgrade test case as we are not able to update it due to work profile issue
User is able to send request and complete the transaction by sending the money
User is able to connect to Dapps and swap the funds
User is able to confirm Phone number via create and restore account flow
User is able to update the PIN to latest PIN

Test rail links:
iOS 15: https://valoraapp.testrail.io/index.php?/tests/view/41920
Devices: iPhone 13 mini(15.1.1)
CC: @jeanregisser
Thanks..!!

authors: ValoraQA jeanregisser

repo: valora-inc/wallet


text:
Fix development mode

Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.
Fixes
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an x in the box that applies

[ ] Non-breaking fix (non-breaking change which fixes an issue)
[ ] Breaking fix (breaking change which fixes an issue)
[ ] Non-breaking feature (non-breaking change which adds functionality)
[ ] Breaking feature (breaking change which adds functionality)
[ ] Refactor (non-breaking change which changes implementation)
[ ] Messy (mixture of the above - requires explanation!)

Checklist
Put an x in the boxes that apply.

[ ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the main branch (left side). Also you should start your branch off our main.
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have locally run services that could be impacted and they do not present failures derived from my changes
[ ] Public-facing documentation has been updated with the changes affected by this PR. Even if the provided contents are not in their final form, all significant information must be included.
[ ] Any backwards-incompatible/breaking change has been clearly documented in the upgrading document.

LGTM. Have you tested that with a service?
Do some tests need to be added in case the dev mode breaks again?
Also please provide details on how to use the dev mode after the new changes and what to expect.

Yes
The actual deployments cannot be testes in the CI at the moment so no
I've updated the documentation, you can take a look here - https://github.com/valory-xyz/open-autonomy/blob/123e085959f44f07db895b3a7cc44893e6a8e47d/docs/advanced_reference/developer_tooling/dev_mode.md

LGTM. Have you tested that with a service?
Do some tests need to be added in case the dev mode breaks again?
Also please provide details on how to use the dev mode after the new changes and what to expect.

Yes
The actual deployments cannot be testes in the CI at the moment so no
I've updated the documentation, you can take a look here - https://github.com/valory-xyz/open-autonomy/blob/123e085959f44f07db895b3a7cc44893e6a8e47d/docs/advanced_reference/developer_tooling/dev_mode.md

Isn't the dev flag deprecated?
https://github.com/valory-xyz/open-autonomy/blob/123e085959f44f07db895b3a7cc44893e6a8e47d/docs/advanced_reference/developer_tooling/dev_mode.md?plain=1#L22

LGTM. Have you tested that with a service?
Do some tests need to be added in case the dev mode breaks again?
Also please provide details on how to use the dev mode after the new changes and what to expect.

Yes
The actual deployments cannot be testes in the CI at the moment so no
I've updated the documentation, you can take a look here - https://github.com/valory-xyz/open-autonomy/blob/123e085959f44f07db895b3a7cc44893e6a8e47d/docs/advanced_reference/developer_tooling/dev_mode.md

Isn't the dev flag deprecated?
https://github.com/valory-xyz/open-autonomy/blob/123e085959f44f07db895b3a7cc44893e6a8e47d/docs/advanced_reference/developer_tooling/dev_mode.md?plain=1#L22

Yes, but it's deprecated on the autonomy build-image not on autonomy deploy build

authors: Adamantios angrybayblade

repo: valory-xyz/open-autonomy


text:
Possibility to set a limit to this bytebufferpool and use as cache?

thanks for fastcache. I'm using victoriametrics fastcache and come across bytebufferpool, which seemed to be faster. So is there a possibility to make it so that there's a limit imposed on this bytebufferpool so we can use as cache?
what happens when oom?

@gitmko0 Ever found a solution to this?

repo: valyala/bytebufferpool

license: mit

license_source: bigquery


text:
Remove number-input spinner decoration in Firefox

I can see the spinner is not shown in Chrome/Safari, but it is visible in Firefox.
Here is an example of 2 fixed inputs and 2 not fixed yet:

In order to achieve this, I had to apply this style to those inputs:
 -moz-appearance: textfield;
One can apply it to every number input, like this:
input[type='number'] {
  -moz-appearance: textfield;
}

Thank you for the report! I just published a new commit that should fix this problem.

Thank you for the report! I just published a new commit that should fix this problem.

authors: thegoldgoat vantezzen

repo: vantezzen/blymp-io


text:
Support generic transaction

As per https://github.com/vapor/fluent/pull/462/commits/85a1f81e065601e81b6bb770be478f2e0ff143f4
All tests passed on local

This has been added on the development branches. Thank you for the contribution!

repo: vapor/fluent-mysql


text:
Made encoding optional

Encoding was protected by a guard and not an optional.

This is a duplicate.

repo: vapor/mysql-provider


text:
Title: Loan Calculator

Describe your issue.
I want to add a project where user can calculate the loan using the amount, rate and year
It will have calculate and reset button
Screenshots (if applicable).
No response
Additional context (if any)
No response

@Drishti-jain21 Go ahead 🚀

@varunKT001
Heyy, I would like to add loan calculator code using javascript.
Please assign this to me.

@035pratheeksha Already assigned to @Drishti-jain21
You can create your issues for the projects you want to build. 😄

@035pratheeksha Already assigned to @Drishti-jain21
You can create your issues for the projects you want to build. 😄

okay,Thankyou.


text:
Day 318

Good morning! Here's your coding interview problem for today.
This problem was asked by Apple.
You are going on a road trip, and would like to create a suitable music playlist. The trip will require N songs, though you only have M songs downloaded, where M < N. A valid playlist should select each song at least once, and guarantee a buffer of B songs between repeats.
Given N, M, and B, determine the number of valid playlists.

Here is a complement to your solution collection (though it needs to be ported to Go):
long numberOfValidPlayListsRec(int required, long downloaded, int buffer) {
    if (buffer >= downloaded) {
        return 0;
    }

    if (required == 0) {
        return 1;
    }

    return downloaded * numberOfValidPlayListsRec(required - 1, buffer == 0 ? downloaded: downloaded - 1, Math.max(0, buffer - 1));
}

long numberOfValidPlayListsIterative(int required, int downloaded, int buffer) {
    if (buffer >= downloaded) {
        return 0;
    }

    long total = 1;
    int available = downloaded;
    for(int i = 0; i <= buffer; i++) {
        total *= available;
        available--;
    }

    if (available < downloaded) {
        available++;
    }

    for(int i = buffer + 1; i < required; i++) {
        total *= available;
    }

    return total;
}

I dont think the solution provided by MaximGovorchuk  works.
long numberOfValidPlayListsRec(int required, long downloaded, int buffer) {
if (buffer >= downloaded) {
return 0;
}
if (required == 0) {
    return 1;
}

return downloaded * numberOfValidPlayListsRec(required - 1, buffer == 0 ? downloaded: downloaded - 1, Math.max(0, buffer - 1));

}
Will always return 0, as at some point of time the function will return 0 so the whole product becomes 0.

Iterative version is also wrong.... as that solution is NOT honoring the constraint "A valid playlist should select each song at least once?
long numberOfValidPlayListsIterative(int required, int downloaded, int buffer) {
if (buffer >= downloaded) {
return 0;
}
long total = 1;
int available = downloaded;
for(int i = 0; i <= buffer; i++) {
    total *= available;
    available--;
}

if (available < downloaded) {
    available++;
}

for(int i = buffer + 1; i < required; i++) {
    total *= available;
}

return total;

}

authors: MaximGovorchuk syam506 vaskoz

repo: vaskoz/dailycodingproblem-go


text:
Add testing pull request text

please review and merge if no problem

please double check the text


text:
TLS certificate common vulnerabilities

Feature request
Include common TLS certificate vulnerabilities and mis-configurations...
Poor strength ciphers etc...
Wildcard certificates...
POODLE etc...

@c0dewhacker could you please share more information about these issues? Where did you identify them and any scanner that your used? Steps to reproduce if possible?

repo: vchinnipilli/kubestriker


text:
Reestructurar los tests

[x] Los fixtures y las configuraciones para tests (que creo que aun no hay ninguna) pueden estar en un archivo aparte llamado tests/conftest.py. Mover todos los fixtures ahi.

[ ] Remover esta linea https://github.com/vcristiani/galaxy-chop/blob/95b966c32a563e7a85d5990abdb83d93618d186c/tests/test_input.py#L28

[x] Los archivos de tests tienen que tener el nombre del modulo que prueban tests/test_core.py, tests/test_util.py.

[ ] Mover todos los datos de tests en legacy a tests/test_data. Incluso pueden tener algo como tests/test_data/real para las galaxias reals (asumo esta estructura de aca en mas)

[ ]  Los paths no pueden estar harcodeados (siguiente seccion).

Sobre la forma de tratar a los paths
La forma canónica de acceder al path donde se encuentra el script actual es:
PATH = os.path.abspath(os.path.dirname(__file__))

TEST_DATA_PATH = PATH / "test_data"

Esto nos daria el path completo y absoluto hasta tests/conftests.py, en mi cado /home/juan/proyectos/galaxychop/src/tests
De ahi en mas se pueden reemplazar linead como estas
https://github.com/vcristiani/galaxy-chop/blob/95b966c32a563e7a85d5990abdb83d93618d186c/tests/test_input.py#L391-L393
por algo como
dm = np.loadtxt(TEST_DATA_PATH / "real" / "dark.dat")
s = np.loadtxt(TEST_DATA_PATH / "real" / "star.dat")
g = np.loadtxt(TEST_DATA_PATH / "real" / "gas_.dat")

About item 2. I can't remove the random line in conftest.py becouse the fixtures "disc_xrotation", "disc_yrotation", "disc_zrotation", and "halo_particles" need the random.
@leliel12  what do you suggest?, An option is define the random line inside each fixture

@pytest.fixture(scope="session")
def halo_particles(mock_dm_halo):
    """Spherical mock halo."""

    def make(size, seed=None):
        random = np.random.RandomState(seed=seed)
        mass_dm, pos_dm = mock_dm_halo(N_part=size)
        vel_dm = random.random_sample(size=(size, 3))

        return mass_dm, pos_dm, vel_dm

    return make

se usa
def test_zaraza(halo_particles):

    halo_particles = halo_particles(size=100, seed=42)

    ...

Por otro lado si los parametros de make en uno seed esta primero que en
todos este primero

the way to access the paths was resolved in #102

this closes with #103

authors: antotaverna leliel12 vcristiani

repo: vcristiani/galaxy-chop


text:
iOS Demo 运行报错

../node_modules/react-native/packager/react-native-xcode.sh: line 41: react-native: command not found
Command /bin/sh failed with exit code 127

请贴详细错误，猜测是没有npm install

authors: ChinaKingKong vczero

repo: vczero/React-Native-App


text:
YAML

Would be great if it also supported YAML.
P.S. I was just about to write this very utility. Now I don't have to. Yeah!!!!

Yeah, I think it would! However, I'm very short on time and I'm trying to dedicate it to big projects, like AVA and Mongorito.
If you feel like doing a PR for it, that'd be great ;)

I can probably do that. Shouldn't take long (assuming there are no complications). What do you want the interface to be? I'm thinking of using a simple heuristic to distinguish YAML vs JSON. Sound okay?

I'm thinking of using a simple heuristic to distinguish YAML vs JSON.

Sounds unstable to me and I feel it will cause bugs.
Here's how I would do it. In case of using stdin for reading template data, I'd introduce --yaml flag to indicate that the incoming data is YAML, not JSON. If a -f flag is used (filename is known), we could just check the file extension (.json or .yml or .yaml). To recap:
$ cat data.yaml | mustached --yaml -t hello.mustache
$ mustached -t hello.mustache -f data.yaml

Okay.

authors: trans vdemedes

repo: vdemedes/mustached


text:
refactorings + backwards-compatible arbitrary emoji processing API

Hello!
Thanks for writing this library, it's definitely saved me a bit of manual labor! I've made some changes, and hopefully you and others might find them handy.
This PR:

Typo fix: rename Emoji::getHtmlHexidecimal to Emoji::getHtmlHexadecimal, but leaves in the old one with a deprecation warning. Hexadecimal is used everywhere else in the code.
Creates interfaces UnicodeProcessor and AliasProcessor, which are used by EmojiParser::processUnicode and EmojiParser::processAliases. These two new methods are generalizations of EmojiParser::parseTo***
Converts the existing EmojiParser::parseTo*** to use the new EmojiParser::process*** API. These conversions are placed in UnicodeParsers and AliasParsers, both singleton classes.
Extracts AliasCandidate and UnicodeCandidate to public classes, instead of inner protected classes of EmojiParser as the processor types depend on these.

In the case of AliasParser, I avoided using Java 8 functional interfaces to allow full backwards-compatibility with Java <8.
Tests are green across the board, and these changes won't (or at least shouldn't) break any existing code that uses this library. If you'd like, I can also add a blurb to the README describing the new processing API.

Coverage decreased (-1.0%) to 93.312% when pulling ecc17f322b2658575e043d3fd97221a7fa0cd578 on iostat:master into c245c8dfb186ec34f373d1966d697a720151c8b2 on vdurmont:master.

Hey @iostat !
Thanks for this contribution! I'm sorry I took so long to answer.
Could you give us some context on your goal?

So, ultimately the goal was to abstract out the parsing process in such a way that I can use emoji-java's parsing engine but control what kind of information I get back, as an example, here's some scala code I use to convert emoji to XML for further downstream processing:
import com.vdurmont.emoji.EmojiParser
import com.vdurmont.emoji.EmojiParser.FitzpatrickAction
import com.vdurmont.emoji.parsers.{UnicodeCandidate, UnicodeProcessor}

import scala.collection.JavaConversions._

object DeEmojifier extends UnicodeProcessor {
  override def shouldRemoveFitzpatrick(fitzpatrickAction: FitzpatrickAction): Boolean = false

  def apply(corpus: String): String = {
    EmojiParser.processUnicode(corpus, this, FitzpatrickAction.PARSE)
  }

  override def apply(input: UnicodeCandidate, fitzpatrickAction: FitzpatrickAction): String =
    <emoji
      tags={input.emoji.getTags.mkString(",")}
      description={input.emoji.getDescription}
      modifiers={Option(input.fitzpatrick).map(_.toString.toLowerCase).getOrElse("")}
      entity={input.emoji.getHtmlHexadecimal.replaceAll("[^0-9A-Fa-fXx]", "")}
    />.toString.replaceAll("\\s{2,}", " ").trim // trim out the extra spaces as a result of line breaks in the code #justscalaxmlthingz
}

Without these changes, I'd have to parse the string myself, find the emoji, do the substitutions, load in my own descriptions, etc., whereas with this new API I am able to just tell emoji-java, "hey just find emoji and do this with them please`. The rest of the changes are just converting the existing code to this new API for consistency. And of course, the one typo fix, probably because I'm too OCD for my own good :P

authors: coveralls iostat vdurmont

repo: vdurmont/emoji-java


text:
Return key on hardware keyboards now sends messages

Signed-off-by: Vivian Lim vivvnlim@gmail.com
Create a class KeyboardGrowingTextView which inherits from HPGrowingTextView, but defines keyCommands. keyCommands defined at any other view or controller layer weren’t being picked up by the OS, but they did work when added to HPGrowingTextView.
I was able to validate this on my machine based on release-v0.5.1 but I can't figure out how to build the project after the App Extension was added. If you have any tips please let me know.
Also let me know if you have any ideas on better ways to call from KeyboardGrowingTextView to RoomInputToolbarView, or why defining keyCommands at any other layer didn't work (I had trouble pinning down exactly which class is the First Responder, and where the OS was looking for keyCommands)

I'm not affiliated with Riot but I will try to take a look at the code for the return/send key tomorrow. I didn't get to build your patch yet but to be clear this is designed to only change the function on the return key on external keyboards?
I would be hesitant to change the function of the return key for only external keyboards. I think ideally there should be a user configurable setting (affecting both on screen and external keyboards) that changes the function of the return key to send.

Agreed with @aaronraimist that it'd be best to have a "send on enter" option in general rather than making it specific to external keyboards.  It would also be really really nice to have shift-enter to insert linebreaks (as per riot-web).

@ara4n Shift-enter works fine on external keyboards, this code only handles unmodified enter keys. 👍🏼
@aaronraimist correct. The code for handling onscreen keyboard returns is pretty different I think, UIKeyCommands are exclusively for hardware keyboards. I did not investigate the onscreen keyboard since the current behavior there is reasonable (if you’re already typing on the touchscreen, the send button is pretty easy to reach, and you still need to be able to insert linebreaks)
I’d like to note that this change opens up the possibility of adding additional UIKeyCommands for more shortcuts later on (i.e. cmd+number to switch between chats), they just need to be registered at this level since this is the delegate the OS inspects the keyCommands of.
@giomfo Thanks, I’ll remove the traversal. That’s much better.

Let's fix here the return key handling for the external keyboard.
I filed another issue #1529 to handle the "send on enter" option in general.

I've been having trouble with getting the app to build since the share extension was added, and I don't have an Apple Developer Program account... could someone please try the latest commit?

thanks!

authors: aaronraimist ara4n giomfo vivlim

repo: vector-im/riot-ios


text:
Enable efloor+fingerslide options [3]

Hi Jamie,
I thought it would be useful to have both the efficient_floor and fingerslide options enabled together, but I noticed you had prevented this. I checked if there were any issues with allowing it, and it seems to work.
Maybe that difference-union-difference-union part should be refactored, but... one step at a time.

UPDATE: This issue was solved by @ostat in his project https://github.com/ostat/gridfinity_extended_openscad


text:
List the PackageIdentifier of the package to be added to automation
RemNote.RemNote
Details about the application
https://download.remnote.io/latest.yml

Access Denied: https://download.remnote.io/RemNote Setup 1.8.8.exe

https://download.remnote.io/RemNote Setup 1.8.7.exe
Accessing non-existent files also results in Access Denied. I thought they revoked the new installer for some reasons but forgot to rollback the update source. 🤔

You can add this now.


text:
Update channels.py for awgn for complex signals

Hi,
there is issue with awgn() for complex signals.
Please check my proposal

Coverage remained the same at 54.271% when pulling 1fa6dfedde0bc78e28709038b8c44414542ff67f on matchius:patch-1 into 57f5ebd2498788dae71d4a213cadb3e59f45c11c on veeresht:master.

57f5ebd is also broken

Thanks! I have merged your PR.

authors: coveralls matchius veeresht

repo: veeresht/CommPy


text:
Not able to pay fee's to close position

Description
Have a large position open on perps market, 95%+ of your settlement asset used.
In the example it was a perps market and 5 USD was available for fee's of a postion of 3900 USDT notional value.
Steps to Reproduce

Go to 'perps market , https://vegafairground.eth.limo/#/markets/2fb61fb4a0ab63c7644d523efbd61b5236d90c7877b5b749c98f22988bac61ee
Open a large position which makes it so you have very little free capital left
Wait for a funding to happen
Try to close position
Deposit a lot of funds and try to close again

Expected behavior
Should be able to close the position but is not due to not having enough to pay the fee's.
See example
https://explorer.fairground.wtf/txs/AEEE3017688B9E81853064BB0CE2A4A538310E141E8A763C7C54354C3EE70C6E
Screenshots

https://github.com/vegaprotocol/frontend-monorepo/assets/100769129/61959fc2-4b8d-4cdb-a8a1-0d2658e4f8ea

This is core working as designed .... and certainly not a Console bug.  Closing.

repo: vegaprotocol/frontend-monorepo


text:
chore(trading): catch ethereum errors and capture to sentry

Related issues 🔗
Closes #2580
Description ℹ
Catch possibly errors from the last stage of creating transaction, when contract endpoints are requested
Demo 📺

Technical 👨🔧
Add catch to promise and log by logger

Code-wise this seems correct, but I think it will generate a lot of Sentry noise that there is nothing that we can do to fix. It could be useful in debugging though hence hitting ✅

IMHO it's better to know, that somethings is wrong, than be surprised later :-).
if we collect data on this subject, we will have more grounds to decide on a possible rework of the user experience of connecting the console to smart contracts, etc


text:
logo

please check if all files are correct

thanks, contact me if you need any graphic design for this project. :)

OK, thanks

authors: linadesteem vellengs

repo: vellengs/typerx


text:
reminder: you for real this time

No YOU made a bad code change.

Screw you, @chrissexton.

repo: velour/catbase

license: WTFPL


text:
How to test handler code

First of all thank you so much for your great work and effort in maintaining this library.
I'm very happy you have added an integration and unit test to the repository.
How can I test our handler code?
Our handler looks this:
//handler.js
import serverlessExpress from '@vendia/serverless-express'
import app from './app'

export default serverlessExpress({app}).handler
using express
//app.js
...
app.get('/health', (req, res, next) => {
  response.setHeader('isBase64Encoded', true)
  response.header('content-type', 'application/json')
  res.status(200).send({
    healthy: true,
    status:200,
  })
})
I would like to have a jest test handler.test.js in our code repo.
This is a smoke test to see if things are more less or okay.
The handler might still not run on AWS but at least we'll catch more gross errors in Jest on dev machine rather than waiting for the code to be pushed to staging to do an E2E test with Cypress.
I've tried passing an event but at best I'm getting an empty object response {}
//handler.test.js

import handler from '../handler'

describe('handler.js', () => {

	it('GET /takeaway/health should return 200', async () => {

		const event = {
			headers: {},
			httpMethod: 'GET',
			path: '/health',
			requestContext: {
				stage: 'prod',
			},
		}

		const context = {}

		const response = handler(event, context)

		console.log('response', JSON.stringify(response, null, 2))

		expect(response.statusCode).toEqual(200)
		const body = JSON.parse(atob(response.body))

		// console.log('body', JSON.stringify(body, null, 2))

		expect(body.status).toEqual(200)
		expect(body.healthy).toEqual(true)

	})

})

I found now a closed Issue #363 https://github.com/vendia/serverless-express/issues/363.
I've tried copy pasting the whole structure of https://github.com/vendia/serverless-express/blob/mainline/jest-helpers/api-gateway-v1-event.js but got a response with an empty object {}.
I'm going to try https://github.com/serverless/event-mocks

Hmm... You probably need const response = await handler(event, context)

Thank you @brettstack . Adding await fixed the problem.
I had started with the await and then removed it when using the wrong event and I didn't put it back.
In the end it was enough to just use this event:
  headers: {},
  httpMethod: 'GET',
  path: '/takeaway/health',
  requestContext: {
    stage: 'prod',
  },
}```

How can I disable the console.debug logging to avoid polluting the jest tests?

The latest version should only log when process.env.NODE_ENV === 'development'.

Thanks! Yes indeed launching NODE_ENV=testing jest handler hides the debug.
@brettstack would you be interested in a PR to add a section How to unit test to the Readme.md?

That'd be great!

One thing that could be helpful would be actually publishing the jest-helpers in the package (or elsewhere).  I'd love to be able to use makeEvent in my own tests.

authors: brettstack giorgio-zamparelli glasser

repo: vendia/serverless-express


text:
Umbraco V9

Do you have any plans to mirgrate this for the new version of Umbraco V9?

Sure, I am working on a v2 release for Vendr 2.0 / Umbraco 8.17+ and Umbraco 9.0+
https://github.com/vendrcontrib/vendr-payment-provider-adyen/tree/v2/dev
Still need to test it further in v8 and v9. I'll check with @mattbrailsford if we can ship a pre-release and it will be very helpful if you want to help testing the payment provider 🤓😎🙌

Perfect – yes of course 😊. I have a project next year, where I can test your implementation. Do you have a lot of experience with adyen ?
Von: Bjarne Fyrstenborg @.>
Gesendet: Montag, 20. Dezember 2021 17:41
An: vendrcontrib/vendr-payment-provider-adyen @.>
Cc: Baumann Manuel @.>; Author @.>
Betreff: Re: [vendrcontrib/vendr-payment-provider-adyen] Umbraco V9 (Issue #1)
Sure, I am working on a v2 release for Vendr 2.0 / Umbraco 8.17+ and Umbraco 9.0+
https://github.com/vendrcontrib/vendr-payment-provider-adyen/tree/v2/dev https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvendrcontrib%2Fvendr-payment-provider-adyen%2Ftree%2Fv2%2Fdev&data=04|01||12cb4970206d45c0607608d9c3d7761f|beb7b05c08234a4cbfac3497745999f7|1|0|637756152430253400|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=YHYPm%2BAYFMZn2QPr5Vwk4JXOSAApsJKHYm4PR2l9Cow%3D&reserved=0
Still need to test it further in v8 and v9. I'll check with @mattbrailsford https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmattbrailsford&data=04|01||12cb4970206d45c0607608d9c3d7761f|beb7b05c08234a4cbfac3497745999f7|1|0|637756152430253400|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=Uj%2FNAokYtTnxzZqzkHN8gdCfTca0Za6G91eVNHtXUM4%3D&reserved=0  if we can ship a pre-release and it will be very helpful if you want to help testing the payment provider 🤓😎🙌
—
Reply to this email directly, view it on GitHub https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvendrcontrib%2Fvendr-payment-provider-adyen%2Fissues%2F1%23issuecomment-998092043&data=04|01||12cb4970206d45c0607608d9c3d7761f|beb7b05c08234a4cbfac3497745999f7|1|0|637756152430253400|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=nCYZUg0xZlHfGl2a3Z84RImfwA1SieMcy1SJbexm6A4%3D&reserved=0 , or unsubscribe https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAM3QEJDCTDFRT2GUUCCXGE3UR5MARANCNFSM5KOC25NA&data=04|01||12cb4970206d45c0607608d9c3d7761f|beb7b05c08234a4cbfac3497745999f7|1|0|637756152430253400|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=97BnsV5bMQsnXKyswueEfVUeF9bLoQBH5WoFjeSLrYU%3D&reserved=0 .
Triage notifications on the go with GitHub Mobile for iOS https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01||12cb4970206d45c0607608d9c3d7761f|beb7b05c08234a4cbfac3497745999f7|1|0|637756152430253400|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=SNwdTnIu89g2QoJn4TpUHd50XWXgrWKy3rv6khSk1ko%3D&reserved=0  or Android.
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AM3QEJHCZKK55DWJP6ML5M3UR5MARA5CNFSM5KOC25NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHN622CY.gif Message ID: @.***>

@slag-manuel not a lot, but I have tested the basically functionality and common features needed on a webshop like the payment request, cancel, charge and refund.
In v2 I still need to test it still works on Umbraco v8 and v9 - it should, but better safe than sorry.

There is a now a 2.0.0-rc0000 build of the Adyen provider on the unstable nuget feed at https://nuget.outfield.digital/unstable/vendr-contrib/v3/index.json

I'll close this as the v2.0.0 release is available here: https://www.nuget.org/packages/Vendr.Contrib.PaymentProviders.Adyen/

authors: bjarnef mattbrailsford slag-manuel


text:
Swift 5.1 - [Session defaultTaskGroup]: unrecognized selector sent to instance

When using Xcode 11 and Swift 5.1 a dataTask called with an URL as parameter (instead of an URLRequest) results in an NSInvalidArgumentException:
[Session defaultTaskGroup]: unrecognized selector sent to instance

Closing now that fix is merged. Thanks @m-herold

authors: dmiluski m-herold

repo: venmo/DVR


text:
DOCS: Introduce Local Deployment guidance into Veraison services README.md

We have an adequate documentation for how services are deployed using docker!
However many users prefer to deploy Veraison locally on their machines with all services running on a local host and on the same machine use cocli tool to provision Endorsements and evcli tool to exchange Evidence with Veraison.
This documentation issue tracks inserting local deployment story to the Veraison services.

Resolved by https://github.com/veraison/services/pull/250

authors: setrofim yogeshbdeshpande

repo: veraison/services


text:
Icon for menu item is not correct

Describe the bug
I've chosen the Newsletter icon, but it shows Paragraph icon for the menu item.

Steps to reproduce

Choose 'newspager-o, section' icon in the list for the menu item.
Another icon is shown, not the icon that was selected

Craft CMS version
5
Plugin version
5
Multi-site?
No response
Additional context
No response

Can you let me know the exact Craft version you're on? That new Entries icon doesn't show for me, and any updates I do to the Craft Icon are working for me. I'm on Craft 5.1.8.

I've also had this. It happens when you update from Craft 4 to 5. It goes away if you revert the nav to defaults.

repo: verbb/cp-nav


text:
Route merging leads to 502 error on /api/main

Using the route merging feature, hits to API endpoints that don't exist return 404 errors, as expected, but hitting /api/main, at least when using vercel dev, leads to a 502 error when it doesn't exist, with the following console output:
thread 'main' panicked at 'internal error: entered unreachable code', api/api/main.rs:10:1
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
TypeError: Object prototype may only be an Object or null: undefined
    at Function.setPrototypeOf (<anonymous>)
    at new LambdaError (/home/arctic-hen7/.nvm/versions/node/v19.3.0/lib/node_modules/vercel/dist/index.js:8983:16)
    at Lambda.<anonymous> (/home/arctic-hen7/.nvm/versions/node/v19.3.0/lib/node_modules/vercel/dist/index.js:9116:27)
    at Generator.next (<anonymous>)
    at fulfilled (/home/arctic-hen7/.nvm/versions/node/v19.3.0/lib/node_modules/vercel/dist/index.js:9030:58

For me, this can be replicated with a minimal route merging configuration as in the readme. Note that line 10 refers to the #[bundled_api] macro. Unfortunately running RUST_BACKTRACE=1 vercel dev doesn't seem to pass the environment variable through for me, so I'm not sure how exactly to get a backtrace on this error locally.

I am still facing this issue in the exact same manner

repo: vercel-community/rust


text:
refreshInterval doesn't work when refreshWhenOffline = false

Bug report
Description / Observed Behavior
When using chrome, when refreshWhenOffline: false it appears that refreshInterval doesn't do anything
I've tested in chrome and firefox, firefox works as intended
Expected Behavior
refreshInterval to work as documented
Repro Steps / Code Example
https://codesandbox.io/s/busy-oskar-fsxky?file=/src/App.js
Additional Context
SWR version: 0.4.2
Chrome version: 88.0.4324.182 (Official Build) (x86_64)
Add any other context about the problem here.
Firefox:

Chrome

Seems related:https://bugs.chromium.org/p/chromium/issues/detail?id=678075

It appears to be a bug with chrome and not swr directly

repo: vercel/swr


text:
UnhandledPromiseRejectionWarning: RPError: JWT not active yet, now 1580794298, nbf 1580794302

Use NodeJs version 12.14.0 and npm version 6.13.4

Could you please give some more information?
What did you do, what did you expect to happen, what happened?
Are multiple systems (server, client) involved? Are their clocks in sync?

Hi @Zubair-Ashraf,
please use the issue template: https://github.com/verdaccio/verdaccio/blob/master/.github/ISSUE_TEMPLATE/Bug_report.md

Could you please give some more information?
What did you do, what did you expect to happen, what happened?
Are multiple systems (server, client) involved? Are their clocks in sync?

I am using xero accounting app https://www.xero.com/us/  for generating invoices so for hitting the invoices API i need access_token, refresh_token and xero_tenant_id and so for getting these things xero provides a sample project that is posted in this repo https://github.com/XeroAPI/xero-node.  I just cloned the repo and started the server. My app connected successfully with xero but after that when navigates to "/callback", it throws an error which says "UnhandledPromiseRejectionWarning: RPError: JWT not active yet, now 1580794298, nbf 1580794302"
invoices api enpoints is: https://developer.xero.com/documentation/api/invoices

@Zubair-Ashraf perhaps you should try with more orthodox way rather than clone the repo, then you play under your own rules. So I'd suggest use either a released npm version or docker and fill the template appropriately. An specific environment leads you to specific errors we don't see and thus cannot help.

I am using xero accounting app https://www.xero.com/us/ for generating invoices so for hitting the invoices API i need access_token, refresh_token and xero_tenant_id and so for getting these things xero provides a sample project that is posted in this repo https://github.com/XeroAPI/xero-node. I just cloned the repo and started the server. My app connected successfully with xero but after that when navigates to "/callback", it throws an error which says "UnhandledPromiseRejectionWarning: RPError: JWT not active yet, now 1580794298, nbf 1580794302"
invoices api enpoints is: https://developer.xero.com/documentation/api/invoices

I don't understand how verdaccio is related to all this. Verdaccio is a NPM server/registry.
If you took an example that uses a specific's company/project's API and that example returns an error, this is nothing verdaccio is responsible for.

I'm closing this, too old, please if the error persist don't hesitate to comment and provide more information 👍

authors: DanielRuf Zubair-Ashraf jachstet-sea juanpicado

repo: verdaccio/verdaccio


text:
Proposal: Add an option to hide sensitive data from logs

Under the scope of GDPR and any future privacy law, I think it would be beneficial for VerneMQ to support a boolean configuration option named log.scrub_sensitive_data, defaulting to false for backward compatibility. This will ideally be implemented in vernemq_dev and reused in the core applications to hide stuff like IP addresses, usernames, allowing plugin developers to also use it for their log messages.

I like this idea a lot! I'll assign this to the 1.7.0 milestone for now.

Just adding a reference: https://github.com/rabbitmq/credentials-obfuscation

Time to address this.
This is about 2 things:

Protecting FSM session state (so that stack traces do not expose password). Credentials_obfuscation is obviously a candidate library.
Sanitize MQTT Frames before logging in all places (main candidate here is the CONNECT frame)

I consider the question of MQTT payload in a logged stack trace to be a bit different. It can be encrypted by end users.
First thing is a concept of what we actually want to do, and how fine-grained obfuscation options should be.
cc @mths1

👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
👉 Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

IMO what should be hidden (as a minimal baseline) is

MQTT passwords
Credentials (Diversity DB, API Keys...)

I played with the credentials-obfuscation library and it worked well (for file-based auth). We would need to make it available in diversity as well if we want to have the password decoded only where necessary. It might also be an option to strip sensitive data in a logging framework (time to switch away from lager :-))
Some other ideas are here:
https://erlef.github.io/security-wg/secure_coding_and_deployment_hardening/sensitive_data.html

@mths1 yes to all of the above :)
Including getting away from lager... a bit of an effort, though.
The format_status callback for OTP behaviours might be a low-hanging way to control leaking of process status.

👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
👉 Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

authors: codeadict ioolkos larshesel mths1

repo: vernemq/vernemq


text:
v0.44.06版本第三方规则异常

lhie1的规则之前是store.steampowered.com放到special规则集里直连的，前几天steam有波动后规则已经注释了这一行

但是openclash这边还是会走直连，已经重复设置过第三方规则

是没有正确的应用到最新的规则吗

我又鼓捣了下，多次来回删除清空重新读取设置第三方规则，最后应该是正确用上了最新的规则了，store.steampowered.com没有再走直连了，请教一下如何定义重新设置第三方规则？今天我查看日志，规则自动更新后说不兼容没有再进行处理等待版本更新，然后更新到最新的版本后，第三方规则那边检测更新是一直是提示无更新的，然后后续就是无论怎么设置都有上面说的问题，是不是其中某一环出了问题导致最新的规则没有被应用上？

provider需要单独更新，去控制面板刷新

我找了下面板貌似没找到，不确定遗漏了哪个地方，麻烦详细说明一下感谢！

刚找到面板规则页右侧有按钮可以更新

我的也是更新不了，规则全空了。请问是怎么解决的？

authors: 404user jeffreymor vernesong

repo: vernesong/OpenClash


text:
Function as objects

So they work as a parameter in apply.

Problems:

How can we solve definition in different files?
How can we still use ADL?

repo: verri/jules

license: Zlib


text:
pandas_to_vertica - possibility to change the csv path

https://github.com/vertica/VerticaPy/blob/master/verticapy/utilities.py#L503
In this line, pandas_to_vertica function write a temporary csv file, before sending the data to Vertica.
We need to can choose the path of this file, because sometimes, we don't have access right to the default path.

Hi Gaetan,
A new parameter 'temp_path' will be added to the function in the next PR.
Badr

authors: gaetan-dion oualib

repo: vertica/VerticaPy


text:
[Bug] flink-cdc 增量同步mysql数据错误

Search before asking

[X] I searched in the issues and found nothing similar.

Flink version
1.13.6
Flink CDC version
2.2.1
Database and its version
mysql 5.7.25
Minimal reproduce step
flink 1.13.16
flink-cdc 2.2.1
mysql:5.7.25
mysql-driver:5.1.49
增量同步阶段报错  请问有人遇到过吗
16:17:56,961 INFO  org.apache.flink.runtime.executiongraph.ExecutionGraph        - Source: MySQL Source Demo -> Sink: Print to Std. Out (1/1) (ba10f3a939779c1435626570e396e950) switched from RUNNING to FAILED on e9414b4e-a65b-4398-95e4-9de240dc1fe8 @ localhost (dataPort=-1).
java.lang.RuntimeException: One or more fetchers have encountered exception
at org.apache.flink.connector.base.source.reader.fetcher.SplitFetcherManager.checkErrors(SplitFetcherManager.java:223)
at org.apache.flink.connector.base.source.reader.SourceReaderBase.getNextFetch(SourceReaderBase.java:154)
at org.apache.flink.connector.base.source.reader.SourceReaderBase.pollNext(SourceReaderBase.java:116)
at org.apache.flink.streaming.api.operators.SourceOperator.emitNext(SourceOperator.java:305)
at org.apache.flink.streaming.runtime.io.StreamTaskSourceInput.emitNext(StreamTaskSourceInput.java:69)
at org.apache.flink.streaming.runtime.io.StreamOneInputProcessor.processInput(StreamOneInputProcessor.java:66)
at org.apache.flink.streaming.runtime.tasks.StreamTask.processInput(StreamTask.java:423)
at org.apache.flink.streaming.runtime.tasks.mailbox.MailboxProcessor.runMailboxLoop(MailboxProcessor.java:204)
at org.apache.flink.streaming.runtime.tasks.StreamTask.runMailboxLoop(StreamTask.java:684)
at org.apache.flink.streaming.runtime.tasks.StreamTask.executeInvoke(StreamTask.java:639)
at org.apache.flink.streaming.runtime.tasks.StreamTask.runWithCleanUpOnFail(StreamTask.java:650)
at org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:623)
at org.apache.flink.runtime.taskmanager.Task.doRun(Task.java:779)
at org.apache.flink.runtime.taskmanager.Task.run(Task.java:566)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.RuntimeException: SplitFetcher thread 0 received unexpected exception while polling the records
at org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.runOnce(SplitFetcher.java:148)
at org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.run(SplitFetcher.java:103)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266)
at java.util.concurrent.FutureTask.run(FutureTask.java)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
... 1 more
Caused by: org.apache.kafka.connect.errors.ConnectException: An exception occurred in the change event producer. This connector will be stopped.
at io.debezium.pipeline.ErrorHandler.setProducerThrowable(ErrorHandler.java:42)
at com.ververica.cdc.connectors.mysql.debezium.task.context.MySqlErrorHandler.setProducerThrowable(MySqlErrorHandler.java:72)
at io.debezium.connector.mysql.MySqlStreamingChangeEventSource$ReaderThreadLifecycleListener.onCommunicationFailure(MySqlStreamingChangeEventSource.java:1185)
at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:973)
at com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:606)
at com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:850)
... 1 more
Caused by: io.debezium.DebeziumException: command 30 not supported now,sql=[J06�͔k��'*�}O] Error code: 1105; SQLSTATE: HY000.
at io.debezium.connector.mysql.MySqlStreamingChangeEventSource.wrap(MySqlStreamingChangeEventSource.java:1146)
... 5 more
Caused by: com.github.shyiko.mysql.binlog.network.ServerException: command 30 not supported now,sql=[J06�͔k��'*�}O]
at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:937)
... 3 more
What did you expect to see?
正常获取增量数据同步
What did you see instead?
报错
Anything else?
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

已经开启checkpoint

1

问题已经解决。目前看是因为使用了dbproxy导致的问题。去掉proxy直连数据库没有问题

repo: ververica/flink-cdc-connectors


text:
[update] update README.md for quick start

When I am using flink1.14+flink cdc 2.2.1, because the flink version depends on the source code is 1.13.5, it will prompt that the dependency org.apache.flink:flink-shaded-guava:18.0-13.0 is missing, if you refer to flink-sql-connector-mysql-cdc, these problems will not appear

cc @leonardBang

cc @leonardBang


text:
[question] should pylarky be a library that customers can install to mimic starlarky compatibility?

Problem or feature statement
A key design decision for Larky is that it will try to mimic the behavior and standard library as well as external party interfaces so that Larky consumers can run Larky code using CPython, e.g. to use code coverage, debugging, etc. tools available for it. The complexity arises from the requirement that whatever we do in Larky must have some equivalent in python to continue to create a “local” dev environment experience for customers. The guiding principle is: "if it works in larky , it can work in python" which is very similar but not the same as "if it works in python it should work in larky."
We focus on the former: "larky scripts should work in python" - but that means our apis are basically limited to third party python packages or stdlib apis.
There should be a backport/compatibility layer that allows Larky code evaluation using CPython tools.
Advised solution
Similar to using something like six. This issue discusses a compatibility layer that offers a module similar to the popular python third party lib: six.
After one import to map larkyisms to python, there should be a module that allows you to expose a third party lib as utils that we can use as way to expose larky functionality written in java directly to python under that module compatible namespace.
That way you can expose java utility methods to larky & consequently write their equivalent in this compatibility module that can mimic larky in python.
We need something to do this. I propose pylarky so customers can just pip install pylarky to the compatibility layer.
Thoughts? Suggestions? Comments?

i think we need this. lots of common patterns on vgs are going to be verbose without it.
i believe the most common patterns are "redact json|regex|xml". having a short hand method for each makes a lot of sense e.g. request.body = transform_json_path(request.body, '$.foo', lambda raw: vault.put(raw, 'format')) as an example is way nicer than having to import libraries and do everything by hand

Not pylarky per se. Pylarky is an interface to run execution in larky.
But we do need a separate larky compatibility lib to run Larky code in python.
Already triaged and would be in backlog

authors: aslepakurov mahmoudimus mjallday

repo: verygoodsecurity/starlarky


text:
Dedup vertex/edge before delete.

Close #1247

Close #1232

repo: vesoft-inc/nebula-graph


text:
Fixes JSON parsing error in input.query in README.md

Fixed this issue
--json "
  {
   'yql': 'select * from vectors where {targetHits:10} nearestNeighbor(vector, q)',
   input.query(q)': '$query'
  }" \
 https://a901b714.aa994632.z.vespa-app.cloud/search/
{"root":{"id":"toplevel","relevance":1.0,"fields":{"totalCount":0},"errors":[{"code":3,"summary":"Illegal query","message":"Json parse error.: Unexpected character ('i' (code 105)): was expecting double-quote to start field name\n at [Source: (byte[])\"\n  {\n   'yql': 'select * from vectors where {targetHits:10} nearestNeighbor(vector, q)',\n   input.query(q)': '[0.2913021147251129,0.5057677030563354,0.5451035499572754,0.27675727009773254,0.10927736759185791,0.06706570088863373,0.1770867556333542,0.7996796369552612,0.6307869553565979,0.7204529047012329,0.13946707546710968,0.8562200665473938,0.3066636025905609,0.1463921070098877,0.8984076976776123,0.6209235191345215,0.47249022126197815,0.09817588329315186,0.17768551409244537,0.8677831292152405,0.\"[truncated 14419 bytes]; line: 4, column: 5]"}]}}%```

Thanks!

authors: kkraune shivamsupr

repo: vespa-cloud/vector-search


text:
vespa-cli 8.82.24 failed to build on macOS Ventura

Looks like there is some build issue on macOS Ventura, raising an issue in here for the record.
==> make all manpages
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
go env -w GOPROXY="https://proxy.golang.org,direct"
diff: unrecognized option `--line-format=%L'
usage: diff [-aBbdilpTtw] [-c | -e | -f | -n | -q | -u] [--ignore-case]
            [--no-ignore-case] [--normal] [--strip-trailing-cr] [--tabsize]
            [-I pattern] [-F pattern] [-L label] file1 file2
       diff [-aBbdilpTtw] [-I pattern] [-L label] [--ignore-case]
            [--no-ignore-case] [--normal] [--strip-trailing-cr] [--tabsize]
            [-F pattern] -C number file1 file2
       diff [-aBbdiltw] [-I pattern] [--ignore-case] [--no-ignore-case]
            [--normal] [--strip-trailing-cr] [--tabsize] -D string file1 file2
       diff [-aBbdilpTtw] [-I pattern] [-L label] [--ignore-case]
            [--no-ignore-case] [--normal] [--tabsize] [--strip-trailing-cr]
            [-F pattern] -U number file1 file2
       diff [-aBbdilNPprsTtw] [-c | -e | -f | -n | -q | -u] [--ignore-case]
            [--no-ignore-case] [--normal] [--tabsize] [-I pattern] [-L label]
            [-F pattern] [-S name] [-X file] [-x pattern] dir1 dir2
       diff [-aBbditwW] [--expand-tabs] [--ignore-all-blanks]
            [--ignore-blank-lines] [--ignore-case] [--minimal]
            [--no-ignore-file-name-case] [--strip-trailing-cr]
            [--suppress-common-lines] [--tabsize] [--text] [--width]
            -y | --side-by-side file1 file2
       diff [--help] [--version]
one or more files need to be formatted: try make fmt to fix this automatically
make: *** [checkfmt] Error 1
make: *** Waiting for unfinished jobs....

relates to https://github.com/Homebrew/homebrew-core/pull/115710

Thanks for reporting this! It should be fixed in our next release.

repo: vespa-engine/vespa


text:
Cleanup config model, part 1

Remove unused code, optimize imports, fix method signatures.
No functional changes.

Merge at will when done

authors: baldersheim hmusum


text:
Deploy tester and real apps in parallell

@freva or @mpolden please review.

Discussed this with @jonmv in a thread in #vespa-devs; this wont work because deployTester is not retrying and configserver does not block until provisioning succeeds for external deployments, so this will deploy the tester app once and then fail because the hosts are not ready yet.
To be able to redeploy tester app multiple times (as we do with the real), we need to either store the key/cert somewhere or be able to regenerate it across the different controllers (VESPA-21067)

authors: freva jonmv


text:
Revert "Refactor identityprovider. Add SiaIdentityProvider"

Reverts vespa-engine/vespa#4984

👍

authors: aressem tokle


text:
Vespa <> Gradle

Gradle build system for all vespa modules
Compilation:
./gradlew compileJava compileTestJava
Build with test:
./gradlew build
This gradle task will generate a test report under ./build/reports/allTests/index.html
Tests are still work in progress, out of 10812 tests, 43 failing
Some advantages to using gradle:

Modern and readable build configuration
Time saving - compilation and test parallelization by default (each module is compiled/tested/packaged in parallel based on the dependency graph)
Easier control over jarhell issues
Great support for IDEs - full control over the IDE project files

Thank you for submitting this pull request, however I do not see a valid CLA on file for you. Before we can merge this request please visit https://yahoocla.herokuapp.com/ and agree to the terms. Thanks! :smile:

@gjoranv @bjorncs @aressem opinions?

I think it is great looking forward for modern development tools like gradle and we should welcome efforts helping us along the way. However, internally I don't see us switching to gradle in the short term, and we don't want to maintain a mix of gradle and maven ( I think). This means that we would probably not use these files in CI/CD and the will become stale. But I don't think it would hurt to merge this and it might be that developers will start experimenting with gradle and start paving the road ahead.

what is next step?

I think the main thing is to understand whether this is in fact worth the effort, beyond catching up with the current master version, there's a significant effort still required to make sure that c++ compilation is not broken, and if there's any other maven related workflow that I missed or was added in the interim it should be added.

Timed out.

authors: aressem bratseth kkraune ohad7 yahoocla


text:
The automated release is failing 🚨

:rotating_light: The automated release from the main branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Downloading https://services.gradle.org/distributions/gradle-8.4-bin.zip
............10%............20%.............30%............40%.............50%............60%.............70%............80%.............90%............100%
Welcome to Gradle 8.4!
Here are the highlights of this release:

Compiling and testing with Java 21
Faster Java compilation on Windows
Role focused dependency configurations creation

For more details see https://docs.gradle.org/8.4/release-notes.html
Starting a Gradle Daemon (subsequent builds will be faster)
Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the @semantic-release/exec plugin to add more helpful information.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

Seems like a temporary issue with dependencies resolution. Re-run and should be good now

repo: vexdev/amarr


text:
Showing game object name instead of script name for script member variable in inspector

I have a monster called "AngelBaby" (don't ask). He has a script attached called "PouterChaseState" which causes the monster to chase the player character. The "PouterChaseState" does this using a Propulsion subtype, in this case, "ForceBasedPropulsion". I dragged the attached "ForceBasedPropulsion" into the Propulsion slot for the "PouterChaseState" but rather than saying the name of the script ("ForceBasedPropulsion") in that slot as I expected, it says the name of the game object ("AngelBaby").
Screenshot highlighted relevant parts:
http://i.imgur.com/hrct0sP.png
Is this a design decision or a bug? I'm treating it as a bug because I'm about to start working on a script that will have a list of Propulsion types and I now won't be able to know which is which in the list because they'll all have the same name after I've dragged them in (in this case "AngelBaby").

Hey check (this)[https://github.com/vexe/VFW/issues/24]
The way It worked it was like vexe suggested: Override theToString method.
This allowed great customization, for example I've used formatMethod to format the Label with an Actor name, and the ToString Method to display a speech string instead of the gameObject Name.
Hope it helps!

Thanks. I took your advice and gave this a try but without success:
public class ForceBasedLocomotion : Locomotion
{
    Rigidbody2D rigidBody_;
    [Serialize] float movementForce_;

    ...

    public override string ToString()
    {
        return this.GetType().Name;
    }
}

What am I missing? Thanks.

I'm not sure, but I think ForceBasedLocomotion should be a system object in order to work.
Maybe you can use Display(FormatMethod)] to format the object's label instead?
Anyways you should wait if Vexe replies. Im still a noob at this.

Hey colms,
unfortunately this is a Unity thing, if you use ObjectField on any non-null object, it will just display its name. In the case of Components (thus behaviours) the name property resolves to the gameObject name the component's attached to. But if you use PropertyField and have a serializedProperty wrapping your component field, it will show "GameObjectName (BehaviourType)" (via the internal property.objectReferenceStringValue) which is what you want I suppose. Since I don't deal with serializedProperties I use ObjectField, thus you get this useless display. I'm gonna try and see how to hack my way in. Worst case I could just use the field style I used on System.Objects, gives you total control over the display text, with a custom picker and all that.

An alternative solution is to include the type name in the label text and use FormatMethod like peladovii suggested, does this work for you?
[Display(FormatMethod = "FormatBehaviour")]
public MonoBehaviour behaviour;

string FormatBehaviour(MonoBehaviour value)
{
    return value == null ? "Behaviour" : "Behaviour (" +  behaviour.GetType().Name + ")";
}

OK I'm hardcoding "Behaviour" here but I'm just trying to see if this style of display works for you or not. I could for instance pass in the MemberInfo of 'behaviour' so you'd get reusable formatting, i.e:
string FormatBehaviour(MonoBehaviour value, MemberInfo member)
{
      string display = member.GetNiceName();
      if (value == null)
          return display
      return display + " (" + value.GetType().Name + ")";
}

Thank you very much :)

authors: colms peladovii vexe

repo: vexe/VFW


text:
SelectEnum on Dictionaries

The SelectEnum popup window fails to change the value of a Dictionary key or value when applied via PerKey or PerValue.
This does not appear to be an isolated problem with SelectEnum, it also applies to a number of other attributes. I believe these issues are caused by the use of a temporary copy of the dictionary in DictionaryDrawer.

Just tried:
[PerKey, SelectEnum]
public Dictionary<KeyCode, int> dictionary2;

and seemed to be changing the key properly. Are you talking about persistency?

It is possible that this behavior changed in 1.3.3. I'm still on 1.3.2, I will update and get back to you.

On unity 5.1.1f1 personal and vfw 1.3.3, the following class produces the bug:
using UnityEngine;
using Vexe.Runtime.Types;
using System.Collections.Generic;

public class Test : BetterBehaviour
{
	[PerKey, SelectEnum]
	public Dictionary<KeyCode, int> dictionary2;
}

Right. You said that this applied to a number of other attributes, like what?
Cause Popup seems to work:
[PerKey, Popup("GetValues", TextField = true)]
public Dictionary<string, int> dictionary2;

string[] GetValues() { return new string[] { "One", "Two", "Three" }; }

Seems that the 'write' block is not running after the value is set from the window - So, the temp kvp list has the updated value, but the original dictionary does not. If we do not write, then the next time we read we'll clear the contents of the temp list and read from the original dictionary again, reading the old value. DictionaryDrawer still proves to be the most challenging drawer to get right.

I did a dirty hack to fix it. Let me know of the other attributes you said to be problematic too so I can try out this hack on them.

Actually I don't believe there are any other attributes that have problems, some of my diagnostic code was interfering with the drawer.


text:
Do you have plan to add websocket proxy support?

I am not sure if websocket can be easily supported

Pingora supports gRPC and websocket proxying, athough I haven't used websocket proxy, but I think it should be usable.

In web3 area, the most use cases are http and websocket rpcs. I am not sure whether websocket proxy can reuse the most logic(code) of http.

Is there any further update on this?

Is there any problem with the websocket proxy？?

Is there any problem with the WebSocket proxy？?

I wasn't able to find any document regarding the websocket. Does it support out of the box?

Yes, you can configure it through the admin web page or toml file. I will provide document later, may be version 0.6.0

It would be great if you could share toml config for the same here for the now. Thank you!

[servers.ws]
addr = "127.0.0.1:6188"
locations = ["ws"]

[locations.ws]
upstream = "ws"

[upstreams.ws]
addrs = ["124.222.224.186:8800"]

I tested it on http://www.websocket-test.com/

@vicanso, thanks for sharing the configuration!
Do you have any documentation for using https://hub.docker.com/r/vicanso/pingap with a docker-compose setup?

Sorry, I don't.

@vicanso, do the docker images support web UI?

Yes. cGluZ2FwOjEyMzEyMw== is base64("pingap:123123").
docker run -it -d --restart=always \
  -v $PWD/pingap:/opt/pingap \
  -p 3018:3018 \
  vicanso/pingap -c /opt/pingap --admin=cGluZ2FwOjEyMzEyMw==@0.0.0.0:3018

authors: Akagi201 Hareramrai vicanso

repo: vicanso/pingap


text:
🛑 SC is down

In 95c7697, SC (https://shop.line.me/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SC is back up in c253307.

repo: vichaos/upptime


text:
[Community skin] --audio-controls-color does not apply on all elements

Current Behavior:
media-community-skin[data-audio] {
  --audio-controls-color: xxx;
}

The color remain #f5f5f5.
Expected Behavior:
The color changed correctly.

Reason

Through these buttons are to --audio-controls-color by :where(media-community-skin[data-audio] [part~='media-ui'])
but :where(media-player [data-media-button]) has a higher priority setting it to var(--media-button-color, #f5f5f5)

Thanks for reporting! I'll release the fix as part of next patch. For now, set --media-button-color as well until it's patched.

repo: vidstack/player


text:
北邮之耻

怎么敢在之前的视频里卖情怀的，tm开源代码都能偷？真以为回学校演讲校友把你当人看？
回学校找校友帮忙一分钱不给还好意思标榜为爱发电，本科绩点后20%的天才科技博主？

Duplicate of #25.

您的issue不符合GitHub Community Code of Conduct的精神，重复的内容可能会打扰到开发者并给开发者带来困扰（issue会通过email通知开发者）
请转移到 #25 去讨论此事，并关闭此issue

何同学视频特效做的还是可以的，硬贴金搞这些。真没什么科技含量，科技感到是拉满了。很会做PPT的一类人。


text:
Support native rails fixture format

The default format for sprig seems very similar to the native fixtures format. It seems like it should be possible to support both with a combination of a new parser and some changes to the lib/sprig/seed/record.rb class.

Pull request with simple proof of concept above. Interested to hear others thoughts.

Sorry @AndrewSwerlick for the delay, I'm not sure how I missed the notification for this PR. I'll take a look this week.

No worries. I've actually decided not to use this specific feature and instead use dynamic fixtures to convert from the sprig format to the fixture format, so it's not a huge need for me anymore.

authors: AndrewSwerlick ltk

repo: vigetlabs/sprig


text:
LLP compression is 10% worse than the Java version

As per title.
This has been repeatedly verified on both the Software Heritage graph (by @progval) and on the cnr-2000 benchmark (by @vigna).
Reason unclear at the moment.

This is no longer the case. Closing.

repo: vigna/webgraph-rs


text:
Update cats-core to 2.2.0

Updates org.typelevel:cats-core from 2.1.1 to 2.2.0.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "cats-core" } ]

Applied Migrations

github:typelevel/cats/Cats_v2_2_0

Documentation:

https://github.com/typelevel/cats/blob/master/scalafix/README.md#migration-to-cats-v220

labels: library-update, semver-minor, scalafix-migrations

Codecov Report

Merging #40 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #40   +/-   ##
=======================================
  Coverage   84.31%   84.31%
=======================================
  Files          28       28
  Lines         816      816
  Branches       27       27
=======================================
  Hits          688      688
  Misses        128      128

Impacted Files
Coverage Δ

...ain/scala/io/github/vigoo/desert/BinaryCodec.scala
94.73% <ø> (ø)

...src/main/scala/io/github/vigoo/desert/codecs.scala
84.27% <ø> (ø)

...ub/vigoo/desert/zio/ZioBinaryDeserializerOps.scala
100.00% <ø> (ø)

...thub/vigoo/desert/zio/ZioBinarySerializerOps.scala
100.00% <ø> (ø)

...main/scala/io/github/vigoo/desert/zio/codecs.scala
100.00% <ø> (ø)

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 07c365c...ca173ce. Read the comment docs.

authors: codecov-commenter scala-steward

repo: vigoo/desert


text:
lazy load on vim.notify

Since there is no discussions section in this repo, I am asking a question as an issue, so apologies in advance!
I am trying to switch to this plugin from nvim-notify, not a fan of popups!
I use the following somewhere in my config:  vim.notify = require("notify") when i use nvim-notify. That way I can lazy load nvim-notify with packer using module = "notify", and have it loaded on vim.notify calls.
How do I do something similar with this plugin? I can of course do module = "notifier" but that does not allow it to be lazy loaded when some function calls vim.notify.
Basically any method that allows me to lazy load this plugin on vim.notify calls?

You could do something like:
vim.notify = function(...)
   require("notifier").notify(...)
end

authors: folke ranjithshegde


text:
Add a carthage compatible badge to README.MD

Abstract
Add a carthage compatible badge to README.MD

Hi, I added the following line to my Carfile, but it does not seem to work.
github "vikmeup/SCLAlertView-Swift"
*** Skipped building SCLAlertView-Swift due to the error:
Dependency "SCLAlertView-Swift" has no shared framework schemes

If you believe this to be an error, please file an issue with the maintainers at Optional("https://github.com/vikmeup/SCLAlertView-Swift/issues/new")

Could you show me how to use this package with Carthage?

Found the issue. Please rename or remove tag 0.22 in the releases. Thanks!

repo: vikmeup/SCLAlertView-Swift